On Mon, Aug 20, 2018 at 11:33 AM, Josh Elser <els...@apache.org> wrote: > Thanks for writing this up, Stack. Very nice read. > > Snipping out some subjects to reply to directly: > > On 8/19/18 6:48 AM, Stack wrote: > >> GITHUB >> Can hbase adopt the github dev flow? Support PRs? >> Its a case of just starting the discussion on the dev list? >> Do we lose review/commentary information if we go github route? Brief >> overview of what is possible w/ the new gitbox repos follows ultimately >> answering that no, there should be no loss (github comments show as jira >> comments). >> Most have github but not apache accounts. PRs are easier. Could encourage >> more contribution, lower the barrier to contrib. > > > This is something the PMC should take to heart. If we are excluding > contributions because of how we choose accept them, we're limiting our own > growth. Do we have technical reasons (e.g. PreCommit) which we cannot accept > PR's or is it just because "we do patches because we do patches"? >
I don't want to bog down this thread, but there are a ton of unanswered questions for allowing github PRs. The biggest one for me is that JIRA is currently our best hope for an authoritative place for authorship information. If we're taking PRs from folks who have GitHub accounts but find ASF JIRA accounts too burdensome, what are we putting for the author in JIRA? Am I going to have to look in JIRA before a certain date and in Git after? Or in Git only if JIRA is set to some "HBase Contributor from GitHub" account?
