mainSavannah Administration - Support: sr #108463, How is write access to SVN/git...

 
 

sr #108463: How is write access to SVN/git controlled

Submitter:  Chris Allegretta <astyanax>
Submitted:  Fri 27 Dec 2013 08:57:22 PM UTC
   
 
Category:  Source code repositories - developer access Priority:  5 - Normal
Severity:  2 - Minor Status:  None
Privacy:  Public Assigned to:  None
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 31 Dec 2013 11:50:09 PM UTC, comment #2: 


> As far as I know (could be wrong) any project member may
> commit to the source code of any project
> for which they are a member.


That is correct.  For any source (or the webpages) repository that is enabled.

Karl Berry <karl>
Site Administrator
Sat 28 Dec 2013 01:05:26 AM UTC, comment #1: 

I have been wondering about this myself.  Which may seem strange that I would reply in that case.  But since I don't think anyone else will reply for perhaps a long time I thought I might as well say what I knew regardless.

As far as I know (could be wrong) any project member may commit to the source code of any project for which they are a member.

The implementation uses a local PAM plugin that implements user accounts through mysql.  Using mysql the database is manipulated through the PHP code of the Savane code base that runs Savannah.  On the vcs.sv.gnu.org machine the /etc/nsswitch.conf file lists "passwd: compat mysql".  The "mysql" addition allows accounts to exist in the shared msyql database tables in addition to the machine local /etc/passwd location.  Projects name Unix account groups.  The effect is that users will have additional groups for every project that they are a member.  Looking at 'id' I see that you are in the group nano for example.

The directories of /srv/git and /srv/svn and others that store the vcs backends are group writable by the project group.  Therefore commits are allowed if they have write permission to the directory.  Version commits that write to the file system will be allowed if they are a member of the group.  If the user is not a member of the group then write access is denied.

I see nothing that differentiates between users who are a member of a group and users that are a member of the group and also have project admin status.  It appears to be purely group membership.

I report the above based upon reverse engineering what I see on the system.  I could easily be wrong.

Just FYI but for these types of discussion questions (instead of tasks to be tracked) I prefer using the mailing lists over the web forum.  On the mailing list I get to use a real editor instead of a browser form.  Your preferences may be quite different form mine however and I know many people prefer the web browser forms.  The -email is unavailable- mailing list (also known as savannah-hackers@gnu.org) would be a perfect place for the discussion.  https://lists.gnu.org/mailman/listinfo/savannah-hackers

Bob Proulx <rwp>
Site Administrator
Fri 27 Dec 2013 08:57:22 PM UTC, original submission:  

Sorry I was not successful finding anything about this in the FAQ, apologies if I missed something:

Im curious what specifically controls write access to the SVN and/or git repos.  I'd assumed it was Admin status on a project, but I want to verify that before I further add project members and roles in Savannah.  Thanks in advance!

Chris Allegretta <astyanax>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by karl (Posted a comment)
  • -email is unavailable- added by rwp (Posted a comment)
  • -email is unavailable- added by astyanax (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-12-31 karl Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code