Perl Steering Council, meeting #002, 2020-01-12

--9e2e674c70324f8e933e96ec54abfde1
Content-Type: text/plain

(Gosh, Neil, I dunno about this precedent of numbering the meetings.  We're going to miss a number at some point and then we'll be sorry.)

Today, Neil and Sawyer and I had our second PSC meeting.  We're still establishing short and long term agenda items, with some top agenda items including:
 1. how do we encourage good interactions on p5p to take us forward in making decisions
 2. what are the principles guiding these decisions (especially at the PSC level)
 3. what is the process for going from "I have an idea for changing Perl" to "I merged it!"
Regarding the two items mentioned by Neil last time:

First was "how are PRs reviewed and merged?".  We wrote up a basic explanation of how we plan to simplify this process,  we think it's a good start, and I'll post a separate email about it soon.

The second was related to TPF grants.  There's no real problem here, we only want to make sure that TPF grants that require approval from the project management (traditionally the Perl 5 Core Maint. grants) can be approved by any of the three of us.  This is a small procedural matter that I'll chase down.

We'll keep p5p posted as we move along, and I hope we'll have some good first-order answers to #2 and #3 above, which are things that a lot of people are asking about.

-- 
rjbs
--9e2e674c70324f8e933e96ec54abfde1
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>(Gosh, Nei=
l, I dunno about this precedent of numbering the meetings.&nbsp; We're g=
oing to miss a number at some point and then we'll be sorry.)<br></div><=
div><br></div><div>Today, Neil and Sawyer and I had our second PSC meeti=
ng.&nbsp; We're still establishing short and long term agenda items, wit=
h some top agenda items including:<br></div><ol><li>how do we encourage =
good interactions on p5p to take us forward in making decisions<br></li>=
<li>what are the principles guiding these decisions (especially at the P=
SC level)<br></li><li>what is the process for going from "I have an idea=
 for changing Perl" to "I merged it!"<br></li></ol><div>Regarding the tw=
o items mentioned by Neil last time:<br></div><div><br></div><div>First =
was "how are PRs reviewed and merged?".&nbsp; We wrote up a basic explan=
ation of how we plan to simplify this process,&nbsp; we think it's a goo=
d start, and I'll post a separate email about it soon.<br></div><div><br=
></div><div>The second was related to TPF grants.&nbsp; There's no real =
problem here, we only want to make sure that TPF grants that require app=
roval from the project management (traditionally the Perl 5 Core Maint. =
grants) can be approved by any of the three of us.&nbsp; This is a small=
 procedural matter that I'll chase down.<br></div><div><br></div><div>We=
'll keep p5p posted as we move along, and I hope we'll have some good fi=
rst-order answers to #2 and #3 above, which are things that a lot of peo=
ple are asking about.<br></div><div><br></div><div>--&nbsp;<br></div><di=
v>rjbs</div></body></html>
--9e2e674c70324f8e933e96ec54abfde1--
0
rjbs
1/12/2021 6:23:24 PM
perl.perl5.porters 48287 articles. 1 followers. Follow

10 Replies
378 Views

Similar Articles

[PageSpeed] 16
Get it on Google Play
Get it on Apple App Store

--000000000000d3e47e05b8b84cf9
Content-Type: text/plain; charset="UTF-8"

Hi *Ricardo*:

Please hold your meetings in public!

On Tue, Jan 12, 2021 at 6:23 PM Ricardo Signes <rjbs@manxome.org> wrote:

> (Gosh, Neil, I dunno about this precedent of numbering the meetings.
> We're going to miss a number at some point and then we'll be sorry.)
>
> Today, Neil and Sawyer and I had our second PSC meeting.  We're still
> establishing short and long term agenda items, with some top agenda items
> including:
>
>    1. how do we encourage good interactions on p5p to take us forward in
>    making decisions
>    2. what are the principles guiding these decisions (especially at the
>    PSC level)
>    3. what is the process for going from "I have an idea for changing
>    Perl" to "I merged it!"
>
> Regarding the two items mentioned by Neil last time:
>
> First was "how are PRs reviewed and merged?".  We wrote up a basic
> explanation of how we plan to simplify this process,  we think it's a good
> start, and I'll post a separate email about it soon.
>
> The second was related to TPF grants.  There's no real problem here, we
> only want to make sure that TPF grants that require approval from the
> project management (traditionally the Perl 5 Core Maint. grants) can be
> approved by any of the three of us.  This is a small procedural matter that
> I'll chase down.
>
> We'll keep p5p posted as we move along, and I hope we'll have some good
> first-order answers to #2 and #3 above, which are things that a lot of
> people are asking about.
>
> --
> rjbs
>


-- 
Thanks,

Phil <https://metacpan.org/author/PRBRENAN>

Philip R Brenan <https://metacpan.org/author/PRBRENAN>

--000000000000d3e47e05b8b84cf9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif">Hi <b>Ricardo</b>:</div><div class=3D"gmail_default" style=3D"fo=
nt-family:tahoma,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:tahoma,sans-serif">Please hold your meetings in public!<br>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Tue, Jan 12, 2021 at 6:23 PM Ricardo Signes &lt;<a href=3D"mailto:=
rjbs@manxome.org">rjbs@manxome.org</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><u></u><div><div>(Gosh, Neil, I dunno abo=
ut this precedent of numbering the meetings.=C2=A0 We&#39;re going to miss =
a number at some point and then we&#39;ll be sorry.)<br></div><div><br></di=
v><div>Today, Neil and Sawyer and I had our second PSC meeting.=C2=A0 We&#3=
9;re still establishing short and long term agenda items, with some top age=
nda items including:<br></div><ol><li>how do we encourage good interactions=
 on p5p to take us forward in making decisions<br></li><li>what are the pri=
nciples guiding these decisions (especially at the PSC level)<br></li><li>w=
hat is the process for going from &quot;I have an idea for changing Perl&qu=
ot; to &quot;I merged it!&quot;<br></li></ol><div>Regarding the two items m=
entioned by Neil last time:<br></div><div><br></div><div>First was &quot;ho=
w are PRs reviewed and merged?&quot;.=C2=A0 We wrote up a basic explanation=
 of how we plan to simplify this process,=C2=A0 we think it&#39;s a good st=
art, and I&#39;ll post a separate email about it soon.<br></div><div><br></=
div><div>The second was related to TPF grants.=C2=A0 There&#39;s no real pr=
oblem here, we only want to make sure that TPF grants that require approval=
 from the project management (traditionally the Perl 5 Core Maint. grants) =
can be approved by any of the three of us.=C2=A0 This is a small procedural=
 matter that I&#39;ll chase down.<br></div><div><br></div><div>We&#39;ll ke=
ep p5p posted as we move along, and I hope we&#39;ll have some good first-o=
rder answers to #2 and #3 above, which are things that a lot of people are =
asking about.<br></div><div><br></div><div>--=C2=A0<br></div><div>rjbs</div=
></div></blockquote></div><br clear=3D"all"><br>-- <br><div dir=3D"ltr" cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr">=
<div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div=
 dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"l=
tr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><div>=
<span style=3D"font-family:tahoma,sans-serif">Thanks,<br><br></span><div di=
r=3D"ltr"><span style=3D"font-family:tahoma,sans-serif"><a href=3D"https://=
metacpan.org/author/PRBRENAN" target=3D"_blank">Phil</a><br><br></span><div=
><a href=3D"https://metacpan.org/author/PRBRENAN" target=3D"_blank"><span s=
tyle=3D"font-family:tahoma,sans-serif">Philip R Brenan</span></a></div></di=
v></div></div></div></div></div></div></div></div></div></div></div></div><=
/div></div></div></div></div></div></div></div></div></div></div></div></di=
v></div></div></div></div></div></div></div></div>

--000000000000d3e47e05b8b84cf9--
0
philiprbrenan
1/12/2021 6:36:09 PM
On Tue, 12 Jan 2021 13:23:24 -0500
"Ricardo Signes" <rjbs@manxome.org> wrote:

>  3. what is the process for going from "I have an idea for changing
> Perl" to "I merged it!"

Thanks :) This one in particular is one I have a strongly vested
interest in seeing the outcome of.

