On Wed, 23 Nov 2016, [email protected] wrote:
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?
Why are you thinking that this needs to be a completely separate codebase? Let's
first do some tests with the existing codebase to see if it's suitable before we
decide that we need to throw things out.
And as for "the ERK stack", that's a pure marketing ploy. We want rsyslog to
work well with ElasticSearch, but there's no reason to limit ourselves to that.
Rsyslog already works pretty well for this use case, we want to find where there
are gaps and fill them, not turn rsyslog into only a logstash replacement.
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.
