docs February 2008

docs@lists.stg.fedoraproject.org

28 participants
38 discussions

Start a nNew thread

DuG
by Marc Wiriadisastra 13 Feb '08

13 Feb '08

Hey all, Quick question is the spelling Xfce or XFCE to match KDE and GNOME. Cheers, Marc

3 2

Meeting with RH Docs team
by Paul W. Frields 12 Feb '08

12 Feb '08

Can Fedora Documentation folks be available next Wednesday evening after hours (EST) for an ad hoc meeting about the new RH Docs team's "publican" documentation tools? You'll especially want to attend if: * You're on the steering committee * You do (or intend to) work on the Release Notes or other formal documentation I would like to give a time to the RH Docs team by NLT Tuesday -- just reply here with times you CANNOT do. Please remember that RH Docs team is in Brisbane, Australia, which is UTC +10 (or 15 hours ahead of EST). When it's 6:00pm Eastern, it's 9:00am the next day in Brisbane. Therefore, we really need to do this after hours, at least on the East Coast. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

9 13

Publican demo meeting
by Paul W. Frields 11 Feb '08

11 Feb '08

Looks like we have plenty of Fedora Docs people who can meet at 0200 UTC, Thu 14 Feb. That equates to 2100 EST(-5)/1800 PST(-8), Wed 13 Feb. See you guys then! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

some leadership thoughts
by Karsten Wade 11 Feb '08

11 Feb '08

I want to throw out a couple of quick thoughts after some recent discussions. We haven't done the best job in enabling leaders in this project to become leaders *of* this project. For example, there is a fair bit of institutional knowledge scattered across the DocsProject pages and within my brain, Paul's brain, etc. Any new leader is challenged by that; becoming aware of all the subtlety of why and how we do things in Fedora Docs is a real challenge. Our focus has been on enabling new writers, and I think we've been fairly successful at making that work (look at all the great content work happening right now.) But when it comes time to enabling leaders to step forward and lead, small parts to large parts, there are some gaps. For example, what actually are the responsibilities of a 'Lead Writer'? I know in my own head, and maybe you do, too, but are they the same thoughts? Etc. Ultimately this makes it hard to attract new leaders to the steering committee or to grow a leader who can take over the project as the Chair/Docs Project Lead. When I took on this role some years ago, the explicit goal was to get the project going and get out of the way, making room for others to lead from within the larger Fedora community. For the most part, that goal has not been accomplished. This is not to say, "I'm tired of Docs and I want out." Actually, I've never been more excited to be a part of this team! But I don't want to keep all the fun to myself. Recently I've been talking with some of the other steering committee members (Paul, Bob, John) about how to improve on this. One idea we've had is to create a new position (Vice Chair). This position is intended to last for six months, at which point the person should be elected by the steering committee into being the Chair for the project. A Chair would then sit for a fixed period of time (12 months?), which gives enough time to bring another person up through the Vice Chair and be in position to be the next Chair. Anyway ... just wanted to get these ideas out there for larger discussion. At the least, let you all know, "There is room in the leadership circle for you." - Karsten "Sometimes the best way to lead is by getting out of the way." -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

1 0

reminder: FDSCo meeting at 2100 UTC on #fedora-meeting
by Karsten Wade 11 Feb '08

11 Feb '08

SSIA -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

3 6

Re: Meeting with RH Docs team
by Mike Dittmeier 08 Feb '08

08 Feb '08

what time? ----- Original Message ----- From: "Paul W. Frields" To: "For participants of the Documentation Project" Subject: Re: Meeting with RH Docs team Date: Fri, 08 Feb 2008 02:10:54 -0500 On Thu, 2008-02-07 at 18:26 -0800, Karsten 'quaid' Wade wrote: > On Thu, 2008-02-07 at 18:32 -0500, Paul W. Frields wrote: > > Can Fedora Documentation folks be available next Wednesday evening after > > hours (EST) for an ad hoc meeting about the new RH Docs team's > > "publican" documentation tools? > > Is this teleconf or IRC? Sorry for not being clear -- this would be IRC. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug << signature.asc >> -- fedora-docs-list mailing list fedora-docs-list(a)redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list Mike Dittmeier mike(a)vegasitpros.com

