permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

onboarding.mdwn (3931B)

      1 The permacomputing ideas and practices are shaped by its community. To actively
      2 participate in the discussion we facilitate moderated services for individuals
      3 and groups: that's the role of the permacomputing infra. We are trying to be as
      4 mindful as possible in the choice of software and hardware we use. Why? Because
      5 permacomputing does not only concern the devices and appliances we physically
      6 interact with, such as a phone or desktop computer, but also the machines and
      7 networks that together provide the digital infrastructures for these more
      8 common devices and appliances.
      9 
     10 Some of these services can be joined by anyone at any time, such as the public
     11 XMPP and IRC chatrooms, or the email discussion list (see [[community]] page).
     12 However for those who want to participate more actively, we also offer access
     13 to a web forum, static web hosting and, of course, the permacomputing wiki. To
     14 do this we maintain a community server which we call Eik. It's kindly provided
     15 by [servus.at](https://core.servus.at/en/about/ueber-uns). Existing members of
     16 the community help maintain the server. We maintain [sysadmin
     17 documentation](https://permacomputing.net/eik/) for this machine.
     18 
     19 
     20 ## Growth at the speed of trust
     21 
     22 We prioritise diversity, moderation and online safety in the permacomputing
     23 community. To this end, we have written a [Code of
     24 Conduct](https://permacomputing.net/terms/) which we ask everyone to read and
     25 agree to before proceeding onwards to participation in our community. All the
     26 services we provide are subject to these terms. To be sure, this is a quick
     27 fix, eventually we will move to better articulated community guidelines.
     28 
     29 Keep in mind all moderation and communication is shared and carried out by
     30 community members on a volunteer basis. Thanks for your patience in advance.
     31 
     32 
     33 ## Overview of the extra services
     34 
     35 ### Web Forum (for individuals and groups)
     36 
     37 We host and maintain a [permacomputing forum](https://bbs.permacomputing.net/)
     38 to promote public discussions around permacomputing.
     39 
     40 
     41 ### Wiki (for individuals and groups)
     42 
     43 We host and maintain the [permacomputing.net wiki](https://permacomputing.net)
     44 together.
     45 
     46 
     47 ### Website hosting (for groups)
     48 
     49 We offer the possibility to host your own permacomputing static websites on
     50 Eik. For example,
     51 [berlin.permacomputing.net](https://berlin.permacomputing.net) and
     52 [top.permacomputing.net](https://top.permacomputing.net).
     53 
     54 
     55 ## How to join (WIP)
     56 
     57 ### Account Request through framaforms
     58 
     59 - 1) New people fill in this [form](https://framaforms.org/account-request-permacomputing-forum-1743087976)
     60 - 2) Swamp work group receives an email and review it (discussion in a dedicated XMPP room)
     61 - 3) If the application receives support from >= 2 members with no objections, it is accepted
     62 - 4) Someone from swamp work group will create the account on Rauthy
     63 - 5) New people receive an email to confirm and activate account
     64 
     65 
     66 ### What can you access with this account?
     67 
     68 * Web forum
     69 * Web hosting (for groups)
     70 * Wiki (pending... We are still working on the editorial guidelines. Once it's published you will get access.)
     71 
     72 
     73 ### TODO
     74 
     75 #### Setup work
     76 
     77 - [x] Back up entire system with Restic
     78 - [x] Investigate backup console access
     79 - [x] Install Rauthy and test forward auth
     80 - [x] Install Rauthy PAM/NSS modules and test
     81 - [x] Ensure toolshed access not limited by Rauthy / PAM breakdown
     82 - [x] Rauthy SFTP integration for web hosting
     83 - [x] Migrate wiki from borok to eik
     84 - [ ] Add Rauthy support to Cerca (web forum)
     85 - [ ] Connect wiki to Rauthy
     86 - [ ] Document new sysadmin reality (Rauthy, SFTP, etc.)
     87 - [ ] Editorial guideline for wiki
     88 
     89 #### Migration hell
     90 
     91 - [ ] Cerca user migrations (LURK SMTP, group mail testing, etc.)
     92 - [ ] Migrate web ssh users to new SFTP setup
     93 - [ ] Cleanup dormant user accounts on eik
     94 
     95 #### On the way out
     96 
     97 - [ ] Adjust signup form to reflect new infra choices
     98 - [ ] Re-organise swamp group to do moderation
     99 - [ ] Announce to the world