Hello dear interested travelers in the outer rim,
another month is now starting and therefore we take this opportunity to report what was and is going on for Hyperbola as project in the past month.
Works on HyperbolaBSD
Coadde has concluded the analysis for binutils and gcc: In fact the original implementation of our HyperBK uses backported assembler-instructions. So the conclusion is making it now possible also that we review the needed code for our implementation and needed backporting. With this we have now a good base for a near first working pre-alpha version of HyperbolaBSD as full BSD-descendant operating-system and the next step for Hyperbola as project in a whole. Please have also a look therefore on our roadmap for all next steps, as we refresh this on-going.
Works on Hyperbola GNU/Linux-libre
Much is going on for packaging, fixing and updating. But throgh was and is also busy with more to come for further additions towards our upcoming release 0.4.5. This will also include our hard-fork hyperman and more.
Wiki and information
We have released further articles for our wiki and therefore added more useful information for Hyperbola. Following up a short listing:
Cooperation and working together
Cryptocurrencies
Hyperbola and Commercialization
Website for Hyperbola
We look out for helping hands so we can further migrate the forum, wiki and issue-tracker into other environments. If you have interests into please just leave us a message via IRC or forums.
Current situation on financials and donations
More details about current financial-report this month to find here.
Until the next report upcoming: Stay curious and build on Hyperbola!
Hello dear explorers, we have added another article in our wiki informing about Hyperbola's stance towards commercialization. Short bound said: Yes, Hyperbola as system-project can be used out of commercial interests as this is part of a free decision. But Hyperbola itself will never accept pure commercialization. Our stance is and stays technical emancipation and enabling users, motivating everyone interested to be developer, user or further administrator. It is the individual decision, but with care for freedom, pricacy and security.
Further details:
We have added another ruleset regarding code / data generated through machine-learning as the Hyperbola-project will always stay true towards data and code generated from people for people. Therefore we reject and do not allow code, imagery and / or texts generated through machine learning to be used direct and / or indirect for Hyperbola and its development.
Further details:
Hello dear interested travelers in the outer rim,
starting from now on we want to give insights into the current state of development at the start of every month. Included are for sure Hyperbola GNU/Linux-libre and HyperbolaBSD. Furthermore we want also give updates what is coming for our website and also report what was changed on our wiki. Included also is the monthly financial report for Hyperbola as project.
Works on HyperbolaBSD
We are currently working on fixing our versions of binutils and gcc. Coadde as our main developer has discovered major problems in relation to our kernel HyperBK ...
Hyperbola as project was and is always oriented on technical emancipation as elemental key. Within this we also want to stay true for supporting x86-compatible, older hardware, including i686 and x86_64 architectures.
This means that we also have no further interest following so-called trends as supporting older hardware makes sense for the good of our community and the good of our planet.
With this elemental point we also want to oppose those from our understanding false definitions of "progress" as users should always have the power to decide on their own and control all parts of their system, which is ...