6
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − + − − * Enable teams across the entire government to leverage best practices and tools for the development and reuse of source code in the GC. − ** Smaller departments may not have the financial resources to host and maintain such a development environment; by providing a common place for all to work together, we would be generating economies of scale beyond single departments. − − * Automate and scale CI/CD with automation and leveraging corporate level tools like automated scanning of known security vulnerabilities and legal compliance. − * Enterprise standard use of open source components (inbound single version of package) − * Set enterprise wide policies as well as department specific policies (prohibit or authorize use of AGPL, MIT, exceptions, etc.) for software inbound. − * Identify duplicate custom code, reuse existing code and create communities around projects across departments. E.g.: meeting room reservation application from department A could be leveraged across the government and potentially even published as open source. Line 47:
Line 39: + + + + + +
no edit summary
<code>''Explain the business problem or opportunity that needs to be solved in one sentence.''</code>
<code>''Explain the business problem or opportunity that needs to be solved in one sentence.''</code>
Current development of Government of Canada computer programs and solutions rely on mixed practices and version control systems specific to each department and agency. By providing a common place to develop and share development projects and solutions, there is an opportunity to:
Current development of Government of Canada computer programs and solutions rely on mixed practices and version control systems specific to each department and agency. By providing a common place to develop and share development projects and solutions, there is an opportunity to reuse the same platform across departments in most cases.
Source code developed by GC employees (software engineering, scientists, researchers,...) to support key programs needs to be available for reuse across departments, and to be scanned for security vulnerabilities.
Source code developed by GC employees (software engineering, scientists, researchers,...) to support key programs needs to be available for reuse across departments, and to be scanned for security vulnerabilities.
* Reduce costs maintenance cost of source code repositories
* Reduce costs maintenance cost of source code repositories
* Improve continuous integration (CI/CD) practices
* Improve continuous integration (CI/CD) practices
* Enable teams across the entire government to leverage best practices and tools for the development and reuse of source code in the GC.
** Smaller departments may not have the financial resources to host and maintain such a development environment; by providing a common place for all to work together, we would be generating economies of scale beyond single departments.
* Automate and scale CI/CD with automation and leveraging corporate level tools like automated scanning of known security vulnerabilities and legal compliance.
* Enterprise standard use of open source components (inbound single version of package)
* Set enterprise wide policies as well as department specific policies (prohibit or authorize use of AGPL, MIT, exceptions, etc.) for software inbound.
* Identify duplicate custom code, reuse existing code and create communities around projects across departments. E.g.: meeting room reservation application from department A could be leveraged across the government and potentially even published as open source.
The use of GCcode is aligned with the GC Digital Standards "Work in the open by default" and "Collaborate widely".
The use of GCcode is aligned with the GC Digital Standards "Work in the open by default" and "Collaborate widely".
