AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2017.11.21 13:15 "[Tiff] Write a tif with JPG compression", by Emmanuel Cosnard
2017.11.21 14:50 "Re: [Tiff] Write a tif with JPG compression", by Emmanuel Cosnard
2017.11.21 15:48 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
2017.11.21 19:56 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
2017.11.21 23:15 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
2017.11.22 00:02 "Re: [Tiff] Write a tif with JPG compression", by Lee Howard
2017.11.22 18:27 "Re: [Tiff] Write a tif with JPG compression", by Lee Howard
2017.11.22 17:24 "Re: [Tiff] Write a tif with JPG compression", by Larry Gritz
2017.11.22 17:56 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
2017.11.22 18:49 "Re: [Tiff] Write a tif with JPG compression", by Larry Gritz
2017.11.22 19:43 "Re: [Tiff] Code hosting -- was: Write a tif with JPG compression", by Roger Leigh
2017.11.22 21:34 "Re: [Tiff] Code hosting -- was: Write a tif with JPG compression", by Bob Friesenhahn
2017.11.22 19:50 "Re: [Tiff] Write a tif with JPG compression", by Olivier Paquet
2017.11.22 18:51 "[Tiff] Code hosting -- was: Write a tif with JPG compression", by Kemp Watson
2017.11.22 18:27 "Re: [Tiff] Write a tif with JPG compression", by Roger Leigh
2017.11.22 19:28 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson
2017.11.22 21:30 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
2017.11.22 23:12 "Re: [Tiff] Write a tif with JPG compression", by Roger Leigh
2017.11.22 23:58 "Re: [Tiff] Write a tif with JPG compression", by Bob Friesenhahn
2017.11.23 10:37 "[Tiff] Switching to gitlab ?", by Even Rouault
2017.11.23 10:49 "Re: [Tiff] Switching to gitlab ?", by Roger Leigh
2017.11.23 13:03 "Re: [Tiff] Switching to gitlab ?", by Olivier Paquet
2017.11.23 14:10 "Re: [Tiff] Switching to gitlab ?", by Bob Friesenhahn
2017.11.30 08:58 "Re: [Tiff] Switching to gitlab ?", by Even Rouault
2017.11.23 09:10 "[Tiff] [PATCH] CI improvements for GitLab and GitHub", by Roger Leigh
2017.11.22 07:00 "Re: [Tiff] Write a tif with JPG compression", by Even Rouault
2017.11.21 15:08 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson

2017.11.22 18:51 "[Tiff] Code hosting -- was: Write a tif with JPG compression", by Kemp Watson

GitHub/libtiff and Bitbucket/libtiff are both held by one ³Antony/Antonis Georgiades², a student. Maybe a nice email or donation would assist?

GitHub/tiff and Bitbucket/tiff are ³Christopher Blum².

GitLab/tiff is taken too, by Tiffany :)

Perhaps interestingly, GitLab/libtiff is taken, but the owner says "TIFF Library and Utilities²... anybody stepping up?

W. Kemp Watson

kemp@objectivepathology.com

Objective Pathology Services Limited

8250 Lawson Road
Milton, Ontario
Canada L9T 5C6

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

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 <http://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 <http://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 seems to me that hosting it on a private server that holds only this one -- especially if the domain name isn't "libtiff.{org,com}", is a proposition that just dooms you to indefinitely being plagued by troubles. > it > project > losing > discoverability

May I suggest establishing an official mirror (if not the definitive home) on Having it at github.com/libtiff/libtiff > GitHub?

> <http://github.com/libtiff/libtiff> would dramatically boost the

> searchability/findability of the project and canonical source.

> --
> Larry Gritz
> lg@larrygritz.com
>
>
>