Influencing projects: do and do not

There are many ways to get an opensource project fit better your needs:

– you contribute to it by doing the missing bits yourself.
– you contribute to it by funding somebody so you get the bits done.
– you ask politely about those bits and you make a point on how those bits could be useful for the developers too (so they will use their time and skill to implement them)

There are also many ways to hinder an opensource project (trying and failing to have it fit better your needs):

– you assume you can lead who is doing since you are using what’s done by them
– you assume that there is democracy and the fact “everybody”* want something (but the people actually doing something) makes that relevant
– you try to annoy people till they give in or give up.

* from interestingly inflated self made estimation

One thought on “Influencing projects: do and do not”

  1. Concerning the first option: If you don’t plan on forking the project, it might be a good idea to negotiate the conditions for acceptance of the contribution first. Or else you might end up doing the work in vain.

    PS: Why can’t I mention g m a i l.com as email address or in the comment?

Leave a Reply

Your email address will not be published.