Archives
Archives
| From: | "Donnie Berkholz (dberkholz)" <dberkholz@g.o> |
|---|---|
| To: | gentoo-commits@l.g.o |
| Subject: | [gentoo-commits] gentoo commit in xml/htdocs/proj/en/userrel/soc: applying.xml |
| Date: | Wed, 21 Apr 2010 01:56:38 |
| Message-Id: | 20100421015636.3B0532C04B@corvid.gentoo.org |
| 1 | dberkholz 10/04/21 01:56:36 |
| 2 | |
| 3 | Modified: applying.xml |
| 4 | Log: |
| 5 | reorder proposal so abstract is first. |
| 6 | |
| 7 | Revision Changes Path |
| 8 | 1.9 xml/htdocs/proj/en/userrel/soc/applying.xml |
| 9 | |
| 10 | file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.9&view=markup |
| 11 | plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?rev=1.9&content-type=text/plain |
| 12 | diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml?r1=1.8&r2=1.9 |
| 13 | |
| 14 | Index: applying.xml |
| 15 | =================================================================== |
| 16 | RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/userrel/soc/applying.xml,v |
| 17 | retrieving revision 1.8 |
| 18 | retrieving revision 1.9 |
| 19 | diff -u -r1.8 -r1.9 |
| 20 | --- applying.xml 21 Apr 2010 01:47:03 -0000 1.8 |
| 21 | +++ applying.xml 21 Apr 2010 01:56:36 -0000 1.9 |
| 22 | @@ -52,14 +52,14 @@ |
| 23 | is not sufficient in most cases to sway anyone. |
| 24 | </p> |
| 25 | <ol> |
| 26 | + <li><e>Abstract</e> - What does the project do; try to keep this section to one |
| 27 | + paragraph. It should not be an in depth analysis but is helpful when |
| 28 | + someone desires an overview of the project.</li> |
| 29 | <li><e>Objective</e> - What problem does the project solve. This does not need to |
| 30 | be a long section. Generally software tries to help make people more |
| 31 | efficient, or foster communication, or entertain folks. Any proposed |
| 32 | software should have a purpose and applicants should define that purpose |
| 33 | here.</li> |
| 34 | - <li><e>Abstract</e> - What does the project do; try to keep this section to one |
| 35 | - paragraph. It should not be an in depth analysis but is helpful when |
| 36 | - someone desires an overview of the project.</li> |
| 37 | <li><e>Deliverables</e> - What will the project consist of when it is finished? |
| 38 | Source code, documentation, a build system, libraries, binaries; these should |
| 39 | all be enumerated in your proposal. Without a concrete set of deliverables |