![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
Archive code update
I need to remember to post these right before or after AD&T meetings so I don't lose track of them!
We just deployed revision 1383 of our code: the ability to backdate chapters and the changes to the filters are probably the most obvious differences. Previously reported problems with filtering should all be fixed *knocks on wood*, and I'm psyched that we've got the fandoms page loading a lot faster.
I did the deploying myself this time, with lots of help and supervision by Systems. The Systems Committee only has a handful of volunteers, and they're responsible for the main OTW site, Fanlore, the archive, the journal, and everything else OTW-related, so they're starting to train people from other committees to do a few things so that the workload can hopefully be spread out a bit more. We had a few more last minute bobbles and bugs than usual, so that was exciting. And then we discovered a tag wrangling bug the next morning, so we'll have to see what we can do about getting the fix for that deployed once it's tested.
Once that's done, we'll hopefully be able to push ahead with the big projects we need to get done for open beta!
What needs to be done and/or is currently being worked on:
1) A redesign and beefing up of our invitations system. This is at the coding stage and is what I'll be working on next.
2) Improvements to tags and tag wrangling code based on feedback from users and tag wranglers.
3) More advanced search options and a more detailed browsing infrastructure. Lots of design work going on there.
4) A better backend for admins to be able to handle abuse complaints and general site issues. (Because I am 12, I giggle whenever anyone refers to this as "admin abuse" or "admin/abuse".)
5) A framework for admins to post various site announcements that can be read on the site and also get sent to users' inboxes.
6) A redesign of bookmarks - we've spent a lot of time talking about that lately, and things are moving along. Bookmarks were always meant to have more features and be more usable than they are now, they just got stuck in park for a while as other things took precedence.
7) Improvements to the translation code and interface. I'm not sure exactly what I'll be able to do when with this, but hopefully once I'm back in write-lots-of-code mode, I'll be able to work on a few different things at once.
8) Brainstorming about what we'd ultimately like the front page of the site to look like.
We're also still plugging away at the owning-the-servers project (colocation). There turned out to be some issues with our first-choice option, but I think we're moving closer to committing again now.
Time-frame-wise, I'd like to get the invitations code done in the next week or so and then tag wrangling stuff done by August 1st. Then maybe translations and caching in the first two weeks of August and then hand it all off to the testers. And also work in an update to Rails 2.3, since it doesn't seem like that will involve any/many code changes, and it'll give us some handy tools to refactor some of our least-pleasant forms. (My goal with that and the tag wrangling changes is to wind up with as much *less* code as I can manage.)
We'll see if that's an optimistic or pessimistic schedule. *g*
We just deployed revision 1383 of our code: the ability to backdate chapters and the changes to the filters are probably the most obvious differences. Previously reported problems with filtering should all be fixed *knocks on wood*, and I'm psyched that we've got the fandoms page loading a lot faster.
I did the deploying myself this time, with lots of help and supervision by Systems. The Systems Committee only has a handful of volunteers, and they're responsible for the main OTW site, Fanlore, the archive, the journal, and everything else OTW-related, so they're starting to train people from other committees to do a few things so that the workload can hopefully be spread out a bit more. We had a few more last minute bobbles and bugs than usual, so that was exciting. And then we discovered a tag wrangling bug the next morning, so we'll have to see what we can do about getting the fix for that deployed once it's tested.
Once that's done, we'll hopefully be able to push ahead with the big projects we need to get done for open beta!
What needs to be done and/or is currently being worked on:
1) A redesign and beefing up of our invitations system. This is at the coding stage and is what I'll be working on next.
2) Improvements to tags and tag wrangling code based on feedback from users and tag wranglers.
3) More advanced search options and a more detailed browsing infrastructure. Lots of design work going on there.
4) A better backend for admins to be able to handle abuse complaints and general site issues. (Because I am 12, I giggle whenever anyone refers to this as "admin abuse" or "admin/abuse".)
5) A framework for admins to post various site announcements that can be read on the site and also get sent to users' inboxes.
6) A redesign of bookmarks - we've spent a lot of time talking about that lately, and things are moving along. Bookmarks were always meant to have more features and be more usable than they are now, they just got stuck in park for a while as other things took precedence.
7) Improvements to the translation code and interface. I'm not sure exactly what I'll be able to do when with this, but hopefully once I'm back in write-lots-of-code mode, I'll be able to work on a few different things at once.
8) Brainstorming about what we'd ultimately like the front page of the site to look like.
We're also still plugging away at the owning-the-servers project (colocation). There turned out to be some issues with our first-choice option, but I think we're moving closer to committing again now.
Time-frame-wise, I'd like to get the invitations code done in the next week or so and then tag wrangling stuff done by August 1st. Then maybe translations and caching in the first two weeks of August and then hand it all off to the testers. And also work in an update to Rails 2.3, since it doesn't seem like that will involve any/many code changes, and it'll give us some handy tools to refactor some of our least-pleasant forms. (My goal with that and the tag wrangling changes is to wind up with as much *less* code as I can manage.)
We'll see if that's an optimistic or pessimistic schedule. *g*