Guillaume Charest

Very good point, we already have a lot of work being done around proprietary software licence management and "asset" tracking. I'm pretty sure we could leverage current practices for the...

Yes, @jeffmcaffer presentation was really putting a lot of importance to removing barriers and automating as much as possible the workflow for the developers. Not doing so basically lead to...

Very good question and I unfortunately can't answer myself.

So, I've been going over other Standard and although there are mentions and references to Official Languages Act and policies, they do not directly reflected them in the requirements sections...

@uferrpi merci pour ces ajouts! Je pense que c'est en effet un avantage au même titre que d'inclure la sécurité et l'accessibilité par défaut. En définissant adéquatement nos balises, il...

Yes, I think we need to work some kind of graphics... The decision tree is meant to go from 80% scenarios you should be able to use OSS under any...

We probably should add some nuance as well to help teams realize what would constitute a reason that the source code could not be published, linking to the conditions we...

Absolutely! Yes, definitely need graphics... Also, clearer introduction might help in the meantime!

Ah yes, the decision tree was more about the software used inbound. A decision tree should probably be done for licences applied to GC projects :thinking: For example, see this...

In other words, if you use without modifications (or any derivative work), you shouldn't be worried about from the OSS licence perspective in most cases as long as it is...