From Fedora Project Wiki
(Get this page into Docs_Project) |
m (removing main docs proj cat - leaving in sub cats) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 49: | Line 49: | ||
{| | {| | ||
|- | |- | ||
|[[ | |[[Improving_the_Docs_Project_workflow_-_Appendix_A:_The_Documentation_Workflow_Cycle| Previous Page - Appendix A - The Documentation Workflow Cycle]] ||[[Improving_the_Docs_Project_workflow| Table of Contents]] ||[[Improving_the_Docs_Project_workflow_-_Appendix_C:_Components_of_the_FOSS_Docs_Toolchain| Next Page - Appendix C - Components of FOSS Docs Toolchain]] | ||
|} | |} | ||
[[Category:Docs_Project_process]] | [[Category:Docs_Project_process]] | ||
[[Category:Improving_the_Docs_Project_workflow]] | [[Category:Improving_the_Docs_Project_workflow]] | ||
Latest revision as of 16:46, 20 May 2009
Appendix B: Types of Knowledge Contributions to a FOSS Project
This table is an excellent overview of how the FOSS community really works. It serves as a great introduction to the "big picture". The author, Daniel German, is an assistant professor in the Department of Computer Science at the University of Victoria. He is a core contributor to
Panotools , a FOSS project hosted on SourceForge.
| Type of contribution | Description |
| Source code | This is perhaps the most visible contribution. |
| Documentation | In the form of Web sites, user and developer manuals, magazine and Web articles, books, FAQs, etc. |
| Internationalization | Translations of the software and documentation into different languages. |
| Code Reviews | The discussion and improvement of source code contributions. |
| Testing and debugging | Formal or informal testing and debugging. |
| Bug reports | Submit bug reports that can be used by the development team to track and fix defects. |
| Configuration management and build process | Tasks required to maintain the environment necessary for multiple developers to participate. |
| Distribution of binaries | Preparation of binaries for download by any user interested to try the software. |
| Suggestions | Ideas on how to improve the product. |
| Answers to developer’s questions | They help other developers who are contributing. |
| Answers to user’s questions | They help individuals who are trying to use the software. |
| Release management | Release management Dedicated to prepare and advertise new releases. |
| Legal | They provide information regarding legal issues, such as licensing, and other intellectual property issues. |
| Web site development and maintenance | These contributions usually gather knowledge from other sources and make sure it is persistent. It can also include those who contribute to wikis. |
| “Pointers” to knowledge | Perhaps the smallest type of contribution it involves answering a question by “pointing” to another source of information (such as a Web site or a research article). |
| Distribution packaging | Knowledge needed to prepare packages to be included in distributions (such as SUSE, Red Hat, Fedora, etc). |
Source: "The Flow of Knowledge in Free and Open Source Communities", Daniel German, presented at 2nd International Workshop on Supporting Knowledge Collaboration in Software Development (KCSD2006) in Tokyo, Japan on September 19, 2006.
- "The Flow of Knowledge in Free and Open Source Communities" (PDF document), by Daniel M. German:
http://l3d.cs.colorado.edu/kcsd2006/papers/German.pdf
| Previous Page - Appendix A - The Documentation Workflow Cycle | Table of Contents | Next Page - Appendix C - Components of FOSS Docs Toolchain |