docs March 2007

docs@lists.stg.fedoraproject.org

32 participants
70 discussions

FDSCo pages updated
by Robert 'Bob' Jensen 11 Mar '07

11 Mar '07

I updated the Steering Committee page[1] with our new FDSCo members. I also created a meeting agenda page[2] and updated the meeting time information. [1] http://fedoraproject.org/wiki/DocsProject/SteeringCommittee [2] http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/MeetingAgenda -- Robert 'Bob' Jensen * * http://fedoraproject.org/wiki/BobJensen gpg fingerprint: F9F4 7243 4243 0043 2C45 97AF E8A4 C3AE 42EB 0BC6 Fedora Docs Projects FDSCo http://fedoraproject.org/wiki/DocsProject

3 2

FDSCo agenda 11-Mar-2007 Item 2 Meeting Location
by Robert 'Bob' Jensen 11 Mar '07

11 Mar '07

It has been suggested that we hold our meetings in #fedora-meeting. As a group we should decide this for ourselves and choose the venue that works best for our project. -- Robert 'Bob' Jensen * * http://fedoraproject.org/wiki/BobJensen gpg fingerprint: F9F4 7243 4243 0043 2C45 97AF E8A4 C3AE 42EB 0BC6 Fedora Docs Projects FDSCo http://fedoraproject.org/wiki/DocsProject

5 5

FDSCo agenda 11-Mar-2007 Item 3 FDP Schedule
by Robert 'Bob' Jensen 10 Mar '07

10 Mar '07

We have a schedule that is dependent on others as release time approaches we keep this schedule updated as the release date shifts. The schedule can be found at http://fedoraproject.org/wiki/DocsProject/Schedule We will need to look at the current schedule discuss the time line we have before us and also find a volunteer to manage changes to the schedule as target dates change. -- Robert 'Bob' Jensen * * http://fedoraproject.org/wiki/BobJensen gpg fingerprint: F9F4 7243 4243 0043 2C45 97AF E8A4 C3AE 42EB 0BC6 Fedora Docs Projects FDSCo http://fedoraproject.org/wiki/DocsProject

2 1

FDSCo agenda 11-Mar-2007 Item 1 Project Lead
by Robert 'Bob' Jensen 10 Mar '07

10 Mar '07

With our new status as the first fully elected FDSCo we need to choose a Project Lead. We should also discuss what our options are to ensure a smooth transition in this time of change. 1. Elect new chair/project leader [MEETING DECISION] 1.1 Decide if chair is 12 mon. or 6 mon. position? [MEETING DECISION] -- Robert 'Bob' Jensen * * http://fedoraproject.org/wiki/BobJensen gpg fingerprint: F9F4 7243 4243 0043 2C45 97AF E8A4 C3AE 42EB 0BC6 Fedora Docs Projects FDSCo http://fedoraproject.org/wiki/DocsProject

1 0

bullets/lists not rendering right on wiki?
by Sam Folk-Williams 10 Mar '07

10 Mar '07

Hi, I'm noticing that the syntax for bullets and numbered lists seems no longer to be working as expected. I wonder if this is due to the template change? For example, see http://fedoraproject.org/wiki/FedoraXenQuickstartFC6 Under the "system requirements" section, for instance, has the right syntax in the raw text: * bullet * syntax * as such But it renders as an indent with extra spaces between each line. Is this a known issue? Thanks, Sam -- Sam Folk-Williams, RHCE Red Hat Global Support Services Phone: 919/754-4558 GPG ID: 1B0D46BA

2 2

Comments on DUG update
by John Babich 07 Mar '07

07 Mar '07

FDP Team Members (especially those at Boston FUDCon): Some quick feedback on the Desktop User Guide: 1. I really like the added anchors in the DUG and the linking from the Sections list to the anchors. 2. Would it be a further improvement to combine the TOC with this section guide and refer to it all as the Table of Contents? 3. On this page regarding "Communications", http://fedoraproject.org/wiki/Docs/DesktopUserGuide/Communications, I originally explained (in an admonition) that all IM accounts, with the exception of Jabber, had to be created beforehand according to each protocol provider. See http://gaim.sourceforge.net/faq.php#q15. If this has changed, let me know otherwise, but this is according to Gaim's official FAQ. 4. Finally, is this just moving to a new location for the wiki, or is it being prepared for conversion to DocBook XML? 5. Remember that the /Docs/Drafts/ location is referenced by the existing default home page. I'm looking forward to joining you on IRC later today. Enjoy FUDCon, John Babich

