On Tue, Feb 4, 2014 at 8:13 AM, Ignasi Barrera n...@apache.org wrote:
...Just wanted to clarify this, as I think this approach doesn't introduce
overhead to commiters/contributors and respects the ASF workflow...
Thanks for this, IIUC this is described at
Hi Bertrand,
Actually that link is deprecated. We point all contributors/commiters to
the following guides:
https://wiki.apache.org/jclouds/How%20to%20Contribute
https://wiki.apache.org/jclouds/Committers%20Guide
We have a re-branding of the site in progress, and all these obsolete links
are
Hi,
On Tue, Feb 4, 2014 at 9:35 AM, Ignasi Barrera ignasi.barr...@gmail.com wrote:
...We're working on it, our apologies for the confusion the old links may
cause!...
Ok - it would be good add those new links and deprecation warning at
the top of the page that I mentioned!
-Bertrand
Hi,
On Fri, Jan 31, 2014 at 6:47 PM, James Taylor jamestay...@apache.org wrote:
The Phoenix project has recently come into incubation from it's former life
as a Github project. I believe other projects have made this same
transition, so I'm looking to get some advice from them...
CouchDB has
Hi,
On 03/02/14 10:42, Bertrand Delacretaz wrote:
On Fri, Jan 31, 2014 at 6:47 PM, James Taylor jamestay...@apache.org wrote:
The Phoenix project has recently come into incubation from it's former life
as a Github project. I believe other projects have made this same
transition, so I'm looking
Hey Sergio
The Apache mirrors on Github are by request and run off from git.apache.org.
Anyone wanting to have a svn or git project mirrored needs to submit an
infra ticket and it can get setup.
As for the Github workflows that are starting to be used, I am not a
proponent of them. These
On the question of tooling, that brings us back to James' inquiry about
having infrastructure that can emulate the GitHub pull request workflow in
house:
Something like the Github model that combines a) the ability for managing
branches and visually reviewing patches and b) a means to gate
Just wanted to point out that in jclouds we only use GitHub for the code
reviews. We don't follow the entire pull request workflow and we actually
use the ASF repos as our primary source of code.
Contributors submit pull requests and code review happen in GitHub. Once
the patch is ready to be
The Phoenix project has recently come into incubation from it's former life
as a Github project. I believe other projects have made this same
transition, so I'm looking to get some advice from them. What's the best
development methodology folks have found for collaborative development when
your
The Phoenix project has recently come into incubation from it's former
life as a Github project. I believe other projects have made this same
transition, so I'm looking to get some advice from them.
Over at Apache jclouds we're running a similar setup, with our main repos in
ASF Git mirrored
10 matches
Mail list logo
