PSR-20 Clock status
112 views
Skip to first unread message
Larry Garfield
Jul 3, 2022, 1:15:37 PM7/3/22
to PHP-FIG
The PSR-20 working group has been inactive for many months now (it's been 10 months since any changes to the spec document[1]), far longer than the allowed time for a working group to be inactive. The Editor, Chris Seufert, has been inactive and unreachable via Discord in the WG's channel for several months. The Sponsor, Chuck Burgess, has also not responded to messages on Discord in the WG's channel.
Per the bylaws[2]:
-----
The Editor or Sponsor of a Working Group may step down at any time by informing the Core Committee via the mailing list. If the departing individual specifies an intended replacement from the Working Group membership, that individual will assume the vacant role immediately, by Implicit Approval. If necessary, a Decision Vote to appoint a new Editor or Sponsor may be held following a suitable nomination period.
Should a Working Group be missing an Editor for 60 days; be missing a Sponsor for 60 days; have insufficient active members for 60 days; or show no signs of activity for six months, then the Core Committee may hold a Decision Vote to name a new Editor or Sponsor, following a suitable nomination process. One of the options in that Decision Vote must be to dissolve the Working Group. If no suitable candidates for Editor or Sponsor may be found, then the Working Group is automatically dissolved.
-----
At this time, the PSR-20 WG is inactive. There are four possible next steps:
1. The Sponsor becomes active again and nominates a new Editor who can complete the PSR and bring it to a vote. If there is a dispute over who the Editor should be, the CC will hold a Decision Vote.
2. The Sponsor may step down as Sponsor, in which case a new Sponsor from the CC will need to step forward. If there is a dispute over who the Editor should be, the CC will hold a Decision Vote. The new Sponsor will then take step 1.
3. Neither the Sponsor nor Editor are heard from, so the CC appoints a new Sponsor and Editor by Decision Vote.
4. The working group is dissolved and PSR-20 is listed as abandoned.
Of note: Other current members of the working group[3] are eligible to be the new Editor, but the Sponsor must be a member of the Core Committee.
If nothing happens within 2 weeks, I believe we should declare option 4 enacted by default and the WG abandoned.
(I would personally like to avoid option 4, as I really do believe this spec is valuable and should be completed.)
[1] https://github.com/php-fig/fig-standards/tree/master/proposed
[2] https://www.php-fig.org/bylaws/mission-and-structure/#working-group-management
[3] https://github.com/php-fig/fig-standards/blob/master/proposed/clock-meta.md#53-working-group-members
--
Larry Garfield
la...@garfieldtech.com
Per the bylaws[2]:
-----
The Editor or Sponsor of a Working Group may step down at any time by informing the Core Committee via the mailing list. If the departing individual specifies an intended replacement from the Working Group membership, that individual will assume the vacant role immediately, by Implicit Approval. If necessary, a Decision Vote to appoint a new Editor or Sponsor may be held following a suitable nomination period.
Should a Working Group be missing an Editor for 60 days; be missing a Sponsor for 60 days; have insufficient active members for 60 days; or show no signs of activity for six months, then the Core Committee may hold a Decision Vote to name a new Editor or Sponsor, following a suitable nomination process. One of the options in that Decision Vote must be to dissolve the Working Group. If no suitable candidates for Editor or Sponsor may be found, then the Working Group is automatically dissolved.
-----
At this time, the PSR-20 WG is inactive. There are four possible next steps:
1. The Sponsor becomes active again and nominates a new Editor who can complete the PSR and bring it to a vote. If there is a dispute over who the Editor should be, the CC will hold a Decision Vote.
2. The Sponsor may step down as Sponsor, in which case a new Sponsor from the CC will need to step forward. If there is a dispute over who the Editor should be, the CC will hold a Decision Vote. The new Sponsor will then take step 1.
3. Neither the Sponsor nor Editor are heard from, so the CC appoints a new Sponsor and Editor by Decision Vote.
4. The working group is dissolved and PSR-20 is listed as abandoned.
Of note: Other current members of the working group[3] are eligible to be the new Editor, but the Sponsor must be a member of the Core Committee.
If nothing happens within 2 weeks, I believe we should declare option 4 enacted by default and the WG abandoned.
(I would personally like to avoid option 4, as I really do believe this spec is valuable and should be completed.)
[1] https://github.com/php-fig/fig-standards/tree/master/proposed
[2] https://www.php-fig.org/bylaws/mission-and-structure/#working-group-management
[3] https://github.com/php-fig/fig-standards/blob/master/proposed/clock-meta.md#53-working-group-members
--
Larry Garfield
la...@garfieldtech.com
Alessandro Lai
Jul 5, 2022, 4:17:48 AM7/5/22
to PHP Framework Interoperability Group
What's the status on the spec? IIRC is basically complete, right? We just need to push it to the approval vote...
It would be a shame to abandon it now, when it's so close to the finish line...
Andreas Heigl
Jul 5, 2022, 4:58:28 AM7/5/22
to php...@googlegroups.com
On 05.07.22 10:17, Alessandro Lai wrote:
> What's the status on the spec? IIRC is basically complete, right? We just
> need to push it to the approval vote...
The spec is in the same state as it was almost a year ago. Since then I
have tried at least twice to get it towards an approval vote but neither
the sponsor or the editor were responding nor was the CC taking any actions.
In at least the last try from my side to get to a readiness vote was
also the option contained to take over the responsibility of the PSR.
There has been no response whatsoever regarding that.
Cheers
Andreas
,,,
(o o)
+---------------------------------------------------------ooO-(_)-Ooo-+
| Andreas Heigl |
| mailto:and...@heigl.org N 50°22'59.5" E 08°23'58" |
| https://andreas.heigl.org |
+---------------------------------------------------------------------+
| https://hei.gl/appointmentwithandreas |
+---------------------------------------------------------------------+
Chuck Burgess
Jul 5, 2022, 7:30:18 AM7/5/22
to php...@googlegroups.com
Sorry folks... if there was another email thread on this trying to move it along, I somehow missed it... and if Discord was deemed the official replacement to replace the email group for such communications, I must have missed it too... I haven't had enough space in my office area to keep my OSS laptop open 24x7 like I used to do.
I'll catch things up in the next week or so... I have something going on late this week that will get in the way, which is why I think it could take me into next week to catch things up.
CRB
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/810d4c14-20e5-07d9-14ea-6d1eb3bbad78%40heigl.org.
Larry Garfield
Jul 19, 2022, 6:18:42 PM7/19/22
to PHP-FIG
Chuck Burgess
Jul 19, 2022, 6:26:05 PM7/19/22
to php...@googlegroups.com
After the progress Chris and I made since Sunday, I want to do one more read-over, possibly a wording PR... and then see if he as Editor is ready for the next formal step.
CRB
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/a499036d-e132-4786-a547-371a4ae585c1%40www.fastmail.com.
Larry Garfield
Jul 20, 2022, 9:49:09 AM7/20/22
to PHP-FIG
Great. When last I looked at it, I still had concerns around the UTC question. "Undefined behavior" bothers me, and even with the added text I wasn't fully convinced that leaving the timezone undefined was the right call. Other than that it seemed fine to me.
--
Larry Garfield
la...@garfieldtech.com
>> To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com <mailto:php-fig%2Bunsu...@googlegroups.com>.
> <https://groups.google.com/d/msgid/php-fig/CANsgjnvOveHXn1vFObA6dyP37%3DwvpiCKPBohY_1MOjcC0nFMKw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
Larry Garfield
la...@garfieldtech.com
>> To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/a499036d-e132-4786-a547-371a4ae585c1%40www.fastmail.com.
>
> --
> You received this message because you are subscribed to the Google
> Groups "PHP Framework Interoperability Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to php-fig+u...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/php-fig/CANsgjnvOveHXn1vFObA6dyP37%3DwvpiCKPBohY_1MOjcC0nFMKw%40mail.gmail.com
>
> --
> You received this message because you are subscribed to the Google
> Groups "PHP Framework Interoperability Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to php-fig+u...@googlegroups.com.
> To view this discussion on the web visit
> <https://groups.google.com/d/msgid/php-fig/CANsgjnvOveHXn1vFObA6dyP37%3DwvpiCKPBohY_1MOjcC0nFMKw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
Chuck Burgess
Jul 23, 2022, 12:01:05 PM7/23/22
to php...@googlegroups.com
My rewording PR for the timezone FAQ section is up, in case you want to review it. I did not expand on any ideas already there... just tried to tighten up the phrasing.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/edd810da-f1a3-4409-b081-d28cb189300d%40www.fastmail.com.
Chuck Burgess
Jul 23, 2022, 12:36:49 PM7/23/22
to php...@googlegroups.com
On the timezone being undefined... the UNIX timestamp integer returned by DateTimeImmutable->getTimestamp() gives a reliably unique value for an instant in time, and the only effect a timezone has on that value is a format string you can retrieve based on that integer timestamp, right? So it's not that you have an ambiguous value in hand... it's just that the interface doesn't demand it present its "string value" in a single way... right?
Chuck Burgess
Aug 4, 2022, 2:11:35 PM8/4/22
to php...@googlegroups.com
Given no further discussion, I'm trying to reach the Editor via Github and Discord (and here, if you see this, Chris Seufert) to get his ok on a readiness vote.
CRB
Chuck Burgess
Aug 10, 2022, 6:32:17 AM8/10/22
to php...@googlegroups.com
Chris,
If you'll send me (my handle at php.net) your email address, I can send you the readiness vote draft. You can then send it out officially as Editor.
Working Group,
If you can check in on the Discord channel, maybe we can get this effort going again.
CRB
Reply all
Reply to author
Forward
0 new messages