Hi, as an occasional contributor, I'm fully supportive.
What is the intent of the "Web scraping the Trac ticket contents and placing in a geos-old-tickets repo" ? (I assume you mean a github repo). To have a "backup" of the Trac content that is easily browsable by non-Trac users ? That repository would be read-only ?
FWIW, what we did in GDAL is to *not* port existing Trac tickets, just disable creation of new Trac tickets, but authenticated users can still modify / close existing ones.
Even Le 29/10/2021 à 21:13, Paul Ramsey a écrit :
http://libgeos.org/development/rfcs/rfc10/ GitHub has been the largest source of 3rd party code contribution via pull-requests for some time now. Moving to Github has the following components: • Move the canonical (writeable) repository to GitHub • Migrate the (current, useful) contents of the Trac wiki to the new web framework • Deleting the migrated and out-of-date contents of the Trac wiki • Switching the Trac tickets to read-only • Web scraping the Trac ticket contents and placing in a geos-old-tickets repo At that point: • New code is pushed to GitHub • New issues are filed at GitHub • New documentation is committed to the repository This should unlock: • Easier path for new contributors to discover and assist with the project • Easier collaboration with downstream projects • Far easier story on “how to we manage the project” and “where the important things happen” • Far less dependence on individual contributors for infrastructure work that only they can do _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
-- http://www.spatialys.com My software is free, but my time generally not. _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
