 |
bitreich-organisation.md - bitreich-documents - The repository to track the cor… |
 |
git clone git://bitreich.org/bitreich-documents/ git://enlrupgkhuxnvlhsf6lc3fzi… |
 |
Log |
|
Files |
|
Refs |
|
Tags |
|
--- |
|
bitreich-organisation.md (1378B) |
|
--- |
|
1 # Bitreich Organisation |
|
2 |
|
3 Bitreich.org is the seed of a movement to improve our daily software |
|
4 life. Based on the principles and words in the bitreich manifesto we |
|
5 work towards providing the basic infrastructure for anyone to host, |
|
6 maintain and publish their projects. |
|
7 |
|
8 ## Inner Circle |
|
9 |
|
10 In the beginning an inner circle is formed to setup the infrastructure |
|
11 and decide about credentials. The inner circle decides about its rules. |
|
12 It has to tell the movement about its work. |
|
13 |
|
14 ## Services |
|
15 |
|
16 ### Source Control Management |
|
17 |
|
18 Git seems to have won the SCM war. Other SCMs are welcome, if someone |
|
19 maintains and adapts them to the global infrastructure. |
|
20 |
|
21 ### Gopher |
|
22 |
|
23 The web has outlived itself. Long live gopher! |
|
24 |
|
25 ### SSH |
|
26 |
|
27 We may consider pushing all services via SSH to gain all advantages of |
|
28 SSH. |
|
29 |
|
30 ### IRC |
|
31 |
|
32 Our main community epicenter is IRC. Using IRC for central communication |
|
33 gives us the advantages of forcing members to be online to see the back�… |
|
34 log. IRC can be easily extended for writing helper bots. Major networks |
|
35 exist to have decentralized services for bitreich. |
|
36 |
|
37 ## Conference |
|
38 |
|
39 There will be a yearly conference. The next conference location is de�… |
|
40 cided at the current conference. |
|
41 |
|
42 We have to make sure everyone can attend the conference via simple and |
|
43 bandwidth‐saving protocols. Graphics will add unneeded bloat when te… |
|
44 is enough. |
|
45 |
