[slf4j-dev] How do you accept code contributions?
Matthew Bishop
Matthew.Bishop at elasticpath.com
Wed Nov 6 18:17:11 CET 2013
I think you just send a pull request.
From: Andreas Magnusson <andreas.ch.magnusson at gmail.com<mailto:andreas.ch.magnusson at gmail.com>>
Reply-To: slf4j developers list <slf4j-dev at qos.ch<mailto:slf4j-dev at qos.ch>>
Date: Monday, November 4, 2013 at 11:01 PM
To: "slf4j-dev at qos.ch<mailto:slf4j-dev at qos.ch>" <slf4j-dev at qos.ch<mailto:slf4j-dev at qos.ch>>
Subject: [slf4j-dev] How do you accept code contributions?
Hello all,
we're starting to use slf4j at my group in the company and we quickly got bitten by bug 242 (http://bugzilla.slf4j.org/show_bug.cgi?id=242). So instead of just griping about it I want to contribute.
But since all open source projects have different rules I thought it best to check here first. So, do I just create branch in Git and issue a push request when I deem myself done?
How do I do with licensing? I have a verbal OK from my company but I guess you might need something in writing?
Anything else I should think of?
Cheers,
/Andreas Magnusson
[http://elasticpath.com/images/ep.gif]
Matthew Bishop, Senior Architect
Mobile: +1-604-218-8102
Email: Matthew.Bishop at elasticpath.com<mailto:Matthew.Bishop at elasticpath.com>
Elastic Path Software Inc.
Web elasticpath.com <http://www.elasticpath.com/> | Blog getelastic.com <http://www.getelastic.com/> | Twitter twitter.com/elasticpath <http://www.twitter.com/elasticpath>
Careers elasticpath.com/jobs<http://www.elasticpath.com/jobs> | Community grep.elasticpath.com <http://grep.elasticpath.com/>
Confidentiality Notice: This message is intended only for the use of the designated addressee(s), and may contain information that is privileged, confidential and exempt from disclosure. Any unauthorized viewing, disclosure, copying, distribution or use of information contained in this e-mail is prohibited and may be unlawful. If you received this e-mail in error, please reply to the sender immediately to inform us you are not the intended recipient and delete the email from your computer system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-dev/attachments/20131106/03510672/attachment.html>
More information about the slf4j-dev
mailing list