A "closed" tag for granted requests and a "exclusion" system for tags filtering
RCS Is open for a long time now, some requests are here for years, and some of them have been granted already.
The result is that some topics here are irrelevant when we search requests to react on and vote in.
E.G. :
- Unlimited Layers and Layer Manager → solved by collections ?
- Cycles Shadow Catcher material → we have shadow catcher option now
- UDIM / UV Tiles Support → coming for 2.8
My proposal consist of two points :
- add a new "closed" tag, that admins can assign to any request considered as granted
- add a "exclude" option in the tags filtering, that way we can both "constrain" search result on a particular tag as well as exclude topics with a particular tag.
By the way, maybe this can be pushed even further:
- we can have more than just a "closed" tag, why not have "released", "in dev", "planned", "rejected", ... so that we also have a clear simple yet efficient dialogue with the main dev team ?
- such "dev status" tags could be visually highlighted
A nice example IMHO is
Allegoritmic's Feedback site
:
I think something like this would be the top of the "nice to have" features. But at least the two first basic request could be "must have first".
6 Comments
There's always been a plan for trying to get this site to also integrate better with developer.blender.org . There should be the following tags:
I'm not sure if this should be integrated with the tagging system in general or if it should be an additional feature. Probably a better question for Pablo or Francesco. Definitely want this, though.
Yes, these necessary feature if we want to make RCS as the go to place for making proposals. Again, for the sanity of the users and the admins as well!
I think it would also be good for those requests taken in to development indicated Blender version where this feature will be release if it possible.
And if Blander have some road map with this feature requests looks like RSI otr UE 4 - it would be cool at all.
Or, if there was a link between RCS and developer.blender.org ? ^^
What about voting on statuses ( tags ) so admins wouldn't have to examine all ideas? Idea would be marked as an duplicate or completed when specified number or percent of votes would be reached. I think similar system is on Stack Exchange
I thought about that, as well as letting topics authors set their topic's tags, but the problem is that the final word should be from developers. But that's still an option, depending on how devs, RCS admins and community would consider it.