2 1

Encryption and Privacy Guide Input
by Eric Christensen 08 Feb '08

08 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A week ago I made some changes to the Encryption and Privacy Guide [1] (EPG) that was going to spread out and categorize all the information that you could possibly put into such a document. Quaid gave me a moment of pause when he said that we need to focus on Fedora-specific information. I agree and disagree at the same time. I don't think we need to reproduce a bunch of information that is already out there but I've also been taught to not keep telling people to go somewhere else for information. Here is what I propose... In order to provide a comprehensive guide that covers privacy and encryption that is available to Fedora I think we should cover in depth the Fedora-specific information while providing a summary and alternate paths for getting information for items that are more Linux-specific. There is already non-Fedora-specific information in our Docs (like a guide for using GPG [2}) that could be rolled into the EPG as a summary. ~ This would allow a guide that would be encompassing while not rewriting the book on everything security. Thoughts? Eric [1] http://fedoraproject.org/wiki/Docs/Drafts/CryptoGuide {2] http://fedoraproject.org/wiki/DocsProject/UsingGpg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHp9OyL5V8yddJCO0RAqMhAJ99TVTCcX2u1FY+3AqL8fzqtw64DwCfVjYE s25JnCmtL25dcvyJVWdemys= =xw7E -----END PGP SIGNATURE-----

2 1

Moin 1.6 Upgrade
by Mike McGrath 08 Feb '08

08 Feb '08

We've successfully gotten a Moin 1.6 install up and migrated. Time for us to sit down, take a look and let us know what's up. Here's the ticket. There's likely to be lots of non-blocking bugs during this upgrade. We'll have to find how different things are. http://publictest10.fedoraproject.org/wiki/ <-- Wiki https://fedorahosted.org/fedora-infrastructure/ticket/337 <-- ticket Please place all notes, comments, questions, etc in the ticket. -Mike

4 4

Single Sourced Summary
by Jonathan Roberts 06 Feb '08

06 Feb '08

Hey all, We're going to try something new for the various release notes/summaries/overviews and see how we go. The plan, and excuse me if I get any details wrong, looks like this: [NB: the big misconception here, I've had it too!!, is that the SingleSourceSummary is not meant to be read from start to finish, but to increase co-ordination in working on these separate docs so we don't duplicate effort] Create a wiki page /Releases/SingleSourceSummary Flesh out that page with sections for: a) Press Release style summary b) Detailed Overview covering all features on /Releases/#/FeatureList either alphabetically or by coolness (latter is debatable as to how we would decide this!). This content is intended to be similar to the Alpha release notes, but with more! c) Technical Summary - brief but aimed at tech journalists d) Detailed Technical Summary - detailed and aimed at geeks, similar to release notes content now. This can then be split out by Include() to create targeted documents, such as press release, cool hip friendly marketing, release notes detailing technical changes etc... We'll then keep developing this page throughout the release cycle, and before each milestone (beta next) tidy up and make static versions of split docs so not to kill wiki. The idea is that by developing all this in one location we won't duplicate any work - we can see what is done and what's not done. Does this make sense? I'm planning on beginning to flesh out the structure of the page this coming week but dive in ahead of me if you like! Best wishes all, Jon

1 0

Self-Introduction: Vladimir Glafirov
by Vladimir Glafirov 06 Feb '08

06 Feb '08

Hi, all. I would like to participate in Fedora Project as a translator of technical documentation or programs from English to Russian or opposite :) Name: Vladimir Glafirov City: Geneve Country: Switzerland Status: System Administrator/Architect Company: CERN (cern.ch) Computer Skills: 8 years of Linux/UNIX administration and development Languages: Russian (native), English (foreign, fluent), French (basics)

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

docs February 2008