EDIT: THIS INFORMATION IS OUTDATED AND DOESN'T REFLECT CURRENT POLICIES OF DASH CORE GROUP INC., PLEASE CONTACT THE HR DEPARTMENT FOR ACCURATE POLICY INFORMATION.
In order to prevent any abuse or perceived abuse of the budget system, we wanted to post a few basic "rules" for any contractors that wish to provide services through the core team. We intend for these to provide basic guidance on the expectations involved, but they are not intended to be a holistic set of the expectations when contracting through the core team. We will continue to add, revise, and clarify this post as the need arises.
The goals in sharing these rules is both to provide the community with assurances that such rules are in place (thus protecting the interests of the network), and to provide prospective contractors an idea of some of the basic restrictions and expectations that would accompany any core team role.
1) Conflicting roles: Contractors may seek a role within the core team, or submit their own budget proposals to the network, but should avoid doing both. This creates a conflict of interest when considering incremental projects may take time away from core team responsibilities. If an independent budget proposal is submitted and funded, a paid role through the core team may require temporary or permanent suspension depending on the nature and duration of the proposal in question.
2) Full-time role availability: Some roles require and are paid for full-time work. While it is unreasonable that a contractor working full-time would never require time off, there must be limits. Also, holidays differ between countries, religions, etc. For this reason, we are setting the expectation that contractors may take up to 20 personal days per year including national and religious holidays, vacations, personal time, sick time, doctor visits, etc. pro-rated for the length of their engagement. Any additional time may result in a reduction in compensation.
3) MIT Licence: All code developed while working on Dash will be released under the MIT license unless otherwise specified (e.g., if we provide support for a business partner's own systems for example).
4) Confidential information: To the extent that contractors are exposed to confidential information, they should not disclose it without permission, including the identities of individuals who wish to remain anonymous, personal addresses and phone numbers, yet-undisclosed partnerships or integrations, and the private business plans of other businesses to which their roles expose them.
There are other expectations as well, which will be clarified prior to entering into any agreement. These include many details including responsibilities for keeping payment addresses used for compensation up to date, expectations for professional behavior, terms of the contract, etc. These are either part of the specific terms of any contract offered, or are details included in a handbook which will be provided upon contracting through the core team.
If you have any feedback or suggestions to supplement or change these rules, please let us know.
In order to prevent any abuse or perceived abuse of the budget system, we wanted to post a few basic "rules" for any contractors that wish to provide services through the core team. We intend for these to provide basic guidance on the expectations involved, but they are not intended to be a holistic set of the expectations when contracting through the core team. We will continue to add, revise, and clarify this post as the need arises.
The goals in sharing these rules is both to provide the community with assurances that such rules are in place (thus protecting the interests of the network), and to provide prospective contractors an idea of some of the basic restrictions and expectations that would accompany any core team role.
1) Conflicting roles: Contractors may seek a role within the core team, or submit their own budget proposals to the network, but should avoid doing both. This creates a conflict of interest when considering incremental projects may take time away from core team responsibilities. If an independent budget proposal is submitted and funded, a paid role through the core team may require temporary or permanent suspension depending on the nature and duration of the proposal in question.
2) Full-time role availability: Some roles require and are paid for full-time work. While it is unreasonable that a contractor working full-time would never require time off, there must be limits. Also, holidays differ between countries, religions, etc. For this reason, we are setting the expectation that contractors may take up to 20 personal days per year including national and religious holidays, vacations, personal time, sick time, doctor visits, etc. pro-rated for the length of their engagement. Any additional time may result in a reduction in compensation.
3) MIT Licence: All code developed while working on Dash will be released under the MIT license unless otherwise specified (e.g., if we provide support for a business partner's own systems for example).
4) Confidential information: To the extent that contractors are exposed to confidential information, they should not disclose it without permission, including the identities of individuals who wish to remain anonymous, personal addresses and phone numbers, yet-undisclosed partnerships or integrations, and the private business plans of other businesses to which their roles expose them.
There are other expectations as well, which will be clarified prior to entering into any agreement. These include many details including responsibilities for keeping payment addresses used for compensation up to date, expectations for professional behavior, terms of the contract, etc. These are either part of the specific terms of any contract offered, or are details included in a handbook which will be provided upon contracting through the core team.
If you have any feedback or suggestions to supplement or change these rules, please let us know.
Last edited by a moderator:
