|
|
Blitz Devel : |
From: Techentin, Robert W. (techentin.robert_at_[hidden])
Date: 2002-10-03 15:19:50
Schoenborn, Oliver [mailto:Oliver.Schoenborn_at_[hidden]] wrote:
>
> I think it's a good idea to move blitz to sourceforge.
I second that!
> The one thing I haven't had to deal with is the ok'ing of
> submissions. E.g., if I want to submit a patch, do I send a
> diff file to one of the developers, or do I create a branch
> and notify the developers, who will then take care of
> approving the merge, etc... I don't know what is the better
> way of doing this.
Every Sourceforge project has a limited number of developers with write
access into CVS. A subset of the developers are the project admins, who are
also responsible for forums, web pages and file releases and stuff like
that.
Everybody else gets read-only access to CVS. But anybody can submit a bug
report or a patch through the bug tracking system. Then it is up to one of
the developers to test the patch and integrate it into the CVS sources.
Most Sourceforge projects have a few developer/administrators. Some (like
Tcl and Python and SquirrelMail) have a few administrators and dozens of
developers with write access to CVS. It is pretty easy to add new
developers, so many projects welcome the additional help.
Bob
-- Bob Techentin techentin.robert_at_[hidden] Mayo Foundation (507) 538-5495 200 First St. SW FAX (507) 284-9171 Rochester MN, 55901 USA http://www.mayo.edu/sppdg/ _______________________________________________ Blitz-dev mailing list Blitz-dev_at_[hidden] http://www.oonumerics.org/mailman/listinfo.cgi/blitz-dev