To be clear - I don't have any strong opinions on *what* the process
should be, but I do really feel we need one. Once we have one I fully
intend to make a lot of use of it.

-- 
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk      |  https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/  |  https://www.tindie.com/stores/leonerd/
0
leonerd
1/12/2021 6:40:32 PM
--546a43ecc9c041aba451b80feb55d5b2
Content-Type: text/plain

On Tue, Jan 12, 2021, at 1:36 PM, Philip R Brenan wrote:
> Hi *Ricardo*:
> 
> Please hold your meetings in public!

No.

You'll get notes, which I expect will become better-kept and more detailed over time.  You'll get a description of actions planned and an explanation of justification and intent, but there will not be a recording of our every word and gesture.

This is final.

-- 
rjbs
--546a43ecc9c041aba451b80feb55d5b2
Content-Type: text/html

<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Tue, Jan 12, 2021, at 1:36 PM, Philip R Brenan wrote:<br></div><blockquote type="cite" id="qt" style=""><div dir="ltr"><div class="qt-gmail_default" style="font-family:tahoma, sans-serif;">Hi <b>Ricardo</b>:<br></div><div class="qt-gmail_default" style="font-family:tahoma, sans-serif;"><br></div><div class="qt-gmail_default" style="font-family:tahoma, sans-serif;">Please hold your meetings in public!<br></div></div></blockquote><div><br></div><div>No.<br></div><div><br></div><div>You'll get notes, which I expect will become better-kept and more detailed over time.&nbsp; You'll get a description of actions planned and an explanation of justification and intent, but there will not be a recording of our every word and gesture.</div><div><br></div><div>This is final.<br></div><div><br></div><div>--&nbsp;<br></div><div>rjbs</div></body></html>
--546a43ecc9c041aba451b80feb55d5b2--
0
rjbs
1/12/2021 6:59:19 PM
--0000000000008d3d0b05b8be3156
Content-Type: text/plain; charset="UTF-8"

