AO3 News

Post Header

2010-08-09 21:27:19 UTC

This isn't so much a meeting update as a general round-up of news from AD&T, since the writing up of reports, er... got away from me a little. But that means it is an extra tasty update!

Recent updates

We deployed new code to the Archive at the end of May - see the exciting list of new features in the Release 0.7.5. This release includes our new advanced search and a revamp to the HTML parser - this stuff was tricky to test and we're proud that the small amount of support requests suggests our testers did a great job of catching all the bugs!

Coming soon - Skins!

We're currently testing some awesome code on our Test archive. All being well, the next deploy will include the long-promised Archive Skins feature - you'll be able to choose from a range of lovely skins created by Archive staff, and create your own custom CSS. We know that lots of people have been looking forward to the opportunity to make the Archive look exactly the way that they want, and this will soon be possible! We're looking forward to seeing the beautiful designs people come up with. So exciting!

Rails upgrade - Faster! Better! More sparkles!

Our next big code project is to upgrade Rails, the application framework the Archive is built on. The latest version of Rails, v. 3.0, has lots of neat new features which will enable us to write much cleaner, faster code. In preparation for this change we have been writing lots and lots of automated tests, which will help us ensure we haven't broken anything in the move.

Refactoring - Code makeover

As we develop more automated tests and get ready to upgrade our version of Rails, we are also refactoring our code. Refactoring involves rewriting the code to make it much neater, more efficient and more beautiful. It's something which is necessary in all programming, but it's particularly important in a big project like ours with lots of contributors: by refactoring the code to make it more elegant, we make it easier for other people to work on it and smooth out any of the lumps and bumps which may have sprung up. Refactoring also improves the performance of code, and it's an important foundation for the next wave of development on the Archive.

Internationalisation on the Archive

We had a very exciting and productive conversation with the International Outreach Committee about the features the Archive needs in order to serve the fannish community internationally. All the work we have been doing on writing automated tests and refactoring will help a lot with developing our international features - we had to retire our old interface for translating the Archive because it caused some major performance issues, so we want to be sure that the new one we are planning will work smoothly. In addition to translations, we've also been discussing ways of improving our system for indicating the language of a work, browsing for works in particular languages, and setting useful defaults for language options. We're very lucky to have a brilliant International Outreach team who help us to see all the angles for our international membership - it's something we try to consider at all times, but it's very helpful having a team who are dedicated to this aspect of our work.

Introducing the new Tag Wranglers committee!

As most users know, the tags are the Archive are managed and organised by our behind-the-scenes team of dedicated and awesome tag wranglers. Until recently, tag wranglers were a subcommittee of AD&T, but there are now 133 volunteer wranglers working around the world to organise more than 99,666 tags, so it was high time for them to take on a more formal committee role. AD&T are very proud to see new committee chair Renay and her awesome team step out on their own: we'll be working closely with the new committee and we know that this change will help to ensure that Archive users continue to get a great experience.

