iInitial commit of the core bitreich documents. - bitreich-documents - The repository to track the core bitreich documents. Err bitreich.org 70 hgit clone git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/bitreich-documents/ URL:git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fziv5h2hhfrinws65d7roiv6bfj7d652fid.onion/bitreich-documents/ bitreich.org 70 1Log /scm/bitreich-documents/log.gph bitreich.org 70 1Files /scm/bitreich-documents/files.gph bitreich.org 70 1Refs /scm/bitreich-documents/refs.gph bitreich.org 70 1Tags /scm/bitreich-documents/tag bitreich.org 70 i--- Err bitreich.org 70 1commit acd3739a8c0912293451db5e592d67924f51531e /scm/bitreich-documents/commit/acd3739a8c0912293451db5e592d67924f51531e.gph bitreich.org 70 hAuthor: Christoph Lohmann <20h@r-36.net> URL:mailto:20h@r-36.net bitreich.org 70 iDate: Wed, 24 Jan 2018 16:11:46 +0000 Err bitreich.org 70 i Err bitreich.org 70 iInitial commit of the core bitreich documents. Err bitreich.org 70 i Err bitreich.org 70 iDiffstat: Err bitreich.org 70 i A bitreich-branches.md | 53 ++++++++++++++++++++++++++++++ Err bitreich.org 70 i A bitreich-manifesto.md | 100 +++++++++++++++++++++++++++++++ Err bitreich.org 70 i A bitreich-organisation.md | 43 ++++++++++++++++++++++++++++++ Err bitreich.org 70 i A bitreich-qa.md | 35 +++++++++++++++++++++++++++++++ Err bitreich.org 70 i A index.gph | 0 Err bitreich.org 70 i Err bitreich.org 70 i5 files changed, 231 insertions(+), 0 deletions(-) Err bitreich.org 70 i--- Err bitreich.org 70 1diff --git a/bitreich-branches.md b/bitreich-branches.md /scm/bitreich-documents/file/bitreich-branches.md.gph bitreich.org 70 i@@ -0,0 +1,53 @@ Err bitreich.org 70 i+# Bitreich Branches Err bitreich.org 70 i+ Err bitreich.org 70 i+Bitreich has several branches which represent ideas of the current time where Err bitreich.org 70 i+the to be done work to change the software around us can be categorized to a Err bitreich.org 70 i+certain or certain tasks. New branches can be created just by your work on Err bitreich.org 70 i+them. Please try to collect them to have at least an index. Err bitreich.org 70 i+ Err bitreich.org 70 i+## New Applications Err bitreich.org 70 i+* This branch can be abstracted further, when more software is produced. Err bitreich.org 70 i+* Write new applications. Err bitreich.org 70 i+* The first goal is to change existing software. If not possible, rewrite as Err bitreich.org 70 i+ simple as possible. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Graphical Interface Err bitreich.org 70 i+* Work on new graphical interface ideas. Err bitreich.org 70 i+ * see tabbed(1) Err bitreich.org 70 i+ * see dwm(1) Err bitreich.org 70 i+ * see dmenu(1) Err bitreich.org 70 i+* Try to get existing graphical interfaces or toolkits to use the new Err bitreich.org 70 i+ metaphors for the sake of our sanity. WIMP is dead. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Abstractions Err bitreich.org 70 i+ Err bitreich.org 70 i+Most libraries tend to be written in complex ugly programming languages, but Err bitreich.org 70 i+they do their task well. The basic fact that the solutions are written in ugly Err bitreich.org 70 i+complex programming languages forces some other programmer to rewrite a Err bitreich.org 70 i+solution or some algorithm. Err bitreich.org 70 i+ Err bitreich.org 70 i+* Write commandline interfaces for ugly abstracted software. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Ugly World Err bitreich.org 70 i+ Err bitreich.org 70 i+Big applications like for example libreoffice are enforced into our life by Err bitreich.org 70 i+public request. Easier access is needed to the ugly world. Err bitreich.org 70 i+ Err bitreich.org 70 i+* Collect or write small utilities, polish them and give examples in how to Err bitreich.org 70 i+ access the ugly world out there in an easy way using the commandline. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Code Cleanup Err bitreich.org 70 i+ Err bitreich.org 70 i+There is software out there which was written by some hobbyist but it does a Err bitreich.org 70 i+very good job. Err bitreich.org 70 i+ Err bitreich.org 70 i+* Collect small application, polish them and make them reusable. Err bitreich.org 70 i+ Err bitreich.org 70 i+Other software is really big but only got big by applying metaphors from Err bitreich.org 70 i+university which were never really understood but are annoying our life just Err bitreich.org 70 i+by their existence. Err bitreich.org 70 i+ Err bitreich.org 70 i+* Find software you daily use, find ugly for example object abstractions and Err bitreich.org 70 i+ remove them using a good functional style. Then try to get the patches into Err bitreich.org 70 i+ mainline. Err bitreich.org 70 i+ Err bitreich.org 70 1diff --git a/bitreich-manifesto.md b/bitreich-manifesto.md /scm/bitreich-documents/file/bitreich-manifesto.md.gph bitreich.org 70 i@@ -0,0 +1,100 @@ Err bitreich.org 70 i+# Bitreich Manifesto Err bitreich.org 70 i+ Err bitreich.org 70 i+## Introduction Err bitreich.org 70 i+ Err bitreich.org 70 i+We live surrounded by complex software which receives new versions and Err bitreich.org 70 i+updates day after day. RAM and CPU consumption never reduce, they in‐ Err bitreich.org 70 i+crease. Software still provides the same features from years ago, but Err bitreich.org 70 i+everything looks new. This is called »advance« in the new speak of pro‐ Err bitreich.org 70 i+prietary software development. Err bitreich.org 70 i+ Err bitreich.org 70 i+This has to change! Err bitreich.org 70 i+ Err bitreich.org 70 i+## Suckless Err bitreich.org 70 i+ Err bitreich.org 70 i+Suckless failed. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Consumerism Err bitreich.org 70 i+ Err bitreich.org 70 i+Consumerism is the ability of persons to lose their skill in thinking on Err bitreich.org 70 i+their own, producing things, applying logical and practical ways of be‐ Err bitreich.org 70 i+having. This disease of consumerism is striking the devices and comput‐ Err bitreich.org 70 i+ers we humans produced to make them not scale in the possibilities they Err bitreich.org 70 i+could be used for. Computers can do things consumers cannot want and Err bitreich.org 70 i+imagine before they use the computer for something. The market economy Err bitreich.org 70 i+of demand and supply does simply not work here. Err bitreich.org 70 i+ Err bitreich.org 70 i+## UNIX Principles Err bitreich.org 70 i+ Err bitreich.org 70 i+In the beginning of the development of software principles were intro‐ Err bitreich.org 70 i+duced how to create software which can be reused in ways the original Err bitreich.org 70 i+developers never imagined. Small utilities are combined using simple Err bitreich.org 70 i+pipes, speaking to eachother, just doing one task well. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Dawn Of Ugliness Err bitreich.org 70 i+ Err bitreich.org 70 i+By not applying this methodology to its extreme, by trying to force new Err bitreich.org 70 i+features of computers into the UNIX principles, binary blobs evolved into Err bitreich.org 70 i+a complexity no young programmer can understand. They are forced into Err bitreich.org 70 i+the industry due to »life events«, where they are degrading to robots Err bitreich.org 70 i+which only apply what they learned at programming school (e.g. life, Err bitreich.org 70 i+university ...). This circle is producing even bigger binary blobs. Err bitreich.org 70 i+Nowadays this evolved into shipping whole operating systems in images Err bitreich.org 70 i+which you run separately. Err bitreich.org 70 i+ Err bitreich.org 70 i+This has to end! Err bitreich.org 70 i+ Err bitreich.org 70 i+## Bitreich Err bitreich.org 70 i+ Err bitreich.org 70 i+We form a movement to improve our daily software life. Software has to Err bitreich.org 70 i+not misbehave, it has to follow our rules, it has to be reusable, it has Err bitreich.org 70 i+to be easily maintainable, it has to provide its recompilable source and Err bitreich.org 70 i+it has to be easily understandable. Err bitreich.org 70 i+ Err bitreich.org 70 i+### Bitreich Principles Err bitreich.org 70 i+ Err bitreich.org 70 i+#### KISP – Keep It Simple Perfect Err bitreich.org 70 i+ Err bitreich.org 70 i+Software needs to do one thing well / perfect. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### Commandline Interfaces Err bitreich.org 70 i+ Err bitreich.org 70 i+Always add a commandline interface to your software. Graphical User In‐ Err bitreich.org 70 i+terfaces are for sissies. Pipes are welcome. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### When Possible Use GPLv3 Err bitreich.org 70 i+ Err bitreich.org 70 i+The signs of MIT‐appearance in the community is based on the circle of Err bitreich.org 70 i+complexity introduced into the minds of libre software programmers by Err bitreich.org 70 i+their oppressors transferring money to their bank accounts every month. Err bitreich.org 70 i+Your software is used in war machines to kill people and the companies Err bitreich.org 70 i+will never give back. So enforce GPLv3, it’s needed. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### Users Are Programmers Err bitreich.org 70 i+ Err bitreich.org 70 i+Software should be written for programmers, which means the code is the Err bitreich.org 70 i+documentation, it should be easy readable, low abstraction levels should be Err bitreich.org 70 i+used (OOP sucks most of the times) and a simple Makefile to build everything Err bitreich.org 70 i+needs to be present. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### Bugreports Are Patches Err bitreich.org 70 i+ Err bitreich.org 70 i+Bugtrackers are obsolete. Whenever you find a bug, fix it. The other Err bitreich.org 70 i+principles make it possible for you to send a patch instead of a report. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### Applications Can Be Done Err bitreich.org 70 i+ Err bitreich.org 70 i+When a project solves a problem, keep it done and declare it so. New Err bitreich.org 70 i+problems are solved by different projects. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### Freedom Of Language Err bitreich.org 70 i+ Err bitreich.org 70 i+The software world is spammed with new revolutionary programming lan‐ Err bitreich.org 70 i+guages every month. Choose whatever you need to solve your problem, but Err bitreich.org 70 i+keep to the above mentioned principles. Most new programming languages Err bitreich.org 70 i+solve a non‐problem the principles of bitreich solve. Err bitreich.org 70 i+ Err bitreich.org 70 i+#### Inevitability Of Change Err bitreich.org 70 i+ Err bitreich.org 70 i+These principles can change, based on the consent of the bitreich elite. Err bitreich.org 70 i+ Err bitreich.org 70 1diff --git a/bitreich-organisation.md b/bitreich-organisation.md /scm/bitreich-documents/file/bitreich-organisation.md.gph bitreich.org 70 i@@ -0,0 +1,43 @@ Err bitreich.org 70 i+# Bitreich Organisation Err bitreich.org 70 i+ Err bitreich.org 70 i+Bitreich.org is the seed of a movement to improve our daily software Err bitreich.org 70 i+life. Based on the principles and words in the bitreich manifesto we Err bitreich.org 70 i+work towards providing the basic infrastructure for anyone to host, Err bitreich.org 70 i+maintain and publish their projects. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Inner Circle Err bitreich.org 70 i+ Err bitreich.org 70 i+In the beginning an inner circle is formed to setup the infrastructure Err bitreich.org 70 i+and decide about credentials. The inner circle decides about its rules. Err bitreich.org 70 i+It has to tell the movement about its work. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Services Err bitreich.org 70 i+ Err bitreich.org 70 i+### Source Control Management Err bitreich.org 70 i+ Err bitreich.org 70 i+Git seems to have won the SCM war. Other SCMs are welcome, if someone Err bitreich.org 70 i+maintains and adapts them to the global infrastructure. Err bitreich.org 70 i+ Err bitreich.org 70 i+### NNTP Err bitreich.org 70 i+ Err bitreich.org 70 i+Mailinglists have the problems of bouncing, registration, ugly maintain‐ Err bitreich.org 70 i+ership etc.. NNTP is far superior for discussions, archival and protocol Err bitreich.org 70 i+access. It reduces abstraction for ease of use. Err bitreich.org 70 i+ Err bitreich.org 70 i+### Gopher Err bitreich.org 70 i+ Err bitreich.org 70 i+The web has outlived itself. Long live gopher! Err bitreich.org 70 i+ Err bitreich.org 70 i+### SSH Err bitreich.org 70 i+ Err bitreich.org 70 i+We may consider pushing all services via SSH to gain all advantages of Err bitreich.org 70 i+SSH. Err bitreich.org 70 i+ Err bitreich.org 70 i+## Conference Err bitreich.org 70 i+ Err bitreich.org 70 i+There will be a yearly conference. Since the main founder of the move‐ Err bitreich.org 70 i+ment is living near Chemnitz, Germany, where the annual Chemnitzer Lin‐ Err bitreich.org 70 i+uxtage (Chemnitzer Linuxdays) are happening in March/April and it’s a Err bitreich.org 70 i+historical place for predecessor movements of bitreich, the conferences Err bitreich.org 70 i+will happen there until further change of this paragraph. Err bitreich.org 70 i+ Err bitreich.org 70 1diff --git a/bitreich-qa.md b/bitreich-qa.md /scm/bitreich-documents/file/bitreich-qa.md.gph bitreich.org 70 i@@ -0,0 +1,35 @@ Err bitreich.org 70 i+# Bitreich Quality Assurance Err bitreich.org 70 i+ Err bitreich.org 70 i+Quality assurance is fraud and used by managers without a clue to cover their Err bitreich.org 70 i+incompetence in organized irresponsibility. Err bitreich.org 70 i+ Err bitreich.org 70 i+## QA in Bitreich Err bitreich.org 70 i+1. Use something. Err bitreich.org 70 i+2. Send in a patch. Err bitreich.org 70 i+ Err bitreich.org 70 i+## QA for Nonbelievers Err bitreich.org 70 i+1. Send in the following form to __20h__ on #bitreich-en in three copies over Err bitreich.org 70 i+ IRC. Err bitreich.org 70 i+2. Wait for the response. Err bitreich.org 70 i+ Err bitreich.org 70 i+### QA Form Err bitreich.org 70 i+ Err bitreich.org 70 i+ ======[ Bitreich QA ]====== Err bitreich.org 70 i+ Name: _________________________ Err bitreich.org 70 i+ Nick: _________________________ Err bitreich.org 70 i+ E-Mail: _______________________ Err bitreich.org 70 i+ Err bitreich.org 70 i+ What is your request? Err bitreich.org 70 i+ [ ] I want to contribute. Err bitreich.org 70 i+ [ ] I want to talk. Err bitreich.org 70 i+ [ ] I want to be cool. Err bitreich.org 70 i+ [ ] I want to lurk. Err bitreich.org 70 i+ Err bitreich.org 70 i+ Date/City: ____________________ Err bitreich.org 70 i+ Err bitreich.org 70 i+ Signature: ____________________ Err bitreich.org 70 i+ Err bitreich.org 70 i+## Formal Ending Err bitreich.org 70 i+ Err bitreich.org 70 i+Yours lovely bitreich quality officer. Err bitreich.org 70 i+ Err bitreich.org 70 1diff --git a/index.gph b/index.gph /scm/bitreich-documents/file/index.gph.gph bitreich.org 70 .