AO3 News

Post Header

Published:
2023-09-27 15:12:18 UTC
Tags:

Five Things an OTW Volunteer Said

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with Brian Austin, who volunteers as a coder for our Accessibility, Design & Technology committee.

How does what you do as a volunteer fit into what the OTW does?

I’m a coding volunteer with the AD&T (Accessibility, Design & Technology) committee. We’re responsible for writing the software that runs AO3, including adding new features and squashing pesky bugs. We also test changes to the Archive’s code before they go live to users to make sure what we’ve written does what we expect it to, and doesn’t have unexpected side-effects.

What is a typical week like for you as a volunteer?

Most often, I will either be writing code or testing changes before they go out to the production version of the Archive.

When I write code, either to add new features or fix old bugs, I start by looking through the AO3 Jira backlog for issues that are high priority, involve familiar parts of the code, or just sound interesting. Once I’ve found something to work on, I’ll tinker around on my laptop until things are ready for another volunteer or community contributor to review and incorporate their feedback.

For testing, I start in the same place: Jira. I use a filter to find issues that need to be tested before they go out to the Archive and go through the steps issue writers have created to test the changes. Exactly what this looks like depends on the changes; one recent example involved creating a work with loads of pipes (|) to make sure the word count doesn’t include them.

I sometimes review code as well, both to help when the more senior folks are super busy and to learn more about how Rails (the web framework the AO3 uses) works.

What made you decide to volunteer?

I started out as a community contributor after a suggestion from a friend (the same one who got me into fanworks). At the time, I was looking to contribute to an open source project and do something a little bit different than the code I wrote at work.

After about a year of writing code as a community contributor – and submitting a design proposal for a feature I really wanted – Accessibility, Design & Technology co-chair sarken messaged me to ask if I would like to join in a more official capacity. I had been wanting to get more involved, so it was an easy decision!

What has been your biggest challenge doing work for the OTW?

In some ways, writing code for the AO3 is a bit different than in a corporate setting. For example, “spinning up a new service to do X” is not as easy when you can’t push a button in AWS and “magically” get more computing resources or another database. That has an impact on how some features get designed, but so far it’s been a fun way to push myself to think differently.

What fannish things do you like to do?

Read lots and lots of fanfic! I’ve bonded with several friends by sharing different fics, and I may have a slight problem with subscribing to many WIPs. I read works across several fandoms, but most consistently works that take Obi-Wan Kenobi and give him a big metaphorical hug because, wow, Legends is rough to that poor soul. Check, Please! also has a special place in my heart for getting me into fandom in the first place.


Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in the comments. Or if you'd like, you can check out earlier Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

Comment

Post Header

Published:
2020-03-27 16:56:46 UTC
Tags:

Five Things an OTW Volunteer Said

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with Sarken, who volunteers as co-chair of the Accessibility, Design, & Technology Committee.

How does what you do as a volunteer fit into what the OTW does?

I'm a co-chair of the committee responsible for the development and maintenance of the Archive of Our Own codebase. The Archive provides a home for over five million fanworks, which supports the OTW's goals of preserving and providing access to fanworks.

What is a typical week like for you as a volunteer?

AD&T operates in release cycles, which generally last more than a week, but it's not uncommon to start the week by finishing a release: ensuring all of the changes have been tested, polishing the release notes, and letting other committees know about any changes that might affect their work before the new code is deployed to the Archive.

Once that's done, we wait about a day before putting the next round of code changes onto our staging site, where volunteers from AD&T and other committees test the changes. I usually help coordinate that work in addition to doing some testing myself.

While that's going on, we're also looking ahead to future releases. That involves prioritizing issues and making sure someone is available to write or review the code.

There are a lot of other tasks that might come up during a given week, too, such as handling requests for database work, consulting with Support, making bug reports, or updating documentation. If we're having a widespread issue like slowness or downtime, we also have to communicate the problem to users, which sometimes involves quickly drafting a news post, but almost always involves tweeting. (If someone is tweeting from @AO3_Status, there's a good chance it's me or my co-chair mumble!)

Once those tasks are handled, then I get to write some code!

What made you decide to volunteer?

In 2011, Elz -- one of the AD&T co-chairs at the time -- saw some of the site skins I'd made and asked if I'd like to volunteer. I'd been a fan of the Archive ever since astolat made her "An Archive of One's Own" post in 2007, so it was an easy yes.

I'm also a tag wrangler, which is a role I volunteered for specifically to improve my understanding of how the wrangling features are used. That knowledge comes in handy when working on the wrangling code, plus it makes it easier to communicate with the Tag Wrangling committee about bugs and feature requests.

What's the most fun thing to you about volunteering for the OTW?

The people! My team is terrific, and I really enjoy getting to talk to and work with people from other committees. There are people I talk to almost every day who I wouldn't have met without volunteering, and my life would be poorer for not knowing such kind, talented people.

Coding itself is a pretty close second, though. It's extremely satisfying to hunt down the cause of a bug, and nothing quite beats the "ah-ha!" moment when you finally solve it. Of course, that moment usually gets ruined pretty quickly by the realization you still need to write tests for your new code...

What fannish things do you like to do?

I've made a few vids and recorded some podfic, but my main fannish activity outside the OTW is writing fic. I mostly write het and femslash, or at least I try to write het and femslash -- about half of those attempts end up being gen.

And whenever I can, I love to leave long comments on fanworks I've enjoyed. You never know when you'll make someone's day, and sometimes you just might make a new friend.


Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in comments. Or if you'd like, you can check out earlier Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

Comment

Post Header

10 Years of AO3

When asked to write up a few words about his time with the OTW and AO3 in particular, james_ had so much to say that he had trouble sticking to the word count. (He’d like to thank Priscilla for helping him to edit!) Below you can read about some of the tougher times that james_ has seen during his time as a member of the Systems and Accessibility, Design and Technology committees. You can also hear about the rewards he’s gained from his hard work to keep our vision clear and our morale high. As you can see below, james_ was amongst the staffers who accepted the Hugo Award for Best Related Work on behalf of AO3.

Volunteering for the OTW in the early days was exciting, stressful, exhausting, and demoralising, but also worth it. At that time we were working with five servers and we were constantly adjusting the load between the few systems we had. We reached out to our friends at Dreamwidth (thanks, Mark) and they helped us. We were learning even as the tsunami of growing AO3 traffic beat down upon our shore.

While there are always people willing to try and pull you down, they are greatly outnumbered by those supporting us and buoying us up. I am grateful to each person who donates to the OTW. Your donations mean that we can afford the machines that keep the Archive running stably, and that nowadays I rarely get woken in the middle of the night due to unexpected downtime.

Something else that has had a significant impact in my volunteering life were the recurring conflicts both my committees had with previous iterations of the OTW Board of Directors. These were a source of great frustration and I even contacted the Legal committee to see how OTW members could call the board to account. After the resignation of the entire 2015 board, things have been much better. No organization is perfect, but I believe everyone in the OTW is very much happier today. I hope this will continue and believe the best way to do that is to ensure that every election is properly contested; I stood for election myself in 2016 and would do so again if necessary to make sure that there were enough candidates.

Our successes have been external as well as internal. This year, I had the pleasure of standing on the stage at Worldcon as AO3 won a Hugo Award and it was such a joy.

james_ holding the AO3’s Hugo award

As for the future, I believe that we will need to raise significantly more than we do today in order to hire paid employees. We cannot sustainably run forever on purely volunteer labor. We get roughly 5% of Wikipedia's pageviews and our budget is about one-third of one percent of theirs.

Comment

Post Header

Published:
2018-11-08 17:47:24 UTC
Tags:

Five Things an OTW Volunteer Said

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with Ariana, who volunteers a staffer in our Accessibility, Design, & Technology Committee and as the Senior Technical Staffer in our Open Doors Committee.

How does what you do as a volunteer fit into what the OTW does?

As a volunteer coder for both Accessibility, Design, & Technology Committee (AD&T) and Open Doors, I mainly help with the OTW's aim of preserving fan history. In my twenty-odd years of online fandom, I've seen many works and sites disappears and it's very satisfying to be able to do my bit to ensure that this happens less frequently in future.

What is a typical week like for you as a volunteer?

Because I have both children and a full-time job, I have to fit my OTW duties in around my "real" life. As a general rule, I will spend several hours at the weekend and at least one or two hours in the evening working on OTW projects, as well as attending the weekly meeting for AD&T and, when I can, the Open Doors one which is a bit late in my timezone.

