Merge lp:~jorge/charm-tools/new-readme-template into lp:charm-tools/1.2

Proposed by Jorge Castro
Status: Merged
Merged at revision: 266
Proposed branch: lp:~jorge/charm-tools/new-readme-template
Merge into: lp:charm-tools/1.2
Diff against target: 70 lines (+28/-15)
1 file modified
charmtools/templates/charm/README.ex (+28/-15)
To merge this branch: bzr merge lp:~jorge/charm-tools/new-readme-template
Reviewer Review Type Date Requested Status
Marco Ceppi (community) Approve
Review via email: mp+196971@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Marco Ceppi (marcoceppi) wrote :

LGTM +1

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'charmtools/templates/charm/README.ex'
2--- charmtools/templates/charm/README.ex 2013-08-28 01:50:02 +0000
3+++ charmtools/templates/charm/README.ex 2013-11-27 20:13:21 +0000
4@@ -1,18 +1,16 @@
5-Describe the intended usage of this charm and anything unique about how
6-this charm relates to others here.
7+Describe the intended usage of this charm and anything unique about how this charm relates to others here.
8
9 This README will be displayed in the Charm Store, it should be either Markdown or RST. Ideal READMEs include instructions on how to use the charm, expected usage, and charm features that your audience might be interested in. For an example of a well written README check out Hadoop: http://jujucharms.com/charms/precise/hadoop
10
11+Use this as a Markdown reference if you need help with the formatting of this README: http://askubuntu.com/editing-help
12+
13 Here's an example you might wish to template off of:
14
15-Overview
16---------
17+## Overview
18
19 This charm provides (service) from (service homepage). Add a description here of what the service itself actually does.
20
21-
22-Usage
23------
24+## Usage
25
26 Step by step instructions on using the charm:
27
28@@ -22,20 +20,35 @@
29
30 You can then browse to http://ip-address to configure the service.
31
32-Configuration
33--------------
34+### Scale out Usage
35+
36+If the charm has any recommendations for running at scale, outline them in examples here. For example if you have a memcached relation that improves performance, mention it here.
37+
38+### Known Limitations and Issues
39+
40+This not only helps users but gives people a place to start if they want to help you add features to your charm.
41+
42+## Configuration
43
44 The configuration options will be listed on the charm store, however If you're making assumptions or opinionated decisions in the charm (like setting a default administrator password), you should detail that here so the user knows how to change it immediately, etc.
45
46-
47-Contact Information
48--------------------
49+## Contact Information
50
51 Though this will be listed in the charm store itself don't assume a user will know that, so include that information here:
52
53-Author:
54-Report bugs at: http://bugs.launchpad.net/charms/+source/charmname
55-Location: http://jujucharms.com/charms/distro/charmname
56+### Upstream Project Name
57+
58+- Upstream website
59+- Upstream bug tracker
60+- Upstream mailing list or contact information
61+
62+
63+### Charm Contact Information
64+
65+- Author: (your contact information)
66+- Report bugs at: http://bugs.launchpad.net/charms/+source/charmname
67+- Location: http://jujucharms.com/charms/distro/charmname
68+
69
70 * Be sure to remove the templated parts before submitting to https://launchpad.net/charms for inclusion in the charm store.
71

Subscribers

People subscribed via source and target branches

to all changes: