Yup. The integration between github and Apache are suboptimal. Infra is aware of the issue and wants to work on it. I have no insights into their plans, other than that they are in constant talks with github employees to improve the integration. Infra has been busy upgrading the services but they are way behind in workâageing and failing hardware being the biggest hurdle.
The reason Apache needs its own server is one of ensuring that the code coming in is actually from someone who is allowed to do so. Apache has no knowledge who is actually behind a github account, so we can't just import the code directly. Also the canonical code needs to be on ASF controlled hardware to ensure nobody else has write access to it (and could rewrite history). So for now it sucks, but things will improve somewhere this year (not saying it is an Earth year :-) Martijn On Thu, Mar 12, 2015 at 9:54 AM, Thibault Kruse <tibokr...@googlemail.com> wrote: > Hi, > > I notice that the core devs have to ask PR submitters to close their > PRs on github: > https://github.com/apache/wicket/pull/101 > > I am curious: Why is that so? > > Looking here: > https://help.github.com/articles/permission-levels-for-an-organization-repository/ > > I assume the wicket core devs are only part of a "read access team", > not a "write access team" within the github apache organisation. But > why would Apache do it like that, given teams can be granted > permissions on a per-repository basis? > > > regards, > Thibault > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
