OpenRailAssociation / OpenRailAssociation/landscape

Overview of projects grouped by domain

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

Nobody has claimed this yet.

Dominant language
HTML
Stars
5
Forks
3
PR merge metrics
No merged PRs in 30d

Description

As an entry point to the landscape it would be useful to have an overview grouped by domains. This could be oriented at the architectural domain models used by the railway industry. Showing the projects grouped by the specific domain where they are providing solutions would make it easier for people coming from these domains to find relevant projects. This would be more a business-oriented view than a technical view.

For displaying these domains an approach as used for example by the Component Gallery could be suitable. This would be a three-level display, on the first level an overview of domains, on the second level an overview of projects per domain, and on the third level the details view of each project. The card-like display of the component gallery could be a way to on one hand give a good overview and on the other hand show the most relevant details at a glance.

As the specific structure of domain models will vary a bit between different organizations, we would need to find some compromise to have a simple model and corresponding structures, which are easy to map from other models. We probably don't want to go too much in detail there, but keep it at a quite high level. This would also reduce the effort to classify projects.

An example based on the current projects would be:

Capactiy planning: OSRD, Netzgrafik-Editor, libLRS
Asset management: RCM OSS, DAC Migration DSS
Journey booking and planning: OpenTripPlanner

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are named. Start by reviewing how the current projects are represented, then define a high-level domain model and a three-level view covering domains, projects, and project details; done means the landscape presents projects grouped by domain in a business-oriented view.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
design, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.