My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
TheSlate  
What our developers are going to do next.
Updated Dec 1, 2010 by prhgr...@gmail.com

Introduction

This 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:

  • Foo
    • Bar
  • Baz

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.

Slates

Peter Hosey

  • Redo General tab (again)
    • Switch from start/stop button to On/Off switch
    • Kill off “Start Growl at login”; make it implied by the On/Off switch
    • Kill off “Hide all notifications” ✓
  • Improve GrowlMailUUIDPatcher
    • New UI ✓
    • Confirmation sheet(s)
    • Fix warning list auto-sizing ✓
    • Un-hard-code current-version detection (get it from a plist file or appcast)

Rudy Richter

  • merge gntp into default
  • burinate legacy udp networking
  • clean up gntp and get decryption working
  • properties and enumerators where it makes sense to use them and where it will result in: (cleaner code, less code)
  • remove the carbon api from the framework
  • implement a replacement for the screen picker that can be used to physically place notifications on a specific screen rather than the current incarnation with corner only positioning
  • clean up and polish GrowlMailUUIDPatcher so that we can release it to the GrowlMail testers
  • implement the close all hot key and the GrowlHotKeyCenter

Evan Schoenberg

Daniel Siemer

  • Growl away history rollup
    • Group notifications by application

Sign in to add a comment
Powered by Google Project Hosting