January 2008 - docs - Fedora mailing-lists

Translated WIKI: Fedora Overview
by Marcelo Martínez 04 Feb '08

04 Feb '08

Hello everyone! I think it is very important that this section be translated into other languages: http://fedoraproject.org/wiki/Overview I will talk with a friend who has a better English to translate the Spanish section. When I get the translated text will posted here. Regards, Marcelo .- --

8 8

One Summary outline draft
by Karsten Wade 04 Feb '08

04 Feb '08

How does this outline look? http://fedoraproject.org/wiki/KarstenWade/Drafts/OneSummary ... in trying to be inclusive for all the parts of the Project. -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

4 7

Spam Mail and Fedora-docs subscribers
by John Babich 04 Feb '08

04 Feb '08

Fedora Infrastructure Team: For the past several weeks, the Fedora Docs list has been hit hard (at least 500+) with spam e-mails. They get rejected, but, I, as an owner of the list, am getting flooded with these rejected notices, making my job harder. I also notice an increase in unsubscribe notices, which may be unrelated. Can you please check this out and let me know if there is anything that can be done to tighten up the filters? I know there are at least 3 other list owners of Fedora-Docs-list who are being affected. Best Regards, John Babich Member, Fedora Docs Steering Committee (FDSCo)

3 2

Fedora howtos ?
by Valent Turkovic 03 Feb '08

03 Feb '08

Hi, I am wondering where can I find official howtos for Fedora? if there are no official howtos are there any good other online resources? Cheers, Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic

8 21

Features for F-9
by Marc Wiriadisastra 01 Feb '08

01 Feb '08

Hey all, Just listing some features which were are documented for F-9. It might be an idea to see what changes are going to take place specifically to update the docs. The other links are more for people to know what has been approved and will make it into Fedora. The install guide may need to be looked at. Cheers, Marc http://fedoraproject.org/wiki/Releases/FeatureEncryptedFilesystems http://fedoraproject.org/wiki/Features/PreUpgrade http://fedoraproject.org/wiki/Anaconda/Features/SecondStageInstallSource

2 3

FDSCo Meeting 2008-01-29 Summary
by Karsten Wade 30 Jan '08

30 Jan '08

Summary of 2008-01-29 FDSCo meeting Attendees: ---------- KarstenWade (quaid) BartCouvrier (couf) BobJensen (EvilBob) JaredSmith (jsmith) ... and friends: ---------------- EricChristensen (Sparks_too) JohnPoelstra (poelcat) JesseKeating (f13) Summary: -------- * Draft idea of what One Summary could look like: - http://fedoraproject.org/wiki/KarstenWade/Drafts/OneSummary ACTION :: List discussion on approach * Fedora Docs asks feature owners to do their duty - Feature owners have the onus to document their feature "If it's worth adding a new feature, it's worth documenting it." - Fedora Docs is going to request of FESCo that the feature process be amended to make release notes a blocking requirement ACTION :: poelcat - make Feature/*/ReleaseNotes a separate page pulled in with an Include() so that Docs + Marketing can watch that content? ACTION :: quaid sending email to f-devel-l to gain consensus ACTION :: FDSCo to raise request to FESCo * F9 Alpha release notes one-sheet - These notes should come from the testing/QA plans ACTION :: quaid to send email to f-devel-l * Software Management Guide - Converted to XML in CVS - Ready for draft pub edit - To include PackageKit if it drops for F9 in time - Target for March beta * Crypto Guide - Initial content confirmed - Researching other additions - Target for March beta? * Administration Guide and Desktop User Guide - On target for March beta * List moderation - Fedora Docs has three lists: f-docs-l, f-docs-commits, and f-relnotes-content - EvilBob requested assistance moderating f-docs-commits - We can share this moderation outside of FDSCo * FDSCo Chair election - Item pushed to next week's agenda -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

1 0

Self-introduction: Naranhuu Uridiinbish
by naranhuu uridiinbish 30 Jan '08

30 Jan '08

Hi, I'm Narankhuu Uridiinbish. I live in Tokyo, Japan and am from Mongolia. I'm a student of Tokyo Intitute of Technology, and learning for IT. I just started to translate Fedora into Mongolian , so I would like to translate the documentation of Fedora to Mongolian. Best regards, Narankhuu Uridiinbish pub 1024D/449582BD 2008-01-28 Key fingerprint = D01D D85F 6F6D 3A3A D615 C4F1 D235 4C99 4495 82BD uid narankhuu <naranhuu(a)gmail.com> sub 2048g/774E5AAB 2008-01-28

2 1

Ready for Review: Software Management Guide
by Eric Christensen 29 Jan '08

29 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just got finished putting some information into chapter nine for Yum-Utils. I will probably go back and revisit what I wrote tomorrow but I think the entire guide is ready for review and editing. The contributers before did a real good job of documenting Yum and the associated programs so there shouldn't be too bad off. Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHn+oEL5V8yddJCO0RAjJtAJ44MsCDswemIeWeqyTZxMRndi4OOgCfYQCd p8zUidopo/T/ygds0LPc8fA= =YPhs -----END PGP SIGNATURE-----

1 0

FDSCo Meeting 2008-01-29 IRC log
by Karsten Wade 29 Jan '08

29 Jan '08

