[asterisk-dev] Git

[Dan Jenkins]

Sounds good!

The first thought for me is the fact that Digium wouldn't have to maintain
it's own git infrastructure, but if this is something Digium wants to do
then fine.

Yes, it's going to be a massive task, to even move the smaller projects
over to git. I agree with Paul in the other thread, Github seems ideal for
digium's open source projects; however I'd have it the other way around to
what you stated above, with the core backup being git.asterisk.org and the
active repo being Github. Like other people have said, there's tonnes of
other hosted git solutions out there, Atlassian have their own that's being
merged into On Demand called BitBucket which works well with Confluence etc
etc. I only said about using github as it's really the home of open
projects with communities.

I mean, I put my private repos on bitbucket but all of my public open repos
(like nodejs modules) are on github, as that seems to be the place that
allows the best community.

It would be great to be able to embrace pull requests, it opens up the
doors to much more community involvement in my eyes, I completely
understand there's a lot of legal issues around this but seems like it
could only benefit the end products.

It's great that Digium are looking at it,

Dan

-- 
Dan Jenkins - Senior Web Developer
email: dan.jenkins at holidayextras.com
twitter: dan_jenkins <http://twitter.com/dan_jenkins>
linkedin: jenkinsdaniel <http://www.linkedin.com/in/jenkinsdaniel>
skype: d-jenkins
blog: www.dan-jenkins.co.uk
about.me: about.me/dan_jenkins



On 19 November 2012 16:55, David M. Lee <dlee at digium.com> wrote:

> On Nov 19, 2012, at 10:02 AM, Daniel Pocock wrote:
>
> On 19/11/12 16:51, Dan Jenkins wrote:
>
> Hi David,
>
>
> Can I ask why git.asterisk.org will be the home?
>
>
> Why wouldn't you use github for your open source projects, where you want
>
> people to be able to submit pull requests and be part of the community? I
>
> don't want to hijack this thread with talk about git, but as you brought up
>
> talk of git.asterisk.org maybe we need to move it out of this thread, if
>
> it's up for discussion?
>
>
> Since I would really love to see the transition to Git happen sooner
> rather than later, I'll see your hijack and raise you a new thread!
>
> When we move to Git, we'll probably setup a mirror on
> https://github.com/asterisk-org, since everyone loves the GitHub.
>
> But hosting the repositories ourselves makes sense since we already have
> the infrastructure. Besides, most of the other stuff that GitHub provides
> we already have with Jira and Confluence.
>
> We don't really want to be subject to the whims of software fashion. Sure,
> GitHub is the new hotness. But what about in 5 or 10 years when there's an
> even newer hotness out there? Code hosting provides may come and go, but
> asterisk.org is forever!
>
> As far as accepting pull requests, though, we still need to ensure that
> contributors have a signed Contributor License Agreement[2] on file. Some
> projects do some interesting things so they can accept pull requests and
> cover their bases from a legal perspective[3]. We'll have to figure out
> what we want to do for Asterisk, and I'm sure lawyers will be involved. Fun.
>
> Given the distributed nature of git, it's quite possible you could do
> both, or just have the whole thing on github (or one of the various
> equivalents, like gitorious), and then set up a cron job to pull
> everything to your private server every hour
>
> For the conversion process, if it is any help, feel free to borrow the
> script I used for reSIProcate (see my earlier email for the link)
>
>
> Thanks! The conversion process will be monstrous, given Asterisk's long
> history. Several people have done some work along those lines already (and
> I see Tzafrir has posted a link to his git mirror of Asterisk).
>
> In addition to converting the repo, there will be a ton of work updating
> tools, documentation, policies, etc. There's a lot of stuff that uses the
> current Subversion infrastructure that needs to be updated. Which tells me
> that step 1 in moving to Git is for someone to actually figure out all the
> other stuff that will need to change.
>
>  [1]: http://www.atlassian.com/software/stash/overview
>  [2]: https://issues.asterisk.org/jira/secure/DigiumLicense.jspa
>  [3]: https://github.com/lift/framework/blob/master/contributors.md
>
> --
> David M. Lee
> Digium, Inc. | Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20121119/0a6469bb/attachment.htm>