Merge lp:~chris.gagnon/autopilot/added-contribute-documentation into lp:autopilot
- added-contribute-documentation
- Merge into trunk
Status: | Merged |
---|---|
Approved by: | Francis Ginther |
Approved revision: | 251 |
Merged at revision: | 245 |
Proposed branch: | lp:~chris.gagnon/autopilot/added-contribute-documentation |
Merge into: | lp:autopilot |
Diff against target: |
172 lines (+117/-5) 6 files modified
docs/_static/centertext.css (+9/-0) docs/_templates/indexcontent.html (+8/-0) docs/_templates/layout.html (+25/-0) docs/contents.rst (+1/-0) docs/faq/contribute.rst (+70/-0) docs/faq/faq.rst (+4/-5) |
To merge this branch: | bzr merge lp:~chris.gagnon/autopilot/added-contribute-documentation |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Francis Ginther | Approve | ||
PS Jenkins bot | continuous-integration | Approve | |
Chris Gagnon (community) | Needs Resubmitting | ||
Review via email:
|
Commit message
add how to contribute documentation
Description of the change
- 243. By Chris Gagnon
-
remove duplicate word in faq
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
- 244. By Chris Gagnon
-
remove unused css from layout.html in docs
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:244
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Francis Ginther (fginther) wrote : | # |
The 'Learn how you can contribute!" line at the top and bottom look out of place to me. I'd like to see it integrated better, maybe add it here: "modules | index | Contribute!"? I've asked the bug reported to clarify with an example.
Also, in the even this link gets added, the '#' should be removed in:
7 + <a href="{
11 + <a href="{
the link currently expands to:
.../faq.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris Gagnon (chris.gagnon) wrote : | # |
I just saw the ## in the url, the double #'s only happen when clicking that link from the faq page, it works from other pages. I'll have to figure out how to fix that.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Francis Ginther (fginther) wrote : | # |
The python docs (http://
© Copyright 1990-2013, Python Software Foundation.
The Python Software Foundation is a non-profit corporation. Please donate.
Last updated on Jun 11, 2013. Found a bug?
Created using Sphinx 1.0.7.
I would be in favor of something similar to this format for the how to contribute link.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris Gagnon (chris.gagnon) wrote : | # |
I can center the header and footer and have the color match so it blends seamlessly.
It's harder than I thought to make sure the link to the anchor doesn't double the # on the faq. because .html is also automatically appended to the link.
I think I need to make a separate contribute page.
- 245. By Chris Gagnon
-
add css file to center text and color header and footer
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris Gagnon (chris.gagnon) wrote : | # |
I moved the contribute section to the top of the FAQ page
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:245
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Francis Ginther (fginther) wrote : | # |
When I build the docs from trunk, I get a copyright message in the footer:
© Copyright 2012-2013, Canonical. Created using Sphinx 1.1.3.
This is not being generated with this MP.
Also, the new header should be removed. Having the contribute link in the footer is sufficient.
The content looks good. I'll re-review when the contribute page is ready.
- 246. By Chris Gagnon
-
add new contribute file and fix up links
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:246
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 247. By Chris Gagnon
-
add new table row for additional item in index.html
- 248. By Chris Gagnon
-
add file a bug link to footer in documentation
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:248
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 249. By Chris Gagnon
-
add section for listing tests
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:249
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Francis Ginther (fginther) wrote : | # |
The contribute page looks very good, I just found a few proofreading corrections:
82 +* Test and Fix: No project is perfect, log some `bugs <https:/
There are extra spaces in the report a bug link. The second link should just go to the bug list: <https:/
119 +All new features should have unit and/or functional test to make sure someone doesn't remove break your new code with a future commit.
Should that be "remove or break"?
123 +From the directory containing the autopilot source code and list the tests::
Sounds like it's missing something. Maybe "From the directory containing the autopilot source code, you can list the tests"?
The footer has been a lot more complicated then I expected. The original footer is generated by a parameterized sphinx layout.html file (the copyright dates, etc. come from the conf.py file or sphinx itself). We should continue to use the parameters so that the layout.html doesn't need to be changed when those parameters change. For the life of me, I can't figure out from the sphinx docs if there is a way to 'subclass' the original footer and just add the contribute and bug links. So...
The best I could come up with is just a copy and paste of the footer block from /usr/share/
docs/_templates
{% extends '!layout.html' %}
{% set css_files = css_files + ["_static/
{% block footer %}
<div class="footer">
<div class=center_text>
<a href="{
<br/>
</div>
{%- if show_copyright %}
{%- if hasdoc('copyright') %}
{% trans path=pathto(
{%- else %}
{% trans copyright=
{%- endif %}
{%- endif %}
{%- if last_updated %}
{% trans last_updated=
{%- endif %}
{%- if show_sphinx %}
{% trans sphinx_
{%- endif %}
</div>
{% endblock %}
Once I did this, I had to remove the background color from div.center_text as the footer class had a slightly different color.
Maybe there is a better way to do this, I'm not very familiar with these templating tools.
Also, I really like the "You know you want to."
- 250. By Chris Gagnon
-
fix footer and links in contribute page
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Chris Gagnon (chris.gagnon) wrote : | # |
I fixed the links
add or between break and remove
I broke apart the list and run so they are separate questions
and used your layout file for the footer.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:250
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
- 251. By Chris Gagnon
-
remove extra word from contribute.rst
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:251
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Preview Diff
1 | === added file 'docs/_static/centertext.css' |
2 | --- docs/_static/centertext.css 1970-01-01 00:00:00 +0000 |
3 | +++ docs/_static/centertext.css 2013-06-14 16:31:37 +0000 |
4 | @@ -0,0 +1,9 @@ |
5 | +div.center_text { |
6 | + text-align: center; |
7 | + color: #ffffff; |
8 | +} |
9 | + |
10 | +div.center_text a { |
11 | + color: #ffffff; |
12 | +} |
13 | + |
14 | |
15 | === modified file 'docs/_templates/indexcontent.html' |
16 | --- docs/_templates/indexcontent.html 2013-04-16 22:51:59 +0000 |
17 | +++ docs/_templates/indexcontent.html 2013-06-14 16:31:37 +0000 |
18 | @@ -26,6 +26,14 @@ |
19 | </td> |
20 | <td> |
21 | <p class="biglink"> |
22 | + <a class="biglink" href="{{ pathto("faq/contribute") }}">How to contribute to autopilot</a><br/> |
23 | + <span class="linkdescr">You know you want to.</span> |
24 | + </p> |
25 | + </td> |
26 | + </tr> |
27 | + <tr> |
28 | + <td> |
29 | + <p class="biglink"> |
30 | <a class="biglink" href="{{ pathto("porting/porting") }}">Porting Autopilot Tests</a><br/> |
31 | <span class="linkdescr">How to port your tests from earlier versions of Autopilot.</span> |
32 | </p> |
33 | |
34 | === added file 'docs/_templates/layout.html' |
35 | --- docs/_templates/layout.html 1970-01-01 00:00:00 +0000 |
36 | +++ docs/_templates/layout.html 2013-06-14 16:31:37 +0000 |
37 | @@ -0,0 +1,25 @@ |
38 | +{% extends '!layout.html' %} |
39 | +{% set css_files = css_files + ["_static/centertext.css"] %} |
40 | + |
41 | +{% block footer %} |
42 | + <div class="footer"> |
43 | + <div class=center_text> |
44 | + <a href="{{pathto("faq/contribute") }}">Learn how you can contribute!</a> / <a href="https://bugs.launchpad.net/autopilot/+filebug">File a bug</a> |
45 | + <br/> |
46 | + </div> |
47 | + {%- if show_copyright %} |
48 | + {%- if hasdoc('copyright') %} |
49 | + {% trans path=pathto('copyright'), copyright=copyright|e %}© <a href="{{ path }}">Copyright</a> {{ copyright }}.{% endtrans %} |
50 | + {%- else %} |
51 | + {% trans copyright=copyright|e %}© Copyright {{ copyright }}.{% endtrans %} |
52 | + {%- endif %} |
53 | + {%- endif %} |
54 | + {%- if last_updated %} |
55 | + {% trans last_updated=last_updated|e %}Last updated on {{ last_updated }}.{% endtrans %} |
56 | + {%- endif %} |
57 | + {%- if show_sphinx %} |
58 | + {% trans sphinx_version=sphinx_version|e %}Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> {{ sphinx_version }}.{% endtrans %} |
59 | + {%- endif %} |
60 | + </div> |
61 | + |
62 | +{% endblock %} |
63 | |
64 | === modified file 'docs/contents.rst' |
65 | --- docs/contents.rst 2013-04-16 21:24:39 +0000 |
66 | +++ docs/contents.rst 2013-06-14 16:31:37 +0000 |
67 | @@ -10,3 +10,4 @@ |
68 | api/index |
69 | porting/porting |
70 | faq/faq |
71 | + faq/contribute |
72 | |
73 | === added file 'docs/faq/contribute.rst' |
74 | --- docs/faq/contribute.rst 1970-01-01 00:00:00 +0000 |
75 | +++ docs/faq/contribute.rst 2013-06-14 16:31:37 +0000 |
76 | @@ -0,0 +1,70 @@ |
77 | +Contribute |
78 | +########################## |
79 | + |
80 | +.. contents:: |
81 | + |
82 | +Autopilot: Contributing |
83 | ++++++++++++++++++++++++ |
84 | +Q. How can I contribute to autopilot? |
85 | +===================================== |
86 | +* Documentation: We can always use more documentation. |
87 | + * if you don't know how to submit a merge proposal on launchpad, you can write a `bug <https://bugs.launchpad.net/autopilot/+filebug>`_ with new documentation and someone will submit a merge proposal for you. They will give you credit for your documentation in the merge proposal. |
88 | + |
89 | + |
90 | +* New Features: Check out our existing `Blueprints <https://blueprints.launchpad.net/autopilot>`_ or create some yourself... Then code! |
91 | + |
92 | + |
93 | +* Test and Fix: No project is perfect, log some `bugs <https://bugs.launchpad.net/autopilot/+filebug>`_ or `fix some bugs <https://bugs.launchpad.net/autopilot>`_. |
94 | + |
95 | +Q. Where can I get help / support? |
96 | +================================== |
97 | + |
98 | +The developers hang out in the #ubuntu-autopilot IRC channel on irc.freenode.net. |
99 | + |
100 | +Q. How do I download the code? |
101 | +============================== |
102 | +Autopilot is using Launchpad and Bazaar for source code hosting. If you're new to Bazaar, or distributed version control in general, take a look at the `Bazaar mini-tutorial first. <http://doc.bazaar.canonical.com/bzr.dev/en/mini-tutorial/index.html>`_ |
103 | + |
104 | +Install bzr open a terminal and type:: |
105 | + |
106 | + sudo apt-get install bzr |
107 | + |
108 | +Download the code:: |
109 | + |
110 | + bzr branch lp:autopilot |
111 | + |
112 | +This will create an autopilot directory and place the latest code there. You can also view the autopilot code `on the web <https://launchpad.net/autopilot>`_ |
113 | + |
114 | + |
115 | +Q. How do I submit the code for a merge proposal? |
116 | +================================================= |
117 | +After making the desired changes to the code or documentation and making sure the tests still run type:: |
118 | + |
119 | + bzr commit |
120 | + |
121 | +Write a quick one line description of the bug that was fix or the documentation that was written. |
122 | + |
123 | +Signup for a `launchpad account <https://help.launchpad.net/YourAccount/NewAccount>`_, if you don't have one. Then using your launchpad id type:: |
124 | + |
125 | + bzr push lp:~<launchpad-id>/autopilot/<text about merge here> |
126 | + |
127 | + example: |
128 | + bzr push lp:~chris.gagnon/autopilot/bug-fix-lp234567 |
129 | + |
130 | +All new features should have unit and/or functional test to make sure someone doesn't remove or break your new code with a future commit. |
131 | + |
132 | +Q. How do I list the tests for the autopilot source code? |
133 | +========================================================= |
134 | +From the directory containing the autopilot source code type:: |
135 | + |
136 | + autopilot list autopilot.tests |
137 | + |
138 | +Q. How do I run the tests for the autopilot source code? |
139 | +======================================================== |
140 | +From the directory containing the autopilot source code type:: |
141 | + |
142 | + autopilot run autopilot.tests |
143 | + |
144 | +To run a single test:: |
145 | + |
146 | + autopilot run autopilot.tests.unit.test_version_utility_fns.VersionFnTests.test_get_version_string_shows_source_version |
147 | |
148 | === modified file 'docs/faq/faq.rst' |
149 | --- docs/faq/faq.rst 2013-05-01 00:48:34 +0000 |
150 | +++ docs/faq/faq.rst 2013-06-14 16:31:37 +0000 |
151 | @@ -5,6 +5,10 @@ |
152 | |
153 | Autopilot: The Project |
154 | ++++++++++++++++++++++ |
155 | +Q. Where can I get help / support? |
156 | +================================== |
157 | + |
158 | +The developers hang out in the #ubuntu-autopilot IRC channel on irc.freenode.net. |
159 | |
160 | Q. How do I install Autopilot? |
161 | ============================== |
162 | @@ -20,11 +24,6 @@ |
163 | |
164 | Autopilot is hosted on launchpad - bugs can be reported on the `launchpad bug page for autopilot <https://bugs.launchpad.net/autopilot/+filebug>`_ (this requires a launchpad account). |
165 | |
166 | -Q. Where can I get help / support? |
167 | -================================== |
168 | - |
169 | -The developers hang out in the #ubuntu-quality IRC channel on irc.freenode.net. |
170 | - |
171 | Q. What type of applications can autopilot test? |
172 | ================================================ |
173 |
PASSED: Continuous integration, rev:243 jenkins. qa.ubuntu. com/job/ autopilot- ci/125/ jenkins. qa.ubuntu. com/job/ autopilot- saucy-amd64- ci/53 jenkins. qa.ubuntu. com/job/ autopilot- saucy-armhf- ci/53
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins: 8080/job/ autopilot- ci/125/ rebuild
http://