Who is working now on Open Apps Ecosystem?

Great !

Hi Marc,

If you agree with this way of doing, we need developers to create plugins (addons) on open apps to make the communicate with the API (Communecter's API for a start). This is a huge work, and I need to be in touch with theses people to build an API capable to communicate well with the plugins of the apps.

So if I understand, this is what you want to build a team for? I will volunteer to work on apps that I am already involved in and know the code. In general, I'm trying to slowly get out of coding in my life, so I want to work only on things where I can do it much quicker than someone else because I already did work on the original app for example. I also want to minimize having to learn new technologies if I can, getting too old. :) So I realize this is not much help, but maybe a little. :)

I'm working to set up an SSO Identifiant Provider and a common menu for the different apps of the ecosystem. As we though that for beginning we could use Communecter.org for dealing with the working groups, the common menu, the common database and the APIs to communicate with other apps, I can work on this task in collaboration with the Communecter developers team.

I don't know if I agree yet, would have to see how it will work. I am hesitant to create a center inside one of the open apps, I fear people will not see it as independent enough to make connections. All the open apps need to actually be peers in the ecosystem, in my opinion.

SSO is sorely needed, and a common menu can be very useful for groups who use different apps. I would be very hesitant to use Communecter directly though, no matter how good it is. Or are you forking it and taking pieces of the code that will be an independent app just for the open apps ecosystem?

Let's also figure out what would be needed in the common database and how to minimize that.

The discussion with Tibor on Tuesday will be at least partly about api's, can you come to that?

And/or - maybe all the technical participants should be part of a discussion of how to architect the peer to peer connections of open apps, even if just to start. This would be beyond the SSO itself.

I know you are jumping in, which I think is really really really great (did I say how great that is?? :) ), and I'm sorry if I am slowing things down, but I also think we need to consider together some of the main architectural decisions, or it risks not gaining acceptance.

What do you and others think?

want to build a team for?
Yes, we need specialists for each app
Thanks for your proposal to help for the apps you know

create a center inside one of the open apps
If we have a common menu, we need a common database to store it. For a start, I suggest to have it on only one server. After, if it works well and people are using it, we could work more to make this database P2P.

We need a platform where people can complete their profile, join groups, be geolocated on a map, have notifications and find other contributors or working groups. Communecter is well designed for managing all that, especially the groups and the relations between them. So I thought it could be the first platform to integrate in the ecosystem. Later, we could add others.

But I agree with you, we could think to create an independent database and software, only for connecting and communicating (via APIs) between the platforms (Communecter as the first one) and the others apps. This software would be the core of the Open App Ecosystem.

Forking Communecter would be a bad idea because we will have difficulties to integrate further enhancements. But Communecter can already communicate threw APIs.

I'm going to change strait away the technical document : https://docs.google.com/document/d/1lhDJgyPB1f3zyLz3Zy626GEvxchwks0yDo-aA3LxSRI/edit

Thanks @lynnfoster for this analyses (tell me what you think about this new proposal), others mustn't hesitate to give their opinion !

If we have a common menu, we need a common database to store it. For a start, I suggest to have it on only one server.

I'm totally fine starting with a common database on one server for things that are ecosystem data, as needed. Ah yes, the money... I am not too worried in the short term, although it is a question for sure as we go forward and grow.... but for later when we have that "problem". :)

@bobhaugen I updated your thread, tell me what you think about that.

I guess the rules to make us work together are :
* If you do an ACTION related to open app ecosystem, add it in the wekan
* This ACTION must be understood in less than 30 sec
* For each ACTION it exists a "GUIDE : How to contribute to the action"
* This GUIDE is really easy to understand and enables anyone to contribute to the ACTION

Is it OK for you all ?

Mostly ok with me, but I don't know how you would tell if "This ACTION [could] be understood in less than 30 sec". I'd make it more like a suggestion, "Please make it as easy to understand as you can." But that's also just a suggestion, do what you will.

@bobhaugen I created a thread about it though. Seemed for me quite good to make everyone agree with it ;)

If I was new to this set of conversations, I would not respond well to all of those MUSTs. Do you understand why?

I don't understand what you mean.

Ah, good, you changed the one that bothered me the most...thank you.