+1 (binding) On Sat, Mar 10, 2018 at 2:03 PM, Beau Barker <[email protected]> wrote:
> +1 for Github. > > Also think that moving to Github issues would be a step in the right > direction. > > > > On 11 Mar 2018, at 05:56, Matthew Housley <[email protected]> > wrote: > > > > +1 (binding) > > > > For future reference, is this vote for anyone on the mailing list, or for > > those with some kind of status in the project? I find the documentation > > here a little ambiguous: > > https://httpd.apache.org/dev/guidelines.html#voting > > Apologies if this has been answered before. > > > > On Sat, Mar 10, 2018 at 8:29 AM Ash Berlin-Taylor < > > [email protected]> wrote: > > > >> Consider this my +1 (binding) vote for the below proposal. This vote > will > >> run for 7 days (until 2018-03-17 15:30+00) > >> > >> **Proposal**: We switch to using GitHub as our primary repo > >> > >> We would still use the Apache Jira for issue/release tracking etc. > >> > >> Benefits: > >> > >> The contributors will gain write access to > >> github.com/apache/incubator-airflow. This would mean we would be able > to: > >> > >> - merge directly on github.com > >> - close stale issues > >> - be able to re-run Travis jobs (I think/hope) > >> > >> Risks: > >> > >> Neither of these are likely to be a problem, but the possible downsides > >> are: > >> > >> - It is still possible to commit to the ASF repo, which if it happens > can > >> lead to "split brain" (i.e. different views of master) which will need > >> INFRA team support to fix. > >> > >> - Contributors will need to agree to Github terms of service. Given this > >> is how PRs are reviewed currently this isn't a problem for any current > >> contributors. Just worth mentioning. > >> > >> > >> If the vote passes we will need to: > >> > >> - Update the airflow-pr tool to work directly on github, not ASF repos > >> - Update any docs that point to ASF repos ( > >> http://incubator.apache.org/projects/airflow.html, > >> https://cwiki.apache.org/confluence/display/AIRFLOW/Committers%27+Guide > - > >> there might be more) > >> - Ensure all committers have access. There is an self-serve process for > >> this (see below) > >> - Open a ticket with the INFRA queue asking them to migrate the repos. > (An > >> example of ticket from another Apache project that did this recently > >> https://issues.apache.org/jira/browse/INFRA-15983 ) > >> > >> > >> Contributor set up steps: > >> > >> - Go to https://id.apache.org/ and ensure you have a github username > >> entered in your profile. This will send an invite to join the Apache > org on > >> Github: accept that. > >> - Go to https://gitbox.apache.org/setup/ and link the accounts > >> > >> These steps can be done now no matter the outcome of the vote -- we just > >> won't get write access to airflow unless we migrate. > >> > >> Ash >
