Coding in the open updates

[gyro2009]

No description provided.

[snyk-io-eu]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Licenses	0	0	0	0	0 issues
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[rockydevnet]

It maybe worth updating the open source governance check list (and/or referencing it somewhere in these docs):

[rockydevnet]

The Source Control Policy should also probably be updated to clearly indicate open by default, and provide links to the other relevant policy and guidance?

[nevillejrbrown]

Here's a few bits of feedback...

[nevillejrbrown]

This page needs to give advice on what license we should use if it's not being open sourced. I think the answer is don't give it any license, but I think this needs to be spelled out here somewhere.

[gyro2009]

I would always advise adding a license to your repository no matter where your coding just to give you that flexibility if you need to change the visibility. I will add something in :)

[nevillejrbrown]

But what if you specifically don't want to license it? This is possible, e.g. in the case of commercially sensitive contend. We need to keep that option open I think.

[nevillejrbrown]

Thanks for making the changes :-)

[nevillejrbrown]

Actually I think we need to resolve the licensing conversation. Do you want to discuss on a call?