Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Our group consists principally of core team members (former lead maintainers of hapi's direct dependencies), and members of the original team that built hapi at Walmart. It is heartening to see so much support pouring out right now— many folks have made it clear that they are interested in spending time contributing to the framework. We want to enable that: this is completely in line with our plans and we look forward to making hapi more of a community effort, but more on that later.
Within this small group you will find a former hapi Community Lead and Chief Architect at npm; a member of the Node.js TSC and libuv maintainer; several engineers working on major projects at Joyent; the finger that famously pressed "the button" on Walmart's Black Friday hapi deployment; several who provide B2B services utilizing the framework; and the creator of hapi pal, an entire sub-ecosystem of hapi. We lived hapi's history, we are aware of the pain points and blind spots, we understand all that there is to love about the framework, and we know you. Perhaps more importantly, if you've been active in the community then you probably know us! Here we are:
This group of seven constitutes hapi's initial Technical Steering Committee (TSC). Yes that's right, we're going to have a TSC! That means that for the first time hapi is going to be taking a more distributed, community-driven approach to governance, in a similar vein to the Node.js organization. It is the TSC's job to provide technical direction, onboard collaborators, and facilitate consensus-seeking within the community. For practical reasons there is a smaller leadership team with exclusive rights to publishing new module versions: Colin, Nathan, and myself.
It's not all about making changes, though. To begin our focus will be to establish stability in maintenance and governance, making only minor adjustments along the way to achieve that goal. We'll be working closely with Eran leading up to the moment he steps away from hapi maintenance, and at that point we will release a new major version, more so to signal to the community this change in leadership than to make any significant API adjustments. Here are some things that we intend to keep, not necessarily an exhaustive list:
We want to keep what's making hapi what it is today but we also have visions for the future for what hapi could become. We're looking forward to all the cool stuff we'll be adding to the project and we're excited for you to help us with that.
And for now that is the "short" of it. Hopefully this gives you a much better sense of who is working to carry hapi forward and what to expect. We understand that there are likely lots of questions coming our way. It is still relatively early in this process and there are still many details to work out, but we will try to speak to those to the best of our ability at this time! Please bear in mind this is still open source, and while we will have some employer support in the near future, this is still a community effort with lots of personal time invested as well.
That is all for now! Expect to hear more in the coming weeks and months— we hope you'll be there with us.
Note: you can find more information about legacy commercial support here.