HTML here: http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings/Minute… 13:05 < quaid> <meeting> 13:05 < quaid> http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings#Agenda 13:06 < quaid> does it mean something that when I start to type "fedor..." in Firefox, it is the Meetings page that comes up first in the history? 13:06 < quaid> ok, so far I've seen 13:06 < quaid> present: quaid, couf, EvilBob 13:07 < quaid> which is good enough to start something 13:07 * quaid . o O { game of whist? } 13:07 < EvilBob> jsmith is here 13:07 < quaid> sorry 13:07 < quaid> present: jsmith :) 13:07 < quaid> quorum! 13:07 < couf> so quorum :-) 13:07 < jsmith> YEah, I'm here 13:07 < quaid> jinx 13:07 < jsmith> Sorry, trying to do five things at once 13:08 < quaid> no worries 13:08 < quaid> let's see ... why discuss the one summary update? 13:08 < quaid> I think there is some confusion still in what we can do 13:08 < quaid> poelcat: if you are here, your input is appreciated on this topic 13:09 * poelcat is here 13:09 < quaid> I want to ponder ... can we do it all in one page with so many different focuses? 13:10 -!- kital [n=Joerg_Si@fedora/kital] has quit [Read error: 113 (No route to host)] 13:10 < quaid> poelcat: btw, my *sigh* over the group release summary was global not targeted; we've let the different summaries get out of control, so that was more self-recrimination than anything 13:10 < EvilBob> this is the one sheet for the release notes? 13:10 < quaid> aye 13:11 < poelcat> quaid: np :) 13:11 < quaid> relnotes OverView + Release/#/Summary + press kit + any other release summary usasges (press releases, etc.) 13:11 < poelcat> hard to say... there are so many focuses and yet so few people that consistently fill out all the details 13:12 < quaid> per feature you mean? 13:12 < quaid> or who come from a feature and fill out the master? 13:12 < poelcat> yes, per feature or enhancements 13:13 < quaid> ok, do we know enough right now about this topic to make a decision? 13:13 < couf> keep a master list, with links to developper/user-specific info? 13:13 < quaid> or do we punt back to the list for more discussion 13:13 < quaid> ? 13:13 < poelcat> one possibility i just thought of 13:13 < poelcat> is have the docs team "own" the 'release notes' and 'documentation' sections of the feature pages 13:13 < poelcat> in terms of making sure they get completed 13:14 -!- fab_away [n=bellet(a)bellet.info] has quit ["Leaving"] 13:14 < poelcat> divide among doc writers so each feature has a "doc owner" 13:14 < poelcat> they can then collaborate with the feature owner 13:14 < poelcat> which could also be parlayed into the release summary? 13:16 -!- tibbs [n=tibbs@fedora/tibbs] has quit ["Konversation terminated!"] 13:16 < jsmith> OK...short term gain, but long term is that sending the right message? 13:16 -!- mether [n=ask@fedora/mether] has quit ["Ex-Chat"] 13:16 < poelcat> what is the "right message" ? 13:17 < jsmith> I thought the message was "If it's worth adding a new feature, it's worth documenting it." 13:17 -!- fab_away [n=bellet(a)bellet.info] has joined #fedora-meeting 13:18 < jsmith> (putting the onus on the person responsible for the feature to add some basic documentation to the feature page) 13:18 < poelcat> jsmith: I would agree with that statement; i'm not sure how many package maintainers would :) 13:18 < quaid> we are mixing discussions somewhat, i think 13:18 < quaid> the Release Notes section in a feature is different than the one summary discussion 13:18 < quaid> but they are interrelated, yes 13:18 < quaid> http://fedoraproject.org/wiki/KarstenWade/Drafts/OneSummary 13:19 < quaid> this is what I was thinking as an example of how to structure it 13:19 -!- ldimagg__ [n=ldimaggi@nat/redhat/x-4cbc4edc2440a198] has joined #fedora-meeting 13:19 < quaid> poelcat: in terms of your idea of per-feature writers, two answers: 13:19 < quaid> yes, we have beat writers for that purpose 13:19 < quaid> no, we have a historical resources issue, and that model doesn't scale as well 13:19 < quaid> I prefer to have Docs + Marketing watch that area 13:20 < quaid> maybe we can make Feature/*/ReleaseNotes a separte page that is Included()ed 13:20 < quaid> then it is easy to have that watched by a group who can help devels 13:20 < quaid> so people can dump they brains in there and we'll help them massage it over time 13:21 < EvilBob> +1 13:23 < quaid> poelcat: I'm writing an email for f-devel-l to tackle relnotes in the features; I am going to propose they be a blocker 13:23 < jsmith> +1 13:24 < couf> +1 13:24 < quaid> as for this topic ... :) 13:24 < quaid> how about I bounce that draft outline to the list and we can discuss it there? 13:25 < jsmith> Sure, sounds good. 13:25 < EvilBob> Sure 13:26 -!- ldimaggi_ [n=ldimaggi@nat/redhat/x-5f368509762a0e12] has quit [Read error: 110 (Connection timed out)] 13:26 < quaid> done 13:27 < quaid> moving on 13:27 < poelcat> quaid: blocker in terms of whether something is "feature complete"? 13:27 -!- quaid changed the topic of #fedora-meeting to: FDSCo - Update on active content work 13:27 < quaid> poelcat: yes 13:28 < quaid> poelcat: it mainly involves changing "should complete this page" to "must complete this page" in the Process 13:28 < quaid> it is otherwise quite clear in the process that release notes (as wel as the entire feature page) is pretty needed 13:28 < quaid> except the feature process itself does not enforce completing a feature page, afaict 13:30 < quaid> ok, back on topic :) 13:30 < EvilBob> We have a topic? 13:30 * quaid looks at the /topic 13:31 < quaid> ok ... it looks like we haven't really asked if anyone wants to do the one-sheet for F9 alpha ... 13:31 < quaid> I did try to blackmail f13 last time we met, but that seems to have failed 13:32 < quaid> f13: the one-sheet relnotes we do for alpha and beta are really for QA, testing, and releng to highlight what they want testers to be thinking about; 13:32 < quaid> what is a good way to gather that info? 13:32 < quaid> we can open the wiki page and send invites to ... ? 13:32 < f13> fedora-devel-list ? 13:32 < f13> feature owners? 13:34 < quaid> http://fedoraproject.org/wiki/Releases/9/Alpha/ReleaseNotes 13:34 -!- GeroldKa [n=GeroldKa@fedora/geroldka] has joined #fedora-meeting 13:34 < quaid> k 13:34 < poelcat> quaid: https://bugzilla.redhat.com/showdependencytree.cgi?id=428703 13:34 < poelcat> for "known issues" 13:35 < quaid> cool 13:38 < jsmith> Next? 13:39 < quaid> yes, thanks 13:39 * quaid was emailing 13:39 < f13> also.. 13:39 < quaid> DUG? AG? SMG? Crypto? 13:40 < f13> http://fedoraproject.org/wiki/QA/9/AlphaTreeTesting 13:40 * Sparks_too needs to bail soon but would like to talk about SMG, Crypto, and Policy Kit 13:41 -!- giallu [n=giallu(a)81-174-45-111.dynamic.ngi.it] has joined #fedora-meeting 13:41 < quaid> Sparks_too: go ahead ... 13:42 < Sparks_too> The SMG is pretty much done... 13:42 < jsmith> I've got the doc-of-many-names in CVS (yum-software-management-guide-thingy) in CVS, but I haven't yet edited it for content. 13:42 < Sparks_too> I'm still working on the yum-addons (yum-util)... 13:42 < jsmith> Hoping to find time for that this week 13:42 < Sparks_too> but it is pretty much done. 13:43 < Sparks_too> I'm also attempting to get information on PackageKit that can be included if it is included in F9. 13:43 < Sparks_too> I hope to finish the yum-addons tonight. 13:44 < Sparks_too> Crypto: I have verified the step-by-step instructions for encrypting your /home partition. I still have a lot of research to do for some other items that need to be included. 13:44 < Sparks_too> That is all I got. 13:45 < jsmith> herlo has converted that section of the Crypto guide to DocBook 13:45 < jsmith> I'll be going over it w/ him later this week 13:47 < quaid> Sparks_too: I know one expert (the original author of the CryptoGuide) has been watching carefully, so he'll let you know if he sees anything bad 13:47 < quaid> we want that one out for F9 13:47 < quaid> then there is better chance that the next RHEL can pick up the content :) 13:47 < quaid> (which is missing from RHEL 5 docs :( ) 13:48 < Sparks_too> quaid: Okay, I'll make that a priority right after the SMG. 13:48 < quaid> Sparks_too or jsmith was going to file a bug about making a new component for the SMG 13:48 < quaid> ok 13:48 -!- trashy [n=trashy@fedora/trashy] has left #fedora-meeting ["Leaving"] 13:48 < quaid> AG and DUG have been updated on list ... 13:48 < quaid> poelcat: did you see the strawman schedules couf put up? 13:48 < jsmith> quaid: What exactly do you mean by "component"? A component in Bugzilla? Or something else? 13:48 * quaid hadn't gone to see if there were any dependency conflicts, etc. 13:48 < quaid> jsmith: yes bugzilla component 13:49 < quaid> it was Sparks_too I was chatting with i guess 13:49 < jsmith> Wasn't me. 13:49 < Sparks_too> quaid: If you want, you can have all SMG bugs go to me if you like. 13:49 < quaid> Sparks_too: put that in the bug you file, that you should be the component owner 13:49 < Sparks_too> quaid: Okay. 13:50 < quaid> I'll recall later how we do that; i know how to fix the CVSROOT/modules but am not clear if that auto-updates bz 13:50 < quaid> beats ... 13:50 < quaid> i'm going to blog about it, send out a reminde rto f-devel-l 13:50 < Sparks_too> quaid: Should we just rename yum-software-manangement to Software Management Guide? 13:50 < quaid> feel free to start bugging people to assign beat writers 13:50 < quaid> Sparks_too: perhaps, unclear if that is how it works 13:50 -!- bzbot is now known as buggbot 13:51 * quaid realizes he needs to leave at five minutes to the hour so we can make the Board meeting call from his house :) 13:51 < quaid> so ... 13:51 < EvilBob> Sorry all I have been away for the last 20 minutes dealing with a staff situation here 13:51 < quaid> punting meeting time until next week 13:51 < quaid> and we still need to discuss chair/leader stuff, but we need to have that with the full FDSCo IMHO 13:51 < EvilBob> I have a couple real quick items that were not in the agenda 13:51 -!- quaid changed the topic of #fedora-meeting to: FDSCo AOB 13:51 < quaid> go mango 13:52 < EvilBob> I would like to put the Chair situation on the agenda for next week 13:52 * Sparks_too heads out... See everyone later this evening. 13:52 < EvilBob> also we have two moderated lists that we are in charge of 13:52 < EvilBob> fedora-docs-\* 13:53 < quaid> on the first item, sure, let 13:53 < EvilBob> I have been handling the moderator requests for list for a couple days and will keep doing so 13:53 < quaid> 's put it on 13:53 < quaid> I filter those requests to the side, to be honest 13:53 < EvilBob> can someone please take care of commits please 13:53 < quaid> because they are always spam 13:53 < EvilBob> nope 13:54 < quaid> really? 13:54 < EvilBob> we had one good message this week 13:54 < quaid> that's a shame 13:54 < quaid> from an external person not on the list? 13:54 < EvilBob> yeah the website question 13:54 < quaid> ah 13:54 < quaid> see 13:55 < quaid> perfect example of why I hate those ones :) 13:55 < quaid> I replied on list and no wonder he didn't reply 13:55 < EvilBob> it will take 5-10 minutes a day or a half hour once a week 13:55 < EvilBob> I will just let it go again now, in a month if no one picked it up I would like to ask that both lists share a password 13:56 < quaid> we can do that one for sure 13:56 < quaid> we can also invite other moderators than the SCo 13:56 < EvilBob> that makes it easier for me to log in to both and handle them 13:56 < EvilBob> that is all I have 13:56 < quaid> EvilBob: you want to go ahead and make the docs-commits password the same as the docs-list one? 13:56 < couf> sorry, got major phone call 13:56 < EvilBob> we can talk more next week' 13:56 < quaid> ok, I've got to jet myself 13:56 < EvilBob> quaid: I can do that 13:57 < quaid> buffer is above, I'll post the log etc. in a few 13:57 < quaid> EvilBob: thanks 13:57 < quaid> good point, glad you saw that post 13:57 < EvilBob> </meeting> 13:57 * quaid must have dumped good stuff in the past :( 13:57 < quaid> <== bad moderator, no donut! 13:57 < quaid> aye 13:57 < quaid> </meeting> -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

1 0

Meeting
by Paul W. Frields 29 Jan '08

29 Jan '08

Apologies, but I probably can't make today's meeting (2008-01-29). This is the last week for which making this meeting means leaving $DAYJOB early, and I simply can't swing it with so little time left. Carry on and I'll see you guys next time around. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

2 1

DuG
by Marc Wiriadisastra 28 Jan '08

28 Jan '08

Hey all, I've added a few more stuff to edit ready and I'm hoping someone will take a look at the remaining stuff for KDE. I'm also going to add KOffice I'm not to sure if it's the default install or not but I believe it is used enough to be added. Thoughts? Cheers, Marc

6 15

one summary to rule them all
by Karsten Wade 28 Jan '08

28 Jan '08

We've struggled for the last several releases with multiple release summaries and overviews, keeping them in sync, and so forth. Last release, Paul and I swore we would find a way to provide a single, canonical source for *all* of these. Today I noticed yet another release summary in the wild that needs taming, inclusion, or something: http://fedoraproject.org/wiki/Features/Policy#Enhancements A release summary is referred to there that can be added to by anyone. *sigh* Do we want to invite those people to instead add their enhancements to canonical summary? Then cross-link back in to that namespace? We can use clever [[Include()]] statements that draw only specific parts, so each 'mirror' of the canonical summary can show the most appropriate fragment. Anyone interested in doing this work? It involves: * Working out a single canonical location from amongst the several - Releases/#/ReleaseSummary - Docs/Beats/OverView - Press release needs (more lightweight) - etc. * Define a format for that page so that it can be fragmented (if needed) for different summaries * Write up a process for jamming all that together * Publicize/evangelize - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

4 5

New toy
by Ignacio Vazquez-Abrams 28 Jan '08

28 Jan '08

Yes, I should probably finish fixing the old toy, but here's something to occupy you in the meantime. https://bugzilla.redhat.com/show_bug.cgi?id=430578 -- Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com> PLEASE don't CC me; I'm already subscribed

2 2

downloads web page minor error
by Brian 28 Jan '08

28 Jan '08

Hi I don't know the correct way to pass on this information, so could you either advise me, or forward it. On the page http://fedoraproject.org/wiki/Distribution/Download The headings for the SHA1 checksums are not correctly associated with the value ====== * i386 (32-bit AMD, Intel Pentium, Intel Core Duo) * 782a0e80de1b8e9f24e10e40055cc1b545390cbd Fedora-8-i386-DVD.iso * x86_64 (64-bit AMD64, EM64T, Intel Xeon, Intel Core 2 Duo) * 88168a5fce834463944ffa714b6c1cf2c81824ea Fedora-8-x86_64-DVD.iso * PowerPC (32-bit and 64-bit Macintosh, 64-bit pSeries) * d4a12f8864eaccf09bf3a8790bd8d6b758b72f64 Fedora-8-ppc-DVD.iso ====== Cheers Brian

2 1

