I am not sure if the reasoning applies to a community as large as Mozilla, but lately I've heard that new contributors can view a project wiki very differently from those heavily involved in a project.
Copying directly from a blog post[1] on this topic: --- - Maintainers believe they're saying "feel free to make any changes you want, the Wiki is owned by the community." By doing that, they are generally hoping to greatly increase collaboration. - Contributors, however, seem to be *intimidated* by a Wiki. Most contributors do not feel completely confident in their ability to add correct content, adhere to standards, fit into the right outline, etc. So paradoxically, by making the medium as open as possible, the Wiki *discourages* contribution. - Readers of documentation greatly appreciate well structured content, and want to be able to trust the accuracy of the content they're reading. Wikis do not inspire this confidence. Despite my previous comments about contributors, readers are (logically) concerned that Wiki content may have been written by someone uninformed, or may have fallen out of date. --- The post goes on to suggest in-tree documentation kept up to date via pull requests as the better approach. I guess the trouble is that at least for mozilla-central, there isn't really a low barrier approach to submitting an in-tree change like a pull request currently. [1]: http://www.yesodweb.com/blog/2015/08/thoughts-on-documentation - Ryan On Fri, Jun 16, 2017 at 10:05 AM, Sylvestre Ledru <sylves...@mozilla.com> wrote: > > > Le 16/06/2017 à 16:40, Boris Zbarsky a écrit : > > On 6/16/17 9:33 AM, Ehsan Akhgari wrote: > >> I certainly feel like the > >> barrier for filing bugs, creating a patch, figuring out how to use > >> readthedocs infrastructure, getting reviews, etc. isn't really worth it > > > > I believe we should not require filing bugs, reviews, or any of that > > for in-tree docs. Just edit the doc, commit, push. Add > > "r=documentation" if needed to placate hooks. Just because it's > > in-tree doesn't mean it needs to use the whole heavyweight process. > > And if we can make these things auto-DONTBUILD, that's even better, of > > course. > > > > I agree it's still slower than a wiki. :( > And far from trivial for volunteers who just want to fix one or two > things in the doc :/ > > S > > _______________________________________________ > dev-builds mailing list > dev-builds@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-builds >
_______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
