Skip to content

Define process for the "proposals" directory #3527

@handrews

Description

@handrews

Currently there is an open PR (#3369) adding a new proposal to the /proposals directory. There is also an issue (#3372) which at first glance is just the proposal pasted into an issue after the PR stalled. And there is also a discussion (#3371) with minimal information linking back to the PR (but not the issue).

Setting aside the contents and merit of that specific proposal, what is supposed to happen here? Should this currently be a discussion, an issue, or a PR? The question of what should be an issue or discussion is also part of #3518, but the proposals directory makes it look like you can just file a PR to make a proposal. Is that what we want, or do we only want PRs for proposals that gain a certain amount of traction?

As it is, I think both the person making this proposal and those of us who have tried to figure out what to do with the PR are too confused to do anything with it.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions