2
$\begingroup$

I'll make it quick.

Problems: Correct documentation for Blender is a moving target, moreso nowadays. It is desirable for old answers to get updated to reflect the new UI, new parameter names, etc. We get some questions that get closed as duplicates with links to old answers.

Suggestion: If we identify a question that has an old duplicate we more or less leave it alone for a while, suggesting any old duplicates as merge targets in the comments. Let the new question gather answers, and merge good answers into whatever is the better formed question.

Maybe there are limits to the merge system I don't understand, but I look forward to discussion.

It would also go some way towards reducing friction with new users.

$\endgroup$
7
  • 1
    $\begingroup$ blender.meta.stackexchange.com/questions/2660/… $\endgroup$ – Duarte Farrajota Ramos Dec 30 '20 at 1:01
  • 5
    $\begingroup$ The idea is to reduce information scattering. By "allowing new questions to gather answers" for newer versions instead of updating "cannonical questions" or adding new answers to them, we start having related information about the same issue scattered all over the place making it harder to find and follow. Closing as a duplicate of a well know answers makes them gather votes and become "more familiar" and easier to find in the future. $\endgroup$ – Duarte Farrajota Ramos Dec 30 '20 at 1:04
  • 3
    $\begingroup$ There are already plenty of very detailed, we'll thought out, and clearly explained answers that show the solutions on outdated interfaces, but that can, and should be updated. Accumulating new redundant (and mostly incomplete) answers instead, will make this site less valuable as a resource. The fact that answers are editable, and therefore updatable, is this site's greatest asset, in my opinion. $\endgroup$ – susu Dec 30 '20 at 8:29
  • 4
    $\begingroup$ Duplicates are not a "bad" thing. Blender changes quickly now, and it will continue to do so for the foreseeable future Let the dupes be dupes, and send users to the ones that are useful. Don't edit old 2.7X questions just to change the answers, write your own if it's really needed. New users come and go, most won't care to learn how the site works. The ones who do will contribute something worthwhile. $\endgroup$ – Timaroberts Dec 30 '20 at 15:28
  • 1
    $\begingroup$ @Timaroberts I agree with most of what you wrote except the "don't edit" part. Plenty of answers can be made better and can be updated while being still useful for those who still use the older versions, or don't have the hardware to run to newer ones. Most functions have not changed, they are just in different coordinates of the interface or have no keyboard shortcut. $\endgroup$ – susu Dec 30 '20 at 18:35
  • $\begingroup$ Ok. To be clear I'm not saying "always this, never that", I more just want to open up a third possibility. It may be that we find some questions once in a while that it would be better to merge new answers into, I'm just throwing the idea out there. We should at least have a rough idea of how it could work. Here's a good post I read the other day. meta.stackexchange.com/questions/158066/… $\endgroup$ – Allen Simpson Dec 30 '20 at 23:09
  • 2
    $\begingroup$ @susu I understand, I should say don't edit to change the answer but if needed to add supplemental information where it makes to, use sound judgement. Looking at a few of my own old answers, it would make more sense to say "now this is here..." instead of of an entire rewrite of the answer. $\endgroup$ – Timaroberts Jan 1 at 19:42

You must log in to answer this question.

Browse other questions tagged .