TIP: Click on subject to list as thread! ANSI
echo: binkd
to: MICHIEL VAN DER VLIST
from: MARK LEWIS
date: 2015-03-02 10:30:00
subject: File requesting with bink

 On Mon, 02 Mar 2015, Michiel van der Vlist wrote to Kees van Eeten:

 KE>  If I were the lead developer, I would answer as the Lead of Linux
 KE> does: "Show me the code, if it is good, I will include it."

 MvdV> That is not how I responded to user requests when I was still an
 MvdV> active programmer. I implemented user requests when they were
 MvdV> reasonable and doable without undue effort. I expect the next
 MvdV> generation of programmers to extend the same courtesy to me.

in FOSS (Free Open Source Software), requests are generally handled in one of
several ways...

  1. an existing developer accepts the request and implements it
     how they see fit.

  2. the requester is asked to code it themselves and submit the
     code for perusal and inclusion. it may be given back with a
     few comments on things that need to be addressed or it may
     be modified and the modified version accepted and included.

  3. they are asked to place a bounty up for the feature and
     someone may decide to implement the request for the bounty
     offered. i've seen requests with bounties that have sat
     dormant until the bounty was increased in value. in other
     cases, the one who implemented the request as said they
     would take less than the bounty offered.

it all depends on the project and the developers... that also reminds me of a
well known saying in the (F)OSS world...

  "There is no crying in (F)OSS."

that statement basically pointing to the above three methods of handling
requests... implement it or pay someone to implement it...

)\/(ark

* Origin: (1:3634/12)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.