Hi all: as part of the ongoing discussions at the OSGeo Board
concerning OSGeo services provisioning, we realize and strongly
support the gitea instance at [1], as a modern, Git-based version
control, issue tracker and wiki for the OSGeo community. In addition,
it would be valuable to streamline this capability and reduce services
providing similar functionality.
Having said this, we would want to decommission the Trac instance [2]
in lieu of gitea, and discuss its implementations with you before
initiating a Board motion.
Can SAC enumerate projects currently using the instance, and whether
gitea could serve their needs instead?
Hi all: as part of the ongoing discussions at the OSGeo Board concerning
OSGeo services provisioning, we realize and strongly support the gitea
instance at [1], as a modern, Git-based version control, issue tracker and wiki
for the OSGeo community. In addition, it would be valuable to streamline this
capability and reduce services providing similar functionality.
Having said this, we would want to decommission the Trac instance [2] in lieu
of gitea, and discuss its implementations with you before initiating a Board
motion.
Can SAC enumerate projects currently using the instance, and whether gitea
could serve their needs instead?
PostGIS , OSGeo, OSGEO4W I think are the prime users of trac.
For the wiki piece of PostGIS we have been migrating the wiki part to our website and are largely done with that.
I think the trac ticketing piece will take a bit more time but is on our PostGIS roadmap to do.
OSGeo I think is doable.
In all cases it's the level of effort to migrate the tickets and see if we can keep the same numbering.
Grass I think still uses it for some things but not sure.
The others it's just a historical history of old tickets that may not have been migrated to github.