Hi !!
- The dev list should be only for communication between developers,
no pacthes, no bugs, no feature request, no end user support. This will keep the list clean. Of course, new features could be discussed on this list once proposed through the SourceForge tracker.
This is always the tricky part, any dev- list tends to be more helpful support-wise than a support- or general- list. Plus patches need to be tested by devs before committed, yes?
once a patch is submited to the tracker it should be assigned to a developer which should apply and test the patch before submitting it, no need to post patches to the list.
Personally I think IRC is always the best way for devs to communicate, but I understand the want to not have the dev- list become a support- list. Why not create a support- list and see if it catches on?
yes, but this takes more time for developers. In my case i have a work and other projects i work in so i have very limited time, having to read all messages on a list, many of them being only end user support, takes a lot of time that could be better used in developing. Same for being on IRC for long time (also take in account time zone diffrences). When things are well organized time is spent is productive and development is of better quality.
But all in all - good ideas, I would like to see more RC development, and perhaps cvs access and commit access for approved devs.
yes, for this to work it's necessary that the project admin either has a lot of time to assing tasks or that there are more than one admin. Same for developers with cvs access.