[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.05: - [jorge] : Highlight Places where people can contribute (https://trello.com/c/RYkKAfH2/314-contributoronramp-highlight-places-where-people-can-contribute): TODO + [jorge] : Highlight Places where people can contribute (https://trello.com/c/RYkKAfH2/314-contributoronramp-highlight-places-where-people-can-contribute): DONE Work items: - [jorge] : Lower the Barrier to entry (https://trello.com/c/1e4Zjzgu/316-contributoronramp-lower-the-barrier-to-entry): TODO + [jorge] : Lower the Barrier to entry (https://trello.com/c/1e4Zjzgu/316-contributoronramp-lower-the-barrier-to-entry): DONE [jorge] Create Problem Tracker for issues found by users (https://trello.com/c/kmBnddSh/355-contributoronramp-create-problem-tracker-for-issues-found-by-users): DONE -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: - Work items for ubuntu-13.04-month-6: - [jjo] Case Studies from webops (move to 2.0 messaging): TODO - [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO - [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO - Work items for ubuntu-13.05: [jorge] : Highlight Places where people can contribute: TODO Work items: [jorge] : Lower the Barrier to entry: TODO [jorge] Create Problem Tracker for issues found by: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Marco Ceppi: 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 + + vUDS 1308 Notes: http://pad.ubuntu.com/uds-1308-servercloud-s-juju- + contributor-onramp 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] James is a sysadmin at a company and is interested in getting his charms into the store for convenience/peer review. He's got some internal stuff that he can keep seperate, but he doesn't want to maintain boring infrastructure charms on his own. 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. Cliff submitted a fix to a charm two weeks ago and has no idea how to get someone to get his fix 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. [notes from cloudsprint 2013-05] Low hanging fruit Docs! Big issue to getting new contributors Instructional videos will be a big help to resolving “How do I get going” for new people “Contribute to this charm” on jujucharms.com Better charm tools to help contributors (charm-helpers, charm-tools, charmsupport) NO LOCAL PROVIDER FOR JUJU-CORE Inhibitor for WebOps, charmers, community, and basically everyone -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.05: [jorge] : Highlight Places where people can contribute: TODO Work items: [jorge] : Lower the Barrier to entry: TODO - [jorge] Create Problem Tracker for issues found by: TODO + [jorge] Create Problem Tracker for issues found by: DONE -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: Work items changed: - Work items for ubuntu-13.05: - [jorge] : Highlight Places where people can contribute: TODO - - Work items: - [jorge] : Lower the Barrier to entry: TODO - [jorge] Create Problem Tracker for issues found by: DONE -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: Work items changed: Work items for ubuntu-13.04-month-6: [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO Work items for ubuntu-13.05: [jorge] : Highlight Places where people can contribute: TODO Work items: [jorge] : Lower the Barrier to entry: TODO + [jorge] Create Problem Tracker for issues found by: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO + Work items for ubuntu-13.05: + [jorge] : Highlight Places where people can contribute: TODO + Work items: - [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Mark Mims: 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] James is a sysadmin at a company and is interested in getting his charms into the store for convenience/peer review. He's got some internal stuff that he can keep seperate, but he doesn't want to maintain boring infrastructure charms on his own. 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. Cliff submitted a fix to a charm two weeks ago and has no idea how to get someone to get his fix 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. + + + [notes] + + Low hanging fruit + Docs! Big issue to getting new contributors + Instructional videos will be a big help to resolving “How do I get going” for new people + “Contribute to this charm” on jujucharms.com + + Better charm tools to help contributors (charm-helpers, charm-tools, + charmsupport) + + NO LOCAL PROVIDER FOR JUJU-CORE + Inhibitor for WebOps, charmers, community, and basically everyone -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: - [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED - [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO - jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO - [jorge] : Bitesize bugs for charms: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO + [jorge] : Highlight Places where people can contribute: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO [jorge] : Highlight Places where people can contribute: TODO + [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: - [jorge] Contribute to this charm! link in the charm store.: BLOCKED - [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED - [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO - [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE - [jorge] Investigate long running contests on juju.ubuntu.com: TODO - [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: - [a.rosales] : Quantify questions from charm schools. : TODO - [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO - [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: - [mark-mims] Investigate making charm documentation testable: TODO - [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO Work items: [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: - [jorge] : Rewrite submission process for charms.: TODO - [jorge] : Get the gui guys to add mean response time measure.: TODO - [jorge] : Schedule reviews for charm reviewers.: TODO - [jorge] : Find 3 people and ask them to charm something to record it.: TODO - [jorge] : At the end of the cycle, do more user testing.: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO [jorge] : Highlight Places where people can contribute: TODO [jorge] : Lower the Barrier to entry: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Mark Mims: 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] James is a sysadmin at a company and is interested in getting his charms into the store for convenience/peer review. He's got some internal stuff that he can keep seperate, but he doesn't want to maintain boring infrastructure charms on his own. 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. Cliff submitted a fix to a charm two weeks ago and has no idea how to get someone to get his fix 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. - - [notes] + [notes from cloudsprint 2013-05] Low hanging fruit Docs! Big issue to getting new contributors Instructional videos will be a big help to resolving “How do I get going” for new people “Contribute to this charm” on jujucharms.com Better charm tools to help contributors (charm-helpers, charm-tools, charmsupport) NO LOCAL PROVIDER FOR JUJU-CORE Inhibitor for WebOps, charmers, community, and basically everyone -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Martin Packman: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO - [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS + [gz] #1069883 Fix bug where defaulting to smallest instance type.: DONE [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: Work items changed: - Work items for ubuntu-13.04-month-6: + Work items: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO - [gz] #1069883 Fix bug where defaulting to smallest instance type.: DONE + [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO - - Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: - Work items: + Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO - [gz] #1069883 Fix bug where defaulting to smallest instance type.: INPROGRESS [jjo] Case Studies from webops: TODO [mthaddon] Case Studies from webops: TODO [timrchavez] Case Studies from PES: TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO + + Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO - [jjo] Case Studies from webops: TODO - [mthaddon] Case Studies from webops: TODO - [timrchavez] Case Studies from PES: TODO + [jjo] Case Studies from webops (move to 2.0 messaging): TODO + [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO + [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] README Review, prioritized based on charm popularity: TODO [jorge] Announce README fixups on the mailing list with maintainers: TODO [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO [jorge] Ensure that the juju gui can run on the local provider: TODO [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO - [jorge] README Review, prioritized based on charm popularity: TODO - [jorge] Announce README fixups on the mailing list with maintainers: TODO - [jorge] Codify for ~charmers to encourage people to fix readmes on submission of other fixes: [jorge] Provider discounts for charmers?: INPROGRESS [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO - [niemeyer] Post instructions on how to use other code hosting options, and juju publish usage.: TODO - [jorge] Ensure that the juju gui can run on the local provider: TODO - [jorge] Investigate Openstack's use of github/launchpad workflow: INPROGRESS - [jorge] fix dead link: https://wiki.ubuntu.com/ServerTeam/MAAS/Juju from https://juju.ubuntu.com/get-started/maas/: TODO + [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO + [jorge] : Rewrite submission process for charms.: TODO + [jorge] : Get the gui guys to add mean response time measure.: TODO + [jorge] : Schedule reviews for charm reviewers.: TODO + [jorge] : Find 3 people and ask them to charm something to record it.: TODO + [jorge] : At the end of the cycle, do more user testing.: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO + [jorge] : Bitesize bugs for charms: TODO + [a.rosales] : Quantify questions from charm schools. : TODO + [a.rosales] : Sync up with webops wrt. charm feedback.: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO [jorge] : Bitesize bugs for charms: TODO [a.rosales] : Quantify questions from charm schools. : TODO - [a.rosales] : Sync up with webops wrt. charm feedback.: TODO + [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Jorge O. Castro: Work items changed: Work items for ubuntu-13.04-month-6: [jorge] Contribute to this charm! link in the charm store.: BLOCKED [jorge] Tell people they can help. There's no mention of how to help on jujucharms.com. That sucks. Not make something and get a prize, make it make something you are going to use and get a prize.: BLOCKED [jorge] charm-tools, we need to talk about it more, make a Best practices for charms should be in write a charm, integrate the mythical best practices page with write a charm.: TODO [mark-mims] Investigate making charm documentation testable: TODO [evilnick] Investigate making charm documentation testable: TODO [jjo] Case Studies from webops (move to 2.0 messaging): TODO [mthaddon] Case Studies from webops (move to 2.0 messaging): TODO [timrchavez] Case Studies from PES (move to 2.0 messaging): TODO [jorge] Update /events page on juju.ubuntu.com to show where we are attending.: DONE [jorge] Investigate long running contests on juju.ubuntu.com: TODO [jorge] Ensure that the juju gui can run on the local provider: BLOCKED Work items: [jorge] File bugs on charms that don't meet quality guidelines. it would be great if this charm did multimaster!! and so on, so people know that they can fix it. needs-scaleout tag?: BLOCKED [jorge] Way to go, we have over 100 people who contributed charms and you told no one. Nice work.: TODO jorge] Pimp my charm contest. or Xprize? Scale out HA x service to blah blah with integrated backups: TODO [jorge] : Rewrite submission process for charms.: TODO [jorge] : Get the gui guys to add mean response time measure.: TODO [jorge] : Schedule reviews for charm reviewers.: TODO [jorge] : Find 3 people and ask them to charm something to record it.: TODO [jorge] : At the end of the cycle, do more user testing.: TODO [jorge] : Bitesize bugs for charms: TODO [a.rosales] : Quantify questions from charm schools. : TODO [a.rosales] : Sync up with webops (mthaddon wedgwood) wrt. charm feedback.: TODO + [jorge] : Make a charm-school tag in lp for juju bugs so core team knows what are high visibility bugs: TODO -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
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] James is a sysadmin at a company and is interested in getting his charms - into the store for convenience/peer review. + into the store for convenience/peer review. He's got some internal stuff + that he can keep seperate, but he doesn't want to maintain boring + infrastructure charms on his own. 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. + - 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. + - 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
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] James is a sysadmin at a company and is interested in getting his charms into the store for convenience/peer review. He's got some internal stuff that he can keep seperate, but he doesn't want to maintain boring infrastructure charms on his own. 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. + Cliff submitted a fix to a charm two weeks ago and has no idea how to + get someone to get his fix 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: Name: servercloud-1303-juju-contributor-onramp = servercloud-s-juju-contributor-onramp -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: 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] + [ASSUMPTIONS] + [RISKS] + [IN SCOPE] + [OUT OF SCOPE] + [USER ACCEPTANCE] + [RELEASE NOTE/BLOG] -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-s-juju-contributor-onramp] Juju Contributor Onramp
Blueprint changed by Antonio Rosales: Priority: Undefined = Medium -- Juju Contributor Onramp https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-contributor-onramp -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
