General presentation of the loomio's group
If you want to modify this document, go there : https://docs.google.com/document/d/10CSLuoQwHpQc4UeO1MVPADTUHTzEZ1daDmRIZjV4qNc/edit?usp=sharing
Objective
The goal is to create an ecosystem of interconnected independent open source applications easy to use, install, configure and contribute to. This ecosystem will enable :
* the new economic and social system to come.
* to connect those who are building and using open systems.
* individuals with the same goal to work together.
Analysis
Open source softwares exist, but are isolated. Therefore, having access to them is difficult : you have to install them on a server, know and remember the URL, create a user account and explain to the persons you are working with how they can join you, so they need to make a new account.
Platforms of apps like Sandstorm or Cloudron exist, groups using them are isolated from other groups or potential other contributors.
Our actions to fulfill the objective
Feel free to join them !
- Single Sign On (SSO) : An SSO provide the capacity to log to several apps with a unique account.
- Building a User Interface (UI) Component Library : Help tiny open app to develop.
RESOURCES we use
Digital TOOLS
- Wekan : ACTIONS manager
- Riot : Chat EN
- Rocket Chat : Chat FR
- Google doc : Centralise all the informations about the open app ecosystem
GUIDE : How to contribute
To contribute to the Open App Ecosystem, it's really simple :
- Your ACTION may fulfill the global OBJECTIVE which is to create an ecosystem of interconnected independent open source applications easy to use, install, configure and contribute to.
- If it does, add it in the wekan
- In the For NEWCOMMERS column you will find a GUIDE to add an ACTION to make it as easy to understand as possible.
Lynn Foster Sun 30 Jul 2017 6:23PM
Just clicked into this https://github.com/open-app/core from the existing intro. Has some good ideas in it, like the list of criteria for an open app in the ecosystem.
Can we make use of some of the original historical references, to keep some continuity?
Draft Sun 30 Jul 2017 7:57PM
I added the github resource.
I'd like this intro to be very concrete. And SSO, common menu are very concrete. Even if we don't all agree on this, it's something hapenning.
What we could do is to make a list of our concrete actions and put the links of the different actions in the wekan, instead of saying go the wekan. Like that people are more likely to participate ? :D
I created a google doc (easier to make comment) : https://docs.google.com/document/d/10CSLuoQwHpQc4UeO1MVPADTUHTzEZ1daDmRIZjV4qNc/edit?usp=sharing
Draft Sun 30 Jul 2017 8:34PM
@lynnfoster Actually I don't understand when you say there are too much "must"
Lynn Foster Sun 30 Jul 2017 9:03PM
Actually I don't understand when you say there are too much "must"
Ah my mistake, they are gone now, I needed to refresh my page it looks like.... sorry about that! (note to self in the future)
Draft Sun 30 Jul 2017 10:39PM
Yeah I need to read myself 3 or 4 times before getting the right ideas off my head :D
Tiberius Brastaviceanu Sun 30 Jul 2017 11:14PM
Waw, this is getting pretty well structured. Good momentum.
Poll Created Fri 11 Aug 2017 9:46PM
Shall we put this description ? Closed Mon 14 Aug 2017 9:56PM
Objective
The goal is to create an ecosystem of interconnected independent open source applications easy to use, install, configure and contribute to. This ecosystem will enable :
* the new economic and social system to come.
* to connect those who are building and using open systems.
* individuals with the same goal to work together.
Analysis
Open source softwares exist, but are isolated. Therefore, having access to them is difficult : you have to install them on a server, know and remember the URL, create a user account and explain to the persons you are working with how they can join you, so they need to make a new account.
Platforms of apps like Sandstorm or Cloudron exist, groups using them are isolated from other groups or potential other contributors.
Our actions to fulfill the objective
Feel free to join them !
- Single Sign On (SSO) : An SSO provide the capacity to log to several apps with a unique account.
- Building a User Interface (UI) Component Library : Help tiny open app to develop.
RESOURCES we use
Digital TOOLS
- Wekan : ACTIONS manager
- Riot : Chat EN
- Rocket Chat : Chat FR
- Google doc : Centralise all the informations about the open app ecosystem
GUIDE : How to contribute
To contribute to the Open App Ecosystem, it's really simple :
- Your ACTION may fulfill the global OBJECTIVE which is to create an ecosystem of interconnected independent open source applications easy to use, install, configure and contribute to.
- If it does, add it in the wekan
- In the For NEWCOMMERS column you will find a GUIDE to add an ACTION to make it as easy to understand as possible.
Results
Results | Option | % of points | Voters | |
---|---|---|---|---|
|
Agree | 42.9% | 3 | |
Abstain | 14.3% | 1 | ||
Disagree | 42.9% | 3 | ||
Block | 0.0% | 0 | ||
Undecided | 0% | 114 |
7 of 121 people have participated (5%)
Bob Haugen Sat 12 Aug 2017 11:18AM
@funkycram
To replace google, why not using https://cloud.communecter.org ? It integrate Collabora which permits to work on open documents in a collaborative way.
I wanted to try it for a list of organizations and their internal working policies in response to a conversation in https://chat.lescommuns.org/channel/open.apps.ecosystem - but it wants a username or email and password, which seem to assume a user account, but does not seem to offer a way to sign up for an account.
Also, how does that compare to https://hackmd.communecter.org/ , which @tiborkatelbach just suggested in that chat?
Jim Whitescarver Sun 13 Aug 2017 5:06PM
Replacing google docs should be a priority but I have found no equivalent collaborative authoring environment. Work in google docs is highly productive in several communities I am in. It will make us more effective in the short term until we can replace it and the rest of google office. Google Script is a way we can integrate with the tools of the future as they become available.
Lynn Foster · Sun 30 Jul 2017 6:12PM
Thanks for gathering this, @draft @funkycram . Good idea to expand the opening page.
Feedback:
I think we should not mention SSO or common menu in the intro, that is too implementation oriented. Or Communecter, let's keep all the specifics out to be more open. Suggest something like "See the wekan board (with link) to see what is being worked on right now."
I agree with @bobhaugen that there are too many MUSTs. If we have a problem with someone's behavior in the collective, we resolve it directly with them.
I think the "technical explanation of the ecosystem" is not discussed or decided yet, it is too early for that to be in the introduction.