<div dir="ltr"><div>Answers inline (sorry, the numbering is broken with the new lines)</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 27 Jan 2026 at 18:03, Jody Garnett <<a href="mailto:jody.garnett@gmail.com">jody.garnett@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr">
We can continue discussion on the ticket, usually it takes a bit of time to hunt down the README, the LICENSE and the user docs and so on.</div><div dir="ltr"><br></div><div dir="ltr">For example your project indicates you have no headers, so this is a chance to do open source advocacy and ask you <i>why</i> you have no headers, to make sure you are doing so on purpose, and to ask where your source code comes from, what do you do when new people contribute etc...</div><div dir="ltr"><br></div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><li>Be geospaital:</li><ol dir="ltr"><li><a href="https://github.com/Pix4D/ntrip-catalog/blob/master/README.md" target="_blank">https://github.com/Pix4D/ntrip-catalog/blob/master/README.md</a><br></li><li>No I cannot include on the website, we give each project team permission to manage their own page, as you are responsible for keep it up to date. What is your OSGeo User ID? For more information see <a href="https://www.osgeo.org/community/getting-started-osgeo/add-a-project/" target="_blank">Add a Project</a></li></ol></ol></div></div></blockquote><div>Ok. I misunderstood the workflow. My user ID is jjimenezshaw</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><ol dir="ltr"><li>I could not find a user guide ... but I also have a question? Is this an open source project (that people would run themselves) or is it a public website (the code of which is open source for others to reference?)<br></li></ol></ol></div></div></blockquote><div>This is more "open data". The source code is just for testing and aggregating the data. The explanation how to use the data it is at the end of the readme. Basically read the json and search for the NTRIP providers <br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><li>Have a free license:</li><ol dir="ltr"><li><a href="https://github.com/Pix4D/ntrip-catalog/blob/master/LICENSE" target="_blank">https://github.com/Pix4D/ntrip-catalog/blob/master/LICENSE</a><br>CC0 is a documentation license (for writing) rather than an open source license for code.<br>CC0 is an alternative to citation for authors composing their own written works, it gives them permission to remix the writing or data into their own creation, granting much the same permissions open source developers enjoy when remixing code beyond its original intent.</li></ol></ol></div></div></blockquote><div>This is a "open data" project. Asking some people they suggested CC0. I am not an expert in licenses, so maybe we should use something else.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><ol dir="ltr"><li>Many open source licenses require headers be applied. If you wish to select an open source license this will be one of the steps to check when adopting it.</li></ol></ol></div></div></blockquote><div>What is a "header" in this context? I naïvely was thinking in the C headers, that define an API (that does not make sense here). </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><li>Welcome contributions</li><ol dir="ltr"><li><font color="#419cff"><a href="https://github.com/Pix4D/ntrip-catalog/blob/master/CONTRIBUTING_GUIDE.md" target="_blank">https://github.com/Pix4D/ntrip-catalog/blob/master/CONTRIBUTING_GUIDE.md</a></font><br></li><ol dir="ltr"><li>This covers some of the mechanics of contributing, but is weak on the legal aspect - who "owns" the resulting work?<br>Do you have shared ownership, or require a contribution license agreement?</li></ol></ol></ol></div></div></blockquote><div>In the "old" contributing guide there was this line "All contributions to NTRIP-catalog are subject to the Developer Certificate of Origin (DCO, <a href="https://developercertificate.org/)">https://developercertificate.org/)</a>." Unfortunately in the PR 22 (BTW from a person from another organization) it was lost. I will add it again.<br></div><div>I don't know if it is enough.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><ol dir="ltr"><li>Collaboration</li><ol dir="ltr"><li><a href="https://github.com/Pix4D/ntrip-catalog/pulls?q=is%3Apr" target="_blank">https://github.com/Pix4D/ntrip-catalog/pulls?q=is%3Apr</a> <br>Key think I am looking for is if this has folks from more than one organization (demonstrate collaboration); but the fact that it is public is great (open to collaboration)<br><a href="https://github.com/Pix4D/ntrip-catalog/issues?q=is%3Aissue" target="_blank">https://github.com/Pix4D/ntrip-catalog/issues?q=is%3Aissue</a> </li></ol></ol></ol></div></div></blockquote><div>Example of PRs and issues from a different organization: <a href="https://github.com/Pix4D/ntrip-catalog/issues?q=author%3Abscholer">https://github.com/Pix4D/ntrip-catalog/issues?q=author%3Abscholer</a></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><ol start="1" style="margin:0px" dir="ltr"><ol dir="ltr"><li><a href="https://github.com/Pix4D/ntrip-catalog/blob/master/CODE_OF_CONDUCT.md" target="_blank">https://github.com/Pix4D/ntrip-catalog/blob/master/CODE_OF_CONDUCT.md</a> <br>Nice work!</li></ol></ol><div><br></div><div dir="ltr">So based on the review there are some questions to answer? Some of which are for you (do you want an open source license, or is this more of an open data project?) and some of which are for OSGeo (do we want to offer a home for open data projects, there used to be a committee for that but I am not sure if it is active).</div></div></div></blockquote><div><br></div><div>Yes, it is an open data project. The actual "code" is minimal. It is in purpose not providing an oficial implementation, to give freedom to the final user. We show it python and a javascrip just as examples.</div><div><br></div><div>Thanks</div><div>Javier</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div>- -<br></div><div>Jody Garnett</div></div></div></div></div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Jan 27, 2026 at 8:27:05 AM, Javier Jimenez Shaw <<a href="mailto:j1@jimenezshaw.com" target="_blank">j1@jimenezshaw.com</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
<div dir="ltr"><div dir="ltr">Hi Jody</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 27 Jan 2026 at 17:01, Jody Garnett <<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr">
Hi Javier,</div><div dir="ltr"><br></div><div dir="ltr">The committee has been looking at how to increase participation, and are looking to moving some of this process form email to an issue tracker.</div></div></blockquote><div>I am already subscribed to the gitea issue #3 . You can answer there if you want to.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><br></div><div dir="ltr">I totally appreciate that you have followed the checklist so I am going to do my best to respond; it would help if you provided the links as I am going to have to hunt that down.</div></div></blockquote><div>Which links do you mean? Is there anything missing? </div><div><br></div><div>Cheers</div><div>Javier.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="ltr"><div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><div>- -<br></div><div>Jody Garnett</div></div></div></div></div><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Oct 20, 2025 at 6:49:45 AM, Javier Jimenez Shaw via Incubator <<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.org</a>> wrote:<br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" type="cite">
<div dir="ltr"><div dir="ltr"><div>Dear OSGeo</div><div><br></div><div>We have an open source project, <a href="http://ntrip-catalog.org" target="_blank">ntrip-catalog.org</a> , that we would like to include as a "Community Project". The last Board meeting said that community projects can be hosted in the OSGeo GitHub organization.</div><div><br></div><div>The repository is currently in <a href="https://github.com/pix4d/ntrip-catalog" target="_blank">https://github.com/pix4d/ntrip-catalog</a></div><div><br></div><div>Attending to the requirements in <a href="https://wiki.osgeo.org/wiki/OSGeo_Community_Projects" target="_blank">https://wiki.osgeo.org/wiki/OSGeo_Community_Projects</a> I think we fulfil all of them (except being on the osgeo website):</div><div><br></div><div><p style="margin:0.5em 0px;color:rgb(32,33,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">Projects applying to the *OSGeo Community* program are asked to:</p><ol style="margin:0.3em 0px 0px 3.2em;padding:0px;color:rgb(32,33,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><li style="margin-bottom:0.1em">Be geospatial<ul style="margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">Confirm by checking README or project description</li><ul><li style="margin-bottom:0.1em">:)</li></ul><li style="margin-bottom:0.1em">project page on the osgeo website</li><ul><li style="margin-bottom:0.1em">Could you include ntrip-catalog on the osgeo website?</li></ul><li style="margin-bottom:0.1em">We ask projects have some user documentation, for example an OSGeo Live quickstart</li><ul><li style="margin-bottom:0.1em">The documentation is there. A final user can also check the web search page.</li></ul></ul></li><li style="margin-bottom:0.1em">Have a free license or an open source license.<ul style="margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">The license must be OSI approved</li><ul><li style="margin-bottom:0.1em">CC0. It was a recommendation from OSGeo members.</li></ul><li style="margin-bottom:0.1em">We ask that the project team check the file headers and double check the license has been appropriately applied</li><ul><li style="margin-bottom:0.1em">There are no headers.</li></ul></ul></li><li style="margin-bottom:0.1em">Welcome participation and new contributors.<ul style="margin:0.3em 0px 0px 1.6em;padding:0px"><li style="margin-bottom:0.1em">We look for a clear contribution policy</li><ul><li style="margin-bottom:0.1em">See the CONTRIBUTING_GUIDE.md</li></ul><li style="margin-bottom:0.1em">We ask that the project demonstrate collaboration, perhaps with a history of bug report or pull requests</li><ul><li style="margin-bottom:0.1em">There are already external contributions in the commit history and issues.</li></ul><li style="margin-bottom:0.1em">Projects are required to have a code of conduct</li><ul><li style="margin-bottom:0.1em">It is there.</li></ul></ul></li></ol><br></div><div>Thank you very much</div><div><br></div><div>Javier Jimenez Shaw.</div><div>OSGeo member 546<br><a href="https://www.osgeo.org/member/jimenezshaw/" target="_blank">https://www.osgeo.org/member/jimenezshaw/</a></div></div>
</div>
<div>
<div>
_______________________________________________<br>Incubator mailing list<br><a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/incubator" target="_blank">https://lists.osgeo.org/mailman/listinfo/incubator</a><br>
</div>
</div>
</blockquote>
</div></div>
</blockquote></div></div>
</blockquote>
</div></div>
</blockquote></div></div>