Should the SDO be open sourced ?

[furiousOyster]

COO, should we open source this thing ?

I think we should, as it would make improvements easier, no permissioning of teams, etc.

This system has very little value to our competitors, contains no sensitive info, and needs to be easily accessible by any external contractors we engage too.

[ScottMaxwellBTL]

Agreed. It will also allow others to propose new refinements to working, especially when they have access to their own deeply experienced Brians.

There are a few steps to do first though. Here's an initial bucket-list - there will be others and these may not be right so we'll need to work on it:

1. Fuller description of the principles behind SDO and what it aims to achieve. Should be standalone so we don't need to keep answering questions.
2. Description of what contributors can add to, and what is fundamental and shouldn't be changed. We have control via pull-requests anyway, but this will help a contributor avoid wasting their time.
3. Style Guide? We can let it evolve, but the style needs to be coherent across the whole thing.
4. License & Contributors Agreement.

Some of these we need to do anyway, so it might be an idea to test release it to contributors inside the BTL/Helix orgs first.