develooper Front page | perl.perl5.porters | Postings from June 2022

Re: Allocating RFC numbers: [was Re: pre-RFC: template strings]

Thread Previous | Thread Next
From:
Graham Knop
Date:
June 20, 2022 15:06
Subject:
Re: Allocating RFC numbers: [was Re: pre-RFC: template strings]
Message ID:
CAM=m89EHt6K3yAWrdCjva_gMoEXrTQDAr_+t-A+srXRneP-48A@mail.gmail.com
On Mon, Jun 20, 2022 at 4:11 PM Neil Bowers <neilb@neilb.org> wrote:
>
> > On that thought: Maybe from now onwards we say that any accepted RFC
> > gets allocated the number that its github PR was
>
> I think better to _not_ use the PR number. There will be PRs done against that repo for other reasons, and multiple PRs against the same RFC as well. This will result in a non-contiguous sequence of RFC numbers, and people possible what happened to RFC#23.
>
> I think there should be a clear step in the process where the PSC say "yup, we think this should have a formal RFC", at which point the number is assigned and recorded in the tracker.

Using the PR number is awkward, but the current process also seems
rather confusing. It's not obvious when an RFC number would be given
or how to request one. Especially since there's already the Pre-RFC
step. If you've been given the go ahead to create the RFC, shouldn't a
number already be allocated?

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About