Right-Click Select This is a read-only archive
← All ideas
  • Published 3 Mar 2021

New Community: Mentioning Rightclickselect-Proposal in the description of a patch should change its development status

The same way that Fix: T45521 ... in the commit message closes the issue T45521, writing something like Right Click Select: /c/rightclickselect/cfhbbc/ should change the development status of the proposal blender.community/c/rightclickselect/cfhbbc/

I think this would be good to have for avoiding misleading Development Statuses on Right Click Select.

100%

Development Status: Open

Upvote 5 Downvote 0
Blender_Defender
3 Mar 2021

8 Comments

IIIFGIII

Would be nice, but now someone have to know that this commit has related suggestion/suggestions on RCS to synchronize (it need to find then using not the best search system between not the best named/described stuff)... As I guess most of them done without any connection to RCS suggestions.

Blender_Defender Author

* @IIIFGIII * I don't understand? In the proposal, I wrote that in the description of a patch, a text formatted like this: Right Click Select: /c/rightclickselect/cfhbbc/ has to appear. This contains the Keyword that mentions an RCS Proposal (Right Click Select:) and the Link to the mentioned proposal ( blender.community/c/rightclickselect/cfhbbc/ ). Patches that don't mention a RCS proposal would be unaffected.

IIIFGIII

* @Blender Defender * Your proposal can be really handy for those why do some patch exactly because of some specific RCS suggestion.

But in general it will solve almost nothing with RCS ton of suggestions status. I mean - not always someone who work on commit which solve RCS suggestion even know about such suggestion existence. Or sometimes commit solve suggestion partially. Or suggestion can be named in stupid unclear way and another possible 100 500 issues...

Here my suggestion to preserve open edges in sculpt mode. Commit which solve it happen without any connection to my suggestion.

Blender_Defender Author

* @IIIFGIII * "Your proposal can be really handy for those why do some patch exactly because of some specific RCS suggestion." --> That's exactly the Type of developers this idea targets. Also, patches often take some time to progress and every one can edit them, so there's at least a bit higher chance that someone discovers a RCS-Proposal and adds it to the patch description, in the right format.

IIIFGIII

* @Blender Defender * :) Now would be nice if some one or two people from dev team will work only on solving RCS things.

Blender_Defender Author

* @IIIFGIII * They do, Pablo Vazquez and some others are working on an entirely new Community Site.

IIIFGIII

* @Blender Defender * No no - I mean people solve tickets from 100 500 800 RCS unsolved suggestion :) Some things stay here forever not solved when devs work on some new buttons or so.

1
Blender_Defender Author

* @IIIFGIII * Oh, yes, that should be done too :)