cgCody
October 23, 2018, 12:20am
3
Something a read a few days ago stands out in my mind, which really made me appreciate the documentation team. It’s easy to forget that a lot of volunteer work goes into Blender’s ecosystem.
And regarding technical writing (I’m replying to this since I wrote the comment you refer to): Look, I’m doing this for fun in my free time. I’m also doing Cycles coding as a job, and if the IES patch was part of that, I’d write documentation if needed. However, it’s not, it’s something I’m doing for fun in my free time on top of a coding job and university. This results in two things. First of all, I have to allocate my time. Sure, I could spend three hours on detailed documentation, but I could also spend them on another feature. And on the other hand - writing code is fun, writing docs isn’t. Again, if this was a job, this wouldn’t matter, but if I’m giving up a rather large part of my free time for this, it absolutely does matter.
and in that same thread:
Just to add to this: The documentation team is always open to contributions. So @Marc_Driftmeyer , if you find the documentation is deficient and you have a more thorough explanation that more people will understand, I’m sure that documentation team would be more than happy to accept your updates.
Blender development is more than just code and it’s more than just developers who can be a part of the process. If the documentation is bad, its all of our fault.
Taken from Cycles Development Updates
1 Like