[sakai-core-team] Contrib tools in github

[Steve Swinsburg]

... and for the interim, migrate them up to the main sakai organisation
(each in their own repo) and they can be moved later.

On Mon, Feb 16, 2015 at 8:09 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
wrote:

> Oh, no I wasn't suggesting they all be in one repo, they are all separate
> repo's in the one organisation: https://github.com/jasig/
>
> IMO this is the least complex setup: have a sakai-contrib organisation,
> and have repos for each project in there.
>
>
> On Mon, Feb 16, 2015 at 9:13 AM, Earle Nietzel <enietzel at anisakai.com>
> wrote:
>
>> I would prefer each project having its own github project as I think that
>> makes it the easiest to manage. The all we need to do is come up with a
>> decent approach (maybe git submodules) for integrating them.
>>
>> The biggest issue that I can see with using one git repo for all of
>> contrib is its like to be more complicated to include only parts of
>> contrib...
>>
>> I am on the side of whichever is easier to work with and avoid anything
>> complex.
>>
>>
>>
>> On Thu, Feb 12, 2015 at 3:13 PM, Steve Swinsburg <
>> steve.swinsburg at gmail.com> wrote:
>>
>>> If we can do it easily enough in the main organisation then that sounds
>>> good. The submodules might work if we document it well.
>>>
>>> FWIW I created the authors file, and have migrated a bunch of my stuff
>>> up to github via svn2git:
>>> svn2git -v https://source.sakaiproject.org/contrib/some/project --trunk
>>> / --nobranches --notags --authors ~/path/to/authors.txt
>>>
>>> Then added the remote and pushed it. Pretty simple.
>>>
>>> So what do we think, do we want to migrate contrib stuff to a contrib
>>> repo in the main Sakai organisaion? (I do). Start with the main ones, trunk
>>> only, SVN can remain for a while with the older tags just like the main
>>> repo. I can migrate them up piecemeal as I've been doing with my own.
>>>
>>> Whats the process for the git submodules?
>>>
>>> cheers,
>>> Steve
>>>
>>>
>>>
>>> On Fri, Feb 13, 2015 at 5:06 AM, Matthew Buckett <
>>> matthew.buckett at it.ox.ac.uk> wrote:
>>>
>>>> On 8 February 2015 at 10:35, Steve Swinsburg <steve.swinsburg at gmail.com>
>>>> wrote:
>>>> >
>>>> > Just wondering if we have a process for getting a contrib tool into
>>>> github?
>>>> > Specifically Evaluations. I would like to contribute some work to it
>>>> and the
>>>> > SVN way is so clunky now we have decent tools.
>>>> >
>>>> > 1. Do we have a Sakai contrib repo? Do we plan to have one or is it
>>>> expected
>>>> > that contrib tools would remain in the wild until they get into core?
>>>>
>>>> I haven't seen a contrib repo, I would expect that each project would
>>>> get it's own git project rather than having one git repository for all
>>>> contrib stuff.
>>>>
>>>> I think in the past I think contrib was used for 2 main purposes:
>>>>
>>>> - projects local to school, (eg
>>>> https://source.sakaiproject.org/contrib/uct/) - in the github world
>>>> there's no reason why these cans just live in an institution's
>>>> organisation until they start getting used by multiple schools.
>>>> - shared projects that aren't part of sakai,
>>>> (https://source.sakaiproject.org/contrib/evaluation/) - these are the
>>>> projects that we want to allow people to find easily but aren't
>>>> actually part of Sakai.
>>>>
>>>> I can see that it might be worth having a contrib github organisation
>>>> might be useful to allow people to easily find projects related to
>>>> Sakai, however there's no reason we couldn't just create teams within
>>>> the main Sakai organisation and have the repos in there. If we created
>>>> a sakaicontrib organisation then we have to manage the admins across
>>>> multiple places now, so why not just add projects that are shared
>>>> between institutions to the main organisation?
>>>>
>>>> The scripts that I used for the main Sakai repository are here:
>>>> https://github.com/buckett/svn-git-scripts
>>>> However these are mainly for merging multiple repositories into one.
>>>>
>>>> > 2. Do we have a documented way to get tools from SVN to github? I
>>>> have done
>>>> > it before (years ago) but assume the process has changed a bit.
>>>>
>>>> In most cases if you grab the authors file:
>>>> https://github.com/buckett/svn-git-scripts/blob/master/authors-all.txt
>>>> then use it, however contrib has people that aren't in the main
>>>> codebase so it's nice if you can update it for the extras
>>>>
>>>> Get list of all authors:
>>>>
>>>> svn log https://source.sakaiproject.org/contrib/evaluation/ | tr ' '
>>>> '\n' | grep '. at .' | sort | uniq
>>>>
>>>> Check that these all exist in authors-all.txt, add people that don't.
>>>>
>>>> git svn clone -s -t  -A authors-all.txt --prefix=origin/
>>>> https://source.sakaiproject.org/contrib/evaluation/ evaluation
>>>>
>>>> this will probably fail, but you cd into the folder and just run:
>>>>
>>>> git svn fetch
>>>>
>>>> until it gets all the way.
>>>> Then you can add the github remote:
>>>>
>>>> git remote add github git at github.com:sakaiproject/evaluation
>>>>
>>>> And push:
>>>>
>>>> git push github
>>>>
>>>> This should keep all the tags and branches, although all feature
>>>> branches that never got merged can probably be dropped.
>>>>
>>>> > 3. What do we think about Evaluations and maybe a few of the other
>>>> popular
>>>> > tools being moved?
>>>>
>>>> I think it makes sense. Then people can pull them into their sakai
>>>> builds with git submodules (urrg), but it makes getting patches back
>>>> easier.
>>>>
>>>> --
>>>>   Matthew Buckett, VLE Developer, IT Services, University of Oxford
>>>>
>>>
>>>
>>> _______________________________________________
>>> sakai-core-team mailing list
>>> sakai-core-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>>
>>>
>>
>>
>> --
>> earle,
>> asahi net int.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150216/ab4f6be5/attachment-0001.html