Analysis of tools used in FairCOOP

(2018)This report aims to better understand the tools used within the ecosystem with their characteristics, advantages and disadvantages. If any of these tools is demonstrated to be essential, in my opinion (Al-Demon) we should enable a version of their own and controlled by the Tech Assembly without using external services.

(2019) An upgrade of the previous situation is taking place, heading to a distributed system (still in progress), decentralising Tech assembly functions in order to allow hardware, software and humanware to get along well together and optimize services and developing.

Software used within the ecosystem, update to march 2019:

  1. Drupal No more used
  2. Wordpress Still used freedomcoop.eu, getfaircoin, ufc
  3. ODOO in FM version 8 is used, planning update to 10 or 12
  4. HTML5 static website that's not a software, it's a MU language, in any case, used
  5. Telegram still used, despite once in a while someone comes with great ideas regarding alternative
  6. RocketChat not fully implemented though used, some Telegram group are bridged to Fairchat (fairkom rocketchat)
  7. Discourse used in Forum
  8. NextCloud used, together with owncloud, descentralised in fairkom
  9. Etherpad descentralised in fairkom
  10. Ethercalc descentralised in fairkom
  11. Wekan descentralised in fairkom
  12. WebCalendar descentralised in fairkom
  13. ValueNetwork used as Agent and Shroom
  14. Mumble (my personal experience (encosianima) is that it doesn't work with more than 5 ppl so that luckly NEVER USED
  15. KeyCloak another identity access manager, NEVER USED
  16. Yacy a search engine still searching out its space in Fair.coop NEVER USED
  17. Storj a nice and decentralised story, potencially, but sadly never happened NEVER USED
  18. LXD Server Roundcube (e-mail client) opens when hitting srv01.fair.coop, fact that makes me infer LXD not in use
  19. ERPnext used as Shroom roots ( even if mushrooms have spores, not roots :)
  20. OpenProject another project manager NEVER USED

Ideal methodology

NB, a category to evaluate electric consumption is missing, we just couldn't gather enough information.

Fields to be completed: - SOFTWARE: [ Name of installed software ]

  1. UPDATE: [ If is update the software and when ]
  2. PLUGINS/MODULES: [ Can we use modules separated about core source code ]
  3. DECENTRALIZED: [ If we can federate servers or sync backups ]
  4. DISTRIBUTED: [ If is a p2p tool ]
  5. CONSUMPTION: [ How energy consumption related normal tool ]
  6. KISS: [ Keep It Simple Stupid - One tool for one purpose ]
  7. DOCUMENTATION: [ If there good documentation with public access ]
  8. 4 FREEDOMS FS: [ If we liberate the code we change on modules ]
  9. COVER NEEDS: [ If now is covering our needs ]
  10. CONTROL VERSION: [ If we have a control system with almost 3 versions develop-testing-production ]

NB Value numbers representing quality and good practices related to software are assigned next to the domain (where? in the report?)… bear in mind that this analysis is extremely experimental and needs to improve both in methodology than in documentation.

### Further analysis software-analysis