Encouraging more code paid for by the Council to be open source would be a good first step, but there are scenarios where the code can't be open-sourced and even opened source code requires a certain level of technical ability to be able to audit/check.
@memespring's talk at OSCON 16 is a good backgrounder on these issues, and maybe his idea for Gherkin tests as more-user-friendly ways to audit code is a good example to pick at?
Prompted by this NY Times article - Showing the Algorithms Behind New York City Services, what could/should we do to improve the transparency of the software systems that affect citizens.
Encouraging more code paid for by the Council to be open source would be a good first step, but there are scenarios where the code can't be open-sourced and even opened source code requires a certain level of technical ability to be able to audit/check.
@memespring's talk at OSCON 16 is a good backgrounder on these issues, and maybe his idea for Gherkin tests as more-user-friendly ways to audit code is a good example to pick at?