Re: How to try out github for the supercollider source (it's not the primary place yet)

On 05/29/2012 11:12 AM, Miguel Negrao wrote:
>
> A 29/05/2012, às 07:50, Dan Stowell escreveu:
>
>> 2012/5/29 Jakob Leben<jakob.leben@...>:
>>> On Mon, May 28, 2012 at 11:43 PM, Dan Stowell<danstowell+sc3@...>
>>> wrote:
>>>>
>>>>>> I propose that we continue to push to sourceforge till June 1st
>>>>>> manually or by a hook also push to github
>>>>
>>>> The discussion in this thread was split between "let's move now" and
>>>> "let's wait until june 1st". Those are no longer very different
>>>> options so how about we go with june 1st? I'll turn on the push
>>>> notifications (from github-->sc-dev)
>>>
>>>
>>> One issue that I see unresolved is: how to block pushing to the old SF
>>> repository? Delete all the devs from the project? Delete the project?
>>
>> We can set access to read-only. But I don't think we should force it
>> out of sync straight away. May as well leave it for a month or two,
>> push updates back to it (the mirror of what we've been doing with
>> github up til now)
>
> Yes, but it would be probably cleaner if only one person (or a script) does this. So maybe disable all the dev
access except for one person, and let that person do the pushing. Then if someone else tries to push by
mistake to sf they will get an error and they will know they should be pushing to github.

+1

If it's possible to push to both, confusion will be inevitable..

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/