Welcome to our weekly update from the chair of ADT. All the news that’s fit to print about the progress of the Archive of Our Own is below the cut. This post may also be found on the Archive of Our Own which is commentable by anyone with or without an AO3 account. Comments are disabled elsewhere as we’re noticing people ask similar questions and would like everyone to be able to share the discussion.
Sat 11pm meeting. I was sick and slept instead but had peppered the agenda with comments and the latest schedule updates (hopefully coherent ones) and sent out a plea for someone to chair the meeting. The lovely ![[info - personal]](http://s.dreamwidth.org/img/silk/identity/user.png){kind=small}
bingeling came to my rescue and stalking the transcript after says they don’t need me at all :p
- Deploy schedule: Next deploy to Beta currently scheduled for 8th November (Release 0.7.1). Also I gotta stop saying ‘push it back’ when talking scheduling because it doesn’t mean the same thing to all of us and I should know better 🙁
- Admin News Post comment email: the link in the email doesn’t work, we’ve put the underscore back in the right place for this deploy.
- AO3 Logo: Temporary logo is on Test. Official Logo competition deferred until we can recruit someone to run it. Heh, the front page in Test is currently displaying: "Latest work: This is a story with very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very very verylong title" *loves on testers*
- Autocomplete: Stopped working for the Post New form when entering tags. We’ve got a fix for that – it’s on Test – and can I just say rustler is awesome 🙂
- Invitations: the code is on Test (yay elz!) , it can do all sorts of things. I turned the invitations queue on and off, entered some email addresses into the queue, checked my predicted invite time and bounced around excitedly. I also issued invite codes to my user account, sent them to other testers and generally poked things. It still need some enhancements (this is the first version of a whole new feature and a big piece of work) but we’re very happy with it so far.
- Open Beta: Mid November. We think we can squeeze the planned stability period (where you deploy code then stare at it and wait for it to explode) down to one week . We wanted two but that was when were doing one deploy containing EVERYTHING rather than splitting it into 0.7.0 (on Beta now) and 0.7.1 (coming to Beta soon).
- Test Team: Are amazing! A piece of work we do after a code deploy is to go through all the issues and confirm that the changes got deployed and are working as expected. That means they do all the testing/verification they did on Test again on Beta (except without creating junk data). There were 89 in total (there were 90 but one fix failed testing) and we’re already down to only 39 waiting for verification.
- Stuff coming up:
- Admin Stats! Yes, I know I’m the only one who cares but OMG I care a lot! *cradles the JQuery plugin tenderly*
- Languages: We’re at the point where we can talk to the Translation team about what languages to add so that people can specify what language they are posting in.
- Notes: *grins* Yes, you may have 5k character Notes, we’re extending the limit.
- Task Queue: We’re conscious that one of the first things you do with a shiny new account is import your back catalogue of works, this hasn’t been a problem in Closed Beta because we add people in such small amounts. Performance testing suggests the AO3 can handle quite a lot before it slows down but we’re looking at ways to make this not an issue. Long term we’ll probably set up a task queue so you can start importing and it will import when it can if it can’t straight away.
If there are things you want to do/say – feel free to share either in comments, or by volunteering, or by messaging or whatever medium you’re comfortable with. You are invited to this party 🙂