This is the public hub where you can find information about what is happening at ROR and contribute feedback about what ROR should do in the future. To make sure your feedback is considered, please contribute via the channels described below.
Information about the ROR roadmap and development work (active, planned, or completed) is tracked on the following boards:
🗓️ High-level summary of current, planned, and completed activities
The public roadmap board offers an at-a-glance view of what ROR is working on or exploring for the future. This includes development work as well as other activities, such as sustainability planning and community engagement.
🗄️ A central store of all proposed development work
The inbox board is used for storing and scoping proposed development work.
💡 Where proposed development work goes through a product review and development workflow
Issues from the inbox board move through ROR's product development workflow as they are reviewed, prioritized, and undergo specification, and as ROR solicits community feedback.
🛠️ Work that is under active development
When issues from the product development board are ready to be worked on, they are moved to the software development board.
If you have suggestions for new ROR features or improvements to existing features, please start a discussion topic in the community discussion forum.
You can also open an issue in this repository using the Feature request template. If you don't have all the information needed to complete the issue template, please start in the discussion forum. Please do not submit pull requests at this time.
If you find a problem with the ROR API, website or search interface, please open an issue using the Bug report template.
Note: Please do not open a bug report to request changes to ROR record data, such as adding new ROR records or changing data on existing records! ROR record data changes are managed through a community-based curation process. To request changes to ROR record data, see Curation requests below.
If you have suggestions for changes to the ROR data model, please start a discussion topic in the community discussion forum. It's a good idea to review the current schema and data model documentation before requesting a change.
You can also open an issue in this repository using the Schema change request template. If you don't have all the information needed to complete the issue template, please start in the discussion forum. Please do not submit pull requests at this time.
Schema change requests will be considered as part of the schema & API versioning process, which includes a community comment period.
If you have feedback about the contents of the registry, e.g., if you wish to suggest any new organizations to be added or any changes to an existing record, use this form. Read more about the registry's curation model and follow the workflow in the ror-updates Github repository.
If you've written code that works with the ROR API or data dump that you'd like to share, please make a pull request in ror-utilities or add the topic research-organization-registry to your own repository.
If you're interested in making code contributions to ROR tools and services, like ror-api and ror-app, please contact us at info@ror.org . We are not likely to accept community pull requests unrelated to tasks on our software development board.