https://cornelius.github.io/technical-committee/Recent content on OpenRail Project HandbookHugoen-ushttps://cornelius.github.io/technical-committee/docs/joining/application/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/joining/application/Applying to become an OpenRail project # The OpenRail Association provides hosting to Open Source projects within the railway sector. Its goal is to facilitate collaboration across organizations so that the huge challenges of the sector can be addressed in a joint effort, effectively and efficiently. The OpenRail Association is open to all participants of the sector, railway companies, vendors, and research institutes, which commit to working on Open Source software in an open model.https://cornelius.github.io/technical-committee/docs/practices/dco/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/practices/dco/Signing off commits with the Developer Certificate of Origin (DCO) # In order to provide clarity about the provenance of code being contributed to OpenRail projects, we use the Developer Certificate of Origin (DCO). This means that with each commit the author of the commit includes a statement which means that they are contributing the code under the license of the project, that they have all rights to do so, and that they are fine with this information being stored publicly.https://cornelius.github.io/technical-committee/docs/joining/onboarding/license-review/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/joining/onboarding/license-review/Review licensing of future/current OpenRail projects # Doing a license review of a project is part of the OpenRail project incubation process, and it might also make sense to make a review continuously or once in a while. This document presents the necessary and possible steps while the mandatory or optional triggers are discussed in other places. Our licensing review focuses on the licensing situation of the own code of the project and the used dependencies.https://cornelius.github.io/technical-committee/docs/practices/reuse/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/practices/reuse/Adopt REUSE to ensure licensing transparency # OpenRail projects are supposed to enable users to easily and safely comply with licensing requirements. Starting from Incubation Stage 2, projects are required to adopt REUSE best practices for licensing and copyright information. REUSE ensures that for every file in a project there is unambiguous information about their license and copyright. It provides a clear standard, along with tools and services, to help with achieving and maintaining this clarity.https://cornelius.github.io/technical-committee/docs/practices/security/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/practices/security/Establish security best practices # OpenRail projects are supposed to follow security best practices. Especially projects from Incubation Stage 2 onwards must follow these to ensure that users can trust them. Some best practices are technical, others rather relate to communication and documentation. We are aware that there can be different perspectives on the selection and priority of certain criteria, but this document defines a baseline which the OpenRail projects agree on.https://cornelius.github.io/technical-committee/docs/joining/governance/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/joining/governance/Setting up Open Governance # We believe that the full power of Open Source is unleashed when Open Source is followed not only by the letter but also in spirit. That’s why we require projects to not only adopt an Open Source license for the code but also an open and transparent collaboration model. We (and others) call that open governance. Principles # Following the statutes of the OpenRail Association and the charter of its Technical Committee we follow certain principles for open governance:https://cornelius.github.io/technical-committee/docs/joining/technical-committee/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/joining/technical-committee/Participating in the Technical Committee # The Technical Committee is the working body of the OpenRail Association which acts as a bridge between the organization and the projects. It runs the incubation process and supports projects to work as high quality open-source projects. The Technical Committee is a hands-on group which jointly does the overarching work necessary to support a healthy ecosystem of Open Source projects within the OpenRail Association.https://cornelius.github.io/technical-committee/docs/charter/Mon, 01 Jan 0001 00:00:00 +0000https://cornelius.github.io/technical-committee/docs/charter/Charter of the Technical Committee of the OpenRail Association # Version 1.0 - Validated by the board of directors on 2024-01-29 Objectives # The OpenRail Association’s Technical Committee (TC) is responsible for selecting and overseeing the Association’s projects to ensure that they are aligned with the Association’s goals and values. The committee works in collaboration with the Board of Directors to make informed decisions on which projects to support and provides the necessary guidance to ensure their success.