search

OpenDataServices / developer-docs

Documentation about how we get our work done. For internal use, but happy to share
Other
1 stars 0 forks source link

Where is our client specific code? #8

Closed Bjwebb closed 8 years ago

Bjwebb commented 8 years ago

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".

Bjwebb commented 8 years ago

The other advantage to having our own forks, as we've seen with OCDS and NRGI is: 1) Being able to set up test/build services like requires.io and Travis without badgering people for permissions 2) 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!)

Bjwebb commented 8 years ago

We may want to add a link to this tip for pushing to two git remotes - https://github.com/OpenDataServices/developer-docs/issues/38