Document the current state of Fedora Fragmentation

[ferdnyc (Frank Dana (FeRD))]

@smooge

Having volunteers doing it is great, but it comes with the caveat that volunteers get to choose the tools they use. If they don’t want to write asciidoc but you tell them they have to… they go somewhere else. If they don’t want to write stuff in a wiki, they will go somewhere else… etc.

FWIW, I personally am on record as believing it is ultimately better to let them, than for every new contributor to contribute a new fork of the documentation platform/backend.

Not using git for docs

So, is the argument here, “People can’t learn things”? Or, “asking people to learn things they don’t already know is an unreasonable expectation for contributors to documentation on a technical project”? I’m honestly not clear on what the goal is here, but the impression I’m getting is, “We want the project documentation to be WYSIWYG-editable by anyone who’s ever seen Microsoft Word.” Accurate? Because, if that is the proposed expectation, please allow me to register my vigorous dissent.

People who genuinely want to contribute are, in my experience, mostly willing to contribute in the correct way — meaning, using the appropriate tools/systems — provided someone is able to explain to them what that correct way even is. (It may be that we’re collectively failing on that last point, more than we are failing to attract contributors willing to work within existing structure.)

And people who want to contribute technical documentation, but have an aversion to all things technical, should not be writing technical documentation. (Purely IMHO.)