bitreich-branches.md - bitreich-documents - The repository to track the core bi… | |
git clone git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fzi… | |
Log | |
Files | |
Refs | |
Tags | |
--- | |
bitreich-branches.md (3083B) | |
--- | |
1 # Bitreich Branches | |
2 | |
3 Bitreich has several branches which represent ideas of the current time | |
4 where the to be done work to change the software around us can be cate�… | |
5 gorized to a certain or certain tasks. New branches can be created just | |
6 by your work on them. Please try to collect them to have at least an in�… | |
7 dex. | |
8 | |
9 ## New Applications | |
10 * This branch can be abstracted further, when more software is produced. | |
11 * Write new applications. | |
12 * The first goal is to change existing software. If not possible, re‐ | |
13 write as simple as possible. | |
14 | |
15 ## Graphical Interface | |
16 * Work on new graphical interface ideas. | |
17 * see tabbed(1) | |
18 * see dwm(1) | |
19 * see dmenu(1) | |
20 * Try to get existing graphical interfaces or toolkits to use the new | |
21 metaphors for the sake of our sanity. WIMP is dead. | |
22 | |
23 ## Abstractions | |
24 | |
25 Most libraries tend to be written in complex ugly programming languages, | |
26 but they do their task well. The basic fact that the solutions are writ�… | |
27 ten in ugly complex programming languages forces some other programmer | |
28 to rewrite a solution or some algorithm. | |
29 | |
30 * Write commandline interfaces for ugly abstracted software. | |
31 | |
32 ## Ugly World | |
33 | |
34 Big applications like for example libreoffice are enforced into our life | |
35 by public request. Easier access is needed to the ugly world. | |
36 | |
37 * Collect or write small utilities, polish them and give examples in how | |
38 to access the ugly world out there in an easy way using the commandlin… | |
39 | |
40 ## Code Cleanup | |
41 | |
42 There is software out there which was written by some hobbyist but it | |
43 does a very good job. | |
44 | |
45 * Collect small application, polish them and make them reusable. | |
46 | |
47 Other software is really big but only got big by applying metaphors from | |
48 university which were never really understood but are annoying our life | |
49 just by their existence. | |
50 | |
51 * Find software you daily use, find ugly for example object abstractions | |
52 and remove them using a good functional style. Then try to get the | |
53 patches into mainline. | |
54 | |
55 ## Protocols | |
56 | |
57 New protocols are introduced to solve problems which have already been | |
58 solved by simpler protocols. | |
59 | |
60 * Get people to use simple protocols by refurbishing old clients, writ‐ | |
61 ing new software for the protocols and educating the world. | |
62 * see IRC | |
63 * see gopher | |
64 * see SSH and kiosk | |
65 * see sfeed for news | |
66 * gopher for radio streaming | |
67 | |
68 ## Memes and Fun | |
69 | |
70 Online culture is an important way to get people into a project. By | |
71 having fun and people benefiting from joining the project, even in a | |
72 simple way of a laugh, will grow Bitreich. | |
73 | |
74 * see annna and the memecache. | |
75 * see bitreich cooking for daily cooking news | |
76 * see various side projects | |
77 * Bithub for intellectual porn | |
78 * Bitreich TV for memes on stream | |
79 * annna for meme management | |
80 * memecache for meme economics | |
81 * see Day Of The GrParazyd (DOTG) for a game | |
82 * see ECTS credit programme for free | |
83 * get your meme degress | |
84 * see data offence anonymous meeting group | |
85 * join the friendless anti-social network | |
86 * become part of the snowmen programme for no benefits | |
87 * we are best at forgeperf | |
88 * see your future | |
89 * get a random joke | |
90 * watch vt100 movies | |
91 | |
92 |