feat: add project lead team #134
Conversation
As this is a team that owns assets which were in Foundation's hands in the past, it makes sense to attach a document in the Foundation repository for it. Signed-off-by: Ryan Lahfa <[email protected]> Signed-off-by: 0x4AF6 Signed-off-by: Janik Haag Signed-off-by: Julien Malka Signed-off-by: hexchen
| @@ -0,0 +1,38 @@ | |||
| In recognition of the paramount importance of formal events within the Nix ecosystem, associated with the NixOS Foundation, we present this proposal for the establishment of a structured organizational framework. This framework seeks to provide a cohesive structure for the planning and execution of all formal events, including but not limited to NixCon, thereby ensuring their continued success and sustained growth. | |||
There was a problem hiding this comment.
Can you do a pass and make it a lot more dry? The goal of these documents should be that the mechanisms become very apparent. If you want I can help with that.
|
|
||
| # Establishment of the "Bootstrap Project Lead Team" | ||
|
|
||
| The cornerstone of this proposal lies in the creation of a "Bootstrap Project Lead Team" in charge of every formal event within the Nix ecosystem. This team shall comprise dedicated individuals from the community, possessing a profound commitment to the Nix ethos and a proven track record in event management. |
There was a problem hiding this comment.
If you extend the scope from NixCon to all formal events, then we need a definition of what constitutes a formal event. Would Oceansprint, for example, fall under this definition?
| @@ -0,0 +1,38 @@ | |||
| In recognition of the paramount importance of formal events within the Nix ecosystem, associated with the NixOS Foundation, we present this proposal for the establishment of a structured organizational framework. This framework seeks to provide a cohesive structure for the planning and execution of all formal events, including but not limited to NixCon, thereby ensuring their continued success and sustained growth. | |||
|
|
|||
| # Establishment of the "Bootstrap Project Lead Team" | |||
There was a problem hiding this comment.
Can I suggest naming it "events team"?
| - @hexchen | ||
| - @Janik | ||
| - @0x4A6F | ||
| - @JulienMalka (new member since the announce) |
There was a problem hiding this comment.
What is the process to join and leave the team?
Is there any leader inside of the team, or what model are you using to make decisions?
| - @0x4A6F | ||
| - @JulienMalka (new member since the announce) | ||
|
|
||
| Additionally, oversight for the Bootstrap Project Lead Team will be provided by Ron Efroni, who represents the NixOS Foundation Board. |
There was a problem hiding this comment.
We could say that a direct line should be open between the board and the team, so they can communicate together on events.
|
|
||
| Additionally, oversight for the Bootstrap Project Lead Team will be provided by Ron Efroni, who represents the NixOS Foundation Board. | ||
|
|
||
| # Formation of the Final Team |
There was a problem hiding this comment.
Typically you would introduce these notions a bit earlier in the document. And then they get expanded upon lower. Think of it as a spiral, with high-level things first, and then expand.
|
|
||
| # Formation of the Final Team | ||
|
|
||
| In tandem with the activities of the Bootstrap Project Lead Team, efforts shall be directed towards the formation of the Final Team, which shall assume responsibility for the comprehensive organization and execution of the event. The Final Team shall be constituted through a transparent and inclusive process, guided by community input and merit-based selection criteria. |
There was a problem hiding this comment.
Doesn't the team composition mostly depend on who is available on the ground? Like at Darmstadt, we had the help of the local hackerspace people. I'm thinking of the reader, or somebody that wants to organize another NixCon, and what they would take out from reading this document.
|
This needs to be re-designed, scoped-down, or simply scrapped. The authorities are broad and the responsibilities have not been demonstrated. The proposal mentions:
After announcing NixCon NA and posting the call for participation, team formation, CFP reminders, sponsorship call, kickoff, schedule announcement - planning started on 2023 October 18. Planning was done in the open, inviting anyone interested to attend+contribute, notes available to all, meetings available to all. The public Matrix room (#nixcon-na:nixos.org) which was announced and has every single proposed Bootstrap Team member in it; but not a single one had any input for the planning whatsoever for the duration nor attended a single planning event. I also personally reached out to various members of the proposed team on at least 2023 Oct 10, Dec 27, Dec 30 in an attempt to coordinate, without any of the above tasks being done or volunteered to be done. Not a single one of the above responsibilities or duties was offered or done by the proposed team, in whole or in part, in spite of every request and opportunity to do so. While it is possible such a team could exist and perform these functions; going from a situation where the proposed team has not done them to being the exclusive authoritative team is very likely to be crippling for new local events and for the growth of the Nix community worldwide. The actual fact of the matter is that the proposed group IS representative of and appropriate to be authoritative specifically for NixCon EU. This is what seems to be de-facto happening and they are free to create a team selection process and phased handoff between their Bootstrap Team and the local organizers as they see fit. On the other hand, thrusting this team into the position to be responsible and authoritative for "every formal event" is unwise. |
Well every one of the proposed team was already involved in organizing one ore more NixCon's so I would argue the opposite.
I can only speak for myself here but you didn't reach out to me (didn't have time to discuss with the team yet).
well we are currently doing them for NixCon EU and started work on NixCon Asia
we don't want to be the team responsible for all community events, only the ones officially endorsed and represented by the NixOS foundation, to have a consistent high quality of events.
Well as stated above we are already working on NixCon Asia so this is not ture.
To be honest this is a fairly bad faith argument, and "thrusting" is not what would happen here. |
|
My rough gloss of this is "the local organizers will do all the work, while the project lead team will make all the important decisions". Is that an unfair reading? At the very least it seems like a possible failure mode. |
As this is a team that owns assets which were in Foundation's hands in the past, it makes sense to attach a document in the Foundation repository for it.
As per @zimbatm ask of a formal document, contains the
Sign-off-byof all the current bootstrap PL team.