Several points are considered.

Change target

- Document
- Test code
- Source code

Document

- Does the documentation explain the feature correctly?
- Direct commit possible

Test code

- Is the test code testing the feature correctly?
- Direct commit possible

Source code

- Bug fix
- Code cleanup
- Performance improvement
- Memory usage improvement
- Feature addition
- Feature modification or deletion

Bug fix

- Have the bugs been fixed? Do you have test code?
- Do all current tests pass?
- Do that negative impact on performance or memory usage?
- Is backwards compatibility kept at the Perl language level?
- Is backward compatibility kept at the public level of C language?
- Is backwards compatibility kept at the private level of C, which is
already in use on CPAN?
- At what level we can commit directly

Code cleanup

- Do all current tests pass?
- Do that negative impact on performance or memory usage?
- Is backwards compatibility kept at the Perl language level?
- Is backward compatibility kept at the public level of C language?
- Is backwards compatibility kept at the private level of C, which is
already in use on CPAN?
- At what level we can commit directly

Performance improvement

- In what areas performance has improved
- Do all current tests pass?
- Do that negative impact on other performance or memory usage?
- Is backwards compatibility kept at the Perl language level?
- Is backward compatibility kept at the public level of C language?
- Is backwards compatibility kept at the private level of C, which is
already in use on CPAN?
- At what level we can commit directly

Memory usage improvement

- In what areas memory usage has improved
- Do all current tests pass?
- Do that negative impact on performance or other memory usage?
- Is backwards compatibility kept at the Perl language level?
- Is backward compatibility kept at the public level of C language?
- Is backwards compatibility kept at the private level of C, which is
already in use on CPAN?
- At what level we can commit directly

Feature addition

- Who wants that feature?
- What thing the feature actually improves
- Additional feature size
- Comparison of the benefits of added feature with the disadvantages of
increased complexity
- Do all current tests pass?
- Do that negative impact on performance or memory usage?
- Is backwards compatibility kept at the Perl language level?
- Is backward compatibility kept at the public level of C language?
- Is backwards compatibility kept at the private level of C, which is
already in use on CPAN?
- Branch required
- Public discussion required
- Vote

Feature modification or deletion

