[OSM-dev] Hosting documentation for OSM related projects
Jochen Topf
jochen at remote.org
Mon Jul 14 07:27:17 BST 2008
On Sun, Jul 13, 2008 at 10:51:18AM +0200, Chris Browet wrote:
> > I'd prefer to see documentation on the wiki, to lower the entry
> > barrier to potential documenters!
> >
>
> I strongly agree.
>
> Having the documentation in SVN will limit the updates to the developers,
> which, especially in my case, have more fun adding features than writing
> docs!
> More, you would have to be proficient in HTML coding or use whatever tool
> which will create bloated, non portable HTML (Frontpage, anyone?)
>
> OTOH, using the wiki would allow any casual mapper willing to contribute to
> add documentation on the fly, when they think the GUI is not obvious enough,
> by instance.
I agree the documentation should preferably be in the Wiki. In the case
of Maplint the part of the doc in the SVN is autogenerated and shouldn't
be edited by anybody. Thats why its not in the Wiki. The "normal"
(non-autogenerated) documentation for it is in the Wiki.
Jochen
--
Jochen Topf jochen at remote.org http://www.remote.org/jochen/ +49-721-388298
More information about the dev
mailing list