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

2016.09.16 15:32 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Jeff McKenna

For the record, the non-subscriber also contacted me, in that same message, but i am hesitant to commit the OSGeo foundation to this, without the approval from the libtiff community here. -jeff

On 2016-09-16 12:26 PM, Kemp Watson 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
(b) the libtiff library

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

On 2016-09-14, 4:26 PM, "Kemp Watson" <kemp@objectivepathology.com> wrote:

Our experience is that Github currently has an excellent product for open source initiatives; many projects have migrated from SourceForge to Github. Also, Github uses primarily Git SCM; SourceForge, although supporting Git, uses primarily the now slightly dated Subversion SCM system.

In terms of popularity, Github hosts 88x as many projects as SourceForge, and claims 4x as many users (though I find these numbers a bit suspect). Github, also, offers website hosting as a part of the repository, easy to update with Markdown, with a lot of tooling built around it.

We (Objective Pathology Services) would be happy to help with hosting libtiff. We currently use BigTIFF for extremely large digital pathology files, and are about to release an open format specification for a web-friendly variation of TIFF designed for online zoomable images. We own TIFF.photo, and TIFF.rocks, and would be happy to allocate these to libtiff, perhaps tiff.photo for specifications and tiff.rocks for format promotion (that¹s exactly our plan for our sub-format also). Shame that tiff.info is taken. We would absorb costs for the Github account, and the two domain registry costs, and handle DNS, as a donation to the community. If this is of interest, I suggest that a short contract be in place to ensure continuity of the domains should unforseen events occur.

If not of interest, it appears that libtiff.cloud, libtiff.rocks, tiff.one are available; not much else of direct relevance that I can see. Or, a simple Github (or other repository) account might suffice all on its own.

On 2016-09-14, 1:00 PM, "tiff-bounces@lists.maptools.org on behalf of tiff-request@lists.maptools.org" <tiff-bounces@lists.maptools.org on behalf of tiff-request@lists.maptools.org> wrote:

> Send Tiff mailing list submissions to

>>> tiff@lists.maptools.l