- Who is requesting that feature fix or deletion?
- What thing the feature actually improves
- feature modification size
- Comparison of the benefits of feature modifications with the
disadvantages of increased complexity
- Do all current tests pass?
- Do that negative impact on performance or memory usage?
- Is backwards compatibility kept at the Perl language level?
- Is backward compatibility kept at the public level of C language?
- Is backwards compatibility kept at the private level of C, which is
already in use on CPAN?
- Branch required
- Public discussion required
- Vote

Public discussion

- P5P mailing list
- Github Issue
- Github Discussion
- Published the feature in Perl.com
- Published the feature in blog perl.org
- Minimum discussion period
- Getting a wide range of consensus
- Are there strong refusal users?

Voting

- Make sure that change meet Perl's goals before voting
- Vote based on conscience and good professional knowledge

--0000000000008d3d0b05b8be3156
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di=
r=3D"ltr"><div dir=3D"ltr">Several points are considered.</div><div dir=3D"=
ltr"><br></div><div dir=3D"ltr">Change target</div><div dir=3D"ltr"><br></d=
iv><div dir=3D"ltr">- Document</div><div dir=3D"ltr">- Test code</div><div =
dir=3D"ltr">- Source code</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">=
Document</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">- Does the docume=
ntation explain the feature correctly?</div><div dir=3D"ltr">- Direct commi=
t possible</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Test code</div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr">- Is the test code testing the =
feature correctly?</div><div dir=3D"ltr">- Direct commit possible</div><div=
 dir=3D"ltr"><br></div><div dir=3D"ltr">Source code</div><div dir=3D"ltr"><=
br></div><div dir=3D"ltr">- Bug fix</div><div dir=3D"ltr">- Code cleanup</d=
iv><div dir=3D"ltr">- Performance improvement</div><div dir=3D"ltr">- Memor=
y usage improvement</div><div dir=3D"ltr">- Feature addition</div><div dir=
=3D"ltr">- Feature modification or deletion</div><div dir=3D"ltr"><br></div=
><div dir=3D"ltr">Bug fix</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">=
- Have the bugs been fixed? Do you have test code?</div><div dir=3D"ltr">- =
Do all current tests pass?</div><div dir=3D"ltr">- Do that negative impact =
on performance or memory usage?</div><div dir=3D"ltr">- Is backwards compat=
ibility kept at the Perl language level?</div><div dir=3D"ltr">- Is backwar=
d compatibility kept at the public level of C language?</div><div dir=3D"lt=
r">- Is backwards compatibility kept at the private level of C, which is al=
ready in use on CPAN?</div><div dir=3D"ltr">- At what level we can commit d=
irectly</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Code cleanup</div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr">- Do all current tests pass?</d=
iv><div dir=3D"ltr">- Do that negative impact on performance or memory usag=
e?</div><div dir=3D"ltr">- Is backwards compatibility kept at the Perl lang=
uage level?</div><div dir=3D"ltr">- Is backward compatibility kept at the p=
ublic level of C language?</div><div dir=3D"ltr">- Is backwards compatibili=
ty kept at the private level of C, which is already in use on CPAN?</div><d=
iv dir=3D"ltr">- At what level we can commit directly</div><div dir=3D"ltr"=
><br></div><div dir=3D"ltr">Performance improvement</div><div dir=3D"ltr"><=
br></div><div dir=3D"ltr">- In what areas performance has improved</div><di=
v dir=3D"ltr">- Do all current tests pass?</div><div dir=3D"ltr">- Do that =
negative impact on other performance or memory usage?</div><div dir=3D"ltr"=
>- Is backwards compatibility kept at the Perl language level?</div><div di=
r=3D"ltr">- Is backward compatibility kept at the public level of C languag=
e?</div><div dir=3D"ltr">- Is backwards compatibility kept at the private l=
evel of C, which is already in use on CPAN?</div><div dir=3D"ltr">- At what=
 level we can commit directly</div><div dir=3D"ltr"><br></div><div dir=3D"l=
tr">Memory usage improvement</div><div dir=3D"ltr"><br></div><div dir=3D"lt=
r">- In what areas memory usage has improved</div><div dir=3D"ltr">- Do all=
 current tests pass?</div><div dir=3D"ltr">- Do that negative impact on per=
