chore: Copy over English text to be translated

fr/1_A_propos.md

@@ -0,0 +1,199 @@
+# DRAFT Terms of reference
+
+## Preamble
+
+On December 14, 2017 the Government of Canada Enterprise Architecture Review Board made a decision to “use open source tools as key components of its technology eco-system” and “support the creation and adoption of open source throughout their practice, resulting in a robust open community within the GC.”
+
+As such, the Secretary of the Treasury Board of Canada established the Government of **Canada Chief Technology Officer Open Source Advisory Board (CTO-OSAB)** as a forum for discussion of the sustainable adoption of open source across the government.
+
+## Background
+
+The CTO-OSAB aims to leverage the knowledge of internal and external subject matter experts to provide advice to senior technology leaders across the GC on the most effective approach to implementing an integrated eco-system of open source
+and closed source technology.
+
+Given that the adoption of open source tools is new across the GC, establishing a forum for dialogue provides a formal structure for regular, two-way communication between the Government and its key open source stakeholders. This process is designed to achieve real gains in transparency, accountability, and participation, while supporting the adoption of the right tools at the right time.
+
+## Effective Date
+
+February 15, 2018
+
+## Operations
+
+_Governance_
+
+The CTO-OSAB is responsible for providing advice to the GC Enterprise Architecture Review Board (GC EARB) on open source projects, open standards, procurement of open source tools, and practices for implementing a more open
+culture.
+
+The advisory board will be co-chaired by the GC CTO and a private sector executive dedicated to the evolution of open source tools within Canada.
+
+General membership will be limited to a maximum of twenty-four members to ensure the most productive discussion possible. Twelve spaces will be provided for both GC and non-GC members. Non-GC members can consist of industry, civil society, academic, and government representatives.
+
+Application for general membership will be submitted to and determined by co-chairs. There will be a one-year term limit for both general membership and the industry co-chair. The GC CTO, or pre-determined delegate will be made available on an on-going basis for this advisory board.
+
+All meetings will be open for anyone to attend. All resources will be
+shared through GitHub which is open to non-GC members.
+
+_Frequency_
+
+The CTO-OSAB meets the third Wednesday of every month, with the option for the committee to meet more frequently as required.
+
+_Working groups_
+
+Domain specific working groups will be established on an as needed basis to manage the effective operation of open source tools within the government. Each working group consists of a lead responsible for reporting back to the CTO-OSAB on a quarterly basis through a written and/ or verbal report. All reports will be made publicly available.
+
+_Location_
+
+Unless otherwise agreed, the room for in-person participation is in Ottawa.
+
+_Participation_
+
+Recognizing that membership will include members not located in Ottawa, the
+Treasury Board Secretariat (TBS) will arrange for remote participation via
+teleconference or
+The CTO-OSAB is responsible for providing advice to the GC Enterprise Architecture Review Board (GC EARB) on open source projects, open standards, procurement of open source tools, and practices for implementing a more open
+culture.
+
+The advisory board will be co-chaired by the GC CTO and a private sector executive dedicated to the evolution of open source tools within Canada.
+
+General membership will be limited to a maximum of twenty-four members to ensure the most productive discussion possible. Twelve spaces will be provided for both GC and non-GC members. Non-GC members can consist of industry, civil society, academic, and government representatives.
+
+Application for general membership will be submitted to and determined by co-chairs. There will be a one-year term limit for both general membership and the industry co-chair. The GC CTO, or pre-determined delegate will be made available on an on-going basis for this advisory board.
+
+All meetings will be open for anyone to attend. All resources will be shared through our GitHub page which is open to non-GC members.
+
+ _Decision-making_
+
+As this is an advisory board, there will be no formal decision making rules. However, consensus on reports provided to EARB will be encouraged.
+
+_Agenda-setting_
+
+The Chairs are responsible for determining each agenda with input from advisory board members. Agendas will be circulated to members for comment prior to the meeting, along with any documents or information to be discussed during the meeting. The Chairs will amend the agenda if necessary and circulate a final agenda prior to the meeting. Regular meetings allocate time for members
+to raise off-agenda items. In general, decisions should not be made on off-agenda items, unless agreed by consensus.
+
+ _Language_
+
+Members may express themselves in either English or French. All meeting materials will be made available in English and French.
+
+_Non-member attendance_
+
+Advisory board meetings will be open to the public. Non-members are encouraged to attend advisory board meetings to listen to the discussion as well as ask questions.
+
+**Mandate**
+
+The CTO- OSAB supports the efforts of the GC EARB to ensure the consideration of business and enterprise priorities related to the use of open source. As such, it will help the effective implementation of the Government of Canada IT Strategic Plan (strategic plan) to improve service delivery for clients and Canadians.
+
+**Responsibilities**
+
+The CTO-OSAB will be responsible for:
+
+* Providing advice on the benefits, advantages, challenges, and use of open source at an enterprise level.
+* Providing input on the anticipated use of open source tools across the government.
+* Creating awareness across Canada, government and industry related to the use of open source in combination with the GC’s existing tool set, including closed source tools.
+* Providing input on open source tools being assessed by the GC EARB.
+* Supporting the proliferation of open source within the GC and across Canada by leading or joining the Open Source Communities.
+
+**Current Membership**
+
+Co-Chairs:
+
+* Chief Technology Officer, Treasury Board of Canada Secretariat; and
+* Jack Gulas, Owner, YoppWorks
+
+GC Members:
+
+* Lena Trudeau, Canadian Digital Service
+* Melanie Robert, Treasury Board Secretariat
+* Christopher Allison, Treasury Board Secretariat
+* Denis Skinner, Public Service Commission
+* Gabrielle Cosette, Shared Services Canada
+* Stephane Dufour, Statistics Canada
+* Peter Silva, Environment
+* Jacob Raffoul, Employment and Social Devlopment Canada
+* Guylaine Carrière / Caroline Bessett, Shared Services Canada
+* Mathieu Fortin, Shared Services Canada
+
+ External members:
+
+* Paul Bellows, Yellow Pencil
+* Jean-Noé Landry, Open North
+* Robin Galipeau, Open Plus
+* Marc Pageau, Oproma
+* Dave Buchanan, Breqwatr
+* Dr. Andrew Pelling, University of Ottawa
+* David Nevins, Redhat
+* Mike Gifford, OpenConcept
+* Harsh Sabikhi, GitHub
+* Noureen Syed, Microsoft Open Source Lead
+* Rodney Helal/ Fil Galiardi, Cloudera
+* Shermineh Salehi Esmarti, Consultant
+* Erin Kennedy, Robots
+
+**Working Group: Rules**
+Responsible for reviewing, assessing, and making recommendations related to open source:
+
+* Policy
+* Legal
+* Licence
+* Procurement
+* Governance
+
+Participants
+
+* Co-Lead: Marc, Oproma
+* Heather Laird, Treasury Board Secretariat
+* Rodney, Cloudera
+* Noureen, Microsoft
+* Robin, Open Plus
+* Christian, Public Service Commision
+* Mike, Eclipse Foundation
+* John, Canadian Digital Services
+* William, Employment and Social Development Canada
+* Ranjan, Canada Border Services
+* Noel, Treasury Board Secretariat
+
+**Working Group: Tools**
+Responsible for determining approach and contributing to:
+
+* Tech stacks
+* Commercialization
+* Dev/ops
+
+Participants
+
+* Co-chair: Jack Gulas, Eclipsys
+* Sebastien Lemay, Treasury Board Secretariat
+* Christopher Allison, Service and GC 2.0 Policy and Community Enablement Division
+* Christopher Jaja |CIOB
+* Ross Thompson, CIOB
+* Rodney Helal, Cloudera
+* Noureen Syed, Microsoft
+* Marc Pagneau, Oproma
+* Michael Nguyen, Github
+* Olivier Dzomo, Public Service Commission
+* Members of Stéphane Dufour's team, Statistics Canada
+* Dave Buchanan, Breqwatr
+* Joel, Open Plus
+* Will Stevens, Cloudops
+* Ross Clarke, Canadian Food Inspection Agency
+* Nick, Immigration, Refugees and Citizenship Canada
+* Reginald, Statistics Canada
+
+**Work Group: People**
+Responsible for developing engagement activities related to the improvement of:
+
+* Community
+* Culture
+* Developer retention
+* Development methodology
+
+Participants
+
+* Co-lead: Christopher, Service and GC 2.0 Policy and Community Enablement Division
+* Co-lead: Richard, Red Hat
+* Christopher, CIOB
+* Erin, Robot Missions
+* Harsh, GitHub
+* Sang, Open Plus
+* Shermineh,
+
+**Terms of Reference will be reviewed and updated annually in Q1.**

