Formal feature proposal process

[b1ek]

i think we should make a formal feature proposal process, to make it clear what has and what doesnt have a go in amber

[b1ek]

i propose this:

1. someone posts a feature proposal issue with a free form description of a feature
   1. feature discussion is opened; members, contributors and users may discuss it and finish up with a final draft
2. 2 maintainers must vote yes on the draft to allow it to be implemented
3. an associated PR can be merged after its implementation is approved

if you want this to happen, press 👍 and if you dont, press 👎 and comment how you see it

[b1ek]

and the feature request is a place where to discuss the feature behaviour, and the PR is to discuss the implementation

[b1ek]

i want to have this to avoid situations when PRs are closed or a lot of changes are requested because it does not comply with how exactly we wanted it implemented or if we wanted it implemented at all. basically, to avoid wasting work

[Mte90]

Yes I think that a PR without a ticket should be closed except if we are talking about an important bug as example.

[Ph0enixKM]

Yeah we can do that. PRs with some functionality that wasn't discussed are too risky to merge and often require the contributor to rewrite everything from new