Some months ago I started this project in my current employer, Pix4D, an open source catalog to maintain the CRS (Coordiante Reference Systems) of the different NTRIP providers: https://github.com/Pix4D/ntrip-catalog
The license is CC0. The purpose is to make it really easy for the providers to contribute to that repo.
The initial plan was to transfer it to OSGeo GitHub organization when it gets some traction. I talked back then personally with Jorge and he thought it was a good idea. We think we have now some traction, and other companies are already using it.
It would be great if we could transfer the repository from Pix4D to OSGeo GitHub organizations, making clear that the project is open source and geospatial.
The “interesting” content of the repo is data. There are a few scripts in python for testing. The legal department in my company said that it’s ok. I’m not an expert in licenses.
I can do the track ticket (I also have to make a ticket in my company. That’s why I asked here, to synchronize things a bit before doing it).
About the GitHub credentials, let’s see what’s needed. I find strange that the same person needs high permissions in both organisations.
I have only ever done it my account and an organization. It perhaps that is for automatic workflow. You can also do a raw clone and push up tones location.
It would be great if we could transfer the repository from Pix4D to OSGeo
GitHub organizations, making clear that the project is open source and
geospatial.
I don't see how keeping it on GitHub makes it clearer that the project
is opensource and spatial. The LICENSE file already makes it clear
that the project is open source and and I believe you can use "tags"
to make it clear it is spatial, ie: gis · GitHub Topics · GitHub
Last time I checked GitHub applied limits to organization so grouping
all projects under the "osgeo" org only really reduces the amount of
resources available to every other project.
To transfer repositories to an organization, you must have permission to create repositories in the receiving organization, and to transfer repositories out of the origin organization. An organization or enterprise owner may have set a policy that prevents certain users from doing these things.
Once a repository is transferred to an organization, the organization’s default repository permission settings and default membership privileges will apply to the transferred repository.
So I think we would add you as an admin to osgeo GitHub, you could then transfer, and set up permissions appropriately.