fr/2_Analyse_rentabilisation.md

@@ -0,0 +1,147 @@
+# Business Case
+
+## Phase 1: The Strategic Context
+
+### Business Needs and Desired Outcomes
+
+#### Strategic Environment
+
+##### Organizational Overview
+
+##### Business Need
+
+##### Drivers for Change
+
+##### Business Outcomes
+
+#### Strategic Fit
+
+#### Detailed Description of the Business Need
+
+##### Problem/Opportunity Statement
+
+##### Prioritized Requirements (High Level)
+
+##### Assumptions
+
+##### Constraints
+
+##### Dependencies
+
+#### Scope
+
+##### Boundaries
+
+##### Stakeholder Analysis
+
+## Phase 2: Analysis and Recommendation
+
+### Preliminary Options Analysis
+
+#### Evaluation Criteria
+
+#### List the Possible Options
+
+##### The Status Quo
+
+##### Describing the Option
+
+#### Screening of Options
+
+#### Rationale for Discounted and Viable Options
+
+### Viable Options
+
+#### Alignment
+
+##### Strategic Alignment
+
+##### Alignment with Desired Business Outcomes
+
+#### Costs
+
+#### Cost-Benefit Analysis
+
+#### Implementation and Capacity Considerations of Viable Options
+
+##### Contracting and Procurement
+
+##### Schedule and Approach
+
+##### Impact
+
+##### Capacity
+
+#### Risk
+
+##### Option Risk Summary
+
+#### Risk Register
+
+### Benchmark
+
+### Policy and Standard Considerations
+
+### Advantages and Disadvantages
+
+## Business Case Phase 3:
+
+> Reference materials below
+
+## Purpose
+
+There needs to be a business value for CIO's in why we are moving to open source
+There is a level of awareness required
+
+## Issues
+
+Dev/ops
+
+## Analysis
+
+## Options
+
+## Recommendations
+
+Communities:
+Conferences
+Meet ups
+Git
+Open Government
+Culture change - myth busting
+
+Developers:
+Skills and training
+Working habits and tools
+Recruitment
+
+OS
+Commercialization: - comes after reference architecture and the what
+Committers
+Enteprise Support
+Distributions
+License Models
+
+OS Technologies and Stacks:
+Reference Architectures
+Apps / Programming Languages
+Data / AI / Machine Learning
+Reactive
+Microservices
+COTS with OS
+
+Development Methodology:
+Agile
+Lean
+UX
+Release and Support
+
+Case Studies
+Customer references
+Use cases: Public Sector IT Efficiency & Good Government (Prevent Fraud
+& Abuse, Deliver Accurate Public Reporting, Citizen Engagement with Social
+Media, New Digital Citizen Services)
+
+Procurement
+
+Next steps: https://github.com/canada-ca/Open_First_Whitepaper/blob/master/en/7_Next_Steps.md

fr/3_Inventaire_libre.md

@@ -0,0 +1,19 @@
+# Open Inventory
+
+Welcome to the Open Source Project Inventory. We are trying to understand all
+of the open source projects that are taking place across the Government of
+Canada. If you are working on a project, please add it to this list. We do not
+want to be too prescriptive at this point, so we have not created a controlled
+vocabulary for domain, however, this list will help us work towards that.
+
+Please submit your project by pull request, an admin will review and approve.
+
+You may also check out the [Open Resource Exchange](https://github.com/canada-ca/ore-ero)
+Thanks!
+
+| Activity/Project | Lead|Contact| Link to Resource |Domain|
+|------------------|-----|-------|------------------|------|
+|CKAN (Open.Canada.ca)|Treasury Board Secretariat| Christopher Ja Ja ([email protected])|https://github.com/open-data | Data Catalogue |
+|MetPX | Shared Services Canada (HPC) | [email protected] | https://github.com/MetPX | Weather Data Communications |
+|Web Experience Toolkit|Service Canada|Mario Bonito ([@masterbee](https://github.com/masterbee))| https://github.com/wet-boew/|Web front-end framework|
+|  |  |  |  ||