Fortunately, as I'm a software developer in real life too, I can also sometimes sneak in code reviews, research, or a bit of coding at work without anyone thinking it odd -- as long as I remember not to actually open the Archive or any of the sites Open Doors is importing! Conveniently, we use a lot of the same tools at work too, including the messaging app used by the OTW, which means I'm able to keep in touch with other volunteers to ask or answer questions and keep track of any major projects we're working on.

Have you recently worked on any particularly interesting or challenging projects?

My main focus over the last couple of years has been to create a sustainable pipeline to import archives rescued by Open Doors into the Archive. This has involved adding a mass import API to the Archive and a generic website that Open Doors can use to feed external data into it. There are also a set of scripts that adapt the contents of the rescued archives to the format needed by the generic website. The main challenge now is how to process the variety of old archives with those scripts; since every site is different, importing each one is still a lot of work and we've recently recruited more technical volunteers to help with this. The aim is to make importing archives as painless as possible so we can provide a home to all the sites whose owners ask us to add them to the Archive.

What's the most fun thing to you about volunteering for the OTW?

Perhaps the most useful thing about volunteering for the OTW has been learning software engineering; when I started out as an AD&T coder six years ago, I only knew a bit of theory and some HTML, and now I'm a Principal Software Engineer for a big multinational company!

In a way that's been fun for me, too, because I love computing, but I think to be honest that the most fun aspect of volunteering has been meeting the people I volunteer with. Over the last few years, I've made a lot of friends, some of whom I even meet in real life on a regular basis! It's great to be able to share anything with a group of people who, though they are scattered across the globe, tend to share my fannish, geeky and open-minded views on things.

What fannish things do you like to do?

When I can squeeze a bit of free time, I love to write stories. Most are quite short, but every few years, I'll embark on something long and rambly: my current WIP is over 100,000 words and has been going for nearly two years now! I've always enjoyed making up stories in my head and imagining how the characters from some book or TV show might behave in a given situation. Thanks to the feedback of various betas over the years, I've improved a lot as a writer -- rather as I've improved as a coder!


Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in comments. Or if you'd like, you can check out earlier Five Things posts.

The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

Comment

Post Header

Published:
2018-02-23 16:49:40 UTC
Tags:

Five Things an OTW Volunteer Said

Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy. Today's post is with Cosette, who volunteers as a coder for the Accessibility, Design, and Technology (AD&T) Committee.

How does what you do as a volunteer fit into what the OTW does?

As an AD&T coding volunteer, I work with the open-source code that powers AO3. Coders are recruited to fix bugs, write tests, and develop features. We also work side by side with testing volunteers, to ensure the changes we've made to the code won't cause anything to catch fire.

What is a typical week like for you as a volunteer?

AD&T uses a project management tool to track issues (bugs, improvements, new features, tests, etc). So it typically goes like this:

  • Check the planning board for issues I think I can solve
  • Try to solve them
  • Sometimes: cry and dramatically shut my laptop
  • Most times: submit the solution

