AO3 News

Post Header

Published:
2013-05-20 14:58:03 -0400
Tags:

We would like to thank everyone who responded to our previous call for Support Staff. The chairs are reviewing applications and should be contacting people within the next two weeks.

Today, we're excited to announce the opening of applications for:

  • Testing Volunteer - Closes May 27th
  • Web Developer Staff - Closes May 27th

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don't see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist volunteers (at) transformativeworks.org in your e-mail client. If you do not receive the auto-reply within 24 hours, please check your spam filters and then contact us.

Note: We are continuing to work on a set of Volunteering Frequently Asked Questions that we hope to have posted within the next few weeks. If you have any questions about volunteering for the OTW, please let us know.

Testing Volunteer
The Accessibility, Design, & Technology committee (AD&T) is the guiding body that coordinates software design and development on behalf of the Organization for Transformative Works. AD&T is committed to developing high quality, accessible products that support the goals of the OTW while providing opportunities for professional and personal growth for its members. The main project concerning AD&T right now is the Archive of Our Own.

Quality Assurance & Testing (QA&T) is a subcommittee of AD&T responsible for testing bug fixes and new features before they go live, overseeing release and issue management tasks, and maintaining relevant documentation.

We are currently looking for motivated testers to join our team of volunteers and help us test new code before deploys. More information is available at the Testing Volunteer application. Applications are due May 27th.

Web Developer Staff
Do you have experience with Drupal and website management? Join our team of Web Developers! Web Developers are responsible for improvements to and maintenance of the primary OTW web properties. You will participate in an on-call rotation with other Web Developers, design and implement new features and fixes for the websites, and help to determine priorities for future web development efforts. More information is available at the Web Developer application. Applications are due May 27th.

Comment

Post Header

Published:
2013-05-05 18:25:29 -0400
Tags:

We would like to thank everyone who responded to our initial call for Tag Wranglers, AO3 Documentation Volunteers, and Communications Staff. The AO3 Documentation Lead and Communications Chairs are reviewing applications and should be contacting people within the next two weeks.

Today, we're excited to announce the opening of applications for:

  • Support Staff - Applications due May 12
  • Tag Wrangler Volunteer (reopening) - Applications accepted on an ongoing basis (role may be temporarily closed based on level of interest)

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don't see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

All applications generate a confirmation page and an auto-reply to your e-mail address. We encourage you to read the confirmation page and to whitelist volunteers (at) transformativeworks.org in your e-mail client. If you do not receive the auto-reply within 24 hours, please check your spam filters and then contact us.

Note: We are working on a set of Volunteering Frequently Asked Questions that we hope to have posted within the next few weeks. If you have any questions about volunteering for the OTW, please let us know.

Support Staff
The Support Committee handles communication between users and the various teams involved with the Archive of Our Own. We receive questions and ideas about all aspects of the Archive from users. The Support team helps to answer questions about using the Archive, diagnosing issues, documenting bugs for the coders to address, getting the most out of features like skins or challenges, passing on questions about tags to the wranglers, documenting requests for new or improved features, or getting answers about general policy.

If you like to interact with a wide variety of people through email and answer their questions, if you're familiar with the Archive, and you like finding the answers to issues, you might enjoy working as Support staff! To come join us, fill out the Support job description and application form. Applications are due May 12

Tag Wrangler Volunteer
The Tag Wranglers are responsible for keeping the hundreds of thousands of tags on AO3 in some kind of order! We choose which form of a fandom title appears on the Media pages, as well as all the character, relationship, and additional tags which appear in the filters and the auto-complete. We link tags together to make all the works and bookmarks on the archive easier to browse and search (so that users can find exactly what they’re looking for, whether that’s alternate universes with Cloud Strife, Steve/Tony and tentacles, or g-rated Rose/Kanaya fluff!)

