Hi !!
Development of RC is comming at a point where organization is a must if we want to do things well. I just want to propose some things that could improve developing and that could be discussed further on this list:
Patches, bugs and feature request should ALWAYS be submitted to the SourceForge tracker:
this will improve tracking what has been done, what left to be done and assign resources (developers) and priorities to each patch, bug or feature request. This will imply that someone has to assign priorities and developers to patches/bugs/features. Developers should go to the SourceForge tracker when they are free to do some programming, list unassigned pacthes/bugs/features and ask through this list or directly to the project admin to get the desired task assigned to him.
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.
Coordination is another problematic point. Most developing at RC needs PHP, JavaScript, DHTML, graphical design and not all of us are masters on all those areas together, so coordination between coders is a must
- 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?
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?
But all in all - good ideas, I would like to see more RC development, and perhaps cvs access and commit access for approved devs.
P
On Sat, 26 Nov 2005 09:54:27 +0100, David Saez Padros david@ols.es wrote:
Hi !!
Development of RC is comming at a point where organization is a must if we want to do things well. I just want to propose some things that could improve developing and that could be discussed further on this list:
Patches, bugs and feature request should ALWAYS be submitted to the SourceForge tracker:
this will improve tracking what has been done, what left to be done and assign resources (developers) and priorities to each patch, bug or feature request. This will imply that someone has to assign priorities and developers to patches/bugs/features. Developers should go to the SourceForge tracker when they are free to do some programming, list unassigned pacthes/bugs/features and ask through this list or directly to the project admin to get the desired task assigned to him.
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.
Coordination is another problematic point. Most developing at RC needs PHP, JavaScript, DHTML, graphical design and not all of us are masters on all those areas together, so coordination between coders is a must
-- Thanx & best regards ...
David Saez Padros http://www.ols.es On-Line Services 2000 S.L. e-mail david@ols.es Pintor Vayreda 1 telf +34 902 50 29 75 08184 Palau-Solita i Plegamans movil +34 670 35 27 53
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.
-
David Saez Padros -
phil