News from our sub-committees and sister committees

  • Coders are working hard on writing automated tests, refactoring, and getting ready for the Rails 3 upgrade.

  • Testers are working on our new set of code on the Archive, and giving the new Skins option a workout!

  • Tag wranglers have been adjusting to their new identity as a committee in their own right, figuring out some new policies, and generally being awesome.

  • Support continue to do awesome work, answering most requests within a couple of days. They are a small but dedicated team and we value their hard work! (Don't forget that if you need a response from Support, you must leave a contact email address.)

If there are things you'd like to do or say, please share them in comments, via the AO3 support and feedback form, by volunteering, or in whatever medium you feel comfortable with. Everyone is welcome to this party!


Post Header

2010-07-16 09:09:37 UTC

Предлагаем вашему вниманию версию 2846 архива, которая приходит на смену версии 2732. Над этим релизом работали сразу девять человек! \0/ Нам особенно приятно отметить, что некоторые из наших новых программистов уже чувствуют себя достаточно уверенно для того, чтобы браться за все более сложные задачи! Мы также с огромным удовольствием приветствуем новых членов нашей команды бета-тестеров. :D

Ключевые моменты

Переработка кода и улучшение производительности

Наши ведущие программисты по-прежнему упорно трудятся над переработкой некоторых ключевых фрагментов кода архива с целью улучшения его производительности. Этот процесс включает в себя редактирование программного кода для того, чтобы сделать его более простым, более понятным и более эффективным. В целом это можно сравнить с вдумчивой, очень тщательной вычиткой текста. Обновленный код должен обеспечить заметные улучшения в плане скорости работы сайта. Это текущий проект, так что работы над улучшением кода будут продолжены.

Автоматическое тестирование

Наряду со внесением изменений в программный код, мы также работали и над улучшением автоматических тестов, в чью задачу входит проверка корректности работы нашего кода. Они упрощают процесс переработки (очень удобно иметь под рукой быстрый способ проверить, не был ли код испорчен в процессе редактирования) и помогают удостовериться в том, что внесенные изменения не вызывают проблем. В этом отношении нам очень помогли наши новые программисты. Мы используем систему под названием Cucumber, которая дает возможность писать автоматические тесты в более дружелюбном интерфейсе, и мы ради видеть, что ее возможности привлекают все больше новичков.

История просмотров

Мы добавили несколько новых опций в историю просмотров - одну из наших самых замечательных функций, которая позволяет отследить, что именно вы читали в Архиве, чтобы вы могли легко найти тот рассказ с наручниками, который вы читали на прошлой неделе. (Видеть историю можете только вы; в любом случае эту функцию можно полностью отключить в настройках аккаунта.) Теперь появилась возможность полностью очистить вашу историю просмотров. Также был добавлен счетчик, который позволяет вам узнать, сколько раз вы просматривали любую из работ. Если вы все еще не используете историю просмотров, то сейчас самое время начать - в будущем мы планируем существенно расширить эту функцию.

Известные проблемы

Со списком известных проблем вы по-прежнему можете ознакомиться в соответствующем разделе сайта.


Post Header

2010-07-16 09:08:21 UTC

Anmerkung der Übersetzerinnen: Alle Links in diesem Text führen zum Archiv, das zur Zeit nur auf Englisch vorliegt. Für weitere Details siehe die englische Version der Anmerkungen.

Willkommen zur Revision 2846, die auf Revision 2732 folgt. Neun verschiedene ProgrammiererInnen haben an dieser Veröffentlichung gearbeitet. Wir freuen uns besonders, dass einige unserer neueren ProgrammiererInnen an Selbstvertrauen gewinnen und mehr und mehr Bugfixes beisteuern. Außerdem konnten wir neue Leute in unserem Test-Team willkommen heißen. :D


Refaktorierung und Leistungsverbesserung

Unsere erfahrenen ProgrammiererInnen haben schwer geschuftet und wichtige Codeabschnitte refaktoriert, um deren Leistung zu verbessern. Refaktorierung heißt, dass der Code umgestaltet wird, damit er weniger komplex, einfacher zu verstehen, und effizienter wird. (Ein bisschen so, als würde man den Code gründlich betalesen.) Der refaktorierte Code sollte einige deutliche Verbesserungen in punkto Geschwindigkeit bedeuten. Dies ist ein andauerndes Projekt, und wir werden noch einiges am Archiv refaktorieren.

Automatisierte Tests

Neben dem Optimieren von bestehendem Code haben wir auch die automatisierten Tests verbessert, die prüfen, ob der Code auch das tut, was er sollte. Das macht das Refaktorieren wesentlich einfacher (da man schnell prüfen kann, ob Umschreiben den Code vielleicht unbrauchbar macht) und hilft sicherzustellen, dass weitere Änderungen keine Probleme verursachen. Auf diesem Gebiet hatten wir großartige Beiträge von unseren neuen Programmiererinnen – wir benutzen ein System namens „Cucumber“, das das Schreiben von automatisierten Tests viel angenehmer macht, und wir freuen uns dass sich dadurch mehr Leute einbringen.


Wir haben ein paar zusätzliche Optionen zur Chronik hinzugefügt. Dieses schicke Feature verfolgt, was ihr im Archiv lest, damit ihr (zum Beispiel) leicht zurückverfolgen könnt, welches nochmal die Geschichte mit den Handschellen war, die ihr letzte Woche gelesen habt ... (Nur ihr könnt eure Chronik einsehen, oder aber in den Einstellungen komplett ausschalten.) Es ist jetzt möglich, die gesamte Chronik zu löschen, und ein Zähler zeigt, wie häufig ihr ein bestimmtes Werk angeschaut habt. Falls ihr die Chronik bis jetzt noch nicht genutzt habt: es lohnt sich, und wir werden in Zukunft noch mehr Funktionen einbauen.


Post Header

2010-07-16 09:05:16 UTC

Nota de la traducción: Todos los enlaces llevan al Archivo, que por ahora sólo está disponible en inglés. Ver los detalles de la nueva revisión en la versión en inglés.

Bienvenid@ a la Revisión 2846, actualizando la número 2732. ¡Nueve programadoras diferentes trabajaron en esta revisión! \0/ Estamos especialmente emocionados de ver nuestras más nuevas programadoras ganando confianza y realizando más arreglos. Estamos también muy felices de haber recibido unas cuantas nuevas personas a nuestro equipo de pruebas.

Los puntos más destacados de esta entrada están ahora disponibles en English, Deutsch y Русский.

Puntos importantes

Arreglos de refactorización y rendimiento

Nuestras programadoras más experimentadas han estado trabajando mucho para refactorizar algunas secciones claves para mejorar el rendimiento. Refactorizar significa re-escribir el programa para hacerlo menos complicado, más fácil de entender, y más eficiente. Es un poco como darle al programa un buen beteado. El programa refactorizado debería conllevar algunas mejoras notables en la velocidad. Este en un proyecto continuado y vamos a estar refactorizando el Archivo mucho más.

Pruebas automatizadas

Al mismo tiempo que hemos mejorado el programa en sí mismo, hemos estado trabajando en mejorar las pruebas automatizadas que prueban si el programa está haciendo lo que debería. Esto hace que sea mucho más simple refactorizar (es agradable tener una manera rápida de probar que re-escribir el programa no lo rompió) y ayuda a asegurar que otros cambios no han causado problemas. Hemos recibido buenísimas contribuciones de nuestras programadoras más recientes en esta área - estamos usando un sistema llamado Cucumber (NT: pepino) que hace escribir las pruebas automatizadas mucho más amigable, y estamos felices de notar que está atrayendo a más gente.

Historial de lectura

Hemos agregado alguna opciones más al Historial de lectura - una de nuestras características más ingeniosas - que sigue lo que lees en el Archivo para que puedas fácilmente encontrar esa historia que leiste la semana pasada con las esposas. (Sólo tú puedes verlo, y puedes apagarlo en preferencias si prefieres.) Ahora es posible limpiar tu Historial de lectura completo, y hemos agregado el número de veces que haz visto un trabajo en particular. Si no haz estado usando el Historial de lectura hasta ahora, vale la pena hecharle una mirada - vamos a estar añadiéndole algunas nuevas características en el futuro.


Post Header

2010-07-16 08:59:55 UTC

The highlights of these release notes are also available in Deutsch, Español and Русский. Many thanks to our fantastic translation teams!

Welcome to Revision 2846, up from 2732. Nine different coders worked on this release! \0/ We're especially excited to see some of our newer coders growing in confidence and committing more and more fixes! We're also very happy to have welcomed some new folk to our testing team. :D



Refactoring and performance fixes

Our senior coders have been working hard on refactoring some key sections of code to improve performance. Refactoring involves rewriting the code to make it less complicated, easier to understand, and more efficient. It's a bit like giving the code a really good beta. The refactored code should bring some noticeable improvements in terms of speed. This is an ongoing project and we'll be refactoring lots more of the Archive.

Automated tests

Along with improving the actual working code, we've been working on improving the automated tests which test whether the code is doing what it should. This makes it much easier to refactor (it's nice to have a quick way to check that rewriting the code hasn't broken it) and helps ensure that other changes haven't caused problems. We've had some great contributions from our newer coders in this area - we're using a system called Cucumber which makes writing automated tests much friendlier, and we're happy to see it drawing more folk in.

Viewing history

We've added some more options in viewing history - one of our neatest features - which tracks what you read on the Archive so you can easily find that work you read last week with the handcuffs. (Only you can see it, and you can turn it off in preferences if you prefer.) It's now possible to clear your entire viewing history, and we've also added a count of the number of times you have viewed any given work. If you haven't been using viewing history up until now, it's well worth checking out - we'll be adding some more features in the future.

Known Issues

See our Known Issues page.

Release details


  • FAQ - Split FAQ sections onto separate pages for faster loadtimes and easier navigation.

  • FAQ - Added ability for admins to delete and reorder FAQ sections.

  • FAQ - Added validation so that all sections of the FAQ must have a title.

  • Improved search function to work with limited terms, so that it's easier to link to a specific search.

  • Added a list of all fandoms a user has created works in to user home page.

  • Improved the options for chapter edits on multi-chapter works so that work edit shows only the details for the whole work, while editing chapter by chapter shows the details for the chapter.

  • Made many small formatting and cosmetic consistency changes to the TOS and TAS FAQ.

  • Viewing history - added an option to clear entire history.

  • Viewing history - added a counter for the number of times you have viewed a work.

  • Collections - added 'x results found' to search results.

  • Improved URL autocomplete function on external bookmarks.

  • Added a way to add or remove an author from a series as a whole.

  • Added the ability to mark a series as complete.

  • Added a link to the account rename function from the edit profile page.

  • Added lots more automated tests!

  • Added some icons optimised for users with low vision as part of our ongoing preparations for alternative skins.


Bug Fixes

  • Fixed a bug which was preventing the editing of bookmarks created before we upgraded our bookmarking function.

  • Tweaked the wording of gift notification emails to reflect our current functions.

  • Ensured that all automated Archive emails include a link to our Support form.

  • Ensured that unused drafts will be deleted after one week (intended behaviour) - in the future we'll have better draft functionality, but for now this ensures they don't cause problems.

  • Fixed a bug which was causing unrevealed multichapter works to be inadvertantly revealed!

  • Fixed a problem where drafts in a series caused problems with series numbering and reordering.

  • Fixed a bug which caused a 500 error when someone other than the creator tried to access an unposted chapter in a work.

  • Fixed error redirects so that trying to access a page for a non-existent user gives a 404 error instead of a 500 error.

  • Fixed bug causing overlapping navigation on comments - you can reply to comments again!

  • Ensured that gift notification emails do not include an empty slot for the name of a collection if the gift is not part of a gift exhange challenge.

  • Tweaked the wording on our admin settings page to make more sense!

  • Fixed inspiration function to ensure that URLS are properly saved and it's possible to add more than one work as an inspiration.

  • Fixed broken comment links on multichapter works.

  • Added missing p tag in the TOS FAQ.

  • Tweaked work blurbs so that the count for bookmarks only includes publicly posted bookmarks.

  • Performance fix - moved values for hit counters to their own database table.

  • Performance fix - refactored the series blurb for greater efficiency and faster load times.

  • Performance fix - masses of refactoring across the site for cleaner code and much improved performance.

  • Performance fix - improvements to mass wrangling pages to make them much faster and more efficient.

  • Performance fix - refactoring on people page to make it load faster and be usable.


Post Header

2010-06-09 22:11:05 UTC

This was a landmark meeting for us - we got through the entire agenda! Several members of the committee were absent because it was a holiday weekend, and those who remained were slightly distracted by the Eurovision Song Contest, but apparently we were borne upwards on butterfly wings!


  • We discussed our volunteers process and ways of making it easier for more people to get involved. We have a lot of awesome and dedicated people on this project, but we would like to make it easier for new people to get involved and to spread the workload a bit! If you know of examples of good practice, we'd love to hear about them.

  • We signed off on a whole bunch of small coding issues which have been waiting for a final bit of design. Coming soon - more control over visibility to search engines, a way of removing a co-author from a series, and a fix for the editing of some old and buggy bookmarks.

Recent updates

We deployed new code to the Archive at the end of May - see the exciting list of new features in the Release 0.7.5. This release includes our new advanced search and a revamp to the HTML parser - this stuff was tricky to test and we're proud that the small amount of support requests suggests our testers did a great job of catching all the bugs!

Archive Roadmap

We've just released an updated version of our Archive Roadmap, which gives an overview of all the amazing work which has been done so far and all the cool things we have planned in the future. We're really proud of what we've achieved - fandom power is awesome! Thanks to our brilliant translations team you can also read the Roadmap in Deutsch or Español.

If there are features you'd like to see in the Archive, then we'd love to hear about them! Please contribute your thoughts to our post on the future of the Archive!

News from our sub-committees and sister committees

  • Coders are gearing up to work on a new round of projects. We're about to revamp our translations code so that it can be used, making improvements on advanced search, and thinking about priorities for new projects.

  • Testers did a great job getting everything ready for the last release, and are now working through the new code on the Beta Archive to verify that it's still working well.

  • Tag wranglers did an awesome job of keeping up with the wealth of new tags introduced onto the Archive during two big challenges - Final Fantasy Exchange and Remix.

  • Support continue to do a great job keeping up with support requests - for one golden moment there were no unclaimed issues! They also did a great job of swinging into action when our Support form had a momentary hiccup. :D

If there are things you'd like to do or say, please share them in comments, via the AO3 support and feedback form, by volunteering, or in whatever medium you feel comfortable with. Everyone is welcome to this party!


Post Header

2010-06-09 09:36:36 UTC

Edit 18.37 UTC, 9 June 2010: The issue has been resolved and the Archive Support and Feedback form is now open for business again! Please submit your feedback and support requests via this form. Many thanks to our lovely users for your patience, and to the wonderful people on our teams who resolved this so quickly.


Due to an issue with the tool we use to host Support bugs, the Support form on the Archive is currently broken. We hope to have the problem resolved very soon, but in the meantime you can get in contact with our Support team via the temporary form on our website. If you would like to leave more general feedback, please feel free to do so via email or by leaving a comment on this post.

Responses may be slower than usual, and requests that came in before our form went down may also be subject to delays. Our awesome Support team will be doing their best to keep up - please bear with us.

We'll update again when the problem is resolved - thank you for your patience in the meantime!


Post Header

2010-06-03 09:36:09 UTC

This post is also available in Deutsch and Español.

We recently published an updated version of the Roadmap for the Archive of Our Own, which shows all the amazing work we've already done and all the big things we plan for the future. All the original plans for the Archive grew out of fannish ideas for a 'dream Archive', and we're really proud of the way those dreams are developing into reality.

Now that the Archive is a reality, we have started to think up features which we had never even thought of. We get loads of great feedback from the fannish community via our Support and Feedback form and have used lots of those ideas to make improvements. However, we always love to hear more ideas! If there's a new feature or an enhancement you'd love to see on the Archive, please comment on this post and let us know! What's your dream feature or the one thing that bugs you? Is there something we didn't mention on the Roadmap that you'd love to see us do? No suggestion too big or too small - tell us your sparkly unicorn ideas!

We can't promise to implement everything that is suggested, but we do our best to incorporate all the cool ideas we get from users. And if you'd like to help us turn even more ideas into a reality, we always welcome volunteers!


Pages Navigation