5 8

Self Introduction Ben Williams
by jbwillia＠fedoraunity.org 07 Mar '07

07 Mar '07

* Ben Williams * Blacksburg VA USA * Windows-Linux Specialist * Department of Mathematics Virginia Polytechnic Institute & State University * My goal for the Fedora is for it to be the best linux distro * Historical qualifications o I consider myself a novice at computer, enjoy learning more and more everyday. started using linux with RH4 (not rhel4). o I am a Windows System-Admin by training, but i also maintain and 50 linux boxes on a daily basis. o I deal with 250 endusers on a daily basis pub 1024D/295A4FBC 2007-02-15 Key fingerprint = 7DC7 B470 4AEC 0187 A7EF 80D0 1957 4336 295A 4FBC uid James B. Williams <jbwillia(a)math.vt.edu> sub 1056g/6E2873A7 2007-02-15

3 2

no FDSCo meeting today, Sunday first new meeting time
by Karsten Wade 07 Mar '07

07 Mar '07

We had a short discussion in #fedora-docs and decided that we could finally retire the Tuesday meeting time. So, 0100 UTC is no longer. :) We're going to meet on Sunday this week 11-Mar-2007 at 1600 UTC on #fedora-docs. In that meeting we'll ratify (if we need to) that our next meeting will be the first of an alternating time. We'll set a time for Mondays based on what we all blocked. - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

3 2

conduct of meetings and voting in FDSCo
by Karsten Wade 05 Mar '07

05 Mar '07

We just had a proposal/idea on #fedora-docs: * The mailing list is for making decisions * IRC meetings are for discussions, working-on-stuff * FDSCo can call a vote/consensus check in IRC if 4+ members are present: - If only 4 members, the vote must be unanimous - If not unanimous, vote must be put-off for a majority presence - If only 5 members, the vote must be 4+ - If fewer than 4 members, send a message to the list - If urgency/emergency situation, the members present on IRC make the best decision they can, alert the list, and hope for the best - This kind of thing happens around release time when release engineering needs a decision and we have five minutes to decide or lose our chance. :) * We have the ability to call for a consensus check or vote on IRC even when a formal meeting is not being held: - Notice must be sent to the list so members not present can have a say - Decisions made this way can change after more list discussion - The email you are reading as self-referential example of this The idea is to make it a pleasure to attend meetings but not mandatory. The pleasure is that, for the most part, the FDSCo participants have preferred a "working meeting"-style instead of a "decision making"-style of meeting. Working can mean "active discussion and problem solving", which can lead to decisions that are sent to the list (like this message!) Because decisions are not the focus of an IRC meeting, it means that FDSCo can have meetings at dual-times to cover all members timezones, and there is not an obligation to attend. Discussion and decision is pushed to IRC. But there is room to make decisions in a fair manner. Then our fixed meeting time/window becomes a place to: 1. Check/update status 2. Regroup and reissue the week's agenda The outcome of this fixed meeting is: 1. A log to IRC 2. An updated of scheduled tasks 3. A new thread for the week that details the new/updated agenda under discussion/decision Thoughts? - Karsten -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

3 3

agenda for 06-Mar-2007 FDSCo meeting
by Karsten Wade 03 Mar '07

03 Mar '07

We have a few items that have backed up to deal with; please help me make sure that enough of these *decision* items make it on the agenda. Bringing them up on-list means we can work out the details *before the meeting*. This is a new paradigm for FDSCo, but one we have all spoken of following (iirc). ;-) 0. Meeting time -- [LIST DECISION] 1. Elect new chair/project leader [MEETING DECISION] 1.1 Decide if chair is 12 mon. or 6 mon. position? [MEETING DECISION] -- on-list discussion? 2. Meetings on #fedora-docs v. #fedora-meeting [MEETING DECISION] 3. Confirm FDP schedule for F7 [LIST DISCUSSION],[MEETING DECISION] 4. AOB -- Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

4 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs March 2007