PSC #016 2021-04-16
Present: Rik, Neil
We reviewed outstanding actions on our todo list, which we've not reviewed for a few weeks, due to Perl 7 discussions and recent events. We briefly checked in on a number of topics that we'll revisit in later weeks, such as trim.
The nomination period for the open position on the Steering Council ends at 10pm EST on Tuesday 20th April. David Golden is running this process, and will communicate the next step on Tuesday night.
J.D. Lightsey has stepped down from the role of Perl Security Lead (if you're not aware, there's a security team, which deals with reports of security issues, CVEs, etc), after being in the role for a year or so. We thank him for his work. Given there hasn't been a lot for the security team to field recently, we decided the PSC will act as the lead for now (previously we didn't have a dedicated lead), but put this on our list of topics to revisit down the road.
Things remain on track for the impending release: Todd Rinaldo is doing 5.33.9, which he'll be releasing on the 20th. We'll then be entering the final code freeze. Rik will be talking to Sawyer to ensure a smooth progression to 5.34.0.
Following the decision to go with "use v7", we now need to work out what 7.0 is going to look like. Given we're going to be pushing adoption of "use v7", and will also be making noise about Perl 7, we want to provide some real bang for your buck. We came up with a list of topics to raise individually on p5p, to help us work out the definition of Perl 7 together. Neil will kick off those discussions.
In the shorter term, Rik will start the ball rolling on what's going to be in 5.35, so we can keep the train moving forward.
Following our email earlier this week, we talked about some of the behaviours we think need to change on p5p. This is not only about hostility/tone, but wanting to improve the quality of the discussion, so signal-to-noise ratio, broader participation, etc. Over the coming weeks we'll introduce different aspects of this, and plan to start nudging behaviour on-list (and on GitHub). We've started reading on this topic, and welcome pointers to resources for this, but send them to us please (steering-council@perl.org). This topic is a tar pit for bike-shedding, so please be considerate if you do join the discussion on this topic.
Present: Rik, Neil
We reviewed outstanding actions on our todo list, which we've not reviewed for a few weeks, due to Perl 7 discussions and recent events. We briefly checked in on a number of topics that we'll revisit in later weeks, such as trim.
The nomination period for the open position on the Steering Council ends at 10pm EST on Tuesday 20th April. David Golden is running this process, and will communicate the next step on Tuesday night.
J.D. Lightsey has stepped down from the role of Perl Security Lead (if you're not aware, there's a security team, which deals with reports of security issues, CVEs, etc), after being in the role for a year or so. We thank him for his work. Given there hasn't been a lot for the security team to field recently, we decided the PSC will act as the lead for now (previously we didn't have a dedicated lead), but put this on our list of topics to revisit down the road.
Things remain on track for the impending release: Todd Rinaldo is doing 5.33.9, which he'll be releasing on the 20th. We'll then be entering the final code freeze. Rik will be talking to Sawyer to ensure a smooth progression to 5.34.0.
Following the decision to go with "use v7", we now need to work out what 7.0 is going to look like. Given we're going to be pushing adoption of "use v7", and will also be making noise about Perl 7, we want to provide some real bang for your buck. We came up with a list of topics to raise individually on p5p, to help us work out the definition of Perl 7 together. Neil will kick off those discussions.
In the shorter term, Rik will start the ball rolling on what's going to be in 5.35, so we can keep the train moving forward.
Following our email earlier this week, we talked about some of the behaviours we think need to change on p5p. This is not only about hostility/tone, but wanting to improve the quality of the discussion, so signal-to-noise ratio, broader participation, etc. Over the coming weeks we'll introduce different aspects of this, and plan to start nudging behaviour on-list (and on GitHub). We've started reading on this topic, and welcome pointers to resources for this, but send them to us please (steering-council@perl.org). This topic is a tar pit for bike-shedding, so please be considerate if you do join the discussion on this topic.