Bounty Program Rules

Version 6

    VMware’s Bounty Program (the “Bounty Program”) allows companies (the “Requestor”) to request and reward community members for creating any original work (the “Work”) (whether a plugin, patch, tool, specification, documentation, sample or other material) (each request, a “Bounty Request”).

    Requestors post a Bounty Request, setting forth the requirements for the Work requested and the monetary reward (the “Bounty”) in the VMware Communities Forums (“Bounty Forums”). Any community member (“Contributor”) can reply to the Requestor in the Bounty Forum to let the Requestor know that he/she intends to develop the requested Work in exchange for the Bounty.

    How to Participate

    Want to list a plugin?

    Requestors must create a new discussion in the Bounty Forum. The title must include an appropriately descriptive name of the requested Work, including any technology you wish to manage or have used, the Bounty offered, and the date (if any) the Bounty Request offer expires.

     

    In the body of the discussion post, outline any specific requirements (e.g., specific metrics you wish to collect or control actions to take). At the end of any post include the following text:

    To accept this Bounty Request, please (i) reply to this post to indicate to others that this effort is being worked on, (ii) send a private message to the Requestor to arrange payment, and (iii) sign the Contributor Agreement and email it to bounty-manager_at_vmware.com.

    As the Requestor, you must pay the stated Bounty after VMware confirms receipt of the Contributor Agreement and you have accepted the Work.  All Contributors must sign a Contributor Agreement, which grants joint ownership between the Contributor, the Requestor, and VMware.  Contributors must post the Work on GitHub, under the VMware Bounty Program organization, licensed under the MIT license noted below.  You are responsible for working out the payment details with the Contributor directly, including getting all necessary information to process payment (e.g. payment address, W-9, etc.).  To request a copy of the Contributor Agreement for your Bounty Request Contributor, please send an email bounty-manager_at_vmware.com.

    Planning on fulfilling a Bounty Request?

    See a Bounty Request that you want to work on?  Please (i) reply to the Bounty Request you are interested in working on (so that others are aware), (ii) send a private message to the Requestor to arrange payment, and (iii) sign the Contributor Agreement (if you haven’t previously signed one) and email it to bounty-manager_at_vmware.com.

     

    All Contributors must sign a Contributor Agreement to be eligible to fulfill a Bounty Request. VMware will add a comment to the Bounty Request once the Contributor Agreement is received. Please note, VMware will provide an executed copy of the Contributor Agreement, upon request, privately to the Requestor(s) of the Bounty Request(s) you indicate you will fulfill.  You must license the Work under the MIT license, so that the entire community can freely use the Work – see more detailed instructions below.

     

    Contributors are advised to wait for (i) the Requestor to acknowledge the intent to create the Work and (ii) VMware to confirm that the Contributor Agreement has been received prior to starting development.

    Publishing Completed Bounty Requests

    Submit the Work to the Requestor and upon acceptance, publish.


    Once you have completed the Work, you should first provide the Work privately to the Requestor so that the Requestor can verify that the Work conforms to the Requestor’s requirements.  Requestors should evaluate the Work within 14 days and provide feedback regarding any gaps that need to be addressed to accept the Work or indicate the Work is ready to be published.

     

    Once the Requestor confirms the Work is ready to be published, the Contributor must take the following steps:

     

    (1) Mark all source code files with the following copyright and license information:

    Copyright © [Year] [name of Contributor], [name of Requestor, if not VMware] and VMware, Inc.

     

    Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

     

    The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

     

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

    (2) Place the same copyright and license information in a LICENSE file and embed in the binary. The LICENSE file should also be visible on the GitHub project page.

     

    (3) Publish the Work on GitHub under the VMware Bounty Program organization.

     

    (4) Update the Bounty Request with a URL to the GitHub repo where the Work can be downloaded from.

    Can I still submit a Work, if I did not write all the code myself?

    Leveraging Multiple Contributors.

    We understand that multiple people might participate in development of a Work – this is fine. Each person must sign a Contributor Agreement and applicable Contributor(s) should be reflected in the copyright notices.  Also, it would be helpful if you highlight this when you submit your Contributor  Agreement.  The team is responsible for allocating the Bounty among team members.

    Use of Open Source Software.

    If you use open source software even developing a Work, you (the Contributor) are responsible for (i) documenting the additional license information in the LICENSE file, (ii) ensuring compliance will all of the terms of the open source license, and (iii) confirm in advance with the Requestor that the Requestor is okay with the inclusion of the open source packages.

    I am ready to accept a developed Work?  What do I need to do?

    Once you have received the Work from the Contributor, you should verify that the Work meets the original requirements you posted in the Bounty Request.  Also, you should verify that the Contributor has properly marked the Work with the copyright and license information, as noted above. If everything looks good, let the Contributor know and ask him/her to post the GitHub URL in the Bounty Request.

     

    Once you accept the Work, you should pay the Bounty to the Contributor within 30 days.  Payment methods should be arranged directly with the Contributor. All Requestors hereby agree that all licenses (including under the MIT license) and ownership rights to the Work are conditioned on payment of the Bounty to the Contributor.

    Suggested Information for Publishing a Requested Work

    Be sure to include basic information for your contribution including:

    1. Installation
    2. Configuration/Administration
    3. General Usage

    As applicable include advanced information on your area page including:

    1. Security
    2. Integration considerations
    3. Internationalization (l10n, i18n)
    4. Troubleshooting: Performance, Usage

    Writing Guidelines

    In general, please use complete sentences and try not to use slang, as some readers may not be native English speakers. If you are doubtful about the spelling of a word, do not guess. Look up the correct spelling.(eg. www.dictionary.com). Proofread the copy that you submit and do correct minor typographical errors, formatting, spelling, or even the wording to ensure other readers will clearly understand you. Also make sure to check that technical steps are accurate, and where specific to an environment, the environmental variables are consistent and clear.

     

    Avoid excessive use of personal pronouns such as I, me, and my, as he/she or him/her. Try to make the identifier role specific such as System Administrators, or IT Operators or Contributors.

     

    When abbreviating any terms, spell them out the first time. For instance, Service Oriented Architecture (SOA). Do not use too many abbreviations. Whereas one, two, or three can be helpful, four or five can be very confusing.

     

    Do not purposely start a new page for discussion, as those should be carried on in the discussion forums.

    Terms and Conditions of Use

    VMware only provides the forum to facilitate the Bounty Program and is not responsible for the offers, collections, or support of the Works developed through the Bounty Program, if VMware is not the Requestor.  Requestors are responsible for providing the stated monetary reward to the Contributor upon acceptance of the Work through methods external and independent of the Bounty Program.

     

    All Contributors must sign a Contributor Agreement, which grants joint ownership between the Contributor, the Requestor, and VMware.

     

    The VMware Community Terms of Use govern all use of the Bounty Forums.