Changes between Version 7 and Version 8 of rfc71_github_migration

Timestamp:

Apr 6, 2018, 12:59:22 AM (5 years ago)

Author:

Jukka Rahkonen

Comment:

Wiki text formatting GitHub -> GitHub

rfc71_github_migration

@@ -9 +9 @@
 
 It is proposed that the GDAL source tree and ticket database moves from
-the OSGeo hosted Subversion repository/Trac database to GitHub.
+the OSGeo hosted Subversion repository/Trac database to !GitHub.
 Full source code history will be preserved. To make the migration simpler,
-existing tickets will remain in OSGeo Trac and will not be migrated to GitHub.
-New tickets will have to be opened in GitHub.
+existing tickets will remain in OSGeo Trac and will not be migrated to !GitHub.
+New tickets will have to be opened in !GitHub.
 
 == Motivations ==
@@ -23 +23 @@
      (or even those with SVN access) to submit their contributions, in particular
      because of the coupling with the continuous integratations services of Travis-CI
-     and AppVeyor that enable maintainers to check that the contribution doesn't
+     and !AppVeyor that enable maintainers to check that the contribution doesn't
      introduce known regressions + the friendly way of commenting a pull request.
-     However the manual porting of GitHub pull requests to Trac is a bit painful
+     However the manual porting of !GitHub pull requests to Trac is a bit painful
      for GDAL maintainers.
-  3. GitHub has become the de-facto hosting platform for a lot of open-source
+  3. !GitHub has become the de-facto hosting platform for a lot of open-source
      projects.
 
 == Details of the migration ==
 
- 0. The existing GitHub git repository will be pushed to
+ 0. The existing !GitHub git repository will be pushed to
     https://github.com/OSGeo/gdal_svn_mirror_backup (eventually removed once we are
     confident further steps have not messed things up)
- 1. As GitHub also uses the syntax "#1234" to link commit messages to its issues
-    that was also used in Trac, currently when following links in GitHub that point to a Trac
-    ticket, one ends up to a non-existing or unrelated GitHub issue/pull request.
-    So the commit messages of the current GitHub mirror will be rewritten by
+ 1. As !GitHub also uses the syntax "#1234" to link commit messages to its issues
+    that was also used in Trac, currently when following links in !GitHub that point to a Trac
+    ticket, one ends up to a non-existing or unrelated !GitHub issue/pull request.
+    So the commit messages of the current !GitHub mirror will be rewritten by
     a "git filter-branch --msg-filter 'python rewrite.py' -- --all" command to
     replace "#1234" with "https://trac.osgeo.org/gdal/ticket/1234"
@@ -49 +49 @@
     git repository.
  5. The cron job on the OSGeo server that refreshes the website from sources
-    will be modified to pull from GitHub rather than SVN.
+    will be modified to pull from !GitHub rather than SVN.
  6. Ticket creation permissions will be removed in Trac. Modification or closing of
     existing open tickets will still be possible. From that point, if closing a
     Trac ticket, one will have manually to reference the github commit.
- 7. The settings of the GDAL GitHub repository will be changed allow tickets to
+ 7. The settings of the GDAL !GitHub repository will be changed allow tickets to
     be filed. Labels and Milestones will be populated with relevant content
 
@@ -59 +59 @@
 other GDAL developers/contributors would be welcome:
 
- * Most visible Trac wiki documentation will have to be revised to point to GitHub
+ * Most visible Trac wiki documentation will have to be revised to point to !GitHub
  * HOWTO-RELEASE will have to be revised.
  * Existing SVN committers still interested in the project will have to request
-   commit access to the GitHub repo.
+   commit access to the !GitHub repo.
  * Some support from OSGeo SAC will be needed to turn the GDAL SVN repository to
    read-only (a complementary option would be to rename it to gdal_historical so that
@@ -72 +72 @@
 == Exit strategy ==
 
-GitHub is a closed platform. In case it would close or would start askin to pay
+!GitHub is a closed platform. In case it would close or would start askin to pay
 unreasonable fees, some backup strategy of the tickets would be needed. The
 solutions might be:
 * https://github.com/josegonzalez/python-github-backup 
-* GitLab has an import module from GitHub.
+* !GitLab has an import module from !GitHub.
 Although some experimentation has been done with those, this RFC does *not* cover
 setting up those solutions as a regular backup system.
@@ -82 +82 @@
 == Not covered by this RFC ==
 
-* Migration of Trac wiki content to GitHub wiki is not in the scope of this RFC. Can be done later
+* Migration of Trac wiki content to !GitHub wiki is not in the scope of this RFC. Can be done later
 
 == Previous related discussions ==