-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #32 from OpenRailAssociation/tc
Add message of the Technical Committee chairs
- Loading branch information
Showing
1 changed file
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,15 @@ | ||
## Message of the Chairs of the Technical Committee | ||
|
||
*Message from the Technical Committee, highlighting beginning collaboration (example OSRD/NGE).* | ||
|
||
In 2024, we built the Technical Committee of the OpenRail Association. It represents the projects, provides open-source governance, and serves as the bridge between the projects and the OpenRail Association as an organization. Our initial focus was to bring the first projects and people together and establish an effective working mode. The **Charter of the Technical Committee** has been validated by the board of directors at the inception of the OpenRail Association. | ||
|
||
We are very happy with what we achieved in our first year. Because we didn't have projects at the beginning yet, the Technical Committee started with three members appointed by the board, **Cornelius Schumacher, Loic Hamelin and Peter Keller**. With accepting the first projects, their representatives joined us and at the end of 2024 we are a healthy team of eight people. | ||
|
||
At the Technical Committee, we strive to lead by example. We focus on getting things done, and our work is fully **public on GitHub**, staying true to the open-source spirit. To maintain momentum and ensure quick decision-making, we hold **weekly meetings**. All this has proven to be a highly effective way of collaboration. | ||
|
||
One of our biggest achievements this year was defining and refining the **incubation process**. Using the first incoming projects as practical examples, we solidified the **criteria for incubation stages**, streamlined the **application process**, and established **best practices for onboarding projects**. We are proud of the result: we now have a **clear, structured approach to becoming an OpenRail project**, and our first five projects already represent a diverse set of initiatives that embody this vision. We established a **Code of Conduct** to ensure that all projects within the Technical Committee uphold the values and spirit of the OpenRail Association. Additionally, we provide project candidates with all the necessary documentation templates to help them meet OpenRail’s requirements. | ||
|
||
We are especially proud to see **collaboration between OpenRail projects** delivering real impact. A great example is **OSRD and Netzgrafik-Editor**, which joined forces to integrate timetable functionality into OSRD. This collaboration **accelerated OSRD’s progress significantly, saving them an estimated two years in time-to-market**. This is exactly the kind of synergy we aim to foster, and we look forward to seeing even more projects benefit from working together in the future. | ||
|
||
-- Cornelius Schumacher and Loic Hamelin, Chairs of the OpenRail Technical Committeee 2024 |