nit picking here
on point 2 (the feature must be of potential interest to someone else), I think
this needs to be expanded on, something along the lines of
Once a feature or module is accepted into the rsyslog codebase, the project will
need to expend effort maintaining it forever. So a module that talks to an
internal, proprietary service that your company has and will never sell to
anyone, would probably be frowned upon.
I also think that in the first paragraph you need to emphisise a bit more that
you will accept contriabutions in just about any form.
David Lang
On Fri, 13 Dec 2013, Rainer Gerhards wrote:
Date: Fri, 13 Dec 2013 12:28:09 +0100
From: Rainer Gerhards <[email protected]>
Reply-To: rsyslog-users <[email protected]>
To: rsyslog-users <[email protected]>
Subject: [rsyslog] contribution policy
I tried to explain how easy it is to contribute.. but not sure if it looks
more frightning than not saying anything. Please have a look and comment:
http://www.rsyslog.com/contribution-policy/
This is an experimental version of the policy and I will probably change
the page during the day. Just be warned.
Feedback very highly appreciated.
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.
_______________________________________________
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.
