After chatting with folks, we decided that we need both a way to organize who is working on particular tasks and identify all the big pieces that need to get done in order to get us to a more usable product. To that end, I've created a public doc:
http://sites.google.com/a/chromium.org/dev/developers/mac-work-plan This gives us a place to mark what we're working on, and having things in buckets by estimated time is helpful for both people who want to contribute and devs just looking for a small task to fill the gaps in their week. We'd rather not just lump these high-level tasks into the buglist, though we will continue to keep our dogfood bugs there (and referenced as an on-going line-item in the doc). Feel free to email me with questions or find us on IRC. -- Mike Pinkerton Mac Weenie [email protected] --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
