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

2016.09.16 18:01 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Kemp Watson

That¹s was my understanding about official oversight as well, wanted to be sure.

Github¹s got all that covered; static but editable website, plus:




No FTP, but an integrated HTTP download mechanism, it¹s all that¹s needed. Better than FTP, as it integrates with Git, Tower, VS, Xcode, and other build systems.

Unfortunately, someone has a Github project at github.com/libtiff. Not even doing anything with it; a squatter. And github.com/tiff is a user. I¹ve set up github.com/bigtiff, in case it¹s of interestŠ also, we own bigtiff.photo, bigtiff.rocks, and bigtiff.info. Bigtiff.org is owned by an ex-employee of Aperio, who took a first (and slightly non-compliant) crack at a BigTIFF implementation.

I¹ll point some domains to this soon, so you might see what this looks like.

W. Kemp Watson
Objective Pathology Services Limited

tel. +1 (416) 970-7284

On 2016-09-16, 12:21 PM, "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us> wrote:

I¹ve also been in touch with a non-subscriber of this list, who owns the domain libtiff.info, and may be willing to donate it to a selected party, providing steps are taken to

>> ensure the domain¹s continuity.

May I inquire who is currently the official keeper of:

(a) the TIFF specification, and

Adobe is the keeper of the TIFF specification, but have not been doing their job appropriately.

(b) the libtiff library

The keepers of the libtiff library are a few of us with CVS commit privileges. A few of us are able to create releases and post them to the ftp site.

While the copyright mentions SGI, SGI has not been involved since 1997.

and, are we looking for a home for the spec/format, or the library, or both?

Only the library is concerned. Associated with the library we need source control, static web site, bug tracker, and ftp site. We may also want file distribution via https URLs.