[osgeo4w-dev] OSGeo4W Governance

[Jeff McKenna]

Matt Wilkie wrote:
> Jeff McKenna wrote:
>> Part of the packaging role, that we define as a PSC, must include
>> documenting your own package in the wiki (user help, specific osgeo4w
>> notes, version notes, anything) otherwise having all these packages
>> are useless to a new user.
> ...
>> - user documentation must exist on the osgeo4w trac wiki
> 
> I agree on the sentiment, but this is a large project in it's own right, 
> bigger than osgeo4w as it exists right now. Also Trac is not a suitable 
> host for presenting the existing package documentation which is in 
> wildly varying formats (txt, html, word docs) without a lot processing.
> 
> We should however have web-facing documentation which details what is 
> osgeo-specific about pkg-X. Where it's located on disk, how to start it, 
> the upstream source, and what was changed to make it fit (for example).
> 
> Unless...  is there a way we could make the website a reflection of an 
> active install? E.g. one of the acceptance hurdles for on o4w package is 
> that it contain /usr/share/$pkg/html and the [wiki:pkg-name] page is an 
> index or symlink to $webserver/usr/share/$pkg/html/index.html? The same 
> mechanism might also be used fo an index to locally installed docs.
> 
> ...just thinking out loud,

Matt,

Yes these are along the same lines that I was thinking.  I'd support 
something like this (documentation requirement) for our 'OSGeo4W 2.0' 
release, that Frank mentioned.

-jeff

-- 
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/