Open question to the community: does it really make sense to create a
new repo at this stage?
I'll try to start as clean as possible, but I agree I can start writing
anywhere
Name + Scope
I mean this project will NOT host rsyslog code, so what will it host?
Shouldn't we benefit from rsyslog code and lessons?
I think it can be faced two ways:
- a new/fresh code, without backward compatibility
- a rsyslog-ng branch, with maybe heavy refactoring, but keeping
backwards compat
Perhaps anyone think's another way? Comments are more than welcome.
gut feeling: wouldn't it better to start by just documenting the
project goals on rsyslog wiki and after that decide of how to move
forward. Just an idea... I don't think my vote counts more than anyone
elses...
Agree. Google-docs /something without git perhaps it's better.
Anyway, just give me a link where to start writing :)
_______________________________________________
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.