formance or other memory usage?</div><div dir=3D"ltr">- Is backwards compat=
ibility kept at the Perl language level?</div><div dir=3D"ltr">- Is backwar=
d compatibility kept at the public level of C language?</div><div dir=3D"lt=
r">- Is backwards compatibility kept at the private level of C, which is al=
ready in use on CPAN?</div><div dir=3D"ltr">- At what level we can commit d=
irectly</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Feature addition</=
div><div dir=3D"ltr"><br></div><div dir=3D"ltr">- Who wants that feature?</=
div><div dir=3D"ltr">- What thing the feature actually improves</div><div d=
ir=3D"ltr">- Additional feature size</div><div dir=3D"ltr">- Comparison of =
the benefits of added feature with the disadvantages of increased complexit=
y</div><div dir=3D"ltr">- Do all current tests pass?</div><div dir=3D"ltr">=
- Do that negative impact on performance or memory usage?</div><div dir=3D"=
ltr">- Is backwards compatibility kept at the Perl language level?</div><di=
v dir=3D"ltr">- Is backward compatibility kept at the public level of C lan=
guage?</div><div dir=3D"ltr">- Is backwards compatibility kept at the priva=
te level of C, which is already in use on CPAN?</div><div dir=3D"ltr">- Bra=
nch required</div><div dir=3D"ltr">- Public discussion required</div><div d=
ir=3D"ltr">- Vote</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Feature =
modification or deletion</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">-=
 Who is requesting that feature fix or deletion?</div><div dir=3D"ltr">- Wh=
at thing the feature actually improves</div><div dir=3D"ltr">- feature modi=
fication size</div><div dir=3D"ltr">- Comparison of the benefits of feature=
 modifications with the disadvantages of increased complexity</div><div dir=
=3D"ltr">- Do all current tests pass?</div><div dir=3D"ltr">- Do that negat=
ive impact on performance or memory usage?</div><div dir=3D"ltr">- Is backw=
ards compatibility kept at the Perl language level?</div><div dir=3D"ltr">-=
 Is backward compatibility kept at the public level of C language?</div><di=
v dir=3D"ltr">- Is backwards compatibility kept at the private level of C, =
which is already in use on CPAN?</div><div dir=3D"ltr">- Branch required</d=
iv><div dir=3D"ltr">- Public discussion required</div><div dir=3D"ltr">- Vo=
te</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Public discussion</div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr">- P5P mailing list</div><div di=
r=3D"ltr">- Github Issue</div><div dir=3D"ltr">- Github Discussion</div><di=
v dir=3D"ltr">- Published the feature in Perl.com</div><div dir=3D"ltr">- P=
ublished the feature in blog <a href=3D"http://perl.org">perl.org</a></div>=
<div dir=3D"ltr">- Minimum discussion period</div><div dir=3D"ltr">- Gettin=
g a wide range of consensus</div><div dir=3D"ltr">- Are there strong refusa=
l users?</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Voting</div><div =
dir=3D"ltr"><br></div><div dir=3D"ltr">- Make sure that change meet Perl&#3=
9;s goals before voting</div><div dir=3D"ltr">- Vote based on conscience an=
d good professional knowledge</div><div><br></div></div></div></div></div><=
/div>

--0000000000008d3d0b05b8be3156--
0
kimoto
1/13/2021 1:38:06 AM
On 2021/01/13 3:59, Ricardo Signes wrote:

> You'll get notes, which I expect will become better-kept and more detailed over time.  You'll get a description of actions planned and an explanation of justification and intent, but there will not be a recording of our every word and gesture.

