In reply to @joepie91:pixie.town
nat-418: as I mentioned above, the project is not structureless to begin with, we already have governance structures, that is not the problem

In reply to @joepie91:pixie.town
nat-418: as I mentioned above, the project is not structureless to begin with, we already have governance structures, that is not the problem

The board is not responsible for technical leadership, decisions, or direction.

this is structurelessness

In reply to @zimbatm:numtide.com

I think people have very different views of the board. Personally I don't see them as our community leaders at all and I absolutely don't want them to be.

That's very true. Our role is to be the interface between the community and legal/commercial. Not to lead the community. The intention was for the community to self-manage, with minimal intervention from the board to unblock where needed.

There is a big mismatch of expectations there, that started happening when we had to weigh on the sponsorship policy.

Just finished reading everything here, Matrix isn't friendly to scrolling.

I definitely hear the different issues raised and apologies for not being able to respond more timely from my end.

Jotting down a few of the issues mentioned that I've caught reading through (feel free to add/correct me)

1. Different wants/expectations around the boards role in the project - Choose and make it very explicit, then set up the structure around it to empower the community. Assuring teams/leads that no one is going to pop out of nowhere and hinder/block/slow/veto
2. Soft power with BDFL, while Eelco doesn't want/see himself as BDFL
3. Moderation pains
4. Conflicts of Interest with DetSys
5. Scope and Time -> Funding for the project
6. Xe's blog

In reply to @ronef:matrix.org

Just finished reading everything here, Matrix isn't friendly to scrolling.

I definitely hear the different issues raised and apologies for not being able to respond more timely from my end.

Jotting down a few of the issues mentioned that I've caught reading through (feel free to add/correct me)

1. Different wants/expectations around the boards role in the project - Choose and make it very explicit, then set up the structure around it to empower the community. Assuring teams/leads that no one is going to pop out of nowhere and hinder/block/slow/veto
2. Soft power with BDFL, while Eelco doesn't want/see himself as BDFL
3. Moderation pains
4. Conflicts of Interest with DetSys
5. Scope and Time -> Funding for the project
6. Xe's blog

In reply to @ronef:matrix.org

Just finished reading everything here, Matrix isn't friendly to scrolling.

I definitely hear the different issues raised and apologies for not being able to respond more timely from my end.

Jotting down a few of the issues mentioned that I've caught reading through (feel free to add/correct me)

1. Different wants/expectations around the boards role in the project - Choose and make it very explicit, then set up the structure around it to empower the community. Assuring teams/leads that no one is going to pop out of nowhere and hinder/block/slow/veto
2. Soft power with BDFL, while Eelco doesn't want/see himself as BDFL
3. Moderation pains
4. Conflicts of Interest with DetSys
5. Scope and Time -> Funding for the project
6. Xe's blog

In reply to @niksnut:matrix.org
The point isn't to "influence" the community but to improve Nix's adoption by addressing some of the biggest pain points (like docs and the installation process). As a Nix-based company growing the Nix user base is extremely important to us.

In reply to @kity:kity.wtf
Growing the Nix user base is an anti-goal for the community. The current "growing pains" as have been previously brought up are becoming a critical issue. Thisobviously aligns very closely with the rights-ratchet model outlined here: https://meshedinsights.com/2021/02/02/rights-ratchet

As well as this, the community will NOT grow and will only keep shrinking unless the issues that have been brought up continuously by every single community member who has left and declared their embarrassment to be part of a project that's behaving in this way are addressed. The community IS Nix.

If Eelco does not want to be seen as a BDFL trying to privatize Nix, he should prioritize the community's interests as stated by the COMMUNITY and maybe actually start reading what community members have been telling him repeatedly over years instead of apparently glancing at their messages for key words and then projecting his own guess of what they must be talking about. It is tone-deaf and insulting to our time and efforts.

In no unclear words let this message state: Eelco Dolstra is an obstacle to the community and should recuse himself immediately.

Growing the Nix user base is an anti-goal for the community.
Just ask for clarification, what does this mean?