buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <pe...@realityforge.org>
Subject Re: Improved integration between Apache and GitHub
Date Mon, 17 Feb 2014 00:46:45 GMT
Hi,

I have submitted requests to the INFRA team as

https://issues.apache.org/jira/browse/INFRA-7326
https://issues.apache.org/jira/browse/INFRA-7327

So hopefully these will be actioned sometime soon and we can go
through and point all the documentation at this new location.


On Sat, Feb 15, 2014 at 10:47 AM, Tammo van Lessen <tvanlessen@gmail.com> wrote:
> I agree that this is twofold, however I think there is no reason to handle
> both parts differently. Moving to git brings us more developer convenience
> (speaking for me but I guess it applies to others here, too) while sticking
> to the ASF rules, which is absolutely what we want. Mirroring that
> repository to Github makes the project available to second open source
> ecosystem. I personal like the structured Apache way very much, but the
> kool kids are now used to a less controlled easy-going way of sharing
> source code, issues and pull requests. Until now the bridge between ASF and
> Github was pretty uni-directional, now it appears to have a back-channel,
> which I highly appreciate. So I think the community will benefit from
> "moving to git and embracing github" a lot as it makes the interaction with
> the project easier (i.e. accessible in broader sense).
>
> So I'm +1 for moving to git and +1 for setting up the github mirror with
> pull request support.
>
> Tammo
>
>
> On Fri, Feb 14, 2014 at 8:17 PM, Jim Jagielski <jim@jagunet.com> wrote:
>
>> My Email was specifically to address Antoine's post... one can
>> "move to git" and not use Github at all. So the question is
>> whether moving to git is enough or if moving to git AND
>> leveraging Github is what Antoine (and maybe others???)
>> are interested in, and voting +1 on.
>>
>> On Feb 14, 2014, at 1:46 PM, Alex Boisvert <alex.boisvert@gmail.com>
>> wrote:
>>
>> > Hi Jim,
>> >
>> > Not sure what you mean exactly.  Of course there's a difference between
>> git
>> > and GitHub... but we're talking specifically about GitHub integration.
>>  See
>> > the article linked on the original post:
>> >
>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>> >
>> > I'm +1 for the integration too.
>> >
>> > alex
>> >
>> >
>> >
>> > On Fri, Feb 14, 2014 at 6:34 AM, Jim Jagielski <jim@jagunet.com> wrote:
>> >
>> >> git != Gitub. ie: moving to git is not the same as
>> >> using Github.
>> >> On Feb 13, 2014, at 12:34 PM, Antoine Toulme <antoine@lunar-ocean.com>
>> >> wrote:
>> >>
>> >>> I would be delighted if we move to git and open ourselves to a wider
>> >>> audience of developers. You have my vote of course.
>> >>>
>> >>>
>> >>> On Wed, Feb 12, 2014 at 1:25 PM, Peter Donald <peter@realityforge.org
>> >>> wrote:
>> >>>
>> >>>> Hi,
>> >>>>
>> >>>> The infrastructure team just announced [1] that they now support
>> >>>> improved integration with GitHub. In a nutshell this means
>> >>>>
>> >>>> "
>> >>>> * Any Pull Request that gets opened, closed, reopened or commented
on
>> >>>> now gets recorded on the project's mailing list
>> >>>> * If a project has a JIRA instance, any PRs or comments on PRs that
>> >>>> include a JIRA ticket ID will trigger an update on that specific
>> >>>> ticket
>> >>>> * Replying to a GitHub comment on the dev@ mailing list will trigger
>> a
>> >>>> comment being placed on GitHub (yes, it works both ways!)
>> >>>> "
>> >>>>
>> >>>> If there is no objections I would like to see it turned on for Buildr.
>> >>>>
>> >>>> [1]
>> >>>>
>> >>
>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>> >>>>
>> >>>> --
>> >>>> Cheers,
>> >>>>
>> >>>> Peter Donald
>> >>>>
>> >>
>> >>
>>
>>
>
>
> --
> Tammo van Lessen - http://www.taval.de



-- 
Cheers,

Peter Donald

Mime
View raw message