<br><br><div class="gmail_quote">On Wed, Jan 14, 2009 at 1:12 AM, KOBA | Hans Rossel <span dir="ltr"><<a href="mailto:hans.rossel@koba.be">hans.rossel@koba.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<span style="border-collapse: collapse;">I've contributed a few times to a chipin, but like rather to contribute and communicate directly with the maintainer for certain specific features. <div>
<br></div><div>I think there are 3 main ways:</div><div>- chipin: for popular much wanted features, a lot of people contributing a small amount. </div><div>- bounty: gathering a few sponsors that contribute a larger amount for a specific feature</div>
<div>- direct contact with the maintainer: for urgent needs or really custom changes to the module for a specific project.<br><div></div></div></span></blockquote><div><br><br>You seem to have left out the 4th way -- which is digging in and and writing some code yourself. If there's a feature that you're willing to pay someone else for, why can't you do it yourself (whether that means writing your own code, or if you're a PM having someone who works for you write the code)? After you write implement the feature yourself, you can contribute that code back in the form of a patch and the maintainer can apply that him/herself. One of the benefits of open source is that the source is open. <br>
</div></div><br>