|
5 | 5 |
|
6 | 6 | By including a ``publiccode.yml`` file in the root of a repository, and populating it with information about the software, technicians and civil servants can evaluate it. Automatic indexing tools can also be built, since the format is easily readable by both humans and machines. |
7 | 7 |
|
8 | | -``publiccode.yml`` is mandatory for all public software developed in Italy, according to the national [guidelines](https://docs.italia.it/AgID/linee-guida-riuso-software/lg-acquisizione-e-riuso-software-per-pa-docs/): this enables the Developers Italia crawler to build the national [software catalog](https://developers.italia.it/). The standard is designed to be interoperable internationally, thus the country-specific keys are separated by the core part and are defined in specific sections that each government can rule. |
| 8 | +``publiccode.yml`` is mandatory for all public software developed in Italy, according to the national `guidelines <https://docs.italia.it/AgID/linee-guida-riuso-software/lg-acquisizione-e-riuso-software-per-pa-docs/>`__: this enables the Developers Italia crawler to build the national `software catalog <https://developers.italia.it/>`__. The standard is designed to be interoperable internationally, thus the country-specific keys are separated by the core part and are defined in specific sections that each government can rule. |
9 | 9 |
|
10 | 10 | Details carried by a ``publiccode.yml`` file include: |
11 | 11 |
|
12 | | -- title and description of the project or product (in one or more languages); |
13 | | -- development state (e.g., ``concept``, ``development``, ``beta``, |
| 12 | +- title and description of the project or product (in one or more languages); |
| 13 | +- development state (e.g., ``concept``, ``development``, ``beta``, |
14 | 14 | ``stable``, ``obsolete``; |
15 | | -- contacts of the entity who published the codebase; |
16 | | -- contacts of the maintainer, if any, including the expire date of the maintainance contract; |
17 | | -- information about the legal context for which the project or product was designed; |
18 | | -- dependencies. |
| 15 | +- contacts of the entity who published the codebase; |
| 16 | +- contacts of the maintainer, if any, including the expire date of the maintainance contract; |
| 17 | +- information about the legal context for which the project or product was designed; |
| 18 | +- dependencies. |
19 | 19 |
|
20 | 20 | and much more. |
21 | 21 |
|
22 | 22 | See also |
23 | 23 | ---------- |
24 | 24 |
|
25 | | -- [More information about software reuse](https://developers.italia.it/en/reuse) |
26 | | -- [publiccode.yml web editor](https://publiccode-editor.developers.italia.it/) |
| 25 | +- `More information about software reuse <https://developers.italia.it/en/reuse>`__ |
| 26 | +- `publiccode.yml web editor |
| 27 | + <https://publiccode-editor.developers.italia.it/>`__ |
27 | 28 |
|
28 | 29 | Table of contents |
29 | 30 | ----------------- |
|
0 commit comments