[sakai2-tcc] Subversion ACL Cleanup [updated]

[Matthew Jones]

Though if you want to be specific to what it can commit to, it only needs
access to all /branches and all /tags, never releases to commits from/to
trunk


On Tue, Jun 4, 2013 at 7:51 AM, Matthew Jones <matthew at longsight.com> wrote:

> Right, cle-release-team is an svn user that Jenkins uses (99% me though)
> to run the maven release process (tag all the artifacts) during a release.
>
> The only reasons I did that was so I didn't have 500 commits personally
> attributed to myself every commit cycle, Jenkins had to have some users
> credentials saved in the .subversion files to do the post-commit hook and
> it looked institution neutral.
>
> So I'd leave that ID until we work out a new process that doesn't involve
> Jenkins.
>
>
> On Tue, Jun 4, 2013 at 6:19 AM, Maurer, Christopher Wayne <
> chmaurer at iupui.edu> wrote:
>
>> I think Matt uses the cle-release-team one when he releases stuff, so you
>> may want to keep that one.  But, confirming with him would be best.
>>
>> Chris
>>
>> On 6/3/13 10:55 PM, "Beth Kirschner" <bkirschn at umich.edu> wrote:
>>
>> >Regarding question #3 - I just ran into Mike Osterman - he is alive and
>> >well and sees no need for his membership in the msub-admins group (it was
>> >an idea that never got acted on), and he's all in favor of cleanup. So
>> >I'd like to move forward with removing that group as well.
>> >
>> >- Beth
>> >
>> >On Jun 3, 2013, at 6:11 PM, Beth Kirschner <bkirschn at umich.edu> wrote:
>> >
>> >> As an experiment during some idle hours today, I took stab at cleaning
>> >>up the ACL lists for Subversion, with the goal to make them easier to
>> >>maintain and understand. I haven't yet "released" the changes, but if
>> >>you're an svn-admin, you can ssh into source.sakaiproject.org and see
>> >>the changes in the svn-acl-policy.new file.
>> >>
>> >> I'd like to "release" these changes following discussion at Thursday's
>> >>TCC meeting at the conference, so if you're not at the conference and
>> >>have any questions or concerns, please let me know.
>> >>
>> >> Here's what I did:
>> >>
>> >> 1) Create one @sak-branches group -- authorization for all SAK branches
>> >>is now consolidated into this one group. This was the only real
>> >>authorization change.
>> >>
>> >> 2) Combine maint-team and svn-admins groups, into one svn-admins group,
>> >>since maint-team was only used as a sub-group of svn-admins. svn-admins
>> >>have access to everything. Removed
>> >>'cle-release-team at collab.sakaiproject.org' from svn-admins group, since
>> >>this isn't a valid svn user. This was a consolidation of groups and
>> >>there is no change in authorization.
>> >>
>> >> 3) I'd like to remove the msub-admins group, since it seems redundant.
>> >>This group has access to all msub repos, and the membership is a sub-set
>> >>of svn-admins, with the exception of ostermmg at whitman.edu (Mike
>> >>Osterman). Does anyone know if he is still active in the community? If
>> >>not, I'll remove the group, since svn-admins have access to everything,
>> >>including msub repos.
>> >>
>> >> 4) I'd like to remove the following obsolete definitions (I think they
>> >>pre-date msub). These directories do not exist in
>> >>https://source.sakaproject.org/svn/ - can anyone think of any reason to
>> >>_not_ remove them?
>> >>
>> >> ## DELETE (start) - directories no longer exist
>> >> [/asu]
>> >> @svn-admins = rw
>> >> joshua.ryan at asu.edu = rw
>> >> * = r
>> >>
>> >> [/bspace]
>> >> @svn-admins = rw
>> >> @bspace = rw
>> >> * = r
>> >>
>> >> [/bspace/spring2-work]
>> >> @svn-admins = rw
>> >> @bspace = rw
>> >> @bspace-spring2-work = rw
>> >> * = r
>> >>
>> >> [/bspace/portal/sakai_2-5-x]
>> >> @svn-admins = rw
>> >> @bspace = rw
>> >> @bspace-portal = rw
>> >> * = r
>> >>
>> >> [/ctools]
>> >> @svn-admins = rw
>> >> @ctools = rw
>> >> * = r
>> >>
>> >> [/unicon]
>> >> @svn-admins = rw
>> >> @unicon = rw
>> >> * = r
>> >>
>> >> [/uct]
>> >> @svn-admins = rw
>> >> @uct = rw
>> >> * = r
>> >> ## DELETE (end) - directories no longer exist
>> >>
>> >>
>> >> Thanks,
>> >> - Beth
>> >>
>> >>
>> >
>>
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130604/288c6fd4/attachment.html