[sakai2-tcc] Github: OAE transfers "sakaiproject" account to Sakai and the CLE

[Steve Swinsburg]

Is there a reason we dont just have an Apereo organisation and have the all
projects underneath that? Sakai CLE is an Apereo project after all.

cheers,
Steve


On Wed, Jun 12, 2013 at 4:04 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Following the announcement that the OAE project was dropping the "Sakai"
> brand in favor of "Apereo" (i.e., Apereo OAE) I asked my friends on the OAE
> team to create a new Github OAE account, transfer their repos to said
> account, and relinquish ownership of the "sakaiproject" account to CLE
> committers.
>
> Separating the two projects repos should help reduce brand confusion as
> well allow the CLE community to inherit a known Github account already
> branded "Sakai" both in name (sakaiproject) and avatar (Sakaiger) should we
> decide at some future date to switch from SVN to Git and utilize Github
> [1].
>
> The OAE team readily agreed to the proposal and the transfer of repos to
> the new "oaeproject" account has been completed--Github makes this process
> an easy one. [2]
>
> Cheers,
>
> Anthony
>
> [1] https://github.com/sakaiproject
> [2] https://help.github.com/articles/how-to-transfer-a-repository
>
>
> Begin forwarded message:
>
> *From: *Nicolaas Matthijs <nicolaas.matthijs at caret.cam.ac.uk>
> *Date: *June 11, 2013 12:27:25 PM EDT
> *To: *oae-dev List <oae-dev at collab.sakaiproject.org>,
> sakai-dev at collab.sakaiproject.org
> *Subject: **[oae-dev] Github repositories move*
>
> Hi everyone,
>
> At the recent Apereo Conference, some of the Sakai CLE TCC members
> indicated that they would like to start using the `sakaiproject` GitHub
> organization account [1] for CLE-related projects (documentation, etc.). As
> the OAE project is rebranding as Apereo OAE, it makes sense for us to free
> up the `sakaiproject` account for CLE-related repositories.
>
> Therefore, we have gone ahead and created an `oaeproject` GitHub
> organization [2] and have moved the following repositories into this
> organization:
>
>
>    - Hilary (back-end)
>    - 3akai-ux (front-end)
>    - puppet-hilary (puppet scripts)
>    - oae-widgetlibrary
>    - ep_oae (Etherpad plugin)
>    - SAMLParser
>    - OAE-model-loader
>    - OAE-Micro-Site
>    - grunt-ver
>    - puppet-nfs
>    - oae-nightly-stats
>    - node-oae-tsung
>
>
> Rather than forking these repositories into `oaeproject`, we have used the
> GitHub move functionality. This means that all of the issues and PRs have
> been moved over and any requests to the old `sakaiproject` repositories
> will redirect to the new `oaeproject` repositories. In theory, this
> shouldn't break anything for people that are using or have forked the
> `sakaiproject` repositories, but we do want to encourage people to update
> any references they might have to the old repositories.
>
> We currently have outstanding pull requests for this move in Hilary,
> 3akai-ux and puppet-hilary. The Hilary branch of the OAE Model Loader has
> also been merged into master. Once these are merged and start to find their
> way into our automated deployment scripts, it's possible that we might see
> some temporary hick-ups which we'll try to resolve as soon as possible.
>
> [1] https://github.com/sakaiproject
> [2] https://github.com/oaeproject
>
> Kind regards,
> Nicolaas
> _______________________________________________
> oae-dev mailing list
> oae-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130612/1b25cc33/attachment-0001.html