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 19:28 "Re: [Tiff] Write a tif with JPG compression", by Kemp Watson

OK, so the "TIFF Library and Utilities² is RogerŠ that¹s good.

The master could live on (well-named) GitLab/libtiff, and I could host a mirror on GitHub/bigtiff/tiff or some such. Plus anybody else can continue to mirror, only now on Git as opposed to aging CVS. An awful lot of advantages to this. Plus both repos can have multiple administrators in case Roger and I are having lunch and a truck comes through the window, not so uncommon these days.

Still the issue of domain names, but it¹s a different issue than the physical location of the code.

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

On 2017-11-22, 1:27 PM, "Roger Leigh" <tiff-bounces@lists.maptools.org on behalf of rleigh@codelibre.net> wrote:

On 22/11/17 17:24, Larry Gritz wrote:

On Nov 22, 2017, at 9:00 AM, Bob Friesenhahn

> <bfriesen@simple.dallas.tx.us <mailto: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 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

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

searchability/findability of the project and canonical source.

Unfortunately the "libtiff" and "tiff" project names are taken on github. "tiff" is also taken on gitlab by a Tiffany, but "libtiff" https://gitlab.com/libtiff showed a 404. I've just registered it to avoid that being taken/squatted as well. gitlab also does the same type of website hosting offered by github, and is more featureful in some ways.

If this is something which would be useful to adopt, happy to transfer ownership/admin of this group to the relevant people. You just need to register an account (or use an existing github one), and then join the group I think. Or I can add you by hand given an account name, and make you the owner.

We already have an unofficial git mirror. Making gitlab an official source repository can be done by re-running the CVS conversion with a full set of username->email mappings (which I posted a few months back).

  Should be doable in a few hours, should this be generally acceptable.

I can set it up as a mirror in the interim for people to have a look at, but it won't be usable for opening merge requests until CVS is abandoned as the canonical source repository and the mirroring is turned off.

Just my 2p, I'd absolutely love to move off CVS as an occasional contributor. This is the only project I use still using CVS, and it's painful to use after a 14 year gap. Moving to git will make tracking changes and making changes vastly simpler for contributors and users.