Source code/project catalogue (discovery tool)
Source code repositories are good for devs - bit not for managers/policy people looking to make strategic decisions around software purchase or development. Like open data, delivery is easy - stick it on the web in a suitable format :-)
The critical precursor - a discovery capability (not dev oriented) is required. This could be a standalone catalogue of relevant projects providing open source for govt initiatives, or perhaps incorporated in data.govt.nz.
However it is done, a suitable catalogue or discovery portal focussed on projects rather than code should be established & NZGOAL-SE should mandate its use.
This could be established very soon, & easily, & it could be populated with past & current projects.
Such a catalogue should link to the dev & home pages of software projects which have been reused (Silverstripe, Koho, Moodle, Alfresco, etc all spring to mind) as well as the local projects which reused them.
Cam Findlay started a proposal Wed 13 Apr 2016
Specific discovery tools should not be included in NZGOAL-SE as this would be out of scope (except to reference them in subsequent guidance notes). Closed Fri 15 Apr 2016
Appears an acceptable and workable way forward on this appears to be to look at specifics in future guidance notes, with a more principled reference in the policy itself. :thumbsup:
There has been discussion here about code discovery tools and their place in NZGOAL-SE. I think we have some agreement that we should keep NZGOAL-SE scope to the licensing aspect and would like to take a quick poll on this to drive further discussion.
|Agree - 7|
|Abstain - 7|
|Disagree - 7|
|Block - 7|
Thu 14 Apr 2016
I do think it's within the scope to say "the repository, which will be kept up-to-date must be registered with the provided central project directory"... without needing to define that solution.
Fri 15 Apr 2016
I concur with Dave Lane. But require entry in an audit-able and publicly accessible authoritative registry (without specifying software) as minimum requirement of publishing. Use similar language as in the versioned repository discussion.