[Project-managers] Move to github (please read!)

[Stefan Vigerske]

Hi,

for projects that are part of the COIN-OR Optimization Suite 
(https://github.com/coin-or/COIN-OR-OptimizationSuite/blob/master/Dependencies) 
we are currently migrating tickets and wiki from each project's Trac to 
the project's mirror on GitHub.
You might get some or many e-mails during this migration as GitHub sends 
out notifications for every created issue or comment.
After the migration, we will restrict creating or editing tickets or 
wiki pages on Trac to the managers of each project.
The mirroring of the source from svn to GitHub is still enabled for the 
moment, but will be turned off eventually.

For projects that are not part of the COIN-OR Optimization Suite, the 
mirroring of svn to GitHub will need to be setup first, then Trac issues 
and tickets will be migrated and finally mirroring will be turned off. 
If you haven't yet have looked at Ted's e-mail from October (below), 
then please do so now.

Project description files (projDesc.xml) will also make it into the 
GitHub repositories.
We hope to still write up some more documentation on how things will work.

Stefan

On 10/25/18 9:28 PM, Ted Ralphs wrote:
> Hi all,
> 
> This e-mail is long overdue and will be followed up by additional ones, as
> needed, providing more details. The TLDR is that we are planning, over the
> next weeks/months, to move all projects to Github. The TRAC sites will
> eventually be shut down after the moves are complete, while the subversion
> repositories will be left in place (but unsearchable by Google) for the
> time being. In addition, we'll also be migrating the mailing lists from the
> current Mailman set up to Google Groups. This was discussed in detail at
> the COIN-OR workshop at IMA last week. Slides that were presented are
> Lectures 2 and 3 available here:
> 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__coral.ie.lehigh.edu_-7Eted_teaching_coin-2Dor_&d=DwIBaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=BRcuJnQr5NAzU29t80hk2rsLc4vrlRySBDabuq0O1ZI&m=GN9KTNfPOTnhYLjzZkJPFrVevEudo6BXnHkTLxjCYf4&s=T8GICoc9PSEyu5EB2_wdjdsCwV2gNoZDd0X4EGtf92c&e=
> 
> Videos of the presentation are also available here:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ima.umn.edu_2018-2D2019_SW10.15-2D19.18-23schedule&d=DwIBaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=BRcuJnQr5NAzU29t80hk2rsLc4vrlRySBDabuq0O1ZI&m=GN9KTNfPOTnhYLjzZkJPFrVevEudo6BXnHkTLxjCYf4&s=zzMotIMCLjpO2dBvoJQEPPagpmgiVL_OKzjgo_prATY&e=
> 
> The most important implication of this move is that we will switch from
> using subversion to using git for repository management. This move should
> not be a big surprise and is the inevitable result of the way the world is
> moving. Git and Github have some major advantages over the way we have been
> doing project management up until now and all recently added projects are
> already managed with git.
> 
> I will offer some Webinars on how to move from subversion to git, as well
> as other assorted topics related to project management using Github if
> there is interest.
> 
> To make the move, the first step will be to mirror the existing subversion
> repositories to Github. This has already been done for the projects in the
> Optimization Suite (and a few others). See
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_coin-2Dor&d=DwIBaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=BRcuJnQr5NAzU29t80hk2rsLc4vrlRySBDabuq0O1ZI&m=GN9KTNfPOTnhYLjzZkJPFrVevEudo6BXnHkTLxjCYf4&s=YgGW-2nyCBXnVs3-UzQJhMKOmXhuIqXlb3I9KYmyAXw&e=
> 
> If your project has already been mirrored to Github, you can ignore the
> rest of this e-mail
> 
> For the remaining projects, I need to know three things:
> 
> 1. The e-mail address of any contributor to your project. Please provide
> this is the form of a list of subversion user id's and associated e-mail
> addresses. This is how the mirroring software will figure out who to
> attribute commits to in git (which uses e-mail addresses instead of user
> id's). If this information is unknown, provide as much information as you
> know.
> 
> 2. Some idea of how to map your subversion repo into git. If you use the
> standard setup of
> trunk/
> stable/
> releases/
> branches/
> tags/
> then 'trunk' will be mapped to the git 'master' branch; any subdirectories
> in 'stable' will be mapped to git branches with names of the form
> 'stable/x.y' (assuming that you are using the standard semantic versioning
> scheme); and any point releases in 'releases' will be mapped to git tags.
> Additionally, subversion branches and tags will be mapped to git branches
> and tags.
> 
> 3. What timeline you would be comfortable with for making the move. We can
> mirror things dynamically for some time (commits made to subversion will be
> automatically mirrored to Girthub) to give you time to acclimate.
> 
> That's it for now. Please let me know if you have any questions or concerns
> and also whether you would be interested in a Webinar to make the move
> smoother.
> 
> Thanks!
> 
> Ted
> 
> 
> _______________________________________________
> Project-managers mailing list
> Project-managers at list.coin-or.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__list.coin-2Dor.org_mailman_listinfo_project-2Dmanagers&d=DwICAg&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=BRcuJnQr5NAzU29t80hk2rsLc4vrlRySBDabuq0O1ZI&m=GN9KTNfPOTnhYLjzZkJPFrVevEudo6BXnHkTLxjCYf4&s=Eoode4uuZ5vxgOtEzc_0JuerEAkGf_Vak0BU6hRNMAw&e=
>