[EPIC] As Open Data Hub maintainer I need to define guidelines for external developers so that their contributions run on and respect the updated architecture / infrastructure

[clezag]

External contributors are still developing on the old infrastructure model and outdated documentations.
We need to update/create new documentation and boilerplate that they can use.
We also need to update our contracts to reflect the new requirements.

[clezag]

@rcavaliere @sseppi

Do you have any technical requirements and specifications documents that you sent to contractors or use when publishing tenders?

[rcavaliere]

@clezag you can check for instance here: https://noi.bz.it/media/pages/ueber-uns/transparente-verwaltung/ausschreibungen-und-vertraege/bekanntmachungen-und-marktkonsultationen/fa260b3889-1729757743/241018_richiestaofferte_datacollectornadim_impact.pdf

[sseppi]

@clezag at the following link you find a typical document I create when I do a Market Research:

https://noi.bz.it/media/pages/ueber-uns/transparente-verwaltung/ausschreibungen-und-vertraege/bekanntmachungen-und-marktkonsultationen/b3acd78139-1729758417/2024-opendatahub-odps-dcatinterfacepoc-marketresearch.pdf

[clezag]

TODO: Documentation must be exportable as PDF, not only links

[clezag]

Putting blocked, because contingent on ongoing documentation revamp

[clezag]

Documentation site is now up for testing.

We are also in contact with a contractor that is developing a data collector using the new infrastructure, and we will use this project as a pilot to develop the documentation as things come up.

This is the technical documentation that we've shared with them: https://docs.dev.testingmachine.eu/data/development/intro.

We've also made some advancements on packaging the infrastructure as a local docker project.