AG - DUG Tentative Schedule
by Bart Couvreur 27 Jan '08

27 Jan '08

Hi all, Just a basic schedule proposal to set some dates for both AG and DUG If this is good, we can add it to our master schedule [1] * now - 15 Feb: writing, shifting content, ... * 15 Feb: Basic deadline for guide writing, content should be edit-ready, and in the correct order * 16 - 22 Feb: Editorial pass on the wiki (to keep edits in wikik-rawhide too) * ?? 23: Wiki2XML tutorial day (might be a good idea) * 23 - 29 Feb: Wiki-to-DocBook conversion * 1 March: Launch of both guides (English version) + send off POT-files to L10N Comments? Bart [1] http://poelstra.fedorapeople.org/schedules/f-9/f-9-docs-details.html -- Bart <couf(a)fedoraproject.org> <couf(a)skynet.be> key fingerprint: 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93

3 2

GRUB
by Karl Larsen 26 Jan '08

26 Jan '08

I am looking for a user paper that explains how grub works and how you set it up with the Rescue DVD and such. I see nothing and guys on the Fedora List know nothing. Karl -- Karl F. Larsen, AKA K5DI Linux User #450462 http://counter.li.org. PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7

3 4

DUG + AdminGuide release, update
by Vladimir Kosovac 26 Jan '08

26 Jan '08

List, few of us had a meeting over on irc and have agreed on a few things: 1] DUG looks good[1] (GNOME) 2] DUG (KDE) almost as good - may need some attention depending on what KDE release goes in F9 3] New placeholder for AG conversion is https://fedoraproject.org/wiki/Docs/Drafts/AGBeta However, listed pages are still edited in their 'old' location: https://fedoraproject.org/wiki/Docs/Drafts/AdministrationGuide/$section As agreed, I have cleaned the AG of stuff that will not be included. Pages that had content are now in Docs/Drafts and the references to those that were empty are removed. The core group of 3-4 people have committed to early March completion of the AG, more hands on deck are more than welcome. [1] - ready for wordsmithing / format fixing Vladimir

5 15

Most Docs modules added in Transifex
by Dimitris Glezos 25 Jan '08

25 Jan '08

A quick heads-up to note that most of the Docs modules have now been added to Transifex: https://translate.fedoraproject.org/submit/module/ As soon as translators will start using Tx to submit files, we'll start to see commits similar to the following: > From: "Transifex System User" (transif) <fedora-docs-commits redhat com> > Author: transif > Log Message: > 2008-01-25 Dimitris Glezos <dimitris glezos com> (via glezos fedoraproject org) > > * po/el.po: Dummy update in Greek translation -d -- Dimitris Glezos Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) --

2 1

DuG Multimedia
by Marc Wiriadisastra 24 Jan '08

24 Jan '08

Hey all, Same as the Office one massive changes additional icons etc included. I felt there was a lot of text with minimal pictures so I added some pictures that do not require translation. http://fedoraproject.org/wiki/Docs/Drafts/DesktopUserGuide/Multimedia Thoughts? Cheers, Marc

1 0

DuG Office
by Marc Wiriadisastra 24 Jan '08

24 Jan '08

Hey all, Massive changes to http://fedoraproject.org/wiki/Docs/Drafts/DesktopUserGuide/Office Have a look and tell me what you think. I should add due to failure of connecting with this mornings ISP issues I will add more links. Cheers, Marc

2 1

FDSCo Meeting 2008-01-22 IRC log
by Karsten Wade 23 Jan '08

23 Jan '08

