On Fri, 13 Dec 2013, Rainer Gerhards wrote:
Hi all,
in spite of the recent discussions: would it make sense to create a
separate documentation project? We could do a fresh start with whatever new
system we come up with.
IMHO we need to be far less strict with commit access in this context. This
is the prime reason I think a separate project would make sense here.
Comments?
on the one hand, splitting the documentation out makes it easier to leave the
documentation out of the final packages.
on the other hand, it will disrupt the documentation and I'm not sure it's
really worth it.
I would suggest appointing someone to the 'the documentation person' and have
that person vet all the documentation changes, and then you can just pull the
docs into the main repo with little or any work.
Also, any new documentation project is almost certinly going to change the
layout of the documentation. the problem with this is that google and bing know
about the old locations and are going to continue to point people at them (we
already have a bit of a problem with this with the node/ pages
All of the existing pages are going to need to continue to exist, just with
different text or links to the new pages.
making a new documentation project seems like it would be more likely to let
things drop through the cracks than continuing to work on the current
documentation.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
