hapi.js governance model

[hueniverse]

Draft proposal posted here: https://github.com/hapijs/hapi/blob/master/docs/Governance.md

Please use this issue to discuss, ask questions, or raise concerns. This is OUR framework and community and the rules we set will affect how this project moves forward.

[Raynos]

You might want to special case hapi as it is a much "bigger" module then any other modules in hapijs.

By bigger I mean api surface area. I might make sense to not have a BDFL for hapi itself.

I would reference @rvagg "lead maintainer" behavior on levelup ( Level/levelup#255 (comment) ) as a interesting example that might suit the governance of hapi itself.

Note that the BDFL and "lead maintainer" approach to all the smaller modules makes sense since their interface and api surface area is smaller in scope (for example the joi interface is kind of a subset of the hapi interface, hapi uses it as a small part of the server.route interface).

[hueniverse]

@Raynos while hapi is clearly the heart of the project, there is nothing fundamentally special about it. It can be easily forked and can be successful as a new framework. I want to keep things simple by setting up three levels of control: consensus, lead decision, community fork.

[briandela]

Looks great.

I'm not sure if it belongs in the Governance doc but I was wondering who one would contact in order to start discussions about including a new repo/project. For example, if person x wanted to submit a repo to the organization what would be the process to start that - the doc mentions that the Lead maintainers will decide to accept/reject new repos but not how to do that (perhaps instructions should live elsewhere)

[hueniverse]

@briandela the operating rules, including how issues are handled, how PR reviewed, and your example should all be clarified in additional document. We have a new discuss repo which would probably be a good start. If it gets busy, we can create another for governance discussions.

[hueniverse]

An so it is.

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.