Index: trunk/doc-rnd/index.html =================================================================== --- trunk/doc-rnd/index.html (revision 2169) +++ trunk/doc-rnd/index.html (revision 2170) @@ -16,7 +16,7 @@
  • debian packages
  • comments, feedback, patches: live chat with the developer or mail to: pcb-rnd (at) igor2.repo.hu
  • Scripting PCB? Check the rosetta stone of pcb-rnd example scripts and the scripting documentation -
  • the project is open for contribution +
  • the project is open for contribution ; if your favorite feature is not supported, please read this howto.

    Index: trunk/doc-rnd/myfeature.html =================================================================== --- trunk/doc-rnd/myfeature.html (nonexistent) +++ trunk/doc-rnd/myfeature.html (revision 2170) @@ -0,0 +1,44 @@ + + +

    pcb-rnd - how to get my favorite feature implemented

    + +The list below is sorted: top items have higher priority, but you +are free to choose any. + +

    1. If you are a programmer with free time to spend

    +Read the contribution howto and join the project. +You are welcome to work only on the feature you are interested in. You get +all the support (e.g. for understending the API, to get a blank plugin +set up so you need to fill in only the feature-specific parts, etc.). Success +rate shoudl be near to 100%. + +

    2. If you are not a programmer and have free time

    +You can join and work on things you don't need that much, but others do. +This will build your reputation in the community which in turns encourages +others to implement your favorite feature even if they wouldn't do it for +themselves. The success rate is somewhat more random, obviously. + +

    3. If you don't have free time

    +Consider donation: buy someone else's time. To do so, contact me +(see the contribution howto page). Since +you don't need to cover all costs and the hourly rates are much lower +on a pet project, and your feature may be simpler than it looks, and +someone who already knows the code also saves thelearning cureve, it may +all be cheaper than you think. The success rate should be close to 100%. +

    +However, this is a last resort solution, the above ones are clearly preferred. + + +

    4. If you don't have anything to contribute with

    +Vote for it in the +feature poll. If your feature is not there, ask on the mailing list. +Chance for success: if it's a popular demand on the feature poll, chances +are somewhat good. Else chances are very low, but not zero. + +

    5. If you tried everythign, even point 4. and all failed...

    +Complain loudly on the mailing list, advertise your opinion, try pushing +the thing - a.k.a. go trolling. Success rate is exactly 0%, +you make a lot of good friends enemies that will make it harder +to ask or contribute later for another feature, but it may make you feel +better. </irony>. +