You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bit of data we need to maintain about OpenRail projects. These are basic things like name, description, important general data such as the license, but also some OpenRail specific data such as which architectural domain the project covers, the incubation stage.
Some of this data is already there, in the GitHub UI, in README or LICENSE files, or in the information around the incubation process. Some data is not there yet, e.g. the architectural domain.
We use this data for the presentation of the projects in various places, in the repository itself, in the project list maintained by the technical committee. We also want to use it on the web site (#95). Or in a bit more informal ways when talking about projects in presentations etc. There something like a summary sheet of the project would be helpful as well, which mostly will contain the meta data we have at other places as well.
To make this easier and consistent and serve the data from one canonical place, it would be good to adopt a common format and a standard location for maintaining this data.
One way this could be done is by adopting publiccode.yml. This is pretty close to what we need.
There is a bit of data we need to maintain about OpenRail projects. These are basic things like name, description, important general data such as the license, but also some OpenRail specific data such as which architectural domain the project covers, the incubation stage.
Some of this data is already there, in the GitHub UI, in README or LICENSE files, or in the information around the incubation process. Some data is not there yet, e.g. the architectural domain.
We use this data for the presentation of the projects in various places, in the repository itself, in the project list maintained by the technical committee. We also want to use it on the web site (#95). Or in a bit more informal ways when talking about projects in presentations etc. There something like a summary sheet of the project would be helpful as well, which mostly will contain the meta data we have at other places as well.
To make this easier and consistent and serve the data from one canonical place, it would be good to adopt a common format and a standard location for maintaining this data.
One way this could be done is by adopting publiccode.yml. This is pretty close to what we need.
An alternative solution might be https://codemeta.github.io/.
The text was updated successfully, but these errors were encountered: