2016.09.07 16:14 "[Tiff] remotesensing.org URLs (http and ftp)", by

2016.09.08 17:53 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Rick Widmer

libtiff.info is available. maybe others too.

On 9/8/2016 9:11 AM, Even Rouault wrote:

Le jeudi 08 septembre 2016 16:51:03, Bob Friesenhahn a écrit:

I could file a ticket to have SAC create a new Trac instance (such as https://trac.osgeo.org/libtiff), and I could create the opening wiki page, like the existing html page. Would this be helpful? I can also add the other html pages as raw html, through a wiki parameter I believe. Or, maybe I should just go ahead with this and report back here?

Then anyone can edit the pages (any champion), and it has a long-term home.

Currently the pages are edited and managed via the CVS repository and they are part of every libtiff release.

It is easy to post the current libtiff html files anywhere (as I just did at http://www.simplesystems.org/libtiff/). The main issue is that users are confused about which ones are actively maintained.

I feared that libtiff bugzilla had been lost but thankfully I see that bugzilla is hosted at a different site. It seems that all that has been lost is a URL used since perhaps 2003.

But similarly to www.remotesensing.org which is privately controlled, I guess the same applies for www.simplesystems.org?, so for long term sustainability perhaps we should aim for another plan.

What about having a libtiff.osgeo.org that could serve as a home and run the cvs checkout with a cron job? (if the libtiff community thinks that OSGeo is a good fit for libtiff home). And then we could ask Mark to redirect http://www.remotesensing.org/libtiff/ to libtiff.osgeo.org?

Longer term we should perhaps decide if we migrate away from cvs.maptools.org + bugzilla to something else (github, osgeo trac with git, etc...), but I guess that we'll have the incentive only when things will break out...