Node.js Foundation is taking shape
Persistence has payed off in the latest Node.js development, with staff from io.js and the Linux Foundation working to bring the band back together. The spin-off framework might finally be coming home.
Mikeal Rogers, who has become the quasi-unofficial-mouthpiece of io.js, has put the call out in a recent blog post for help reconciling Node.js and io.js under the banner of a new Node.js Foundation.
New project life cycle
A strategy paper has been put together to include provisions “for more projects than just core”, seen as necessary due to the approx. 50 io.js Working Groups that need to be integrated into the new foundation. These Working Groups count for about 300 members, with the paper to define the structure these groups would operate under.
The foundation will regulate the budgets required to be distributed to different projects. Since these resources would be limited, it would be for purely economic reasons if new projects or groups couldn’t go ahead.
However, since one of the great strengths of io.js is precisely this freedom to break the work up, a balanced solution to the problem is still in progress:
In io.js we have no resources (money, legal, etc) and so we could be very liberal about spinning up new working groups and projects because it didn’t cost us anything. With a foundation there are resources afforded to each project and so it makes sense that the board would want more restrictions in place to protect those resources.
Comments are open here, while additional feedback from the community is welcome.
TSC Charter and Policy Design
Another document has been created to define the roles and responsibilities of the Technical Steering Committee (TSC), which will be the primary governance body of the combined platform. Rogers states for those that are familiar with io.js that this would replace the Technical Committee and include members of the previous TC as well as core Node.js committers.
The TSC Charter shall be approved by the Board of the Foundation. Changes to the document will also require board approval, which will cover certain rights such as technical decision-making autonomy. Rogers has highlighted the need for the charter to be as minimal as possible, in order to continue to iterate on TC processes. “If we overload this document with the specifics of that process it will become quite difficult”.
The TSC Policy draft is the document that will ratify the direction, values, and scope of what the TSC is doing, covering aspects like details of the release process, technical scope and business objectives. Legal issues are left out, cited as being handled by the foundation itself, rather than members of the TSC.
While this news may be a welcome progression for some, the io.js community still has many opponents of the new course. The whole complex reconciliation issue can be followed on GitHub.