[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp

[Jorge O. Castro]

Blueprint changed by Jorge O. Castro:

Whiteboard changed:
  UDS 1303 Pad Data:
  Pad: http://pad.ubuntu.com/uds-1303-servercloud-1303-juju-contributor-onramp
  Old spec:  https://blueprints.launchpad.net/ubuntu/+spec/community-r-juju-contributor-onramp-1
  
  Idea:
  In regards to using other code hosting: mariusko_: Also maybe compare with how it is done with nodejs: "npm help publish" (https://npmjs.org/doc/developers.html)
  
- [USER STORIES] 
+ [USER STORIES]
+ 
+ James is a sysadmin at a company and is interested in getting his charms
+ into the store for convenience/peer review.
+ 
+ Kirk is deploying a charm but finds that it's missing a feature or needs
+ a bugfix and he thinks he knows how to fix it.
+ 
+ Robert is a developer at a company who works on a database that is
+ charmed up, he notices that the charm needs improvement to follow his
+ project's recommended best practice, but isn't sure how to claim
+ ownership of a charm.
+ 
+ Lars is used to github and is totally confused on how to get charms he's
+ interested in.
+ 
  [ASSUMPTIONS]
+ 
+ - Mims/Castro want to mirror how OpenStack does reviews and code
+ contributions as well as their usage of LP Blueprints.
+ 
  [RISKS]
+ 
+ - There's only so much simplification that can happen when it comes to submitting code.
+ - Poor response time leads people to believe that we don't want to help them.
+ - Workflow ties into the store, so we need to be careful on how we simplify this.  
+ 
  [IN SCOPE]
+ 
+ - Refining workflow for submission
+ - Measuring contributor metrics and enforcing a fast response time. 
+ 
  [OUT OF SCOPE]
+ 
  [USER ACCEPTANCE]
+ 
  [RELEASE NOTE/BLOG]
+ 
+ - We've made it easier than ever to contribute to charms with a new
+ submission workflow.

-- 
Juju Contributor Onramp
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp