AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2017.06.07 22:30 "[Tiff] [PATCH] Windows CI support for GitHub and AppVeyor", by Roger Leigh
2017.06.08 09:47 "Re: [Tiff] [PATCH] Windows CI support for GitHub and AppVeyor", by
2017.06.09 10:54 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by
2017.06.08 11:22 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by
2017.06.08 20:46 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Even Rouault
2017.06.09 11:12 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Even Rouault
2017.06.09 13:18 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Bob Friesenhahn
2017.06.09 21:10 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Roger Leigh
2017.06.09 21:23 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Even Rouault
2017.06.09 22:00 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Roger Leigh
2017.06.09 22:05 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Aaron Boxer
2017.06.09 23:15 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Even Rouault
2017.06.10 01:56 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Kemp Watson
2017.06.10 08:58 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Roger Leigh
2017.06.10 09:33 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Even Rouault

2017.06.10 01:56 "Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis", by Kemp Watson

I¹ve made this offer to the list before, but here it is again:

We (Objective Pathology) work heavily with libTIFF for it¹s BigTIFF features which are important

in our digital pathology field. We will be open-sourcing our own BigTIFF subspec/flavour designed

for interactive online viewing fairly soon ­ it¹s already fairly widely in use.

We own Organization BigTIFF on GitHub, and domains tiff.photo, tiff.rocks, libtiff.online, and bigtiffŠ

   .net .ca .us .photo .info .rocks .asia .desi .eu .lat .online;
bigtiff.org is owned by an associate company.

Maybe something could be done with one or several., like hosting libtiff under BigTIFF/libTIFF or some such.

No agenda other than a bit of credit for our company for supporting the project, not dissimilar to

the current support from Aware, OSGeo, Remote Sensing, Simple Systems, who knows whatŠ all very confusing

now as the domains have been lost/hijacked several times.

We maintain close to 300 domains, and the site would be accelerated through a paid Cloudflare CDN account

with bandwidth paid by us if not on GitHub.

I do feel strongly that it¹s time to move libtiff away from CVS and over to Git, and it¹s my personal

opinion that GitHub offers the most value overall for open-source projects.

What¹s the scoop with libtiff.org? That would certainly be the most sensible home.

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

From: <tiff-bounces@lists.maptools.org> on behalf of Even Rouault <even.rouault@spatialys.com>

That doesn't sound good, hope they regain access soon. Related to that, is there any plan to move fully over to git? The existing mirror works pretty well; all my recent patches are generated directly with it. Could we create a libtiff organisation on GitHub or GitLab? Unfortunately, "libtiff" is taken on github, as is "tiff". But libtiff is available on GitLab.

I've sent a query to github to see if they can get libtiff back for the project (as the existing account seems to have no recent activity since 3 years).

I've attached the patches to invoke the script directly (0002) plus the original fixes (0001).

Applied