state of plone.org/kb and sprint

Hi,

I saw it today again on irc, new people are often confused about how we
handle documentation, with the result that ppl. not able to find
something or give up looking further because the link for example is
pointing to developer.plone.org and then they assume it is for
developers not for admins [happened today].
The other point is we do have some documentation under plone.org/kb and
some under developer.plone.org, for example if I take documentation
about apache, this could be/is confusing ....
How we want to solve this ?
- do we still want to use /kb or we want to integrate kb content to
developer.plone.org
- if we want to use kb and developer.p.o what goes where ?
- do we want to have developer.plone.org and for example
documentation.plone.org ?

Any ideas on this ? Anyone ? :)

Oh and what do you think about a 'github issues squashing party' aka a
documentation sprint ?

cheers

Sven

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk