[Building Sakai] Moving YAFT and CLOG to github

[Adrian Fish]

If, like Anthony states, github can rewire the project nesting later, then
I'll go ahead and just create a couple of projects under my account. I'll
give those svn2git utils a try as well. I'd like to get the history in
rather than just leave it in SVN. I'll leave the SVN projects intact and
mark them as deprecated somehow.

Thanks for all the replies.

Cheers,
Adrian.


On 27 August 2013 16:38, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> I suggest we follow the jquery example on this.
> https://github.com/jquery
>
> Official (core) jquery projects go under the jquery account. All other
> plugins (of which there are at least hundreds) go whereever they like
> in github, bitbucket, google code, etc.
> -AZ
>
>
> On Tue, Aug 27, 2013 at 11:32 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
> >
> > Would this be a good time to get the sakaiproject permissions sorted on
> > GitHub so these projects can get cracking?
> >
> >
> > Perhaps.  Depends on whether or not we want to add contrib project repos
> > under https://github.com/sakaiproject or limit the account to code,
> docs,
> > etc. that we provide in our distributions.
> >
> > We could encourage contrib developers to locate their repos under
> > sakaiproject alongside our core repo(s).  One location is convenient but
> > contrib projects range from highly supported to one-off
> > experiments--locating them all under a single account might not make
> sense
> > given the variable levels of developer support provided such projects and
> > the implication that if a repo exists under sakaiproject we are obliged
> to
> > support it.
> >
> > We could mimic the svn core/contrib repo model and create a github
> > sakaiproject-contrib account in order to maintain a separation between
> > what's core and what's not.  Or we provide no "sakaiproject-contrib"
> branded
> > account for contrib developers and leave it them to set up their own
> > accounts and repos.  If a contrib project is later included in our
> > distribution then github provides a mechanism to transfer repos between
> > accounts.
> >
> > Stuff to think about.
> >
> > Anth
> >
> >
> > anthony whyte | its and mlibrary | university of michigan |
> > arwhyte at umich.edu | 517-980-0228
> >
> >
> > On Aug 27, 2013, at 10:23 AM, Steve Swinsburg wrote:
> >
> > Yes definitely perform a migration if that's where you want to be.
> Svn2git.
> > There is a guide on GitHub itself, as well.
> >
> > Would this be a good time to get the sakaiproject permissions sorted on
> > GitHub so these projects can get cracking?
> >
> > Cheers,
> > Steve
> >
> > Sent from my iPad
> >
> > On 28/08/2013, at 0:00, Mike Jennings <mike_jennings at unc.edu> wrote:
> >
> > Adrian,
> >
> >
> > I love the idea of moving things to Git....
> >
> >
> > I have used this guide in the past to convert svn repos to git and keep
> >
> > the reversion history
> >
> >
> > http://john.albin.net/git/convert-subversion-to-git
> >
> >
> > Mike
> >
> >
> > On 08/27/2013 09:32 AM, Adrian Fish wrote:
> >
> > I'm thinking of using github for YAFT and CLOG development from hereon,
> >
> > would anybody have any issues with that? I like the idea of encouraging
> >
> > pull requests from people; I think it may encourage more developers as
> >
> > they are more likely to get the commit kudos when their stuff gets
> pushed.
> >
> >
> > I have two concerns:
> >
> >
> > disaster backups
> >
> > svn logs being lost.
> >
> >
> > Cheers,
> >
> > Adrian.
> >
> >
> >
> > _______________________________________________
> >
> > sakai-dev mailing list
> >
> > sakai-dev at collab.sakaiproject.org
> >
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
> >
> > --
> >
> > =========================================
> >
> > Mike Jennings
> >
> > Teaching and Learning Developer
> >
> > T: 919.843.5013
> >
> > E: mike_jennings at unc.edu
> >
> > _______________________________________________
> >
> > sakai-dev mailing list
> >
> > sakai-dev at collab.sakaiproject.org
> >
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
> >
> >
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130827/e497941f/attachment.html