Other responsibilities include:

  • Creating issues for newly discovered bugs (things that aren't working as intended), improvements (things that could work better), new features (things that don't exist yet but will in the future), tests (automated tests that ensure the website behaves as intended), and so on.


  • Communicating with other members of the AD&T committee about my progress, and keeping up to date with their progress and plans as well.

  • Whenever questions come up, AD&T staff is always helpful in answering them! Also, there's usually some off-topic conversation in the chat room, which is fun.

    Do you have other roles in the OTW besides being a coder?

    Yeah, I also volunteer for Webs, which is the committee that maintains the OTW's website as well as the Elections and Open Doors websites. This mainly consists of fighting WordPress. Since I’m a liaison to Communications, I must also keep them up to date with any problems or changes to the website, and provide answers when they have questions or need a bit of help. Additionally, Webs offers technical assistance to other committees wherever they may need it.

    What's the most fun thing to you about volunteering for the OTW?

    The community. There's a lot of socialising that goes on in the OTW and you can always find someone with a common interest. I've never been a part of a working community that was entirely comprised of fans. In theory, you'd think that would be awesome, and in practice, it is.

    What fannish things do you like to do?

    Writing fanfiction!! Translating manga. And browsing fan art. Encouragement is everything so, when I see something I like, I tell the creator how much I love it. Also, brainstorming headcanons and AUs with friends. The existence of fandom is a pillar in my life and I want to do my part in protecting it and contributing to it; that's why I volunteer for the OTW.


    Now that our volunteer’s said five things about what they do, it’s your turn to ask one more thing! Feel free to ask about their work in comments. Or if you'd like, you can check out earlier Five Things posts.


    The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

    Comment

    Post Header

    Five Things an OTW Volunteer Said

    Every month or so the OTW will be doing a Q&A with one of its volunteers about their experiences in the organization. The posts express each volunteer's personal views and do not necessarily reflect the views of the OTW or constitute OTW policy.

    As part of our 10th anniversary celebrations, we have a special retrospective Five Things this month. Today's post is with Naomi Novik, one of the founders of the OTW, a past board member, and a current staffer with the Accessibility, Design, & Technology Committee. The following is an interview transcript which has been edited for length and clarity.

    What was the first year of the OTW like? What do you remember most from it?

    I don't remember the high points as well, I find that over time what I remember are the problems. In the beginning there was a lot of work we had to do to reassure people about what we were trying to do, such as that they weren't going to get into [legal] trouble, that there would be ways to give people control over their stories. The other piece that first year is that some people expected to see something 5 minutes after we formed! You know, where is the Archive? But it all takes time, there were a lot of growing pains you have when you're putting things together from scratch that the OTW has been left with. But my philosophy is to do the thing if you have the momentum, and it's better to have done something that was not perfect than to not have anything done at all.

    There were certain ways in which a sustainable organization doesn't work on passion, at the same time that you want to be able to harness passion. I think we were struggling a bit with how to get an organization running but at the same time have it grow. A lot of the details are gone for me now -- I have a terrible memory for this sort of thing because once something is no longer my problem, I forget about it, it's just gone.

    One example is figuring out Communications and what it was going to be like [for the OTW and as a committee]. [The early volunteers] were all on LiveJournal, and so regarding communications I thought that it would be just the newsletters we have, and then people from the organization posting on their journals and talking to other fans on an individual level. And it didn't work very well, and I wasn't involved myself, but I remember frustration that we weren't being very successful at doing what we wanted to do there.

    I was more involved on the technical level, which we had plenty of disagreements about too. Because the question was do you design it first, to have everything the way you want it, and then you build it or do you just start building? And I feel very very strongly that we ended up doing it the right way. We really did just dive in and start building. Overall, I'm quite happy with the success of that strategy, and then later, we know it's imperfect and there's things it doesn't do, so that unfortunately you haven't served everyone as well as you could have. It's a trade-off to having an archive.

    I do think, fundamentally, it was the right call, and we are not, by far, the first organization that had to make that call. There are many different ways to make that call and we could have done it in a better way. Now the cost of that strategy has to be paid over a long time. But what matters most to me is that we made something. And the work is being done to get it to a sustainable place. At the beginning there was a very propulsive sort of drive to establish something and to get it running.

    What do you see as the major turning points of the OTW during its ten years?

    We had a huge advantage at the beginning, which is that we started with a small group of people who mostly all knew one another. Me, [current OTW Legal staffer] Rebecca Tushnet and [current Transformative Works & Cultures staffer] Francesca Coppa knew each other, and the other first Board members were in relatively close geographical proximity to one another, so we could get together face to face and discuss things. That was a big help. But we also had enormous expertise in the early group -- legal, academic, pro writing, technical experts. The people on the first board were the lynch pins of their respective committees. So it was a small group that could work together closely and develop things quickly in their own areas.

    For a while in the middle of the OTW's growth we fell away from that. Being on the Board is a tough job and it takes an enormous amount of time to do the work well. I have done it well and have also done it poorly. It's not entirely, but is largely, based on how much time you have to offer, as well as the people you work with, and whether you can communicate with them effectively and whether there's a level of personal trust among you.

    I feel there was a terrible low point that we went through. There was a middle wave; there's been research done on this process among non-profits that shows that what the OTW went through is a common pattern. There is a visionary founder, or team of founders, who bite off much more than they can do. That approach leaves a lot of loose ends. The people who are then recruited and pulled in because of the vision that the founders established see the problems with what was done or with what is happening, but they feel frustrated because they may not have the access to the founders or to ways of solving the problem. So then things turn antagonistic on either a personal or organizational level. So the OTW then had lots of people running for the Board being against what was happening to the Board.

    So while things aren't going well and the Board isn't doing everything great, at the same time the people on the Board know a lot about what's going on in the organization because there have already been discussions and arguments that led up to that point, they've been there, and know the reasons for why things are happening. But there's no trust anymore and the Board as a group has gotten dysfunctional. And we have had several dysfunctional Boards.

    Then you have the third wave who are happy doing their thing within the OTW and don't necessarily want to be on the Board. But they've seen the problems, they've come up in the organization and have seen what is going on at the top. And even though they'd rather just be able to keep doing the work that they've been doing, they feel they have to step up and fix this situation we've found ourselves in. That's the kind of Board we have now, and that's a good place. The OTW got through those growing pains, which is important because there are a lot of organizations who don't make it through that period, through those transitions.

    In the beginning the contrast was, we had lots of disagreements but it was a foundation when everyone knew each other and respected each other's skills and knew of one another before ending up on the Board. That can be good but it also creates insularity. Those first few years were about just vrooom -- anything you wanted to try, you just tried. There wasn't anything that stopped you. There was nothing there yet so you just created something.

    So in the beginning you didn't have people already doing things a certain way that then would all have to be changed -- you can't do that to people and disrupt their work and processes in that way. Especially on the coding side, that's an enormously creative period in the beginning where you're just creating. And in general, many people like to build new things and do not like to maintain old things, technology-wise. So at the beginning it's much easier. We all got our hands dirty. None of us had ever worked on anything the scale of what the OTW is now and we were just figuring it all out. For some people it is stressful having to start something, but for others it also is to maintain and grow it.

    During your time with the OTW, what have you personally achieved that you feel the most proud of?

    The Archive of Our Own is there, just, it exists. On a meta level, when I first made the post about building an archive, I wasn't thinking of it as something I would do. I even said it was something we needed and if someone else would do it then I would help them. But then I saw that no one was volunteering, and I had a moment, I remember this moment, knowing that setting this project in motion would be an enormous time sink, and an emotional sink, and that it would have opportunity costs for the rest of my life. But I did it anyway.

    That original discussion generated a certain momentum, and we needed to build on it right away. There's one moment when you can take an idea to the table, and if you miss it, it's going to collapse, it's not going to be a thing at all. At the time I made that post I did it because I was mad and I believed it, I believed we had to do something. It's that whole cliche 'You have to be the change you want to see in the world.' And so I went to Rebecca and Francesca and said 'we're going to do it, but I can't do this without you.' And they said 'alright, we're in.' We'd had conversations before about the problems we wanted the OTW to address and this was the time to do something.

    What do you see as the role of the OTW now and do you think that's changed since it began? How might it change in the next 10 years?

    The #1 thing that I feel like the OTW has now that it didn't at the very beginning was the role of maintaining things, such as keeping the AO3 up and functioning. And now the Archive, and Fanlore too, but Fanlore is much easier to keep up. It's not easier to grow it, but just to keep it from falling down it's easier. Even the AO3 is hard to grow over the next 10 years just because you need to bring it up to a modern technical level. There should be discussions going on, and I expect there are, about version 2.0 of the Archive. But the AO3 should not look the same 10 years from now, and we need to start thinking about that plan [of how to get there] now rather than later.

    We took a responsibility on and I know that -- even during the darkest moments of the Board where I literally thought that the entire tech staff would quit and there would be no one to run AO3 -- that what kept people on [as volunteers] even though there wasn't any kind of good resolution to the problems, it was the inertia of not wanting to drop the ball. There can come a time where there can be too high a personal cost in continuing to work on our projects, but if it requires me [personally] to keep working on it then it's not going to survive anyway. I could not be the one responsible at that stage of my life to continue the maintenance and development of what we had started. I had a small child, my life was changing. And I actually had tried to have conversations with the Board, which was difficult, that if you don't trust the staff to know what to do and to have the room to make those things happen then the project isn't going to survive. There's just a few people keeping it up, and there still are only a few people doing that work, but now there are contractors involved to help move us forward and a process for making the Archive more maintainable.

    We all need to gracefully agree and also gracefully fail. And there can be a day when the lights don't come on. There could be a day when we can't afford to keep it running but we keep the stories available for download and provide the data so that someone else can take it on. It's the same thing that Open Doors is trying to save us from, that there are sites that just shut their doors, bye, all your work's gone. [The website] iMeem did that to [fans who were] vidding. Just one day, oh we're not going to host vids anymore. I feel very strongly that we have an obligation not to do that, that's the mission, that the #1 thing the OTW has to do. And I feel that it's happening [that we're keeping things going and maintaing them] so I'm happy with that.

    I also feel that legally we're in a better place than we were which is great, and I'm really proud of everything that the Legal Advocacy team has accomplished. It's been amazing to see their victories. I feel like the OTW has done a good job of preserving things too through Open Doors, that's something I'd like to see more focus on, preservation work. But the major thing to work on is also the next generation. Fandom is much larger now than it used to be so we don't need to get everybody, to have the OTW be something to every fan out there. But you do need to be in a place where the kids are at, there's not enough engagement with Wattpad for example. So I think we have people come to the Archive and want and expect things of it, and then go away without quite understanding what it's supposed to be.

    One thing I don't want the OTW to do is to try and become hip and trendy and reinvent ourselves in order to try and do that. We want to be the library, the boring place but the one that everyone knows about, and it's there if you need it.

    What has been the most fun thing to you about volunteering for the OTW?

    Building the AO3. I love coding, I think it's enormously fun, just building and coding something. I love that, that's the best.


    Now that one of our founders has said five things about what they've done, it’s your turn to add one more thing! How long have you known about the OTW? Do you use the different projects? How long have you been in fandom?

    You can also check out earlier Five Things posts by some of our other volunteers.

    The Organization for Transformative Works is the non-profit parent organization of multiple projects including Archive of Our Own, Fanlore, Open Doors, Transformative Works and Cultures, and OTW Legal Advocacy. We are a fan run, entirely donor-supported organization staffed by volunteers. Find out more about us on our website.

    Comment

    Post Header

    As you might have noticed if you're following our Release Notes, we've been focusing on humdrum back-end updates for quite a while now. Words like "test coverage" and "strong parameters" have featured prominently in every change log for almost a year, and we haven't been able to focus on more visible features and fixes. However, progress is being made, and thanks to your donations we have the financial means to work with contractors for a good part of these updates!

    Having worked with a few other contractors in the past, primarily on smaller fixes to our codebase, we now have a stellar team that's been by our side for much of our big Rails upgrade, and will hopefully stay on for a few more projects after that. \o/

    However, it's important to note that being able to afford contractors doesn't mean that all the work gets done right away. (Alas.) Our small team of volunteer coders and testers still has to thoroughly review and test all code submissions, while still living up to their pesky "real life" commitments. Bugs can still take days to solve, whether the person elbow-deep in code is being paid or not. And unforeseen problems affecting site stability and security still take precedence above all else, tying up volunteer time. (This is also the reason major code updates have been delayed for so long: there's always another fire to put out!)

    As a result, the slog through our outdated code will take a while longer, and progress will seem slow from the user side. We are currently on Rails 3.2 and our upgrade will take us to the latest version of Rails 5. (Anyone familiar with Rails knows that this is quite a bit of work.) And once we’re done with the Rails work, we need to upgrade Elasticsearch, which powers the Archive's search and filtering functionality. After that's all done, we'll take a little nap we can go back to more exciting and significantly more visible projects!

    We want to thank you for bearing with us through it all, and for the donations that make it possible to outsource some of the workload involved in updating the Archive code. We can't always reply to comments here, and we can't respond to every tweet (even if the reaction gif is really funny), but we see you, and we appreciate you. Thanks for your support over all these years! <3

    Comment

    Post Header

    Here at AO3, we've been looking into getting some paid coding help for a few years, to work on projects that are larger or more time-consuming than our volunteers are able to tackle in their spare time, and also just to help with the backlog of work and offer some extra assistance. We had a contractor take on a few small projects last year, but to outsource work on major projects, you need to be able to form longer relationships.

    Today we're excited to announce that thanks to user donations, we've been able to contract an experienced programmer for several months' worth of work! \o/ And she isn't just an experienced Ruby developer — she's a Ruby developer who has been working on the Archive since 2008! Since she's familiar with all the nooks and crannies of our infrastructure, it will be easy for her to jump right in on major projects, like the much-needed update to our searching and filtering code. After that, it's onwards to back-end improvements, code cleanup, and other long-awaited projects like site internationalization.

    Our new contractor is starting work next week, and we'll have a preview of her work on the searching and filtering code soon! Thanks to all of you for the donations that have been keeping the site running and are now enabling us to make it even better.

    Comment


    Pages Navigation