Alternative version control repositories
Propose that options in addition to Github are mentioned....
Principles guiding the choice of code repository for publicly-funded software:
* repository provides full public access to source code, to promote discovery and re-use
* respository software support government standards for accessibility for a full range of users
* repository software is itself free code, with no proprietary dependencies, so a user can access it without being required to use any proprietary software, either directly or indirectly
* repository software implements all relevant open standards
* respository may be self-hosted by the project or department developing it, or another public organisation, or a gratis public service hosted by an external provider
* projects and the repository they are using should be listed on a regularly-updated list of free code projects used across all-of-government, to increase standardization and reduce unnecessary duplication of effort
Cam Findlay started a proposal Mon 4 Apr 2016
Code release should occur in a publicly open repository without imposing any particular technologies or locations. Closed Tue 12 Apr 2016
Reasonable agreement here that we should keep specific technologies outside the NZGOAL_SE and focus on principles that lead to selection of a suitable release space (however only 42% voted can this be considered "passed"?). There are some further spin off suggestions (summarised at top of thread). We may run follow up polls on each of these items (or split off into own thread for longer form discussion).
Agreement means that you'd like to see the policy wording changed to indicate that the desired behaviour here is release of code in an open and public digital space. This does not include what technology platform to use, nor where this is located online (this would be up to the agency to decide though there might be guidance given outside the NZGOAL-SE).
|Agree - 10|
|Abstain - 10|
|Disagree - 10|
|Block - 10|
Mon 4 Apr 2016
I think we should agree that FOSS code should be managed using git, but the repository through which it is shared can be selected (or there can be multiple - see git mirror). Perhaps projects need to register their location somewhere centrally...
Mon 11 Apr 2016
I don't think general policy statements should advertise US-based corporations whose website uses a number of proprietary components (ie GITHub). If specific examples are given they should be chosen from among those that use only free code components