I don't think a fork make sense, why keep two versions? As a branch in rsyslog-repo, that makes a lot of sense, but I'd move in smaller refactoring steps and merge each one as early as possible. A total rewrite from scratch is out of question, except if somone has a couple of month to years time.
Agree, but that scratch couldn't be far... :P
Let's treat this as experiment:https://github.com/rsyslog/rsyslog/wiki I think this wiki should only host development-related content, not user doc. User doc should go to rsyslog-doc.
IMHO a single repo could be enough, if we just have a doc directory...otherwise, user documentation and design docs wont be on the same place/can't easily reference code snippets.
*Again (based on my experience, it sucks): something more collaborative/multiple editing, like gdocs than github?*
Have you/anyone considered involving/getting feedback from elastic people? _______________________________________________ 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.