13:05 < stickster> <meeting> 13:05 < stickster> here 13:05 * couf 13:06 * EvilBob 13:06 * jsmith is here 13:06 < stickster> great! Quorum :-) 13:06 < EvilBob> sweet 13:06 -!- stickster changed the topic of #fedora-meeting to: Docs Project: F9 docs review 13:07 * Sparks is here somewhere 13:07 < stickster> OK, couf can talk about the AG status 13:07 < couf> OK 13:07 < couf> even DUG actually :-) 13:07 < stickster> Yes indeedy :-) 13:08 < couf> both AG and DUG are targeting release at F9-beta which is beginning of March 13:08 < couf> had a small meeting this weekend with the core group, meeting log and summary posted to the group 13:09 < couf> basic needs are input from KDE-knowlegable people for DUG and some server-fu specialists to check down AG 13:09 < jsmith> I'd be happy to look through the AG 13:09 < couf> both are pretty much on target as it is, so it's shaping up to become good 13:09 < stickster> couf: What recruiting are you and the other writers doing to get KDE people to examine the docs? 13:09 < couf> core group is committed to "get it done" so that's very good 13:10 * stickster has found the only way to get developers focused is by pestering them politely, loudly and repeatedly 13:10 < couf> we've tried to get the KDE-sig on board but they don't have manpower available 13:10 < couf> so we're going to track some people on the fedora-list, and probably try and trick some upstream guys into checking our work 13:10 < stickster> Some blogging might be good... 13:10 < EvilBob> couf: I will see if I can pick anyone out of #fedora that might be willing to step up 13:11 * stickster tries to think up some other ways to attract eyeballs 13:11 < couf> EvilBob: much appreciated 13:11 < stickster> messages to KDE docs team? 13:11 < couf> yep 13:11 * quaid is finally here 13:12 < stickster> I know Fedora has a thriving KDE user community -- *some* of those folks have to be interested in having good KDE docs! 13:12 < couf> blogging might be a good one too 13:12 < couf> indeed 13:12 < stickster> If we can't get KDE love, what's the drop back plan? 13:12 < stickster> Is there one? 13:12 < stickster> Hi quaid! 13:12 * stickster hands over gavel 13:12 < quaid> hola amigos y amigas 13:13 < couf> not really, the idea would be to use the KDE docs itself, but they have different licenses 13:13 < couf> which could be messy 13:13 < quaid> exactly 13:13 < couf> GFDL iirc 13:13 < quaid> that would be the upstreadm suggestion, typically 13:13 < couf> yeah 13:13 < quaid> so ... 13:14 < quaid> we have to pressure within the project 13:14 < quaid> and kindly ask without 13:14 < quaid> +1 to fedora-list asking 13:14 < quaid> is there one person doing this seeking for KDE help? 13:14 < couf> we've got some work on XFCE too, btw (jmbusser is handling that) 13:14 < couf> yeah, marc wiriadisastra is doing that 13:15 < quaid> fallback == beta has GNOME only, work on KDE for beta2? 13:15 * couf hopes he got that name right :-) 13:15 -!- Irssi: #fedora-meeting: Total of 85 nicks [1 ops, 0 halfops, 0 voices, 84 normal] 13:15 < stickster> couf: it's right :-) 13:15 < quaid> strikeforce++ 13:15 * nirik is happy to answer Xfce questions as well. 13:15 < couf> quaid: possible, yes 13:15 < EvilBob> nirik: thanks 13:15 < couf> the idea was to have both AG and DUG ready so we can tackle IG, relnotes etc after 13:16 < quaid> is there a schedule with milestones from here to beta? 13:16 < couf> not set in stone 13:16 < quaid> we need enough time to convert to XML 13:16 < stickster> For AG/DUG, maybe not -- for relnotes, http://poelstra.fedorapeople.org/ has milestones for things like relnotes 13:16 < quaid> with training for new folks, so make it a bit longer 13:16 < stickster> sorry, redundancy 13:16 < quaid> stickster: just an internal schedule so we are on time 13:16 < quaid> that is 13:16 < quaid> don't miss an obvious dependency, etc. :) 13:17 < stickster> poelcat can help us with that if we desire. 13:17 < couf> heh 13:17 -!- antgreen__ [n=green@nat/redhat/x-7afb8a70da5dec4d] has quit [Read error: 110 (Connection timed out)] 13:17 < quaid> couf: do you want final wordsmith and technical edits in Wiki or after in XML? 13:17 < quaid> i.e., where is it easier and does the other writers the most good? 13:17 * quaid thinks maybe wiki, from that ... 13:17 * stickster hopes he is not volunteering poelcat out-fo-turn 13:17 < couf> I think as it is now, we can have the DUG and AG ready by half Feb in wiki terms, which gives us a lot off time 13:18 < couf> quaid: would be best wiki-way, as to help for further versions, if me do them 13:18 < couf> s/me/we 13:18 < quaid> couf: can you make a draft schedule? just working backwards like that 13:18 < couf> sure 13:18 < quaid> include X days (5?) for wiki edit, and similar for conversion to XML 13:18 < quaid> ok, we can get poelcat to add it to the overall docs schedule after that 13:19 < quaid> and jmbuser can use the template for the DUG 13:19 * couf adds to TODO 13:19 -!- jlaska [n=jlaska@nat/redhat/x-9326078e383ea5fc] has joined #fedora-meeting 13:19 < quaid> yeah, then we can get the schedule to correctly reflect when we do the IG and relnotes work 13:19 < poelcat> just open a ticket at poelcat.hosted ;-) 13:19 < couf> so just want to give a thumbs up to both marc and vladimir, they been doing terrific work 13:19 < quaid> nice! 13:19 < stickster> Who's the man!?! 13:19 -!- antgreen__ [n=green@nat/redhat/x-49e6128e5ad7196e] has joined #fedora-meeting 13:20 < quaid> couf: +1 to that 13:20 < stickster> couf: amen 13:20 < quaid> I've been trying not to overpraise and stuff, but they are certainly worthy of the Big Fedora Love 13:21 * couf ends DUG-AG status 13:22 < quaid> ok, relnotes prep ... 13:22 < quaid> 1. time to start advertising the Docs/Beats for other contributos 13:22 < quaid> 2. recruit more dedicated help? 13:22 < quaid> we need someone with eyes like mether 13:23 < quaid> s/one/ones/ ? 13:23 < stickster> There have been a number of changes rolling in already 13:23 < quaid> yes 13:23 < quaid> here's the question from me ... 13:23 < quaid> we've tried the regular beat maintainers, and it is hot-or-miss 13:23 < quaid> most of the work comes from a small handful 13:23 < quaid> what is the right thing to do from here? 13:23 < quaid> <discuss> 13:23 < stickster> blog blog blog 13:23 < quaid> s/hot/hit/ :) 13:24 < quaid> ah, nagmail++ 13:24 < quaid> blognag 13:24 < stickster> Isn't that a town in Ireland? 13:24 < jsmith> Does it taste like eggnog? 13:24 < quaid> yes and yes 13:24 * stickster apologizes to any residents of the Auld Sod listening in 13:25 < couf> different approach maybe: starting from the features list and working through that to get the people behind them doing some content 13:25 < quaid> isn't there a section in the feature page for relnotes content? 13:26 < couf> d'oh, /me feels sheepish 13:27 < stickster> Ouch, wiki getting pounded today apparently. 13:27 < stickster> Yes, they each have a place for that content 13:27 < stickster> Doesn't appear to be filled in for at least some of them 13:27 * stickster hasn't counted but is not optimistic :-D 13:28 < quaid> couf: no, that is a good point 13:28 < quaid> couf: and another reason to blog, creating more attention :) 13:28 < quaid> poelcat: is completion of release notes/marketing spew required for a feature to be complete? 13:29 < quaid> this is the release we SWORE we would get the overviews synced and from one canonical source ... 13:29 < couf> ah that way it might be interesting 13:29 * EvilBob swears all the time anyhow 13:30 < poelcat> quaid: not exactly 13:30 < quaid> Marketing SIG may still decide to write up a higher level overview, but we can coordinate 13:30 < EvilBob> poelcat: fix that for F10 13:30 < stickster> Yes, we want to draw all OverView from one source 13:30 < poelcat> or at all :-/ 13:30 < EvilBob> lol 13:30 < quaid> poelcat: :( 13:30 -!- kital [n=Joerg_Si@fedora/kital] has quit [Remote closed the connection] 13:30 < poelcat> the focus is really on "does the functionality work" 13:31 < quaid> well 13:31 < stickster> "If a tree falls in the woods and no one hears it..." 13:31 < quaid> that's more of a focus of a package set :) 13:31 < poelcat> and when a feature is submitted prior to feature freeze a lot of times those things are TBD 13:31 < quaid> a feature needs more than that 13:31 < quaid> well, needs to be completed by some point, not at the start 13:31 < poelcat> sometimes rightfully and other times procrastination? :) 13:32 < quaid> poelcat: would you agree to the concept of "release notes and some attempt at a lousy marketing blurb" as a feature completion requirement? for the future, that is ... 13:32 < poelcat> quaid: i'll let someone else propose to FESCo that features be dropped if the release notes aren't complete ;-) 13:32 < quaid> ok 13:32 < poelcat> quaid: it seems reasonable to me, though I have a hunch the developers/maintainers may not agree 13:32 < quaid> poelcat: as Feature Wrangler, can you kindly ask folks when you interact with them to complete those parts by ... 13:33 < quaid> and we can see how that goes 13:33 < poelcat> quaid: glad to 13:33 < quaid> if there is universal adoption and no need for onerousness, why wrestle with FESCo on it? 13:33 * stickster will raise this with bpepple 13:33 < poelcat> and if there are particular ones you want me to nag, send me mail 13:33 < stickster> At least we should alert him what we're doing 13:34 < quaid> stickster: my point, as I'm sure you know, is that Fedora is more than a bunch of packages that work together :) 13:34 < stickster> Absolutely 13:34 < quaid> k 13:34 < quaid> all: please blog wihin the next 10 days about: 13:34 < quaid> * relnotes beats (Docs/Beats/) 13:34 < quaid> 0r * features content 13:34 < quaid> or * new beat writers 13:35 < quaid> anything else on this topic? 13:35 < couf> what needs to be done for the one-page relnotes? 13:35 * quaid waits for stickster ... 13:35 < stickster> Is there any concern about us now being another RH bureaucratic layer strangling poor, hapless developers who are trying to GTD? 13:36 < quaid> couf: hold that thought one sec ... 13:36 < quaid> stickster: but we are Fedora!!! :) 13:36 < quaid> stickster: for the features request? 13:36 < stickster> And you can too 13:36 < stickster> Right 13:36 < quaid> here's the thing, IMNSHO about features 13:36 < quaid> if you want to call yourself a feature and get the attention 13:36 < quaid> it means more than just completing shit and making it work on time 13:36 < jsmith> stickster: "I am Fedora and You Can Too"? 13:36 < stickster> jsmith: exactly 13:37 < quaid> it means you are willing to be called up to the stage in a conference to talk about it 13:37 < quaid> it means you are willing to be a community leader about it 13:37 < jsmith> stickster: That's the title of your next blog post, btw 13:37 < quaid> it means you are willing to do the marketing, sales, etc. 13:37 < stickster> jsmith: obsolete already I think 13:37 < stickster> quaid: +1, just FYI 13:37 < quaid> if not, then don't ask Fedora to "care" about your feature enough to devote so much time to it 13:37 < quaid> that's my thinking :) 13:37 < couf> +1 13:37 < stickster> We're just making sure that people watching this channel know *why* we're asking for this. 13:37 < jsmith> If it's worth writing, it's worth documenting/marketing/plugging 13:37 < stickster> Exactly. 13:38 < quaid> jsmith +1 13:38 < stickster> So, all you eavesdroppers -- make us care! 13:38 < couf> that's the idea :-) 13:38 < jmtaylor> should that be something that get added to the feature form? a note about expected commitment? 13:38 < quaid> stickster: thanks for the excuse to rant, though :) 13:38 < stickster> quaid: NP, I live to serve. 13:38 < quaid> jmtaylor: good question; not sure if that is part of the feature process or expectation, but I think it should be 13:38 < quaid> ok, now to couf's question ... 13:38 < quaid> the one-sheet 13:39 < quaid> we need content for it, and we can draw that from the existing state of Docs/Beats 13:39 < quaid> so we don't have to recruit for it, but we might want to. 13:40 < quaid> as a reminder of what the one-sheet is ... 13:40 < quaid> this is a single Wiki page that we can link from the alpha, beta ISOs 13:40 < quaid> so we can change it up to the last minute, link updated bug reports from it, etc. 13:41 < quaid> it also is a quick-overview of what is in this alpha, beta that is noteworthy 13:41 < quaid> supposed to be lower-impact work to Docs compared to what we did before, which was a full run from Wiki => XML + translation for each test release 13:41 < quaid> *whew* 13:42 < quaid> so, in many ways, the content "belongs" to release eng (f13), features (poelcat), etc. 13:42 < stickster> http://fedoraproject.org/wiki/Releases/8/Test/F8Test2/ReleaseNotes 13:42 < couf> quaid you steal my words 13:42 < couf> but do continue 13:42 < quaid> couf: maybe I should stop talking :) 13:42 < quaid> stickster: F8Test? 13:43 < stickster> That's the last one-sheet we did for the previous cycle 13:43 < quaid> oh, right, sorry 13:43 * quaid is lost in version numbering 13:43 < stickster> Just for reference in case people haven't seen that one 13:43 < stickster> There's a lot of copy/paste material in there. 13:43 < quaid> so we need Releases/9/Alpha/ReleaseNotes 13:44 < poelcat> quaid: good reminder for me to ping the feature owners for a status update 13:44 < couf> yeah, so same counts here: get blogging, news-spreading and let the people behind it create the content :-) 13:44 < stickster> Thank you poelcat: http://poelstra.fedorapeople.org/schedules/f-9/f-9-docs-details.html 13:44 * stickster notes the dates are a bit off because of the 1-week Alpha slide 13:45 < poelcat> stickster: i'll fix that 13:45 < stickster> poelcat: Thanks! :-) 13:45 < stickster> Fortunately it hasn't rippled 13:45 < poelcat> that's what I get for lurking on this channel... more action items :) 13:46 < quaid> heh 13:46 < stickster> poor poelcat 13:46 * EvilBob thinks that is how he became FDSCo 13:46 < stickster> Oh my, we're 40 minutes in and haven't covered a few other items 13:47 < quaid> yep, let's move on 13:47 < stickster> quaid and I have to bail in time to make the next meeting :-D 13:47 < quaid> aye 13:47 < quaid> ok, so IG 13:47 < stickster> So... IG. :-) 13:47 < quaid> two approaches: 13:47 < quaid> 1. raw recruit 13:47 < stickster> I can definitely *help* 13:47 < quaid> 2. build on what is working so far 13:48 < quaid> what I mean by 2 is, let's old and new hands make sure the AG and DUG hit their target, then that frees *all* of us up to split up the IG work 13:48 < quaid> in there we build the skills to do the relnotes work, as well 13:48 < stickster> right 13:48 < quaid> (which coinicidentally leads to the next agenda item :) 13:48 < couf> that's the basic goal yes 13:48 < stickster> Hey, how'd *that* get there?!? 13:48 < quaid> stickster: can you advertise for a co-maintainer who will take over post F9? 13:48 < stickster> jsmith is too modest 13:48 < stickster> quaid: absosmurfly 13:48 < quaid> and then set the expectation that you are there to mentor and the group is there to help? 13:49 < jsmith> stickster: Who, me? 13:49 < stickster> Yeah, you! 13:49 < stickster> quaid: +1 13:49 < stickster> That will be blog #2 tonight 13:49 * stickster already preparing blog #1 for relnotes 13:50 < EvilBob> stickster: I am willing to take that on if you mentor me, I do as many or more installs in a release lifetime as anyone 13:50 < EvilBob> stickster: plus I really need a document 13:50 < EvilBob> stickster: talking about the IG 13:50 < couf> EvilBob++ 13:50 < jsmith> :-) 13:51 < stickster> I am here to help whoever wants to take it on 13:51 < stickster> It's not *quite* as bad as it seems, honestly 13:51 < couf> jsmith: has the yum-guide :-) 13:51 < quaid> sorry, had to pay the heater repair fella 13:52 < quaid> ok, last item 13:52 < quaid> training 13:52 < quaid> we are doing a ton more wiki2xml this time 13:52 < quaid> so we really need a process, how-to, etc. 13:52 -!- loupgaroublond [n=yankee(a)pool-71-182-215-182.pitbpa.east.verizon.net] has joined #fedora-meeting 13:52 < jsmith> quaid: Agreed! 13:52 < jsmith> quaid: I'm happy to help write that, after I finish wrapping my head around it all 13:53 < quaid> let's cobble together our notes this week and have it as an action/task to have a beta usable how-to by next week? 13:53 < stickster> http://fedoraproject.org/wiki/DocsProject/Tools/Wiki2XML 13:53 < stickster> May just need to be refreshed 13:53 < jsmith> Fair enough 13:53 < quaid> yeah 13:53 < couf> +1 13:53 < jsmith> stickster: Why didn't you show me that last week? 13:53 * jsmith ducks 13:53 < quaid> that page + how-to with steps 13:53 < stickster> jsmith: Oops, I just remembered it because quaid triggered my supermnemonic memory with the title meme 13:53 < quaid> jsmith: leaky carpenter's roof? 13:54 < quaid> ironically ... I named that page, too, and forgot about it 13:54 * quaid updates WorkFlow 13:54 < stickster> This very topic is one that jsmith and I were working on the other night with the yum guide 13:54 < jsmith> quaid: The cobbler's kids have no shoes... 13:55 < jsmith> stickster: Speaking of which... I have a lot more things to go back through on the yum guide 13:55 < EvilBob> We do have another item we need to discuss, your successor, maybe next meeting or list? 13:55 < quaid> http://fedoraproject.org/wiki/DocsProject/WorkFlow 13:56 < quaid> EvilBob: yeah, we do, let's go for the list perhaps 13:56 < quaid> we still need a meeting time where all can meet :) 13:56 < EvilBob> right 13:57 < couf> so anything left? 13:58 < EvilBob> OK </meeting> ? 13:58 < quaid> nope 13:58 < quaid> 5 13:58 < quaid> 4 13:58 < quaid> 3 13:58 < quaid> 2 13:58 < quaid> last chance! 13:58 < quaid> 1 13:58 < quaid> </meeting>

