ePayments - Service Assessment
...make it quicker to roll out updates and improvements. Point 15 - Make all new source code open and reusable, and publish it under appropriate licences (or give a convincing...
...make it quicker to roll out updates and improvements. Point 15 - Make all new source code open and reusable, and publish it under appropriate licences (or give a convincing...
...code open and reusable- point 15 The service team should continue the work to open their source code. Testing the end to end service - Point 17 Ensure the service...
...panel were glad to see that improvements had been made since Alpha. The team have immediate plans to open up validation engine code, to support the external software providers, who...
...and constantly improving the service. A strong commitment to open sourcing the code (with all code being placed on Github), as well as to open data with each page being...
...place to make all new source code (or specific subsets of the source code) open and reusable. The panel expect evidence of this to be demonstrated at the beta assessment....
...code open and reusable The team have a plan to open source the subsets of the code they are able to. We encourage them to do this sooner rather than...
...also not passed point 8 – although there are plans to share code within DVLA, and the team expressed a willingness to make its source code open and reusable, there...
...understand and comment on. We decided to use Jupyter Notebook to document our experiments, because it allows us to write both code and free-form text, and expose the notebook via...
...follow-up post about how they’ve built RAP into their day-to-day working and what we’ve all learned from their experiences. DCMS DCMS were the first department who we collaborated with to...
...look for specific accessibility content issues. We wrote it in Python, as it’s a GDS-supported programming language, and structured the code in a way that allowed us to write and...