Forums : FOSS Questions
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
When to accept new developers on an Sourceforge project?
Hi to everybody,
I am relatively new to the cooperative development intrinsics to the open source community and I was wandering how to organize the write accesses on the CVS codebase for the project I manage. Is it better to allow anyone who is potentially interested to commit his/her changes to the code, or it is better for the manager to review code contributions and allow access only if the code is good, coming from trusted contributors?
I think the second possibility is applicable only on small projects such as mine (OhLoh counts 12,7 k lines of Java code). I know the CVS system allows to track very precisely code commits, but is it easier to proceed this way?
In other words, how can you be sure a potential developer is worth giving the write access on the CVS database? Better check before or after?
Thanks in advance!
The book Producing Open Source Software
by Karl Fogel has an entire chapter dedicated to that question :)
A good read in any case, especially when you're new to the open source world.
Hi, Dhaun,
many thanks for the hint! I will read this book, it sounds very interesting.
Hi Dhaun, thanks again for the suggestion. I downloaded the book and read it entirely. I can confirm it is very interesting. An absolute must for every project manager.