Loomio

Digital Development Principles and Licensing

M
Max Public Seen by 15

With looking at the direction ahead for community and alignment of our values and purpose to be aligned with our code and development practices ... it is time we discuss and decide licensing and principles we approach ALL technology projects via Solutions for Humanity Inc.

I have discussed generally with the devs before bringing this to members for a formal vote, to make sure my thinking around values is aligned by their thoughts on this also; especially, purpose driven contributors.

M

Max started a proposal Mon 18 Jan

Align with Principles for Digital Development Closed Sun 31 Jan

Outcome
by Max Sun 31 Jan

Proposal to align with the general guidelines of the Digital Development Principles was discussed and passed by member, with no blocking votes.
Has been marked for review in round 6 months, and see how they are working for us, how we align, etc.

Ref: https://digitalprinciples.org/principles/

We are working for a better future for people and planet - and we should align with the principles developed for that sector. I believe that a very good guideline for us to write into the rules of how SFH Inc works with the technology we develop and the community and partners we work with.

There are of-course ethical AI guidelines and other things that are "technical guides" for certain projects (like isgood.ai), but the principles linked are more as something that are broadly understood and applied on how we operate as members, community and coop.

The sooner this can be reviewed and discussed for agreement the better :)

Agree - 5
Abstain - 0
Disagree - 0
Block - 0
5 people have voted (100%)
M

Max
Agree
Mon 18 Jan

I want to be absolutely clear on aligning purpose and ways we approach our tech work, and many experts have worked on creating these principles to help guide us. If there is some conflict in the future, we can work with that as needed ... aligning with the principles are not hand-cuffs 馃槈

JB

Judith Baeta
Agree
Mon 18 Jan

Great! @Max is your suggestion, assuming the result of the vote is favourable, to "audit" or review how we are currently doing things to ensure we align to these Principles, or an alternative way to incorporate them into our organisation?

G

Gareth
Agree
Mon 18 Jan

Following best practice and including users is always a good idea

S

Simon
Agree
Fri 29 Jan

These principles seem sensible.

M

Max started a proposal Mon 18 Jan

Open Community Licence Where Applicable Closed Sun 31 Jan

Outcome
by Max Sun 31 Jan

Proposal was passed, with no blocking votes, that for the near future we adopt the following approach for isgood.ai (only current project):

  1. WebApp / Front-end code ->聽GNU GPLv3

  2. Backend / API functions and integrations layer -聽GNU AGPLv3

  3. Data-wrangling, streaming & open-scripts -聽GNU AGPLv3

  4. Data-platform data-structures, systems, R&D & scripts - closed source & internal private repos


Has been marked for review in round 6 months, and see how it's working for us, how we align, etc.

Aligning with our purpose of doing good, and also as per our manifesto and the "Principles for Digital Development" we should consider to operate as an open, collaborative and transparent first and whenever possible organisation. This is also regarding our code.

This does NOT include all of our platform scripts, especially when there is a risk to either our #techforgood purpose or good for people and planet (eg. being used for evil). It also does not reduce our ability to have certain code/functions/systems being patented, IP held, or never making public certain tech or code when it is not considered to be in the best public interest.
Where it does apply, is when there is overall benefit of doing so, either for our #techforgood purpose or good for people and planet.

The proposal is, that for the near future we adopt the following approach for isgood.ai (only current project):

  1. WebApp / Front-end code -> GNU GPLv3

  2. Backend / API functions and integrations layer - GNU AGPLv3

  3. Data-wrangling, streaming & open-scripts - GNU AGPLv3

  4. Data-platform data-structures, systems, R&D & scripts - closed source & internal private repos

Again, if you are able to consider, discuss and decide ASAP, it will help move things faster for our devs, DS and community contributors .... as well as our OKRs and roadmap planning.

Agree - 4
Abstain - 0
Disagree - 0
Block - 0
4 people have voted (100%)
M

Max
Agree
Mon 18 Jan

I've been thinking about this a LOT .... and believe this is the right thing to do ... both for our benefit, and for the impact we can make.

JB

Judith Baeta
Agree
Mon 18 Jan

Thanks for sharing the resources for better understanding. Your approach and thought process seems very reasonable to me and I am happy to go ahead with this. :)

G

Gareth
Agree
Mon 18 Jan

Agreed after chatting with Max to ensure that this being open where it helps isgood (e.g. customer interactions by easier API integration) and does NOT include any core IP including the R&D code. Keep the core IP private and secure is critical.

M

Max Tue 19 Jan

additional comment in side chat about this, copying across for sake of transparency:

Reason being is that pretty much everything outside of the backend DS platform is pretty standard functionality... stuff like APIs would be public to enable more integrations and dev contributions ... webapp is open source anyway .... and opening up what is NOT sensitive enables us to have a lot more contributors and access to many initiatives we wouldn鈥檛 have if 100% closed.

Important thing is that we are not looking at opening anything that is sensitive or related to our IP for the platform design (or R&D stuff).

With the licensing it forces anyone who uses it to have the same license and state all changes on anything served over network.

What is your main concern about this?

M

Max Fri 22 Jan

While we have a majority, we do need to wait for Simon to come back from holidays, in case he has a blocking vote.

M

Max Thu 28 Jan

have re-opened, awaiting Simon to return

M

Max Sun 31 Jan

Now we have agreement of this we need to put this as part of our handbook/documentation and content, to help keep us aligned and on track ... so, we need to look at this and where the different bits of guiding info need to go and how we use it to underpin our values and modus operandi.

I will add an item to our "ideas and feedback" backlog in clickup.

M

Max Thu 4 Feb

moved discussion and decisions to SFH Community Public Forum

M

Max Fri 2 Jul

This was marked for review now ..... and still seems a solid approach ... will gather strength and come into it's own as we go.

Need to be VERY STRICT about "secret" type DS access, to the system design AND the code itself .... as that is our trade secrets, and we need to make sure it is not stolen and used against us or others who are trying to do good in the world.