+1. > Before creating a proposal, we should have a discussion first on the mailing list, just get feedback on the motivation.
I think it's a good idea to separate the motivation and formal proposal for complicated PIPs. So that we can avoid spending too much effort if the community is not interested in the PIP. > If there are no objections, the proposal owner can add a line to the file with the PIP number through a... It's better to set a clear rule or a specific time limit for this non-objection step in the new PIP guidelines for beginners. Thanks, Haiting On Tue, Aug 23, 2022 at 6:07 PM PengHui Li <peng...@apache.org> wrote: > Bump > > Penghui > > On Thu, Aug 18, 2022 at 11:27 PM PengHui Li <peng...@apache.org> wrote: > > > Hi all, > > > > Currently, the new proposal will be added to the issue list and then > > shared link in the email > > to request the proposal review. It's really hard to review a long > proposal > > if you want to comment > > in detail. > > > > Here is an example: > > https://github.com/apache/pulsar/issues/16763#issuecomment-1219606491 > > This seems very unintuitive. > > > > I think we can move all the PIPs to the codebase and the new proposal and > > proposal without > > any reviews should happen with a PR first. So that we can review and > > comment easily. > > Certainly, all the votes should happen on the mailing list. And we can > > also discuss the > > proposal on the mailing list. > > > > Following this way, we don't need to sync the PIPs from the issue to the > > wiki page. > > We can just add a link that points to the PIPs dir to the contribution > > guide or README. > > > > We have another pain point about the duplicated PIP number. We can > > maintain a file, a list of > > all the proposal contains the approved, in-review, drafting. Before > > creating a proposal, we should > > have a discussion first on the mailing list, just get feedback on the > > motivation. If there are no objections, > > the proposal owner can add a line to the file with the PIP number through > > a PR, like PIP-123: xxx (Under Discussion). > > So that we can prevent the duplicated PIP number(which will conflict if > > someone merged first). > > After the PR is merged, we can send out a new PR to add the proposal. > > > > Thanks, > > Penghui > > > > > > > > > > >
