Le 12 mars 2012 13:07, Jonathan Clarke <[email protected]> a écrit :
> On 12/03/12 10:55, Thomas Chemineau wrote:
>> Le 12 mars 2012 09:09, Clément OUDOT <[email protected]
>> <mailto:[email protected]>> a écrit :
>>
>>     Le 12 mars 2012 00:30, Jonathan Clarke <[email protected]
>>     <mailto:[email protected]>> a écrit :
>>     > Hi there,
>>     >
>>     > This is a message that may lead to some debate, but I think the
>>     question
>>     > still needs asking...
>>     >
>>     > LTB source repositories are currently hosted on ltb-project.org
>>     <http://ltb-project.org>, using
>>     > subversion. This causes some service administration load to our
>>     > currently small team, and is currently dysfunctional (no emails when
>>     > commits are made).
>>     >
>>     > GitHub offers an amazing service, to mention a few of the advantages:
>>     > - free hosted repos for open source projects
>>     > - the many advantages of using git over svn
>>     > - the GitHub "pull request" model, which makes it very easy for
>>     > contributors to propose patches [1], rather than having them in the
>>     > bugtracker, and discuss contributions [2].
>>     >
>>     > For all of these reasons, I feel it would be good to move our source
>>     > repo to GitHub. We can of course conserve the SVN history (there are
>>     > good migration tools around), and I would be willing to put in some
>>     > effort to do the migration.
>>     >
>>     > What are your thoughts?
>>
>>     Yes, I was thinking about this too. This will allow us to really split
>>     our subproject (SSP, OpenLDAP init script, etc.).
>>
>>     Are we agree to keep our redmine as the main issues manager?
>>
>>     Clément.
>>
>>
>> Hi all,
>>
>> I am totally agree with moving sources onto github. This is a powerfull
>> service, and could lead more people to be interested into the LTB project.
>>
>> I think it could be easier to keep redmine as the main issues tracker.
>> Because this server hosts website, packages, mailing lists, and others
>> things that would not be stored onto github. Also, be carefull, the
>> redmine is referenced by search engines (issues, annonces, etc.). If
>> Github becomes the main tracker, it could be hard to keep the
>> referencement, by building 301 redirections onto github pages for each
>> redmine's issue.
>>
>> +1 on SVN migration tools
>
> Hi Thomas,
>
> I missed your email, but thanks for your support :)
>
> You have a good point about Redmine and search engines - another reason
> not to change.
>
> Do you already know about migrating SVN repos to git? I understand that
> you can just use git-svn clone http://svn/repo/here/trunk, then git push
> to GitHub, to keep all history. Is it that simple?

I already done such migration for LemonLDAP::NG contributions, it is
really easy. The complex thing is to map SVN authors (we will need
your GitHub account ID) and the transformation of tags and branches
into git system.

Clément.
_______________________________________________
ltb-dev mailing list
[email protected]
http://lists.ltb-project.org/listinfo/ltb-dev

Reply via email to