Talk: Suggest improvements for GNU Generation
(Created page with ' == Make Reports Weekly or Bi-Weekly == Currently, GNU Generation has bi-monthly reports. This creates an environment where participants feel as if they need to have done someth…') |
(→Make Reports Weekly or Bi-Weekly) |
||
| Line 7: | Line 7: | ||
This is the system a few groups I've worked with in the past have used, and it's proven very effective. | This is the system a few groups I've worked with in the past have used, and it's proven very effective. | ||
| + | |||
| + | -- | ||
| + | |||
| + | I couldn't agree more with you. I have felt discouraged at least one time when submitting a progress report because I haven't done anything "big" and I didn't think reporting "I filled some bugs on X, W and Y projects and did some patches for them." was worth it. The reports should be on a shorter timespan, and should be public, so members can see what others are doing and discover new projects, help with them, and get new ideas. | ||
| + | --[[User:Turl|Turl]] 00:21, 4 May 2010 (UTC) | ||
Revision as of 19:21, 3 May 2010
Make Reports Weekly or Bi-Weekly
Currently, GNU Generation has bi-monthly reports. This creates an environment where participants feel as if they need to have done something "worth two months" to report in and discourages people from coming in and getting rewarded with feedback.
Instead, GNU Generation should take a page from the Xtreme Programming book, and have progress reports several times a week. For best results, these should be on a mailing list, so that participants get feedback on what others are doing and can offer advice or assistance if necessary. With reports happening multiple times a week, new participants could immediately do something to signify themselves as "part of the community" or as "working on GNU Generation stuff," and all participants will have more reason to report in, because there won't be any expectation for them to have done something "big."
This is the system a few groups I've worked with in the past have used, and it's proven very effective.
--
I couldn't agree more with you. I have felt discouraged at least one time when submitting a progress report because I haven't done anything "big" and I didn't think reporting "I filled some bugs on X, W and Y projects and did some patches for them." was worth it. The reports should be on a shorter timespan, and should be public, so members can see what others are doing and discover new projects, help with them, and get new ideas. --Turl 00:21, 4 May 2010 (UTC)
