Hi,
It's not a problem. This type of open source collaboration based on
quality of work can be quite a new concept. If you have a look at the
mailing list archives, you can find all the patches the Seb submitted
to the project before he was voted to be given commit access. I set
up a special development branch for his additions - the relaxation
data consistency testing code - into which his patches were applied.
This isn't an exclusive club, one just has to show competency and
quality of work before being granted the power to freely modify the
code base. The code is also peer reviewed as I carefully check all
changes committed, others may also do this, and any problems found can
be resolved or reverted. Also everything is out in public and
permanently archived, all emails about relax are sent to the mailing
lists (there are a few very rare exceptions).
Regards,
Edward
On Sat, Mar 22, 2008 at 9:57 PM, Ryan MB Hoffman
<ryan.hoffman@xxxxxxxxxxx> wrote:
dear Edward,
thanks for your quick reply. although i have experience with CVS and python,
i have no experience with open source development per se, and so i do indeed
need to learn more about the structure of the project.
i will sign up for the mailing lists, and read that material. i saw that
Sebastien Morin (a graduate student from a biochemical background, like
myself) was a member so i thought i'd join the Gna! group as well.
until then,
Ryan M.B. Hoffman
PhD Candidate (lab of Brian D. Sykes)
Department of Biochemistry,
University of Alberta.
On 21-Mar-08, at 2:36 PM, Edward d'Auvergne wrote:
Dear Ryan,
Thank you for your interest in the relax open source project. You
contributions would be most welcome. However the procedure for
becoming a developer with commit access to the source code repository
in an open source project is a bit more democratic. I would recommend
to first read chapter 3 of the relax manual, ' Open source
infrastructure', which came with the program or can be found at
http://download.gna.org/relax/manual/1.2/relax.pdf or
http://www.nmr-relax.com/manual/1.2/relax.html. Then chapter 9,
'relax development', describes in detail the steps required to become
a developer with commit access. These two chapters need to be read
thoroughly. You will need to sign up to the relax mailing lists and
first prove your abilities by submitting your changes as patches.
Only afterwards can we, the relax developers, vote to grant you commit
access. If you only wanted to use relax and not modify the source
code or documentation, then membership to the group relax is not
necessary.
Sincerely,
Edward
On Thu, Mar 20, 2008 at 9:33 PM, Ryan MB Hoffman <rmb.hoffman@xxxxxxxxx>
wrote:
Ryan MB Hoffman requested membership to the group relax
at Gna!
User Details:
-------------
Name: Ryan MB Hoffman
Login: rydog
Email: rmb.hoffman@xxxxxxxxx
Project Details:
----------------
Name: relax
Unix Name: relax
Main Page: https://gna.org/projects/relax
Message from user:
------------------
i signed up with Savane because i want to use and develop relax.
so include me, please!
thanks,
ry
Note:
-----
You receive this email because you are registered as an administrator of
this
project and the system has been configured to send emails to administrators
when new users register.
Please login and go to the page
https://gna.org/project/admin/useradmin.php?group=relax
and approve or discard this membership request.
-- the Gna! team
_______________________________________________
Message sent via/by Gna!
http://gna.org/
Re: Membership request for group relax