Guillaume Charest

You are correct, the Open Standard section has not yet been implemented. Very limited work has been done on that topic (although I know it's a very important one). Part...

Yes, very good point. Feature contribution Vs bug fix, documentation and others have different involvment levels. The process may need additional guidance for departments. Le jeu. 28 mars 2019 10...

Jeff McAffer comments/questions Contributors Licence Agreement: - Individual - Corporate Not every company will authorize individual contributions, only corporate. Opportunity to eliminate friction.

Joseph Potvin comments/questions Exec Director XAlgorithms: TBS IP policy defaults maps nicely to Fedora contributor agreement. Challenge: no one follows the policy. It's a confusing policy => copyright remains with...

Thanks @jtcowie ! Le ven. 26 oct. 2018 10 h 11, jtcowie a écrit : > CLA's appear to be a slippery slope where in some cases, prior to >...

So, just to continue the discussion here, we will need to look at both sides of this: * CLA to contribute to external OSS projects. * Whether we need CLA...

Valid points, I think we really are looking at a pilot project for now to manually point to GC projects or indeed packaged OSS in use one the GC. From...

It is important that as we choose our tools, platforms and solutions for our move to a more open government, we do so in line with our own policy direction....

Awesome! Really glad you find it useful! That book helped me get more comfortable but also really interested in the licencing questions in OSS.

Great points @NoureenS ! I think we need to enhance the security dimension. We've broken down 2 sections: [Work in the open](https://github.com/canada-ca/open-source-logiciel-libre/blob/master/en/guides/publishing-open-source-code.md#work-in-the-open) and [Releaseing a Legacy Application](https://github.com/canada-ca/open-source-logiciel-libre/blob/master/en/guides/publishing-open-source-code.md#publishing-a-legacy-application) (It's just a...