March 20th, 2019
- Welcome
- OSS Best practices and Lessons learned
- Update on Guidelines
- Update: Rules Working Group
- Update: People Working Group
- Update: Tools Working Group
- Roundtable
Attendees
- Marc Pageau, Oproma
- Dugald Topshee, Department of Justice
- Gabriella Signorini, TBS
- Dave Buchanan, Breqwatr
- Robin Galipeau, Open PLus
- Paul Jackson, ISED
- Andre Whittingham, TBS
- Guillaume Charest, TBS
- Ashley Casovan, TBS
- Daniel Buijs, Health Canada
- SSC
- Mark Bohannon, RedHat
- Jim Cowie, ESDC
- Intel
- Barry Kong, TBS
- Marco Mannarino, Cloudera
- Mike Cardy, Redhat
- Martin, SSC
- Vincent Fortier
- Philippe Martin, Cloudera
- Mathieu Fortin
- Mike Gifford, OpenPlus
- Harsh, Github
- Reg Maltais, StatsCan
- Travis Broughton
- Chris Allison, CSPS
To view this presentation, please consult our Issues page
Questions
- When you mentioned that the department of defence said that it was ok using Open Source Software, were there any concerns about the legal implications?
- They put in place the right processes to address questions by creating an FAQ. There was also a collaborative effort from lawyers to respond to any concerns.
- Is purchasing a subscription the only alternative to purchasing a perpetual licence?
- Purchasing a subscription is the most viable way in the context of the US government
- Does that imply that the subscription/service comes only from the company that released the software?
- A subscription model kind of implies vendor lock-in, which is one of the risks of proprietary software that open source is supposed to address
- Is there anything stopping someone from switching from RedHat to CentOS?
- Do you think government has any unique opportunities for engaging and supporting open source? If so, what are they? Have you seen any examples that we should see?
- Release often
- Contribute back and engage in the open source community you are working with
- Start small, socialize it in your organization
- Find test beds
- Forking projects= risk
- GoC could contribute back and participate in many roles in the linux foundation - in fact, SELinux was a heavy US government contributor.
- We should consider defining open source community (where software technology is focus, purpose, objectives) versus "open community innovation practices" that would ideally be formed within the GoC and handle how collaboration is done across departments using OSS communities’ software
- We should look into setting up a CCLA (corporate committer license agreement) for the GoC for contributing back to the open source communities which you engage with
- We are requesting you to provide feedback on the following guides:
- We are trying to build off what we built in Appendix C on the Directive on the Management of IT
- Feedback is due by end of day March 27th
Questions/comments
- In regards to contributing to an open source project with a Government of Canada email, how will we manage this?
- Values and Ethics could help with this
- Align with social media
- Science-based Departments have scientific integrity policies that apply to the work product of their scientists. Most of the language is oriented primarily toward patent and commercialization, but the policy is oriented specifically toward intellectual property
- Some employers are changing their HR policies to contribute to OSS
- Redhat Legal presentation
- Working on the guidelines
- OGP Hackathon
- Created a project plan, confirming participation, addressing business challenges that have come up
- Working on reference architecture
- Assessing projects like Drupal
- Reach out to Values and Ethics about email
- Ask Anthony Pane to review to comment
- Share link to OGP Hackathon planning documents