You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this section is useful as it is, but I think maybe "our code" (code we're responsible for building, and possibly maintaining) is in our client's organisations. Maybe we want a policy of always maintaining forks in our organisation, so that people can easily find "our code".
The text was updated successfully, but these errors were encountered:
The other advantage to having our own forks, as we've seen with OCDS and NRGI is:
Being able to set up test/build services like requires.io and Travis without badgering people for permissions
Deploying code to our servers from repositories we control (risk of malicious activity is relatively small here, but I think there's a very real risk of people accidentally breaking stuff!)
https://github.com/OpenDataServices/developer-docs/blob/master/code-checklist.md#our-codeprojects-should-be-in-version-control-and-present-links-to-issue-trackers-and-source-code
I think this section is useful as it is, but I think maybe "our code" (code we're responsible for building, and possibly maintaining) is in our client's organisations. Maybe we want a policy of always maintaining forks in our organisation, so that people can easily find "our code".
The text was updated successfully, but these errors were encountered: