2014-11-12 19:47 GMT+01:00 David Lang <[email protected]>: > On Wed, 12 Nov 2014, Rainer Gerhards wrote: > > It's not the final shot, as I need to think about a couple of modules. For >> example, imjournal is contributed, but now that RH-based systems so >> heavily >> depends on it, it may make sense to upgrade it to become a core modules. >> > > I would say that the availablility of tests, documentation, how clean the > code is, what the level of code churn is, etc should be what drives things > down into the contrib directory, not just who the author of the code is. > > I mostly agree, but would like to add "how well I do know a subsystem" as another predicate. For example, no matter how well a module is, I cannot add it to the core set if I am unable to maintain it. Things are may be different if the author is a long-term contributor.
Rainer > If the author sets up tests and documentation, the code is clean enough > (and under the appropriate license), then I would seriously consider > promoting it out of contrib to the main tree. > > > 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. > _______________________________________________ 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.
