META: linking duplicate RCS proposals

With 2.80, Blender is seeing a huge influx of new users and this will presumably continue to grow- That is fantastic news. However, I do not believe that RCS is prepared for this type of growth. Originally it felt like new proposals had time to soak on the front page for enough time to generate useful discussion- with the massive amounts of new users it's starting to feel like a "wishing well". A user tosses a random idea out there, it gets upvotes from the handful of people that see it before it gets bumped off the front page a couple of hours later. Extrapolate this out into the future with even MORE users and the front page lifespan of a new proposal would be measured in minutes if not seconds.

I know this is probably a heavy lift and might be too RCS-specific for Dillo, but please consider how useful it would be to have duplicate proposals linked, similar to how bug reports work in Maniphest . It may be that Dillo is not viable for this type of task in the long-term and something like Maniphest is better equipped for it.

Example scenario: A proposal for viewport backface shading in workbench. As of right now, there are ~7 proposals that could feasibly be merged together. All seven have upvotes, and a few of them have more than 50+. The discussion for these proposals is all over the place, and once it's bumped off of the front page the discussion is limited to the original people who commented on the proposal (and thus, receive notifications of responses)- or those rare unicorns who actually use the search feature.

As a start, proposals that are 100% duplicates and add nothing new to the existing concept need to be closed and locked. BUT- for duplicate proposals that contribute an interesting new angle or line of thinking- those need to be preserved and linked to the original. In this scenario, upvotes for these new proposals go toward the original to give it added visibility. Each proposal in this "family of proposals" would have links to all of the other members of the group. The user that created the new proposal that got merged in would be automatically subscribed to the original proposal.

I think this type of format would help to create a more guided discussion of features, rather than RCS being a giant "wishing well" where every random idea somebody has gets upvoted a couple of times and then bumped off of the front page by the next brain fart that shows up.