Josh Wilcox1. Crown Platform Community Developers
Version 0.11
06/21/2018
Chris Kibble, Josh Wilcox
Document History** , Approval & Contributors**
1.1. Revision History
| Version | Revised By | Date | Status | Release Notes |
|---|---|---|---|---|
| 0.1 | Chris Kibble | 04/08/2018 | Creation | |
| 0.11 | Josh Wilcox | 06/21/2018 | WIP | Some phrasing and grammatical edits |
1.2. Internal review
| Role | Name |
|---|---|
1.3. Document Approval
| Role | Name | Signature | Date |
|---|---|---|---|
1.4. Document Contributors
The following people contributed to the production of this document:
| Role | Name |
|---|---|
| Test Manager | Chris Kibble |
| Product Manager | Josh Wilcox |
2. Glossary
| Abbreviation | Full Description |
|---|---|
| CRW | Crown Platform |
3.Overview
As a community project it's vital that Crown can attract contributors for all aspects of development work. This document outlines the guidelines for community developers, how they will be asked to work and how the Crown team can make an extra effort to accommodate them.
3.1.Personal Integration
The Crown Development team can make extra efforts to help make community contributors feel at home and integrated. The Crown team will make an effort to complete the following;
-
Introduce them to the rest of the development team, make the development team aware of who they are and encourage them to contact them. We have many forms of contact and we should make the effort to say hello and introduce yourself. A regular office approach would be to have snacks on a new team members desk to encourage staff members to stop by and say hello to introduce themselves, please take this in to consideration.
-
Inform the community member of who is who within Crown. The Crown Roles and Responsibilities can be shared with new community developers so that they can learn quickly who is who and what they're performing for Crown. This is important so that the community developer can see the lines of communication and a great reference for questions.
-
If the community developer is interested then the Crown team should make an effort to run a social media post about this person and how they're going to help Crown. This could be in the context of a Medium blog. It gives a little bit of insight into them for the rest of our community and allows Crown to show others how we treat everyone that is willing to help out Crown. Finally, we also get some more exposure to our proposal system and how it can be used by anyone.
3.2.Technical Integration
- GitLab access is now public. The community developer is given a brief tour by Josh (fin) or Chris (dzlbobo). The main focus points for the GitLab tour are:
-
Access to the build and the requirements for their own development test area
-
Issues being worked on within this milestone
-
How the dev team run milestones
-
How their work will be important to the next release
-
Access to our wiki to see our coding standards and what the developers will expect of their work
-
Merge requests
-
Code reviews from the development team
-
Daily dev call on Zoom (consider Discord for community members) catch ups and what we'd like to hear from them if they have an update from us
-
Introduce the community developer to the proposal system with a test run for submitting a proposal to make sure they're aware that any development they complete for the team can be rewarded with Crown payments.