Big task list
From The_Open_Source_Way
(adding to a category, removing from an accidentally applied cat) |
(adding a bit more about content needs) |
||
| Line 10: | Line 10: | ||
* Rename sections to something snappier and more memorable, where needed. | * Rename sections to something snappier and more memorable, where needed. | ||
** Useful for the process of making each section a stand-alone page. | ** Useful for the process of making each section a stand-alone page. | ||
| + | |||
| + | === Principles === | ||
| + | |||
| + | Some sections are still just a title (an assertion) without a properly written principle and implementation. | ||
| + | |||
| + | If you see one that you have a clear idea for, add it. | ||
| + | |||
| + | === Implementations === | ||
| + | |||
| + | Other sections have a weak or missing implementation detail. This is where we explain exactly how to apply a principle. | ||
| + | |||
| + | If you've ever worked with the principle, perhaps you have some suggestions on how it should be implemented? | ||
| + | |||
| + | === Examples === | ||
| + | |||
| + | The book is full of examples intentionally left blank. We want examples that are beyond our experiences in free and open source software. | ||
| + | |||
| + | What can you think of that are good examples of the principles of the open source way? | ||
== Wiki == | == Wiki == | ||
Revision as of 21:06, 17 May 2010
Updated 2010-02-16
This is one, big task list.
Contents |
Content
- Incorporate http://people.redhat.com/rjones/how-to-supply-code-to-open-source-projects/
- Ensure license terms in place
- Reference, draw from under CC BY SA http://www.booki.cc/collaborativefutures/credits/
- Rename sections to something snappier and more memorable, where needed.
- Useful for the process of making each section a stand-alone page.
Principles
Some sections are still just a title (an assertion) without a properly written principle and implementation.
If you see one that you have a clear idea for, add it.
Implementations
Other sections have a weak or missing implementation detail. This is where we explain exactly how to apply a principle.
If you've ever worked with the principle, perhaps you have some suggestions on how it should be implemented?
Examples
The book is full of examples intentionally left blank. We want examples that are beyond our experiences in free and open source software.
What can you think of that are good examples of the principles of the open source way?
Wiki
- Does the How to create a user account page work and make sense?
- What new Category:How to pages do we need?
- Take a look at fedoraproject.org, e.g. https://fedoraproject.org/wiki/Help:Editing
- Make sure to attribute in the "Summary:" field with the URL back to the source page.
- Take a look at fedoraproject.org, e.g. https://fedoraproject.org/wiki/Help:Editing
Topic-specific pages
MediaWiki works best when each node of information is a unique page. These can be transcluded to make single source pages for a group of information. In this book, each chapter has multiple sections and sub-sections. Each section and probably each next-level sub-section need to be converted to individual pages.
- Take a chapter.
- Create a new page for each == Section 2 == named the same as the section name.
- The new page should not include the page title as a separate section header; remove that header and let the page stand as the "header 1" for that page.
- Make certain that each new page is in relevant categories:
- In the chapter page, use transclusion to pull in the sub-sections.
- Include appropriate categories for the chapter
- Sections may be transcluded in to other sections, and then aggregated in to chapters, but the section markup needs to be manually organized. For example:
DocBook XML
- Upload stand-alone git repo to fedorahosted.org. Tarball of the repo from User:Quaid's system.
- Configure access on https://fedorahosted.org/tosw
- Configure Tract on https://fedorahosted.org/tosw
