2017.11.22 17:56 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson

I totally agree, have been pushing for this for a year. It's time to move off CVS as well.

GitHub/libtiff is taken, as are the .com and .org domains. I and Justin Derrick have offered up libtiff.info, and I do have a spot on GitHub/bigtiff. Also have libtiff.cloud, libtiff.online, tiff.photo, tiff.rocks, and 12 bigtiff.*.

GitHub hosts nearly 40 MILLION repos, allows modern source control, multiple users/owners, and currently triple repo redundancy. Not including private mirrors.

W. Kemp Watson
Objective Pathology Services Limited
Halton Data Center
8250 Lawson Road
Milton, Ontario
Canada L9T 5C6

http://www.objectivepathology.com

kemp@objectivepathology.com
tel. +1 (416) 970-7284

> On Nov 22, 2017, at 12:24 PM, Larry Gritz <lg@larrygritz.com> wrote:

>

>> On Nov 22, 2017, at 9:00 AM, Bob Friesenhahn <bfriesen@simple.dallas.tx.us> wrote:

All of the libtiff web content comes from the libtiff CVS server (and is also contained in each release tarball). There is no reason why

>> libtiff.info can not be serving up current libtiff web pages already.

Based on past history, redundancy is good.

No slight to your generosity and stewardship of the project and web site, but it seems to me that hosting it on a private server that holds only this one project -- especially if the domain name isn't "libtiff.{org,com}", is a losing proposition that just dooms you to indefinitely being plagued by discoverability troubles.

May I suggest establishing an official mirror (if not the definitive home) on GitHub? Having it at github.com/libtiff/libtiff would dramatically boost the searchability/findability of the project and canonical source.