| 25 | | * The developer creates & submits a proposal. (to where?, [haiku-inc], [haiku-development], [haiku]) |
| 26 | | * Other developers review the proposition & determines: |
| 27 | | * if the costs are reasonable |
| 28 | | * if proposition is acceptable. |
| 29 | | * The proposal is submitted to the website and fund raising begins. |
| | 22 | * The developer creates & submits a proposal to either info@haiku-os.org or haiku-inc@freelists.org |
| | 23 | * The BOD will review the proposal and make modifications as necessary. |
| 34 | | * The details of the planned work are explained. |
| 35 | | * The end goal needs to be something quantifiable. |
| 36 | | * An outline of implementation will display a thorough understanding of the proposed task. |
| 37 | | * An estimate of the time required, eg days, weeks, months |
| 38 | | * Pricetag in USD. |
| 39 | | * Preferred payment schedule |
| 40 | | * single at end of term |
| 41 | | * 1/2 at midterm, 1/2 at end of term |
| 42 | | --> |
| 43 | | }}} |
| | 28 | * length of contract |
| | 29 | * wage in USD |
| | 30 | * specific area of development |
| | 31 | |
