Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Option 1  : Projects can decide to do a fixed short duration event  event such as 2 weeks ( to align with say a 1 sprint duration) focused event, where maintainers free up their time to be able to answer queries / review the pull requests and run the event with a lot of posts/ tweets/ daily updates etc. This model can have additional rewards for "max pull requests" 

...

  • Determine how we will recognize people who contribute during event 
    • Swag:
      • Options include creating a project/lab specific item (such as a shirt or a poker chip) or virtual item (such as a badge) that we can give to contributors
      • Physical swag items are a good option to consider for Contribute-a-thon sponsors who have some budget available and virtual items are good in situations where budget isn't available
    • Shout-outs:
      • There are also many ways to recognize people using Hyperledger's channels (such as posting thank yous on Twitter, creating a Developer Spotlight post for people who contributed, etc)
      • For an example from Mozilla, they were regularly posting a thank you blog featuring all new contributors to a given release every time a new release came out
    • Reward points:
      • Would work like accumulating points that are equivalent to say a $amount. Then partnering with online partners such as Amazon that have significant global presence, where that $ value can be used to purchase anything. 
    • Any other 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.

...