3 6

Documentation Feature for Fedora 9
by Karsten Wade 23 Jan '08

23 Jan '08

Something I glanced on IRC this morning ... < mwiriadi> I think docs for F-9 will be a huge + for the distro ... set off a spark in my head. What do you all think of putting forward "more and better 100% community produced documentation" as a feature for Fedora 9? If you look at the definition of a feature[1], you see that it is "a significant change or enhancement to the version of Fedora currently under development that may or may not include new packages." Sounds like our current workload to me. :) One benefit is that our feature becomes part of the formal list of features that we promote for the release. How does this sound? We ready for more spotlight? Anyone interested/excited to write up our feature and remain the point of contact for it? - Karsten [1] http://fedoraproject.org/wiki/Features/Policy#Definition_of_a_Feature -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

2 1

Publishing translated DuG and Administration Guide in a magazine
by Nicolas A. Corrarello 23 Jan '08

23 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I'm trying to contact a local magazine editor and get them to distribute a one time edition of a Fedora Magazine with a F8 dvd (maybe 9 by the time) with the DuG and the Administration Guide. Might be a useful project to all countries. But I wanted to check before with you the legal aspects regarding that. Can we publish those documents without any legal paperwork done? - -- - - -- Nicolas A. Corrarello Fedora Ambassador Argentina c: +54 (911) 5182-2245 e: ncorrare(a)fedoraproject.org GPG Key: DFC893EE h: fedoraproject.org/wiki/NicolasCorrarello/ GPG Fingerprint: 5C93 42DA 98E1 4EEF B24B 7F8C E145 B2F9 DFC8 93EE Import my key: $ gpg --keyserver pgp.mit.edu --recv-key 0xDFC893EE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHlz1e4UWy+d/Ik+4RAq1ZAJoCAWOGCyrY78eB83chvDHEgGFl9QCeOqlb ErOB7jmzLuY3l+v89wXuueI= =Dm7P -----END PGP SIGNATURE-----

4 3

Up-stuffed
by Marc Wiriadisastra 23 Jan '08

23 Jan '08

Hey all, Can someone remove the chapter I added. I originally thought the whole thing was getting done in cvs/docbook I was incorrect and it is done on the wiki. The file that I committed is irrelevant since the wiki has an updated version of it. Removal would be very muchly muchly appreciated :) Apologies for the inconvenience. Cheers, Marc

1 0

NTP
by Marc Wiriadisastra 23 Jan '08

23 Jan '08

Hey all, http://fedoraproject.org/wiki/Docs/Drafts/AdministrationGuide/Servers/NTP Just added content I tried to match the layout and other details to the webserver guide which is edit ready. Would love some feedback. Cheers, Marc

2 1

meeting reminder 2100 UTC today
by Karsten Wade 22 Jan '08

22 Jan '08

Reminder that we are having our first meeting of the new year and first meeting of the new FDSCo. #fedora-meeting 2100 UTC 22 Jan http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings#Agenda -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

2 1

Getting Involved Guide
by Paul W. Frields 22 Jan '08

22 Jan '08

Docs Project colleagues, The following thoughts come out of the sessions we had at FUDCon about doing a better job involving new contributors in Fedora. I'm going to start out with the summary, so if you don't want to read all of this you can skip it and immediately make comments. Those of you who want a larger picture can read more after the summary. Please keep in mind that I am not yet paid by Red Hat, and this message comes from me as a fellow contributor, and not the FPL. As always, it will be up to each of us to evaluate what effort we want to give to Fedora, and where we put it. I hope the following will give you some inspiration about Fedora's future.... * * * * * THE PUNCHLINE: For its size, the Docs Project has done great things thanks to the energy and generosity of its members. But in the post-F9 era, we need to get off the treadmill of simple user/admin documentation, which is duplicated many times over in both the free and for-pay spheres, and move to goals that are more contributor-oriented. * * * * * THE LONG VERSION: Originally I suggested a "Developer Guide Reboot" session and hackfest, a document that would support entry of developers into the project. It would give a tour of some important packages and online resources so they wouldn't have to navigate a metric boatload of wiki pages to get started. Over time, though, it became clear that this wasn't just an issue about developers, but about contributors of all flavors. Part of our "lowering barriers" mission has to be about encouraging and educating people who aren't doing just coding jobs, but website/infrastructure folks, artists, documentation writers, coding and non-coding packagers, ambassadors, and just plain friends. Historically, the Docs Project has concerned itself mainly with helpful user/administrator level guides, but by focusing on the trees, we may be missing the mark on the forest, so to speak. There are a huge number of existing guides and tutorials on the web -- not all of them authoritative -- and a full selection of dead-tree books to be had at any bookstore. Is it really worth our time to be competing on that level? I say this not to call into question the excellent work that's being done by contributors, but to get people thinking about the post-F9 Docs Project, and where we should be focusing our sights. If Fedora does not grow and extend its contributor base, it will wither over time. We cannot demand that the same people do the same work in Fedora for extended periods; people change and grow, and naturally move on to other Fedora tasks, the same way they move on to other jobs, homes, or ways of thinking. Instead, we should focus on bringing new entities into the project and giving them the resources they need to contribute to the project. Note that I say "entities" and not "people," because Fedora also stands to gain if we bring in additional commercial or other non-individual contributors who themselves gain from a contributory partnership in Fedora. Fedora needs to grow also beyond just its partnership with and sponsorship by Red Hat. By doing that, we secure the health of the project in a more sustainable way. The idea of the Developer Guide for these reasons was transformed during our working sessions at FUDCon into a "Get Involved Guide" (GIG). This sort of documentation allows us to escape the treadmill of trying to update countless pages of advice on how to perform end-user tasks that do not necessarily help people contribute to Fedora (and thus help it grow and thrive). Michael Tiemann stated in his speech at FUDCon that the future of IT commerce is in "the communities that [companies] build." If we want to position Fedora at the forefront of open source in the 21st century, we must think larger than simply showing people how to run Fedora -- we need to show people how they can *get involved*, not just in Fedora documentation, or packaging, or feature development, but in the many fields of endeavor this project covers. I would also make the point that what you read above is not the end of the whole Fedora vision, but just a facet of a larger idea which I am still fleshing out with other Fedora leaders. As always, we will be talking about this much more in the future with as much openness and transparency as possible, to encourage community input, awareness, and enthusiasm. * * * * * As you all know, I am not one for long, rambling emails when I can avoid them. They try my patience too! But nevertheless, there are many positive messages in the above ideas. I have a huge amount of respect for the work everyone is doing, and I hope you will not find the above to be a criticism, but rather a "leap-ahead" vision for where we should set our sights for goals after Fedora 9. "DOCS ROCKS!" -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

4 6

Docs on Transifex
by Diego Búrigo Zacarão 22 Jan '08

22 Jan '08

Hi, All! I have noted that we have just a doc module (Install Guide) on transifex to be commited translations[1]. It's the time to use more intensely our new web tool to commit translations and I would like to ask to include other essential docs modules there: docs-common release-notes homepage about-fedora readme readme-burning-isos readme-live-image If any help is need to do it, please tell me. [1] https://translate.fedoraproject.org/submit/module/ Regards -- Diego Búrigo Zacarão Linux User #402589 USE SOFTWARE LIVRE

1 0

Re: Xmlto-0.0.20 with experimental fop support
by Karsten Wade 22 Jan '08

22 Jan '08

On Mon, 2008-01-21 at 15:51 +0100, Ondřej Vašík wrote: > Hello, > as requested in RHBugzilla #147472 , comment #6 by Karsten Wade, I'd > like to inform you that xmlto with fop support is available > in rawhide branch. > I did a few tests with fop, seems to work properly (only sometimes I had > some troubles with special characters but maybe caused by my not 100% > perfect configuration of fop). Karsten said that it would be good to > test it by Fedora Docs toolchain, so I would appreciate any feedback to > improve fop support or to fix some possible issues. Thanks. I'll work on getting a rawhide install going to do the testing. Anyone else interested and capable? - Karsten -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

1 0

Centralised Docs
by Marc Wiriadisastra 21 Jan '08

21 Jan '08

Can we sort out or generate a list of documents that are available on the wiki that are available. I bring this up because there seems to be docs all over the place and a lot of information is located on the wiki but isn't referenced except from other docs. Cheers, Marc

2 1

mitwi on track again
by ria das 20 Jan '08

20 Jan '08

Hi all, My project mitwi which deals with "Publication of all man and info pages for each release through a web interface" is back on track again. Presently it is hosted under dgplug site. http://mitwi.dgplug.org When you click on the above-stated site you will get an option to change the language in which you want to view the pages. You can select the language according to your choice and then you will have to click on 'change language'. Your language is change now. Now you can select any one of the releases. Presently only F7 release is available. So you will have to select Fedora 7. You have to then select one of the page types. Presently info pages are not available, so you will have to select man. Then on clicking on 'show commands' it will show you the names of commands an an alphabetical order. You can click on any of the commands to view it's man page. You also have a search option where you can search a particular command. On searching a command it's name, page type and release will be shown. You can click on the command name to view it's page. If you want direct link to any man page you can use links like http://mitwi.dgplug.org/man/man1/ls.1.html You can get this direct link in any man page opened in miwi which is at the top of the page. There are lot of bugs which I am fixing slowly. regards Ria

