GnomeGoals Rules!
A few weeks ago I had to repeat the same maintenance work over and over in gucharmap, vte, dasher, and devhelp. Things like the right way to install an icon, or various metadata files like MAINTAINERS, etc. So I was thinking about pointing things like that, the best practices of maintaining GNOME modules, in my weblog as something like a GNOME Maintainers' Tips series. So I started listing them in a file in ~/blog till I get to them later. Well, I don't have to anymore.
Vincent's
GNOME Goal series is just that, with a subtle difference: when he sets a goal, everybody hurries up to fix all modules he maintains or commits to (
Update: or better yet, others contribute patches to fix these.) Nice indeed. So I simply dumped my list and filed my tips at
GnomeGoals wiki page. I even wrote drafts for a couple of them. Help up and add your secret tips. Given that we only have about 20 more weeks to go before next code freeze (if not less), we may need to accelerate.
A not-so-irrelevant idea is
Gnome Recipes project. What both projects have in common is that they generate very good material for the GNOME ISV guide, and that's a good thing.
On a completely unrelated note, I'm enjoying the new Bugzilla My Bugs page even more and actually using the "Assigned to" field of bugs, assigning bugs that I want to look into shortly to myself, and find them right there in my bugs page.