We have to reflect both the independence of projects within the FairCoop ecosystem but also need some hierarchy for folder lists etc.
In general we should avoid abbreviations, as this discriminates newcomers. Always write in full FairCoop or explain in a footnote OCP = OpenCollaborationPlatform etc.
FairCoop name space
Mainly used with folder or project structures. We prepend FairCoop to folder names if the system can not show the full tree, when a folder is being shared, so a user knows where it belongs to. If the platform allows naming a project separately from its URI (filname, folders, URL), then we can use : and if sharing always includes the tree, then we do not need to use the FairCoop prefix. We will use the prefix for owncloud or chat groups.
This is the fair.coop root of the files system or the root group at gitlab.
FairCoopMediaCommunication (= gitlab project + owncloud folder with subfolders:)
FairCoopGraphicDesign (strongly connected to local nodes)
FairCoopTech (= gitlab subgroup)
FairCoopSites (= gitlab subgroup)
FairCoopWelcomeSupport (= gitlab project + owncloud folder with subfolders:)
FairCoopEducation (move Tutorials folder in owncloud here)
FairCoopCommonsManagement (will mainly use OCP and has the following chat groups:)
In addition, we will use the following labels to assign tasks or files to projects. Labels are supported by gitlab and nextcloud (tag extension).
Each service may have its own or more chat groups.
FairCoin has several chat channels, so let's assign a second root, which we do not necessarily need at other services.
gitlab project and software management by fairkom. More open source web apps at fairapps.net