1 0

Introduction
by Clint Savage 20 Jan '08

20 Jan '08

As is customary, I'm introducing myself to the fedora documentation project. I've been a member of the Fedora Project for about 6-8 months IIRC and have been participating mostly in an Ambassadors role. However, as I get a little more involved, I'd like to participate in further projects and the docs is one where I feel I could help immensely. This weekend, I attended my first FUDCon and met several people, of which a few (Paul Frields, Jared Smith) are on the docs project as well. I find that I could probably help here as I'm regularly asked to document things for my work regarding Fedora specific features and thus could help the Fedora project to improve its documentation as well in these areas (and others as I can). I am a linux instructor (Guru is the title we get when we're hired) at a small company in Utah called Guru Labs. We provide training for Red Hat and other companies throughout the world. Its quite a fun job, and I get to see much of the country (and sometimes world). I am a resident of Utah, which is Mountain Time, though I travel quite a bit to the East Coast of the US. I usually try to stay on mountain time, however so I can do that translation in my head (or because my computer is always on that time). Here's my gpg info: gpg --fingerprint 62A2258E pub 1024D/62A2258E 2006-07-09 Key fingerprint = 8C10 443D 7F49 A694 018C A2DD 7D27 D8A2 62A2 258E uid Clint Savage (It's Guru Time) <clints(a)gurulabs.com> uid Clint Savage <clint(a)herlo.org> uid Clint Savage <herlo1(a)gmail.com> uid Clint Savage (Utah Open Source) <clint(a)utos.org> sub 2048g/5F818B03 2006-07-09 Hopefully, I can contribute where needed and look forward to working with you all. I'm currently working on learning docbook and should be more comfortable in the near future. Cheers, Clint

3 3

Please update Spanish Fedora Documentation and create central spanish forums!
by Marcelo Martínez 19 Jan '08

19 Jan '08

Hello, I'm Marcelo from Uruguay. The spanish Fedora users needs Updated spanish documentation. The documentation in spanish is out of date, and we need easy access to the documentation. When I visit fedoraproject.org the web is in spanish, (great!!) but when i navigate others web sections see are in "English", for example http://docs.fedoraproject.org/ (and every subsections there, including docs, of course) I think Red Hat is a worldwide linux leader and must give more resources to fedora, the documentation is very important and in fedora is poor. My English is basic and not good to make spanish translations of the documentation, but Red Hat can paid traductors. Another reclaim is about the forums... There is not central spanish forums for fedora, I think fedoraforums.org must create a "spanish section" or create a new forum for centralize all spanish questions and projects, like ubuntuforums loco teams subforums. Best Regars, Marcelo Martínez.- Sorry if you don't understand my bad English but I speak Spanish.-

3 2

remaining observations on "Managing Software with yum"
by Robert P. J. Day 19 Jan '08

19 Jan '08

section 7: once again, there is no "Extras" repo since F7, right? section 7.1: i think it would be worth mentioning how you can just "yum install" 3rd-party repo files as well, rather than manual copying then. (and wouldn't that also automatically add the public key to your key ring as well?) section 7.3: another reference to "Extras", but it might be useful to have a real-life example of repo compatibility issues -- for instance, livna versus freshrpms or something like that. and it would be *really* useful to explain the "--enablerepo" option, i would think. perhaps in section 7.4. section 9.2: "Fedora Core includes the installonlyn plugin. This plugin modifies yum to remove excess kernel packages, so that no more than a set number of kernels exist on the system. By default, installonlyn retains the two most current kernels, and automatically removes older kernel packages." - but that's not a plugin anymore, is it? there's certainly nothing by that name in /usr/lib/yum-plugins. isn't that feature now handled by "installonly_limit" in /etc/yum.conf, or something like that? section 9 or 10: i think it would be useful to introduce the yum-downloadonly plugin. i think that would fit nicely right around here. and i think i'm done here. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================

5 8

meetin' times for FDSCo
by Karsten Wade 18 Jan '08

18 Jan '08

We almost seem to have a consensus on a good time for FDSCo to meet. Hoping John and Jared can make the time ... So, let's meet next: Tuesday 22 January 2100 UTC #fedora-meeting We shouldn't consider it permanent until: i. John and Jared get a chance to weigh in on the time matrix[1] ii. Paul starts his new job and gets a chance to re-think his "free time" concept http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/MeetingTimeMatr… -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

3 2

Re: Fedora 9
by Davidson Paulo 18 Jan '08

18 Jan '08

2008/1/18, Rahul Sundaram <sundaram(a)fedoraproject.org>: > There was a open call in fedora-devel list and all of the names were > suggested from people in the community and need to pass through legal > review which has already been done. The names won't be changed now. So sugestions are made on fedora-devel... Good to know this. :-) We need to make more and better sugestions, because if that list contains only the better names among all those suggested, I don't want to imagine the names that were not been approved... I heard that the fisrt Fedora codenames were all alchool-related. Zod is a fiction character. Moonshine is a home-distilled alchool made specially in places where this production is illegal. Werewolf is a legendary monster. We really want to associate Fedora with alchool? Fedora is not made by drunks, I'm sure. Developers may drink, but they don't produce any code or work under effect of alchool, I'm sure (and, if yes, I think is better if Fedora users don't know that). And what about monsters? Has someone here ever seen a werewolf, a chupacabra, or Zod? Fedora is real, and its codename need to be something undoubtedly real. Finally, I can't figure out how 3 diseases names could be accepted as options. What type of marketing could we do with names like those, "Fedora 9: Sick, like you"? Why I'm saying this? Because we have a list with codenames that vary from bad to worst and we are responsible for this because we don't suggested better codenames. We need to participate this process before we start do have Fedora Dracula, Malt or Ebola... By now, let's choose a codename that is not so bad. Best regards, Davidson Paulo http://fedoraproject.org/wiki/DavidsonPaulo

1 0

[Fwd: [Bug 147472] Adding FOP support]
by Karsten Wade 17 Jan '08

17 Jan '08

xmlto in rawhide supports FOP. w00t! -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

3 2

DUG + AG release planning
by Vladimir Kosovac 16 Jan '08

16 Jan '08

To better prepare for the irc meetup this weekend, I've put together a brief list of observations/food for thought[1] related to the current status of AG draft. So far, these people have confirmed participation: - Bart (couf) - Marc (mwiriadi/strikeforce) - John (jmbuser) - Vladimir (vnk_fd) $date: Saturday, 19th Jan. 14:00 (2 PM) UTC It'd be good to assess current state of DUG release readiness, too and try to assign some timed tasks to writers/editors/xml converters, etc. [1] == Sections == Introduction ------------ New, shinny intro required for release, existing intro is A draft doc related, no change required DirectoryStructure ------------------ Shoud this be part of the AG? UserAccounts ------------ Edit-ready Permissions ----------- Edit-ready AccessControlLists ------------------ XML conversion-ready ManagingStorage --------------- currently writing (vnk); may split into LVM only for F9 release and keep the whole ToC here Disks[RemovableStorage] ----------------------- This stuff is mostly automatic these days - remove from AG? ManagingSoftware ---------------- Edit-ready ManagingServices ---------------- Edit-ready ModifyingStartup ---------------- Not sure how beneficial would this be for the AG; (too many too specific kernel parameters don't seem to have a place in a general doc) MailServer ---------- Sendmail needs just a bit of nursing; as with LVM, we may split sendmail part into F9 release; add dovecot config so receiving is covered; WebServer --------- some content available; needs editing and probably not much more content, if any; FTPServer --------- anon ftp part is OK; will add few common options from vsftpd.conf to cover authenticated ftp; NetworkFileSystem ----------------- Edit-ready SambaServer ----------- Edit-ready DNSBIND ------- probably needs a bit of trimming; bind-chroot is default; should cover named.conf for various server roles and a few zone/rev file examples, not much more; Firewall -------- I don't want to handle this one! CupsPrinting ------------ existing page is inapropriate for AG; in need of complete overhaul; ModifyingXwindow ---------------- don't think this should be part of the AG; MonitoringSystem ---------------- requirements on the AG front page are over the top; should cover basic stuff (ps, top, df, du, logs/logrotate, free); SchedulingTasks --------------- Edit-ready ======================================================= Possibly include: Squid ----- NTP --- ======================================================= Anything else? Vladimir

1 0

Fedora 9
by Marc Wiriadisastra 15 Jan '08

15 Jan '08

Are we going to release information as to what our targets are for a feature of admin guide and desktop guide? http://fedoraproject.org/wiki/Releases/9/Schedule I'm personally hopeful at us having the DuG ready for F9 should we start pushing it or should we wait? Cheers, Marc

4 7

Bug #306221
by Paul W. Frields 14 Jan '08

14 Jan '08

OK, this bug has been dormant too long. Does someone have a good solution for this that isn't hacky and ugly? I guess in retrospect it would have been nice to have our rpm-info DTD include a "locale" attribute for "translator" elements, so we could extract the desired credit using the existing packaging/bookinfo.xsl in the docs-common/ module. Any suggestions appreciated -- please put them in the bug: https://bugzilla.redhat.com/306221 -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

whoops, forgot this one
by Robert P. J. Day 14 Jan '08

14 Jan '08

sorry, this should have been at the end of that previous list: http://docs.fedoraproject.org/yum/en/sn-updating-your-system.html su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start' i'm pretty sure the service name should be "yum-updatesd" these days, no? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================

1 0

observations on "Managing Software with yum"
by Robert P. J. Day 14 Jan '08

14 Jan '08

might as well collect my observations on http://docs.fedoraproject.org/yum/en/index.html section 1.3: might mention that "tsclient" can also be invoked just from the command line, not only from the menus section 2.2: "To view a list of all of the available package groups for your Fedora system, run the command su -c 'yum grouplist'. " - i don't believe just getting a yum grouplist requires root access, and i'd avoid typing "su -c" where it's technically not required. section 4.1: if you're going to mention "yum groupinstall", it might be useful to also mention "yum groupinfo", unless you cover that later. (i notice you do cover "yum groupupdate" and "yum groupremove" just a bit farther down the page.) section 5.1: again, i would avoid prefixing commands with "su -c" that don't require it. i also don't see any mention of "yum info" on that page, which i find handy, particularly with wildcard patterns. section 5.2: the example of "yum provides libneon" might emphasize that that search covers only installed packages, no? more later, possibly. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================

1 0

erroneous reference to fedora "extras"??
by Robert P. J. Day 14 Jan '08

14 Jan '08

on: http://docs.fedoraproject.org/yum/en/sn-software-management-concepts.html IIRC, that repo disappeared as of F7, no? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ========================================================================

1 0

FDSCo results
by Karsten Wade 13 Jan '08

13 Jan '08

With a slight delay for the holidays to get the results :), the following persons will be staying or joining the Fedora Documentation Steering Committee (FDSCo): Bart Couvreur John Babich Jared Smith Congratulations to those chosen. All candidates are doing great work in Fedora Docs, and by virtue of that are already leaders within the project. When we next have a round of formal elections, I hope you all consider running again. We'll have our first FDSCo meeting after the new year. Members - let's work out a meeting time. To start, we need to refresh our matrix: http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/MeetingTimeMatr… You can refer to the old one[1] for what you put in last time. Our goal is to pick a meeting time or two; we can alternate between then, if that works. Another option is to have two meetings a month and do more preparation and work in them. Open for discussion! Thanks - Karsten [1] http://fedoraproject.org/wiki/BobJensen/MeetingTimes -- Karsten Wade, Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41

5 5

Delineation: document vs application
by George (Skip) VerDuin 13 Jan '08

13 Jan '08

I have run into an issue needing an assignment to the most appropriate group for resolution -- it may be an application or documentation issue. As a matter of background, I've been following this reflector for many months but have not submitted a formal self intro... I'm sorry that I don't already know the answer to my question. Specific to the task of hooking up klamav to evolution while in the KDE desktop environment [to filter out virus laden incoming mail] I ran into an ambiguity that hinders my administrative work. The reference document I used is provided as a text window by klamav that is specific to this task. My resultant setup in evolution leaves me wondering if I have correctly set up the interface and quite frankly I suspect I have done it wrong... I am reserving the detail of the issue, it is in the form of two screen shots plus my narrative. Rather than resolving the problem here on the reflector, I am asking whether this qualifies as a bug for the application or if this fits within the documentation domain. After watching this reflector, I am not clear which team on-line pop-up window material falls into. I would be pleased to collaborate with the author of the window text to remove the ambiguity no matter which group takes the lead. Warmest regards from here, thanks up front for your consideration. George

2 2

RE: Request for Review: Using FireGPG
by Eric Christensen 10 Jan '08

10 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I submitted this document for review on 03 Jan 2008. Thanks to the help of couf and mwiriadi on IRC this morning I was able to structure the document a bit better and feel it is ready for the main stream. Please look over the document and see if everything flows. I'd also like for someone to try the steps and validate the procedure. This page should be linked from http://fedoraproject.org/wiki/DocsProject/UsingGpg which hopefully will put my document into better context. Thanks, Eric >http://fedoraproject.org/wiki/Docs/Drafts/WithFireGPG > >I started this page yesterday before finding all the information on joining >the documentation team and how to PROPERLY submit a work. Sorry... > >I have started a page with instructions on installing and setting up FireGPG >which is a Firefox extension that allows users to sign and encrypt e-mail >messages when using a webmail client. It was actually specifically designed >to integrate with Gmail but also works with other webmail products (really any >time you need to sign and/or encrypt text you can use the extension). > >I haven't added the information for using it with webmail clients other than >Gmail but what is there should be correct. I'd appreciate someone verifying >the information. > >Thanks, >Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: http://firegpg.tuxfamily.org iD8DBQFHhjl0L5V8yddJCO0RAt5ZAJ0WmRGpNtk+DHvHZB5KgYmMMWnvzQCeNPlr tuANIgm8qOO/biF7kvnNTbA= =0NWu -----END PGP SIGNATURE-----

1 0

DUG
by dan＠new2linux.com 10 Jan '08

10 Jan '08

Hello all, It's been a busy couple weeks and I haven't had much time to get much work done on the DUG. I'm going on a business trip for a couple days and had planned on spending the weekend catching up on the DUG. IIRC there was talk of having the DUG complete by sometime next week? What needs to be done? Regards, Dan O'Brien

10 59

nfs section /etc/sysconfig/nfs
by Murray McAllister 09 Jan '08

09 Jan '08

Hi, I was taking a look at the NFS section, and found at the start "Firewall rules are configured to allow for the proper port access". The section is marked edit ready, which is why I'm asking before doing, but would it be worthwhile documenting /etc/sysconfig/nfs? Otherwise it is hard to configure firewall rules since portmap assigns ports dynamically. I have recently done the content for work, so it wouldn't be hard to add some of the details into the wiki... Thanks, Murray. ------------------------------------------------------------------------------------------------ pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18] Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com> sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]

