|
| 1 | +# Meeting on 2025-03-18 |
| 2 | + |
| 3 | +Present: Cornelius, Florian, Frederik, Max, Peter, Tristram |
| 4 | + |
| 5 | +## Agenda |
| 6 | + |
| 7 | +* Project Handbook/Website of TC (https://github.com/OpenRailAssociation/technical-committee/issues/211) |
| 8 | +* Planned milestones of projects for 2025 |
| 9 | +* Annual report |
| 10 | + |
| 11 | +## Protocol |
| 12 | + |
| 13 | +* Project handbook |
| 14 | + * Do we want to separate the project handbook information and the rest of the content in the TC repo (meetings, project proposals) |
| 15 | + * It's hard to split things, as it's not always clear, if it belongs to the handbook or is "general" information |
| 16 | + * What is the target audience? Projects are a target group, internal audience, also targeted at new projects |
| 17 | + * We also have the OpenRail Association website for the outside world, also targeted at new members |
| 18 | + * Decision: We make the project handbook the TC website, keep it in one repository, add all the information of the repo we want to have on the website |
| 19 | + * Decision: We use the domain projects.openrailassociation.org |
| 20 | + * Decision: We add list of TC members, list of projects, incubation process definition, project proposal questionnaries |
| 21 | + * We try to minimize duplication by using Hugo mounts where needed, so that the repo doesn't contain redundancies. The website then renders that. We think search engines can deal with that to not confuse people. |
| 22 | +* Milestones |
| 23 | + * We have concrete OSRD and DAC Migration DSS milestones for 2025 in the annual report |
| 24 | + * Netzgrafik-Editor: |
| 25 | + * Roadmap: https://github.com/SchweizerischeBundesbahnen/netzgrafik-editor-frontend/blob/main/ROADMAP.md |
| 26 | + * Short-term goals are for 2025 |
| 27 | + * Peter will look at the roadmap and refine it if necessary |
| 28 | + * RCM OSS, library planned for 2026 |
| 29 | + * libLRS, software is stable, increase adoption, incremental development |
| 30 | + * New projects: tp-lib is already a candidate, look at Entur projects, which would fit into the OpenRail Association (domain customer information, potentially large audience) |
| 31 | +* Annual report: https://github.com/OpenRailAssociation/annual-report |
| 32 | + * Content is mostly final |
| 33 | + * Feedback is welcome, feel free to create issues and pull requests |
| 34 | + * If you have any additional pictures, please add them |
| 35 | + * We want to finalize the content this week |
0 commit comments