Fwd: Brooklyncentral GitHub Repository

[Andrew Kennedy <an...@cloudsoftcorp.com>]

Although Aled responded on the right list, here is the original message in
case anyone missed it, with the change that I suggest we cut over
repositories next week, once we have a consensus on committer Git workflow.

Andrew.
---------- Forwarded message ----------
From: Andrew Kennedy <an...@cloudsoftcorp.com>
Date: 28 May 2014 12:07
Subject: Brooklyncentral GitHub Repository

All,

We are down to the last couple of open pull requests on the existing
GitHub, so once they are all closed (next week, hopefully) I think we
should stop accepting any new PRs on the 'Brooklyn Central' account.

- https://github.com/brooklyncentral/brooklyn.git

Richard has been mirroring the GitHub 'brooklyncentral/brooklyn' repository
across to the ASF Git (at 'git-wip-us') so we will turn this off at the
same time, making the ASF Git the repository of record for Brooklyn.

- https://git-wip-us.apache.org/repos/asf/brooklyn.git
- git://git.apache.org/incubator-brooklyn.git

There is now a choice as to how we wish to continue. There are two
read-only mirrors of the ASF Git repo at GitHub. The official Apache one
mirrors the ASF Git:

- https://github.com/apache/incubator-brooklyn.git

It is also possible to have two way JIRA integration with pull requests
automatically, which I think we should request. See this Blog entry for
more details:

-
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

Finally, there is the Brooklyn organisation on GitHub, which also mirrors
the ASF Git read-only.

- https://github.com/brooklyn/brooklyn.git

It's not clear which of the GitHub repos we should be raising pull request
against, and it seems to vary between projects. The consensus seems to be
that they should be merged into the ASF repo, and if that is done properly
then I believe the 'asfgit' Bot will close the pull request automatically.
 As long as branches are named according to JIRA issues, it seems they can
be tracked.

Some further guidance on the use of these repositories would be
appreciated, as well as opinions on what integrations should be requested
with JIRA. I'm actually not sure whether the JIRA integration described
above can be done on repos owned by anyone other than the Apache GitHub
account, so this would be good to know? And we are also going to find out
from Dave if there is an 'official' Apache stance.

In general, we went our code review process to be public and transparent,
so making pull requests somewhere is essential., It would be good to have a
simple workflow for committers,  although it is always possible to pull the
changes onto the ASF Git repo once everyone is happy. Other contributors
will always have to attach the patch to a JIRA issue to cover contributions
legally, anyway.

Cheers,
Andrew.
-- 
-- andrew kennedy ? engineer : http://cloudsoftcorp.com/developers/ ;

Re: Brooklyncentral GitHub Repository

[Richard Downer <ri...@apache.org>]

On 29 May 2014 11:16, Andrew Kennedy <an...@cloudsoftcorp.com> wrote:
> Git workflows for
> committers (since that for a non-committer is always via JIRA)

I don't think this is true - the GitHub-using projects also allow
non-committers to make pull requests. The committer has the
responsibility to ask the contributor to submit an ICLA, if one is
required. This is part of the jclouds model, for example.

Richard.

Re: Brooklyncentral GitHub Repository

[Andrew Kennedy <an...@cloudsoftcorp.com>]

FYI,

While waiting for a response to the Usergrid workflow, I have been looking
around at other Apache projects to determine their Git workflows for
committers (since that for a non-committer is always via JIRA) which are
usually documented on their sites or wikis. One in particular stood out as
a nice example we could follow; Cordova.

- http://wiki.apache.org/cordova/GitWorkflow



Other similar project workflows using pull requests:

- https://libcloud.readthedocs.org/en/v0.14.0-beta3/development.html
-
https://github.com/apache/incubator-storm/blob/master/DEVELOPER.md#merge-a-pull-request-or-patch
- https://deltacloud.apache.org/send-pull-request.html

Off topic, I really like the 'readthedocs.org' site, we should look into
hosting Brooklyn documentation there eventually.

Andrew.

-- 
-- andrew kennedy ? engineer : http://cloudsoftcorp.com/developers/ ;


On 29 May 2014 09:27, Andrew Kennedy <an...@cloudsoftcorp.com>wrote:

> Although Aled responded on the right list, here is the original message in
> case anyone missed it, with the change that I suggest we cut over
> repositories next week, once we have a consensus on committer Git workflow.
>
> Andrew.
> ---------- Forwarded message ----------
> From: Andrew Kennedy <an...@cloudsoftcorp.com>
> Date: 28 May 2014 12:07
> Subject: Brooklyncentral GitHub Repository
>
> All,
>
> We are down to the last couple of open pull requests on the existing
> GitHub, so once they are all closed (next week, hopefully) I think we
> should stop accepting any new PRs on the 'Brooklyn Central' account.
>
> - https://github.com/brooklyncentral/brooklyn.git
>
> Richard has been mirroring the GitHub 'brooklyncentral/brooklyn'
> repository across to the ASF Git (at 'git-wip-us') so we will turn this off
> at the same time, making the ASF Git the repository of record for Brooklyn.
>
> - https://git-wip-us.apache.org/repos/asf/brooklyn.git
> - git://git.apache.org/incubator-brooklyn.git
>
> There is now a choice as to how we wish to continue. There are two
> read-only mirrors of the ASF Git repo at GitHub. The official Apache one
> mirrors the ASF Git:
>
> - https://github.com/apache/incubator-brooklyn.git
>
> It is also possible to have two way JIRA integration with pull requests
> automatically, which I think we should request. See this Blog entry for
> more details:
>
> -
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> Finally, there is the Brooklyn organisation on GitHub, which also mirrors
> the ASF Git read-only.
>
> - https://github.com/brooklyn/brooklyn.git
>
> It's not clear which of the GitHub repos we should be raising pull request
> against, and it seems to vary between projects. The consensus seems to be
> that they should be merged into the ASF repo, and if that is done properly
> then I believe the 'asfgit' Bot will close the pull request automatically.
>  As long as branches are named according to JIRA issues, it seems they can
> be tracked.
>
> Some further guidance on the use of these repositories would be
> appreciated, as well as opinions on what integrations should be requested
> with JIRA. I'm actually not sure whether the JIRA integration described
> above can be done on repos owned by anyone other than the Apache GitHub
> account, so this would be good to know? And we are also going to find out
> from Dave if there is an 'official' Apache stance.
>
> In general, we went our code review process to be public and transparent,
> so making pull requests somewhere is essential., It would be good to have a
> simple workflow for committers,  although it is always possible to pull the
> changes onto the ASF Git repo once everyone is happy. Other contributors
> will always have to attach the patch to a JIRA issue to cover contributions
> legally, anyway.
>
> Cheers,
> Andrew.
> --
> -- andrew kennedy ? engineer : http://cloudsoftcorp.com/developers/ ;
>
>