1 0

Re: SELinux in guides [was: Self-Introduction: Eric Christensen]
by Murray McAllister 08 Jan '08

08 Jan '08

On Jan 5, 2008 3:39 AM, Karsten Wade <kwade(a)redhat.com> wrote: > On Thu, 2008-01-03 at 17:01 -0500, Eric Christensen wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Eric H. Christensen > > Newport News, VA USA > > Information Assurance Analyst > > Honeywell Technology Solutions Inc > > Welcome Eric. > > Let us know (via this list) if you run into any issues with getting > signed up for accounts or figuring out what to do or where to go. > > The carpenter's roof is leaking a bit, but we're working on it. :) > > > * Your goals in the Fedora Project > > o What do you want to write about? Security mostly but I'll write > > about anything because it helps me learn! > > That is very true. You should have seen my security knowledge when I > started tracking SELinux development as a tech writer. :) > > If you are interested, I think our in-progress Fedora Administration > Guide (AG) could use a fresh look at these two areas: > > * Big view -- make sure that overall the document is consistent and > promotes good security practices that use Fedora-packaged solutions. > > * Focused view -- what is missing? Can we merge the SELinux content > into the AG? What about all those blog posts from Dan Walsh? What > other security content can we cover? Hi, I am trying to fix the dns section I wrote so it reflects using an RPM instead of a tarball. I have only gotten around to one little section regarding selinux, but I am going to include how to set the correct context for each file/folder created. I think it would be good to merge selinux into each section (if applicable), considering it is shipped and enabled by default, instead of making people look all over the place. Regards, Murray. ------------------------------------------------------------------------------------------------------------------ pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18] Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com> sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]

7 18

KDE critique (DUG)
by Marc Wiriadisastra 08 Jan '08

08 Jan '08

Hey All, I had a quick chat to Rex about the DUG and he's going to post to the KDE SIG to see if someone is willing to work with us to make sure the KDE parts are all correct. Since with F-9 XFCE will actually be a spin we will need to consider the default XFCE settings etc. Can someone email whoever takes care of the package or if there is a SIG the SIG so we can liase with them. I'm hoping to make the DUG more inclusive so users won't have to try and figure out whats going on. [offtopic] The selinux guide I will work on but my main priority right now is the DUG unless someone wants to finish it off reasonably quick so I can start work on the selinux guide. :) [/offtopic] Cheers, Marc P.S. Dan I also said they could contact you if needed. If I receive anything I'll forward it to the mailing list. I did advise them to try and mail to the mailing list and use us as a backup option. (probably the wrong thing to do)

3 4

Selinux guide
by Marc Wiriadisastra 07 Jan '08

07 Jan '08

Hey All, It seems like someone was eager awhile ago http://fedoraproject.org/wiki/Docs/Drafts/SELinux has been put up already. Should we use that link or change it to SELinuxGuide? I'm going to start creating the pages over the next week or so. I would like some input from everyone as to what to add. Cheers, Marc

3 6

FAQ = F7
by Marc Wiriadisastra 06 Jan '08

06 Jan '08

Hey all, Do we have a new FAQ the current one linked to http://docs.fedoraproject.org/ points to the Fedora 7 FAQ? Cheers, Marc

2 2

Self Introduction
by Karl Larsen 06 Jan '08

06 Jan '08

I have done the things needed to get a CLA in that part of the Doc works. I just verified it works. I now need permission to edit a wiki and the rules say that a member of that group has to add me to the list. My wiki name is KarlLarsen and my email address is k5di(a)zianet.com Karl -- Karl F. Larsen, AKA K5DI Linux User #450462 http://counter.li.org. PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7

2 2

Meeting times
by Paul W. Frields 06 Jan '08

06 Jan '08

OK, we have a few people left to fill out the meeting time matrix: John Babich Bob Jensen Jared Smith http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/MeetingTimeMatr… Please go to that page and indicate in the chart where you *can* attend a meeting, so we can get off the ground the first available time after FUDCon. I know some of us will be there, and we should certainly make sure any of the new folks who haven't met get acquainted. Thanks guys! -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

Re: Self-Introduction: Kazuo Ishii
by Kazuo Ishii 06 Jan '08

06 Jan '08

Paul; Thank you for your quick reply. I will make progress step-by-step in Japanese translation. And I hope the improvement of Fedora Japanese environment. Kazuo Ishii, Ph.D. The Linux Users #411141 GPG Key fingerprint = D064 929C C6B6 D1C4 CD66 152B 5320 B0E6 3E15 9E3F 日本Rubyの会 freeparis2(a)gmail.com http://officeparis.org/blog/

1 0

The Brennan Home Server HOWTO
by Timothy Murphy 05 Jan '08

05 Jan '08

Miles Brennan said: -------------------------------------------------------------- Although the document was written to suit Fedora Core, I tried to maintain generic configuration and commands where possible so other distros could also benefit from it. Also stayed away from the GUIs. Converting the plain HTML version of the document to wiki format was much more painful than first anticipated. I wanted to keep the feel of the original HOWTO styled document, as I believe they are much easier to read and follow than the current wiki construct. However the wiki code does not easily support the formatting of tables, cells, preformatted text and other basis formatting. Working in RAW wiki code was very time consuming. Here is the draft of the HOWTO I worked on: http://fedoraproject.org/wiki/Docs/Drafts/ServerInstallationGuide I installed moinmoin on my own server to work on the formatting issues a little easier and found I needed to make some significant changes to the CSS for the document to look and feel the way I wanted it to. It was also mentioned at the time that FDP would be moving to a Plone and Zope based system, making these type of migrations easier. Although I had no experience with these two applications, I was happy to try something new. I eventually gave up on transferring the documentation because the new system has not been implemented and I found the wiki frustrating. If FDP is still willing to accept the documentation, I am happy to change the licensing and Tim is prepared to start some work on it. Perhaps we start a new thread on updating the HOWTO and moving it into the FDP. Open to suggestions. -------------------------------------------------------------- I'm not quite sure if I am the Tim referred to here, but if I am then I would be happy to try my hand at bringing the HOWTO into the Fedora Documentation Project. On the content side, there are a couple of points that I wondered about: 1. You talk a little about PPPoE in chapter 5. Is this still necessary? I had the impression that all *DSL modems now do this for you, and basically give an Ethernet connection to the Internet? 2. Does one have to understand IPtables any more (chapter 6)? I use shorewall, which seems to me to make this bit of life much easier. Am I right in thinking shorewall is more or less the default Fedora firewall nowadays? 3. Do people still use FTP (chapter 14)? 4. I wonder if a chapter on SVN might be worth while? But these are probably better discussed off the list, if indeed I am given the task of trying to bring your HOWTO (and it would remain your HOWTO) into the FDP? Tim

