AWARE [SYSTEMS]
AWare Systems, , Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
June 2017

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



New Datamatrix section



Valid HTML 4.01!



Thread

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

2017.06.10 01:56 "Re: [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>
Date:  Friday, June 9, 2017 at 7:15 PM
To:  Roger Leigh <rleigh@codelibre.net>
Cc:  <tiff@lists.maptools.org>
Subject:  Re: [Tiff] [PATCH] Unix/Linux CI support for GitHub and Travis

> 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

 

 

-- 

Spatialys - Geospatial professional services

http://www.spatialys.com
_______________________________________________ Tiff mailing list:
Tiff@lists.maptools.org http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/