Is there any plan to put notes to more browsable place (like https://github.com/Perl/perl5/wiki)?
0
argrath
1/13/2021 1:52:48 PM
--000000000000cab77605b8c8d9f4
Content-Type: text/plain; charset="UTF-8"

On Tue, 12 Jan 2021 at 18:23, Ricardo Signes <rjbs@manxome.org> wrote:

> (Gosh, Neil, I dunno about this precedent of numbering the meetings.
> We're going to miss a number at some point and then we'll be sorry.)
>

Well, I mean, if you can't even get the date right :-)

Dave...

--000000000000cab77605b8c8d9f4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, 12 Jan 2021 at 18:23, Ricardo Sig=
nes &lt;<a href=3D"mailto:rjbs@manxome.org">rjbs@manxome.org</a>&gt; wrote:=
<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><u></u><div><div>(Gosh, Neil, I dunno about this precedent of n=
umbering the meetings.=C2=A0 We&#39;re going to miss a number at some point=
 and then we&#39;ll be sorry.)</div></div></blockquote><div><br></div><div>=
Well, I mean, if you can&#39;t even get the date=C2=A0right :-)</div><div><=
br></div><div>Dave...</div></div></div>

--000000000000cab77605b8c8d9f4--
0
dave
1/13/2021 2:20:59 PM
--00000000000085683405b8e4ac6f
Content-Type: text/plain; charset="UTF-8"

2020 was such a great year that no one wants it to end? :)

On Wed, Jan 13, 2021 at 8:35 PM Dave Cross <dave@dave.org.uk> wrote:

> On Tue, 12 Jan 2021 at 18:23, Ricardo Signes <rjbs@manxome.org> wrote:
>
>> (Gosh, Neil, I dunno about this precedent of numbering the meetings.
>> We're going to miss a number at some point and then we'll be sorry.)
>>
>
> Well, I mean, if you can't even get the date right :-)
>
> Dave...
>

--00000000000085683405b8e4ac6f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">2020 was such a great year that no one wants it to end? :)=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Wed, Jan 13, 2021 at 8:35 PM Dave Cross &lt;<a href=3D"mailto:dave@d=
ave.org.uk">dave@dave.org.uk</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">On Tue, 12 Ja=
n 2021 at 18:23, Ricardo Signes &lt;<a href=3D"mailto:rjbs@manxome.org" tar=
get=3D"_blank">rjbs@manxome.org</a>&gt; wrote:<br></div><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u><div><div>=
(Gosh, Neil, I dunno about this precedent of numbering the meetings.=C2=A0 =
We&#39;re going to miss a number at some point and then we&#39;ll be sorry.=
)</div></div></blockquote><div><br></div><div>Well, I mean, if you can&#39;=
t even get the date=C2=A0right :-)</div><div><br></div><div>Dave...</div></=
div></div>
</blockquote></div>

--00000000000085683405b8e4ac6f--
0
perl
1/14/2021 11:32:34 PM
--00000000000070b04705b8e7181a
Content-Type: text/plain; charset="UTF-8"

I vote for using Roman numerals to number the meetings - like the Super
Bowl does. Gives it gravitas...

On Thu, Jan 14, 2021 at 6:33 PM Karen Etheridge <perl@froods.org> wrote:

> 2020 was such a great year that no one wants it to end? :)
>
> On Wed, Jan 13, 2021 at 8:35 PM Dave Cross <dave@dave.org.uk> wrote:
>
>> On Tue, 12 Jan 2021 at 18:23, Ricardo Signes <rjbs@manxome.org> wrote:
>>
>>> (Gosh, Neil, I dunno about this precedent of numbering the meetings.
>>> We're going to miss a number at some point and then we'll be sorry.)
>>>
>>
>> Well, I mean, if you can't even get the date right :-)
>>
>> Dave...
>>
>

-- 
Matthew O. Persico

