[Incubator] ntrip-catalog as community project.
Javier Jimenez Shaw
j1 at jimenezshaw.com
Thu Jan 29 07:59:18 PST 2026
Answers inline (sorry, the numbering is broken with the new lines)
On Tue, 27 Jan 2026 at 18:03, Jody Garnett <jody.garnett at gmail.com> wrote:
> 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.
>
> For example your project indicates you have no headers, so this is a
> chance to do open source advocacy and ask you *why* 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...
>
>
> 1. Be geospaital:
> 1. https://github.com/Pix4D/ntrip-catalog/blob/master/README.md
> 2. 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 Add a
> Project
> <https://www.osgeo.org/community/getting-started-osgeo/add-a-project/>
>
> Ok. I misunderstood the workflow. My user ID is jjimenezshaw
>
> 1. 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?)
>
> 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
> 1. Have a free license:
> 1. https://github.com/Pix4D/ntrip-catalog/blob/master/LICENSE
> CC0 is a documentation license (for writing) rather than an open
> source license for code.
> 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.
>
> 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.
>
> 1. 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.
>
> 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).
>
> 1. Welcome contributions
> 1.
> https://github.com/Pix4D/ntrip-catalog/blob/master/CONTRIBUTING_GUIDE.md
> 1. This covers some of the mechanics of contributing, but is weak
> on the legal aspect - who "owns" the resulting work?
> Do you have shared ownership, or require a contribution license
> agreement?
>
> In the "old" contributing guide there was this line "All contributions to
NTRIP-catalog are subject to the Developer Certificate of Origin (DCO,
https://developercertificate.org/)." Unfortunately in the PR 22 (BTW from a
person from another organization) it was lost. I will add it again.
I don't know if it is enough.
>
> 1. Collaboration
> 1. https://github.com/Pix4D/ntrip-catalog/pulls?q=is%3Apr
> 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)
> https://github.com/Pix4D/ntrip-catalog/issues?q=is%3Aissue
>
> Example of PRs and issues from a different organization:
https://github.com/Pix4D/ntrip-catalog/issues?q=author%3Abscholer
>
> 1.
> https://github.com/Pix4D/ntrip-catalog/blob/master/CODE_OF_CONDUCT.md
>
> Nice work!
>
>
> 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).
>
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.
Thanks
Javier
> - -
> Jody Garnett
>
>
> On Jan 27, 2026 at 8:27:05 AM, Javier Jimenez Shaw <j1 at jimenezshaw.com>
> wrote:
>
>> Hi Jody
>>
>> On Tue, 27 Jan 2026 at 17:01, Jody Garnett <jody.garnett at gmail.com>
>> wrote:
>>
>>> Hi Javier,
>>>
>>> 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.
>>>
>> I am already subscribed to the gitea issue #3 . You can answer there if
>> you want to.
>>
>>>
>>> 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.
>>>
>> Which links do you mean? Is there anything missing?
>>
>> Cheers
>> Javier.
>>
>>> - -
>>> Jody Garnett
>>>
>>>
>>> On Oct 20, 2025 at 6:49:45 AM, Javier Jimenez Shaw via Incubator <
>>> incubator at lists.osgeo.org> wrote:
>>>
>>>> Dear OSGeo
>>>>
>>>> We have an open source project, ntrip-catalog.org , 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.
>>>>
>>>> The repository is currently in https://github.com/pix4d/ntrip-catalog
>>>>
>>>> Attending to the requirements in
>>>> https://wiki.osgeo.org/wiki/OSGeo_Community_Projects I think we fulfil
>>>> all of them (except being on the osgeo website):
>>>>
>>>> Projects applying to the *OSGeo Community* program are asked to:
>>>>
>>>> 1. Be geospatial
>>>> - Confirm by checking README or project description
>>>> - :)
>>>> - project page on the osgeo website
>>>> - Could you include ntrip-catalog on the osgeo website?
>>>> - We ask projects have some user documentation, for example an
>>>> OSGeo Live quickstart
>>>> - The documentation is there. A final user can also check the
>>>> web search page.
>>>> 2. Have a free license or an open source license.
>>>> - The license must be OSI approved
>>>> - CC0. It was a recommendation from OSGeo members.
>>>> - We ask that the project team check the file headers and double
>>>> check the license has been appropriately applied
>>>> - There are no headers.
>>>> 3. Welcome participation and new contributors.
>>>> - We look for a clear contribution policy
>>>> - See the CONTRIBUTING_GUIDE.md
>>>> - We ask that the project demonstrate collaboration, perhaps
>>>> with a history of bug report or pull requests
>>>> - There are already external contributions in the commit
>>>> history and issues.
>>>> - Projects are required to have a code of conduct
>>>> - It is there.
>>>>
>>>>
>>>> Thank you very much
>>>>
>>>> Javier Jimenez Shaw.
>>>> OSGeo member 546
>>>> https://www.osgeo.org/member/jimenezshaw/
>>>> _______________________________________________
>>>> Incubator mailing list
>>>> Incubator at lists.osgeo.org
>>>> https://lists.osgeo.org/mailman/listinfo/incubator
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20260129/5fcd910c/attachment-0001.htm>
More information about the Incubator
mailing list