(→Recommendation for a new mission statement: new section) |
|||
Line 8: | Line 8: | ||
:Probably not. I say remove it. --[[User:Sparks|Sparks]] 21:44, 17 December 2009 (UTC) | :Probably not. I say remove it. --[[User:Sparks|Sparks]] 21:44, 17 December 2009 (UTC) | ||
::I'm not so sure — "provide recommendations on setting of software or systems (security, performance, etc)" sounds like the whole purpose of the Deployment Guide and the various Security Guides. Even the Installation Guide contains recommendations about settings. --[[User:Rlandmann|Rlandmann]] 22:18, 17 December 2009 (UTC) | |||
== 100% FLOSS mission == | == 100% FLOSS mission == |
Revision as of 22:18, 17 December 2009
Is technology recommendation task out of scope for Docs?
The section on technology recommendations, is that really on topic for a Documentation team?
Individual team members having these skills is important to the team's mission, but in Fedora that role is filled by either the packager or someone in Infrastructure.
--Quaid 21:40, 17 December 2009 (UTC)
- Probably not. I say remove it. --Sparks 21:44, 17 December 2009 (UTC)
- I'm not so sure — "provide recommendations on setting of software or systems (security, performance, etc)" sounds like the whole purpose of the Deployment Guide and the various Security Guides. Even the Installation Guide contains recommendations about settings. --Rlandmann 22:18, 17 December 2009 (UTC)
100% FLOSS mission
What happened to the idea and mission about making 100% FLOSS content, toolchain, and process so as to be repeatable by anyone. I.e., "has to build from source" as a main mission goal.
--Quaid 21:40, 17 December 2009 (UTC)
- Add it! --Sparks 21:44, 17 December 2009 (UTC)
Recommendation for a new mission statement
The mission of the Fedora Documentation Project is to provide documentation to users and contributors to improve the overall usage and experience of Fedora. We do that by overseeing content on the wiki, explaining the usage of certain pieces of software or systems, and documenting for special events (releases, etc). In pursuit of this work, the Docs Project creates and works with 100% free/libre and open source software, content, tools, and processes to create a reusable documentation system that is buildable from source by anyone and free forever.