Changes between Version 29 and Version 30 of GitMigration

Timestamp:

Apr 22, 2019, 8:25:59 AM (5 years ago)

Author:

neteler

Comment:

+ section on Implementation of migration from OSGeo SVN and trac to GitHub

GitMigration

@@ -90 +90 @@
 
 
-* Sign in using OSGeo Userid
-* Autonomously create and manage teams
-* Autonomously create and manage repositories
-* Create private repositories (for software vulnerability testing, etc.)
-* Import tickets from Trac
-* Import tickets from Redmine
-* Comment tickets via email
-* Comment/close tickets via commit log
-* SVN->GIT sync - (Mirroring existing SVN repository) see:/ticket/1654
-* Integration with CI service (hosted eg. Travis-CI, !AppVeyor, !GitLab CI), self-hosted (e.g. !Buildbot, ?))
+ * Sign in using OSGeo Userid
+ * Autonomously create and manage teams
+ * Autonomously create and manage repositories
+ * Create private repositories (for software vulnerability testing, etc.)
+ * Import tickets from Trac
+ * Import tickets from Redmine
+ * Comment tickets via email
+ * Comment/close tickets via commit log
+ * SVN->GIT sync - (Mirroring existing SVN repository) see:/ticket/1654
+ * Integration with CI service (hosted eg. Travis-CI, !AppVeyor, !GitLab CI), self-hosted (e.g. !Buildbot, ?))
 
+Extra link:
+ * ~~ New !GitHub API for importing issues: https://gist.github.com/jonmagic/5282384165e0f86ef105 ~~ (we didn't know about it in time)
 
-== Next steps ==
+== Next steps Feb 2019 ==
 
 === User Survey ===
@@ -112 +114 @@
 20 Feb 2019:
  * Results available here: https://docs.google.com/forms/d/1BoTFyZRNebqVX98A3rh5GpUS2gKFfmuim78gbradDjc/viewanalytics
-
 
 === git test migration ===
@@ -124 +125 @@
 === PSC vote ===
 
- * Motion: 18 Apr 2019
+ * RFC 6
+   * https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub
+ * Motion on RFC 6: 18 Apr 2019
    * https://lists.osgeo.org/pipermail/grass-psc/2019-April/002026.html
- * Result: tbd
+ * Result: motion carried 22 Apr 2019
+   * 
 
-=== Transfer to OSGeo organization within !GitHub ===
+== Implementation of migration from OSGeo SVN and trac to !GitHub ==
 
-In case of positive voting:
+=== Transfer to repo to OSGeo organization within !GitHub ===
+
+One option is to update the existing draft migration (https://github.com/grass-svn2git/) uner the existing OSGeo organization on !GitHub:
  * https://help.github.com/en/articles/transferring-a-repository
-=== RFC 6: Migration from SVN to !GitHub ===
 
-  * https://trac.osgeo.org/grass/wiki/RFC/6_MigrationGitHub (draft)
-== Extra technical links ==
+=== Migration of trac issues ===
+  * ...
 
-  * ~~ New !GitHub API for importing issues: https://gist.github.com/jonmagic/5282384165e0f86ef105 ~~ (we didn't know about it in time)
+===  New labels in the GitHub issue tracker ===
+  * c.f. also current QGIS cleanup
+
+=== Migration of trac wiki ===
+  * ...
+
+=== Setup of Gitlab mirror ===
+
   * Import your project from !GitHub to !GitLab: https://docs.gitlab.com/ee/user/project/import/github.html
+  * how to mirror !GitHub issues?
 
-== Future plans not being part of this RFC ==
+== Future plans not being part of initial migration ==
 
-  * Usage of github backporting application, https://github.com/apps/backporting (already used by GDAL, PROJ, QGIS, ...)
-  * DOI support through zenodo by connecting repos on !GitHub with Zenodo: https://guides.github.com/activities/citable-code/
+  * Usage of github backporting application
+    * https://github.com/apps/backporting (already used by GDAL, PROJ, QGIS, ...)
+  * DOI support through zenodo by connecting repos on !GitHub with Zenodo:
+    * https://guides.github.com/activities/citable-code/
   * Release of GRASS GIS 8.0.0 (or earlier) from !GitHub