> On Oct 30, 2021, at 2:37 PM, Even Rouault <even.roua...@spatialys.com> wrote: > > 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 ?
Yes, the idea is to have a back-up of the trac content that is not dependent on trac, so that the whole trac.osgeo.org/geos infra can be turned off eventually and traffic to trac.osgeo.org/geos/ticket/XXXX handled with a simple redirect. > 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. That is the same as what I'm proposing. No more new trac tickets. No copying of trac tickets into GH. Anything that is live-and-important can be re-opened as a GH issue. Anything that is not will become history over time. Save history for posterity by taking the HTML snapshot. P. > > 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