5 12

Editquew like problems
by Karl Larsen 05 Jan '08

05 Jan '08

I want permission to edit a wiki page. I tried to join a group waiting for this and the web page is broken. Or seems to be to me. So I will just wait until something happens I guess. No chance to write other wise. I even have a place on the wiki. I can't edit it :-) Karl -- Karl F. Larsen, AKA K5DI Linux User #450462 http://counter.li.org. PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7

1 0

Self-Introduction: Kazuo Ishii
by Kazuo Ishii 05 Jan '08

05 Jan '08

Hello, My name is Kazuo Ishii. I am working in the unuv. for research in pharmacy and I am a bioinformatics scientist for statistics computing using R/S-PLUS in Linux OS. I am maintaining some official and private websites about datamining, which are described in Japanese, English and French. Privé http://freeparis2.blogspot.com/ R/S-PLUS http://officeparis.org/blog/ IPEJ-BIO http://officeparis.org/bioxoops/ IPEJ-IEC http://officeparis.org/hiki/ tDiary http://officeparis.org/tdiary/ My real speciality is biotechnology, bioinformatics, computational statistics and molecular biology. I also use another internet name Pierre I. Katz, which is translated to French from Japanese, because I have working experience in Paris for about three years. I would like to maintain Japanese environment of Linux for the basis of my business, bioinformatics. My personal data is shown below; * Full legal Kazuo Ishii, Ph.D. * City, Country; Noda, Chiba, Japan * Profession; Reasearch Scientist (Bioinformatics Specialist) * School; Tokyo Univ. of Sci. * Your goals in the Fedora Project; Fedora translation in Japanese * Historical qualifications o What other projects have you worked on in the past? Debian JP Project develnews translation o What level and type of computer skills do you have? Bioinformatics scientist specializing data mining using R, S-PLUS and Perl. o What other skills do you have that might be applicable? Statistics computing and datamining using R, and S-PLUS Programming using Perl, Ruby, Python and Java. Web site construction; LAMP, XOOPS, Wiki, Blog and Ruby on Rails Language; Japanese, English, French and Germany o What makes you an excellent match for the project? Translation in Japanese * GPG KEYID and fingerprint [kazuo@freeparis2 ~]$ gpg --fingerprint 3E159E3F pub 1024D/3E159E3F 2008-01-05 Key fingerprint = D064 929C C6B6 D1C4 CD66 152B 5320 B0E6 3E15 9E3F uid Kazuo Ishii (Fodora) < freeparis2(a)gmail.com> sub 2048g/3853ECD4 2008-01-05 -- 石井一夫日本Rubyの会 freeparis2(a)gmail.com http://officeparis.org/blog/

2 1

Overview rewrite
by Rahul Sundaram 04 Jan '08

04 Jan '08

Hi, Finally did a quick rewrite of the overview page that I have been wanting to do for a while now. Appreciate a review and additional content. http://fedoraproject.org/wiki/Overview Rahul

4 6

Self-Introduction: Eric Christensen
by Eric Christensen 04 Jan '08

04 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric H. Christensen Newport News, VA USA Information Assurance Analyst Honeywell Technology Solutions Inc * Your goals in the Fedora Project o What do you want to write about? Security mostly but I'll write about anything because it helps me learn! o What other documentation do you want to see published? Not sure what else needs to be published but I'm open to ideas. o Anything else you'd like to do? I'm open to suggestions. * Historical qualifications o What other projects or writing have you worked on in the past? I do a lot of web work and work on documenting networks. o What level and type of computer skills do you have? I'm just getting out of the noob status in Linux and am trying hard to get the skills I need to becoming a Linux (read that Fedora & Red Hat) administrator/guru. I've been working with computer for the last 18 years, mostly in the Windows world. o What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. I have to interface with people all the time so I'm usually pretty good at that. I'm not a programmer but am an excellent networking engineer and security auditor. I know how to explain security to people that aren't in security. o What makes you an excellent match for the project? I have a certain attention to detail that helps me go back to a document or webpage that I've published and refine it to help make it clearer. * GPG KEYID and fingerprint D74908ED 2007-12-31 [expires: 2008-12-30] Key fingerprint = 4395 EF8D DDFF E681 26CB 7165 2F95 7CC9 D749 08ED -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHfVtHL5V8yddJCO0RAlGFAJ0e1D5CuC0QwKFb234T9qhDkfChNwCdERkj 8NjMFCybJ8GxgmN/TZZ3jSw= =TOY8 -----END PGP SIGNATURE-----

2 2

jEdit
by Karl Larsen 04 Jan '08

04 Jan '08

I got jEdit working in a terminal but it doesn't work. If I use $ jedit file1 it comes up and a panel that does nothing comes up in the way. I tried to make a file and have tried Control-s to save it and it does not work. The instructions seem not to be for a Linux Terminal. Does anyone here know how to use jEdit? Karl -- Karl F. Larsen, AKA K5DI Linux User #450462 http://counter.li.org. PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7

8 28

text editor documentation for docbook
by Murray McAllister 04 Jan '08

04 Jan '08

Hi, I have, very slowly, been working internally on a few small documents for Kate and jEdit, concentrating on the features to make it easy to use/work with XML (plug-ins, extra packages etc). Paul suggested I could host this somewhere and let everyone else add to it. Does anyone know if it is possible to set up, say, svn in fedorapeople? For example, set up a directory in my home directory on fedorapeople and run svn from there? Or is there a place on the wiki I could post this? I have finished Kate, just not jEdit...nothing is private, so I don't see the problem in copying it all straight into somewhere public. I am not an expert with Kate or jEdit so it would be great to see what other people know. Thanks for your help. Regards, Murray. ------------------------------------------------------------------------------------------------------------------- pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18] Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com> sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]

2 1

Request for Review: Using FireGPG
by Eric Christensen 03 Jan '08

03 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://fedoraproject.org/wiki/Docs/Drafts/WithFireGPG I started this page yesterday before finding all the information on joining the documentation team and how to PROPERLY submit a work. Sorry... I have started a page with instructions on installing and setting up FireGPG which is a Firefox extension that allows users to sign and encrypt e-mail messages when using a webmail client. It was actually specifically designed to integrate with Gmail but also works with other webmail products (really any time you need to sign and/or encrypt text you can use the extension). I haven't added the information for using it with webmail clients other than Gmail but what is there should be correct. I'd appreciate someone verifying the information. Thanks, Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: http://firegpg.tuxfamily.org iD8DBQFHfZVML5V8yddJCO0RAgWEAJ9q6chMYqZ3UZLP18R7B/ZjfuRN8QCffy2C kG3w/COnc6Cc3fhhHdwxCQk= =Eezi -----END PGP SIGNATURE-----

1 0

[Fwd: Re: GPG Keysigning at FUDCon]
by John Poelstra 03 Jan '08

03 Jan '08

Would it make sense to change our docs to refer to subkeys.pgp.net instead of MIT? John -------- Original Message -------- Subject: Re: GPG Keysigning at FUDCon Date: Thu, 3 Jan 2008 13:43:54 -0500 From: Todd Zullinger <tmz(a)pobox.com> Reply-To: Development discussions related to Fedora <fedora-devel-list(a)redhat.com> To: fedora-devel-list(a)redhat.com References: <20071212214010.GA20896(a)auslistsprd01.us.dell.com> <477C3AA7.9010700(a)redhat.com> <1199353983.13378.1.camel(a)rousalka.dyndns.org> <477D1646.6080207(a)redhat.com> John Poelstra wrote: > I looked into it more and changed the expiration by: > > 1) gpg --edit <key> and then option "expire" > 2) gpg --keyserver pgp.mit.edu --send-keys <key> to make change > public FWIW, you may want to send that to subkeys.pgp.net, which is where Matt plans to pull the keys from for the key signing. This is the default keyserver in recent gnupg releases. I think that there is a sync between pgp.mit.edu and subkeys.pgp.net, but I'm not positive. The gnupg default is subkeys.pgp.net because pgp.mit.edu runs ancient keyserver software that has many known problems (it ignores photo packets, can munge up multiple subkeys, and other annoyances). -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I do nothing, granted. But I see the hours pass - which is better than trying to fill them. -- E. M. Cioran -- fedora-devel-list mailing list fedora-devel-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list

3 2

copying+pasting screen examples
by Murray McAllister 01 Jan '08

01 Jan '08

Hi, I am trying to re-do the DNS section for use with RPMs instead of tarball. I have just noticed that I can't correctly copy and paste the examples I have done using {{{ }}}. I assume these will be converted to <screen> tags eventually, maybe the problem will go away then. For example, copying the /etc/named.conf options section from https://fedoraproject.org/wiki/Docs/Drafts/AdministrationGuide/Servers/DNSB… appears as the following in vim: options { directory "/etc/bind"; allow--query {any;}; recursion no; pid--file "/var/run/named/named.pid"; zone--statistics yes; statistics-f-ile "/etc/bind/namedstats.log"; }; There are double "-" characters, however these characters did not appear when I copied them from vim into here :( . These options will not be valid when double "-" characters are used. I'm not sure if this is a huge problem, but I thought it would be ncie if people could copy and paste these samples to get a basic working configuration before changing it to suit their needs. I was thinking of putting a warning to look out for this, but I thought it would look sloppy. Has anyone had this problem before? Kind Regards, Murray. -------------------------------------------------------------------------------------------------------------------- pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18] Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com> sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]

3 6

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 January 2008