-1 The only reason why -1 is I don't see a point in enabling issues for flink-web. We already track them in Jira and I think adding another channel for it will make tracking issues only harder.
With issues disabled for flink-web I vote +1. On 22/05/18 09:32, Chesnay Schepler wrote: > Hello, > > since no concerns have been raised in the discussion about enabling > GitBox [1] I'm opening this vote to make things official. > > Please vote on enabling GitBox integration for the flink and flink-web > repositories as follows: > > [ ] +1, Approve GitBox > [ ] -1, Do not approve GitBox (please provide specific comments) > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > If accepted I will file a ticket with INFRA to enable GitBox with the > following settings: > > flink: > > * no wiki > * no issues > * no projects > * no merge commit button (rebase/squash merge button still enabled) > * protected branches [2]: master, release-1.[0-5] (the latter we will > have to update with each release) > > flink-web > > * no wiki > * issues enabled > * no projects > * no merge commit button (rebase/squash merge button still enabled) > * protected branch: asf-site > * default branch: asf-site (while we're at it...) > > [1] > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html > [2] https://help.github.com/articles/about-protected-branches/ >
