You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

WORK IN PROGRESS - DRAFT

Phases At a high-level, a Contribute-a-thon would have a before, during and after phase.  We'll first define the specifics of what are the possible actionable's to be done in each of the different phases. And structure it with who/which team will have to work on those actions.


Before :

For the campaign and reach out

  • 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 the repository > pick issue tagged as "good first issue" > raise a pull request > until the Pull request is merged
  • Work with the Hyperledger Marketing and PR team and the relevant teams to create a timeline for the campaign and define the channels we will use (Twitter, website, LinkedIn, Wiki, meetups, etc.)
  • Create an Awarding Rules and Criterion section/page and put together on how will the winners be decided and add that in the 2nd phase of campaign
  • Organize Enablement workshops to make community aware of pre-requisites of using the product and improve the documentation and scripts from the feedbacks.
  • Reach out to partners ( all DLT platform partners ) to spread awareness on project and Contribute-a-thon

For the entire duration of the event : 

  • Create a good amount of "Good First Issues" on Github to create a healthy repository of independent issues to work upon during the contribute-a-thon phase.
  • Review the information currently available on "read the docs "about how someone can contribute to project and update or add more details and create new assets as needed.
  • 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 the rocketchat.
  • 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 ? , 3)

For post event actions

  • Determine how we will recognize people who contribute during event 
    • Swag?  Real (like a shirt or a poker chip) or virtual (like a badge)
    • Shout-outs?  Thank yous on Twitter, Developer Spotlight posts?
    • Other ideas?
  • 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.
  • No labels