On Wed, Jan 22, 2014 at 5:35 PM, Boylan, James <[email protected]>wrote:
> Hmm. That's a tougher question. On the one hand I can see the benefit to > it. But on the other hand, is it the best choice for location... One could > argue that processing scripts like that should be in their own repo since > they are not directly linked to the Rsyslog codebase. > Yup (btw: "rsyslog" -- it should be all lower case - forgot to answer that in some thread...). Pro: * easier to maintain for it's developer * no need to involve rsyslog core team for updates Con: * (much?) harder to find for end user * harder to find out for the rsyslog team what actually exist * may provide lower "political" benefit (in regard of attracting contributors, visible contributor base, etc...). Some more? Other views? 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.
