> Yeah, that's a little text-heavy, though. Better than nothing, eh? Which is what I see at the moment - you have to search through the dev sections to find out about the repo. Which has got to be discouraging to someone just getting started with docs.
The previously mentioned link - http://apache-server.com/tutorials/ATdocs-project.html - looks to be nearly a decade old, so it might need a bit of editing. Otherwise, yeah, it'd be good information to have. > 1) Email us and say "hey, this bit is wrong". BTW, I never got any response (not even a "patches welcome") to my first email on this list suggesting some changes (5/13). > 2) Submit an actual patch to the mailing list > 3) Open a ticket in bugzilla. Perhaps this would be a good time to point out I have a suggested patch at https://issues.apache.org/bugzilla/show_bug.cgi?id=50048 if someone wouldn't mind applying it :-) > 4) Get svn access and commit it yourself > > I'd like to encourage a culture where we get lots of patches via the mailing > list, but also people are encouraged sufficiently that they rise swiftly to > #4 if they have any interest in doing so. I don't know what it takes to become a committer, but I'm pretty sure it won't happen to someone who doesn't get started. I think encouraging such a culture is an important goal if you want more than a few brave souls working on documentation. So I'd like to encourage the current brave souls to take some time to foster such a culture by lowering the bar to entry (which translates to, at least, improve the "How to get involved" section) and improving responsiveness to those who attempt to help. It doesn't happen by itself. -Luke --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
