Meta: Guidelines and structure for RCS, Devtalk & Developers
In my opinion it is very confisung between these three forums. It feels a bit like a video game where new proposals are posted in RCS and in User Feedback in Devtalk.
A guideline or landing page should help:
Is it a new feature? Then post on right click select
Is it feedback which is already in Blender? Then post on Devtalk.
In addition, if new proposals are in the works for implementation, feature requests from RCS should be collected, evaluated and then the status "in development" "rejected" "done" etc should be updated.
This makes everything a bit more clear, but I feel it's a bit difficult how to organize everything. There is a ton of very bad poposals here where just a video by Disney Research is posted without any text.
What do you guys think?
4 Comments
..to me the biggest problem with RCS is the structure. I would recommend a classical forum structure by tpics, now "tags" here. One level deeper the propasal, next level the discussion. Many good requests just get burried by "hot" topics etc. Really hard to keep track of anything here...
* @Oliver Weingarten * these "hot topics" also create a lot of duplicates
Since at this point, RCS only has one moderator (me), we rely a lot on people who make proposals to keep track of any development that happens and update their posts as necessary.
Until we have a more full-fledged flagging system on the RCS backend ( Dillo ), we'll need to rely on that or, if you see a proposal that needs its status changed, feel free to ping me (probably easiest on blender.chat ) and I'll go in and update it.
* @Jason van Gumster * thank you for your reply, didn't know that! I am quite new in the Blender community and hope to be helpful.