This question comes up a lot when it comes to Apache’s github policy. The short 
answer, unfortunately, is no.

In order to ensure the integrity of the IP, Apache needs to host the source 
code through its entire lifecycle. When a committer pushes to 
git-wip-us.apache.org, Apache is able to record who is doing the pushing. The 
commit(s) being pushed might be by a different person, but the committer is 
vouching for them (checking IP integrity is one of the core responsibilities of 
a committer).

Those records are available for inspection if the provenance of the code were 
ever questioned.

When someone creates a pull request against github.com/apache/foo, this serves 
as a record that the contributor intended to make the contribution under ASL.

I know it’s inconvenient to close PRs. (You’ve discovered the trick of adding a 
‘Close #NNN’ comment, I assume.) There’s actually quite a lot going on, in a 
legal sense, when a committer accepts code contribution to an Apache project, 
so I think it’s OK that there is a little extra overhead.

By the way, it’s up to each project whether they do CTR (commit-then-review) or 
RTC (review-then-commit), but in Calcite we allow committers to commit code 
that have authored themselves. (They generally ask for a review first if it is 
non-trivial, and they always make sure that the test suite passes first.) So in 
that case, no pull request is required. Quickstep should decide whether they 
require pull requests for every commit, and how code should be reviewed.

Julian



> On Jul 28, 2016, at 1:40 PM, Jignesh Patel <[email protected]> wrote:
> 
> Currently we use the git-wip-us.apache.org as the main repo for Quickstep. 
> This works, but has limitations compared to doing development on github. One 
> key limitation is closing PRs on github is far easier.
> 
> 
> 
> Question: Is it possible for us to use github instead of ASF git server to 
> host the main code base? I know we have a mirror on github, but is it 
> possible to also have the main repo on github?
> 
> 
> 
> Thanks!
> 
> Jignesh
> 

Reply via email to