Don't get me wrong: I'd like to have Hyperbola / HyperbolaBSD being free and independent, being built with open and transparency in mind, so everyone can use, include and build on top of that. Therefore my thoughts and questions at this point as the last entry is dated back more than a year ago. What was absolutely cool to have more insights with the TODO-lists for example, but since everything was reworked those are no longer functional and therefore more or less of no further usage for now. Also the spreadsheet with wished software-packages for 0.4-release is a great idea, but how far is the progress and what is needed next? Getting multilib-support for 0.4? Or is this something to rely onto the community and therefore building an own repository-database as proposal? Hey, there is much possible, but with better communication this can be done even more faster, just my proprosal so far.

throgh, our team of volunteers lacks of someone who could do the communication about our progress here and those tasks that you are requesting. Would you like do it for Hyperbola Project and become part of the new team? Please join in the ASLE's IRC channel (#asle) from Monday to Friday at 14h00 UTC-5.

Thanks for the answers. First things first: I just want to help the project and the people behind as I think Hyperbola is so much more and near to my understanding of free software / free culture. Therefore my criticism as deeply respect and callout for help. To build a kernel, userland for BSD and also a distribution for Linux-libre is very hard, with much time needed. To help having Hyperbola being transparent is so much more important. That's not meant as "failure" from my side, just an invitation for thoughts and points also here in the thread: Building something needs a workflow, a toolkit and everything is here. But don't left the group of developers and supportes just alone, don't leave the community alone with names and people unknown. This is not meant as being "intentionally", just meant: Let's talk with each other.

Thank you and I will follow this invitation.
So I think the community itself can be just so much helpful: Not only as users, with nothing to say. You all have to say something, to help this incredible project. Let's build this together!

Thank you for your time throgh, it will be so important for us, not just to spread info and invitations here or for our lacking of time, but helping those students who never heard about free software and licenses concepts. It's making so hard for us to create a new team, but you could make more easy and possible by joining our official team and doing those tasks such as the communication and another important similar things where we developers aren't good doing it.

Valid point, so I'd propose to keep the "balance of trust": sagaracharya made that clear.
Besides: I'm also developer, but perhaps also within other parts engaged. That doesn't mean this is in some way "better", it's just the way to start with more transparent communication as I've learned this is an elementary part for a project: The "balance of trust" means having information collected for everybody of one community to read. The other way is loosing the connection and that's my point as I know how this feels and looks like: Loosing the connection to others. We have seen this, seeing this now and I think the invitation should be part for every member of the community. Therefore my sentence towards all here, everyone included. It's by beings for beings and there are many possibilities! Of course I'll follow the invitation, but just to note: I'll want to carry the information back into here. It would be also interesting to have more information about the upcoming work on HyperbolaBSD, the students to learn. I think especially here everyone, every member can come up with own motivations as sagaracharya noted.

The essential question: Why coming to Hyperbola? Why using HyperbolaBSD? It's not about technical issues, there are people here having so much more. But I cannot be a spokesperson for all and I don't want to be standing upon others, because I would be part of a ranking and I cannot speak for others, just giving insights and views. Sometimes my words and sentences even sound like a paraphrased utopia coming up from the essential whish, so I understand even everybody calling me an "illusionist". Therefore my proposal: Making some protocols, some notes about the rounds. Perhaps there are also people being more motivated? Empowering users freedom and knowledge. Having everyone in some developer, diplomatic and also scientist for alternatives alike, to keep free, libre software on a course. Learning here, to learn with others and giving knowledge.

But to summarize: I think the invitation can be seen for everyone interested learning more for development? This would a great news-entry for the forum, by the way.

As also said in the IRC: I'll give some more notes here in this thread, coming back from the talk later on. Therefore I summarize the concurrent points, but I can also say that the last sessions had interesting information as the team is building up to get HyperbolaBSD up and running in development. Thumbs up so far and I see the need to have more communication also here in the forum. Of course everybody interested can join, discuss and ask, being critical!

Well, that's a proper announcement. It should come from one of the founders though ideally.

Thanks for having me in Hyperbola Team.

Regarding important events, each member of the Hyperbola community (as seen in Founders, Devs, Support Staff, Security Team, Artists and Member fellows) should get a mail, preferably signed by one of founders. This will ensure politics stays away and each person would be able to give his thoughts if needed.

This does not mean there's democracy and everyone will get 1 vote in the decisions. Founders can override the concensus if they feel so. But people should know the important things. Each and every person.

Responsibilities should be clearly assigned so accountability can be checked in future. In communities, "do as you wish" attitude is the one which makes efficiency worse. Ask relevant people whether they would do a certain task and if they say yes, assign them on it and ask for accountability.