2016-11-23 16:58 GMT+01:00 [email protected] <[email protected]>: > >> 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
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. > > 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 :) 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. Rainer _______________________________________________ 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.
