Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add project lead team #134

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat: add project lead team #134

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 38 additions & 0 deletions event-project-lead.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can I suggest naming it "events 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?


The Bootstrap Project Lead Team shall assume responsibility for the comprehensive organization and execution of the event, including the management of formal event assets and brands.

It's crucial to clarify that the Bootstrap Project Lead Team is a separate entity from the local event organizers that may or may not exist for a given event. However, in all cases, they must collaborate with the Project Lead Team on event organization matters.

The responsibilities of the Bootstrap Project Lead Team shall encompass:


- **Early planning** and strategizing for the event, including ensuring **event consistency** to maintain integrity, reputation, and impact.
- **Venue selection**, taking into account factors such as accessibility, cost, and capacity.
- **Budget planning**, fundraising, and **sponsorship acquisition** in collaboration with the NixOS Foundation.
- **Speaker outreach** and curation of a diverse and engaging lineup.
- **Community engagement** to foster participation and contributions.
- **Documentation** of the organizational process for future reference.
- **Establishment** of a clear timeline with milestones for all organizational tasks.

The provisional members of the Bootstrap Project Lead Team are as follows:

- @raitobezarius
- @hexchen
- @Janik
- @0x4A6F
- @JulienMalka (new member since the announce)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?


Additionally, oversight for the Bootstrap Project Lead Team will be provided by Ron Efroni, who represents the NixOS Foundation Board.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could say that a direct line should be open between the board and the team, so they can communicate together on events.


# Formation of the Final Team
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


To this end, community members interested in joining the Final Team are encouraged to express their interest and qualifications. The selection process shall prioritize diversity, expertise, and a demonstrated commitment to the Nix ecosystem.

Until such time as the Final Team is duly constituted, the Bootstrap Project Lead Team shall remain active to ensure continuity in event organization and facilitate a smooth transition of responsibilities.