As everyone has probably seen by now, we are experimenting with using Fedora Discussion for the community feedback and review portion of our Change Process. This makes the process more open and transparent to all. That’s great — we want more visibility and participation. But, as we’ve just seen, conversation can quickly get unmanageable.
With something big and controversial, this could happen no matter where or how we have the conversation. We need clear guidelines so that discussion is productive, in line with our community values, and easy to follow and participate in. Some of these guidelines will be similar to those we already have for our mailing lists, and others need to be new for the new format.
I propose the following. I’d like to adopt this as soon as possible, for the anticipated upcoming revision to the recent controversial proposal. Of course, we should continue to learn and adjust as we go forward.
I think it may be important to not over engineer things.
This is a very important topic to many people
The first part of the readme looks great IMHO.
Breakout Topics
So, I read things here via the email interface.
It’s worth noting that the ‘breakout’ threads didn’t affect email at
all. I see everything as one big long 1000+ post thread. 
I don’t know if thats a bug or expected.
IMHO, breakout topics should be for things that are substantially
different than the proposed change. Like if someone starts discussing
the change process itself or has some other idea sparked by this change.
Trying to break apart ‘kinds’ of discussions for the change seems doomed
to me, people will reply to particular things and likely not stay on one
topic. Also, general feedback then becomes harder to see where it goes.
It might be worthwhile to ask our discourse upstream what they would
suggest or look at other larger communities how they handle things.
We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to write, consider simply giving that post a
instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”.
Is there any way to tally / show a overview of those?
Like “this post got 12 ’s?”
I’m not too keen on polls. I guess that could be another good way to get
more feedback, but writing poll questions is… not at all simple. It’s
super easy to skew things by wording poorly or just not including some
popular options. I’d personally just leave polls to the change
submitter. If they want to gather info about something they could do so.
Having moderators write up polls seems… dicey.
My 0.000002 cents.