From Fedora Project Wiki

(resolving with a final mission proposal)
(add explanation for modifying transclusion)
Line 1: Line 1:
 +
== Explanation: Modification to Transclusion ==
 +
 +
I changed the <noinclude> tags to <onlyinclude> tags. This way, only the mission statement itself is transcluded. As it was, the autolang thing was also being transcluded, which meant it would appear on the final page twice. Worse, when transcluded, autolang would always refer to the page being viewed (not the mission statement). The result is wasted space because of redundant autolang things, and the potential to confuse readers.
 +
 +
[[User:Crantila|Christopher Antila]] ([[User talk:Crantila|talk]]) 19:52, 21 April 2014 (UTC)
 +
 
== Is technology recommendation task out of scope for Docs? ==
 
== Is technology recommendation task out of scope for Docs? ==
  

Revision as of 19:52, 21 April 2014

Explanation: Modification to Transclusion

I changed the tags to tags. This way, only the mission statement itself is transcluded. As it was, the autolang thing was also being transcluded, which meant it would appear on the final page twice. Worse, when transcluded, autolang would always refer to the page being viewed (not the mission statement). The result is wasted space because of redundant autolang things, and the potential to confuse readers.

Christopher Antila (talk) 19:52, 21 April 2014 (UTC)

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)
But how many of those recommendations are generated by Docs, and how many come from other groups? If Docs is not generating the bulk of the recommendations, I'd say it is outside the scope. --bcotton 00:04 18 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)
+1 --bcotton 0008 18 December 2009 (UTC)
+1, serve as a model for others. Mel Chua 01:16, 18 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.

I like this, unless we decide to keep the 'making recommendations' part. I do wonder if we should mention the wiki explicitly. Our mission is independent of the technology we use. Maybe we change that clause to "We do that by overseeing community-maintained content,"? --bcotton 0013 18 December 2009 (UTC)

Revised final proposal

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 community-maintained content, explaining the usage of certain pieces of software or systems, and documenting technology recommendations and 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.