Internal Tools? What are these things and why should I care?

Published: 2012-07-22 17:57:51 -0400

Some of you might have noticed in Support tickets a link to something called "Trello" or might have noticed a new FAQ about "Internal Tools", but weren't sure what these things might be. Or you might've wondered if you're the only who's seen a bug or requested a new feature. Or you might just be curious about our code.

We'd like to introduce the three public tools that we've been using to track development information for the Archive. We've been using them for different lengths of time, but haven't really advertised them. In the spirit of transparency, we thought we'd present them to you! We're hoping these tools will make it easier for you to understand what's going on behind the scenes and what we're working on.

First up is our very organized friend, the Trello Feature Requests Board. He's a detail-oriented individual who loves hearing about where our users think the Archive should go and what features our coders should implement. He records all of the requests for new features or revisions of current features. Browsing his cards, you can see features and changes that have been proposed, ones that have are accepted for development and will be coded eventually, ones that are implemented, and even ones that aren't currently possible on the Archive. He even takes notes on coders' and users' thoughts on the various features. I should note that he might not have labeled some cards clearly, so it's always worth browsing around a little.

Next is the Google Code Issues Tracker. She is our best beta, keeping track of features that have been approved for development on Trello, as well as the bugs our coders, testers, and users have found (all 3200 and counting)! She's been working for us the longest, keeping a list of everything we've broken and everything we've fixed. She's got some categories you can search by, but you can also just search by keywords.

Finally, we have the otwarchive on Github. She's the one in charge of our actual code, where the Archive gets rewritten. She'll take notes if you've figured out how to fix something, and even let you copy out the whole Archive code to work with on your own server. She's also starting to collect notes about our development and design guidelines as the AD&T committee standardizes them for the version 1.0 release.

We have a FAQ with a few more questions and answers about Trello, Google Code and Github, as well as links to all three. You can access it here: Internal Tools FAQ. If you have any questions about any of these tools or about something on them, let us know at our Support form (which also will soon have links to these tools)!

- Sam J., AO3 Support