Back To: Proposed SME Server Community Constitution Docs

Fundraising And Other Ideas



In the course of developing the administration portion of the constitution, a number of ideas were bandied about. These ideas are captured here for use as a starting point should these ideas find merit in the community.


Bounty System / Sponsored Software Development


A bounty system is proposed that will provide a mechanism for other parties to directly sponsor or reward the development of core features, SME add-ons, and/or documentation. The scheme will be loosely modeled after the system used by the horde team (http://www.horde.org/bounties/). The proposed bounty system will have the following features:
Two categories of bounty items will be established: Open Bounties and Suggested Bounties.

Bounty code will be released to the contributors upon completion. Bounty project code will not be released to the general public for three months as a reward to the sponsors of the bounty. Bounty contributors that have contributed at least $50 in the last twelve months will be allowed to download ANY bounty project released within -3/+9 months of their contribution.


The following rules (borrowed from Horde and extended) will apply to developers:


Bounty Rules

To successfully claim a prize you need to follow a few rules:


1. All code submitted for a bounty must be without any known intellectual property limitations.
2. The code must be accepted and committed into the development branch by the module's maintainers before any prize will be awarded.
3. Patches must conform to dev group coding and style standards.
4. Potential developers must submit a 'notice of intent' to the DM to indicate that they are working on a particular bounty. The DM will post the fact that work is under way on the website. Additional developers will have three weeks to submit a notice of intent to the DM, or development applications for that bounty item will be considered 'closed'. All developers must provide an estimated completion date which must be accepted by the DM.
5. In the case of multiple submissions for a single bounty, the judging panel will select and award the highest quality one. Judging will take place after completion date listed by the project with the latest development due date has passed (with a TBA grace period). The judges’ decision is final.
6. Group or corporate submissions must designate a lead person who will submit the claim on behalf of the group.
7. All bounty awards or rejections are at the sole discretion of the judging panel. The DM will form the judging panel which will include at least one member from the developers group, the communications group, and ideally a user (perhaps the originator of the suggestion) for a minimum group of two people. We may refuse to award a bounty to anyone for any reason at any time (although there will certainly be a valid reason, since it is in everyone's interest for the bounty process to work smoothly).
8. A bounty project may be disqualified at the discretion of the DM if a project is way overdue and the developer cannot justify the delay. In such cases, the bounty may be awarded to a competing developer or may be opened up again to new developers.
9. Any taxes, fees, etc. are the responsibility of the recipient.


Once you have submitted your code and it has been accepted, use this form to claim the bounty prize. Prizes will be paid out using a suitable means that verifies the receipt of funds.


The SME Credit System


Recognizing the tension that is created when regular contributors consider the monetary rewards given through the bounty program, a 'credit' system is proposed to provide rewards to contributors other than bounty program participants. The SME community recognizes that the distribution has thrived based on the freely contributed time and effort of the many participants. The credit system is proposed to provide a mechanism to provide some small recognition for those that have contributed to the community in a 'significant' way. The credit system will function as follows:

The credit system will be administered by a member of the administrative team selected by the elected Business Agent.


The SME Store


It is proposed that a small 'store' is established to generate modest income from the sales of SME related and other merchandise. The store would have the dual function of providing merchandise that can be selected by participants in the SME reward system. The idea is loosely modeled on the old Mandrake (and many other) stores that support their own goals. The store would function as follows:


Store funds would be distributed by a fixed allocation as decided by the leadership committee. It is envisioned that the major portion of the profit would be used to fund the credit/recognition program with the balance being allocated to other needs.


Website Advertising


It is proposed that limited advertising / sponsoring be used on the community website to subsidize the cost of hosting the site. Said advertising options may include, but is not limited to:


The ads can be offered site wide (appearing in all pages) or may be limited to specific pages (such as software ads on the GForge pages). A payment schedule should be setup based on demand and on the depth (site-wide or not). At no time should the advertising exceed the nominal page length of the affected page. The advertising should be limited to a fraction of a single column in a three column website design, and preferably should appear in a block at the bottom of the page where it interferes with the content of the page the least.


Advertising standards should be setup that include, but are not limited to:


It is left to the community leadership to decide how and if ads may be used to reward corporate sponsors.





Headline:


See Help/GoodStyle tips for editing.

Help:TextFormattingRules
Emphasis: _ for italics, * for bold, _* for both, = for fixed width.
Lists: * for bullet lists, # for numbered lists, Term:<new-line> definition for definition lists.
Preformatted text: Enclose text in <pre></pre> or <verbatim></verbatim>.
Indented text: Indent the paragraph with whitespaces.
References: JoinCapitalizedWords or use square brackets for a [page link] or URL [http://cool.wiki.int/].
Preventing linking: Prefix with "~": ~DoNotHyperlink, name links like [text | URL or pagename].
Misc: "!", "!!", "!!!" make headings, "%%%" or "<br>" makes a linebreak, "----" makes a horizontal rule.
Allowed HTML tags: b big i small tt em strong abbr acronym cite code dfn kbd samp var sup sub