Even,
Have you considered sending out a Poll so as to allow people to vote? For
what it is worth I think the steering committee is a great idea.
Cheers,
Jeremy
-----Original Message-----
From: Tiff <[email protected]> On Behalf Of
[email protected]
Sent: Tuesday, March 5, 2024 2:21 AM
To: [email protected]
Subject: Tiff Digest, Vol 60, Issue 1
Send Tiff mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osgeo.org/mailman/listinfo/tiff
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re:
Contents of Tiff digest..."
Today's Topics:
1. Re: Proposition for the creation of a libtiff project
steering committee (Even Rouault)
2. Re: Proposition for the creation of a libtiff project
steering committee (Frank Warmerdam)
3. new release of checkit_tiff, a fast conformance checker for
baseline TIFFs (Romeyke, Andreas)
----------------------------------------------------------------------
Message: 1
Date: Tue, 5 Mar 2024 00:46:19 +0100
From: Even Rouault <[email protected]>
To: [email protected]
Subject: Re: [Tiff] Proposition for the creation of a libtiff project
steering committee
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi,
No other reactions? I know that procedural topics aren't particularly exciting,
but we'd probably welcome a bit more support from the community (at least the
part reading those emails) before formally bootstrapping the PSC.
Best regards,
Even
Le 27/02/2024 ? 16:07, Even Rouault via Tiff a ?crit?:
> Dear libtiff community,
>
> The libtiff project has run for many years without a formal governing
> body, and while it has worked well for most of the time, when
> difficult non-consensual decisions have to be made, it has showed its
> limits. Recently this was the case for the removal in the default
> build of the retired TIFF command line utilities. Hence with a group
> of other stakeholders including me, Su Laus, Bob Friesenhahn, Leonard
> Rosenthol, Roger Leigh, Olivier Paquet and Timothy Lyanguzov, we are
> proposing to form a Project Steering Committee (PSC) for libtiff, with
> us as the initial members of the PSC. That committee would have voting
> powers to make decisions on behalf of the project. This is a structure
> that is heavily used in most of the projects affiliated with the Open
> Source Geospatial Foundation (OSGeo) in the geospatial field where I'm
> involved. A rather successful model for the working and scope of such
> a committee is for example the one used by the GDAL
> (https://gda/
> l.org%2Fdevelopment%2Frfc%2Frfc1_pmc.html&data=05%7C02%7Cjeremy.bennet
> t%40siemens.com%7Cf7300298fe744171db3508dc3ced2cba%7C38ae3bcd95794fd4a
> ddab42e1495d55a%7C1%7C0%7C638452236582280983%7CUnknown%7CTWFpbGZsb3d8e
> yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%
> 7C%7C%7C&sdata=%2Bd2lhJ1U4TArF2869dhi%2FYVA4oXD3rvLVsCZ%2FmGFI1s%3D&re
> served=0) and MapServer
> (https://map/
> server.org%2Fdevelopment%2Frfc%2Fms-rfc-23.html&data=05%7C02%7Cjeremy.
> bennett%40siemens.com%7Cf7300298fe744171db3508dc3ced2cba%7C38ae3bcd957
> 94fd4addab42e1495d55a%7C1%7C0%7C638452236582288241%7CUnknown%7CTWFpbGZ
> sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> D%7C0%7C%7C%7C&sdata=MFT%2BqUlqsOlw80P0MJYkbG1Xwcn00k2UVSGm1%2FeCRGc%3
> D&reserved=0) projects since 2007
>
> Those rules have served well those projects in the last 17 years, and?
> can handle situations where PSC members become inactive without
> formally? resigning (the PSC can of course also decide to formally
> remove members that no longer participate). So we are considering
> taking strong inspiration from them for the working of the libtiff PSC
> . In the adaptations that have been discussed between us, the 2
> business day minimum delay indicated for formal votes is probably too
> short given libtiff usual pace and could be extended to 5. For GDAL
> and MapServer, we also traditionally put adoption of release
> candidates as final approved releases to a PSC vote.? It could be
> discussed if we'd want to do that for libtiff too. For the concrete
> mode of operation, typically in GDAL, when a formal decision has to be
> made, there is a first round of emails "Call for discussion: topic
> XXXX", and once the discussion seems to have come to a conclusion
> there's a "Motion: decision XXXX" where PSC members cast their +1, +0,
> 0, -0, -1 votes.
>
> One advantage of the PSC is that difficult decisions are made on
> behalf on the group, which avoids them to be borne by individuals.
> Having a PSC doesn't obviously exclude trying to reach consensus among
> the broader community. Not everything needs to be formally discussed
> and voted. Normal bug-fixing or "small" new features can be dealt in
> merge requests as usual, and don't require email traffic. But removing
> tools or functionality, break of backward compatibility, or
> significant addition of new functionality are topics for discussion
> and formal votes.
>
> So, this email is to gather feedback from the libtiff community at
> large to check if the idea of a PSC, and its proposed initial
> membership, makes sense. If people would like to be included to the
> initial PSC, they can (possibly privately) reach to us, so we can
> discuss this possibility.
>
> Best regards,
> --
> http://www.s/
> patialys.com%2F&data=05%7C02%7Cjeremy.bennett%40siemens.com%7Cf7300298
> fe744171db3508dc3ced2cba%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C
> 638452236582293230%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo
> iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=DQVexdXjFdg
> ocuOqwo9ZDA7isexxLLU418H9mAzHNi4%3D&reserved=0
> My software is free, but my time generally not.
>
> _______________________________________________
> Tiff mailing list
> [email protected]
> https://list/
> s.osgeo.org%2Fmailman%2Flistinfo%2Ftiff&data=05%7C02%7Cjeremy.bennett%
> 40siemens.com%7Cf7300298fe744171db3508dc3ced2cba%7C38ae3bcd95794fd4add
> ab42e1495d55a%7C1%7C0%7C638452236582298379%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C
> %7C%7C&sdata=gb1PSQzFany0LcInXQpmY5H5tce8SGaNq59r0ulVNZU%3D&reserved=0
--
http://www.spatialys.com/
My software is free, but my time generally not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/tiff/attachments/20240305/74bf386a/attachment.htm>
------------------------------
Message: 2
Date: Mon, 4 Mar 2024 23:38:42 -0500
From: Frank Warmerdam <[email protected]>
To: Even Rouault <[email protected]>
Cc: "[email protected]" <[email protected]>, "Lyanguzov,
Timothy" <[email protected]>
Subject: Re: [Tiff] Proposition for the creation of a libtiff project
steering committee
Message-ID:
<CA+YzLBezXz2Y7XCmPrnPxza51QJp97xr=t2948gl3cgcey+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Even,
I support this move!
Best regards,
Frank
On Tue, Feb 27, 2024 at 10:08?AM Even Rouault via Tiff <[email protected]>
wrote:
> Dear libtiff community,
>
> The libtiff project has run for many years without a formal governing
> body, and while it has worked well for most of the time, when
> difficult non-consensual decisions have to be made, it has showed its limits.
> Recently this was the case for the removal in the default build of the
> retired TIFF command line utilities. Hence with a group of other
> stakeholders including me, Su Laus, Bob Friesenhahn, Leonard
> Rosenthol, Roger Leigh, Olivier Paquet and Timothy Lyanguzov, we are
> proposing to form a Project Steering Committee (PSC) for libtiff, with
> us as the initial members of the PSC. That committee would have voting
> powers to make decisions on behalf of the project. This is a structure
> that is heavily used in most of the projects affiliated with the Open
> Source Geospatial Foundation (OSGeo) in the geospatial field where I'm
> involved. A rather successful model for the working and scope of such
> a committee is for example the one used by the GDAL (
> https://gdal/
> .org%2Fdevelopment%2Frfc%2Frfc1_pmc.html&data=05%7C02%7Cjeremy.bennett
> %40siemens.com%7Cf7300298fe744171db3508dc3ced2cba%7C38ae3bcd95794fd4ad
> dab42e1495d55a%7C1%7C0%7C638452236582314825%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7
> C%7C%7C&sdata=AyGVfpUkzcOhTfsYSBTo4MWlnLOLvDYTqb396Wsv1iw%3D&reserved=
> 0) and MapServer (
> https://maps/
> erver.org%2Fdevelopment%2Frfc%2Fms-rfc-23.html&data=05%7C02%7Cjeremy.b
> ennett%40siemens.com%7Cf7300298fe744171db3508dc3ced2cba%7C38ae3bcd9579
> 4fd4addab42e1495d55a%7C1%7C0%7C638452236582319305%7CUnknown%7CTWFpbGZs
> b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
> %7C0%7C%7C%7C&sdata=jJyCGSseXcLUWCWQzeNuasMK23LR60v%2FWOyQT9O1W6k%3D&r
> eserved=0 ) projects since 2007
>
> Those rules have served well those projects in the last 17 years, and
> can handle situations where PSC members become inactive without
> formally resigning (the PSC can of course also decide to formally
> remove members that no longer participate). So we are considering
> taking strong inspiration from them for the working of the libtiff PSC
> . In the adaptations that have been discussed between us, the 2
> business day minimum delay indicated for formal votes is probably too
> short given libtiff usual pace and could be extended to 5. For GDAL
> and MapServer, we also traditionally put adoption of release
> candidates as final approved releases to a PSC vote. It could be
> discussed if we'd want to do that for libtiff too. For the concrete
> mode of operation, typically in GDAL, when a formal decision has to be
> made, there is a first round of emails "Call for
> discussion: topic XXXX", and once the discussion seems to have come to
> a conclusion there's a "Motion: decision XXXX" where PSC members cast
> their
> +1, +0, 0, -0, -1 votes.
>
> One advantage of the PSC is that difficult decisions are made on
> behalf on the group, which avoids them to be borne by individuals.
> Having a PSC doesn't obviously exclude trying to reach consensus among
> the broader community. Not everything needs to be formally discussed
> and voted. Normal bug-fixing or "small" new features can be dealt in
> merge requests as usual, and don't require email traffic. But removing
> tools or functionality, break of backward compatibility, or
> significant addition of new functionality are topics for discussion and
> formal votes.
>
> So, this email is to gather feedback from the libtiff community at
> large to check if the idea of a PSC, and its proposed initial
> membership, makes sense. If people would like to be included to the
> initial PSC, they can (possibly privately) reach to us, so we can discuss
> this possibility.
>
> Best regards,
>
> --
> http://www.s/
> patialys.com%2F&data=05%7C02%7Cjeremy.bennett%40siemens.com%7Cf7300298
> fe744171db3508dc3ced2cba%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C
> 638452236582324340%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo
> iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=72nfefUXxBI
> QQTvHEnoFUL5AeryWWMtaLg4ec4eAUb8%3D&reserved=0
> My software is free, but my time generally not.
>
> _______________________________________________
> Tiff mailing list
> [email protected]
> https://list/
> s.osgeo.org%2Fmailman%2Flistinfo%2Ftiff&data=05%7C02%7Cjeremy.bennett%
> 40siemens.com%7Cf7300298fe744171db3508dc3ced2cba%7C38ae3bcd95794fd4add
> ab42e1495d55a%7C1%7C0%7C638452236582329671%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C
> %7C%7C&sdata=0aEyKe3ApeuEWP2r3IkTZpufRCG3S8TJEURt35PlfOg%3D&reserved=0
>
--
---------------------------------------+--------------------------------
---------------------------------------+------
I set the clouds in motion - turn up | Frank Warmerdam,
[email protected]
light and sound - activate the windows | USA: +1 650-701-7823
<http://voice.google.com/calls?a=nc,%2B16507017823>
and watch the world go round - Rush | CAN: +1 343-550-9984
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.osgeo.org/pipermail/tiff/attachments/20240304/c836c1ee/attachment.htm>
------------------------------
Message: 3
Date: Tue, 5 Mar 2024 08:20:42 +0000
From: "Romeyke, Andreas" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [Tiff] new release of checkit_tiff, a fast conformance
checker for baseline TIFFs
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi,
checkit_tiff version 1.5.0 "deep funky funk" is now available.
checkit_tiff is a conformance checker for baseline TIFFs and is one of the
fastest TIFF validators (1751 TIFFs in 2.75s on Core i7, 4.8Ghz)
New features:
- With version 1.5.0, recursive scanning of directories is supported for
the first time ("-D" option)
- baseline IFD (IFD0) and tag-based IFDs are also checked for empty IFDs
(tag count = 0) in "mode(enable_ifd_checks)".
- baseline IFD (IFD0) and also tag-based IFDs are checked in
"mode(enable_ifd_checks)" for offsets that are outside the file size
Side note: Both of the checks mentioned are not yet supported by ?dpfmanager??.
Error images at Imagemagick results in messages:
- "display-im6.q16: Sanity check on directory count failed, zero tag
directories not supported. `TIFFFetchDirectory' @ error/tiff.c/TIFFErrors/603.
display-im6.q16: Failed to read custom directory at offset 30944552.
`TIFFReadCustomDirectory' @ error/tiff.c/TIFFErrors/603."
- " display-im6.q16: Sanity check on directory count failed, this is
probably not a valid IFD offset. `TIFFFetchDirectory' @
error/tiff.c/TIFFErrors/603. display-im6.q16: Failed to read custom directory
at offset 30944164. `TIFFReadCustomDirectory' @ error/tiff.c/TIFFErrors/603."
Bug fixes:
- Improvement in memory handling
- Modernization in cmake (compile environment detection, support ninja,
clang-tidy, etc.)
The JS variant and TAR-ball are available at
http://andreas-romeyke.de/software.html#_checkit_tiff
The release is available in the repository at
https://git.fsfe.org/art1pirat/checkit_tiff/releases.
I would appreciate any feedback!
Best regards Andreas
?dpfmanager is a conformance checker for TIFF that was developed as part of
Preforma.
--
team member ?long-term preservation?
Saxon State- and University Library Dresden (SLUB) Department 2 (IT), Division
2.3 (infrastructure and digital long-term preservation) Zellescher Weg 18 |
01069 Dresden
phone: +49 351 4677 763
E-Mail: [email protected]
http://www.slub-dresden.de/ | @slubdresden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6944 bytes
Desc: not available
URL:
<http://lists.osgeo.org/pipermail/tiff/attachments/20240305/20566041/attachment.bin>
------------------------------
Subject: Digest Footer
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff
------------------------------
End of Tiff Digest, Vol 60, Issue 1
***********************************
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff
