Difference between revisions of "git migration"

From Free Pascal wiki
(Page in which to discuss SVN to Git migration for FPC)
 
(Migrating from SVN to git)
Line 1: Line 1:
= Migrating from SVN to git =
+
This page is about migrating FPC from SVN to git
  
== Concerns/Questions ==
+
= Concerns/Questions =
=== What part of SVN to migrate ? ===
+
== What part of SVN to migrate ? ==
**  More is better.
+
*  More is better.  
**  In order to save on diskspace, find ways to tell user how to clone only a part.
+
  Jonas has a very complete git mirror of the SVN+CVS part.
=== Branching model ?  ===
+
  (care needs to be taken: there used to be a time when copyrighted code was checked in)
 +
*  In order to save on diskspace, find ways to tell user how to clone only a part.
 +
== Branching model ?  ==
 
Various models exist:
 
Various models exist:
 
   [https://barro.github.io/2016/02/a-succesful-git-branching-model-considered-harmful/ Something like the current one]
 
   [https://barro.github.io/2016/02/a-succesful-git-branching-model-considered-harmful/ Something like the current one]
 
   [http://nvie.com/posts/a-successful-git-branching-model/ or a different one?]
 
   [http://nvie.com/posts/a-successful-git-branching-model/ or a different one?]
=== User management ? ===
+
== User management ? ==
 
Git has no concept of users. To manage permissions on a server, a separate program is needed.
 
Git has no concept of users. To manage permissions on a server, a separate program is needed.
==== gitorious ====
+
=== gitorious ===
 
* Advantages
 
* Advantages
 
** uses git repo for administration
 
** uses git repo for administration
Line 19: Line 21:
 
** administration needs ssh key, only ssh possible.
 
** administration needs ssh key, only ssh possible.
 
** Web integration ?
 
** Web integration ?
==== gitea ====
+
=== gitea ===
 
* Advantages
 
* Advantages
 
** Web based
 
** Web based
Line 26: Line 28:
 
** Separate config
 
** Separate config
 
** Requires running binary all the time, on a separate port.
 
** Requires running binary all the time, on a separate port.
=== What about Lazarus ? ===
+
== What about Lazarus ? ==
== Work to do ==
+
= Work to do =
=== Migrate SVN repo. ===
+
== Migrate SVN repo. ==
=== Set up user management and permissions. ===
+
== Set up user management and permissions. ==
=== Set up and automate github mirror ===
+
== Set up and automate github mirror ==

Revision as of 15:23, 16 December 2017

This page is about migrating FPC from SVN to git

Concerns/Questions

What part of SVN to migrate ?

  • More is better.
  Jonas has a very complete git mirror of the SVN+CVS part.
  (care needs to be taken: there used to be a time when copyrighted code was checked in)
  • In order to save on diskspace, find ways to tell user how to clone only a part.

Branching model ?

Various models exist:

 Something like the current one
 or a different one?

User management ?

Git has no concept of users. To manage permissions on a server, a separate program is needed.

gitorious

  • Advantages
    • uses git repo for administration
    • No server binary
  • Disadvantages
    • No web interface
    • administration needs ssh key, only ssh possible.
    • Web integration ?

gitea

  • Advantages
    • Web based
    • Fine tuning possible
  • Disadvantages
    • Separate config
    • Requires running binary all the time, on a separate port.

What about Lazarus ?

Work to do

Migrate SVN repo.

Set up user management and permissions.

Set up and automate github mirror