Hyperbola was and is meant to be as a complete new paradigm within free, libre software and culture. Generic historical seen most projects act with the difference between maintainers, developers and users. The maintaining and developing persons act furthermore on behalf of a roadmap or when users report problems. But there is a residing problem within this as many users do not get more deep into their system and just demand it should work.

As the role “user” is most focussed on exactly “make usage of the operating-system running” is surely correct. But the intention is missed to make the “user” really free from further restraints and in the further progress of time those intentions were more and more forgotten likewise the complexity of installed software enlarged further. Today the restraints are not gone, just moved into other directions and embedded deep into many systems. To name some:

• restraint of non-free implemented firmware-blobs in drivers and / or even kernel
• restraint of non-free services and their implementation in per definition free and libre licensed projects (making them also to be named as complete non-free in the retrospective)
• restraint of data being added but perhaps not even free and libre licensed (to note that Hyperbola is not adding any of such projects, read therefore here)
• restraint of packages being added into free, libre system-projects but not licensed in any way free, libre and permissive

The list could go on further, but the named points are most important as users have the outlined impression that their used system is also “somewhat” freedom oriented and that is enough. Because most the time it is just the point that the hardware should work out of the box. Learning on how to configure options so perhaps a service can run? Or a missed out piece of hardware could nevertheless work? Impossible in those definitions as this does not work out of the box and whatever else: The maintainers, the developers should look after that, because a user uses the system. Nothing more and nothing less.

But this results in several problem-fields:

• smaller systems will not get more help and people reject them just because of those elementary failures in thoughts listed above
• free and libre projects, full community-oriented and driven by also a minority do not get more support
• in general free, libre software and culture is more shuttered with time passing by

It would be too easy and at the same time also not correct to claim this is only caused by one group or just one generic behaviour. It is the whole situation going out of control: Companies and corporations implementing more and more their known paradigm of trademarks and patents, projects following using tademarks and patents or even creating more their own also above, developers and maintainers following the whole course without either having the point of questioning or done this and gotten not very far with it including also further frustration and users in the end just accepting. Because of? Yes, because it is marked with buzzwords alike “open”, “open-source” or “free”.

All of those buzzwords are vague and not helpful in any way. But they mark the current development going out of hands and in the wrong direction: People associate “open” with “free and libre”, “open-source” with “free software” alone without recognizing the major differences and minor intrusive placed wording misguiding people over time. For sure this was not all intentional, but it was also accepted as it helped out with more ignorance in the whole amount and also with a desastrous outcome now.

In a whole we have a more strict perspective nowadays. For sure it is understandable that users just want a stable and reliable system working on. But we have also to confront ourself with the fact, that bad habits got in place so people just await getting not only a working system but also served at the same time all explanations, information and more. Sometimes not even with asking but just the awaitment. The desastrous outcome is in the end for all participating groups and individuals: Developers and maintainers get exhausted over time, sometimes even frustrated as they do not get helping hands when people await even more. And users get frustrated as they await a “working system” serving their expectations.

But that is not all: Over time services and generic operating-systems got even more complex. Not only inbound local complex but also enumerating outside services around the global network. So users await:

• newest (web-)services included local to be accessed at any given time without perspective on security, privacy and freedom
• services like wiki, forum and more all-time available, managed and working flawless
• full capacity downloads at any time, every day, week, month and year around

And as the result is “somewhat open”, concluding in comparison “free is gratis”, all is just in relation to be “in whatever state”. Users want to use the system, ask for sure questions and await therefore support and help. Some surely give more, some will help and some maintain and contribute. But the strict difference in a matter of “roles” is kept nevertheless.

In fact Hyperbola does not even want to enforce anything from anyone. It is just the common point we want to question and for sure change on behalf of using and attending at this project: We want to shake up people a bit that free, libre software and projects can only kept active when more people get also active themself. It does not matter on which way for the start and point being of now. There is enough to do: Documentation, testing, management of infrastructure, evaluation of services, further approval of more minimalistic approaches, development, license approvals and many more possible areas where people could engage in.

We need to acknowledge that smaller, minimalistic services and systems are the way forward. Monolithic, centralized places are surely a promise of safety, but in fact they have approved to be unreliable in regards to privacy, security and generic respect for every being with interest attending.

Hyperbola is not asking or / and demanding from its users to be also developers and maintainers at the same time. But if there are issues to be reported, it is not much asked for to work together on exactly those issues. So instead of just reporting them and afterwards await something from an individual or group in the role of “maintainers” we ask to stand up for being also a possible maintainer and researcher. To test and approve as this is all part of our one special interest named technical emancipation. As already mentioned the wording “emancipation” has many meanings and in political terms, it often means to free a being from a previous restraint or legal disability that violates basic human rights. We ask therefore the people to stand up for their right of informational self-determination, to keep their data under own control and to learn together more about tools and ways to keep each other safe with a working privacy and also mindset for exactly this.

So as “user” keep in mind that you can also be maintainer and developer at the same time. Please let us work together under the philosophy of Hyperbola, which finally includes do it yourself. You miss a package? Build it and share your insights. You found an issue? Share your insights and support people supporting you more. You have interests to help? Raise a hand and get in touch. But do not await only others to help you without giving something. Not only report and await afterwards movement. That is not the mood and interest of Hyperbola as project, as said: We want to break up with the named problems of “user as common role”. All of the named points “users” await are not self-evident and in fact hard work the smaller a project is. Asking for support, for donations and time helping others is a generic point free, libre projects did and need to do also today as it is their most important point: Giving “users” a point back, but also “users” should slip out of the generic role seemingly pre-defined. It is not, it should not as everyone can be user, developer and maintainer.