Seems like a bad idea unless she’s very familiar with the projects she would help document. Documentation is notoriously not something that can be produced by a newcomer, because it requires experience that a newcomer doesn’t have.

I guess the best way for a newcomer to help would be to try to use the product and ask every little question they have to make sure they receive the correct answers and context and, at the end of the process, enough knowledge would be gained to contribute at least one piece of documentation. But the bulk of the knowledge would still come from people that already know the product, so in terms of efficiency it’s way worse than having the authors write it.

Of course, if the authors are unwilling or unable to write good (or any, even) documentation, having someone that has the will to gather the scattered information into a central place and work on it so it’s digestible and high quality is still unbelievably useful.

But yeah, my point being that documentation is far trickier than it seems as far as open source contributions go.

Not so fast now! High resolution video only available on edge on windows

Regarding that part of the second edit: a very wise colleague of mine with managerial duties once told me that he expects people to give 50 to 70% every day. First, it’s unsustainable to give 100% all the time, and burnout has far worse direct and indirect consequences than simply scaling the operation up to allow more slack time. Second, when shit actually hits the fan and you need all hands on deck, there’s no more that can be given if you were already giving it 100%