-
Notifications
You must be signed in to change notification settings - Fork 5
Reduce friction for providers to contribute #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce friction for providers to contribute #22
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for this, I like the idea of the template and the contributing page is cleaner and more structured. I just have some minor suggestions.
Co-authored-by: Juan Hernando <[email protected]>
Co-authored-by: Juan Hernando <[email protected]>
Co-authored-by: Juan Hernando <[email protected]>
Co-authored-by: Juan Hernando <[email protected]>
Co-authored-by: Juan Hernando <[email protected]>
Co-authored-by: Juan Hernando <[email protected]>
@hernando thanks for your suggestions! Accepted all of them. |
Good, let's wait until @javier-jimenez-shaw-pix4d is back from holidays for his approval and then we can merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. This is very nice. I hope it helps users/providers to contribute.
About your examples in the US... let's see if they still apply one NATRF2022 becomes official ;)
Why?
In the interest of reducing friction for NTRIP providers to contribute their data, I've simplified CONTRIBUTING.md, added examples to it, and added an issue templates that should guide providers through the process of contributing their info to the catalog.
Notably, this more highly encourages providers to just create an issue, which we'd then flesh out in JSON. Sure, this is more work for maintainers, but I think it's better to have providers make issues themselves, rather than not contribute at all. Of course, if the workload is too high as a result of this (which I doubt), we can always change it later.
Note: These issue templates will work out of the box after this is on master. Try them out on my fork
Walkthrough
https://www.loom.com/share/79b54b95968c4470a701ffb2c8d3acea?sid=e0774fcc-0e4f-46d4-932f-3992b4e1ff4f