Source Code Project Organization
I thought here, we could discuss how the improvement features will be managed. For example, One person each contributes a patch, and one person compiles it together.
Or something like that........
Or something like that........
Hi,
While this approach has worked for some rather large projects, I don't consider it to be a good approach here as it would likely lead to code forks ("Well, that stupid maintainer still hasn't merged in my patch, so now I'll start my own version so that people can use my great features" or similar). As such, a code repository (CVS as offered on savannah.nongnu.org, berlios.de, sourceforge.net) to allow several developers to work on the code base at once sounds like the most promising approach to me.
This doesn't completely solve the problem, of course, since the question of who write access should be given to can't be answered straightforwardly, but it would make a major difference.
-- Christoph
While this approach has worked for some rather large projects, I don't consider it to be a good approach here as it would likely lead to code forks ("Well, that stupid maintainer still hasn't merged in my patch, so now I'll start my own version so that people can use my great features" or similar). As such, a code repository (CVS as offered on savannah.nongnu.org, berlios.de, sourceforge.net) to allow several developers to work on the code base at once sounds like the most promising approach to me.
This doesn't completely solve the problem, of course, since the question of who write access should be given to can't be answered straightforwardly, but it would make a major difference.
-- Christoph
I think Sourceforge CVS is the way to go. Write access may not be a problem, however. All the person has to do is e-mail the patch to a person who does have write access. I don't believe that this would cause any problems, but I don't know how trustworthy people are these days...
