[sakai-core-team] Contrib tools in github

[Steve Swinsburg]

I should note that Jasig have all subprojects in the one organisation - 63
repos in all.

On Sun, Feb 15, 2015 at 1:28 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
wrote:

> I've done some research on submodules and almost everyone is suggesting
> not to use this approach due to the complexities it introduces. The
> alternative is git subtree, but even then it has its own complexities.
>
> So we don't get hungup here, I think the best way forward is just to make
> a repo in the main sakai organisation for each of the contrib projects,
> prefixed with contrib- and then we can decide what we want to do later -
> whether that is a separate sakai-contrib organisation and individual
> repositories in there, or some other approach.
>
> I'd like to migrate the evaluation tool across ASAP.
>
> On Fri, Feb 13, 2015 at 8:05 AM, Steve Swinsburg <
> steve.swinsburg at gmail.com> wrote:
>
>> If they are in a sakai-contrib repo inside the Sakai org, we can mitigate
>> this by a note at the top saying 'Some of these projects may contain
>> licenses that are incompatible with the main ECL 2 license. Check each
>> projects individual POM or README' or something similar.
>>
>>
>> On Fri, Feb 13, 2015 at 7:24 AM, Matthew Jones <matthew at longsight.com>
>> wrote:
>>
>>> Just for completeness, the third reason that projects are in contrib
>>> were because they used libraries which are incompatible with the Sakai ECL
>>> license.
>>>
>>> For these projects, we might not even want to have them under
>>> https://github.com/sakaiproject. I don't know of any specific that
>>> still exist in there, but I know there probably are and have been in the
>>> past.
>>>
>>> I'm pretty sure evaluation was not one of these cases, it was under case
>>> #2.
>>>
>>> On Thu, Feb 12, 2015 at 1:06 PM, 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
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150215/5dc29d59/attachment-0001.html