search

TOMP-WG / TOMP-API

Transport Operator to Mobility-as-a-Service Provider-API development for Mobility as a Service
Apache License 2.0
100 stars 41 forks source link

Suggested implementation of working group structure and license #68

Open ro5k0 opened 5 years ago

ro5k0 commented 5 years ago

Here are some examples of software communities who have a centralised but open source approach to contribution and management:

Django

Apache

Open JS

Please add other examples that you see as being fitting to the discussion of how to define the working group as a future organisation.

I personally feel the above three examples give a solid foundation on which to base our working model, our governance, and our licensing.

Martijnvdlinden commented 5 years ago

Input from meeting 13-11-2019:
https://www.apache.org/licenses/LICENSE-2.0

Martijnvdlinden commented 5 years ago

https://tldrlegal.com/

ro5k0 commented 4 years ago

https://docs.brew.sh/Homebrew-Governance

ro5k0 commented 4 years ago

To add to the above we also need to agree on a CLA. Again the Django Software Foundation has quite a robust example of these for both a person and a corporation. I propose we adopt this for our purposes. https://www.djangoproject.com/foundation/cla/faq/

ro5k0 commented 4 years ago

Having been through the https://tldrlegal.com/ site I believe the Apache 2.0 license is the best option for what we need.

https://tldrlegal.com/license/apache-license-2.0-(apache-2.0)

The main discussion point for me would be the ability for a user or organization to sublicense the API. I think we need to clarify what that means to the WG.