On 5/28/07, Yoav Shapira <[EMAIL PROTECTED]> wrote:
Agree, I wasn't going for lab-specific Board reports. I wasn't even asking for status files, though those are fine as well. Just a "hey, I just added [some cool feature] to [lab name] -- is anyone interested in playing with it?" email to this list would be great. Optional, but great for everyone I think.
At work, we find that keeping a "development journal" in standup meeting format makes it easier for people to follow along. (What I did yesterday, what I'm doing today, and what problems I'm having.) I also find it makes it easier for me to follow my own work :) For open source projects, I tend to do a closing-day journal rather than an opening day journal. Then, the format is "what I did today" and "what I'm doing next". If I get behind, I just review the commit logs and make a quick catch-up entry. Here's a journal that I've been keeping for a Google Code project I started in April. * http://code.google.com/p/yazaar/issues/detail?id=16 At work, we do the same sort of thing, but as a comments to a JIRA ticket. Depending on how many of us are working on a project, we run weekly or monthly tickets. Lab developers might consider doing the same sort of thing. The end game for a lab is to attract other developers. Of course, we can always review the commit logs to find out what's happening, but I find it's harder to get started that way. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
