[asterisk-dev] DAHDI migration to Git

Thu Dec 6 03:13:37 CST 2012

6 dec 2012 kl. 09:46 skrev Dan Jenkins <dan.jenkins at holidayextras.com>:

> Hi,
> 
> I'm not a contributor to dahdi but I am on this mailing list, and we've already had this conversation in part about Asterisk specifically moving to git, but I really don't understand why you wouldn't utilise github or even bitbucket (which is now integrated into atlassian's on-demand/hosted service - so I think you should have access to it) rather than having to run your own git servers. By using either of these tools (or the many more out there online) you could end up getting even more interaction within the dahdi project, if you still want a core backup then make git.asterisk.org your core backup, and get bitbucket or github to clone back to git.asterisk.org using a git hook.
> 
> Just my opinion, but isn't that part of the whole reason for moving to git? Yes, git can be much nicer to work with but git naturally allows more people to get involved in a project, due to these awesome tools,
>  

Digium is a commercial company and by far the largest sponsor of Asterisk and Dahdi. By the licensing agreement, they have commercial
rights to the source code. When dealing with the commercial side of Asterisk, there are probably agreements in place that relates
to code management, something that is quite common in larger commercial software deals. 

Reading the github.com terms of service, where they can shut down the service at any time, without any notice, I'm a bit concerned. They also
reserve the right to judge my content. I would have a problem with the terms in commercial projects. (I'm speculating here, since I'm not aware 
of any details of Digium's dealings with 3rd parties).

In addition, there are things that we as Asterisk developers have grown depending on that needs to be in place, like the automerge system that is awesome,
but not in place in many other projects. I personally don't know if that's a feature of GIT or and addon, but most people I've asked haven't given 
me any answers on how to replace that.

I think we as a project have to respect Digium's situation and follow their flow in this case. I'm grateful for the infrastructure provided by Digium,
and as a constant abuser of branching and automerging in their svn, I can't complain ;-)

While GITHUB may be great, I don't like a situation where one site, one company has all the infrastructure. Diversity is great.
The internet is a distributed model. 

/O

> Dan Jenkins
> 
> -- 
> Dan Jenkins - Senior Web Developer
> email: dan.jenkins at holidayextras.com
> twitter: dan_jenkins
> linkedin: jenkinsdaniel
> skype: d-jenkins
> blog: www.dan-jenkins.co.uk
> about.me: about.me/dan_jenkins
> 
> 
> 
> On 5 December 2012 16:52, Russ Meyerriecks <rmeyerriecks at digium.com> wrote:
> Great news! DAHDI is migrating to Git!
> 
> This is mainly to ease development burden as the DAHDI developers
> already use Git in our primary workflow. Also, the Asterisk project
> has expressed interest in making the same move and might be
> interested in our switch as a pilot. [1]
> 
> The idea here is to create a non-rewindable "golden" repo that
> developers may clone from. Patches may be built off of this repo as
> was done prior in svn.  More info will be provided on the wiki but
> here is a quick example:
> 
> Previously:
>   svn co http://svn.asterisk.org/svn/dahdi/linux/trunk dahdi-linux
>   cd dahdi-linux
>   <make edits to files>
>   svn diff > patch.patch
>   <upload patch to http://issues.asterisk.org>
> 
> Now:
>   git clone git://git.asterisk.org/dahdi/linux dahdi-linux
>   cd dahdi-linux
>   <make edits to files>
>   git commit -a
>   <write commit message>
>   git format-patch HEAD^
>   <upload patch to http://issues.asterisk.org>
> 
> I have created what I think to be a suitable "golden" dahdi-linux
> git repo here:
> http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=summary
> 
> Here are the highlights:
> 
> * It contains all commits from version 2.4.0 and up. DAHDI versions
> prior to 2.4.0 contain a subversion external (the oct612x library)
> which breaks compiles from git checkouts. We plan on creating a
> dahdi/history git repository that does a best effort job of
> publishing the entire history of DAHDI in a git repository.
> 
> * Development branches have been named 2.4.y, 2.5.y, 2.6.y to follow
> linux tree convention. Point releases and minior point releases are
> then tagged off of these.
> 
> * All svn "tags" are now git tags with proper reference off of their
> development branch. Tags beginning with "v" indicate a cut/tarballed
> release.
> 
> * Author attributes are handled properly where able. If you
> submitted a patch in the past that was committed by somebody else,
> you might now have the proper attribution. (This is a big bonus
> feature of git vs svn, in my mind)
> 
> * I've added a series of branched-* tags that are used to indicate,
> from the main branch, where a sub-branch joins. This is handy in
> situations when you're browsing the code and would like to know what
> patches are in what version.
> 
> If you have an interest in DAHDI, please give the repo a sanity
> check as feedback is welcome.
> 
> As this migration moves forward, I will be adding more info onto a
> page on wiki.asterisk.org. I will explain the git workflow and how
> to do everything you're currently doing in svn, in git.
> 
> [1] https://wiki.asterisk.org/wiki/display/AST/AstriDevCon+2012#AstriDevCon2012-Policies
> --
> Russ Meyerriecks
> Digium, Inc. | Linux Kernel Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> direct: +1 256-428-6025
> Check us out at: www.digium.com & www.asterisk.org
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20121206/a23393aa/attachment-0001.htm>