OpenRailAssociation / OpenRailAssociation/technical-committee

Project roadmap review

Open
#367 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
7
Forks
11
Avg merge
1d 14h
Merged PRs (30d)
11

Description

As discussed in the TC meeting on 2026-07-14, we would like to do a review of the project roadmaps in the Technical Committee.

We will plan one session per project in the regular meeting on Tuesday, where each project should show the current roadmap, ideally answering the following questions:

  • What is the concrete work planned short-term (next few iterations)?
  • What work is planned mid-term (within the next 12 months)?
  • What is the long-term plan?
  • What work would be good to be done, but isn't planned (due to limited resources or any other reasons)? This could be a chance for new contributors to jump in.
  • Is there anything the OpenRail Association in general and the Technical Committee specifically can support with?

Each session should be about 20 minutes.

Tentative plan:

  • RCM OSS (July 28)
  • DAC Migration DSS (Aug 4)
  • Netgrafik-Editor (Aug 4)
  • libLRS (Sep 8)
  • OSRD (at community meetup on September 10, 14:00)
  • MscViewer (Sep 15)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the discussion in the Technical Committee meeting linked from PR 365 and the tentative schedule in this issue. Coordinate the remaining roadmap sessions for OSRD and MscViewer, covering short-, mid-, and long-term plans, unplanned work, and support needs. Done means the listed project roadmap reviews have been completed and recorded.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.