[sakai-core-team] Subversion -> Github Migration

[Matthew Jones]

Yeah, it looks like we can both remove and add permissions.

So we'll just have to set each tool to read only and remove the specific
permissions allowing overrides within the tools (like for bundles and
help). Tried it on training as expected.

[/training/trunk]
* = r

So would be
[/chat/trunk]
* =r

[/assignment/trunk]
* = r

. . . etc

A much simpler acl file. Thanks!

On Wed, Dec 24, 2014 at 10:16 AM, Neal Caidin <neal.caidin at apereo.org>
wrote:

> Since you understand the structure better than I do, it might make sense
> for you to do it.
>
> (unless you think what I've done already would be cool.)
>
> I kind of did that third example you show.
>
>
> On Wed, Dec 24, 2014 at 10:13 AM, Matthew Jones <matthew at longsight.com>
> wrote:
>
>> I think it would be cool if we could change
>>
>>
>> [/chat]
>> @svn-admins = rw
>> @chat = rw
>> * = r
>>
>> to
>>
>> [/chat/trunk]
>> * = r
>>
>> or
>>
>> [/chat/trunk]
>> @svn-admins = r
>> @chat = r
>> * = r
>>
>> To remove permissions from the top level, but that's something I didn't
>> test. I know that every tool directory (msub excluded) only has branches
>> and tags though.
>>
>> On Wed, Dec 24, 2014 at 10:11 AM, Matthew Jones <matthew at longsight.com>
>> wrote:
>>
>>> The /chat/tags would have also had.
>>>
>>> @chat = rw
>>>
>>> Must have been a typo :) Really just making the top level read only to
>>> all, and moving the specifics down to only the tags/branches.
>>>
>>>
>>> On Wed, Dec 24, 2014 at 10:10 AM, Matthew Jones <matthew at longsight.com>
>>> wrote:
>>>
>>>> I was thinking of like it would involve changing. My estimate was based
>>>> on about 30 second for each change for each tool. It might work where you
>>>> could restrict based on the sub-directory but I don't know for sure rather
>>>> than have it restrictive to start with, but I don't know for sure. I know
>>>> the below will work and will be the same for every tool.
>>>>
>>>> Changing
>>>>
>>>> [/chat]
>>>> @svn-admins = rw
>>>> @chat = rw
>>>> * = r
>>>>
>>>> to
>>>>
>>>> [/chat]
>>>> * = r
>>>>
>>>> [/chat/branches]
>>>> @svn-admins = rw
>>>> @chat = rw
>>>> * = r
>>>>
>>>> [/chat/tags]
>>>> @svn-admins = rw
>>>> @chat = r
>>>> * = r
>>>>
>>>>
>>>> On Wed, Dec 24, 2014 at 10:02 AM, Neal Caidin <neal.caidin at apereo.org>
>>>> wrote:
>>>>
>>>>> >I think it will be all in the authz, just removing svn-admins from
>>>>> the top level directory and adding them to the each specific tools's
>>>>> branches/tags directory. Will be a little bit of work but doesn't seem like
>>>>> it should be more than 15 minutes, not something I'm worried about.
>>>>>
>>>>> What is this top level director that you speak of?
>>>>>
>>>>> I just made a local copy of authz and went through every directory
>>>>> that has "trunk" and set all the groups from rw to r. It took more than 15
>>>>> minutes.
>>>>>
>>>>> Would anyone like to review? I can send the text file. Then it should
>>>>> just be a matter of copy/paste and take a couple of minutes.
>>>>>
>>>>> Thanks,
>>>>> Neal
>>>>>
>>>>>
>>>>> On Wed, Dec 24, 2014 at 9:55 AM, Matthew Jones <matthew at longsight.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> On Wed, Dec 24, 2014 at 8:42 AM, Neal Caidin <neal.caidin at apereo.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I'm writing to Wush to see if there is an easy way to set trunk to
>>>>>>> read-only and keep all the msubs read/write, but I suspect not. I think it
>>>>>>> will have to be what you wrote, that I have to update all the trunk folders
>>>>>>> to read-only for all the groups in that folder.
>>>>>>>
>>>>>>
>>>>>> I think it will be all in the authz, just removing svn-admins from
>>>>>> the top level directory and adding them to the each specific tools's
>>>>>> branches/tags directory. Will be a little bit of work but doesn't seem like
>>>>>> it should be more than 15 minutes, not something I'm worried about.
>>>>>>
>>>>>> I'll make a copy of the Authz file so that our revert, should we need
>>>>>>> it, will be super quick.
>>>>>>>
>>>>>>> I would prefer to make the changes Sunday evening rather than Monday
>>>>>>> morning, if that is okay?
>>>>>>>
>>>>>>
>>>>>> I think that depends on the time Matthew plans to start it. If it's
>>>>>> morning GMT it should be the night before. If it's not till the afternoon
>>>>>> or later in the day Monday GMT then we can just wait to make the changes on
>>>>>> Monday.
>>>>>>
>>>>>> What time did you plan to start it, Matthew? I'd include specific
>>>>>> times in the email.It doesn't sound like you need anything else from us but
>>>>>> I'll be around for either Sunday night or most/all of the EST day Monday.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20141224/c96fc0d2/attachment-0001.html