From tomkralidis at gmail.com Sat Sep 5 06:55:48 2026 From: tomkralidis at gmail.com (Tom Kralidis) Date: Sat, 5 Sep 2026 09:55:48 -0400 Subject: migrating trac instance to gitea Message-ID: 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? Thanks ..Tom [1] https://git.osgeo.org [2] https://trac.osgeo.org From jody.garnett at gmail.com Sat Sep 5 14:52:38 2026 From: jody.garnett at gmail.com (Jody Garnett) Date: Sat, 5 Sep 2026 14:52:38 -0700 Subject: migrating trac instance to gitea In-Reply-To: References: Message-ID: I would be preferred (for the website issues reported to trac). Indeed trac was cited as a ooor experience when looked at what could be done to make OSGeo more welcoming. - - Jody Garnett On Sat, Sep 5, 2026 at 06:56 Tom Kralidis wrote: > 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? > > Thanks > > ..Tom > > [1] https://git.osgeo.org > [2] https://trac.osgeo.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Sun Sep 6 11:53:38 2026 From: lr at pcorp.us (Regina Obe) Date: Sun, 6 Sep 2026 14:53:38 -0400 Subject: migrating trac instance to gitea In-Reply-To: References: Message-ID: <000601dd3e31$07ca7010$175f5030$@pcorp.us> > 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? > > Thanks > > ..Tom > > [1] https://git.osgeo.org > [2] https://trac.osgeo.org 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. From osgeo at neteler.org Mon Sep 7 00:04:10 2026 From: osgeo at neteler.org (Markus Neteler) Date: Mon, 7 Sep 2026 09:04:10 +0200 Subject: migrating trac instance to gitea In-Reply-To: <000601dd3e31$07ca7010$175f5030$@pcorp.us> References: <000601dd3e31$07ca7010$175f5030$@pcorp.us> Message-ID: Am 06.09.26 um 8:53 PM schrieb Regina Obe: >> 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? >> >> Thanks >> >> ..Tom >> >> [1]https://git.osgeo.org >> [2]https://trac.osgeo.org > > 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. GRASS uses esp. the old tickets on trac for reference. We would be very grateful to see the GRASS trac instance migrated as well. Thanks Markus > > The others it's just a historical history of old tickets that may not have been migrated to github. > -- Markus Neteler, PhD https://www.mundialis.de - Earth. Data. Solutions. https://esmeralda.earth - ecosystem restoration https://grass.osgeo.org https://neteler.org/blog https://www.linkedin.com/in/markusneteler/ -------------- next part -------------- An HTML attachment was scrubbed... URL: