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.
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?
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
@lynnfoster Actually I don't understand when you say there are too much "must"
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)
Yeah I need to read myself 3 or 4 times before getting the right ideas off my head :D
Waw, this is getting pretty well structured. Good momentum.
@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?
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.
Apparently Net cloud is a good alternative, but I can't say as I didn't test it yet.
Have you ?
P.S. I generally agree with Bob's and Lynn's concerns about Google Docs. (I didn't consider that in my very specific and quick "vote".)
We're experimenting with @funkycram 's suggestions. @jimwhitescarver you might want to add your organization(s) to this doc:
https://hackmd.communecter.org/MYFgzMCGAMCcIFoAmsBswEgEZYEwK1gEZYFdytolhpUAzSMIA===
[edit] You probably need some access permissions, which you can probably get from funkycram...
@gregorycassel @bobhaugen @jimwhitescarver @lynnfoster
Our new "Google drive" open alternative (Nextcloud on our server) has just been launch : https://cloud.openappecosystem.cc/index.php/s/ySqpaoi6AGuZzsx
Feel free testing it.
For https://hackmd.communecter.org , you need an account to edit, but registration is open : just enter a username and password, click on "register" and enter your username and password again to login.
I'm sorry for not taking part to all the Loomio discussions, but I don't have enough time to both participate to the debates and code. So when needed a technical information, contact me preferentially on https://chat.lescommuns.org/channel/open.apps.ecosystem or in private message in this chat. Thanks.
Regarding potential Google Docs alternatives: They sometimes lack one or more of the specific features of Google Docs, such as selection-based commentary which I find extremely helpful during RFC/ request for comments phases. (Sometimes, the alternatives also have extra functions of IMO variable usefulness.) However, my main concern really with collaborative editing is data security.
Google Docs creates a good deal of data security IMO by being a longstanding feature of a wealthy corporate monolith. I'm confident that my Google Docs aren't likely to disappear for a very long time, if ever. Alternatives definitely vary on this front.
Ideally, a collaborative editing app should enable people to easily export all data in a reasonably readable (or ready-to-use) format. (For instance, by using structural metadata which directly links selection-based comments to the selections they were attached to.) If an app did this-- allowed easy, effective & complete export-- then I'd be much less concerned about data security.
At least some of the document styles in https://cloud.openappecosystem.cc/index.php/s/ySqpaoi6AGuZzsx (like that one) allow selection-based comments.
I have installed https://nextcloud.com/collaboraonline/ for ODT files editing. It support changes recording, multiple users editing in the same time and selection-based commentary.
Backups are done every day. Files are standard ODT files, you can edit them on your local computer with Libre Office.
@funkycram 's comment arrived just as I was posting mine, but I can confirm selection-based comments...
Shall we put this description ?
proposal by Draft 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 | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 3 | 43 | 2 | ||
| Abstain | 1 | 14 | 1 | ||
| Disagree | 3 | 43 | 2 | ||
| Block | 0 | 0 | 0 | ||
| Not voted | 114 | 94 |
I think we should take some time to figure out an open source alternative to google docs.
(Trying this again, I don't see that it showed up the first time.) I would like to eliminate the actions and resources sections. I would like to not use Google. I would like to deepen our analysis, check discussion from Ivan and others.
I would like to eliminate the actions and resources sections so we don't have to change it to keep it up to date. I would like to not use Google. I would like to deepen our analysis, check discussion from Ivan and others.
Ok for the text. To replace google, why not using https://cloud.communecter.org ? It integrate Collabora which permits to work on open documents in a collaborative way.
We need to start somewhere, this looks like a good start.
I'd prefer other wording, per a very detailed comment I made in this group a couple of weeks ago:
- the emergence of open, inclusive economic and social systems
- connection between people who build and use open systems
- collaboration in general
Definitions should be taken from previously agreed OAE / CTA discussions. e.g. the vision and the definition of OAE as: "A suite of interoperable tools which support transparent, democratic, decentralised collaboration."
I made a proposal for the objective (we didn't agree on this before) : https://www.loomio.org/d/AwIh7mYM, I personnally agree with all your propositions ;)
Put all the docs in the nextcloud is a good idea.
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.