Developer GitHub Organisation - Revision history

Krizar at 13:35, 25 January 2026

2026-01-25T13:35:16Z

Krizar at 21:09, 1 April 2025

2025-04-01T21:09:27Z

Oxalin at 11:18, 2 December 2022

2022-12-02T11:18:41Z

Oxalin at 11:02, 2 December 2022

2022-12-02T11:02:48Z

Oxalin at 11:00, 2 December 2022

2022-12-02T11:00:16Z

Krizar: Added creation date

2022-09-06T07:10:24Z

Added creation date

Oxalin at 20:51, 5 September 2022

2022-09-05T20:51:20Z

Krizar at 21:26, 25 August 2022

2022-08-25T21:26:20Z

Krizar: /* Further Information */

2022-08-24T19:56:59Z

Further Information

Krizar: Created main GitHub info page

2022-08-24T19:56:15Z

Created main GitHub info page

@@ Line 21: / Line 21: @@
 * [[Crewe & Chester Northern Services]]
 * [[Manchester Area]]
 == Further Information ==

@@ Line 18: / Line 18: @@
 * [[O' Tannenbaum]]
 * [[Xmas 2022]]
 == Further Information ==

@@ Line 11: / Line 11: @@
 * [[Cardiff Valley Lines]]
 * [[Castlefield Corridor]]
 * [[Island Line - Isle of Wight UK]]
 * [[King's Cross]]
 * [[Llandudno Junction]]
 * [[Nottingham Trams North]]
 * [[Xmas 2022]]

@@ Line 10: / Line 10: @@
 * [[Barnham and Ford]]
 * [[Cardiff Valley Lines]]
 * [[Island Line - Isle of Wight UK]]
 * [[King's Cross]]

@@ Line 14: / Line 14: @@
 * [[Llandudno Junction]]
 * [[Nottingham Trams North]]
 == Further Information ==

← Older revision		Revision as of 07:10, 6 September 2022
Line 1:		Line 1:
−	The '''Railway-Op-Sim GitHub Organisation''' is a group for developers of routes and software to collaborate ~~on such routes and software~~ on the code version control hosting site GitHub. The original aim of the group was to provide a central development area for the creation of route add-ons for [[Railway Operation Simulator]] where a standard can be implemented to ensure all projects are structured in a similar manner and contain all the information required to initialise a simulation. However over time the usage has extended to the creation of tools and interfaces to improve interaction with the software.	+	The '''Railway-Op-Sim GitHub Organisation''' is a group created on 22nd September 2019 for developers of routes and software to collaborate on the code version control hosting site GitHub. The original aim of the group was to provide a central development area for the creation of route add-ons for [[Railway Operation Simulator]] where a standard can be implemented to ensure all projects are structured in a similar manner and contain all the information required to initialise a simulation. However over time the usage has extended to the creation of tools and interfaces to improve interaction with the software.

	[[File:Railway-Op-Sim_Logo.png\|thumb\|Logo for the Railway-Op-Sim GitHub Organisation]]		[[File:Railway-Op-Sim_Logo.png\|thumb\|Logo for the Railway-Op-Sim GitHub Organisation]]

@@ Line 6: / Line 6: @@
 Requests for access to the GitHub organisation should be made via the [[Railway Operation Simulator]] Discord server.
 == Further Information ==
 * [[Introduction to Git for Development]]
 * [[Project Template|Using the Add-on Template]]
 * [[Continuous Integration]]
 * [[Organisation Teams and Projects]]

← Older revision		Revision as of 21:26, 25 August 2022
Line 1:		Line 1:
	The '''Railway-Op-Sim GitHub Organisation''' is a group for developers of routes and software to collaborate on such routes and software on the code version control hosting site GitHub. The original aim of the group was to provide a central development area for the creation of route add-ons for [[Railway Operation Simulator]] where a standard can be implemented to ensure all projects are structured in a similar manner and contain all the information required to initialise a simulation. However over time the usage has extended to the creation of tools and interfaces to improve interaction with the software.		The '''Railway-Op-Sim GitHub Organisation''' is a group for developers of routes and software to collaborate on such routes and software on the code version control hosting site GitHub. The original aim of the group was to provide a central development area for the creation of route add-ons for [[Railway Operation Simulator]] where a standard can be implemented to ensure all projects are structured in a similar manner and contain all the information required to initialise a simulation. However over time the usage has extended to the creation of tools and interfaces to improve interaction with the software.
		+
		+	[[File:Railway-Op-Sim_Logo.png\|thumb\|Logo for the Railway-Op-Sim GitHub Organisation]]

	Projects hosted under the domain of the organisation are assumed to fall under an open source license (e.g. GPLv3) and be open to contributions from other developers under the condition that the correct etiquette for collaborative code writing be followed including issue opening and merging of changes through pull requests. Route add-on development is encouraged to follow the conventions set out within the GitHub [https://github.com/Railway-Op-Sim/UN-Template template repository] which also includes automated testing using the GitHub Actions Continuous Integration (CI) system. The template defines a standard directory structure for constituent files, and introduces the concept of a metadata file which contains additional useful information not covered by the existing route and timetable files. As part of the CI system if a metadata file is not found one is generated and should be updated by the author to contain correct information.		Projects hosted under the domain of the organisation are assumed to fall under an open source license (e.g. GPLv3) and be open to contributions from other developers under the condition that the correct etiquette for collaborative code writing be followed including issue opening and merging of changes through pull requests. Route add-on development is encouraged to follow the conventions set out within the GitHub [https://github.com/Railway-Op-Sim/UN-Template template repository] which also includes automated testing using the GitHub Actions Continuous Integration (CI) system. The template defines a standard directory structure for constituent files, and introduces the concept of a metadata file which contains additional useful information not covered by the existing route and timetable files. As part of the CI system if a metadata file is not found one is generated and should be updated by the author to contain correct information.

← Older revision		Revision as of 19:56, 24 August 2022
Line 1:		Line 1:
−	The '''~~ROS~~ GitHub Organisation''' is a group for developers of routes and software to collaborate on such routes and software. ~~To create~~ route ~~projects,~~ a ~~template is provided which ensures that~~ projects are in a ~~standard form~~. ~~The organisation also features open source software, such as~~ the ~~[[ROSPkgManager]]~~ and ~~[[json2ttb]]. You can view on GH here: [https://github.com/Railway-Op-Sim]~~.	+	The '''Railway-Op-Sim GitHub Organisation''' is a group for developers of routes and software to collaborate on such routes and software on the code version control hosting site GitHub. The original aim of the group was to provide a central development area for the creation of route add-ons for [[Railway Operation Simulator]] where a standard can be implemented to ensure all projects are structured in a similar manner and contain all the information required to initialise a simulation. However over time the usage has extended to the creation of tools and interfaces to improve interaction with the software.

−	~~Edit~~ access ~~can~~ be ~~received by getting in touch on~~ the [[~~ROS~~ Discord server]].	+	Projects hosted under the domain of the organisation are assumed to fall under an open source license (e.g. GPLv3) and be open to contributions from other developers under the condition that the correct etiquette for collaborative code writing be followed including issue opening and merging of changes through pull requests. Route add-on development is encouraged to follow the conventions set out within the GitHub [https://github.com/Railway-Op-Sim/UN-Template template repository] which also includes automated testing using the GitHub Actions Continuous Integration (CI) system. The template defines a standard directory structure for constituent files, and introduces the concept of a metadata file which contains additional useful information not covered by the existing route and timetable files. As part of the CI system if a metadata file is not found one is generated and should be updated by the author to contain correct information.
		+
		+	Requests for access to the GitHub organisation should be made via the [[Railway Operation Simulator]] Discord server.
		+
		+	== Further Information ==
		+
		+	* [[Introduction to Git for Development]]
		+	* [[Project Template\|Using the Add-on Template]]
		+	* [[Continuous Integration]]
		+	* [[Organisation Teams and Project]]