Who is working now on Open Apps Ecosystem?

things seem to be heating up in the channel :) +111

as for Communecter, it mustn't be a game breaker but a game builder , or just a brick amongst others.
In the process of buidling things for the french ecosystem working on the commons, We build a "no brand version" which is interesting for trying to step away from any Branding and naming issue. Which, many beleive (so do I ) is a big source of the problem.
Getting a real ecosystem to work out , means :
1 - we (any of our communities) can seemlessly use and benefit 1.1 from each of our features,
1.2 - from any of our open data content and Each communities users decide what is opendata and what is not

2 - we all contribute to a common system (database and/or feature base ) , that grows not only through a common app but by the relations and contributions of each the ecosystems plateform

I won't go into detail, on how we (Communecter) imagined and are doing all this , but it's happening with a few use cases (apps and apis interconnecting ) and will be getting better month after month.
This would be a great call for discussion amongst architects , designer and developpers as you propose @lynnfoster

@funkycram
Our friends at Framasoft have a user DB, that can access a whole list of open source projects , it's part of solution but not all of it , and if I'm not mistaken, they are building an Linux distrib OS based on whyYouNoHost , that only contains open source installed apps , all this because Framasoft doesn't want to host you as a user, and is going for a distributed mainstream system.
Anyone today can do this on his own computer, they are just packaging it conveniantly.
I still undrestand this is not exactly what you have in mind and you want something directly online without a system to install.
If the ecosystem works out, I think the question remains on who serves and pays the service ?

so let's make it a call, with pleasure

I think the question remains on who serves and pays the service ?

Very important question. I think one trend is everybody hosts their own node, and organizations host their own node.

I am not a bigtime blockchain fan, but blockchains pay for hosting and operating the consensus method(s) by transaction fees. We also see more organizations taking responsibility for developing as well as hosting their own systems.

[edit] I missed this question, read too fast:

I still undrestand this is not exactly what you have in mind and you want something directly online without a system to install.

I suspect different people in this group have different things in mind...

Yes, I would like to build an ecosystem for non "geek" people.
Give to everyone the possibility to work without proprietary software.

And link it to a social platform such as Communecter so people can meet each other and make their project being known (and much more !).

I think the question remains on who serves and pays the service ?

Ha ha ! That's an eternal problem. Let's do it, and if many people enjoy it we will ask them to contribute or help us to find resources.

I won't go into detail, on how we (Communecter) imagined and are doing all this , but it's happening with a few use cases (apps and apis interconnecting ) and will be getting better month after month. This would be a great call for discussion amongst architects , designer and developpers

I look forward to learning more of the detail and the use cases!

I'll start a separate discussion....

I think the question remains on who serves and pays the service ?

The question could be : Who makes this job ? Who construct the machines ? (If we think in term of new economical organisation)

https://hangouts.google.com/hangouts/_/ytl/-SQJ_Vi0kfW73_TL06RXhJjsz3c6iSd1B0Gj8GBqMOs=?hl=fr_FR&authuser=0

This hangout is starting now - to look at Communecter, and talk about vocabulary and interoperability. We'll record it, in case you wanted to join but couldn't.

here's the recording
https://www.youtube.com/watch?v=9Yb5bomm-QE
thanks for joinning @lynnfoster @bobhaugen hope it was clear (and fun ;) )

I highly recommend people watch or at least skim the recording of today's demo. And yes it was fun! :)

We talked about others doing the same thing. Bob and I would volunteer to do one, in maybe 2 weeks. It would be NRP/OCP (brief because it is an app among many, not a linking app), Locecon (still pretty brief, might have some linking possibilities but we don't know), and ValueFlows (meant to create links among apps). If there is time in one session (which there well might be), we could also include the new Kamasi front-end, which also has linking possibilities, if @ivan116 is willing. It right now talks to NRP/OCP but the goal is to make it more independent.

Or if someone else wants to go first, that is good too.

We also talked about where to communicate. I'm dropping some links here for @tiborkatelbach to see if the Communecter vocabulary translation system can handle them. I'll also put them in the Wekan action, and also in https://chat.lescommuns.org/channel/open.apps.ecosystem once I get an account there.

They are from the ValueFlows Vocabulator demo.
* Agents:
* http://valueflows.pythonanywhere.com/vocab/agents/json/
* http://valueflows.pythonanywhere.com/vocab/agents/json-ld/
* Agent Relationships:
* http://valueflows.pythonanywhere.com/vocab/agentrelationships/json/
* http://valueflows.pythonanywhere.com/vocab/agentrelationships/json-ld/
* For a stretch goal, Processes:
* http://valueflows.pythonanywhere.com/vocab/processes/json/
* http://valueflows.pythonanywhere.com/vocab/processes/json-ld/

I need to get the process flows presented in json and json-ld, too, but in the meantime, here's a diagram.

I work on open technology standards-- not directly on any apps, for now. Of course, I think that Open App Ecosystem certainly needs to develop one or more standards (or protocols).

Here are my main recent works-in-progress:

• Modular Organization Terminology
• Peer-to-Peer Digital Networking
• Agreement-Based Governance
• Shared Resource Development and Support System

^ Please note that I'm refactoring my "Conversation for Action" prototype as a component of that "SRDSS" system.

I also have some IMO relevant "back burner" projects including:

• Distributed Media Network Governance
• Open Intermedia Commons

[Edit]: My designs are intentionally generic, and some of them probably aren't appropriate for trying to develop an Open App Ecosystem right now. Also, I don't want to "clutter up" the Wekan much.

I may add one or more of the three most fundamental active projects--MOT, P2PDN and ABG-- to the Wekan. It depends on how strictly you want this OAE effort to be focused.