If you like organizing, bringing order to chaos, excuses to fact-check your favorite fandom canons, or you just get a kick out of seeing all the wacky and wonderful terms fans come up with, you might enjoy tag wrangling! To join our team, click through to the Tag Wrangler job description and application form. Applications are accepted on an ongoing basis

Comment

Post Header

Published:
2013-04-12 14:44:04 -0400
Tags:

We are pleased to announce that our first applications for new OTW volunteers are open! We have three roles from across the OTW in the first round:

  • AO3 Documentation Volunteer
  • Communications Staff (Media Outreach)
  • Tag Wrangler Volunteer
    Updated 14 April 2013 - Due to the fantastic response from individuals interested in Tag Wrangling, we've temporarily closed the application while we train the over 50 volunteers who have already responded and get them settled in. We aim to reopen Tag Wrangler recruiting in mid-May.

We have included more information on each role below. Open roles and applications will always be available at the volunteering page. If you don't see a role that fits with your skills and interests now, keep an eye on the listings. We plan to put up new applications every few weeks, and we will also publicize new roles as they become available.

You may be wondering why you aren't seeing positions listed here that you know are open. Those committees are finalizing their position descriptions and training plans, and we will be posting those opportunities when they're ready.

If you have any questions about volunteering for the OTW, please let us know through the Volunteers & Recruiting contact form.

AO3 Documentation Volunteer
The AO3 Documentation Workgroup manages external AO3 docs such as the FAQs and Tutorials, and helps create and/or expand our internal knowledge base.

We’re looking for some people who are familiar with the Archive of Our Own and are good at writing and proofreading help documentation. If this sounds like something you’re interested in, click through to read the full details and apply to join the workgroup. Applications are due April 26

Communications Staff (Media Outreach)
Communications has primary responsibility for internal and external communication for the OTW. We manage the OTW blog and social media outlets and assist other teams in managing project-specific communication. We also field requests from outside the organization and work to spread awareness of the OTW and its projects.

We’re currently looking for someone to perform Media Outreach, which involves making direct pitches to media contacts and working to place stories about the OTW. If you have knowledge or experience in the area of media relations and are interested in helping build up our communication strategies, click through to learn more about the role and apply to join the Communication Staff Applications are due April 26

Tag Wrangler Volunteer
The Tag Wranglers are responsible for keeping the hundreds of thousands of tags on AO3 in some kind of order! We choose which form of a fandom title appears on the Media pages, as well as all the character, relationship, and additional tags which appear in the filters and the auto-complete. We link tags together to make all the works and bookmarks on the archive easier to browse and search (so that users can find exactly what they’re looking for, whether that’s alternate universes with Cloud Strife, Steve/Tony and tentacles, or g-rated Rose/Kanaya fluff!)

If you like organizing, bringing order to chaos, excuses to fact-check your favorite fandom canons, or you just get a kick out of seeing all the wacky and wonderful terms fans come up with, you might enjoy tag wrangling! Updated 14 April 2013 - Due to the fantastic response from individuals interested in Tag Wrangling, we've temporarily closed the application while we train the over 50 volunteers who have already responded and get them settled in. We aim to reopen Tag Wrangler recruiting in mid-May.

Comment

Post Header

Published:
2011-01-02 17:04:09 -0500
Tags:

Do you love the Archive? Do you have skills in database analysis? Would you like to make these great two tastes taste great together?

We're looking for a MySQL database developer who can help us optimise our database performance on the Archive of Our Own. The Archive is run on MySQL 5.0 and Rails 3, but you don't need to know Rails to help -- we would really like someone who can look over our database query logs and help us spot inefficiencies!

You'd be joining a team of dedicated and passionate volunteers with a love of fandom and tech-geekery. We're looking for someone with the time and skills to help us evaluate and optimise our current setup — this can be a short-term commitment, although if you are able to join us for the long haul your skills will be very welcome.

If you're interested, please contact our Volunteers and Recruitment Committee using 'MySQL database developer' as your subject line, and let us know your skills and experience.

