Reward & Recognition :
For BAF we plan to explore virtual rewards :
| # | Options for Reward & Recognition | Description | Can do today? | Cost? |
| 1 | Award contribution certificates | Each contributor gets a certificate of contribution/participation from Hyperledger labs | yes | No |
| 2 | Give vouchers or credits | Discount vouchers to be used across Hyperledger certifications | yes | Yes |
| 3 | Recognize in a newsletter | A newsletter featuring the contributors is published | yes | |
| 4 | Digital badge | Digital badge that can we used on social network profile pics | maybe | |
| 5 | Give subscriptions to courses | For eg. pluralsight etc. | no | yes |
| 6 | Tech magazines annual/half year subscriptions | no | yes |
Duration :
1 sprint or even lesser
What are the team's needs:
Contributor challenges:
- There is a learning curve – for example, people need to know Ansible, Kubernetes, etc in order to get started
Scope :
- Technical tasks / issues on Github
- Contributor pathway: (for example: read this blog post, go to the list of good first issues, etc)
- Contributor persona: (for example: someone already familiar with Kubernetes)
- Article in an online publishing forum such as Medium
- Blogpost
- Deployment video
- Custom digital badges?
Planning :
| # | PLANNING ACTIVITY | Status |
| 1 | Create a contribution pathway we want to use in the campaign – what are the steps we want people to take? For example, read this blog post > clone BAF repository > pick a good first issue > raise a pull request > until the Pull request is merged // possibly different pathways for different personas | In progress |
| 2 | Organize Enablement workshops to make community aware of pre-requisites of using BAF and improve the documentation and scripts from the feedbacks. | Done |
| 3 | Create a good amount of "Good First Issues" to create a healthy repository of independent issues to work upon | In Progress |
| 4 | Review the information currently available about how someone can contribute to BAF and update or add more details and create new assets as needed. | In Progress |
| 5 | Reach out to partners (all DLT platform partners) to spread awareness on project and contribute-a-thon | To Be started |
| 6 | Create a task force of maintainers and key contributors to monitor the number of issues, review the pull requests as they come and answer queries on chat. | In Progress |
| 7 | Discuss on how to handle certain "What if" scenarios. 1) Too many pull requests, how to merge the code, 2) many people pick the same issue to work on, should that be controlled at the onset or the best code wins? | In Progress |
| 8 | Discuss on campaign shout outs during the event (tweets, publishing a daily leader board until the event, etc.) | To Be started |
| 9 | Determine how you will handle additions by contributors for items that were not in the original list of "known" issues | To Be started |
| 10 | Establish a set of metrics we will use to track success of the campaign and contribute-a-thon and create a baseline report to show contribution levels before campaign starts so that a post event metric comparison can help define the outcomes. | In Progress |