As a contributor I have no github permissions to do even the simplest project management task - I can't neither add a label, provide information about priority/severity of an issue nor add issues to projects etc. Given the current github permission difference between committer and contributors and our stated goal to grow the size and participation of the community, I disagree that github provides sufficient project management features and capabilities.
While our current Jira setup has a lot of opportunity for improvements, it does allow contributors to participate in some level of project management. E.g. with recently added capability to use story points we can measure velocity and make estimations of project completions. As we are discussing alternatives, I would encourage to consider the desire of contributors to support the project in more than just code contributions, i.e. requirements for both contributors and committers for a low overhead project management solution. Steffen On Sat, Jun 9, 2018 at 11:43 PM Sebastian <s...@apache.org> wrote: > > > > -1 as I afraid it may violate "Apache Way". Microsoft is going to buy > > GitHub. What happens to Apache histories if one day he decided to drop > > GitHub data including Apache projects histories?! or decided to change > > usage license or payment?! and etc! > > > > However, I found it seems was legally OK in 2016 [1] BUT I think we must > > ask again also "general@incubator and/or community@apache and/or board > > rather than at legal-discuss" [1]. (at least informs them about the > > state of the art). > > I don't think we need to worry about Microsoft buying Github at the > moment and this should also not affect this discussion. If Apache > becomes unhappy with github at some point in time, we can just move the > code (to which github does not have any claims) someplace else. > > -sebastian >