Your Archive needs YOU!

Comment

Post Header

Published:
2010-03-27 06:28:44 -0400
Tags:

Help review the Archive FAQ!

Our goal for the Archive of Our Own is that it should be as accessible and usable as possible. An important aspect of this is documentation - we want our FAQ to be clear and useful. It's a big job writing documentation for a site like the Archive, and we'd love our users' feedback. When we have completed our review of the FAQ, our wonderful translators will be translating it, making the Archive even more accessible to international users.

If you are a user of the Archive and you'd like to help, please do the following:

  1. Pick a section (or part of a section) on the Archive FAQ and read through it carefully. (It's a good idea to check the comments here to see what has already been discussed.)
  2. Think about the following:
    • Is it clear and understandable?
    • Does it tell you what you need to know about the feature it describes?
    • Is it accurate? (Some things on the Archive may have changed since it was written!)
    • Does it use exclusive language (for example, does it involve descriptions that would only work for sighted users?)
  3. Leave a comment on this post noting anything you think we need to change. Tell us:
    • The section and question(s) you're commenting on.
    • Any wording which is unclear or problematic (and suggestions for improvements if you have them).
    • Anything which is inaccurate.
    • Any questions which are not answered at all.
    • Anything else you think we should know.

Example:

Section reviewed: Importing and mass editing.

Question: 'How do I import a single work?'
- It says 'you'll see the import form' - biased to sighted users. Could say 'The import form will load'.
- It says you have to go to the 'Post New Work' form but there's also a link on the main page.

Question: 'How do I import a chaptered work?'
- This section is a bit confusing, the formatting should make it easier to see that there are different instructions for importing from FF.net and from other sites.

Comment

Post Header

Published:
2010-03-16 16:48:51 -0400
Tags:

Do you like playing around the AO3 and finding issues to report back? Do you want to help out with the project but you're not sure how? If you answered yes to any of the questions above this post is for you.

Whenever we have a new release of code, we need to verify on the main (Beta) Archive that fixes are actually working before labeling a bug fixed. We have a lot of these after this release and we could use your help verifying them.

These bugs live in our issue list at our Google Code project.

What can you do to help:

You can find list of things that needs verifying at our list of deployed to beta issues.

  1. Sign in using the link on top left corner. Any google account will work (gmail, gchat etc). Your comment will display the name associated with that account, so be sure it's one you're happy to display publicly.
  2. Pick an issue that you would like to read more about and click on it.
  3. Read through the comments.
  4. Test to see if the issue is fixed or not, or if the new feature is working as expected.
  5. Use the comment field at the bottom to leave feedback.

Testing tips

Try to play around with the issue or feature reported.

  1. Does it work when things are done correctly?
  2. Does it handle things correctly when done in a different way? (e.g. what if you put in optional tags, or don't put them?)
  3. How does it handle errors (for example if you are testing the form for posting a new story, what happens when you forget to put a title in? Does it allow you to still post when it shouldn't?)

Try to keep track of what you did step by step.

Writing your feedback comment

Whether you found out that the problem is fixed or is still persisting, please write down step by step what you did. Browser information will also help us. Below is an example report which would be written after testing the bookmark feature.

Testing on Firefox 3.5.

  1. I click the add bookmark link
  2. Fill out tags
  3. Press submit
  4. It works

I also tried adding a comment. No problem there either. The form now works as expected.

What if I run into an unrelated problem while testing?

If you run into something unrelated while testing, or would like to give us additional feedback or suggestions, please do not do so in Google Code, but use the support and feedback form on the Archive. This will allow us to avoid duplicate issue creation and keep things in the right place.

If you enjoyed doing this and would like to assist testing regularly, apply to be a volunteer and mention you would like to join the testing team. We can always use more people.

Please feel free to comment under this post with any questions. Thanks for your time and effort :)

Comment


Pages Navigation