|
TheSlate
What our developers are going to do next.
IntroductionThis page is sort of a shared to-do list for our developers. Each developer can have a list here of the next few Growl-related things they're going to do. These are not tickets. Items listed here are smaller than a whole bug report or feature request; an item might be part of fixing a bug or adding a feature. Just because you don't see “fix the crash on actuating the veeblefritzer” or “add a veeblefritzer to GrowlMail” doesn't mean we aren't working on it; those are forests, and these items are trees. These are also not the whole team's plans. These lists—plural—are what developers are individually going to do. The union of these lists is a subset of the plans of the team as a whole. And these lists are not complete. Each list is the selection of things that a developer is planning to do in the near term. Actions not coming up in the near term should not be listed here; the developer who plans to do them should consider filing a ticket or commenting on a relevant ticket instead. To report bugs or request features, we recommend that you contact us. Instructions (for developers)Add items below your name. If your name isn't listed (welcome, new Growl developer!), add a heading for your name. Items should be as small as possible. Whatever ticket you're working on, make a list of the steps needed to solve it, and put that list here. You should also include a reference/link to the ticket. A list in GCH wiki format looks like this:
Put a check mark (✓) after any item you've completed locally but not yet pushed. When you've finished something and pushed it, remove it from your slate completely, and then update any relevant tickets. SlatesPeter Hosey
Rudy Richter
Evan SchoenbergDaniel Siemer
|