AD&T this year
Aug. 25th, 2011 07:24 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
jennystSo, I started my year in AD&T with lots of high idealism about how I was going to post regularly about what happened. As you can see, it didn't work out quite like that. But I've got a few months left, and it's important to keep trying.
I missed a couple of meetings during the summer due to holidays, but I think now is a good time to shine a spotlight on what actually happens, because it's easy to take for granted the stuff I already know.
So, AD&T is the Accessibility, Design & Technology committee for the OTW, which means we manage the teams that do the design, coding and testing for the AO3. Like most other OTW committees, we have a two-hour committee meeting in Campfire once a fortnight. We're larger than most committees - historically about 10-15 members, compared to an average of 5 for most committees.
In theory, after every meeting, as well as posting the minutes on the internal wiki (which is visible to all volunteers), we email a summary to all the coders, testers and designers, and post a summary as an AO3 news post. In practice, writing good summaries appropriate for each audience is a fair amount of work, so it sometimes slips to a monthly news post.
So actually, right now, I'm going to go and help with the official post, rather than spending more time on this one.
I missed a couple of meetings during the summer due to holidays, but I think now is a good time to shine a spotlight on what actually happens, because it's easy to take for granted the stuff I already know.
So, AD&T is the Accessibility, Design & Technology committee for the OTW, which means we manage the teams that do the design, coding and testing for the AO3. Like most other OTW committees, we have a two-hour committee meeting in Campfire once a fortnight. We're larger than most committees - historically about 10-15 members, compared to an average of 5 for most committees.
In theory, after every meeting, as well as posting the minutes on the internal wiki (which is visible to all volunteers), we email a summary to all the coders, testers and designers, and post a summary as an AO3 news post. In practice, writing good summaries appropriate for each audience is a fair amount of work, so it sometimes slips to a monthly news post.
So actually, right now, I'm going to go and help with the official post, rather than spending more time on this one.