--00000000000070b04705b8e7181a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I vote for using=C2=A0Roman numerals to number the meeting=
s - like the Super Bowl does. Gives it gravitas...</div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jan 14, 2021 at 6=
:33 PM Karen Etheridge &lt;<a href=3D"mailto:perl@froods.org">perl@froods.o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr">2020 was such a great year that no one wants it to end? =
:)<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Wed, Jan 13, 2021 at 8:35 PM Dave Cross &lt;<a href=3D"mailto:dave=
@dave.org.uk" target=3D"_blank">dave@dave.org.uk</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=
=3D"ltr">On Tue, 12 Jan 2021 at 18:23, Ricardo Signes &lt;<a href=3D"mailto=
:rjbs@manxome.org" target=3D"_blank">rjbs@manxome.org</a>&gt; wrote:<br></d=
iv><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><u></u><div><div>(Gosh, Neil, I dunno about this precedent of numberin=
g the meetings.=C2=A0 We&#39;re going to miss a number at some point and th=
en we&#39;ll be sorry.)</div></div></blockquote><div><br></div><div>Well, I=
 mean, if you can&#39;t even get the date=C2=A0right :-)</div><div><br></di=
v><div>Dave...</div></div></div>
</blockquote></div>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Matthew O. Persico</div>

--00000000000070b04705b8e7181a--
0
matthew
1/15/2021 2:25:59 AM
--1c8f986786d74d0d92327d17b1093fc6
Content-Type: text/plain

On Wed, Jan 13, 2021, at 8:52 AM, SHIRAKATA Kentaro wrote:
> On 2021/01/13 3:59, Ricardo Signes wrote:
> 
> > You'll get notes, which I expect will become better-kept and more detailed over time.  You'll get a description of actions planned and an explanation of justification and intent, but there will not be a recording of our every word and gesture.
> 
> Is there any plan to put notes to more browsable place (like https://github.com/Perl/perl5/wiki)?

No *plans*, but I expect we'll get there.  Right now we're focusing on getting all in sync, making sure we know that the three of us can move things forward with a common plan, and then I think administrative details will get more attention.

-- 
rjbs
--1c8f986786d74d0d92327d17b1093fc6
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Jan 13,=
 2021, at 8:52 AM, SHIRAKATA Kentaro wrote:<br></div><blockquote type=3D=
"cite" id=3D"qt" style=3D""><div>On 2021/01/13 3:59, Ricardo Signes wrot=
e:<br></div><div><br></div><div>&gt; You'll get notes, which I expect wi=
ll become better-kept and more detailed over time.&nbsp; You'll get a de=
scription of actions planned and an explanation of justification and int=
ent, but there will not be a recording of our every word and gesture.<br=
></div><div><br></div><div>Is there any plan to put notes to more browsa=
ble place (like&nbsp;<a href=3D"https://github.com/Perl/perl5/wiki">http=
s://github.com/Perl/perl5/wiki</a>)?<br></div></blockquote><div><br></di=
v><div>No <i>plans</i>, but I expect we'll get there.&nbsp; Right now we=
're focusing on getting all in sync, making sure we know that the three =
of us can move things forward with a common plan, and then I think admin=
istrative details will get more attention.<br></div><div><br></div><div>=
--&nbsp;<br></div><div>rjbs</div></body></html>
--1c8f986786d74d0d92327d17b1093fc6--
0
perl
1/16/2021 3:52:44 PM
--365fa9bd6b4a47328b4def79c650ce96
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 13, 2021, at 9:20 AM, Dave Cross wrote:
> On Tue, 12 Jan 2021 at 18:23, Ricardo Signes <rjbs@manxome.org> wrote:=

>> __
>> (Gosh, Neil, I dunno about this precedent of numbering the meetings. =
 We're going to miss a number at some point and then we'll be sorry.)
>=20
> Well, I mean, if you can't even get the date right :-)

I believe I am exactly the appropriate amount of embarrassed by that mis=
take now=E2=80=A6

--=20
rjbs
--365fa9bd6b4a47328b4def79c650ce96
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Jan 13,=
 2021, at 9:20 AM, Dave Cross wrote:<br></div><blockquote type=3D"cite" =
id=3D"qt" style=3D""><div dir=3D"ltr"><div dir=3D"ltr">On Tue, 12 Jan 20=
21 at 18:23, Ricardo Signes &lt;<a href=3D"mailto:rjbs@manxome.org">rjbs=
@manxome.org</a>&gt; wrote:<br></div><div class=3D"qt-gmail_quote"><bloc=
kquote class=3D"qt-gmail_quote" style=3D"margin-top:0px;margin-right:0px=
;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-s=
tyle:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div>=
<u></u><br></div><div><div>(Gosh, Neil, I dunno about this precedent of =
numbering the meetings.&nbsp; We're going to miss a number at some point=
 and then we'll be sorry.)<br></div></div></blockquote><div><br></div><d=
iv>Well, I mean, if you can't even get the date&nbsp;right :-)<br></div>=
</div></div></blockquote><div><br></div><div>I believe I am exactly the =
appropriate amount of embarrassed by that mistake now=E2=80=A6<br></div>=
<div><br></div><div>--&nbsp;<br></div><div>rjbs</div></body></html>
--365fa9bd6b4a47328b4def79c650ce96--
0
perl
1/16/2021 3:53:08 PM
Reply: