Re: CALL FOR DISCUSSION (continued): PNG Registration Process 20170125

Glenn Randers-Pehrson <[email protected]>
Newsgroups gmane.comp.graphics.png.general
Message-ID <CA+PdXcuSdTKMJxP+v6kxytupgEqPQw+7iO1F585iKFjW6-5y=g@mail.gmail.com>
On Sun, Jan 29, 2017 at 6:50 PM, John Bowler <
[email protected]> wrote:

>
> ,,,I therefore suggest an I hope non-disruptive modification, to wit:
>
> 1) A proposal is submitted in a form of the proposers choice to the
> png-mng-misc discussion list.
> 2) At any point thereafter the proposer may submit a formal call for
> discussion.
> 3) At a point between 14 and 28 days after a formal call for
> discussion a proposer may issue a call for votes.
> 4) The vote shall be on the proposal exactly as submitted for the call
> for discussion; no changes, however minor, are permitted.
>

I believe the discussion period should allow changes to the proposal;
otherwise
what's the point of the discussion period?  It would be the same as an
"RFC" which is anything but an actual request for comments.

The current registration proposal says that the proposal must not change
during the final two weeks of the discussion period (i.e., if there are
changes, the two-week clock is restarted).  In general that works.  In the
present examples, eXIf zXIf, it has introduced a 4 and 14 day delay
(initial CFD 14 Jan, final CFDs 19 Jan and 28 Jan).

Even APNG, which ultimately failed, only had a four-week discussion period
with several drafts of the CFD over the span of four weeks, with
significant improvements to the proposal during that time.

I think that's OK.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
png-mng-misc mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/png-mng-misc
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.