<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi,</p>
<p>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.</p>
<p>Best regards,</p>
<p>Even<br>
</p>
<div class="moz-cite-prefix">Le 27/02/2024 à 16:07, Even Rouault via
Tiff a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:36e0314c-0b9e-42ba-a7a3-55f7c43e142d@spatialys.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div aria-live="assertive" id="magicdomid2" class="ace-line"
spellcheck="true"><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">Dear
libtiff community,</span></div>
<div aria-live="assertive" id="magicdomid3" class="ace-line"
spellcheck="true"><br>
</div>
<div aria-live="assertive" id="magicdomid4" class="ace-line"
spellcheck="true"><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">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 (</span><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp url"><a
href="https://gdal.org/development/rfc/rfc1_pmc.html"
rel="noreferrer noopener" class="moz-txt-link-freetext"
moz-do-not-send="true">https://gdal.org/development/rfc/rfc1_pmc.html</a></span><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">) and
MapServer (</span><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp url"><a
href="https://mapserver.org/development/rfc/ms-rfc-23.html"
rel="noreferrer noopener" class="moz-txt-link-freetext"
moz-do-not-send="true">https://mapserver.org/development/rfc/ms-rfc-23.html</a></span><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp"> )
projects since 2007</span></div>
<div aria-live="assertive" id="magicdomid5" class="ace-line"
spellcheck="true"><br>
</div>
<div aria-live="assertive" id="magicdomid6" class="ace-line"
spellcheck="true"><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">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. </span></div>
<div aria-live="assertive" id="magicdomid7" class="ace-line"
spellcheck="true"><br>
</div>
<div aria-live="assertive" id="magicdomid8" class="ace-line"
spellcheck="true"><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">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. </span></div>
<div aria-live="assertive" id="magicdomid9" class="ace-line"
spellcheck="true"><br>
</div>
<div aria-live="assertive" id="magicdomid10" class="ace-line"
spellcheck="true"><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">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.</span></div>
<div aria-live="assertive" id="magicdomid11" class="ace-line"
spellcheck="true"><br>
</div>
<div aria-live="assertive" id="magicdomid12" class="ace-line"
spellcheck="true"><span
class="author-a-dz79zz80zz74zz72zbkrz83zz89zk3x9bp">Best
regards,</span></div>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com"
moz-do-not-send="true">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Tiff mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tiff@lists.osgeo.org">Tiff@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/tiff">https://lists.osgeo.org/mailman/listinfo/tiff</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>