- We should have usernames as close as possible to first initial+last name
Backwards compatibility: the older usernames should stay for consistency with the thousands of line of code through the year that are stored in the cvs repository.
Everyone with check-in permission should have an entry at the developers file. Otherwise, as the email notification does not show everyone, we sometimes cannot contact someone that made a suspicious change in the code.
Notification:
There are 152 people with check in permission, but a lot of these people not active on the code anymore. We could remove their writing permission and shrink the list to 30-40 people only.
There are people who used the code for some time, then they moved to another project and come back to the code after an extended period of time. Should these people be bothered by tons of commit messages? Graeme says this is not a problem, because in a worst case scenario he just deletes them. Andre tends to focus on the modules he works on. Most of the active people read the messages (no matter how many) and delete them. Axel mentioned that it would be good if people could choose which modules they want to receive messages about. Wolfgang described it as a bookkeeping nightmare.
Axel's suggestion
SVN notification
= SVN permission
= phone list
= bug tracker (trac)
A person in any of these "lists" should get notification. They lose their notification when logging out of the three lists.
Discussion: Putting the Pencil code in SourceForge can turn the notification process relatively painless. Should we do it now or leave it for the pencil code meeting 2009? Another option is Google Code. They even have a space for blogs, so this blog could be moved there as well.
No comments:
Post a Comment