[sakai-core-team] Merging from github to svn?

[Steve Swinsburg]

I think that if the github process is working, then we should think about
moving everything that people are likely going to need to use for a
production install so its not fragmented (maven plugin looks good btw).

I don't really see the point of keeping SVN around for main Sakai code now,
its probably going to take more time for people to get patches to their
install then the few hours it would take for them to retool to use Git.
Plus its a service we provide for free, I'm sure we can make a decision
about it.

That would mean moving msub, and potentially tags and branches.

SVN would then remain for contrib only, which is (likely) not dependent on
the main code for patches. Maybe even move contrib, but I'm ambivalent
about that.






On Mon, Jan 12, 2015 at 10:28 PM, Matthew Buckett <
matthew.buckett at it.ox.ac.uk> wrote:

> I wonder if its easier if we start to push more projects into github so
>> that we don't have the burden of jumping between the two?
>>
>
> What other project were you thinking of?
> At David's suggestion I've done a quick convert of the sakai-maven-plugin:
>
> https://github.com/sakaiproject/sakai-maven-plugin
>
> Any comments about moving that?
> Is it best to delete everything in SVN for the maven plugin and leave a
> pointer to the repository location in github?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20150113/9e0a2dfb/attachment.html