Risultati
202 risultati
-
italia
Policy del catalogo del software open source di Developers Italia
Regole per la pubblicazione di software nel catalogo di Developers Italia. Questo documento si pone l’obiettivo di rendere più trasparente e condivisa la modalità di valutazione del software candidato ad entrare nel catalogo di Developers Italia ...
-
italia
Ammissione del software a catalogo
Nel catalogo del software di Developers Italia non sono ammessi:. I repository ospitati in uno strumento di code hosting non conforme ai requisiti espressi nell’allegato A delle linee guida. I repository che contengono:. software incompleto;. software non compilabile / installabile;. software privo di documentazione relativa alla compilazione o all’installazione;. software che non rientra nella definizione di cui all’art. 1.2 delle linee guida;. software che non raggiunge un livello sufficiente di unità funzionale. I repository che violano delle regole di diritto:. software privi di licenza aperta;. repository contenenti licenze tra loro incompatibili;. software che violano diritti di proprietà intellettuale o altri diritti di terzi;. repository con contenuti illegali, commerciali o che violano norme di legge. I repository contenenti un file publiccode.yml non valido:. non rispondente alle specifiche (descritte qui);. che non permette di capire lo scopo, le finalità e i requisiti del software;. I gestori della piattaforma Developers Italia si riservano il diritto di rimuovere dal catalogo i repository che violano queste regole. In caso di esclusione i gestori della piattaforma Developers Italia comunicheranno le motivazioni al gestore del repository attraverso i canali di comunicazione disponibili. A seguito della eventuale correzione delle violazioni segnalate e della relativa comunicazione ai gestori di Developers Italia, il software potrà essere incluso nuovamente nel catalogo ...
-
italia
Il Catalogo di Developers Italia
La seguente policy si applica all’inserimento di soluzioni software open source all’interno del catalogo di Developers Italia. Il catalogo di Developers Italia contiene due aree:. La seconda è dedicata a soluzioni open source, la cui titolarità sia attribuita a soggetti terzi, che potrebbero essere di interesse di una PA. L’aggiunta di software al catalogo avviene in automatico tramite una scansione periodica notturna di diverse fonti:. Gli spazi di code hosting inseriti attraverso una procedura di Pull Request nel file di whitelist presente sul repo GitHub. Questi software entrano nella seconda area del catalogo (B). Altri spazi di code hosting individuati dai gestori del catalogo di Developers Italia con mezzi manuali o automatizzati. Questi software entrano nella seconda area del catalogo (B) ...
-
italia
Limitazione di responsabilità
AgID e il Team per la Trasformazione Digitale non sono responsabili per il software pubblicato, per la sua rispondenza alle normative e per la sua sicurezza. L’acquisizione e la messa in opera di tale software avvengono sotto la responsabilità di ciascun ente secondo le disposizioni e le limitazioni di responsabilità indicate nella relativa licenza. L’inclusione delle soluzioni nel catalogo avviene con mezzi automatizzati come sopra descritto e pertanto i gestori della piattaforma Developers Italia non svolgono attività di verifica preventiva ...
-
italia
1.2. Software covered by these guidelines
In order to dispel any interpretative doubts, in the context of Articles 68 and 69 of the CAD, the terms ‘programs’, ‘solutions’, ‘computer programs’ and ‘ICT solutions’ are to be understood as the same. The subject matter of the obligation laid down by the provision in question is ‘software’. A non-exhaustive list of software thus covered by these guidelines includes the following:. Desktop applications. Mobile applications. Semi-finished applications and components. Frameworks. Libraries. Plug-ins. Operating systems. Websites (front-end and back-end). These guidelines are intended for encouraging the rationalisation of solutions used in sectors/services familiar to public administrations, such as, for example, human resources management, document management and storage, management of decision-making processes, institutional communication and administrative transparency. Furthermore, it is important to note that the term ‘software’, as used in this document, refers not only to the source and/or executable code, but also to all artefacts produced during the process of developing and using software, i.e. documentation, graphical assets, manuals, etc., as explained in Article 69(1) ...
-
italia
1.6. Software compliance with regulations
Reusing software amplifies any selection made within the information technology field and is completely neutral with respect to the quality or lack thereof of selections made. It can multiply the impact of good practice or, in the same way, negatively enhance the impact of erroneous choices whose dissemination is undesirable. In promoting the reuse and dissemination of software over which the intellectual property rights of an administration are emphasised, along with the important economic and efficiency advantage, it is crucial to draw the attention of individual administrations to the importance of the software being reused - as with the entire software range used by each administration - complying with the regulations in force. Since the process of acquiring software for reuse often includes customisations and aggregations of different components, some of which may no longer be in use or were released years earlier, it is important to remember that the verification of full compliance with the regulatory framework remains the responsibility of the administration that reuses the software, since it alone is responsible for decisions taken within the assigned margins of discretion and in accordance with the constitutional principles of good performance ...
-
italia
1.3. Software reuse
The ‘reuse’ of software refers to the set of activities carried out to enable the software to be used within a different context from that for which it was originally created, in order to satisfy requirements similar to those that led to its initial development. The original product is ‘transported’ into its new context, enriched, if necessary, with additional functionalities and technical characteristics that may represent ‘added value’ for its users. Through the combined provisions of Articles 68 and 69 of the CAD, software for reuse is exclusively that released under open licence by a public administration. Therefore, this is a subset of all open source software available for acquisition. These guidelines distinguish, where appropriate, the methods in which public administration software under an open licence is acquired, in comparison to third-party open source software. A fundamental condition of reuse in the context of public administrations is that an administration that ‘reuses’ software receives it free of charge from the transferring administration, and in acquiring it only incurs the costs of its adaptation, not those of design and implementation ...
-
italia
1.4. Subjects of the guidelines
These guidelines are addressed to public administrations referred to in Article 1(2) of Legislative Decree No 165 of 30 March 2001, in compliance with the division of competence referred to in Article 117 of the Constitution, including the port system authorities, as well as the independent administrative authorities of assurance, control and regulation, i.e. ‘institutes and schools of any class and grade, and educational institutions, autonomous state companies and administrations, the regions, provinces, municipalities and mountain communities and their consortia and associations, university institutions, autonomous social housing institutes, chambers of commerce, industry, crafts and agriculture and their associations, all non-profit national, regional and local public bodies, administrations, companies and bodies of the national health service, ARAN (l’Agenzia per la rappresentanza negoziale delle pubbliche amministrazioni - Contractual Representation Agency for Public Administrations) and the agencies cited in Legislative Decree No 300 of 30 July 1999 and CONI (Comitato Olimpico Nazionale Italiano - Italian National Olympic Committee) (for the latter administration, up until the organic review of the regulations for the sector)’. The provisions for the reuse of solutions shall not apply where there are ‘justified reasons concerning public order and safety, national security and defence, and electoral consultations’. With reference to the scope of application of these guidelines, it is hoped that public administrations will use the cooperation and collaboration tools provided by current legislation, such as collaboration agreements provided for by Article 15 of Law No 241/1990, in order to implement co-design initiatives, broadening the sharing of knowledge, decision-making processes and common paths, through, for example, centres of expertise and support throughout the life cycle of the software ...
-
italia
1.1. Purpose and structure of the document
These guidelines are adopted in implementing Articles 68 and 69 of the Digital Administration Code (hereinafter CAD):. as provided for in Article 69(2a), identifying in Chapter 3 Guidelines for software reuse (Article 69), the platform for the publication of source code under open licence and software documentation available for reuse by administrations, specifying the technical methods for use. They also replace the previous Circular 63/2013, entitled ‘Guidelines for comparative assessment provided for by Article 68 of Legislative Decree No 82 of 7 March 2005, the Digital Administration Code’ and its annexes. This document and the methodology described within are to be understood as aids to a decision-making process that remains under the full responsibility of administrations, when they share solutions as well as when they adopt them for reuse in compliance with the regulations in force, in particular with regard to digital public administration, public contracts and the protection of personal data. With reference to the latter area of law, EU Regulation 2016/679 has defined/specified principles and criteria that are particularly relevant with respect to the subject matter of these guidelines. Among these principles and criteria, the requirement to consider data protection from the design stage and by default (Article 25 of the aforementioned regulation) is highlighted. Furthermore, attention should be paid to AgID technical rules that may affect the subject matter, such as the Minimum security measures (Circular 2/2017) and Guidelines for the development of secure software. This document is the starting point of a cultural process in which public administrations are the protagonists for the increasing use of open software, as is evident from Article 69(1), which requires public administrations ‘that own solutions and computer programs created at the specific instructions of the public client’ to ‘make the relevant source code available, complete with documentation and released in a public repository under open licence. . . ‘. Therefore, the aforementioned regulation was the starting point for the preparation of these guidelines, highlighting the vigorous drive of the legislator towards the increasing use of open source software by public administrations. This can be seen from the simultaneous elimination of the provision of the so-called ‘reuse catalogue’, without this preventing, if necessary, public administrations from entering into agreements (for example, on the basis of Article 15 of Law No 241/90) for the reuse of solutions that do not comply with the provisions of Article 69(1) and that cannot fall within the scope of the cases dealt with here, which, it is stressed, must be those that are subject to an open licence. In any case, the legislator, adopting this strong propensity towards open source for public administrations, has reasonably provided for a general exclusion, only for ‘justified reasons of public order and safety, national defence and electoral consultations’ - in Article 69(1), final bullet point - , in order to safeguard those more sensitive areas of digital government of the country, which from the sharing and community management of open software may be exposed to risk. The approach described above, which favours open source, can also be inferred clearly from the wording of Article 69(2), which requires public administrations ‘in project specifications’ to ‘always be the owners of all rights to programs and information and communication technology services, specifically developed for them’. A safeguard has also been provided for in this case, uniquely for circumstances in which ‘this is excessively onerous for proven technical-economic reasons’. Consequently, Article 68 shall be understood and implemented in this document, in full compliance with the aforementioned interpretation of Article 69. Public administrations are in the position to best know their requirements and will be capable of rejecting the methodology proposed here, in relation to its context, as well as to the characteristics of the acquisition to be carried out. In this sense, the guidelines are not merely a regulatory tool, but suggestions for new follow-up, awareness and information processes ...
-
italia
1.5. Ownership
In accordance with Article 69 of the CAD, as regards reuse, an administration is to be considered as the owner of software designed to meet its own specifications whenever:. the software was developed by resources within the administration itself. When negotiating a contract to commission the development of software, each administration must ensure, at the conclusion of the execution of the contract, their full and exclusive ownership of all rights over the software under development, unless this is excessively onerous for proven technical and economic reasons (from Article 69(2) of the CAD). Software under development refers to the parts of software actually developed in execution of the contract; it is understood that development could be based on the use of existing software components (e.g. open source libraries and frameworks of third parties) for which acquiring ownership is not necessary, only a licence is required (which must be compatible with the purposes of reuse). Failure to acquire ownership of the work cannot be used to obtain more advantageous economic conditions, since it does not constitute a proven technical-economic reason within the meaning of Article 69(2) of the CAD. An administration, within the meaning of Article 69, must also acquire all intellectual and industrial property rights to any customisations or software modules intended to be integrated with or interfaced with proprietary software. In this case, the obligation set forth in Article 69 shall apply exclusively to the module or part of the software being developed; this module must therefore be separated from the rest of the software and released in accordance with the methods specified in Development of software from scratch, taking care to specify the required ownership dependency within the documentation. For example, wording such as the following, where present in software development contracts, allows for the administration to be deemed to be the owner of the rights in the sense required by Article 69 of the CAD:. ‘the ownership of the IT solution covered by the contract will be attached to the client or administration’;. ‘at the end of the contract, the intellectual property of the IT solution under development will lie within the competence of the awarding administration’;. ‘all copyrights on the developed software will be transferred, after the completion of the work, to the awarding administration, which will become the owner’;. ‘all economic exploitation rights as regards the contracted software shall lie within the competence of the awarding administration’ ...
-
italia
1.7. Glossary
Artefacts By-products created during software development that help describe functions, architecture, design and commissioning; for example: functional requirements, description of databases and processes, the test set. Code Hosting (tool) A platform that allows for the publication of the source code, organised into multiple repositories. Code hosting tools often also offer functionalities related to software evolution such as ticketing systems, processes for third-party code contribution, an area for downloading releases, etc. Within the framework of these guidelines, the tools chosen by the administrations must have minimum requirements in terms of functionality (3.4.1 Identifying a code hosting tool). Source code The source code (often referred to simply as ‘source’) is the text of a program written in a programming language (e.g. C or Visual Basic) from which the final program used by the user is derived. Access to the source code is essential for modifying a program. Community Aggregation of natural and legal persons and resources (e.g. forums, chatrooms and technologies for meeting and interacting in a virtual location), with rules and a structure, aimed at the implementation and/or management of a common project. Open format (data) The public data format, versioned, comprehensively documented and without restrictions at implementation. An open format is a format recognised by a standardisation body and maintained in a shared manner among multiple bodies that provide concurrent implementations, with a transparent process. The format must remain consistent with the affirmed version. Data format Data representation method. Interoperability In the field of information technology, the capacity of different and autonomous systems to cooperate and exchange information automatically, on the basis of shared rules. Licence In the field of information technology, the legal text with which certain rights are granted to the software and the data distributed, which would otherwise be reserved by exclusivity rights. Lock-in A technical and economic phenomenon in which a generic user is unable to free themselves from a previously made technological choice. This inability is typically caused by the high costs of changing technology but, in many cases, it may also depend on the adoption of proprietary solutions that prevent migration. The use of open formats for data storage, and free access to such data (especially in the case of SaaS solutions) are prerequisites for avoiding lock-in situations. Open source This refers to a method in which software can be licensed. It is implemented by granting the public rights to use, copy, modify and distribute copies, including modified copies, of the software; to do this, the source code must also be freely available. Also referred to as ‘free software’, ‘open software’ or ‘software released under open license’. The certification body for software licences corresponding to this definition is the Open Source Initiative (OSI). Repository Within a code hosting tool, a repository is the minimum containment unit for the source code of a piece of software. The term ‘reportorio’ is its Italian translation (used for example in CAD Article 69(1)). Reuse In the context of these guidelines, this refers to the process outlined by the CAD (Article 69) with which an administration distributes (‘making available for reuse’) software that it owns in open source, for the benefit of other administrations that can use it (‘reusing’). All reusable software is open source, but not all open source software is reusable (since not all open source software is owned by an administration). SaaS Software as a Service. Refers to a method of software distribution that does not involve installation on operators’ workstations, but that occurs through remote access to a server, for example by connecting to an address through a browser. Wikipedia is an example of software distributed in Software as a Service mode. Proprietary software This is software that has restrictions on its use, modification, reproduction or redistribution imposed by the owner of the economic exploitation rights, i.e. the author or - in the event of a transfer of proprietary rights - the assignee of the rights in question. TCO Total Cost of Ownership: Approach used to assess all the costs of the life cycle of an IT resource calculated over a time window appropriate to the context of the assessment and that includes the cost of migration to another solution (e.g. acquisition, installation, management, maintenance and decommissioning). The TCO approach is based on the consideration that the total cost of using an IT resource depends not only on the acquisition costs, but also on all the costs that occur during the entire operating life of the resource itself ...
-
italia
2.1. Introduction and legislative context
For public administrations, the Digital Administration Code, hereinafter referred to as the CAD, governs the reuse of open solutions and standards. Articles 68 and 69, which these guidelines aim to implement, also deal with the issues of reuse, software ownership and open source code for public administrations. The articles referred to have been modified by Legislative Decree No 179 of 26 August 2016 as well as Legislative Decree No 217 of 12 January 2017. The latest update involved:. the rewording of Article 69(2);. the introduction of Article 69(2a);. the repeal of Article 70, which is entitled ‘Database of reusable computer programs’. The text of Article 68 remains unchanged, except for the updating of the regulatory reference to Legislative Decree No 50/2016 [1] replacing the reference to the previous procurement legislation. Up until the modification implemented by Legislative Decree No 217/2017, the following factors played a role in the acquisition of software by public administrations:. framework conventions and agreements concluded, in accordance with the legislation in force, by CONSIP and by aggregators;. the national catalogue of reusable programs managed by AgID. The first two continue to carry out their functions, while the catalogue functions, repealed as such by the CAD, are assumed by the Developers Italia (https://developers.italia.it) portal, which assumes the role of ‘platform’, or more precisely of repository - according to the wording of Article 69(1) and of the platforms referred to in Article 69(2a). This document reiterates that the ‘principles of economy and efficiency, investment protection, reuse and technological neutrality’ (Article 68(1) of the CAD [2]) are achieved by implementing the provisions of Article 69(2) of the CAD [3]: ’the reuse of computer programs owned by public administrations’ ensuring that the latter, in addition to being owners of the software, make the software available through open source with the affixing of an open licence. http://www.normattiva.it/uri-res/N2Ls?urn:nir:stato:decreto.legislativo:2016-04-18;50!vig=. http://www.normattiva.it/uri-res/N2Ls?urn:nir:stato:decreto.legislativo:2005-03-07;82!vig=~art68. http://www.normattiva.it/uri-res/N2Ls?urn:nir:stato:decreto.legislativo:2005-03-07;82!vig=~art69 ...