We now have a response from @lava in a separate thread, giving a bit more context for this "developer summit".
I try to quote main points from @lava here and post further questions for this organization:
I apologize for not giving more context on where this invitation comes from and what our intentions are.
Thanks, more context would have been great! However reading your full reply I still do not have an answer to what your intentions are with the initial topics you proposed for your summit?
I assume someone from your group thought a bit about this and listed the topics most relevant to your group as the initial starting point and I am curious as to why 67% of your topics concern coordination/governance of the reticulum project as a whole and the countless communities surrounding Reticulum?
The group I refer to, the "we" in the original invitation, is a loosely organized group of community organizers, hackers, artists and activists who have been organizing many reticulum workshops at autonomous centers, squats and cultural spaces in the Netherlands and beyond.
OK, now I better understand the conflation between voluntary community workshops and the summit invitation!
Looking at the link you provided, the general community work you seem to have been organizing looks awesome. No hard feelings from anyone on that point I think!
Your initial invite very much made it sound like this came from CriticalInfraLab and you had many references to them in your initial invite including signing yourself as "Lava, with the critical infrastructure lab" and "the research is done in collaboration with Maxigas (Dr. Peter Dunajcsik)".
The list of topics to discuss at the summit is only a proposal and there are, naturally, contested ones.
IMHO this reply "there are, naturally, contested ones" in the response to the topics criticized, is a very vague and non-satisfying answer to all the concerned raised!
To respond to Mark's concern, I have not heard anything about replacing RNS...
Your initial topics proposed for this "developer summit" very much suggested this. I hear no acknowledgment from your side about the concern raised on the agenda points, only a vague "I have not heard anything".
What is also true is that here are no networks without communities maintaining them.
I think everyone here acknowledges this, and I have never seen any hostility towards communities building networks, sharing knowledge and discussing Reticulum in general.
That being said, communities exists who calls for the removal of Mark from core Reticulum development and the replacement of him "by a community driven implementation", the replacement proposed is often maintained by a different single person, no real community implementation have ever showed itself and could never have solved the problems Mark is solving in RNS. Most of these one-man "communities" can expect a well deserved push-back when posting in this forum!
An example being a person called Liam with this presentation as a FOSDEM event. They acknowledge that Mark is still maintaining the RNS protocol behind the scenes (as he explicitly stated time and time again, that absurd discussion, like this one, are draining all his energy from core development).
Liam's group embraces the use of Beechat's implementation instead of RNS and have a full slide stating: A healthy project must separate from its founder.
Or Jobi Jara Kroese with "shared protocol spec scope and an initial conformance/test-vector plan that enables independent implementations", a protocol spec that will undoubtedly diverge from RNS itself. Especially since it is LLM-generated and get important parts of the protocol wrong. See Mark's notes on these "specs" here.
As we have seen clearly already, people are perfectly capable of creating Reticulum implementations that actually work and interoperate with the reference without any external LLM-generated "protocol specs" made by people who did not themselves seems to have read a single line of the reference implementation.
Now I will ask you this to rule out the possibility (as your agenda points to decentralizing of RNS and a separate Reticulum Foundation and protocol spec):
Are you Liam? Or Jobi? Who are you actually?
Your "summit" agenda with decentralization of development and a reticulum foundation to manage and distribute funds for developers very much points towards "decentralization" of Reticulum core development, by the removal of Mark.
So far your groups response to this real criticism have been non-existent.
it was hurtful to read through the comments and I hope rns.recipes can be a more welcoming space in the future.
You replied you felt hurt by the response you received here on rns.recipies.
You initiated a "developer summit" with these agenda suggestions:
- decentralization of development - This could only point to RNS itself, as everything else is already 100% decentralized.
- a reticulum foundation to manage and distribute funds for developers - Without ever contacting the active inventor/creator/maintainer of the network-stack to discuss this.
You literately catapulted a big blob of mud at the core developers - without taking responsibility for this or acknowledging this. And your response to the criticism is that you felt hurt and stating the space is unwelcoming when the mud was catapulted back.
Why is it hurtful to you that people reject external governance/coordinators of Reticulum and its communities as a whole? Aren't you the one talking about "decetralization"?
Why did you think people would embrace the proposed topics with open arms?
Do you think this is perfectly valid topics to discuss at a "developer summit" where core developers and maintainers are not present?
Do you not see the rudeness in this?
Why do you think it is your task to discuss a Reticulum Foundation without coordination with Mark?
Further I would still like to see replies to the list of questions posted earlier from the organizers of this "developer summit", and I would love to hear the thoughts behind the initially listed topics by anyone involved with the arrangement of this "developer summit".