Code bounty proposal

[Jean Louis]

I find the Code Bounty stimulations at DragonflyBSD fine thing:
https://www.dragonflybsd.org/docs/developer/Code_Bounties/

Explanation

A code bounty is a certain financial stimulant to encourage someone to
put his or her effort into a project. A code bounty in the
DragonFlyBSD project needs to adhere to a set of rules defined
hereunder, though these are only preliminary and subject to
change. One could for example imagine developers accepting sponsorship
on a wholly different basis, or non-financial rewards for completing a
bounty project, like free hardware (we love that!).  Rules

    Bounty Projects are open to anyone that has a reasonable
    capability of completing the project. Typically it's on first to
    ask basis, but the sponsor of the bounty may choose differently.

    If the developer can not complete the project by the given time
    period, the bounty agreement is void and no money will be issued
    for work done. DragonFly developers may extend the time period if
    it's reasonable and prudent to do so. Upon voiding the agreement,
    someone may reissue the project again to another developer.

    Payment for a project shall be issued in no less than 72 hours
    after the DragonFly developers has had ten business days to
    determine if the code is stable and usefulness, no major issues
    are left unresolved and able for being merged into the
    project. Payment shall be in either ?Paypal (preferred), some
    money sending company or a bank account transfer.

    Upon receiving payment, the project developer shall issue (within
    24 hours) a message in the WIKI and to DragonFly development ML
    that they have received payment.

    All code submitted shall be of the same license as DragonFly. Any
    questions on the licensing issues should be directed to the
    DragonFly Team.

It would be good idea for Emacs developers to use something
similar. It can be used for GNU ELPA as well. 

Proposal draft:

A code bounty is a certain financial stimulant to encourage someone to
put his or her effort into a project. A code bounty in the Emacs
project needs to adhere to GNU and Emacs development principles or
rules.

One could for example imagine developers accepting sponsorship on a
wholly different basis, or non-financial rewards for completing a
bounty project, like free hardware (we love that!).

Rules

    Bounty Projects are open to anyone that has a reasonable
    capability of completing the project. Typically it's on first to
    ask basis, but the sponsor of the bounty may choose differently.

    If the developer can not complete the project by the given time
    period, the bounty agreement is void and no money will be issued
    for work done. GNU developers may extend the time period if it's
    reasonable and prudent to do so. Upon voiding the agreement,
    someone may reissue the project again to another developer.

    Payment for a project shall be issued in no less than 72 hours
    after the GNU or Emacs developers has had ten business days to
    determine if the code is stable and usefulness, no major issues
    are left unresolved and able for being merged into the
    project.

    Payment shall be..... (no Paypal due to non-free Javascript)

    Upon receiving payment, the project developer shall issue (within
    24 hours) a message on the mailing list that they have received
    payment.

    All code submitted shall be of the same license as GNU Emacs. Any
    questions on the licensing issues should be directed to the
    FSF.