From frankly3d at gmail.com Wed Jul 1 10:34:58 2009 From: frankly3d at gmail.com (Frank Murphy) Date: Wed, 01 Jul 2009 11:34:58 +0100 Subject: OT probably: Fedora rpm guides to beBook? Message-ID: <4A4B3BD2.3050206@gmail.com> Can someone give me the best way, to get the guides http://fedoraproject.org/wiki/PackageMaintainers/CreatingPackageHowTo https://fedoraproject.org/wiki/Packaging/Guidelines https://fedoraproject.org/wiki/Packaging:Java https://fedoraproject.org/wiki/Package_Review_Process I need to an ebook reader. http://mybebook.com/ Frank -- jabber | msn | skype: frankly3d http://www.frankly3d.com http://fedoraproject.org/wiki/SIGs/Development From jim at dls.net Wed Jul 1 13:08:39 2009 From: jim at dls.net (Jim Thompson) Date: Wed, 01 Jul 2009 08:08:39 -0500 Subject: OT probably: Fedora rpm guides to beBook? In-Reply-To: <4A4B3BD2.3050206@gmail.com> References: <4A4B3BD2.3050206@gmail.com> Message-ID: <1246453719.4640.44.camel@localhost> On Wed, 2009-07-01 at 11:34 +0100, Frank Murphy wrote: > Can someone give me the best way, > to get the guides > > http://fedoraproject.org/wiki/PackageMaintainers/CreatingPackageHowTo > https://fedoraproject.org/wiki/Packaging/Guidelines > https://fedoraproject.org/wiki/Packaging:Java > https://fedoraproject.org/wiki/Package_Review_Process > > I need to an ebook reader. > > http://mybebook.com/ > Looks like your ebook reader supports .htm Save the pages you want as .htm from Firefox or your favorite web browser. Import into the reader. If there are pictures that you care about on any of these pages you may have to play around with placement of the image files and format of the tags to make your reader happy. Regards, jim From frankly3d at gmail.com Wed Jul 1 19:14:43 2009 From: frankly3d at gmail.com (Frank Murphy) Date: Wed, 01 Jul 2009 20:14:43 +0100 Subject: OT probably: Fedora rpm guides to beBook? In-Reply-To: <1246453719.4640.44.camel@localhost> References: <4A4B3BD2.3050206@gmail.com> <1246453719.4640.44.camel@localhost> Message-ID: <4A4BB5A3.8050500@gmail.com> On 01/07/09 14:08, Jim Thompson wrote: > > > Looks like your ebook reader supports .htm > > Save the pages you want as .htm from Firefox or your favorite web > browser. > Import into the reader. > > If there are pictures that you care about on any of these pages you may > have to play around with placement of the image files and format of the > tags to make your reader happy. > > Regards, > > jim > Thanks Jim. Frank From ian at ianweller.org Thu Jul 2 00:01:49 2009 From: ian at ianweller.org (Ian Weller) Date: Wed, 1 Jul 2009 19:01:49 -0500 Subject: Fedora Project documentation moving to CC BY-SA (fwd) Message-ID: <20090702000149.GH8872@deathray.ianweller.org> ----- Forwarded message from Mike Linksvayer ----- Date: Wed, 1 Jul 2009 15:05:03 -0700 From: Mike Linksvayer To: Ian Weller Cc: nathan at creativecommons.org Subject: Re: Fedora Project documentation moving to CC BY-SA Yes, would be glad to. Ping us when the relicensing is done and we can blog it. Or if you want a quote for a press release or something, can provide that too. Mike On Wed, Jul 1, 2009 at 9:03 AM, Ian Weller wrote: > (paulproteus on IRC sent me your way...) > > Hi, I'm on the Docs Team at the Fedora Project [1], and we're very close > to relicensing our documentation (and potentially our wiki) under the CC > BY-SA license (pending our legal team giving multiple nods). > > We were wondering if you could provide us with a little marketing buzz > on the subject. Let me know what we can work out. :) > > Thanks! > > -- > Ian Weller > GnuPG fingerprint: ?E51E 0517 7A92 70A2 4226 ?B050 87ED 7C97 EFA8 4A36 > -- http://support.creativecommons.org help us build http://creativecommons.org/asharedculture ----- End forwarded message ----- -- Ian Weller GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From eric at christensenplace.us Thu Jul 2 01:16:57 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 01 Jul 2009 21:16:57 -0400 Subject: Docs Meeting 2009-07-02 IRC log Message-ID: <1246497417.4454.8.camel@thunder> 00:00:44 #startmeeting 00:01:01 #maintopic Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting 00:01:39 Hmmm.... 00:01:45 #topic Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting 00:01:51 Roll Call!!! 00:01:54 * Sparks is here 00:01:59 * radsy is here 00:02:00 hi! 00:02:07 * jjmcd is here 00:02:12 annette! 00:02:16 * ianweller adds something to the agenda really fast 00:02:21 * poelcat here for ~ 30min (schedule worked out) 00:03:30 * ianweller is done adding things to the agenda 00:03:32 poelcat: Great, we'll get you in at the beginning 00:03:34 * quaid is here 00:03:39 ianweller: noted 00:03:48 Sparks: oh you were looking for #meetingtopic earlier instead of #maintopic 00:03:55 Sparks: or you can pass that as an argument to #startmeeting. 00:04:19 * Sparks moves some things around... 00:04:34 ianweller: That's what I was looking for... Gees... 00:04:35 TU 00:05:43 Okay... I've modified the agenda a bit... 00:06:04 #meetingtopic Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting 00:06:19 #topic F12 Calendar <-- poelcat 00:06:51 poelcat has been nice enough to create a calendar for us for the F12 release... 00:06:58 looking to see if there was any feedback on the schedules I proposed 00:07:02 and he sent it to everyone via the list. 00:07:13 Has everyone looked at it? 00:07:26 also curious if there was any interest in the ical/ics file? 00:07:28 * Sparks goes to get the links real quick. 00:07:38 poelcat: I like the ical... 00:07:47 someone have a link handy? 00:07:53 it's worth having anyway 00:07:57 Don't know enough about what we are going to do to know whether it makes sense or not 00:08:00 #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-tasks.html 00:08:12 #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-releng-tasks.html 00:08:20 #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs.ics 00:08:32 The first link is the docs tasks on a calendar... 00:08:46 the second link is the docs + releng tasks on a calendar... 00:08:57 and the third link is the docs ics 00:09:39 jjmcd: This is the master calendar for the F12 release. 00:09:52 Yes, but I have significant questions 00:09:59 jjmcd: go! 00:10:11 Now that alpha is a real alpha, for example, does the 1 page RN's make sense 00:10:37 Before alpha was a hoax, now it is feature complete 00:10:59 i took the previous "beta" tasks and relabled them "alpha" 00:11:21 That is probably not too bad an approximation 00:11:42 Especially since we probably don't really know how alpha and beta will turn out 00:11:56 the biggest things to consider are "is there enough time to do the tasks listed and do the order of events look right" 00:12:04 What Jesse things might not turne out 00:12:11 + based on what you learned in F11... have we factored that in 00:12:48 I think that is a good start 00:13:07 i can always change/adjust things 00:13:32 and most importantly as you notice things in F12 that don't work well that you want to change for F13... tell me as they happen 00:13:46 and i'll start factoring them into a draft for f13 00:14:13 * poelcat says f13 for one more channel highlight for jesse ;-) 00:14:35 Gees, are we already thinking f13? 00:14:46 well nobody else probably is, but I do :) 00:14:51 I mean, gees, we just got done with f11 and we are already thinking f13? 00:14:56 f13 00:14:57 always think ahead 00:15:01 f13... Wow... f13 00:15:02 :) 00:15:09 yeah, poor Jesse 00:15:22 his nick will light up for _years_ 00:15:32 another important thing to consider is handoffs between translation team and docs 00:15:49 and to verify if those look right 00:16:03 jjmcd: How long did it take the translators to finish the RN for f11? 00:16:17 several weeks - three i think 00:16:36 i created another special version for that: http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.html 00:16:37 and that's with making changes along the way, right? 00:16:47 yes 00:17:13 * Sparks would still like to figure out a better process so we aren't making so many changes 00:17:16 I think it ought to go better with propere warning 00:18:47 Yeah 00:18:57 so any more input to the calendar? 00:19:12 poelcat: Can you put our weekly meeting on the ics? 00:20:07 Sparks: i can definitely try... there are some things that make creating the ics not so straight forward 00:20:15 I can imagine. 00:20:20 Okay, anything else about this topic? 00:20:26 as just building the taskjuggler file, but it will either work or it won't 00:20:33 the challenge is landing it at the right time 00:20:38 i'll look into it 00:20:48 Thanks 00:21:05 what is the official meeting time in UTC ? 00:21:22 0001 UTC 00:21:31 and we go for an hour or so 00:21:34 got it.. that's all from me 00:21:39 Thanks! 00:21:41 Anyone else? 00:21:58 #topic Status on CC license discussion. <--quaid 00:22:06 * Sparks hears quaid has news 00:23:00 quaid: Ummm... quaid? 00:23:02 mebbe he didn't hear his que 00:23:05 ok 00:23:11 yeah, silent alarm or what 00:23:23 I don't have any more news than what was on list 00:23:31 i) we seem to have consensus 00:23:50 ii) but there is concern that people will feel overridden by the CLA directives being used 00:24:10 iii) I'm writing a blog post that gives all the Real and Great Reasons we need to enact the nuclear option in the CLA 00:24:32 once that is out there...maybe a thread'O'doom on f-devel-l is called for? 00:24:43 the point is, we need to alert people the change is imminent 00:24:50 maybe set a deadline for comments? 2 weeks? 00:24:56 and spread the word wide and noisy 00:24:57 wait 00:24:58 then do it 00:25:01 comments? questions? 00:25:08 Well... I'd like a quick vote... Does anyone have any problem with using the CLA to push the license change? 00:25:24 vote-- 00:25:25 +1 to changing the license using the nuclear option 00:25:31 we have a consensus on list 00:25:34 +1 00:25:52 if there are objections,we need to take them right back to the discussion, is all I'm saying. 00:25:56 quaid: Yeah, I just want to make sure no one here has any problems that we can work on now. 00:26:02 so even a single -1 == back to the list IMO 00:26:10 yes 00:26:30 did I sufficiently answer Sparks questions on list? 00:26:44 that was what made me realize I needed to do a wider post; reexplain from the top,etc. 00:26:47 what? 00:26:57 ianweller: your coffee is boiling over 00:27:23 ocrap 00:27:25 ;) 00:27:40 quaid: oh god a thread'O'doom?! 00:27:47 i don't need more email than i'm already getting 00:28:33 Anyone care to put a vote down or am I to assume that no vote is a +1 vote? 00:28:43 I'll vote 0 00:28:47 ianweller: I expect arrows, mud,and pitch 00:29:01 quaid: i expect all of that to be flaming. :( 00:29:03 when we tell people that the CLA needs to be used to change a license like that 00:29:14 * ianweller votes 0 on the proposal, i just wanna nuclearize it now ;) 00:29:23 jjmcd: are you unsettled by something? 00:29:40 at the least,folks,make sure I answer all the questions when I write this article :) 00:29:43 I like the CC by SA, a little uncomfortable wit pushing too hard 00:30:09 my argument is that we are on a teeny, tiny island all by ourselves 00:30:18 jjmcd: The problem we have is the problem of calling in everyone that has ever touched anything that is covered by the license. We just can't do that. 00:30:19 for example,we rewrite GNOME docs each release. 00:30:40 for our ability to do open content 00:30:41 Yeah, the best we can do is to get all our current contributors to buy in 00:30:48 the relicensing is crucial 00:31:16 jjmcd: Yes and I think we (Docs) has been doing that. 00:31:30 ok, I'll write my piece, cross post it,and see where that goes 00:31:41 I haven't heard objections, but I haven't heard from laubersm, don't recall Zach 00:31:43 OK with setting a 2 week deadline for discussion? 00:32:03 Sounds like a plan 00:32:11 Apache consensus rules are in effect 00:32:16 quaid: Yes... 2 weeks from today. If we need to we'll hold a town hall meeting and I'll put you at the front of the room. :) 00:32:26 if someone doesn't speak up in a reasonable period of time, that is taken as consent :) 00:32:33 Sparks: OK! 00:32:58 But lets make a special effort to be sure the F10 contributors have heard the story 00:32:58 :) 00:33:06 jjmcd: how? 00:33:11 that is, we've been discussing it on list for 6 weeks 00:33:30 Direct email to those that haven't been here - I doubt there's more than 2 or three 00:33:53 ok 00:33:57 * quaid will do that 00:34:10 I don't forsee a problem, but some have been busy lately, I'm thinking of laubersm but I suspect there may be one or two others 00:34:16 quaid: We can hit the list that goes to everyone that is on the Docs FAS group 00:34:38 Sparks: but they should all be on f-docs-l 00:34:45 I'll email people 00:34:52 who committed changes to any repo for the last two releases 00:35:04 Yeah, I don't know we need to go after the whole list - quaid - exactly 00:35:11 but I don't want to circumnavigate the established channels of communication. 00:35:29 the list == the channel, but hey :) 00:35:35 ;-) 00:36:29 After listening to Paul and Jan maybe I'm a little over sensitive 00:36:59 Okay, anything else? 00:37:57 #topic Ian has news from CC on the licensing change marketing whatnottery 00:38:00 ianweller: Go! 00:39:16 Is someone else asleep? 00:40:10 hmmm - while I was watching ianweller changed from 10 minutes ago to 144 minutes ago, whats up with that 00:40:16 Okay, we'll come back to him. 00:40:20 what? 00:40:21 i'm here 00:40:30 sorry :) 00:40:34 marketeer time 00:40:35 ianweller: ^^^ topic 00:40:46 http://www.redhat.com/archives/fedora-docs-list/2009-July/msg00003.html <-- got this from CC today. 00:40:51 it's been sent to fedora-docs-list as you can tell. 00:40:59 that's all i've got ;) 00:42:00 ianweller: Well... what is it? 00:42:12 that they're willing to make a blog post 00:42:28 saying "hey look they switched licenses whee" 00:42:35 and we just need top ing them when we're ready to do that 00:43:12 cool 00:43:16 Anyone have any questions? 00:44:02 #topic Shared open-source style guide 00:44:08 ke4qqq: You around tonight? 00:45:20 I guess not. 00:45:39 I don't think there has been any change. Does anyone have any questions or comments? 00:46:24 no 00:46:27 #topic Bugzilla Component Changes 00:46:38 #link https://fedoraproject.org/wiki/User:Sparks/BZ_and_Guide_Table 00:46:58 So I started the process of moving files around and removing the products from our BZ component. 00:47:22 If anyone has a project that needs to be in BZ please let me know and I can get you setup pretty quickly. 00:47:31 Anyone have any questions or comments? 00:48:23 #topic 00:48:28 #topic Outstanding BZ Tickets 00:48:42 #link http://tinyurl.com/lgx98o 00:48:54 If everyone would take a look at the above link... 00:49:03 those tickets are just outstanding! ;) 00:49:13 these are the outstanding tickets that were opened during the month of June that haven't been accepted. 00:49:40 ianweller: Yes they are because these are tickets that people filed because they care enough about our products! 00:49:51 :D 00:50:58 I'm not going to go through them all tonight but I would like to start running through the ones we need to work on so we can respond to the appropriately. 00:51:10 but feel free to take one! 00:52:07 questions? 00:52:25 #topic DocsProject wiki pages changes 00:52:32 ianweller: What's the word on wikibot? 00:52:42 it's on my to-do list 00:53:29 Okay... 00:53:42 IOW, nothing. :( 00:54:04 Yeah... Well, we should probably revisit this again and see what needs to be done. 00:54:09 questions? 00:54:51 #topic With the new definition of alpha and beta, do we need to treat release notes differently? 00:54:58 jjmcd: Did you put this up there? 00:55:04 Yes 00:55:20 I wonder whether the one pager is in keeping with "feature complete" 00:55:45 Not sure that it is realistic to do much more so early tho 00:55:56 the one pager? Is this the idea stickster_afk had at the FAD? 00:56:03 But I haven't fully digested the schedule and what it means 00:56:12 No, that's what poelcat just sait 00:56:15 said 00:56:41 What we used to do for beta 00:56:47 Ahhh 00:57:06 Well, if you want to do something different this time around I'm all ears. 00:57:21 f13 really wants alpha and beta to actually be alpha and beta, and I understand his point 00:57:38 but I obviously can't predict whether what he wants will actually happen 00:58:26 So perhaps this needs another week for a more meaningful discussion, with proposals for ppl to chew on 00:59:03 worksfor me 00:59:18 I'll digest it all over the next week 00:59:42 Still haven't dug out from my email since I was away 00:59:59 All that Berliner Kindl you know 01:00:07 :) 01:00:56 okay, so we'll discuss it more next week. 01:01:06 Also I spoke with glezos and the German translator about their problems 01:01:22 Anything to report? 01:01:37 Not really, just what you would expect, except perhaps 01:01:49 that the new transifex will help us both 01:01:58 Amen 01:02:20 when will that be up and running? 01:02:29 Well, it's finally been packaged 01:02:40 That's encouraging. 01:02:42 So I guess RSN :) 01:03:10 As I understand, that was the blocker 01:03:28 usually is 01:03:36 ;) 01:03:40 Also 01:03:46 * quaid >muffle, muffle, murg< 01:04:16 spot didn't laugh too much at my spec file, so I guess I have more confidence in pushing to do whatever I need to in order to won that and get Jesse out of the loop 01:04:24 * ianweller has to run, bye 01:04:30 s/won/own 01:04:40 seeYA ianweller 01:06:33 eof 01:06:34 Okay, anything else? 01:06:46 #topic Guide needs? 01:06:53 Anyone have any needs for their guides? 01:07:41 I guess not... 01:07:48 #topic New Guides 01:07:55 Okay, someone put down the RPM guide 01:07:58 Who was that? 01:08:06 Florian asked if we could take over the rpm guide 01:08:19 apparently the guide in docs.fp.o might not be THE guide 01:08:21 Who is Florian? 01:08:36 he is going to send me a link to their repo so I can look at it 01:08:42 I have no problems with it. I have a ticket open for it to be moved to the wiki for redevelopment. 01:08:49 and then come to one of our meetings to discuss it 01:09:01 .bug 508930 01:09:02 I see that, not sure that wiki is the desired target but 01:09:03 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=508930 medium, low, ---, fedora-docs-list, NEW, Move RPM Guide to wiki 01:09:06 Sparks: Bug 508930 Move RPM Guide to wiki - https://bugzilla.redhat.com/show_bug.cgi?id=508930 01:09:07 Bug 508930: medium, low, ---, fedora-docs-list, NEW, Move RPM Guide to wiki 01:09:08 um what? 01:09:19 which guide is not which guide? 01:09:28 we can discuss it when we have him on channel 01:09:32 ok 01:09:53 fwiw, yeah, converting from XML to wiki is rarely a good idea :) 01:10:05 I think he is talking about the guide at rpm.org 01:10:27 Evidently the rpm guys can't even build th guide 01:10:52 quaid: I know but things die in docs.fp.o, too 01:11:00 So for now, jut a heads up that this is coming 01:11:28 jjmcd: Cool 01:11:28 oh, I wonder if the one at rpm.org is the same guide, of sourts 01:11:31 Anyone else? 01:11:32 ok, I'll hold my fire. 01:13:20 #topic All other business 01:13:27 Okay, does anyone have anything else? 01:14:15 5 01:14:18 4 01:14:20 3 01:14:23 2 01:14:26 1 01:14:33 Thanks for everyone coming! 01:14:36 #endmeeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Fri Jul 3 04:08:18 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 2 Jul 2009 21:08:18 -0700 Subject: Public Review of The DocBook Publishers Schema Version 1.0 [OASIS] Message-ID: <20090703040818.GC19749@calliope.phig.org> Att'n DocBook geeks ... ----- Forwarded message from Mary McRae ----- From: Mary McRae To: members at lists.oasis-open.org, tc-announce at lists.oasis-open.org Date: Thu, 2 Jul 2009 23:17:43 -0400 Cc: docbook-tc at lists.oasis-open.org, OASIS TAB Subject: [members] Public Review of The DocBook Publishers Schema Version 1.0 To OASIS members, Public Announce Lists: The OASIS DocBook TC has recently approved the following specification as a Committee Draft and approved the package for public review: The DocBook Publishers Schema Version 1.0 The public review starts today, 2 July 2009, and ends 31 August 2009. This is an open invitation to comment. We strongly encourage feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of OASIS work. Please feel free to distribute this announcement within your organization and to other appropriate mail lists. More non-normative information about the specification and the technical committee may be found at the public home page of the TC at: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook. Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be located via the button marked "Send A Comment" at the top of that page, or directly at: http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=docbook. Submitted comments (for this work as well as other works of that TC) are publicly archived and can be viewed at: http://lists.oasis-open.org/archives/docbook-comment/. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. The specification document and related files are available here: Editable Source: http://docs.oasis-open.org/docbook/specs/publishers-1.0-spec-cd-01.xml PDF: http://docs.oasis-open.org/docbook/specs/publishers-1.0-spec-cd-01.pdf HTML: http://docs.oasis-open.org/docbook/specs/publishers-1.0-spec-cd-01.html Schema: http://docs.oasis-open.org/docbook/rng/publishers/publishers.rnc OASIS and the DocBook TC welcome your comments. Mary P McRae Director, Technical Committee Administration OASIS: Advancing open standards for the information society email: mary.mcrae at oasis-open.org web: www.oasis-open.org twitter: fiberartisan #oasisopen phone: 1.603.232.9090 --------------------------------------------------------------------- This email list is used solely by OASIS for official consortium communications. Opt-out requests may be sent to member-services at oasis-open.org, however, all members are strongly encouraged to maintain a subscription to this list. ----- End forwarded message ----- -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugzilla at redhat.com Fri Jul 3 19:27:02 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 3 Jul 2009 15:27:02 -0400 Subject: [Bug 508930] Move RPM Guide to wiki In-Reply-To: References: Message-ID: <200907031927.n63JR2sb032193@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508930 Karsten Wade changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kwade at redhat.com --- Comment #1 from Karsten Wade 2009-07-03 15:27:01 EDT --- Gong from XML to wiki and back to XML is an enormous PITA and potential waste of time. Why not use Zikula + the wysiwyg DocBook editor for this instead? This guide actually needs a fedorahosted.org instance; that will help enable contributors. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Fri Jul 3 19:27:21 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 3 Jul 2009 15:27:21 -0400 Subject: [Bug 508935] Need to move the Documentation Guide to the wiki In-Reply-To: References: Message-ID: <200907031927.n63JRLJk017826@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508935 Karsten Wade changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kwade at redhat.com --- Comment #2 from Karsten Wade 2009-07-03 15:27:21 EDT --- Gong from XML to wiki and back to XML is an enormous PITA and potential waste of time. Why not use Zikula + the wysiwyg DocBook editor for this instead? This guide actually needs a fedorahosted.org instance; that will help enable contributors. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From poelstra at redhat.com Fri Jul 3 21:19:53 2009 From: poelstra at redhat.com (John Poelstra) Date: Fri, 03 Jul 2009 14:19:53 -0700 Subject: logistics list Message-ID: <4A4E75F9.8040900@redhat.com> The logistics at lists.fedoraproject.org mailing list has been created to meet the requirements discussed here: http://www.redhat.com/archives/fedora-advisory-board/2009-July/msg00000.html Anyone is welcome to join the list at: https://admin.fedoraproject.org/mailman/listinfo/logistics and participants are strongly encouraged to use it only for important topics that need to be coordinated across teams. I have also take the liberty to sign up leads from each the teams that attended the Fedora 11 Release Readiness meetings (assuming they will be the same for Fedora 12) as well as the people who have expressed an interest in helping with or learning more about the Fedora Zikula CMS implementation. Feel free to adjust things by adding or removing yourself. John From satya.komaragiri at gmail.com Mon Jul 6 09:30:13 2009 From: satya.komaragiri at gmail.com (satya komaragiri) Date: Mon, 6 Jul 2009 15:00:13 +0530 Subject: [Fwd: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]] In-Reply-To: <146c63b10905271106p56d5f2bfn5018a681c45669a1@mail.gmail.com> References: <612251041.2725171242995912855.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> <4A19E7AD.9010707@redhat.com> <4A19FBC5.7090500@fedoraproject.org> <4A19FCC4.5040901@redhat.com> <4A19FE48.2070504@fedoraproject.org> <4A1A23B2.70307@redhat.com> <146c63b10905271106p56d5f2bfn5018a681c45669a1@mail.gmail.com> Message-ID: <146c63b10907060230xb80b145tba3c9bef3f78aeea@mail.gmail.com> Hello, I was wondering where could I get in touch with the Zikula and Publican teams within Fedora. I will be soon finishing my DocBook plugin (support for subset of tags as decided on this list[1]) for Beacon and will look to integrating it with Zikula and Publican. Regards, Satya From foss.mailinglists at gmail.com Mon Jul 6 09:33:00 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Mon, 6 Jul 2009 15:03:00 +0530 Subject: [Fwd: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]] In-Reply-To: <146c63b10907060230xb80b145tba3c9bef3f78aeea@mail.gmail.com> References: <612251041.2725171242995912855.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> <4A19E7AD.9010707@redhat.com> <4A19FBC5.7090500@fedoraproject.org> <4A19FCC4.5040901@redhat.com> <4A19FE48.2070504@fedoraproject.org> <4A1A23B2.70307@redhat.com> <146c63b10905271106p56d5f2bfn5018a681c45669a1@mail.gmail.com> <146c63b10907060230xb80b145tba3c9bef3f78aeea@mail.gmail.com> Message-ID: <35586fc00907060233i62794f50u666abc1650f03fda@mail.gmail.com> On Mon, Jul 6, 2009 at 3:00 PM, satya komaragiri wrote: > I was wondering where could I get in touch with the Zikula and > Publican teams within Fedora. I will be soon finishing my DocBook > plugin (support for subset of tags as decided on this list[1]) for > Beacon and will look to integrating it with Zikula and Publican. The Publican folks are on this list and, I would not know about the Zikula folks :) -- http://www.gutenberg.net - Fine literature digitally re-published http://www.plos.org - Public Library of Science http://www.creativecommons.org - Flexible copyright for creative work From satya.komaragiri at gmail.com Mon Jul 6 09:37:40 2009 From: satya.komaragiri at gmail.com (satya komaragiri) Date: Mon, 6 Jul 2009 15:07:40 +0530 Subject: [Fwd: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]] In-Reply-To: <35586fc00907060233i62794f50u666abc1650f03fda@mail.gmail.com> References: <612251041.2725171242995912855.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> <4A19E7AD.9010707@redhat.com> <4A19FBC5.7090500@fedoraproject.org> <4A19FCC4.5040901@redhat.com> <4A19FE48.2070504@fedoraproject.org> <4A1A23B2.70307@redhat.com> <146c63b10905271106p56d5f2bfn5018a681c45669a1@mail.gmail.com> <146c63b10907060230xb80b145tba3c9bef3f78aeea@mail.gmail.com> <35586fc00907060233i62794f50u666abc1650f03fda@mail.gmail.com> Message-ID: <146c63b10907060237g1f444967xe9c78db9de0467c9@mail.gmail.com> > The Publican folks are on this list and, > I would not > know about the Zikula folks :) > > -- Thanks a lot :) From stickster at gmail.com Mon Jul 6 11:47:38 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 6 Jul 2009 07:47:38 -0400 Subject: [Fwd: Re: [Fwd: Re: Proposal for Implementing a Docbook Editor]] In-Reply-To: <146c63b10907060237g1f444967xe9c78db9de0467c9@mail.gmail.com> References: <612251041.2725171242995912855.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> <4A19E7AD.9010707@redhat.com> <4A19FBC5.7090500@fedoraproject.org> <4A19FCC4.5040901@redhat.com> <4A19FE48.2070504@fedoraproject.org> <4A1A23B2.70307@redhat.com> <146c63b10905271106p56d5f2bfn5018a681c45669a1@mail.gmail.com> <146c63b10907060230xb80b145tba3c9bef3f78aeea@mail.gmail.com> <35586fc00907060233i62794f50u666abc1650f03fda@mail.gmail.com> <146c63b10907060237g1f444967xe9c78db9de0467c9@mail.gmail.com> Message-ID: <20090706114738.GB9868@localhost.localdomain> On Mon, Jul 06, 2009 at 03:07:40PM +0530, satya komaragiri wrote: > > The Publican folks are on this list and, > > I would not > > know about the Zikula folks :) > > Thanks a lot :) Simon and a couple other Zikula folks are present on this list too. (Thanks for hanging around, guys!) -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From stickster at gmail.com Mon Jul 6 13:23:37 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 6 Jul 2009 09:23:37 -0400 Subject: [Fwd: [publican-list] Publican 1.0] Message-ID: <20090706132337.GH9868@localhost.localdomain> FYI... Paul ----- Forwarded message from Michael Hideo ----- Date: Mon, 06 Jul 2009 09:01:03 +1000 From: Michael Hideo To: publican-list at redhat.com Subject: [publican-list] Publican 1.0 X-BeenThere: publican-list at redhat.com Folks, This is a heads up email for the plan to begin testing Publican 1.0 on Fedora. These are the actions we are looking at right now to begin alpha testing the software: F12 Guides ========== * Installation Guide * Security Guide * Deployment Guide * Virtualization Guide * Release Notes We will need someone from l10n to check that the translations come out cleanly. Additionally, we will need a dedicated person to do QE against the new bugs and to regression test against the old bugs. Also we need someone to work between l10n and QE to ensure that all the langs still build correctly. A few other activities that need to performed: * Brands need to be repackaged (cc-by-sa for fedora/rh) * Need to start a lock on the test repos Rough timeline is sometime in the next 2 weeks. Note that the publican software has been completely re-written from the ground up. Apparently it will not use a "make" system but will use proper commands and actions. This will provide more flexibility for the future and allow us to be cross platform. More timelines and infotainment to come shortly. - Mike _______________________________________________ publican-list mailing list publican-list at redhat.com https://www.redhat.com/mailman/listinfo/publican-list Wiki: https://fedorahosted.org/publican ----- End forwarded message ----- From bugzilla at redhat.com Tue Jul 7 04:09:51 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 7 Jul 2009 00:09:51 -0400 Subject: [Bug 229153] docs-common should move to submodule (&docs-common) In-Reply-To: References: Message-ID: <200907070409.n6749pOk016624@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=229153 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Component|docs-common |docs-requests --- Comment #1 from Eric Christensen 2009-07-07 00:09:50 EDT --- Ticket moved to allow products to be removed from BZ. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From eric at christensenplace.us Tue Jul 7 04:14:15 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 07 Jul 2009 00:14:15 -0400 Subject: Removal of Fedora Documentation products in BZ. In-Reply-To: <4A4A3AF6.902@redhat.com> References: <1246378277.3429.65.camel@echristensen.tkctech.com> <4A4A3AF6.902@redhat.com> Message-ID: <1246940055.2298.35.camel@ericlaptop.christensenplace.us> On Tue, 2009-06-30 at 12:19 -0400, David Lawrence wrote: > On 06/30/2009 12:11 PM, Eric Christensen wrote: > > Request the following products be removed from the Fedora Documentation > > component in BZ: > > > > hardening > > press-release > > proxy-guide > > toolchain-devel > > usb-hotplug > > xml-normalize > > docs-common > > desktop-up2date > > mirror-tutorial > > updates > > translation-guide > > translation-guide-windows > > > > > > hardening: deleted > press-release: deleted > proxy-guide: still has 1 bug assigned to it > toolchain-devel: has 10 bugs assigned to it > usb-hotplug: has 1 bug assigned to it > xml-normalize: has 1 bug > docs-common: has 40 bugs > desktop-up2date: has 1 bug > mirror-tutorial: has 12 bugs > updates: has 3 bugs > translation-guide: deleted > translation-guide-windows: has 1 bug > > Some I was able to remove. The others will need their bugs moved to a > different component so that their old component can be removed. Just > being closed is not enough. > > Thanks > Dave > > > > All tickets in these products should be closed. > > > > Thanks, > > Eric Christensen > > Fedora Docs Project Lead > > > > Fedora Talk: 5102043 Phone: 919-424-0063 x 5102043 > > E-Mail: sparks at fedoraproject.org SIP: sparks at talk.fedoraproject.org > > IRC: Sparks on freenode.net > > > > GPG Fingerprint: CA02 4ACA EB6C 1A76 F0D6 1127 7D04 D240 BD0C 14C1 > > > > Dave, All tickets should have been moved, now. Thanks, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From ian at ianweller.org Tue Jul 7 20:11:40 2009 From: ian at ianweller.org (Ian Weller) Date: Tue, 7 Jul 2009 15:11:40 -0500 Subject: python-mwlib + odfpy is a mess. Message-ID: <20090707201140.GF27918@deathray.ianweller.org> Can someone volunteer to comaintain python-mwlib and odfpy for me so that they can get in proper working order? Can somebody on Docs also write a test suite (a few commands that Docs uses a lot) so I know whether or not we can consider it working or not? :) -- Ian Weller GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From eric at christensenplace.us Tue Jul 7 20:24:11 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 07 Jul 2009 16:24:11 -0400 Subject: Release Notes Meeting Message-ID: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> I'd like to hold a Release Notes meeting some time within the next couple of weeks to discuss changes and how F12's notes are going to come together. I know there is only a handful of people interested in this so those that are please let me know when you are available[1]. [1] http://whenisgood.net/UbMSZS Thanks, Eric From wb8rcr at arrl.net Tue Jul 7 20:50:40 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Tue, 7 Jul 2009 16:50:40 -0400 Subject: Release Notes Meeting References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> Message-ID: <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> Since the web page makes no mention of time zone, is it safe to assume that they are UTC? --McD ----- Original Message ----- From: "Eric Christensen" To: Sent: Tuesday, July 07, 2009 4:24 PM Subject: Release Notes Meeting > I'd like to hold a Release Notes meeting some time within the next > couple of weeks to discuss changes and how F12's notes are going to come > together. > > I know there is only a handful of people interested in this so those > that are please let me know when you are available[1]. > > [1] http://whenisgood.net/UbMSZS > > Thanks, > Eric > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > From stickster at gmail.com Tue Jul 7 21:18:40 2009 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 7 Jul 2009 17:18:40 -0400 Subject: Release Notes Meeting In-Reply-To: <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> Message-ID: <20090707211840.GI2867@localhost.localdomain> On Tue, Jul 07, 2009 at 04:50:40PM -0400, John J. McDonough wrote: > Since the web page makes no mention of time zone, is it safe to assume > that they are UTC? The app relies on the organizer to set the "use timezones" flag, then respondents indicate their timezone in their reply and the times are magically set up properly for local time. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From eric at christensenplace.us Tue Jul 7 23:25:07 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 07 Jul 2009 19:25:07 -0400 Subject: Release Notes Meeting In-Reply-To: <20090707211840.GI2867@localhost.localdomain> References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> <20090707211840.GI2867@localhost.localdomain> Message-ID: <1247009111.2310.35.camel@ericlaptop.christensenplace.us> On Tue, 2009-07-07 at 17:18 -0400, Paul W. Frields wrote: > On Tue, Jul 07, 2009 at 04:50:40PM -0400, John J. McDonough wrote: > > Since the web page makes no mention of time zone, is it safe to assume > > that they are UTC? > > The app relies on the organizer to set the "use timezones" flag, then > respondents indicate their timezone in their reply and the times are > magically set up properly for local time. And the organizer has now activated the tz flag. Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Tue Jul 7 23:50:52 2009 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 7 Jul 2009 19:50:52 -0400 Subject: python-mwlib + odfpy is a mess. In-Reply-To: <20090707201140.GF27918@deathray.ianweller.org> References: <20090707201140.GF27918@deathray.ianweller.org> Message-ID: <20090707235052.GF10765@localhost.localdomain> On Tue, Jul 07, 2009 at 03:11:40PM -0500, Ian Weller wrote: > Can someone volunteer to comaintain python-mwlib and odfpy for me so > that they can get in proper working order? > > Can somebody on Docs also write a test suite (a few commands that Docs > uses a lot) so I know whether or not we can consider it working or not? > :) I put up a simple test page here: https://fedoraproject.org/wiki/Test_page_for_mwlib Good news and bad news: * Upstream mwlib is really chugging along. That's healthy. * Current mwlib is now at 0.11.2, which is way ahead of our anemic 0.9.10. It now requires odfpy==0.9. * odfpy-0.9 shouldn't be too hard to do, right? I think mwlib is the only thing using it. * Oh wait, did I mention there's more? mwlib-0.11.2 also needs python-lockfile>=0.8 and python-timelib>=0.2, neither of which we have yet, meaning more packaging. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From ian at ianweller.org Wed Jul 8 05:21:37 2009 From: ian at ianweller.org (Ian Weller) Date: Wed, 8 Jul 2009 00:21:37 -0500 Subject: python-mwlib + odfpy is a mess. In-Reply-To: <20090707235052.GF10765@localhost.localdomain> References: <20090707201140.GF27918@deathray.ianweller.org> <20090707235052.GF10765@localhost.localdomain> Message-ID: <20090708052137.GP27918@deathray.ianweller.org> On Tue, Jul 07, 2009 at 07:50:52PM -0400, Paul W. Frields wrote: > I put up a simple test page here: > https://fedoraproject.org/wiki/Test_page_for_mwlib > Thanks :) Thanks also to Dave Nalley volunteered to commandeer the effort to fix this crapola I created (whee!) so I'll double check that he read this (I assume so). > Good news and bad news: > > * Upstream mwlib is really chugging along. That's healthy. > > * Current mwlib is now at 0.11.2, which is way ahead of our anemic > 0.9.10. It now requires odfpy==0.9. > > * odfpy-0.9 shouldn't be too hard to do, right? I think mwlib is the > only thing using it. > Correct AFAIK... > * Oh wait, did I mention there's more? mwlib-0.11.2 also needs > python-lockfile>=0.8 and python-timelib>=0.2, neither of which we > have yet, meaning more packaging. > Oh did I mention there's some dependency epic fail going on in EL-5? I don't know what to do about it, nor do I remember what it is, but it has something to do with a Python library being an older version that what we need and the maintainer isn't willing to update because it would break previous code. I'm thinking of dropping EPEL for both of these packages (it was odfpy that was the culprit when I was updating it to 0.9). -- Ian Weller GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From david.nalley at fedoraproject.org Wed Jul 8 05:33:13 2009 From: david.nalley at fedoraproject.org (David Nalley) Date: Wed, 8 Jul 2009 01:33:13 -0400 Subject: python-mwlib + odfpy is a mess. In-Reply-To: <20090708052137.GP27918@deathray.ianweller.org> References: <20090707201140.GF27918@deathray.ianweller.org> <20090707235052.GF10765@localhost.localdomain> <20090708052137.GP27918@deathray.ianweller.org> Message-ID: On Wed, Jul 8, 2009 at 1:21 AM, Ian Weller wrote: > On Tue, Jul 07, 2009 at 07:50:52PM -0400, Paul W. Frields wrote: >> I put up a simple test page here: >> https://fedoraproject.org/wiki/Test_page_for_mwlib >> > Thanks :) > > Thanks also to Dave Nalley volunteered to commandeer the effort to fix > this crapola I created (whee!) so I'll double check that he read this (I > assume so). > >> Good news and bad news: >> >> * Upstream mwlib is really chugging along. ?That's healthy. >> >> * Current mwlib is now at 0.11.2, which is way ahead of our anemic >> ? 0.9.10. ?It now requires odfpy==0.9. >> >> * odfpy-0.9 shouldn't be too hard to do, right? ?I think mwlib is the >> ? only thing using it. >> > Correct AFAIK... > >> * Oh wait, did I mention there's more? ?mwlib-0.11.2 also needs >> ? python-lockfile>=0.8 and python-timelib>=0.2, neither of which we >> ? have yet, meaning more packaging. >> > Oh did I mention there's some dependency epic fail going on in EL-5? I > don't know what to do about it, nor do I remember what it is, but it has > something to do with a Python library being an older version that what > we need and the maintainer isn't willing to update because it would > break previous code. I'm thinking of dropping EPEL for both of these > packages (it was odfpy that was the culprit when I was updating it to > 0.9). > > -- > Ian Weller > GnuPG fingerprint: ?E51E 0517 7A92 70A2 4226 ?B050 87ED 7C97 EFA8 4A36 > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > Yes I have been reading and started looking at this tonight. Hopefully will have a bit more time tomorrow to dedicate to it. From aph at redhat.com Wed Jul 8 09:41:58 2009 From: aph at redhat.com (Andrew Haley) Date: Wed, 08 Jul 2009 10:41:58 +0100 Subject: Help button in Fedora Message-ID: <4A5469E6.1020908@redhat.com> In Ubuntu there's a "Help" button on the top menu bar that leads to a nice help application, yelp. We have that app too, but it doesn't seem to have the same contents, which are: New to Ubuntu? Adding and Removing Software Files, Folders and Documents Customising Your Desktop Internet Music, Videos and Photos Assistive Tools Keeping Your Computer Safe Printing, Faxing and Scanning Advanced Topics And under each section there's a clear explanation of what to do. Maybe we have something equivalent for Fedora, but I can't find it. Andrew. From wb8rcr at arrl.net Wed Jul 8 11:10:51 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Wed, 8 Jul 2009 07:10:51 -0400 Subject: Help button in Fedora References: <4A5469E6.1020908@redhat.com> Message-ID: <45D38FD1756A4C608A5F6D098694C64F@Aidan> Yelp is basically a document display application. It has the great advantage of being very bright about localization. We currently display the release notes and "About Fedora" in yelp. Unfortunately, yelp is a Gnome application, and the KDE crowd dislikes it. There is a KDE analog, but it seems to be abused rather than used. There is so much junk in it that it is impossible to find anything, and what is there seems to be mostly useless. Much of what you describe in the Ubuntu help is in the Fedora User's Guide, which will probably be getting a higher profile now that it is up to date. Personally, I like yelp and would like to see it used more effectively. But for the practical reason of trying to be desktop neutral, I would expect our use of yelp to decline rather than increase. --McD ----- Original Message ----- From: "Andrew Haley" To: Sent: Wednesday, July 08, 2009 5:41 AM Subject: Help button in Fedora > In Ubuntu there's a "Help" button on the top menu bar that leads to a > nice help application, yelp. We have that app too, but it doesn't > seem to have the same contents, which are: > > New to Ubuntu? > Adding and Removing Software > Files, Folders and Documents > Customising Your Desktop > Internet > Music, Videos and Photos > Assistive Tools > Keeping Your Computer Safe > Printing, Faxing and Scanning > Advanced Topics > > And under each section there's a clear explanation of what to do. > Maybe we have something equivalent for Fedora, but I can't find it. > > Andrew. > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > From mclasen at redhat.com Wed Jul 8 12:49:18 2009 From: mclasen at redhat.com (Matthias Clasen) Date: Wed, 08 Jul 2009 08:49:18 -0400 Subject: Help button in Fedora In-Reply-To: <45D38FD1756A4C608A5F6D098694C64F@Aidan> References: <4A5469E6.1020908@redhat.com> <45D38FD1756A4C608A5F6D098694C64F@Aidan> Message-ID: <1247057358.2153.4.camel@planemask> On Wed, 2009-07-08 at 07:10 -0400, John J. McDonough wrote: > Yelp is basically a document display application. It has the great > advantage of being very bright about localization. We currently display the > release notes and "About Fedora" in yelp. > > Unfortunately, yelp is a Gnome application, and the KDE crowd dislikes it. > There is a KDE analog, but it seems to be abused rather than used. There is > so much junk in it that it is impossible to find anything, and what is there > seems to be mostly useless. Much of what you describe in the Ubuntu help is > in the Fedora User's Guide, which will probably be getting a higher profile > now that it is up to date. > > Personally, I like yelp and would like to see it used more effectively. > But for the practical reason of trying to be desktop neutral, I would expect > our use of yelp to decline rather than increase. If you ask me, that so called 'desktop neutrality' is exactly what makes the Fedora offerings in this area so much inferior to Ubuntu. What Andrew was asking for is to make the Help button show useful task-oriented documentation. In the default installation, that Help button brings up Yelp. So, if you want your documents to be found by the majority of users that need them, this is exactly where they should be: Behind the help button, in yelp. From aph at redhat.com Wed Jul 8 13:20:11 2009 From: aph at redhat.com (Andrew Haley) Date: Wed, 08 Jul 2009 14:20:11 +0100 Subject: Help button in Fedora In-Reply-To: <45D38FD1756A4C608A5F6D098694C64F@Aidan> References: <4A5469E6.1020908@redhat.com> <45D38FD1756A4C608A5F6D098694C64F@Aidan> Message-ID: <4A549D0B.5060407@redhat.com> John J. McDonough wrote: > Yelp is basically a document display application. It has the great > advantage of being very bright about localization. We currently display > the release notes and "About Fedora" in yelp. > > Unfortunately, yelp is a Gnome application, and the KDE crowd dislikes > it. There is a KDE analog, but it seems to be abused rather than used. > There is so much junk in it that it is impossible to find anything, and > what is there seems to be mostly useless. Much of what you describe in > the Ubuntu help is in the Fedora User's Guide, which will probably be > getting a higher profile now that it is up to date. Yeah, but help needs to be there, right behind the Help button. Of course I don't care whether it's yelp or something else. Andrew. From eric at christensenplace.us Wed Jul 8 15:05:30 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 08 Jul 2009 11:05:30 -0400 Subject: Fedora Docs Meeting Reminder Message-ID: <1247065530.2665.2.camel@echristensen.tkctech.com> REMINDER: There will be a Fedora Docs Meeting today at 0001 UTC. The agenda can be found at: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Wed Jul 8 19:11:35 2009 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 8 Jul 2009 15:11:35 -0400 Subject: python-mwlib + odfpy is a mess. In-Reply-To: References: <20090707201140.GF27918@deathray.ianweller.org> <20090707235052.GF10765@localhost.localdomain> <20090708052137.GP27918@deathray.ianweller.org> Message-ID: <20090708191135.GT24763@localhost.localdomain> On Wed, Jul 08, 2009 at 01:33:13AM -0400, David Nalley wrote: > On Wed, Jul 8, 2009 at 1:21 AM, Ian Weller wrote: > > On Tue, Jul 07, 2009 at 07:50:52PM -0400, Paul W. Frields wrote: > >> I put up a simple test page here: > >> https://fedoraproject.org/wiki/Test_page_for_mwlib > >> > > Thanks :) > > > > Thanks also to Dave Nalley volunteered to commandeer the effort to fix > > this crapola I created (whee!) so I'll double check that he read this (I > > assume so). > > > >> Good news and bad news: > >> > >> * Upstream mwlib is really chugging along. ?That's healthy. > >> > >> * Current mwlib is now at 0.11.2, which is way ahead of our anemic > >> ? 0.9.10. ?It now requires odfpy==0.9. > >> > >> * odfpy-0.9 shouldn't be too hard to do, right? ?I think mwlib is the > >> ? only thing using it. > >> > > Correct AFAIK... > > > >> * Oh wait, did I mention there's more? ?mwlib-0.11.2 also needs > >> ? python-lockfile>=0.8 and python-timelib>=0.2, neither of which we > >> ? have yet, meaning more packaging. > >> > > Oh did I mention there's some dependency epic fail going on in EL-5? I > > don't know what to do about it, nor do I remember what it is, but it has > > something to do with a Python library being an older version that what > > we need and the maintainer isn't willing to update because it would > > break previous code. I'm thinking of dropping EPEL for both of these > > packages (it was odfpy that was the culprit when I was updating it to > > 0.9). > > Yes I have been reading and started looking at this tonight. Hopefully > will have a bit more time tomorrow to dedicate to it. Re: EPEL, as much as I love to have lots of good Fedora stuff in those repos, is there a specific call for mwlib to work there? I thought our use of mwlib was going to be entirely client-side. Are there any plans to use, or situations where we might need, mwlib to call from a server app? Sorry if I'm not remembering something obvious, too much juggling for one brain. ;-) -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From ian at ianweller.org Wed Jul 8 19:28:17 2009 From: ian at ianweller.org (Ian Weller) Date: Wed, 8 Jul 2009 14:28:17 -0500 Subject: python-mwlib + odfpy is a mess. In-Reply-To: <20090708191135.GT24763@localhost.localdomain> References: <20090707201140.GF27918@deathray.ianweller.org> <20090707235052.GF10765@localhost.localdomain> <20090708052137.GP27918@deathray.ianweller.org> <20090708191135.GT24763@localhost.localdomain> Message-ID: <20090708192817.GK29325@deathray.ianweller.org> On Wed, Jul 08, 2009 at 03:11:35PM -0400, Paul W. Frields wrote: > Re: EPEL, as much as I love to have lots of good Fedora stuff in those > repos, is there a specific call for mwlib to work there? I thought > our use of mwlib was going to be entirely client-side. Are there any > plans to use, or situations where we might need, mwlib to call from a > server app? > I haven't heard of anything. When I did the package review I thought to myself "hmm, somebody might like this in EPEL, and it wouldn't necessarily be too hard dependency-wise." oh if only I could see ahead :) -- Ian Weller GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From stickster at gmail.com Wed Jul 8 23:43:39 2009 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 8 Jul 2009 19:43:39 -0400 Subject: Help button in Fedora In-Reply-To: <1247057358.2153.4.camel@planemask> References: <4A5469E6.1020908@redhat.com> <45D38FD1756A4C608A5F6D098694C64F@Aidan> <1247057358.2153.4.camel@planemask> Message-ID: <20090708234339.GC666@localhost.localdomain> On Wed, Jul 08, 2009 at 08:49:18AM -0400, Matthias Clasen wrote: > On Wed, 2009-07-08 at 07:10 -0400, John J. McDonough wrote: > > Yelp is basically a document display application. It has the great > > advantage of being very bright about localization. We currently display the > > release notes and "About Fedora" in yelp. > > > > Unfortunately, yelp is a Gnome application, and the KDE crowd > > dislikes it. There is a KDE analog, but it seems to be abused > > rather than used. There is so much junk in it that it is > > impossible to find anything, and what is there seems to be mostly > > useless. Much of what you describe in the Ubuntu help is in the > > Fedora User's Guide, which will probably be getting a higher > > profile now that it is up to date. > > > > Personally, I like yelp and would like to see it used more > > effectively. But for the practical reason of trying to be desktop > > neutral, I would expect our use of yelp to decline rather than > > increase. > > If you ask me, that so called 'desktop neutrality' is exactly what > makes the Fedora offerings in this area so much inferior to Ubuntu. > > What Andrew was asking for is to make the Help button show useful > task-oriented documentation. In the default installation, that Help > button brings up Yelp. So, if you want your documents to be found by > the majority of users that need them, this is exactly where they > should be: Behind the help button, in yelp. How others abuse the khelpcenter shouldn't be our concern, as long as we're providing clearly available docs there. (I wrote KDE desktop-specific entries for this in the past release notes that might be useful to someone at some point.) My personal opinion is that we should be using Yelp *more* than we do. If you want to see some cool stuff, look up the GNOME Project Mallard to see the future of task-based documentation, which (I believe) will Yelp will be capable of presenting. How can we reconcile those advances with the use of Publican in Fedora Docs? http://www.gnome.org/~shaunm/mallard/index.html -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From eric at christensenplace.us Thu Jul 9 01:25:27 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 08 Jul 2009 21:25:27 -0400 Subject: Docs Meeting 2009-07-09 IRC log Message-ID: <1247102727.2294.4.camel@ericlaptop.christensenplace.us> 00:01:31 #startmeeting 00:01:31 #meetingtopic Docs Project meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings#Thursday_July_9.2C_2009_.28Wed_US_Time.29 00:01:48 * Sparks is here 00:02:26 * jjmcd is here - barely 00:02:30 * rudi is here 00:02:38 * laubersm hides in the back 00:02:47 hiiii 00:02:48 * mhideo here 00:04:04 * Sparks gives everyone a few more minutes to trickle in 00:04:24 jjmcd: busy or tired? 00:04:39 Just got back 2 minutes ago -- need coffee badly 00:06:49 Okay, let's get started... 00:06:52 #topic Using a forked version of Publican 00:06:52 #link https://bugzilla.redhat.com/show_bug.cgi?id=476471 00:06:54 Bug 476471: medium, low, ---, petersen, ASSIGNED, Review Request: fedora-security-guide - A security guide for Linux 00:07:04 The link above is to the Security Guide which is where this question originates. The Security Guide wasn't supposed to have a component (fc11) attached to the name because it is not version specific. A hacked version of Publican was used to create the latest SRPMs which allowed us to do this. The reviewer is would like a concensus on whether using a forked (hacked) version of Publican to produce these files is okay or should we only allow "officia 00:07:28 This might be a moot point because Mike will talking about the new Publican (1.0) here in a sec... 00:07:45 but this might be something to look at from a distance as well. 00:07:46 Sparks: you fail at message lengths 00:07:52 Sparks: cut off at allow "officia 00:07:54 Do you really need to hack Publican? Why not just make your own RPM? 00:08:17 ianweller: l" releases of Publican. 00:08:31 jjmcd: Well, at the time I was just trying to make the tool work. 00:08:46 * ianweller is against forking, just use a hacked rpm 00:09:05 The question is... can we use a non-supported tool to get the job done? 00:09:11 yes. 00:10:10 Anyone else? 00:10:13 I would be concerned if someone needed some unavailable tool to build the document from sources. I'm less concerned about the rpm itself 00:10:27 yeah you would want to post what hacks you did 00:10:30 on the wiki, most likely 00:10:38 but other than that, whatever 00:10:45 ianweller: good point 00:10:50 wait. 00:11:07 Sparks: is the fedora-security-guide rpm created from docbook sources or does docbook stuff the rpm with html files? 00:11:14 s/docbook stuff/publican stuff/ 00:11:25 also, correct me if i sound stupid 00:11:36 ianweller: Good question. 00:11:48 ianweller, I think the answer is yes 00:11:55 well then 00:12:02 wait. 00:12:03 The package built correctly in koji and looks appropriate 00:12:17 if the hacked version of publican isn't what's on koji then how can it work 00:12:33 Because koji gets the srpm 00:12:44 because the hacked version is what created the srpm and spec... 00:12:50 the spec is what the problem is 00:12:52 ohhhhhhhh. 00:13:08 yeah don't worry about forking, just say on the wiki what the changes were so other people can reproduce it. 00:13:14 my USD 0.02 00:13:19 cool 00:13:21 anyone else? 00:14:09 I'm still confused 00:14:25 Isn't the hacked version of publican needed to do the building according to the spec? 00:14:25 * bcotton is perpetually confused 00:14:34 lol 00:14:40 Or is the hack *purely* to change the way the srpm/spec are created, and has nothing to do with the build process? 00:14:57 stickster: the hack "fixed" the spec issues 00:15:08 nothing to do with the build process 00:15:17 OK, question answered, thanks 00:15:28 anyone else? 00:15:30 #agreed We can use "hacked" versions of tools (Publican) to create SRPMs. 00:15:34 opps 00:15:46 That wasn't supposed to have gone out quite yet. 00:16:05 #agreed We can use "hacked" versions of tools (Publican) to create SRPMs as long as it doesn't affect the build process and the "hack" is documented on the wiki. 00:16:23 And while we are on the subject of Publican... 00:16:26 #topic The new and improved (and shiny, too) Publican. <-- mhideo 00:16:27 disco 00:16:40 mhideo: Tell us about Publican 1.0, please. 00:17:15 One of the challenges with publican is the number of features that the software needs to support 00:17:33 everything from glossaries in japanese to printing non-A4 sized paper 00:17:42 lots of other things 00:18:01 the package maintainer has spent the last 3 months re-writing it to use plugins 00:18:13 so if you want a feature, you can write a dead-simple plug in for it 00:18:39 that way development does not bottleneck on a single soul and individual features can be trialed buy different writers/translators 00:18:48 Sparks, does the above make sense? 00:19:22 mhideo: yes it does! 00:19:33 mhideo: Is there documentation available for writing a plugin? 00:19:34 does anyone have any questions about the above? 00:19:46 Is this available at the fedorahosted.org/publican repo? 00:19:47 Sparks, that is the plan 00:20:15 stickster, not sure, 00:20:25 The documentation group is writing documentation on their documentation tool. 00:20:29 :) 00:20:44 mhideo: I'll check the site quick 00:21:03 fh.o would probably be a good place to put all the plugins and such. 00:21:37 most of our efforts over the next 2 weeks will revolve around regression testing 00:21:58 mhideo: The last change in "bin/" is 5 months ago 00:22:01 that has been the largest problem so far. we make a change to fix problem X, but it introduces problem Y 00:22:05 mhideo: That can't be right, can it? 00:22:23 stickster, i don't know 00:22:52 all i know at this point is that a QA guy does the regression testing next week sometime 00:22:52 mhideo: I think jsmith said he would be available to help test 00:23:16 a good way to help would be to go through all the publican bugs and write a test case for it 00:23:28 that is what my week will look like 00:24:04 mhideo: Any idea when 1.0 will hit the Fedora repos? 00:25:02 Sparks, that is the hard part, scheduling. i borrow devel time and qa time from folks. 00:25:41 understood 00:26:00 Any other questions? 00:26:17 the above is just fyi, i would proceed with your efforts as previously planned 00:26:36 Okay... Thanks for the update Mike. 00:27:35 Okay... moving on to some F12 talk... 00:27:39 #topic F12 Calendar 00:27:39 #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-tasks.html 00:27:42 #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-releng-tasks.html 00:27:46 #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs.ics 00:28:07 These are the official calendars for the F12 release. Has everyone looked at them? Any corrections? 00:28:31 * juhp scrolls back 00:28:48 The first item coming down the road is just under four weeks away. 00:29:12 Any questions? 00:29:51 #topic Status on CC license discussion. <--quaid 00:30:03 quaid: You here? 00:30:49 If he shows up later we'll come back to this. 00:30:58 AFAIK everything is on go for the switch... 00:31:14 quaid has been putting the word out and I haven't heard any flak from anyone. 00:31:23 Does anyone have any questions or comments? 00:32:15 #topic Shared open-source style guide <--ke4qqq 00:32:23 #link https://www.redhat.com/archives/fedora-docs-list/2009-June/msg00163.html 00:32:28 ke4qqq: You around? 00:33:15 We'll come back to this topic if he shows up. 00:33:29 #topic Bugzilla Component Changes 00:33:36 #link https://fedoraproject.org/wiki/User:Sparks/BZ_and_Guide_Table 00:34:21 Okay, so all the BZ products on the lower part of that table have been removed from BZ. 00:35:02 All the open tickets were closed as WONTFIX. 00:36:05 I haven't done anything with the "Move to the wiki" guides as stickster had a good idea to not move them to the wiki but just wait for the CMS to come and put them in there for development... 00:36:13 so we don't have to mess with formatting and such. 00:36:21 Any questions or comments? 00:36:48 Sparks: Sorry, was PM'ing with someone else 00:37:51 stickster: Did you have anything? 00:37:54 did anyone check with translation teams about those two at the bottom of the abandon list? They seem to be a still relevent topic unless there is a replacement 00:38:13 yes.. 00:38:19 Not really Sparks -- just saw my name pop up. I agree somewhat with quaid that we don't want to move things twice, or move them in a way that decimates metadata we might want 00:38:21 they said dump them. they are no longer supported. 00:38:38 cool 00:39:01 stickster: Yeah. Valid. Of course I'm having problems locating some of the source... :( 00:39:19 other wise list looks good to me - with the "move to wiki" really meaning "move to place of a more living doc - such as wiki or cms" 00:39:38 laubersm: Yeah, I'll change that. 00:40:17 Sparks: Where? 00:40:22 Sparks: sorry, which source? 00:40:39 * laubersm sees translation quick start in the keep now... 00:40:45 * laubersm is slowly catching up 00:40:57 stickster: For some of the documents we were going to move to the... CMS. 00:42:36 Okay, anything else? 00:42:48 Sparks: Right, I meant which documents are causing you problems 00:43:47 stickster: Oh, I don't remember. I'll look again this week and notate on the page. 00:44:49 Okay... let's move on to everyone's favorite topic... stuff to do! 00:44:55 #topic Outstanding BZ Tickets 00:45:07 link http://tinyurl.com/lbrq84 00:45:07 The link above shows all the tickets that are currently NEW or ASSIGNED for Documentation. Please take a look in there and see if there is a ticket (or two) that you can work on. If so, please assign it to yourself. I'd like for everyone to update their tickets weekly (prefereably on Wednesdays before the meeting) so I can keep track of what needs attention and what doesn't. 00:45:13 Comments or questions? 00:45:16 #link http://tinyurl.com/lbrq84 00:48:00 okay... moving right along... 00:48:09 #topic DocsProject wiki pages changes 00:48:23 ianweller: I won't ask what the status is of the wikibot... 00:48:37 but I will ask about the status of ianbot! 00:48:40 Interesting. 00:48:49 Even though it's zodbot, the command is still #? 00:48:55 s/command/character 00:49:11 So is there still a list of changes that need to happen to the wiki? 00:49:12 ricky: yeah it's cuz meetbot is a snarfer 00:49:15 Sparks: yes. 00:49:19 They must have done some extra-weird stuff to get it that way. 00:49:21 Sparks: they're in fh.o/fedora-wiki 00:50:22 Okay. So can you give us a summary next week of what needs to be done? Maybe we can put a task out on the wiki for a newbie to work on. 00:51:30 * stickster sees that some of those tickets are his and will work on them this weekend 00:52:43 stickster: TU 00:53:23 * jjmcd_ started on some RN tickets but ran into a git wall ... need to get back at that 00:53:50 Okay... moving on... 00:53:57 #topic Release Notes meeting 00:54:39 I sent a message to f-doc-l earlier this week about a Release Notes meeting. Please look at that message and let me know your availability if you want to work on the F12 RNs. 00:54:44 Questions or comments? 00:55:06 I am now free most of thu/fri, wasn't earlier but am now 00:55:30 * Sparks doesn't know if you can go back and change your answers. 00:55:47 me too 00:56:02 jjmcd_: Well, let me know. 00:56:04 Anyone else? 00:56:27 #topic Guide needs? 00:56:35 Does anyone need anything for their guides? 00:57:22 #topic New Guides 00:57:31 Anyone have any ideas for a new guide? 00:57:44 I know that the RPM Guide could use some love. 00:58:59 Anyone want to volunteer to work on the RPM Guide? 00:59:19 I still need to hear from Florian 00:59:23 I'll ping him 00:59:38 i can learn what i need about RPM to work on the guide if nobody who knows what they're doing steps up 00:59:41 Okay. I've added the RPM Guide to the Guide table. 01:00:16 bcotton: The guide already exists but needs to be updated. You might look at what's existing and go from there. 01:00:45 sparks: can do. any guidance on what kind of updates it needs, or just in general? 01:01:01 in general. Not sure when it was last looked at. 01:01:14 bcotton: Get with me after the meeting in #fedora-docs. 01:01:24 Sparks: aye, cap'n 01:01:43 I think it talks about punch card rpms 01:01:56 oooo Those are the good kinds 01:02:05 s/kinds/kind 01:02:44 easier to edit than paper tape 01:02:58 * Sparks likes paper tape 01:03:14 did i bring my X-acto knife for nothing, then? :'( 01:03:52 Well, I'm sure you can figure out some way to use it. 01:04:39 anything else? 01:05:49 #topic Go over task table 01:06:01 I believe all the tasks that are in the task table are now in Bugzilla. I'd like to use Bugzilla for tracking all these items. Opinions? 01:07:17 anyone? 01:07:34 * bcotton feels very neutral 01:07:59 Okay then... 01:08:02 #topic All other business 01:08:11 Anyone have anything? 01:09:35 If not... we'll close... 01:10:28 5 01:10:32 4 01:10:34 3 01:10:37 2 01:10:40 1 01:10:45 Thanks everyone for coming! 01:10:49 #endmeeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Jul 9 12:23:27 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 09 Jul 2009 08:23:27 -0400 Subject: Another language complete for the User Guide. Message-ID: <1247142207.2497.5.camel@thunder.christensenplace.us> I just caught up on my reading of the f-translations-l and saw where a translator finished the Bosnian translation of the User Guide. Can we get that up on docs.fp.o? Thanks, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From danielsmw at gmail.com Thu Jul 9 16:08:27 2009 From: danielsmw at gmail.com (Matthew Daniels) Date: Thu, 09 Jul 2009 12:08:27 -0400 Subject: User Guide update Message-ID: <4A5615FB.1060106@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In September 2008, Karsten wisely wrote in his new wiki stub for the User Guide[1]: Each desktop application has integrated Help, so the scope of this document may need to be considered carefully. I feel like I've somewhat let this admonition go unattended since I've been in charge of the User Guide. Would striking a lot of specific, step-by-step tasks from the UG offend any previous content writers? Is this the direction to go? I would bring this up at a FDSCo meeting, but I've been unable to make them lately. I'd appreciate some guidance on the list. Cheers, Matthew [1] https://fedoraproject.org/wiki/User_Guide -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpWFfoACgkQ8q6Smu6JjuulhQCdFSdnjthhVt6Nx+FydAjJm6m4 DR4Ani4jM8W14XdR6bDWvUiCpO1+YL5X =k1jI -----END PGP SIGNATURE----- From eric at christensenplace.us Thu Jul 9 16:42:07 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 09 Jul 2009 12:42:07 -0400 Subject: User Guide update In-Reply-To: <4A5615FB.1060106@gmail.com> References: <4A5615FB.1060106@gmail.com> Message-ID: <1247157732.2659.1.camel@echristensen.tkctech.com> On Thu, 2009-07-09 at 12:08 -0400, Matthew Daniels wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In September 2008, Karsten wisely wrote in his new wiki stub for the > User Guide[1]: > > Each desktop application has integrated Help, so the scope of this > document may need to be considered carefully. > > I feel like I've somewhat let this admonition go unattended since I've > been in charge of the User Guide. Would striking a lot of specific, > step-by-step tasks from the UG offend any previous content writers? Is > this the direction to go? > > I would bring this up at a FDSCo meeting, but I've been unable to make > them lately. I'd appreciate some guidance on the list. > > Cheers, > Matthew > > [1] https://fedoraproject.org/wiki/User_Guide > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.10 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkpWFfoACgkQ8q6Smu6JjuulhQCdFSdnjthhVt6Nx+FydAjJm6m4 > DR4Ani4jM8W14XdR6bDWvUiCpO1+YL5X > =k1jI > -----END PGP SIGNATURE----- > What kind of step-by-step tasks are you proposing? Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From jmbuser.fedora at gmail.com Thu Jul 9 16:53:57 2009 From: jmbuser.fedora at gmail.com (John Babich) Date: Thu, 9 Jul 2009 19:53:57 +0300 Subject: User Guide update In-Reply-To: <4A5615FB.1060106@gmail.com> References: <4A5615FB.1060106@gmail.com> Message-ID: On Thu, Jul 9, 2009 at 7:08 PM, Matthew Daniels wrote: > > In September 2008, Karsten wisely wrote in his new wiki stub for the > User Guide[1]: > > Each desktop application has integrated Help, so the scope of this > document may need to be considered carefully. > > I feel like I've somewhat let this admonition go unattended since I've > been in charge of the User Guide. Would striking a lot of specific, > step-by-step tasks from the UG offend any previous content writers? Is > this the direction to go? I do appreciate that the User Guide has been updated for Fedora 11. See http://docs.fedoraproject.org/user-guide/f11/en-US/html/ for the English version. I'm sure it took many hours of dedicated work. BACKGROUND As the lead writer for the Fedora 6 User Guide (and a Fedora Project newbie at the time), I often felt confused over the scope of the User Guide. I wanted to put in specific instructions with screen shots, but was wisely discouraged from doing screen shots since it would limit the ability for the doc to be translated. At the same time, not having screen shots, I believe, took away from its usefulness. There's also the issue of trying to cover all the Desktop Managers. F6 User Guide had only GNOME coverage and was severely criticised for not covering KDE. The current User Guide includes KDE and XFCE along with GNOME. Now, what about LXDE, my current desktop? Include in the mix the fact that default applications come and go, influenced by what apps are default in the GNOME and KDE desktops in particular. There always other popular apps like OpenOffice.org and Firefox. We all seem to have our recent favorites, mine being FreeMind, which isn't even packaged for Fedora. OPTION 1 - CONTRIBUTE UPSTREAM On the other hand, perhaps it would be better to contribute updates to the upstream projects, especially ones like Gnome, KDE, XFCE and LXDE. (There's also a FLOSS docs project, but I haven't really checked it out yet.) We can then assemble a set of links to these docs while filling any gaps that may exist upstream. OPTION 2 - CONTINUE DEVELOPING THE CURRENT FEDORA DOC That's one approach. Let the community vote with their contributions. If the User Guide is useful, volunteers will continue to update it and translate it into even more languages. Overall, it helps with the change in license from OPL to Creative Commons. OPTION 3 - DO BOTH There's no reason we can't do both. Bottom line: It's a Fedora Doc community decision. > I would bring this up at a FDSCo meeting, but I've been unable to make > them lately. I'd appreciate some guidance on the list. The FDP meetings are currently being held at my local time of 4 am, so I can't attend them. :-( Slightly off-topic: I have always seen one of the main purposes of the Docs Project as being the production of world-class release notes. This is why I am trying to learn Publican so I can help with this effort. Best Regards, John Babich Volunteer, Fedora Project -------------- next part -------------- An HTML attachment was scrubbed... URL: From danielsmw at gmail.com Thu Jul 9 17:00:36 2009 From: danielsmw at gmail.com (Matthew Daniels) Date: Thu, 09 Jul 2009 13:00:36 -0400 Subject: User Guide update In-Reply-To: <1247157732.2659.1.camel@echristensen.tkctech.com> References: <4A5615FB.1060106@gmail.com> <1247157732.2659.1.camel@echristensen.tkctech.com> Message-ID: <4A562234.1070801@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric Christensen wrote: > On Thu, 2009-07-09 at 12:08 -0400, Matthew Daniels wrote: Would > striking a lot of specific, step-by-step tasks from the UG offend > any previous content writers? Is this the direction to go? What > kind of step-by-step tasks are you proposing? Eric I would propose removing items which should be included in documentation already shipped with software components. Examples of some things I'd like to trim or rewrite are thing like the current OOo section[1], or the description of KMyMoney[2]. These are things that can either be found shipped with the programs or that are too common sense to include in documentation (like explaining what your options will be if you click on the "Edit" menu). These kind of small details are also extremely version sensitive; these things could even change between Fedora releases, meaning that the guide becomes inaccurate. Examples of the type of "generalized" information I'd rather see kept are things that orient the user in the way Fedora is organized. Comparing the GNOME desktop to Microsoft Windows would fit here; also, explaining things like how and why one mounts/unmounts volumes. Troubleshooting common problems should also be included, as well at meta-information. By meta-information, I mean things like Package Installation instructions -- there is documentation for that, but so much of the User Guide depends on that process that I feel it needs to be included anyway. - -- Matthew [1] https://fedoraproject.org/wiki/User_Guide_-_Office_Tools#OpenOffice.org_Writer [2] https://fedoraproject.org/wiki/User_Guide_-_Financial_Software#Using_KMyMoney -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpWIjMACgkQ8q6Smu6Jjuv7FwCcD6ATaJe4lWlsOQ3eTinBIT8b FScAnRXUDIViRM10IIoIw4Fo80iVsf1a =Tr8X -----END PGP SIGNATURE----- From danielsmw at gmail.com Thu Jul 9 17:09:05 2009 From: danielsmw at gmail.com (Matthew Daniels) Date: Thu, 09 Jul 2009 13:09:05 -0400 Subject: User Guide update In-Reply-To: References: <4A5615FB.1060106@gmail.com> Message-ID: <4A562431.3050806@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Babich wrote: > There's also the issue of trying to cover all the Desktop Managers. > F6 User Guide had only GNOME coverage and was severely criticised > for not covering KDE. The current User Guide includes KDE and XFCE > along with GNOME. Now, what about LXDE, my current desktop? I use Fluxbox, myself. Implied in what I suggested would be a kind of writing that helps the user understand the Linux model in a more general sense, so they would more easily be able to adapt what they learn from the guide to topics too numerous for us to cover. If we talk about DEs in general (example: how to I select the DE I log into? How do I install new ones? Where can I find documentation on other DEs?) as well as talking specifically about GNOME/KDE, then we offer the user more choice without _necessarily_ weighing them down with too much information. > OPTION 1 - CONTRIBUTE UPSTREAM ... OPTION 2 - CONTINUE DEVELOPING > THE CURRENT FEDORA DOC ... OPTION 3 - DO BOTH > > There's no reason we can't do both. > > Bottom line: It's a Fedora Doc community decision. The only reason we can't do both is because of manpower. I think reporting documentation errors upstream would be good, but this is something the user would be doing anyway if reading Mozilla's Firefox documentation instead of Fedora's Firefox documentation. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpWJDEACgkQ8q6Smu6JjuuTWgCcCkfiOWc8tEQ50+nIXCGfxs9J oZgAnRGIyAEGLXdW+RT7JR88SCNsMs+7 =fLJ7 -----END PGP SIGNATURE----- From r.landmann at redhat.com Fri Jul 10 00:06:52 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Fri, 10 Jul 2009 10:06:52 +1000 Subject: User Guide update In-Reply-To: <4A5615FB.1060106@gmail.com> References: <4A5615FB.1060106@gmail.com> Message-ID: <4A56861C.4090102@redhat.com> Some thoughts on the UG, based on what I saw while converting it to build in Publican and publishing it for the F11 release: A large part of the document is made up of listing the contents of the main menus of applications. The examples that Matthew pointed to in OpenOffice and KMyMoney are quite typical. As far as I can see, this material is pretty much useless to anybody. Anyone who wants to see what's offered under these menus is going to click on the menu, not look it up in documentation. Furthermore, as Matthew has already pointed out, most of this stuff is intuitive to anyone who has much experience with any recent, mainstream desktop on any platform, and is also a maintenance nightmare to keep up-to-date. Finally, the way that much of this has been written attempts to turn menu entries into connected English prose. Most of the time, this comes out OK, but my hat is off to those dedicated souls who have managed to translate the result into any other language! I strongly believe that all of this should go. Show no mercy. The User Guide really needs to be re-thought on a fundamental level and deliberately planned out. The key questions are "who do we envisage reading this book?" and "what do we think that they need to know about Fedora from it?" Off the top of my head (and all IMHO only): I envisage two main groups of people in the target audience: people who have emigrated from other operating systems (primarily Windows) and a smaller group of people who have never owned a computer before (in particular, I'm thinking of socially disadvantaged people who might have received a rebuilt PC with Fedora on it). To paraphrase an old retail maxim, nobody owns a computer to own a computer ? people own computers to do stuff with them. Documentation needs to remain task-oriented. So, what both groups that I named above need to know about Fedora is: * Some background knowledge about Fedora, and Linux in general, eg: * This is a totally different environment from Windows and Mac -- you can't expect software designed for those platforms to work on your computer, and need to be careful with hardware * Task -- so where do I get software from? * Task -- if I want to buy a printer, how do I know it will work with Linux? * Task -- how do I perform the tasks that I used to do on a Windows computer, or that people say I need to have Microsoft Word for? How do I access my old files? * Linux is very secure -- the viruses and spyware that are part of the Windows world won't trouble you here. * Task -- how do I make my computer safe from viruses and hackers? (All the tasks above will be covered later in the doc; for now, it's enough to touch on these questions and refer readers to the relevant sections) * Finding their way around the desktops -- this should cover all desktops that people in the target audiences are likely to encounter. From what I've seen, Xfce (and increasingly LXDE) are popular choices for old machines rebuilt by charities. For each desktop: * Task -- how do I know which of these applies to me? (screenshots are vital here) * Task -- how do I turn off/restart my computer? (I've seen even experienced Windows users baffled by this in GNOME...) * Task -- how do I find the programs? * Task -- how do I get new programs if I can't buy them at the store? * Task -- how do I find my documents? * Task -- how do I personalise my desktop -- change the wallpaper? change the screen saver? (This is very important to many people, I think it helps them "own" the machine) * Task -- how do I transfer a document to or from this floppy disk/CD/Flash drive? (and you might be surprised at how many people are still using floppies in these audiences) * Task -- how do I keep my computer up-to-date? How do I upgrade to a new version of Fedora (and will I have to pay for this?) * Performing common tasks on the desktops (the stated raison d'etre for this book) -- again, this should cover each desktop that people in the target audiences are likely to encounter, and each desktop should have a separate section. Applications that are widely used on multiple desktops (for example, OpenOffice) should appear under each desktop -- common text can be xi:included into multiple sections of the document. For each task, only the default application for that task on that desktop needs to be discussed, plus any really widely-used application that's likely to show up on multiple desktops (OpenOffice, Firefox, and Thunderbird are the only ones that spring to mind). I think that the general categories identified in the User Guide in its current form are pretty good, and for most applications, I think there's at least some usable text in the doc already. The emphasis here is very definitely not to be comprehensive, but to point out major features and tell users where to find more in-depth help. In every case, the task is similar, for example: * Task -- how do I write/edit/print documents? * Task -- how do I transfer music to my MP3 player? * Task -- how do I view/edit/print my digital photos? * Task -- how do I access the web? * Task -- how do I get/send email? * Task -- where do I find games? All of the above is only a rough outline straight off the top of my head; it's not meant to be anything more than a starting point for a content definition. I agree with John that it would be nice to engage with upstream communities for some of this. For example, when we describe a particular desktop, I think we really should try to develop some common text that would be useful for other distros too. However, I think there's value in a distinctly Fedora User Guide -- that branding is valuable, and it imparts confidence to users that "yes, this book applies to me and to my computer". So while (for example), we might share a general description of the KDE desktop with/from the upstream community, a KDE User Guide will no doubt go into far more detail than we would ever want to. Finally, I hope it goes without saying that none of the above is intended to detract in any way from the hard work and dedication that people have put into developing the User Guide. With a little more direction and definition, the genuinely good and useful content that already exists in the guide can be brought into focus and become useful to people starting out in Fedora. Cheers Rudi From eric at christensenplace.us Fri Jul 10 00:23:57 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 09 Jul 2009 20:23:57 -0400 Subject: User Guide update In-Reply-To: <4A562234.1070801@gmail.com> References: <4A5615FB.1060106@gmail.com> <1247157732.2659.1.camel@echristensen.tkctech.com> <4A562234.1070801@gmail.com> Message-ID: <1247185437.2478.6.camel@thunder.christensenplace.us> On Thu, 2009-07-09 at 13:00 -0400, Matthew Daniels wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Eric Christensen wrote: > > On Thu, 2009-07-09 at 12:08 -0400, Matthew Daniels wrote: Would > > striking a lot of specific, step-by-step tasks from the UG offend > > any previous content writers? Is this the direction to go? What > > kind of step-by-step tasks are you proposing? Eric > > I would propose removing items which should be included in > documentation already shipped with software components. Examples of > some things I'd like to trim or rewrite are thing like the current OOo > section[1], or the description of KMyMoney[2]. These are things that > can either be found shipped with the programs or that are too common > sense to include in documentation (like explaining what your options > will be if you click on the "Edit" menu). These kind of small details > are also extremely version sensitive; these things could even change > between Fedora releases, meaning that the guide becomes inaccurate. > > Examples of the type of "generalized" information I'd rather see kept > are things that orient the user in the way Fedora is organized. > Comparing the GNOME desktop to Microsoft Windows would fit here; also, > explaining things like how and why one mounts/unmounts volumes. > Troubleshooting common problems should also be included, as well at > meta-information. By meta-information, I mean things like Package > Installation instructions -- there is documentation for that, but so > much of the User Guide depends on that process that I feel it needs to > be included anyway. > > - -- Matthew > > [1] > https://fedoraproject.org/wiki/User_Guide_-_Office_Tools#OpenOffice.org_Writer > [2] > https://fedoraproject.org/wiki/User_Guide_-_Financial_Software#Using_KMyMoney > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.10 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkpWIjMACgkQ8q6Smu6Jjuv7FwCcD6ATaJe4lWlsOQ3eTinBIT8b > FScAnRXUDIViRM10IIoIw4Fo80iVsf1a > =Tr8X > -----END PGP SIGNATURE----- > Yeah, I agree with not reinventing the wheel when it comes to reiterating what is already written elsewhere. Maybe a link to where they can read more? - Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From stickster at gmail.com Fri Jul 10 00:52:03 2009 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 9 Jul 2009 20:52:03 -0400 Subject: User Guide update In-Reply-To: <4A56861C.4090102@redhat.com> References: <4A5615FB.1060106@gmail.com> <4A56861C.4090102@redhat.com> Message-ID: <20090710005203.GI19273@localhost.localdomain> On Fri, Jul 10, 2009 at 10:06:52AM +1000, Ruediger Landmann wrote: > Some thoughts on the UG, based on what I saw while converting it to build > in Publican and publishing it for the F11 release: [...snip...] This is one of the best summaries I've seen about where the UG might go in the future to become an invaluable resource to users. Brilliant. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From bugzilla at redhat.com Fri Jul 10 00:54:09 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 9 Jul 2009 20:54:09 -0400 Subject: [Bug 508935] Need to move the Documentation Guide to the wiki In-Reply-To: References: Message-ID: <200907100054.n6A0s9Hg028516@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508935 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |DEFERRED --- Comment #3 from Eric Christensen 2009-07-09 20:54:08 EDT --- Okay. We'll hold this until Zikula gets going. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From danielsmw at gmail.com Fri Jul 10 01:10:53 2009 From: danielsmw at gmail.com (Matthew Daniels) Date: Thu, 09 Jul 2009 21:10:53 -0400 Subject: User Guide update In-Reply-To: <20090710005203.GI19273@localhost.localdomain> References: <4A5615FB.1060106@gmail.com> <4A56861C.4090102@redhat.com> <20090710005203.GI19273@localhost.localdomain> Message-ID: <4A56951D.4020001@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul W. Frields wrote: > On Fri, Jul 10, 2009 at 10:06:52AM +1000, Ruediger Landmann wrote: >> Some thoughts on the UG, based on what I saw while converting it to build >> in Publican and publishing it for the F11 release: > [...snip...] > > This is one of the best summaries I've seen about where the UG might > go in the future to become an invaluable resource to users. > Brilliant. I have to agree wholeheartedly. Incredible insights, Rudi. I didn't imagine I'd get such a thorough and well-thought-out response when I started this thread. Eric, I'm going to try to make it to the next FDSCo meeting Wednesday; if I get this on the agenda, can we dedicate some time to talking about it? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpWlR0ACgkQ8q6Smu6JjusJoQCeNvcxVzPY9obPF/mZdn1maLNa DPUAn3J2Ay3t05u2dgEfUjMcWAW7gpbQ =AqWq -----END PGP SIGNATURE----- From eric at christensenplace.us Fri Jul 10 02:03:49 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 09 Jul 2009 22:03:49 -0400 Subject: User Guide update In-Reply-To: <4A56951D.4020001@gmail.com> References: <4A5615FB.1060106@gmail.com> <4A56861C.4090102@redhat.com> <20090710005203.GI19273@localhost.localdomain> <4A56951D.4020001@gmail.com> Message-ID: <1247191429.2478.8.camel@thunder.christensenplace.us> On Thu, 2009-07-09 at 21:10 -0400, Matthew Daniels wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Paul W. Frields wrote: > > On Fri, Jul 10, 2009 at 10:06:52AM +1000, Ruediger Landmann wrote: > >> Some thoughts on the UG, based on what I saw while converting it to build > >> in Publican and publishing it for the F11 release: > > [...snip...] > > > > This is one of the best summaries I've seen about where the UG might > > go in the future to become an invaluable resource to users. > > Brilliant. > I have to agree wholeheartedly. Incredible insights, Rudi. I didn't > imagine I'd get such a thorough and well-thought-out response when I > started this thread. > > Eric, I'm going to try to make it to the next FDSCo meeting Wednesday; > if I get this on the agenda, can we dedicate some time to talking > about it? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.10 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkpWlR0ACgkQ8q6Smu6JjusJoQCeNvcxVzPY9obPF/mZdn1maLNa > DPUAn3J2Ay3t05u2dgEfUjMcWAW7gpbQ > =AqWq > -----END PGP SIGNATURE----- > You put it on the agenda and we'll discuss it. Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From bugzilla at redhat.com Fri Jul 10 04:45:41 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 10 Jul 2009 00:45:41 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907100445.n6A4jfqJ000891@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 505932, which changed state. Bug 505932 Summary: Review Request: zikula-module-crpTag - Simple Zikula component for tagging items, based on hooks https://bugzilla.redhat.com/show_bug.cgi?id=505932 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |NEXTRELEASE -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From wb8rcr at arrl.net Fri Jul 10 12:05:08 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Fri, 10 Jul 2009 08:05:08 -0400 Subject: RPM Guide and RPM Max Message-ID: <207B4B40D82E4BC68A319D06EBE12698@Aidan> At FUDcon, Florian Festi approached me about Docs updating the RPM Guide and the book, Maximum RPM, both of which have gotten a little stale. The RPM Guide was already on our radar, and Ben Cotton has taken point on getting that ready to be worked on. Maximum RPM is currently hosted at rpm.org, and does not appear to have been built with the old doc tools. There seem to be some specific dependencies on Fedora 8, so there will be a little work converting it to something more up to date. The other issue, though, is licensing. This probably won't be difficult to deal with but it is something that needs to be addressed. The current copyright holder is Red Hat. We will probably discuss this at an upcoming Docs Team meeting, but I did want to give everyone a heads-up that this is going on. We may also want to carry on some discussion on an rpm.org mailing list so that community is also aware of the effort. At this point not much has actually happened. Ben has moved the RPM Guide to git, but I don't think anything else has happened there, I have looked at the Maximum RPM sources and verified Florian's assessment that this isn't a straightforward build, and quaid is aware of the licensing issues. The RPM Guide is at: git.fedoraproject.org/rpmguide.git Maximum RPM is at rpm.org/git/max-rpm.git --McD From bcotton+fedora at gmail.com Fri Jul 10 12:31:42 2009 From: bcotton+fedora at gmail.com (Ben Cotton) Date: Fri, 10 Jul 2009 08:31:42 -0400 Subject: RPM Guide and RPM Max In-Reply-To: <207B4B40D82E4BC68A319D06EBE12698@Aidan> References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> Message-ID: <87f35b5e0907100531u55680715v8b183bef006670b2@mail.gmail.com> McD, You're right, apart from getting the RPM Guide into git last night, nothing has been done on it yet. When I tried to make it last night, I got some errors barfed at me that were apparently bad enough to prevent the creation of a PDF. I got an intro to DocBook/Publican from jsmith yesterday, so I feel reasonably well-equipped to get it figured out. BC On 7/10/09, John J. McDonough wrote: > At FUDcon, Florian Festi approached me about Docs updating the RPM Guide and > the book, Maximum RPM, both of which have gotten a little stale. The RPM > Guide was already on our radar, and Ben Cotton has taken point on getting > that ready to be worked on. > > Maximum RPM is currently hosted at rpm.org, and does not appear to have been > built with the old doc tools. There seem to be some specific dependencies > on Fedora 8, so there will be a little work converting it to something more > up to date. > > The other issue, though, is licensing. This probably won't be difficult to > deal with but it is something that needs to be addressed. The current > copyright holder is Red Hat. > > We will probably discuss this at an upcoming Docs Team meeting, but I did > want to give everyone a heads-up that this is going on. We may also want to > carry on some discussion on an rpm.org mailing list so that community is > also aware of the effort. > > At this point not much has actually happened. Ben has moved the RPM Guide > to git, but I don't think anything else has happened there, I have looked at > the Maximum RPM sources and verified Florian's assessment that this isn't a > straightforward build, and quaid is aware of the licensing issues. > > The RPM Guide is at: > git.fedoraproject.org/rpmguide.git > > Maximum RPM is at > rpm.org/git/max-rpm.git > > --McD > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > -- Sent from my mobile device Ben Cotton From wb8rcr at arrl.net Fri Jul 10 12:36:56 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Fri, 10 Jul 2009 08:36:56 -0400 Subject: RPM Guide and RPM Max References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> <87f35b5e0907100531u55680715v8b183bef006670b2@mail.gmail.com> Message-ID: <01CB48B02F0745AB8EB9467548008999@Aidan> ----- Original Message ----- From: "Ben Cotton" To: "For participants of the Documentation Project" ; "Florian Festi" Sent: Friday, July 10, 2009 8:31 AM Subject: Re: RPM Guide and RPM Max > McD, > > You're right, apart from getting the RPM Guide into git last night, > nothing has been done on it yet. When I tried to make it last night, > I got some errors barfed at me that were apparently bad enough to > prevent the creation of a PDF. I think there is an issue with creating pdf's with the current version of Publican. You might try make-html-en-US --McD From stickster at gmail.com Fri Jul 10 13:12:35 2009 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 10 Jul 2009 09:12:35 -0400 Subject: RPM Guide and RPM Max In-Reply-To: <207B4B40D82E4BC68A319D06EBE12698@Aidan> References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> Message-ID: <20090710131235.GC28530@localhost.localdomain> On Fri, Jul 10, 2009 at 08:05:08AM -0400, John J. McDonough wrote: > At FUDcon, Florian Festi approached me about Docs updating the RPM Guide > and the book, Maximum RPM, both of which have gotten a little stale. The > RPM Guide was already on our radar, and Ben Cotton has taken point on > getting that ready to be worked on. > > Maximum RPM is currently hosted at rpm.org, and does not appear to have > been built with the old doc tools. There seem to be some specific > dependencies on Fedora 8, so there will be a little work converting it to > something more up to date. > > The other issue, though, is licensing. This probably won't be difficult > to deal with but it is something that needs to be addressed. The current > copyright holder is Red Hat. Do we need to update both, or is it sufficient to get all coverage into the new RPM Guide, and make that our focus? As for licensing: * Maximum RPM is under OPL + exception (no paper publication without express permission). It has one author, Ed Bailey, and the copyright is owned by Red Hat, probably making re-licensing easy. (We ask, and Legal approves, maybe following a discussion, likely brief and simple, with Red Hat Content Services.) * RPM Guide is under OPL with no exceptions. It has a single author, Eric Foster-Johnson, whom we'd need to ask to relicense the material. > We will probably discuss this at an upcoming Docs Team meeting, but I did > want to give everyone a heads-up that this is going on. We may also want > to carry on some discussion on an rpm.org mailing list so that community > is also aware of the effort. > > At this point not much has actually happened. Ben has moved the RPM Guide > to git, but I don't think anything else has happened there, I have looked > at the Maximum RPM sources and verified Florian's assessment that this > isn't a straightforward build, and quaid is aware of the licensing issues. > > The RPM Guide is at: > git.fedoraproject.org/rpmguide.git Did you make this into a git repo using the instructions provided on the wiki? There's a one line log, which looks wrong to me. Since we're just starting out, I would recommend you blow away this git repo and replace it with a fresh one, done by following these instructions: https://fedoraproject.org/wiki/Importing_Docs_CVS_modules_to_git > Maximum RPM is at > rpm.org/git/max-rpm.git -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From wb8rcr at arrl.net Fri Jul 10 14:14:23 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Fri, 10 Jul 2009 10:14:23 -0400 Subject: RPM Guide and RPM Max References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> <4A574210.40108@redhat.com> Message-ID: <496A9B628C0B4FE1BEED77E77E84745B@Aidan> ----- Original Message ----- From: "Panu Matilainen" To: "Florian Festi" Cc: "John J. McDonough" ; "For participants of the Documentation Project" Sent: Friday, July 10, 2009 9:33 AM Subject: Re: RPM Guide and RPM Max > Indeed, there's little point in wasting scarce resources on trying to keep > two books up to date, better concentrate on just one. The RPM Guide is far > far closer to being up-to-date than Max-RPM which *should* mean it's far > easier to update to match current RPM versions. I think the question that needs to be asked is how much value does Maximum RPM add, and is it appropriate or necessary to include that in the RPM Guide. I haven't studied either well enough to be in a position to even offer an opinion. But, that is additional fodder for the discussion. --McD From bcotton+fedora at gmail.com Fri Jul 10 15:27:32 2009 From: bcotton+fedora at gmail.com (Ben Cotton) Date: Fri, 10 Jul 2009 11:27:32 -0400 Subject: RPM Guide and RPM Max In-Reply-To: <20090710131235.GC28530@localhost.localdomain> References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> <20090710131235.GC28530@localhost.localdomain> Message-ID: <87f35b5e0907100827o65fefbd5le317579491c4071a@mail.gmail.com> On Fri, Jul 10, 2009 at 9:12 AM, Paul W. Frields wrote: > Did you make this into a git repo using the instructions provided on > the wiki? ?There's a one line log, which looks wrong to me. ?Since > we're just starting out, I would recommend you blow away this git repo > and replace it with a fresh one, done by following these instructions: > > https://fedoraproject.org/wiki/Importing_Docs_CVS_modules_to_git > With help from Paul and Ricky, the RPM Guide has been re-uploaded to git, correctly this time. -- Ben Cotton From fabhoneydew at gmail.com Fri Jul 10 15:30:06 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Fri, 10 Jul 2009 21:00:06 +0530 Subject: Need Feedback on HOWTO wiki created by /me. Message-ID: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> Hi, Last week I made a wiki page on HOWTO Install Fedora 11. The page is an effort to help users with the installation of Fedora 11. I used VirtualBox to install Fedora 11 virtually on my laptop, and, in the process, took screenshots of every step that I encountered and wrote down the installation procedure in steps. The wiki page is available here [1]. This is the first time I have created such a HOWTO or guide and I may have missed out on something. I would be glad to receive any comments, criticism, etc. which would help me to improve this wiki and in my future ventures. [1] http://www.burntomlette.in/index.php?title=Installing_fedora11 Thanks, Regards, Kishan Goyal. From fabhoneydew at gmail.com Fri Jul 10 15:35:59 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Fri, 10 Jul 2009 21:05:59 +0530 Subject: Need Feedback on HOWTO wiki created by /me. Message-ID: <9f45b2730907100835n3acb156dse0deae7ba290b5a7@mail.gmail.com> Hi, Last week I made a wiki page on HOWTO Install Fedora 11. The page is an effort to help users with the installation of Fedora 11. I used VirtualBox to install Fedora 11 virtually on my laptop, and, in the process, took screenshots of every step that I encountered and wrote down the installation procedure in steps. The wiki page is available here [1]. This is the first time I have created such a HOWTO or guide and I may have missed out on something. I would be glad to receive any comments, criticism, etc. which would help me to improve this wiki and in my future ventures. [1] http://www.burntomlette.in/index.php?title=Installing_fedora11 Thanks, Regards, Kishan Goyal. From eric at christensenplace.us Fri Jul 10 15:45:52 2009 From: eric at christensenplace.us (Eric Christensen) Date: Fri, 10 Jul 2009 11:45:52 -0400 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> Message-ID: <1247240752.2520.28.camel@thunder.christensenplace.us> On Fri, 2009-07-10 at 21:00 +0530, kishan goyal wrote: > Hi, > Last week I made a wiki page on HOWTO Install Fedora 11. The page is > an effort to help users with the installation of Fedora 11. > I used VirtualBox to install Fedora 11 virtually on my laptop, and, in > the process, took screenshots of every step that I encountered and > wrote down the installation procedure in steps. The wiki page is > available here [1]. > > This is the first time I have created such a HOWTO or guide and I may > have missed out on something. I would be glad to receive any comments, > criticism, etc. which would help me to improve this wiki and in my > future ventures. > > > [1] http://www.burntomlette.in/index.php?title=Installing_fedora11 > > > Thanks, > Regards, > Kishan Goyal. > Kishan, Have you looked at our Installation Guide[1]? I would hate for you to have to reinvent the wheel. Maybe you could work with the team on this guide? [1] http://docs.fedoraproject.org/install-guide/f11/ -- Thanks, Eric Christensen Fedora Docs Project Lead Fedora Talk: 5102043 Phone: 919-424-0063 x 5102043 E-Mail: sparks at fedoraproject.org SIP: sparks at talk.fedoraproject.org IRC: Sparks on freenode.net GPG Fingerprint: CA02 4ACA EB6C 1A76 F0D6 1127 7D04 D240 BD0C 14C1 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From fabhoneydew at gmail.com Fri Jul 10 16:03:02 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Fri, 10 Jul 2009 21:33:02 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <1247240752.2520.28.camel@thunder.christensenplace.us> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <1247240752.2520.28.camel@thunder.christensenplace.us> Message-ID: <9f45b2730907100903i4e788649u51e63d07a2c37927@mail.gmail.com> On Fri, Jul 10, 2009 at 9:15 PM, Eric Christensen wrote: > Kishan, > > Have you looked at our Installation Guide[1]? No, I had looked at this guide. >?I would hate for you to have to reinvent the wheel. ?Maybe you could work with > the team on this > guide? Yes, I am looking forward to working with the team on this guide. Actually, that wiki was a short guide for my classmates. And in the process, I learnt a lot about writing a wiki page. I was just looking for some comments on how I could improve my work. > > [1] http://docs.fedoraproject.org/install-guide/f11/ > Thanks, Regards, Kishan Goyal From stickster at gmail.com Fri Jul 10 16:04:49 2009 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 10 Jul 2009 12:04:49 -0400 Subject: RPM Guide and RPM Max In-Reply-To: <87f35b5e0907100827o65fefbd5le317579491c4071a@mail.gmail.com> References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> <20090710131235.GC28530@localhost.localdomain> <87f35b5e0907100827o65fefbd5le317579491c4071a@mail.gmail.com> Message-ID: <20090710160449.GO28530@localhost.localdomain> On Fri, Jul 10, 2009 at 11:27:32AM -0400, Ben Cotton wrote: > On Fri, Jul 10, 2009 at 9:12 AM, Paul W. Frields wrote: > > > Did you make this into a git repo using the instructions provided on > > the wiki? ?There's a one line log, which looks wrong to me. ?Since > > we're just starting out, I would recommend you blow away this git repo > > and replace it with a fresh one, done by following these instructions: > > > > https://fedoraproject.org/wiki/Importing_Docs_CVS_modules_to_git > > > With help from Paul and Ricky, the RPM Guide has been re-uploaded to > git, correctly this time. We didn't have to help much -- awesome job Ben! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From ricky at fedoraproject.org Fri Jul 10 16:57:42 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Fri, 10 Jul 2009 12:57:42 -0400 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <1247240752.2520.28.camel@thunder.christensenplace.us> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <1247240752.2520.28.camel@thunder.christensenplace.us> Message-ID: <20090710165742.GF3196@alpha.rzhou.org> On 2009-07-10 11:45:52 AM, Eric Christensen wrote: > Have you looked at our Installation Guide[1]? I would hate for you to > have to reinvent the wheel. Maybe you could work with the team on this > guide? The difference between the type of documentation that Kishan made and our official docs is something that I've been thinking about lately. While there definitely is a place for a comprehensive install guide that covers every single installation case, perhaps it'd be nice to have a shorter, less intimidating version that goes through the defaults that most brand new users would go through. As an example of what I mean, openSUSE has some friendly, screenshot-filled install guides that they link off of their download page: http://en.opensuse.org/INSTALL_Local http://en.opensuse.org/Installation/11.1_Live_CD one striking fact that I noticed is that even with those tall screenshots, both of those pages are not much larger than just the table of contents page of our install guide (http://docs.fedoraproject.org/install-guide/f11/en-US/html/). Sure, those pages don't cover the install process even nearly as completely as our docs do, but from the perspective of a new user who just wants to go with the defaults and get to a working system, that style of documentation seems *really* nice. I'm very interested to hear what you guys think about that - would Zikula perhaps make it any easier or nicer to manage smaller documents like these? Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From fabhoneydew at gmail.com Fri Jul 10 17:09:58 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Fri, 10 Jul 2009 22:39:58 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <20090710165742.GF3196@alpha.rzhou.org> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <1247240752.2520.28.camel@thunder.christensenplace.us> <20090710165742.GF3196@alpha.rzhou.org> Message-ID: <9f45b2730907101009x18b7a491y2e55ded93fbe8773@mail.gmail.com> On Fri, Jul 10, 2009 at 10:27 PM, Ricky Zhou wrote: > The difference between the type of documentation that Kishan made and > our official docs is something that I've been thinking about lately. > While there definitely is a place for a comprehensive install guide > that covers every single installation case, perhaps it'd be nice to have > a shorter, less intimidating version that goes through the defaults that > most brand new users would go through. Yes, a very good point brought up. A new user just wants *simple* steps that would guide him through the installation process. > > As an example of what I mean, openSUSE has some friendly, > screenshot-filled install guides that they link off of their download > page: > > http://en.opensuse.org/INSTALL_Local > http://en.opensuse.org/Installation/11.1_Live_CD > Does something similar to this exist in Fedora? Having such small guides would be very good for new users. > one striking fact that I noticed is that even with those tall > screenshots, both of those pages are not much larger than just the table > of contents page of our install guide > (http://docs.fedoraproject.org/install-guide/f11/en-US/html/). > > Sure, those pages don't cover the install process even nearly as > completely as our docs do, but from the perspective of a new user who > just wants to go with the defaults and get to a working system, that > style of documentation seems *really* nice. > > I'm very interested to hear what you guys think about that - would > Zikula perhaps make it any easier or nicer to manage smaller documents > like these? Zikula... I need to get googling... for not having followed the activites of the team of late. Regards, Kishan Goyal. From eric at christensenplace.us Fri Jul 10 17:13:18 2009 From: eric at christensenplace.us (Eric Christensen) Date: Fri, 10 Jul 2009 13:13:18 -0400 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <9f45b2730907101009x18b7a491y2e55ded93fbe8773@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <1247240752.2520.28.camel@thunder.christensenplace.us> <20090710165742.GF3196@alpha.rzhou.org> <9f45b2730907101009x18b7a491y2e55ded93fbe8773@mail.gmail.com> Message-ID: <1247245998.2520.35.camel@thunder.christensenplace.us> On Fri, 2009-07-10 at 22:39 +0530, kishan goyal wrote: > On Fri, Jul 10, 2009 at 10:27 PM, Ricky Zhou wrote: > > > The difference between the type of documentation that Kishan made and > > our official docs is something that I've been thinking about lately. > > While there definitely is a place for a comprehensive install guide > > that covers every single installation case, perhaps it'd be nice to have > > a shorter, less intimidating version that goes through the defaults that > > most brand new users would go through. > > Yes, a very good point brought up. A new user just wants *simple* > steps that would guide him through the installation process. > > > > As an example of what I mean, openSUSE has some friendly, > > screenshot-filled install guides that they link off of their download > > page: > > > > http://en.opensuse.org/INSTALL_Local > > http://en.opensuse.org/Installation/11.1_Live_CD > > > > Does something similar to this exist in Fedora? Having such small > guides would be very good for new users. A quick start guide... Hmmm... > > > one striking fact that I noticed is that even with those tall > > screenshots, both of those pages are not much larger than just the table > > of contents page of our install guide > > (http://docs.fedoraproject.org/install-guide/f11/en-US/html/). > > > > Sure, those pages don't cover the install process even nearly as > > completely as our docs do, but from the perspective of a new user who > > just wants to go with the defaults and get to a working system, that > > style of documentation seems *really* nice. > > > > I'm very interested to hear what you guys think about that - would > > Zikula perhaps make it any easier or nicer to manage smaller documents > > like these? > > Zikula... I need to get googling... for not having followed the > activites of the team of late. Zikula is our new CMS solution. > > Regards, > Kishan Goyal. > --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From bugzilla at redhat.com Fri Jul 10 20:46:18 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 10 Jul 2009 16:46:18 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907102046.n6AKkImx018717@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 LukasHetzi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luhe at gmx.at -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From a.mani.cms at gmail.com Fri Jul 10 23:14:57 2009 From: a.mani.cms at gmail.com (Mani A) Date: Sat, 11 Jul 2009 04:44:57 +0530 Subject: User Guide update Message-ID: <78323d480907101614u346b7e4fn6224b512ba6d1760@mail.gmail.com> "Paul W. Frields" wrote: > On Fri, Jul 10, 2009 at 10:06:52AM +1000, Ruediger Landmann wrote: >> Some thoughts on the UG, based on what I saw while converting it to build >> in Publican and publishing it for the F11 release: > [...snip...] > > This is one of the best summaries I've seen about where the UG might > go in the future to become an invaluable resource to users. > Brilliant. I think we should turn it into a UG specification sheet and put it up on the wiki. Of course many points can be added. Other questions: Should the Live CD install and DVD install have different user guides? Can user guides be made to depend on the specific install choices? I think it makes sense Best A. Mani -- A. Mani ASL, CLC, AMS, CMS http://amani.topcities.com http://www.logicamani.co.cc From bugzilla at redhat.com Sun Jul 12 00:15:19 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sat, 11 Jul 2009 20:15:19 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907120015.n6C0FJr1016283@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |510881 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From foss.mailinglists at gmail.com Sun Jul 12 14:32:12 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Sun, 12 Jul 2009 20:02:12 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> Message-ID: <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> On Fri, Jul 10, 2009 at 9:00 PM, kishan goyal wrote: > Last week I made a wiki page on HOWTO Install Fedora 11. The page is > an effort to help users with the installation of Fedora 11. > I used VirtualBox to install Fedora 11 virtually on my laptop, and, in > the process, took screenshots of every step that I encountered and > wrote down the installation procedure in steps. The wiki page is > available here [1]. Nice quick start. Would it be possible for you to: - have it as a page within the Fedora wiki ? - make a PDF / print-ready version available ? - investigate how to make the content available as translation source files so as to enable ready translation etc ~sankarshan -- http://www.gutenberg.net - Fine literature digitally re-published http://www.plos.org - Public Library of Science http://www.creativecommons.org - Flexible copyright for creative work From fabhoneydew at gmail.com Sun Jul 12 15:32:25 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Sun, 12 Jul 2009 21:02:25 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> Message-ID: <9f45b2730907120832n72db63b5ud35fb7c2cabd7fee@mail.gmail.com> On Sun, Jul 12, 2009 at 8:02 PM, sankarshan wrote: > > Nice quick start. Would it be possible for you to: > > - have it as a page within the Fedora wiki ? okay. will do so and provide the link in this thread. > - make a PDF / print-ready version available ? that would not be a problem. will make a pdf. > - investigate how to make the content available as translation source > files so as to enable ready translation etc The images have been uploaded to [1]. Translation has already begun. I have begun translating the wiki to Hindi [2] Rtnpro and Meejan are working on the bengali one. [3] [1] http://www.burntomlette.in [2] http://www.burntomlette.in/index.php?title=Installing_fedora11_hindi [3] http://www.burntomlette.in/index.php?title=Installing_fedora11_bengali Regards, Kishan Goyal. From foss.mailinglists at gmail.com Sun Jul 12 15:46:39 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Sun, 12 Jul 2009 21:16:39 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <9f45b2730907120832n72db63b5ud35fb7c2cabd7fee@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> <9f45b2730907120832n72db63b5ud35fb7c2cabd7fee@mail.gmail.com> Message-ID: <35586fc00907120846p7a36f81cjaf3fc2bcc158b923@mail.gmail.com> On Sun, Jul 12, 2009 at 9:02 PM, kishan goyal wrote: >> - investigate how to make the content available as translation source >> files so as to enable ready translation etc > > The images have been uploaded to [1]. > Translation has already begun. > I have begun translating the wiki to Hindi [2] > Rtnpro and Meejan are working on the bengali one. [3] For the local language translations, please try and use the local language interface too. And, please do take time to inform the folks maintaining the languages (in Fedora) so as to let them run an eye over the document. The Bengali one has some errors (generated by typing wrongly) and, they need to be fixed. I fear we are deviating a bit from the intent of this list so, I'll keep an eye on the docs. > [1] http://www.burntomlette.in > [2] http://www.burntomlette.in/index.php?title=Installing_fedora11_hindi > [3] http://www.burntomlette.in/index.php?title=Installing_fedora11_bengali -- http://www.gutenberg.net - Fine literature digitally re-published http://www.plos.org - Public Library of Science http://www.creativecommons.org - Flexible copyright for creative work From bugzilla at redhat.com Sun Jul 12 16:47:52 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 12 Jul 2009 12:47:52 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907121647.n6CGlq0S021143@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 510881, which changed state. Bug 510881 Summary: Review Request: php-LightweightPicasaAPI - A lightweight API for Picasa in PHP https://bugzilla.redhat.com/show_bug.cgi?id=510881 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |DUPLICATE -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From david.nalley at fedoraproject.org Sun Jul 12 20:06:40 2009 From: david.nalley at fedoraproject.org (David Nalley) Date: Sun, 12 Jul 2009 16:06:40 -0400 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> Message-ID: On Fri, Jul 10, 2009 at 11:30 AM, kishan goyal wrote: > Hi, > Last week I made a wiki page on HOWTO Install Fedora 11. The page is > an effort to help users with the installation of Fedora 11. > I used VirtualBox to install Fedora 11 virtually on my laptop, and, in > the process, took screenshots of every step that I encountered and > wrote down the installation procedure in steps. The wiki page is > available here [1]. > > This is the first time I have created such a HOWTO or guide and I may > have missed out on something. I would be glad to receive any comments, > criticism, etc. which would help me to improve this wiki and in my > future ventures. > > > [1] http://www.burntomlette.in/index.php?title=Installing_fedora11 > > > Thanks, > Regards, > Kishan Goyal. > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > Hi Kishan - Rudi and I have actually talked about needing to have a more concise - 'here is how you install fedora' document', akin to the one page release notes, and keep the 'install guide' as the complete reference addition. (esp now that it's almost 300 pages). We'd love to have help in working on this. If you want to start moving stuff to the wiki that would be welcome. I also enjoyed your 'how to setup Sahana' doc and would like to see that on the wiki as well. From sundaram at fedoraproject.org Sun Jul 12 20:18:43 2009 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Mon, 13 Jul 2009 01:48:43 +0530 Subject: RPM Guide and RPM Max In-Reply-To: <496A9B628C0B4FE1BEED77E77E84745B@Aidan> References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> <4A574210.40108@redhat.com> <496A9B628C0B4FE1BEED77E77E84745B@Aidan> Message-ID: <4A5A4523.6000706@fedoraproject.org> On 07/10/2009 07:44 PM, John J. McDonough wrote: > I think the question that needs to be asked is how much value does > Maximum RPM add, and is it appropriate or necessary to include that in > the RPM Guide. I haven't studied either well enough to be in a position > to even offer an opinion. > > But, that is additional fodder for the discussion. While doing this, might want to keep in mind that RPM and the tools around RPM has changed quite a bit rendering a number of instructions complete obsolete and even misleading in the old docs. The setting of buildroot by RPM itself, groups is now optional and so on. A document which is more up2date but also much shorter is at http://fedoraproject.org/wiki/How_to_create_an_RPM_package While merging in content together into a single guide, make sure it reflects the current latest information. Rahul From r.landmann at redhat.com Sun Jul 12 22:40:10 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 13 Jul 2009 08:40:10 +1000 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> Message-ID: <4A5A664A.6090109@redhat.com> On 07/13/2009 06:06 AM, David Nalley wrote: > Rudi and I have actually talked about needing to have a more concise - > 'here is how you install fedora' document', akin to the one page > release notes, and keep the 'install guide' as the complete reference > addition. (esp now that it's almost 300 pages). We'd love to have help > in working on this. > > Absolutely! We noted the need for this in the lead up to Fedora 11 but didn't have time to make it happen. We'll definitely have one for Fedora 12, and we'd love to have you on board, Kishan. The only "gotcha" I'll point out at this stage is that as far as is possible, the new guide should be built from chunks of XML that already exist in the Installation Guide (and perhaps the Live CD documentation). Sharing "code" between the full Installation Guide and the "Quick" guide has the following advantages: 1. The chunks taken from existing documentation will already be translated into a large number of languages (the IG is already partially translated into around 36 languages) 2. We will only have to maintain the same step in one place (for example, if we need to change something about keyboard selection in the IG, we can then just copy that changed paragraph into the Quick guide) 3. Any maintenace changes that we make (from step 2 above) will only need to be translated once, either in the "Full" guide or the "Quick" guide, and we can copy the translation from one book to the other and it will still work. I'll pull something like this together in the next couple of days -- that will allow anyone who's interested in helping to identify and work on any extra text that we need to link everything together. What should we call this book? I'm thinking one of the following permutations -- * Fedora 12 Quick Installation Guide * Fedora 12 Installation Quick Start Guide * Fedora 12 Quick Start Installation Guide Any preferences? Cheers Rudi From eric at christensenplace.us Mon Jul 13 01:18:33 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sun, 12 Jul 2009 21:18:33 -0400 Subject: User Guide update In-Reply-To: <78323d480907101614u346b7e4fn6224b512ba6d1760@mail.gmail.com> References: <78323d480907101614u346b7e4fn6224b512ba6d1760@mail.gmail.com> Message-ID: <1247447913.2476.4.camel@thunder.christensenplace.us> On Sat, 2009-07-11 at 04:44 +0530, Mani A wrote: > Other questions: > > Should the Live CD install and DVD install have different user guides? > Can user guides be made to depend on the specific install choices? > > I think it makes sense > > Best > > A. Mani The User Guides should probably refer to the Installation Guide for advice on installing from a Live CD or DVD or network install or... -- Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From r.landmann at redhat.com Mon Jul 13 01:47:01 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Mon, 13 Jul 2009 11:47:01 +1000 Subject: User Guide update In-Reply-To: <1247447913.2476.4.camel@thunder.christensenplace.us> References: <78323d480907101614u346b7e4fn6224b512ba6d1760@mail.gmail.com> <1247447913.2476.4.camel@thunder.christensenplace.us> Message-ID: <4A5A9215.7040302@redhat.com> On 07/13/2009 11:18 AM, Eric Christensen wrote: > The User Guides should probably refer to the Installation Guide for > advice on installing from a Live CD or DVD or network install or... > > Agreed. The User Guide should assume a working Fedora installation already. Moreover, given the main audiences that I imagine needing the UG most, the document should be written with the assumption that the person sitting at the computer did not install or configure Fedora (or know how to install Fedora, or even care about installing Fedora). Cheers Rudi From bugzilla at redhat.com Mon Jul 13 02:28:25 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 12 Jul 2009 22:28:25 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907130228.n6D2SP8H025509@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |510979 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From stickster at gmail.com Mon Jul 13 02:42:03 2009 From: stickster at gmail.com (Paul W. Frields) Date: Sun, 12 Jul 2009 22:42:03 -0400 Subject: Zikula progress Message-ID: <20090713024203.GD23439@localhost.localdomain> Sorry about my lag time on one of the modules I was assigned (mediashare, BZ 506038). Out of the three dependency libs, Looks like Nick has phpFlickr under control. I picked up my dropped ball on php-LightweightPicasaAPI this weekend (BZ 505942), and also packaged the last, phpSmug (BZ 510979). -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From bugzilla at redhat.com Mon Jul 13 03:07:24 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 12 Jul 2009 23:07:24 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907130307.n6D37OLm000690@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 505942, which changed state. Bug 505942 Summary: Review Request: php-LightweightPicasaAPI - A lightweight API for Picasa in PHP https://bugzilla.redhat.com/show_bug.cgi?id=505942 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |NEXTRELEASE -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From fabhoneydew at gmail.com Tue Jul 14 06:16:39 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Tue, 14 Jul 2009 11:46:39 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> Message-ID: <9f45b2730907132316i685b22e4wada06481331b300a@mail.gmail.com> On Mon, Jul 13, 2009 at 1:36 AM, David Nalley wrote: > Hi Kishan - > > Rudi and I have actually talked about needing to have a more concise - > 'here is how you install fedora' document', akin to the one page > release notes, and keep the 'install guide' as the complete reference > addition. (esp now that it's almost 300 pages). We'd love to have help > in working on this. It would be my pleasure to help in whatever way I can. > > If you want to start moving stuff to the wiki that would be welcome. Thank You. So, I suppose, I would create a page for this 'quick start' on the Fedoraproject wiki and mail the link. > I also enjoyed your 'how to setup Sahana' doc and would like to see > that on the wiki as well. Thanks a lot. Glad you liked it. okay. That page wo Regards, Kishan Goyal. From fabhoneydew at gmail.com Tue Jul 14 06:26:05 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Tue, 14 Jul 2009 11:56:05 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <4A5A664A.6090109@redhat.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <4A5A664A.6090109@redhat.com> Message-ID: <9f45b2730907132326g3d53473ai95c3783597cb64fa@mail.gmail.com> On Mon, Jul 13, 2009 at 4:10 AM, Ruediger Landmann wrote: > Absolutely! We noted the need for this in the lead up to Fedora 11 but > didn't have time to make it happen. We'll definitely have one for Fedora 12, > and we'd love to have you on board, Kishan. > Thank you. :) > The only "gotcha" I'll point out at this stage is that as far as is > possible, the new guide should be built from chunks of XML that already > exist in the Installation Guide (and perhaps the Live CD documentation). > Sharing "code" between the full Installation Guide and the "Quick" guide has > the following advantages: > > 1. The chunks taken from existing documentation will already be translated > into a large number of languages (the IG is already partially translated > into around 36 languages) > 2. We will only have to maintain the same step in one place (for example, if > we need to change something about keyboard selection in the IG, we can then > just copy that changed paragraph into the Quick guide) > 3. Any maintenace changes that we make (from step 2 above) will only need to > be translated once, either in the "Full" guide or the "Quick" guide, and we > can copy the translation from one book to the other and it will still work. > Yes, that would be very advantageous. > I'll pull something like this together in the next couple of days -- that > will allow anyone who's interested in helping to identify and work on any > extra text that we need to link everything together. > Thank you for doing that. That would be of much help. :) > What should we call this book? I'm thinking one of the following > permutations -- > > * Fedora 12 Quick Installation Guide > * Fedora 12 Installation Quick Start Guide > * Fedora 12 Quick Start Installation Guide > > Any preferences? > all the above names are fine. how would "Quick Start Fedora 12" be? Regards, Kishan Goyal. From nikoyoshio at gmail.com Tue Jul 14 15:30:48 2009 From: nikoyoshio at gmail.com (Niko Yoshio) Date: Tue, 14 Jul 2009 12:30:48 -0300 Subject: how can I help? Message-ID: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> Hi everyone, how can I contribute? where do I start? thanks From absolute3d86 at gmail.com Tue Jul 14 16:06:48 2009 From: absolute3d86 at gmail.com (Thomas Arici) Date: Tue, 14 Jul 2009 18:06:48 +0200 Subject: translation contribute Message-ID: <7552f5b70907140906yc40d02ct22be3f2c23967354@mail.gmail.com> Hello, i've just signed to fedora contib and i wanna start to help the fedora community with language translation (english to italian). How can i start it? thanks thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric at christensenplace.us Tue Jul 14 16:11:28 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 14 Jul 2009 12:11:28 -0400 Subject: New Proposal for Publican files Message-ID: I've written a proposal[1] for reviewing Publican documents. I'm looking for input, changes, and comments. [1] https://fedoraproject.org/wiki/Policy_for_reviewing_Publican_documents Thanks, Eric From wb8rcr at arrl.net Tue Jul 14 19:23:44 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Tue, 14 Jul 2009 15:23:44 -0400 Subject: how can I help? References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> Message-ID: <15B2519003F145F6B486334DF6970C57@Aidan> ----- Original Message ----- From: "Niko Yoshio" To: Sent: Tuesday, July 14, 2009 11:30 AM Subject: how can I help? > Hi everyone, > how can I contribute? > where do I start? Welcome Niko Well, there are a number of startup things you need to take care of, they are outlined at: https://fedoraproject.org/wiki/Joining_the_Docs_Project Basically, you need to sign up to this list (apparently, you already are), post a "self-introduction" to the list letting us know who you are and what you are comfortable with. You will need to apply for membership in the Docs group of the Fedora Account System, which means you need to join the Fedora Account System, aggree to the CLA, then apply for membership in the Docs group. Someone, probably Sparks or myself, will read your self-introduction and sponsor you for membership in the Docs group. You will also want a bugzilla account - if you already have one no need for another. As you get involved in projects you will want membership in a number of other groups, but the FAS Docs group is the key to all that. We are beginning the Fedora 12 cycle, so it is a good time to sign on. Members hang out on the freenode IRC channel #Fedora-Docs, and a lot of organization gets done there. We also have a meeting on #Fedora-Meeting at 0001Z Thursday morning (That is Wednesday evening U.S. time). You don't need to have gotten all the paperwork dealt with to join the IRC channels, so stop by and introduce yourself. Welcome aboard --McD From wb8rcr at arrl.net Tue Jul 14 19:26:16 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Tue, 14 Jul 2009 15:26:16 -0400 Subject: translation contribute References: <7552f5b70907140906yc40d02ct22be3f2c23967354@mail.gmail.com> Message-ID: <2A460F08AD494D3DB4ABB4BB29C25F82@Aidan> ----- Original Message ----- From: Thomas Arici To: fedora-docs-list at redhat.com Sent: Tuesday, July 14, 2009 12:06 PM Subject: translation contribute > Hello, i've just signed to fedora contib and i wanna start to > help the fedora community with language translation > (english to italian). How can i start it? Thomas Welcome, we certainly appreciate the help. Translators join the L10N group: https://www.redhat.com/mailman/listinfo/fedora-trans-list Translators work a little differently than the Docs group, so you will want to post over there and start to meet some of the folks on that list. --McD From eric at christensenplace.us Tue Jul 14 19:47:52 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 14 Jul 2009 15:47:52 -0400 Subject: Release Notes Meeting In-Reply-To: <1247009111.2310.35.camel@ericlaptop.christensenplace.us> References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> <20090707211840.GI2867@localhost.localdomain> <1247009111.2310.35.camel@ericlaptop.christensenplace.us> Message-ID: On Tue, Jul 7, 2009 at 19:25, Eric Christensen wrote: > On Tue, 2009-07-07 at 17:18 -0400, Paul W. Frields wrote: >> On Tue, Jul 07, 2009 at 04:50:40PM -0400, John J. McDonough wrote: >> > Since the web page makes no mention of time zone, is it safe to assume >> > that they are UTC? >> >> The app relies on the organizer to set the "use timezones" flag, then >> respondents indicate their timezone in their reply and the times are >> magically set up properly for local time. > > And the organizer has now activated the tz flag. > > Eric > Okay, we really didn't have a good match. I've added another week on to the whenisgood[1] so we can try again. [1] http://whenisgood.net/UbMSZS Eric From dlbewley at lib.ucdavis.edu Wed Jul 15 00:11:59 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 14 Jul 2009 17:11:59 -0700 Subject: bug in f11 relnotes Message-ID: <1247616719.9691.15.camel@tofu.lib.ucdavis.edu> It's not earth shattering, but I just noticed a bug in http://docs.fedoraproject.org/release-notes/f11/en-US/sect-Release_Notes-Virtualization.html This string: package is now obsoleted by pngqemu-kvm. Should read: package is now obsoleted by qemu. -- Dale Bewley From eric at christensenplace.us Wed Jul 15 00:37:03 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 14 Jul 2009 20:37:03 -0400 Subject: bug in f11 relnotes In-Reply-To: <1247616719.9691.15.camel@tofu.lib.ucdavis.edu> References: <1247616719.9691.15.camel@tofu.lib.ucdavis.edu> Message-ID: <1247618223.2593.13.camel@thunder.christensenplace.us> On Tue, 2009-07-14 at 17:11 -0700, Dale Bewley wrote: > It's not earth shattering, but I just noticed a bug in > http://docs.fedoraproject.org/release-notes/f11/en-US/sect-Release_Notes-Virtualization.html > > This string: > > package is now obsoleted by href="http://admin.fedoraproject.org/pkgdb/packages/name/qemu-kvm">pngqemu-kvm. > > Should read: > > package is now obsoleted by href="http://admin.fedoraproject.org/pkgdb/packages/name/qemu">qemu. > > -- > Dale Bewley > Hi Dale, Thanks for the information. Could you submit this as a bug in our Bugzilla[1], please? It would be most helpful. [1] https://bugzilla.redhat.com/enter_bug.cgi?component=release-notes&product=Fedora%20Documentation Thanks, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From irashadul at gmail.com Wed Jul 15 14:53:52 2009 From: irashadul at gmail.com (Rashadul Islam) Date: Wed, 15 Jul 2009 10:53:52 -0400 Subject: Self Introduction: Rashadul Islam In-Reply-To: <17fa59580907150740o6a983262ib3e0eae1415daa6d@mail.gmail.com> References: <17fa59580907150740o6a983262ib3e0eae1415daa6d@mail.gmail.com> Message-ID: <17fa59580907150753l14835099if42d2b83ba03bc70@mail.gmail.com> *Dear Fedora Documentation team: *As a beginner in Documentation team I would like to introduce myself as instructed. *While working as a FEDORA AMBASSADOR, I myself interested to be the part of Fedora Documentation team. Below is some details about me: Personal* Name: Rashadul Islam Web: https://fedoraproject.org/wiki/RashadulIslam * Questionnaires What other projects or writing have you worked on in the past? *1. I used to work as a Constitution writer for the associations at Concordia University, Montreal, Canada. 2. Work as a curriculum committee member to review, reedit, and writing the content of academic update of the course outlines. 3. Doing technical reports on several projects. 4. Very good knowledge in Engineering rules and related writing in technical field: specially Code of Ethics in Engineering in Canada (Federal and Provincial rules). 5. Researching artificial intelligence project myself on a topic. *What level and type of computer skills do you have? *I am a BSc in Computer Science Student and my specialty is on Software. I define myself Medium High on Computer Skills. *What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. *Programming Skills: Java, c++, SQL, c scripting Working as a Regional Ambassador for Fedora Project to maintain its wide marketing and local publicity in Montreal as well as in Canada. *What makes you an excellent match for the project? * While working as an Ambassador I would like to involve in documentation because it is related to my field of profession. Moreover, I want to apply my technical skill for Fedora and its documentation team for the advancement of Documentation team. * GPG KEYID and fingerprint* Fingerprint=CFB7 CAEC 157A 308A F9CE CE00 3620 8084 5557 BFAC GPG KEY: 5557BFAC Email: irashadul at gmail.com Thanking you in advance to give me the chance to work with Fedora Documentation team and help the team to lead the best. Sincerely, Rashadul Islam GPG KeyID: 5557BFAC Email: irashadul at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Wed Jul 15 18:46:41 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 14:46:41 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907151846.n6FIkfs1010213@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 505946, which changed state. Bug 505946 Summary: Review Request: zikula-module-menutree - Menutree allows to create multilevel, hierarchical (tree-like) menu https://bugzilla.redhat.com/show_bug.cgi?id=505946 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |CANTFIX -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From nikoyoshio at gmail.com Wed Jul 15 20:39:44 2009 From: nikoyoshio at gmail.com (Niko Yoshio) Date: Wed, 15 Jul 2009 17:39:44 -0300 Subject: how can I help? In-Reply-To: <15B2519003F145F6B486334DF6970C57@Aidan> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> Message-ID: <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> 2009/7/14 John J. McDonough : > > ----- Original Message ----- From: "Niko Yoshio" > To: > Sent: Tuesday, July 14, 2009 11:30 AM > Subject: how can I help? > > >> Hi everyone, >> how can I contribute? >> where do I start? > > Welcome Niko > > Well, there are a number of startup things you need to take care of, they > are outlined at: > > https://fedoraproject.org/wiki/Joining_the_Docs_Project > > Basically, you need to sign up to this list (apparently, you already are), > post a "self-introduction" to the list letting us know who you are and what > you are comfortable with. ?You will need to apply for membership in the Docs > group of the Fedora Account System, which means you need to join the Fedora > Account System, aggree to the CLA, then apply for membership in the Docs > group. ?Someone, probably Sparks or myself, will read your self-introduction > and sponsor you for membership in the Docs group. > > You will also want a bugzilla account - if you already have one no need for > another. ?As you get involved in projects you will want membership in a > number of other groups, but the FAS Docs group is the key to all that. > > We are beginning the Fedora 12 cycle, so it is a good time to sign on. > Members hang out on the freenode IRC channel #Fedora-Docs, and a lot of > organization gets done there. ?We also have a meeting on #Fedora-Meeting at > 0001Z Thursday morning (That is Wednesday evening U.S. time). ?You don't > need to have gotten all the paperwork dealt with to join the IRC channels, > so stop by and introduce yourself. > > Welcome aboard > > --McD > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list > Hi everyone, Well, the company where I work we use the mediawiki to documenting procedures, I have some experience in editing or creating articles, but I would document projects. It could also translate documents from English to Portuguese-Brazilian. The accounts are created (bugzilla and FAS), my public ssh key is okay. thanks best regards, From eric at christensenplace.us Wed Jul 15 21:01:02 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 15 Jul 2009 17:01:02 -0400 Subject: Fedora Docs Meeting Reminder Message-ID: <1247691662.2633.3.camel@thunder.christensenplace.us> REMINDER: There will be a Fedora Docs Meeting today at 0001 UTC. The agenda can be found at: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting If anyone has anything to add to the agenda please do so before 23:30 UTC. Thanks, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From bugzilla at redhat.com Wed Jul 15 21:13:31 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 17:13:31 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907152113.n6FLDVZn013707@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 505946, which changed state. Bug 505946 Summary: Review Request: zikula-module-menutree - Menutree allows to create multilevel, hierarchical (tree-like) menu https://bugzilla.redhat.com/show_bug.cgi?id=505946 What |Old Value |New Value ---------------------------------------------------------------------------- Status|CLOSED |ASSIGNED Resolution|CANTFIX | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 15 21:51:15 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 17:51:15 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907152151.n6FLpFAt011539@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |511998 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 15 21:52:10 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 17:52:10 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907152152.n6FLqAUG011666@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 505946, which changed state. Bug 505946 Summary: Review Request: zikula-module-menutree - Menutree allows to create multilevel, hierarchical (tree-like) menu https://bugzilla.redhat.com/show_bug.cgi?id=505946 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CANTFIX -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From sijis at fedoraproject.org Wed Jul 15 23:06:02 2009 From: sijis at fedoraproject.org (Sijis Aviles) Date: Wed, 15 Jul 2009 18:06:02 -0500 Subject: Fedora Knowledge Base Message-ID: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> Hi all, Based on a submitted enhancement request (https://fedorahosted.org/fedora-infrastructure/ticket/208) I started investigating possible solutions. I eventually ended up finding a php-based tool named phpmyfaq which seems to have met the original submitter's feature list. I'm bringing my findings here as I believe the docs team would be the primary user of this tool. I'd like to get some feedback and alternatives and know if this is something worth pursuing. Thanks, Sijis From bugzilla at redhat.com Wed Jul 15 23:47:35 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 19:47:35 -0400 Subject: [Bug 512025] Need to package zikula News module In-Reply-To: References: Message-ID: <200907152347.n6FNlZOG000362@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=512025 --- Comment #1 from Paul W. Frields 2009-07-15 19:47:34 EDT --- Oh criminy, that should have read "Need to package News." No take-backs! -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Wed Jul 15 23:47:11 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 19:47:11 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907152347.n6FNlBL2011043@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512025 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 15 23:47:11 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 19:47:11 -0400 Subject: [Bug 512025] New: Need to package zikula News module Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Need to package zikula News module https://bugzilla.redhat.com/show_bug.cgi?id=512025 Summary: Need to package zikula News module Product: Fedora Documentation Version: devel Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: docs-requests AssignedTo: eric at christensenplace.us ReportedBy: stickster at gmail.com QAContact: fedora-docs-list at redhat.com CC: stickster at gmail.com Blocks: 504066 Classification: Fedora Description of problem: Need to package MediaAttach. Current: http://code.zikula.org/news/browser/tags/News-2.4.1 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Thu Jul 16 00:03:43 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 15 Jul 2009 20:03:43 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907160003.n6G03hn1014204@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512027 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From eric at christensenplace.us Thu Jul 16 01:07:29 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 15 Jul 2009 21:07:29 -0400 Subject: Docs Meeting 2009-07-16 IRC log Message-ID: <1247706450.2633.7.camel@thunder.christensenplace.us> 00:02:22 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting 00:02:30 Roll Call! 00:02:30 * Sparks is here 00:02:38 * danielsmw is present 00:02:50 * Tsagadai is present 00:02:53 * ianweller 00:02:54 * joat is too 00:03:07 * jjmcd is here as well 00:03:38 * ianweller is *still* here 00:04:22 * rudi is here 00:05:42 Good turn out... still waiting for stickster and quaid 00:05:51 and poelcat 00:06:00 and ke4qqq 00:06:17 * stickster is here for a few minutes 00:06:32 Sparks: Did poelcat know about the schedule item? 00:06:52 I thought 00:07:01 IOW, did someone let him know? 00:07:29 specifically about this meeting? I didn't. 00:07:46 I don't know how he was supposed to know to be here then 00:07:47 He's not on IRC ATM 00:08:12 He's logged in, just not around here 00:08:21 Wasn't he here last week when we pushed the calendar to this week? 00:08:29 Not sure, I wasn't either :-D 00:08:30 * ke4qqq is here 00:08:31 But anyhow 00:08:39 Let's move on and see if he comes in later 00:08:45 * quaid pops in 00:08:48 I pinged him 00:08:57 * Sparks was on the wrong IRC server 00:09:17 * stickster waves to quaid 00:09:23 Okay, let's get going! 00:09:27 #topic Status on CMS (Zikula) <-- ke4qqq 00:09:32 ke4qqq: Where are you? 00:09:37 right here 00:09:46 ke4qqq: Where are we on zikula? 00:10:15 getting very close WRT packaging - -Content is the big outstanding one I think 00:10:26 and we need mediashare 00:10:34 I'll try and get mediashare done by tonight 00:10:42 and get everything that's up for review done 00:10:47 as well 00:11:06 * Sparks didn't add his poll packages to the Zikula ticket as they weren't required. 00:11:09 and we still have the fedora specific stuff which I am trying to get uploaded now 00:11:34 ke4qqq: If there's anything lacking by tomorrow, let me know -- I can spend some time on this Friday if needed. 00:11:47 * stickster blocked out time with ianweller to make sure packages are reviewed and pushed 00:11:53 outstanding! 00:13:14 Cool 00:13:38 Are all the "Need to Package" tickets assigned and being handled? 00:13:41 News is done, by the way, awaiting review 00:13:54 .bug 512027 00:13:56 stickster++ 00:13:56 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=512027 medium, medium, ---, nobody, NEW, Review Request: zikula-module-News - Manages news articles on your Zikula site 00:13:57 Bug 512027: medium, medium, ---, nobody, NEW, Review Request: zikula-module-News - Manages news articles on your Zikula site 00:13:57 Sparks: the mediashare I don't know if it is done 00:14:16 Hmm, those bots need to figure out who's on first. 00:14:19 I seem to remember that one had some problems? 00:14:46 Sparks: We really need to set up dedicated time to go through these one by one. 00:14:48 Sparks: it needed several dependencies which I think stickster took care of most of, and I took care of the other one 00:15:02 i.e. bug review for packages for those that aren't closed 00:15:11 Maybe ianweller and I can make that a focus for Friday. 00:15:20 Friday Focus(tm) 00:15:32 * stickster prefers a methodical approach so we don't wonder, "Didn't we... did you...?" later.. 00:15:59 stickster: I agree. Put me down for Friday. I'll see what my calendar looks like tomorrow 00:16:04 +1 the scope is just a bit large at the moment and I don't think any of us have spent the time looking at all ~20 tickts/packages. 00:16:11 stickster: who are you again? 00:16:11 ;) 00:16:26 The guy who capitalizes stuff 00:16:32 everything but your nick 00:16:47 moving on! 00:16:49 :) 00:17:12 Okay... anything else on the Zikula stuff? 00:17:22 So ACTION - ianweller, stickster, Sparks(?), ke4qqq(?) to look at status with a magnifying glass on Friday 00:17:54 #ACTION ianweller stickster Sparks ke4qqq to look at status on Zikula on Friday to make sure everything is getting done. 00:18:24 * ianweller isn't sure if it takes CAPITALIZED commands 00:18:31 #action ianweller stickster Sparks ke4qqq to look at status on Zikula on Friday to make sure everything is getting done. 00:18:39 #lights #camera 00:18:40 We'll soon find out ;-) 00:19:00 C programmers - sheesh 00:19:06 Okay... Moving on... 00:19:29 #topic Status on CC license discussion. <--quaid 00:19:34 #link http://creativecommons.org/licenses/by-sa/3.0/us/ 00:19:54 quaid: What do you have for us tonight? 00:20:56 * Sparks thought quaid was here 00:21:26 * ianweller thought so too 00:21:26 * ke4qqq is stepping away for a moment 00:21:35 I think it works when you say: quaid quaid quaid quaid quaid 00:21:36 Like that. 00:21:41 Oh 00:21:49 quaid quaid quaid quaid quaid 00:22:01 quack quack quack quack quack 00:22:18 So Sparks, what was the holdover from the last meeting on this topic? 00:22:41 the last meeting was week 1... we were waiting for the sky to fall 00:22:45 but it didn't 00:23:10 Right, and we set a 2 week call for input, right? 00:23:14 yes 00:23:17 * stickster overuses "right," right? 00:23:21 right 00:23:23 correct 00:23:24 Heh 00:23:34 I haven't personally seen any odd input. 00:23:41 No even input, either. 00:23:46 I haven't personally seen any input 00:24:01 If it were my call, I would say that the time for input is over and the time for action is now. 00:24:03 Does anyone have any input? 00:24:16 * danielsmw doesn't. 00:24:37 MOTION: I say we make everything written CC-BY-SA v3. 00:24:39 I don't know what's happening internally with RH Content Services though, quaid was mediating that 00:24:43 second 00:24:47 +1 00:24:53 +1 00:24:57 +1 00:24:59 +1 00:25:46 +1 for new stuff 00:26:22 * stickster tries to remember how zodbot is commanded here... "resolved?" 00:26:30 #agreed All documenation will be changed to a CC-BY-SA v3 license. 00:26:35 yeah, that's the ticket. 00:26:51 * Sparks waits for all the confetti and ticker tape to stop falling 00:27:01 * danielsmw observers that the confetti stopped. 00:27:09 * danielsmw s/observers/observed/ 00:27:21 Okay... moving on 00:27:29 ke4qqq: You back? 00:28:31 #topic Outstanding BZ Tickets 00:28:42 #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW 00:29:03 *sigh* 00:29:08 you guys never need me when I'm on this screen 00:29:10 There are 23 tickets that haven't been assigned. Please go through them and see what you can work on. 00:29:25 quaid: We called and quacked but you didn't come 00:29:39 yeah, I see that _now_ 00:29:48 jjmcd: There are a few tickets in there for the RNs 00:30:24 Yep, I thought I grabbed most of them. Having some git issues a week or so ago, expect to come up for air Friday (finally) 00:30:43 I'm going to start assigning them on Friday so if you want something cool better roger up for it now! :) 00:30:54 * stickster is going to close his if he doesn't get input from f13 or jeremy 00:30:54 I thought it would be tomorrow but I gotta go up to gladwin for a funeral 00:31:16 yeah, most of the rn ones are straightforward 00:31:17 .bug 474368 by the way 00:31:19 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=474368 medium, low, ---, stickster, NEW, Live CDs README says wrong minimal memory requirement 00:31:38 Ha, zodbot, you lose 00:32:53 So there are 23 NEW tickets and 58 tickets in process. Let's see if we can clean that up some before next week. 00:33:28 Anyone have anything else? 00:33:36 ke4qqq: You back? 00:33:39 Sorry, miskey here 00:34:01 * stickster has to run away now that he fixed what he done broke 00:34:08 bah 00:34:17 #topic F12 Calendar <-- poelcat 00:34:27 Does anyone have any input on the F12 calendar? 00:34:56 do you have a link? 00:35:12 * Sparks thinks someone hasn't been paying attention 00:35:29 i have my hands in about 500 subprojects, what do you expect :) 00:35:40 ianweller: for you to know where the F12 calendar is. 00:35:48 I actually don't have that link handy right this second. 00:35:54 I've been using the iCal. 00:36:00 :-o 00:36:04 I'll push it on the list later. 00:36:21 anyone else? 00:36:28 http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-and-trans-tasks.html 00:36:36 rudi++ 00:37:31 * ianweller has nothing 00:38:11 #topic Guide needs? 00:38:19 User Guide 00:38:19 #link https://www.redhat.com/archives/fedora-docs-list/2009-July/msg00034.html 00:38:22 #link https://www.redhat.com/archives/fedora-docs-list/2009-July/msg00039.html 00:38:30 danielsmw: What do you have for the User Guide? 00:38:39 Well, one thing I have 00:38:46 I take that back 00:38:50 I have a lot more than one thiing. 00:39:09 Um... so rudi's response on the list if you saw it was very good (it's the latter link) 00:39:21 And a lot of whats in that document is where I want to go with the UG. 00:39:45 So the plan in my head is to completely start from scratch, and pull in the old content that we want to use on a case-by-case basis 00:39:53 (+1) 00:40:05 so we aren't abandoning the old content, but we're bringing it in to a new format so to speak. 00:40:08 Wow, now that's a makeover 00:40:15 Yeah, it is. 00:40:18 But I think it really needs it. 00:40:26 danielsmw -- that's definitely the easiest way to do it 00:40:44 Since I took the thing over for F8 00:40:55 it's really just been changed slightly every release 00:41:06 and it's become somewhat less easy to manage as it is. 00:41:14 It's needs a cleanup makeover. 00:41:16 So that's the plan. 00:41:19 Also, as a side note, 00:41:33 danielsmw: Do you have the help/resources you need to make it happen? 00:41:50 * rudi is happy to help out with the Publican XML skeleton 00:41:59 Sparks: not formally 00:42:05 danielsmw: cool 00:42:22 But anyway, I was thinking... I'm not sure that User Guide is an appropriate name. 00:42:30 If we go this new route per rudi's suggestions and my thoughts. 00:42:39 Do Stuff Guide 00:42:41 Because it would be more like a mixture of an FAQ and a cookbook 00:42:54 Like a Fedora Desktop Cookbook 00:42:55 or something 00:42:59 cool 00:42:59 ooh i like that. 00:43:04 very much like that. 00:43:08 thanks ianweller :) 00:43:19 One other poll question 00:43:27 The audience for this document.... 00:43:57 I was thinking about this: is it for the previously computerless new user? or is it for someone who probably new what they were doing in windows and wants to get involved in linux now? 00:44:10 both. 00:44:17 ianweller: that's what i was afraid of 00:44:19 I agree, both 00:44:24 danielsmw: i know it's scary 00:44:34 Okay, that's still fine. 00:44:44 Buuut, don't overestimate the degree to which "they knew what they were doing in Windows" 00:44:54 lol 00:45:05 I'm not sure how much one can know what they're doing in windows, 00:45:07 but i get what you mean. 00:45:07 I didn't mean that in an entirely cynical way 00:45:21 Right 00:45:22 But I mean 00:45:38 I don't need to explain mouse usage or how to insert a CD. 00:45:39 More that 90% of people spend 90% of their time at their home/small business computers doing the same small number of tasks 00:45:56 There's an element of self-selection here... 00:45:56 packaging? 00:46:26 Oh, and as for contributing upstream 00:46:31 I think those things are at an even more basic level than we can really cater to 00:46:32 per rudi's email's suggestion 00:46:39 I think that will be more doable in the new format as well. 00:46:44 As would be pulling from downstream. 00:46:50 So that could help a lot with the rewriting process. 00:47:26 * rudi emphasises that wherever we can reuse existing text, we need to make an effort to do so, to ease the load on l10n 00:47:36 rudi: understood 00:47:47 And with that, the brevity drought I tend to bring on is at an end. 00:48:46 Cool 00:49:04 Anyone have anything for the User Guide/Fedora Desktop Cookbook? 00:49:27 * rudi really dislikes the "Cookbook" title, but will take it to the mailing list 00:50:06 noted 00:50:15 Okay... I have a request for the Security Guide 00:50:50 So I finally got it approved and submitted the SRPM but it fails to build in koji. 00:51:04 #link http://koji.fedoraproject.org/koji/getfile?taskID=1474242&name=build.log 00:51:21 Being that this should affect all Publican patches I'm trying to get it figured out. 00:51:25 I just don't understand this one. 00:52:08 So if anyone has any ideas please get with me after the meeting 00:52:18 Anyone have anything else for existing guides? 00:52:59 #topic New Guides 00:53:02 Tsagadai: Go 00:53:31 yes 00:54:05 I have been writing the Virtualization Guide for some time 00:54:21 It's time to send the good stuff upstream 00:55:03 Tsagadai: what format? DocBook? 00:55:09 Docbook 00:55:14 about 300 pages :) 00:55:20 (and already Publicanized) 00:55:30 +1000 00:56:15 +9000 00:56:40 Tsagadai: We can set you up on docs.fp.o if you like 00:56:55 that would be great 00:57:41 Tsagadai: Great. We'll get you setup tonight 00:57:41 Tsagadai -- you should also open an infra ticket to get the code hosted 00:58:05 link please? 00:58:30 Tsagadai -- I'll walk you through it after the meeting :) 00:58:32 to host on fh.o? 00:58:39 * danielsmw has to leave a bit early; peace. 00:58:51 Yeah, so you can get Transifex hooked into it as well 00:58:58 ah 00:59:25 * ianweller notes we have 35 seconds left in the hour 00:59:26 So the Fedora Virtualization Guide is approved for F12? 00:59:38 Tsagadai: Go ahead and build the html, html-single, and PDF and we'll get all that uploaded tonight to docs.fp.o. 00:59:47 Tsagadai: WORKSFORME 00:59:49 :) 01:00:00 Anyone have anything for the Virtualization Guide? 01:00:57 Tsagadai: Thank you for bringing this to us tonight. 01:01:04 Any other new guides? 01:01:07 * rudi has been sketching out the Installation Quick Start Guide, but the skeleton's not quite ready yet. 01:01:27 rudi: Have you seen the screenshots on the wiki? 01:01:31 Yes 01:01:52 #link https://fedoraproject.org/wiki/Installing_Fedora_11_Leonidas 01:01:57 ^^^ for those that haven't 01:02:35 rudi: Anything else on that? 01:02:44 Nothing at this stage 01:02:51 ok 01:03:02 I hoped to have something ready for today, but don't :) 01:03:04 Tsagadai: Almost forgot... Can you add your guide to https://fedoraproject.org/wiki/Docs_Project_meetings#Guides, please? 01:03:13 sure 01:03:22 Okay... 01:03:34 #topic All other business 01:03:42 Anyone have anything they want to discuss? 01:05:30 * jjmcd moves to adjourn 01:05:37 nAnyone? 01:05:48 Thanks everyone for coming! 01:05:50 #endmeeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From david.nalley at fedoraproject.org Thu Jul 16 02:07:24 2009 From: david.nalley at fedoraproject.org (David Nalley) Date: Wed, 15 Jul 2009 22:07:24 -0400 Subject: Fedora specific Zikula module source Message-ID: Simon passed me (and I just put up) the fedora specific Zikula modules: To get the source: git clone git://git.fedorahosted.org/git/fedora-zikula.git Included here is: zikula-module-fedora-fasauth zikula-module-fedora-theme I'll try and get these packaged shortly. If you need commit access to this repo, let me know and we'll make that happen. Thanks From stickster at gmail.com Thu Jul 16 15:18:59 2009 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 16 Jul 2009 11:18:59 -0400 Subject: Fedora Knowledge Base In-Reply-To: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> References: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> Message-ID: <20090716151859.GL8801@localhost.localdomain> On Wed, Jul 15, 2009 at 06:06:02PM -0500, Sijis Aviles wrote: > Hi all, > > Based on a submitted enhancement request > (https://fedorahosted.org/fedora-infrastructure/ticket/208) I started > investigating possible solutions. I eventually ended up finding a > php-based tool named phpmyfaq which seems to have met the original > submitter's feature list. > > I'm bringing my findings here as I believe the docs team would be the > primary user of this tool. I'd like to get some feedback and > alternatives and know if this is something worth pursuing. This seems like yet another use case for Zikula. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From sijis at fedoraproject.org Thu Jul 16 17:16:14 2009 From: sijis at fedoraproject.org (Sijis Aviles) Date: Thu, 16 Jul 2009 12:16:14 -0500 Subject: Fedora Knowledge Base In-Reply-To: <20090716151859.GL8801@localhost.localdomain> References: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> <20090716151859.GL8801@localhost.localdomain> Message-ID: <747290270907161016j3b8ce1a7jba1af2a4130fca02@mail.gmail.com> Paul, Could you elaborate what you mean? I do not understand. Thanks, Sijis On Thu, Jul 16, 2009 at 10:18 AM, Paul W. Frields wrote: > On Wed, Jul 15, 2009 at 06:06:02PM -0500, Sijis Aviles wrote: >> Hi all, >> >> Based on a submitted enhancement request >> (https://fedorahosted.org/fedora-infrastructure/ticket/208) I started >> investigating possible solutions. I eventually ended up finding a >> php-based tool named phpmyfaq which seems to have met the original >> submitter's feature list. >> >> I'm bringing my findings here as I believe the docs team would be the >> primary user of this tool. I'd like to get some feedback and >> alternatives and know if this is something worth pursuing. > > This seems like yet another use case for Zikula. > > -- > Paul W. Frields ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?http://paul.frields.org/ > ?gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 ?5906 ACDB C937 BD11 3717 > ?http://redhat.com/ ? - ?- ?- ?- ? http://pfrields.fedorapeople.org/ > ?irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > From ricky at fedoraproject.org Thu Jul 16 18:11:09 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 16 Jul 2009 14:11:09 -0400 Subject: Fedora Knowledge Base In-Reply-To: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> References: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> Message-ID: <20090716181109.GA13177@alpha.rzhou.org> On 2009-07-15 06:06:02 PM, Sijis Aviles wrote: > Based on a submitted enhancement request > (https://fedorahosted.org/fedora-infrastructure/ticket/208) I started > investigating possible solutions. I eventually ended up finding a > php-based tool named phpmyfaq which seems to have met the original > submitter's feature list. > > I'm bringing my findings here as I believe the docs team would be the > primary user of this tool. I'd like to get some feedback and > alternatives and know if this is something worth pursuing. Hi, as I mentioned on IRC, I think this is one of the most important things Fedora is missing in making us a more newbie-friendly distro, so I'm really excited to see Sijis working on this :-) One example of the problems I see from the user's perspective is the ease of searching for certain information. If you look at the results for: http://www.google.com/search?q=opensuse+apache http://www.google.com/search?q=fedora+apache the difference in the quality of the results is astounding. Another example of the type of user resource that I'm trying to describe here is http://en.gentoo-wiki.com/wiki/Index:Tutorials (although maybe including some even more basic topics, like how to use yum, or how to setup sudo, etc. - the helpers in #fedora could be an excellent group to ask about what types of docs would be useful). One thing I'm curious about is what you guys think about doing these sorts of howtos via the wiki vs. the knowledge base. Although the barrier to entry for a knowledge base might be a tiny bit higher, it might have workflow features that you guys would find handy. How do you all think we can approach starting an effort to create this type of friendly, "task-driven" HOWTO-style documentation? Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From stickster at gmail.com Thu Jul 16 18:22:39 2009 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 16 Jul 2009 14:22:39 -0400 Subject: Fedora Knowledge Base In-Reply-To: <747290270907161016j3b8ce1a7jba1af2a4130fca02@mail.gmail.com> References: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> <20090716151859.GL8801@localhost.localdomain> <747290270907161016j3b8ce1a7jba1af2a4130fca02@mail.gmail.com> Message-ID: <20090716182239.GA910@localhost.localdomain> On Thu, Jul 16, 2009 at 12:16:14PM -0500, Sijis Aviles wrote: > On Thu, Jul 16, 2009 at 10:18 AM, Paul W. Frields wrote: > > On Wed, Jul 15, 2009 at 06:06:02PM -0500, Sijis Aviles wrote: > >> Hi all, > >> > >> Based on a submitted enhancement request > >> (https://fedorahosted.org/fedora-infrastructure/ticket/208) I started > >> investigating possible solutions. I eventually ended up finding a > >> php-based tool named phpmyfaq which seems to have met the original > >> submitter's feature list. > >> > >> I'm bringing my findings here as I believe the docs team would be the > >> primary user of this tool. I'd like to get some feedback and > >> alternatives and know if this is something worth pursuing. > > > > This seems like yet another use case for Zikula. > > Could you elaborate what you mean? I do not understand. Hi Sijis*, I'll post the little bit of conversation we had on IRC so others can see what I meant, since I didn't do a good job of explaining. Thanks for asking about it! sijis: Zikula is the content management system we're working on, and it may have a knowledge base-type function that would keep us from having to evaluate yet another application to run on Infrastructure. stickster: Hey, I'm curious as to what your thoughts are on wiki vs. zikula for a knowledge-base/howto type thing ricky: The wiki is more difficult to enforce a review workflow That's the chief difference IMHO I think a collection of good howtos is one of the biggest things that Fedora is missing in being a more newbie-friendly distro ricky: I agree. The Docs Project is the place to help with that, no doubt. HOWTOs could easily be on the wiki [...snip...] stickster: yeah, i know that you guys are working on zikula. thakns for the info. i agree it would be better to stay on a single platform. stickster: i thought it would be helpful, simialr to what ricky is talking about. I agree, a KB is something we've wanted to try for a long time = = = * Also, if you don't mind, please put your replies at the bottom of email, it makes them so much easier to read! Thanks. https://fedoraproject.org/wiki/Communicate/MailingListGuidelines#If_You_Are_Replying_to_a_Message -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From kwade at redhat.com Thu Jul 16 21:56:58 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 16 Jul 2009 14:56:58 -0700 Subject: RPM Guide and RPM Max In-Reply-To: <20090710131235.GC28530@localhost.localdomain> References: <207B4B40D82E4BC68A319D06EBE12698@Aidan> <20090710131235.GC28530@localhost.localdomain> Message-ID: <20090716215658.GC24072@calliope.phig.org> On Fri, Jul 10, 2009 at 09:12:35AM -0400, Paul W. Frields wrote: > > Do we need to update both, or is it sufficient to get all coverage > into the new RPM Guide, and make that our focus? +1 A single, canonical RPM guide should be the goal. As Rahul said, updating content from the wiki is important, much has changed. Concepts need vetting, too. Old locations should be deprecated, including the wiki content, once it has been moved. Too much is inaccurate and scattered. One of the best services we can do for rpm.org is to give them a single, canonical upstream to steer. > As for licensing: > > * Maximum RPM is under OPL + exception (no paper publication without > express permission). It has one author, Ed Bailey, and the copyright > is owned by Red Hat, probably making re-licensing easy. (We ask, and > Legal approves, maybe following a discussion, likely brief and simple, > with Red Hat Content Services.) I joined and emailed rpm-maint about this; I haven't seen my join yet (held for approval?), nor the email I sent. I'm compiling a single list on the wiki of all the content in Fedora and in Red Hat, and now rpm.org, that we want to relicense. https://fedoraproject.org/wiki/Relicensing_OPL_to_CC_BY_SA#Specific_content_to_be_relicensed I'm seeing the OPL all over the place - Infrastructure's CSI work, the system-config-* content, etc. I don't think we can do the update in a single swooping move, we'll still find stragglers for some time. But I don't think I need to take each and every guide individually to Red Hat Legal or Content Services, a list should be sufficient. I'll confirm that with Richard Fontana and Michael Hideo-Smith (after I compile it a bit), but I heard a clear mandate from Legal to move entirely from the OPL to CC BY SA 3.0 Unported in all cases. Content Services also wanted to move all and not selectively. They don't want any stragglers, either. > * RPM Guide is under OPL with no exceptions. It has a single author, > Eric Foster-Johnson, whom we'd need to ask to relicense the material. Ah, good point. He did that at our request, and it is covered by the CLA, but even simple courtesy says, let's ask. I take care of that. - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Thu Jul 16 22:02:59 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 16 Jul 2009 15:02:59 -0700 Subject: how can I help? In-Reply-To: <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> Message-ID: <20090716220259.GD24072@calliope.phig.org> On Wed, Jul 15, 2009 at 05:39:44PM -0300, Niko Yoshio wrote: > Well, the company where I work we use the mediawiki to documenting > procedures, I have some experience in editing or creating articles, > but I would document projects. It could also translate documents from > English to Portuguese-Brazilian. > The accounts are created (bugzilla and FAS), my public ssh key is okay. Great! We are seeing a lot of interest in using the wiki for writing general-purpose how-to documentation. I wonder ... would it be useful for people to read fedora-list, fedoraforum.org, and talk with moderators on #fedora about common issues, then turn those in to short articles on the wiki? The next thing is, of course, to post back to that thread (email, forum) with a link to the new canonical wiki source for that answer. We were talking earlier today about a knowledge base (kbase). That is another great idea, focused on much shorter articles to solve a specific problem. While that is being researched, why not start writing content in to the wiki? It would be a good idea to add a category at the bottom of each article, such as: [[Category:Kbase article]] [[Category:Kbase article draft]] [[Category:Kbase food]] Maybe not all of those, but one of them. :) - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Thu Jul 16 22:07:36 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 16 Jul 2009 15:07:36 -0700 Subject: Self Introduction: Rashadul Islam In-Reply-To: <17fa59580907150753l14835099if42d2b83ba03bc70@mail.gmail.com> References: <17fa59580907150740o6a983262ib3e0eae1415daa6d@mail.gmail.com> <17fa59580907150753l14835099if42d2b83ba03bc70@mail.gmail.com> Message-ID: <20090716220736.GE24072@calliope.phig.org> On Wed, Jul 15, 2009 at 10:53:52AM -0400, Rashadul Islam wrote: > *Dear Fedora Documentation team: > > *As a beginner in Documentation team I would like to introduce myself as > instructed. So, of the items you saw discussed in IRC today ... * Knowledge base & short, targeted articles * Wiki-based how-to articles on comprehensive topics Do you see that as a way you can contribute? Do you want short, quick to accomplish items, or to immerse yourself in a larger work? Are there specific topics you'd like to write/edit about? Are you interested in editing for technical accuracy? It appears we may be getting some more content incoming from the Red Hat Content Services team. You might be interested in doing technical editing for that, which will introduce you to DocBook & Publican, as well as the general writing style, etc. - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From bugzilla at redhat.com Thu Jul 16 23:00:07 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 16 Jul 2009 19:00:07 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907162300.n6GN07Mn018060@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 David Nalley changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512273 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From kwade at redhat.com Thu Jul 16 23:14:19 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 16 Jul 2009 16:14:19 -0700 Subject: Fedora Knowledge Base In-Reply-To: <20090716181109.GA13177@alpha.rzhou.org> References: <747290270907151606ibc4e638o7d3ae49ea12e5099@mail.gmail.com> <20090716181109.GA13177@alpha.rzhou.org> Message-ID: <20090716231419.GF24072@calliope.phig.org> On Thu, Jul 16, 2009 at 02:11:09PM -0400, Ricky Zhou wrote: > One thing I'm curious about is what you guys think about doing these > sorts of howtos via the wiki vs. the knowledge base. Although the > barrier to entry for a knowledge base might be a tiny bit higher, it > might have workflow features that you guys would find handy. I'll paraphrase a bit about what I said on IRC. While a kbase can contain larger articles, it is usually filled with short, topic-based solutions to specific problems. "How to start Apache web server", "How to see how much space is available to add to an LVM", "How to add a new logical volume to an LVM" A wiki is nice for organizing a set of such instructions with wrapping to make it a nice topic-based short guide. "Installing and starting Apache HTTPD Web server", "Adding more space to an LVM". Wikis are also more responsive to the day-to-day needs of an active mailing list and IRC channel. This page: http://fedoraproject.org/wiki/Writing_how_to_documentation_on_the_wiki ... in intended to give simple guidelines on "how to" writing for the wiki. There is a modular idea we might consider, and might as quickly reject. 1. If each kbase article represented a discrete, canonical piece of information, and ... 2. If it fits in to a longer wiki article automagically, then ... 3. Each wiki article is a chapter (or large section of a big chapter) in a full-length guide. Full length guide writers will remind us (rightly!) that a long document without a narrative and flow is going to feel like ... a bunch of smaller how-to articles jammed in to a chapter wrapper. But I've often wondered what would happen if just steps 1 and 2 were implemented. Would a wiki article feel disjointed if it consisted of a number of smaller kbase articles? BTW, all of this could probably be done within a Zikula instance, so it is less wiki-like but more wysiwyg-like. - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From kwade at redhat.com Thu Jul 16 23:38:40 2009 From: kwade at redhat.com (Karsten Wade) Date: Thu, 16 Jul 2009 16:38:40 -0700 Subject: Fedora specific Zikula module source In-Reply-To: References: Message-ID: <20090716233840.GG24072@calliope.phig.org> On Wed, Jul 15, 2009 at 10:07:24PM -0400, David Nalley wrote: > Simon passed me (and I just put up) the fedora specific Zikula modules: > > To get the source: > git clone git://git.fedorahosted.org/git/fedora-zikula.git > > Included here is: > zikula-module-fedora-fasauth > zikula-module-fedora-theme F! T! W! Not to be too cheery in the middle of the field of play, but I'd like to pause to acknowledge the innovation happening in the middle of the Docs Team. We are right now creating a way that other teams can use to interact with each other to accomplish web interface objectives. Other Fedora sub-projects can use the new logistics list[1] for cross-team collaboration, and follow this model for seeking an appropriate technical solution. Who would have thought of the idea, "Let's give the technical solution to whichever free software project team wants to come make their solution happen within Fedora's infrastructure"? Thanks, Toshio! As many of us have experienced, if this were an engineering documentation team inside of a company trying to get IT, web design, and project management to move this quickly on a new front-facing CMS solution ... well, it would either be a start-up and not have the same enterprise quality legs that we have in the Fedora Project, or it wouldn't happen this quickly and gracefully. Great, great work ... - Karsten [1] https://admin.fedoraproject.org/mailman/listinfo/logistics -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From poelstra at redhat.com Fri Jul 17 02:01:58 2009 From: poelstra at redhat.com (John Poelstra) Date: Thu, 16 Jul 2009 19:01:58 -0700 Subject: Fedora specific Zikula module source In-Reply-To: <20090716233840.GG24072@calliope.phig.org> References: <20090716233840.GG24072@calliope.phig.org> Message-ID: <4A5FDB96.6060705@redhat.com> Karsten Wade said the following on 07/16/2009 04:38 PM Pacific Time: > On Wed, Jul 15, 2009 at 10:07:24PM -0400, David Nalley wrote: >> Simon passed me (and I just put up) the fedora specific Zikula modules: >> >> To get the source: >> git clone git://git.fedorahosted.org/git/fedora-zikula.git >> >> Included here is: >> zikula-module-fedora-fasauth >> zikula-module-fedora-theme > > F! T! W! > > Not to be too cheery in the middle of the field of play, but I'd like > to pause to acknowledge the innovation happening in the middle of the > Docs Team. > > We are right now creating a way that other teams can use to interact > with each other to accomplish web interface objectives. Other Fedora > sub-projects can use the new logistics list[1] for cross-team > collaboration, and follow this model for seeking an appropriate > technical solution. Who would have thought of the idea, "Let's give > the technical solution to whichever free software project team wants > to come make their solution happen within Fedora's infrastructure"? > Thanks, Toshio! > > As many of us have experienced, if this were an engineering > documentation team inside of a company trying to get IT, web design, > and project management to move this quickly on a new front-facing CMS > solution ... well, it would either be a start-up and not have the same > enterprise quality legs that we have in the Fedora Project, or it > wouldn't happen this quickly and gracefully. > > Great, great work ... > > - Karsten > > [1] https://admin.fedoraproject.org/mailman/listinfo/logistics > Speaking of which... is anyone interested in helping me write the text that goes into mailman and explains what the logistics list is for? And then helping me figure out where to add it to mailman? Thanks, John From fabhoneydew at gmail.com Fri Jul 17 14:27:29 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Fri, 17 Jul 2009 19:57:29 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> Message-ID: <9f45b2730907170727v5a954785gb85d0f40065a5f92@mail.gmail.com> On Sun, Jul 12, 2009 at 8:02 PM, sankarshan wrote: > Nice quick start. Would it be possible for you to: > > - have it as a page within the Fedora wiki ? wiki page made. link [1] > - make a PDF / print-ready version available ? pdf made. [2] [1] http://fedoraproject.org/wiki/Install_Fedora11 [2] http://kishan.fedorapeople.org/Fedora11_Install.pdf The pdf is in a minimal form... expecting some feedback to improve it. Thanks, Regards, Kishan Goyal From bugzilla at redhat.com Fri Jul 17 19:04:34 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:04:34 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171904.n6HJ4YP7032052@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|505982 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:05:45 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:05:45 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171905.n6HJ5j1w000439@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|510979 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:04:54 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:04:54 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171904.n6HJ4sqH032213@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|511998 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:08:30 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:08:30 -0400 Subject: [Bug 512025] Need to package zikula News module In-Reply-To: References: Message-ID: <200907171908.n6HJ8ULf013292@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=512025 --- Comment #3 from Paul W. Frields 2009-07-17 15:08:29 EDT --- See bug 512027. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Fri Jul 17 19:06:52 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:06:52 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171906.n6HJ6q27012960@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|512273 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:08:37 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:08:37 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171908.n6HJ8bsm013545@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|512027 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:05:40 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:05:40 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171905.n6HJ5eVK012396@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|506056 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:08:38 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:08:38 -0400 Subject: [Bug 512025] Need to package zikula News module In-Reply-To: References: Message-ID: <200907171908.n6HJ8c6B013615@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=512025 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512027 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Fri Jul 17 19:09:15 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:09:15 -0400 Subject: [Bug 508379] Need to package "Simple Voting System" In-Reply-To: References: Message-ID: <200907171909.n6HJ9FsR013768@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508379 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512016(zikula-module-Polls) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Fri Jul 17 19:07:09 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:07:09 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171907.n6HJ79NY013052@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 512025, which changed state. Bug 512025 Summary: Need to package zikula News module https://bugzilla.redhat.com/show_bug.cgi?id=512025 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |NEXTRELEASE -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:07:09 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:07:09 -0400 Subject: [Bug 512025] Need to package zikula News module In-Reply-To: References: Message-ID: <200907171907.n6HJ79bF013033@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=512025 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |NEXTRELEASE --- Comment #2 from Paul W. Frields 2009-07-17 15:07:05 EDT --- Currently awaiting CVS, otherwise done. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Fri Jul 17 19:10:54 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:10:54 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171910.n6HJAshm001954@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|510881 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:09:20 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:09:20 -0400 Subject: [Bug 508382] Package Advanced Voting System for Zikula In-Reply-To: References: Message-ID: <200907171909.n6HJ9KhW001296@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508382 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512021 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Fri Jul 17 19:10:49 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:10:49 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171910.n6HJAn8D014744@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|505942 | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:23:00 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:23:00 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907171923.n6HJN0vK017726@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 512025, which changed state. Bug 512025 Summary: Need to package zikula News module https://bugzilla.redhat.com/show_bug.cgi?id=512025 What |Old Value |New Value ---------------------------------------------------------------------------- Status|CLOSED |ASSIGNED Resolution|NEXTRELEASE | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Fri Jul 17 19:23:00 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:23:00 -0400 Subject: [Bug 512025] Need to package zikula News module In-Reply-To: References: Message-ID: <200907171923.n6HJN0tZ017709@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=512025 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Reopened Status|CLOSED |ASSIGNED Resolution|NEXTRELEASE | --- Comment #4 from Paul W. Frields 2009-07-17 15:22:59 EDT --- Oops, my workflow bad. This stays open until rel-eng gets it in the repos. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Fri Jul 17 19:39:12 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:39:12 -0400 Subject: [Bug 505938] Need to package MediaAttach. In-Reply-To: References: Message-ID: <200907171939.n6HJdCoh021336@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=505938 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |512273 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Fri Jul 17 19:52:50 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:52:50 -0400 Subject: [Bug 505938] Need to package MediaAttach. In-Reply-To: References: Message-ID: <200907171952.n6HJqoU4024647@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=505938 --- Comment #4 from Ian Weller 2009-07-17 15:52:49 EDT --- Packaging dependency: PHP getid3 libraries, http://www.getid3.org -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Fri Jul 17 19:54:56 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:54:56 -0400 Subject: [Bug 505938] Need to package MediaAttach. In-Reply-To: References: Message-ID: <200907171954.n6HJsuYc024954@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=505938 Ian Weller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian at ianweller.org --- Comment #5 from Ian Weller 2009-07-17 15:54:55 EDT --- Licensing issues: (from pndocs/credits.txt) -- Highslide JS http://vikjavev.no/highslide/ License: Creative Commons Attribution-NonCommercial 2.5 License (http://creativecommons.org/licenses/by-nc/2.5/) -- JavaScript Image Cropper UI http://www.defusion.org.uk/code/javascript-image-cropper-ui-using-prototype-scriptaculous/ Copyright (c) 2006, David Spurr (www.defusion.org.uk) All rights reserved. -- JW FLV Player http://www.jeroenwijering.com/?item=JW_FLV_Player License: Creative Commons Attribution-NonCommercial 2.0 License (http://creativecommons.org/licenses/by-nc-sa/2.0/) -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Fri Jul 17 19:59:39 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 17 Jul 2009 15:59:39 -0400 Subject: [Bug 505938] Need to package MediaAttach. In-Reply-To: References: Message-ID: <200907171959.n6HJxdi4026064@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=505938 --- Comment #6 from Ian Weller 2009-07-17 15:59:38 EDT --- JS-TreeMenu, from their website: "This software is freeware for non-commercial use." -- http://www.gerd-tentler.de/tools/treemenu/?page=download -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From stickster at gmail.com Fri Jul 17 23:21:09 2009 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 17 Jul 2009 19:21:09 -0400 Subject: Zikula progress Message-ID: <20090717232109.GA26316@localhost.localdomain> I got a couple steps further on Zikula, after I fixed my system from being bitten by a missing nss-mdns.x86_64 package: * Ian Weller got me briefed on how to do a good package review these days * Got a package review done for David Nalley (php-File-Bittorrent2) * Started working on Mediashare module * Buffed up on how to package phpSmug properly Not as far as I would have liked to get, but per usual I had to fight my way past ignorance and inexperience to get there. The good news is, I'm ready to do better work this weekend if time allows! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From ian at ianweller.org Sat Jul 18 03:44:21 2009 From: ian at ianweller.org (Ian Weller) Date: Fri, 17 Jul 2009 22:44:21 -0500 Subject: Zikula progress In-Reply-To: <20090717232109.GA26316@localhost.localdomain> References: <20090717232109.GA26316@localhost.localdomain> Message-ID: <20090718034421.GK7115@hovercraft.mobile.ianweller.org> On Fri, Jul 17, 2009 at 07:21:09PM -0400, Paul W. Frields wrote: > I got a couple steps further on Zikula, after I fixed my system from > being bitten by a missing nss-mdns.x86_64 package: > > * Ian Weller got me briefed on how to do a good package review these > days > > * Got a package review done for David Nalley (php-File-Bittorrent2) > > * Started working on Mediashare module > > * Buffed up on how to package phpSmug properly > > Not as far as I would have liked to get, but per usual I had to fight > my way past ignorance and inexperience to get there. The good news > is, I'm ready to do better work this weekend if time allows! > Stuff I got done: - rebuilt the FE-ZIKULA dependency tree so that dependencies are in the right places - (please don't just tag everything related as FE-ZIKULA, if something is blocking a review request or the like set that as the blocker) - started working on MediaAttach and reached a level of doom emphasized by licensing (noncommercial crapola) issues and bundled libraries -- Ian Weller "Why, a four-year-old could understand this report. Find me a four-year-old child. I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From stickster at gmail.com Sat Jul 18 11:17:53 2009 From: stickster at gmail.com (Paul W. Frields) Date: Sat, 18 Jul 2009 07:17:53 -0400 Subject: Zikula progress In-Reply-To: <20090718034421.GK7115@hovercraft.mobile.ianweller.org> References: <20090717232109.GA26316@localhost.localdomain> <20090718034421.GK7115@hovercraft.mobile.ianweller.org> Message-ID: <20090718111753.GB1355@localhost.localdomain> On Fri, Jul 17, 2009 at 10:44:21PM -0500, Ian Weller wrote: > On Fri, Jul 17, 2009 at 07:21:09PM -0400, Paul W. Frields wrote: > > I got a couple steps further on Zikula, after I fixed my system from > > being bitten by a missing nss-mdns.x86_64 package: > > > > * Ian Weller got me briefed on how to do a good package review these > > days > > > > * Got a package review done for David Nalley (php-File-Bittorrent2) > > > > * Started working on Mediashare module > > > > * Buffed up on how to package phpSmug properly > > > > Not as far as I would have liked to get, but per usual I had to fight > > my way past ignorance and inexperience to get there. The good news > > is, I'm ready to do better work this weekend if time allows! > > > Stuff I got done: > > - rebuilt the FE-ZIKULA dependency tree so that dependencies are in the > right places > - (please don't just tag everything related as FE-ZIKULA, if something > is blocking a review request or the like set that as the blocker) > - started working on MediaAttach and reached a level of doom emphasized > by licensing (noncommercial crapola) issues and bundled libraries The licensing situation in some of these modules is pretty ugly, no doubt. It's a great thing that the Zikula guys are working with us to resolve them, but I hope we can get traction soon since we'd like to have our system off the ground in August. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From david.nalley at fedoraproject.org Sat Jul 18 14:19:38 2009 From: david.nalley at fedoraproject.org (David Nalley) Date: Sat, 18 Jul 2009 10:19:38 -0400 Subject: Zikula progress In-Reply-To: <20090718111753.GB1355@localhost.localdomain> References: <20090717232109.GA26316@localhost.localdomain> <20090718034421.GK7115@hovercraft.mobile.ianweller.org> <20090718111753.GB1355@localhost.localdomain> Message-ID: On Sat, Jul 18, 2009 at 7:17 AM, Paul W. Frields wrote: > On Fri, Jul 17, 2009 at 10:44:21PM -0500, Ian Weller wrote: >> On Fri, Jul 17, 2009 at 07:21:09PM -0400, Paul W. Frields wrote: >> > I got a couple steps further on Zikula, after I fixed my system from >> > being bitten by a missing nss-mdns.x86_64 package: >> > >> > * Ian Weller got me briefed on how to do a good package review these >> > ? days >> > >> > * Got a package review done for David Nalley (php-File-Bittorrent2) >> > >> > * Started working on Mediashare module >> > >> > * Buffed up on how to package phpSmug properly >> > >> > Not as far as I would have liked to get, but per usual I had to fight >> > my way past ignorance and inexperience to get there. ?The good news >> > is, I'm ready to do better work this weekend if time allows! >> > >> Stuff I got done: >> >> - rebuilt the FE-ZIKULA dependency tree so that dependencies are in the >> ? right places >> ? - (please don't just tag everything related as FE-ZIKULA, if something >> ? ? is blocking a review request or the like set that as the blocker) >> - started working on MediaAttach and reached a level of doom emphasized >> ? by licensing (noncommercial crapola) issues and bundled libraries > > The licensing situation in some of these modules is pretty ugly, no > doubt. ?It's a great thing that the Zikula guys are working with us to > resolve them, but I hope we can get traction soon since we'd like to > have our system off the ground in August. > And while they hate the pain of the work involved. they do realize that this is beneficial to them. They are essentially getting a licensing audit for free. And just as we are getting help from them, we are returning that help. From a.mani.cms at gmail.com Sat Jul 18 14:30:19 2009 From: a.mani.cms at gmail.com (Mani A) Date: Sat, 18 Jul 2009 20:00:19 +0530 Subject: Computers Book Message-ID: <78323d480907180730s7a2b0862t46bcc22a79af21f0@mail.gmail.com> http://www.darknet.org.uk/2006/03/how-computers-work-free-e-book/ This is a well written book for people without knowledge of basic electronics to become hardware hackers. But will be useful for those who know as well. Best A. Mani -- A. Mani ASL, CLC, AMS, CMS http://amani.topcities.com http://www.logicamani.co.cc From stickster at gmail.com Sat Jul 18 18:03:48 2009 From: stickster at gmail.com (Paul W. Frields) Date: Sat, 18 Jul 2009 14:03:48 -0400 Subject: Zikula progress In-Reply-To: References: <20090717232109.GA26316@localhost.localdomain> <20090718034421.GK7115@hovercraft.mobile.ianweller.org> <20090718111753.GB1355@localhost.localdomain> Message-ID: <20090718180348.GD17289@localhost.localdomain> On Sat, Jul 18, 2009 at 10:19:38AM -0400, David Nalley wrote: > On Sat, Jul 18, 2009 at 7:17 AM, Paul W. Frields wrote: > > On Fri, Jul 17, 2009 at 10:44:21PM -0500, Ian Weller wrote: > >> On Fri, Jul 17, 2009 at 07:21:09PM -0400, Paul W. Frields wrote: > >> > I got a couple steps further on Zikula, after I fixed my system from > >> > being bitten by a missing nss-mdns.x86_64 package: > >> > > >> > * Ian Weller got me briefed on how to do a good package review these > >> > ? days > >> > > >> > * Got a package review done for David Nalley (php-File-Bittorrent2) > >> > > >> > * Started working on Mediashare module > >> > > >> > * Buffed up on how to package phpSmug properly > >> > > >> > Not as far as I would have liked to get, but per usual I had to fight > >> > my way past ignorance and inexperience to get there. ?The good news > >> > is, I'm ready to do better work this weekend if time allows! > >> > > >> Stuff I got done: > >> > >> - rebuilt the FE-ZIKULA dependency tree so that dependencies are in the > >> ? right places > >> ? - (please don't just tag everything related as FE-ZIKULA, if something > >> ? ? is blocking a review request or the like set that as the blocker) > >> - started working on MediaAttach and reached a level of doom emphasized > >> ? by licensing (noncommercial crapola) issues and bundled libraries > > > > The licensing situation in some of these modules is pretty ugly, no > > doubt. ?It's a great thing that the Zikula guys are working with us to > > resolve them, but I hope we can get traction soon since we'd like to > > have our system off the ground in August. > > > > And while they hate the pain of the work involved. they do realize > that this is beneficial to them. They are essentially getting a > licensing audit for free. And just as we are getting help from them, > we are returning that help. Nothing like a win-win! Karsten put it well here: http://iquaid.org/2009/07/16/fedora-zikula-infrastructure-of-freedom-ftw/ Paul From danielsmw at gmail.com Sun Jul 19 15:22:45 2009 From: danielsmw at gmail.com (Matthew Daniels) Date: Sun, 19 Jul 2009 11:22:45 -0400 Subject: Fedora Desktop Guide Update Message-ID: <17cd57cf0907190822x5ea41054n5d778e6175f025ce@mail.gmail.com> At last week's FDSCo meeting, I blabbered along for a few minutes concerning where I wanted to go with the User Guide (and, subsequently, that I thought we should rename it). I've put together a mock table of contents and a few sample paragraphs of the sort of style I envisioned in the rewritten guide. I'd appreciate any comments on other ways to address the audience, better topics to choose, or anything else that you feel would make it better. Please note that it's neither properly formatted nor spell/grammar-checked nor comprehensive in scope. I'm just looking for ideas before we get too far instead of after we've done half the guide. Links: http://danielsmw.fedorapeople.org/Guide.pdf http://danielsmw.fedorapeople.org/Guide.odt Also, because of the way this has been restyled, I think it could be easier for people to contribute; instead of delving into the full document and pulling out a scalpel to existing, messy content, people could just send me a paragraph or two on a particular question they care about or think is relevant. Cheers! - - -- --- ----- -------- ------------- --------------------- Matthew Daniels Fedora Project + danielsmw at gmail.com Clemson University + mdaniel at clemson.edu Home Page / Blog + people.clemson.edu/~mdaniel + danielsmw.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwulf at redhat.com Mon Jul 20 00:03:55 2009 From: jwulf at redhat.com (Joshua Wulf) Date: Mon, 20 Jul 2009 10:03:55 +1000 Subject: Fedora Desktop Guide Update In-Reply-To: <17cd57cf0907190822x5ea41054n5d778e6175f025ce@mail.gmail.com> References: <17cd57cf0907190822x5ea41054n5d778e6175f025ce@mail.gmail.com> Message-ID: <4A63B46B.5000508@redhat.com> On 07/20/2009 01:22 AM, Matthew Daniels wrote: > At last week's FDSCo meeting, I blabbered along for a few minutes > concerning where I wanted to go with the User Guide (and, > subsequently, that I thought we should rename it). > > I've put together a mock table of contents and a few sample paragraphs > of the sort of style I envisioned in the rewritten guide. I'd > appreciate any comments on other ways to address the audience, better > topics to choose, or anything else that you feel would make it better. > > Please note that it's neither properly formatted nor > spell/grammar-checked nor comprehensive in scope. I'm just looking > for ideas before we get too far instead of after we've done half the > guide. > > Links: > http://danielsmw.fedorapeople.org/Guide.pdf > http://danielsmw.fedorapeople.org/Guide.odt > > Also, because of the way this has been > restyled, I think it could be easier for people to contribute; instead of delving into the full document and pulling out a scalpel to existing, messy content, people could just send me a paragraph or two on a particular question they care about or think is relevant. > > Cheers! > - - -- --- ----- -------- ------------- --------------------- > Matthew Daniels > Fedora Project > + danielsmw at gmail.com > Clemson University > + mdaniel at clemson.edu > Home Page / Blog > + people.clemson.edu/~mdaniel > + danielsmw.wordpress.com "Linux is an open source operating system created by Linus Torvalds in the early 1990s. " Maybe something about GNU and the FSF? -- Joshua J Wulf Manager Engineering Content Services Red Hat Asia Pacific eml: jwulf at redhat.com tel: +61 7 3514-8140 cel: +61 431 929 675 -------------- next part -------------- An HTML attachment was scrubbed... URL: From valent.turkovic at gmail.com Mon Jul 20 08:15:29 2009 From: valent.turkovic at gmail.com (Valent Turkovic) Date: Mon, 20 Jul 2009 10:15:29 +0200 Subject: Ultimate Linux Remote Control Message-ID: <64b14b300907200115s432da725w4d83693275829bf@mail.gmail.com> I have been building Linux media center and one thing that was missing was a great remote control. I was impressed with Fiire Chief remote, but it is too expensive and the Fiire company stopped making it ;( Then I found out that you can use Wiimote on Linux and that it costs 40$ on Ebay. This guide isn?t intended only for those with Media Centers, because you can use Wiimote as a remote for any desktop application, presentations or even games. There are some basic hardware requirement likes usb bluetooth dongle or bluetooth already built in your laptop and Nintendo Wiimote. This guide is more focused on Fedora but you can use it with OpenSuse, Arch and Ubuntu. The main difference is how to install tools, other things should be same. There is also an Ubuntu guide that you can use as parallel with this guide. If you are interested in this topic please read the full article at: http://kernelreloaded.blog385.com/index.php/archives/ultimate-linux-remote-control/ If you have any suggestions or questions please feel free to contact me. If somebody likes this article feel free to transfer it to Fedora Wiki. Cheers! -- 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 From foss.mailinglists at gmail.com Mon Jul 20 08:18:24 2009 From: foss.mailinglists at gmail.com (sankarshan) Date: Mon, 20 Jul 2009 13:48:24 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <9f45b2730907170727v5a954785gb85d0f40065a5f92@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> <9f45b2730907170727v5a954785gb85d0f40065a5f92@mail.gmail.com> Message-ID: <35586fc00907200118o5038ca0fmdec9406fd7647d77@mail.gmail.com> On Fri, Jul 17, 2009 at 7:57 PM, kishan goyal wrote: > wiki page made. link [1] Thank you. > pdf made. [2] Thanks again. Can you work on this a bit to have similar stylistic look as the other Fedora documents ? /sankarshan -- http://www.gutenberg.net - Fine literature digitally re-published http://www.plos.org - Public Library of Science http://www.creativecommons.org - Flexible copyright for creative work Sent from Raleigh, NC, United States From fabhoneydew at gmail.com Mon Jul 20 10:15:06 2009 From: fabhoneydew at gmail.com (kishan goyal) Date: Mon, 20 Jul 2009 15:45:06 +0530 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <35586fc00907200118o5038ca0fmdec9406fd7647d77@mail.gmail.com> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <35586fc00907120732o50153449x5c241cb92e216770@mail.gmail.com> <9f45b2730907170727v5a954785gb85d0f40065a5f92@mail.gmail.com> <35586fc00907200118o5038ca0fmdec9406fd7647d77@mail.gmail.com> Message-ID: <9f45b2730907200315h3f094d4bp6611f9c46d2f9197@mail.gmail.com> On Mon, Jul 20, 2009 at 1:48 PM, sankarshan wrote: >> pdf made. [2] > > Thanks again. Can you work on this a bit to have similar stylistic > look as the other Fedora documents ? okay. doing so. Regards, Kishan Goyal. From awilliam at redhat.com Mon Jul 20 19:02:16 2009 From: awilliam at redhat.com (Adam Williamson) Date: Mon, 20 Jul 2009 12:02:16 -0700 Subject: how can I help? In-Reply-To: <20090716220259.GD24072@calliope.phig.org> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> <20090716220259.GD24072@calliope.phig.org> Message-ID: <1248116536.6035.37.camel@adam.local.net> On Thu, 2009-07-16 at 15:02 -0700, Karsten Wade wrote: > Great! We are seeing a lot of interest in using the wiki for writing > general-purpose how-to documentation. > > I wonder ... would it be useful for people to read fedora-list, > fedoraforum.org, and talk with moderators on #fedora about common > issues, then turn those in to short articles on the wiki? The next > thing is, of course, to post back to that thread (email, forum) with a > link to the new canonical wiki source for that answer. > > We were talking earlier today about a knowledge base (kbase). That is > another great idea, focused on much shorter articles to solve a > specific problem. While that is being researched, why not start > writing content in to the wiki? > > It would be a good idea to add a category at the bottom of each > article, such as: > > [[Category:Kbase article]] > [[Category:Kbase article draft]] > [[Category:Kbase food]] I hate to be a stop-energy-spreader, but I'm not a big fan of the 'ten thousand tiny pages' school of documentation. It winds up with two major drawbacks: you can't ever find anything, and nothing gets updated. (Visit the Gentoo wiki to observe both in operation). Most issues that are encountered on #fedora or forums, for instance, should be documented in either the Common Issues page, or the Release Notes. This was mostly what my earlier (long) email to the list was about, which no-one seemed to reply to. I really think it's better to keep things in some semblance of organization in central, canonical pages, rather than having zillions of single-issue pages... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net From eric at christensenplace.us Mon Jul 20 19:09:52 2009 From: eric at christensenplace.us (Eric Christensen) Date: Mon, 20 Jul 2009 15:09:52 -0400 Subject: Release Notes Meeting In-Reply-To: References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> <20090707211840.GI2867@localhost.localdomain> <1247009111.2310.35.camel@ericlaptop.christensenplace.us> Message-ID: On Tue, Jul 14, 2009 at 15:47, Eric Christensen wrote: > On Tue, Jul 7, 2009 at 19:25, Eric Christensen wrote: >> On Tue, 2009-07-07 at 17:18 -0400, Paul W. Frields wrote: >>> On Tue, Jul 07, 2009 at 04:50:40PM -0400, John J. McDonough wrote: >>> > Since the web page makes no mention of time zone, is it safe to assume >>> > that they are UTC? >>> >>> The app relies on the organizer to set the "use timezones" flag, then >>> respondents indicate their timezone in their reply and the times are >>> magically set up properly for local time. >> >> And the organizer has now activated the tz flag. >> >> Eric >> > > Okay, we really didn't have a good match. ?I've added another week on > to the whenisgood[1] so we can try again. > > [1] http://whenisgood.net/UbMSZS > > Eric > It would seem that this Thursday at 11:00 (EDT) (15:00 UTC) is the best time for most of our main players to meet. Is this still good? Eric From ricky at fedoraproject.org Mon Jul 20 19:28:18 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Mon, 20 Jul 2009 15:28:18 -0400 Subject: how can I help? In-Reply-To: <1248116536.6035.37.camel@adam.local.net> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> <20090716220259.GD24072@calliope.phig.org> <1248116536.6035.37.camel@adam.local.net> Message-ID: <20090720192818.GE10719@alpha.rzhou.org> On 2009-07-20 12:02:16 PM, Adam Williamson wrote: > I hate to be a stop-energy-spreader, but I'm not a big fan of the 'ten > thousand tiny pages' school of documentation. It winds up with two major > drawbacks: you can't ever find anything, and nothing gets updated. > (Visit the Gentoo wiki to observe both in operation). I think prioritizing documentation can help with this. For example, a list of wiki pages/things that absolutely most be updated every release (does anything like this currently exist?) I hate to keep picking on these few points, and this is not meant to put down our docs in any way, but I think the issue of http://docs.fedoraproject.org/install-guide/f11/en-US/html/ vs. http://en.opensuse.org/INSTALL_Local http://en.opensuse.org/Installation/11.1_Live_CD is a very serious one. Our organized, comprehensive docs definitely have their place, but the unfortunate fact is that some new users will be scared off by the table of contents alone. This is where specific, task-based documentation (with an eye towards the defaults) is very useful. > Most issues that are encountered on #fedora or forums, for instance, > should be documented in either the Common Issues page, or the Release > Notes. This was mostly what my earlier (long) email to the list was > about, which no-one seemed to reply to. I really think it's better to > keep things in some semblance of organization in central, canonical > pages, rather than having zillions of single-issue pages... Where will the (currently nonexistent) docs about how to properly setup Apache go, for example? I don't think we can get much worse than the kind of outdatedness that you get with: http://www.google.com/search?q=fedora+apache vs. http://www.google.com/search?q=opensuse+apache (this is also partially in response to your comment about docs being hard to find) Here's an example that happens to be commonly used in #fedora - currently the first search result for fedora sudo, I'm happy to say. http://fedorasolved.org/post-install-solutions/sudo This is the kind of documentation that I think we need for many common tasks. Perhaps if each of our HOWTO pages had a header listing the applicable Fedora releases and date when the HOWTO was last updated? I think that something would be better than the nothing that we have now. I'm sorry for constantly regurgitating these same old examples, but I think they're indicative of where we currently stand in how the documentation that we have is presented to users, and I hope they show a few approaches that we can consider taking to improve the situation. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From r.landmann at redhat.com Mon Jul 20 20:24:59 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Tue, 21 Jul 2009 06:24:59 +1000 Subject: how can I help? In-Reply-To: <20090720192818.GE10719@alpha.rzhou.org> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> <20090716220259.GD24072@calliope.phig.org> <1248116536.6035.37.camel@adam.local.net> <20090720192818.GE10719@alpha.rzhou.org> Message-ID: <4A64D29B.8000606@redhat.com> On 07/21/2009 05:28 AM, Ricky Zhou wrote: > I hate to keep picking on these few points, and this is not meant to put > down our docs in any way, but I think the issue of > > http://docs.fedoraproject.org/install-guide/f11/en-US/html/ > > vs. > > http://en.opensuse.org/INSTALL_Local > http://en.opensuse.org/Installation/11.1_Live_CD > > is a very serious one. > I now have a draft of the Installation Quick Start Guide available in html[1] and pdf[2] format. Feedback is most welcome, after which I'd like to take the draft tags off and put up a copy on docs.fp.o. I'll hold off from preparing PO files pending comments, but hopefully, this will be a very light load for L10N, since the vast bulk of the text comes from the existing Installation Guide and the "Readme:Live image" document. Cheers Rudi [1] http://rlandmann.fedorapeople.org/IQSG/en-US/html-single/ [2] http://rlandmann.fedorapeople.org/IQSG/en-US/pdf/Installation_Quick_Start_Guide.pdf From stickster at gmail.com Mon Jul 20 21:53:38 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 20 Jul 2009 17:53:38 -0400 Subject: Release Notes Meeting In-Reply-To: References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> <20090707211840.GI2867@localhost.localdomain> <1247009111.2310.35.camel@ericlaptop.christensenplace.us> Message-ID: <20090720215338.GQ4200@localhost.localdomain> On Mon, Jul 20, 2009 at 03:09:52PM -0400, Eric Christensen wrote: > On Tue, Jul 14, 2009 at 15:47, Eric Christensen wrote: > > On Tue, Jul 7, 2009 at 19:25, Eric Christensen wrote: > >> On Tue, 2009-07-07 at 17:18 -0400, Paul W. Frields wrote: > >>> On Tue, Jul 07, 2009 at 04:50:40PM -0400, John J. McDonough wrote: > >>> > Since the web page makes no mention of time zone, is it safe to assume > >>> > that they are UTC? > >>> > >>> The app relies on the organizer to set the "use timezones" flag, then > >>> respondents indicate their timezone in their reply and the times are > >>> magically set up properly for local time. > >> > >> And the organizer has now activated the tz flag. > > > > Okay, we really didn't have a good match. ?I've added another week on > > to the whenisgood[1] so we can try again. > > > > [1] http://whenisgood.net/UbMSZS > > It would seem that this Thursday at 11:00 (EDT) (15:00 UTC) is the > best time for most of our main players to meet. Is this still good? This week it might possibly be difficult, but usually it will be no problem. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From stickster at gmail.com Mon Jul 20 21:55:26 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 20 Jul 2009 17:55:26 -0400 Subject: how can I help? In-Reply-To: <20090720192818.GE10719@alpha.rzhou.org> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> <20090716220259.GD24072@calliope.phig.org> <1248116536.6035.37.camel@adam.local.net> <20090720192818.GE10719@alpha.rzhou.org> Message-ID: <20090720215526.GR4200@localhost.localdomain> On Mon, Jul 20, 2009 at 03:28:18PM -0400, Ricky Zhou wrote: > On 2009-07-20 12:02:16 PM, Adam Williamson wrote: > > I hate to be a stop-energy-spreader, but I'm not a big fan of the 'ten > > thousand tiny pages' school of documentation. It winds up with two major > > drawbacks: you can't ever find anything, and nothing gets updated. > > (Visit the Gentoo wiki to observe both in operation). > I think prioritizing documentation can help with this. For example, > a list of wiki pages/things that absolutely most be updated every > release (does anything like this currently exist?) > > I hate to keep picking on these few points, and this is not meant to put > down our docs in any way, but I think the issue of > > http://docs.fedoraproject.org/install-guide/f11/en-US/html/ > > vs. > > http://en.opensuse.org/INSTALL_Local > http://en.opensuse.org/Installation/11.1_Live_CD > > is a very serious one. Our organized, comprehensive docs definitely > have their place, but the unfortunate fact is that some new users will > be scared off by the table of contents alone. This is where specific, > task-based documentation (with an eye towards the defaults) is very useful. How much could we avoid that scare by tuning the table of contents to look more like what you see in the corner of a yelp screen? I.e., chapter titles only, with a more detailed listing at the beginning of the chapter itself? This doesn't solve everything, but incremental steps help. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From awilliam at redhat.com Mon Jul 20 23:07:56 2009 From: awilliam at redhat.com (Adam Williamson) Date: Mon, 20 Jul 2009 16:07:56 -0700 Subject: how can I help? In-Reply-To: <20090720192818.GE10719@alpha.rzhou.org> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> <20090716220259.GD24072@calliope.phig.org> <1248116536.6035.37.camel@adam.local.net> <20090720192818.GE10719@alpha.rzhou.org> Message-ID: <1248131276.6035.46.camel@adam.local.net> On Mon, 2009-07-20 at 15:28 -0400, Ricky Zhou wrote: > On 2009-07-20 12:02:16 PM, Adam Williamson wrote: > > I hate to be a stop-energy-spreader, but I'm not a big fan of the 'ten > > thousand tiny pages' school of documentation. It winds up with two major > > drawbacks: you can't ever find anything, and nothing gets updated. > > (Visit the Gentoo wiki to observe both in operation). > I think prioritizing documentation can help with this. For example, > a list of wiki pages/things that absolutely most be updated every > release (does anything like this currently exist?) I don't believe so. What I'd really like to see in this area would be the smart use of templates (this is something Wikipedia does to some extent); we could use these both to mark pages that will need regular attention, and to do some kinds of stuff automatically (for instance, if we had a {{version|current}} template - or something like that - it'd help immensely; there are many pages which just want to mention the number of the current release, for whatever reason. This may exist without me knowing about it, I don't discount the possibility :>) > I hate to keep picking on these few points, and this is not meant to put > down our docs in any way, but I think the issue of > > http://docs.fedoraproject.org/install-guide/f11/en-US/html/ > > vs. > > http://en.opensuse.org/INSTALL_Local > http://en.opensuse.org/Installation/11.1_Live_CD > > is a very serious one. > Where will the (currently nonexistent) docs about how to properly setup > Apache go, for example? I don't think we can get much worse than the > kind of outdatedness that you get with: These are both good examples; if that's the kind of thing you're talking about I can't give a better idea than a Wiki / knowledge base article, from a documentation perspective. There's an argument that this information should be in the application documentation and if the instructions for Fedora differ significantly from what the upstream instructions are / should be, that's a bug...but that's a tricky area. > Here's an example that happens to be commonly used in #fedora - > currently the first search result for fedora sudo, I'm happy to say. > > http://fedorasolved.org/post-install-solutions/sudo > > This is the kind of documentation that I think we need for many common > tasks. Yeah, that's another good example. When I saw the word 'issues' I was kind of keying on 'bugs'. I don't think a Wiki page for every little task like this is a really awesome way to do things, but equally I've never been able to come up with a better one :\ > Perhaps if each of our HOWTO pages had a header listing the applicable > Fedora releases and date when the HOWTO was last updated? I think that > something would be better than the nothing that we have now. A header's OK, but you can't get to that information very easily. I'm sure we could think of something better, so we could have a way to know very easily when a page might be out of date... > I'm sorry for constantly regurgitating these same old examples, but I > think they're indicative of where we currently stand in how the > documentation that we have is presented to users, and I hope they show a > few approaches that we can consider taking to improve the situation. Nope, I certainly see where you're coming from, and I can't argue on those examples. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net From wb8rcr at arrl.net Mon Jul 20 23:53:32 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 20 Jul 2009 19:53:32 -0400 Subject: how can I help? References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com><15B2519003F145F6B486334DF6970C57@Aidan><653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com><20090716220259.GD24072@calliope.phig.org><1248116536.6035.37.camel@adam.local.net><20090720192818.GE10719@alpha.rzhou.org> <1248131276.6035.46.camel@adam.local.net> Message-ID: ----- Original Message ----- From: "Adam Williamson" To: "For participants of the Documentation Project" Sent: Monday, July 20, 2009 7:07 PM Subject: Re: how can I help? The problem with the XML docs is that they are imposing. The problem with the wiki is that you can't find anything. And find means not only the user finding things, but the maintainers. The one thing that I *can* find on the wiki is the release notes beat pages, and that is only because I know where the index is. Most of the other pages have nothing pointing to them, so you can only find a page by sheer dumb luck. We had hoped to make the search function useable by renaming the pages, but that doesn't seem to have succeeded, and we lost the ability to navigate a tree in the attempt. I wonder whether the release notes model isn't a good one for the other docs? That is, write the doc in the wiki, and then nearing release convert it to xml. With some sort of table of contents pages, the data might actually be findable. The wiki offers us something else that the XML does not; pages can be organized in multiple ways. We could, for example, have a page that describes writing a letter in OO. This could be pointed to by the "task" table of contents "how to write a letter" as well as by the Open Office table of contents, using OOWriter.. if the individual pages were somewhat atomic, we might find that some fragments of content could be used in more than one document. Just some rambling. --McD From wb8rcr at arrl.net Mon Jul 20 23:54:36 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 20 Jul 2009 19:54:36 -0400 Subject: Release Notes Meeting References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan><20090707211840.GI2867@localhost.localdomain> <1247009111.2310.35.camel@ericlaptop.christensenplace.us> Message-ID: ----- Original Message ----- From: "Eric Christensen" To: "For participants of the Documentation Project" Sent: Monday, July 20, 2009 3:09 PM Subject: Re: Release Notes Meeting > It would seem that this Thursday at 11:00 (EDT) (15:00 UTC) > is the best time for most of our main players to meet. Is this > still good? Looks OK from here --McD From oglesbyzm at gmail.com Tue Jul 21 06:02:55 2009 From: oglesbyzm at gmail.com (Zach Oglesby) Date: Tue, 21 Jul 2009 08:02:55 +0200 Subject: Release Notes Meeting In-Reply-To: References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> <20090707211840.GI2867@localhost.localdomain> <1247009111.2310.35.camel@ericlaptop.christensenplace.us> Message-ID: <20090721060255.GA8959@zaphod.zach.tk> On Mon, Jul 20, 2009 at 03:09:52PM -0400, Eric Christensen wrote: > It would seem that this Thursday at 11:00 (EDT) (15:00 UTC) is the > best time for most of our main players to meet. Is this still good? > > Eric I will be there as long as my wife is not in labor! -- Zach Oglesby GPG Key: 1378F79F http://fedoraproject.org/wiki/User:Zoglesby -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From stickster at gmail.com Tue Jul 21 12:35:16 2009 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 21 Jul 2009 08:35:16 -0400 Subject: how can I help? In-Reply-To: <1248131276.6035.46.camel@adam.local.net> References: <653b25610907140830kf6678e8j9343e97f7399e30e@mail.gmail.com> <15B2519003F145F6B486334DF6970C57@Aidan> <653b25610907151339t7ab07f3ejc0fae034569b0e8e@mail.gmail.com> <20090716220259.GD24072@calliope.phig.org> <1248116536.6035.37.camel@adam.local.net> <20090720192818.GE10719@alpha.rzhou.org> <1248131276.6035.46.camel@adam.local.net> Message-ID: <20090721123516.GF1753@localhost.localdomain> On Mon, Jul 20, 2009 at 04:07:56PM -0700, Adam Williamson wrote: > On Mon, 2009-07-20 at 15:28 -0400, Ricky Zhou wrote: > > On 2009-07-20 12:02:16 PM, Adam Williamson wrote: > > > I hate to be a stop-energy-spreader, but I'm not a big fan of the 'ten > > > thousand tiny pages' school of documentation. It winds up with two major > > > drawbacks: you can't ever find anything, and nothing gets updated. > > > (Visit the Gentoo wiki to observe both in operation). > > > > I think prioritizing documentation can help with this. For example, > > a list of wiki pages/things that absolutely most be updated every > > release (does anything like this currently exist?) > > I don't believe so. What I'd really like to see in this area would be > the smart use of templates (this is something Wikipedia does to some > extent); we could use these both to mark pages that will need regular > attention, and to do some kinds of stuff automatically (for instance, if > we had a {{version|current}} template - or something like that - it'd > help immensely; there are many pages which just want to mention the > number of the current release, for whatever reason. This may exist > without me knowing about it, I don't discount the possibility :>) We do already have this -- refer to the following pages: https://fedoraproject.org/wiki/Template:FedoraVersion https://fedoraproject.org/wiki/Template:FedoraVersionName https://fedoraproject.org/wiki/Template:FedoraVersionNumber I like the idea of the "Update these pages every release" page. That page should definitely then be linked on John Poelstra's release schedule (maybe in Docs) as a task, i.e. "Update all pages listed on the '' page," and a target date for that to happen, probably the night before or day of release. > > I hate to keep picking on these few points, and this is not meant to put > > down our docs in any way, but I think the issue of > > > > http://docs.fedoraproject.org/install-guide/f11/en-US/html/ > > > > vs. > > > > http://en.opensuse.org/INSTALL_Local > > http://en.opensuse.org/Installation/11.1_Live_CD > > > > is a very serious one. By the way, I think that adding a page like this to the wiki is very easy. However, if you actually read that page, you're going to find that it's utterly useless at providing any information or answering any questions about what's going on, beyond "What does this screen mean?". It's a nice tour of the screenshots that works only for someone who just clicks next, next, next -- nothing more. I'm not saying we shouldn't have something like that, just that this particular document has a very different purpose than the Installation Guide, which actually tells you (if you read it) important information about how to set up your installation. > > Where will the (currently nonexistent) docs about how to properly setup > > Apache go, for example? I don't think we can get much worse than the > > kind of outdatedness that you get with: > > These are both good examples; if that's the kind of thing you're talking > about I can't give a better idea than a Wiki / knowledge base article, > from a documentation perspective. There's an argument that this > information should be in the application documentation and if the > instructions for Fedora differ significantly from what the upstream > instructions are / should be, that's a bug...but that's a tricky area. Since the upstream instructions almost always include "download from here, then compile from source," I think the trickiness is unavoidable! :-) > > Here's an example that happens to be commonly used in #fedora - > > currently the first search result for fedora sudo, I'm happy to say. > > > > http://fedorasolved.org/post-install-solutions/sudo > > > > This is the kind of documentation that I think we need for many common > > tasks. > > Yeah, that's another good example. When I saw the word 'issues' I was > kind of keying on 'bugs'. I don't think a Wiki page for every little > task like this is a really awesome way to do things, but equally I've > never been able to come up with a better one :\ > > > Perhaps if each of our HOWTO pages had a header listing the applicable > > Fedora releases and date when the HOWTO was last updated? I think that > > something would be better than the nothing that we have now. > > A header's OK, but you can't get to that information very easily. I'm > sure we could think of something better, so we could have a way to know > very easily when a page might be out of date... Mediawiki does tell you the last time a page was updated in the footer of every page it displays. If you need it someplace in the content, you can use the info at http://meta.wikimedia.org/wiki/Help:Variable to do so. {{REVISIONTIMESTAMP}} <-- a bit harder to read {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} <-- easier to read Categories are probably the best way to do this. If it were me, I'd probably consider categorizing pages in the releases to which they apply, which makes things simple. So for example, a category on how to set up sudo would include: [[Category:Howto]] [[Category:F9]] [[Category:F10]] [[Category:F11]] -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From kwade at redhat.com Wed Jul 22 07:29:36 2009 From: kwade at redhat.com (Karsten Wade) Date: Wed, 22 Jul 2009 00:29:36 -0700 Subject: [mmaslano@fedoraproject.org: [relnotes] rpms/cronie/devel .cvsignore, 1.5, 1.6 cronie.spec, 1.18, 1.19 sources, 1.5, 1.6] Message-ID: <20090722072936.GJ12672@calliope.phig.org> Well, will ya look at that! The *docs* keyword in a CVS commit log still works. ----- Forwarded message from Marcela Ma?l??ov? ----- From: Marcela Ma?l??ov? To: relnotes at fedoraproject.org Date: Mon, 20 Jul 2009 18:12:37 +0000 (UTC) Cc: Subject: [relnotes] rpms/cronie/devel .cvsignore, 1.5, 1.6 cronie.spec, 1.18, 1.19 sources, 1.5, 1.6 X-BeenThere: fedora-relnotes-content at redhat.com Author: mmaslano Update of /cvs/pkgs/rpms/cronie/devel In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv19635 Modified Files: .cvsignore cronie.spec sources Log Message: *docs* For better cooperation between cronie and anacron, cronie now include anacron as a subpackage. Each hour cron executes scripts from cron.hourly which contains 0anacron executable. 0anacron script checks whether the regular jobs - cron.daily, cron.weekly and cron.monthly - were executed or not. The list of all regular jobs is in /etc/regular-jobs instead of /etc/crontab. Manual pages mentioned options how to set up regularly-jobs to behave the same way as in the previous versions of cron. Index: .cvsignore =================================================================== RCS file: /cvs/pkgs/rpms/cronie/devel/.cvsignore,v retrieving revision 1.5 retrieving revision 1.6 diff -u -p -r1.5 -r1.6 --- .cvsignore 27 Apr 2009 10:22:21 -0000 1.5 +++ .cvsignore 20 Jul 2009 18:12:36 -0000 1.6 @@ -1 +1 @@ -cronie-1.3.tar.gz +cronie-1.4.tar.gz Index: cronie.spec =================================================================== RCS file: /cvs/pkgs/rpms/cronie/devel/cronie.spec,v retrieving revision 1.18 retrieving revision 1.19 diff -u -p -r1.18 -r1.19 --- cronie.spec 18 Jun 2009 11:42:28 -0000 1.18 +++ cronie.spec 20 Jul 2009 18:12:36 -0000 1.19 @@ -5,19 +5,16 @@ Summary: Cron daemon for executing programs at set times Name: cronie -Version: 1.3 -Release: 2%{?dist} -License: MIT and BSD +Version: 1.4 +Release: 1%{?dist} +License: MIT and BSD and GPLv2 Group: System Environment/Base URL: https://fedorahosted.org/cronie Source0: https://fedorahosted.org/releases/c/r/cronie/%{name}-%{version}.tar.gz -Patch0: reboot-alias-check-the-return-value.patch -#Source0: http://mmaslano.fedorapeople.org/cronie/%{name}-%{version}.tar.gz Buildroot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) Requires: syslog, bash >= 2.0 Requires: /usr/sbin/sendmail -Requires: anacron Conflicts: sysklogd < 1.4.1 Provides: vixie-cron = 4:4.4 Obsoletes: vixie-cron <= 4:4.3 @@ -46,9 +43,18 @@ scheduled times and related tools. It is has security and configuration enhancements like the ability to use pam and SELinux. +%package anacron +Summary: Utility for running regular jobs +Requires: crontabs +Group: System Environment/Base + +%description anacron +Anacron becames part of cronie. Anacron is used only for running regular jobs. +The default settings execute regular jobs by anacron, however this could be +overloaded in settings. + %prep %setup -q -%patch0 -p1 %build @@ -63,8 +69,10 @@ SELinux. --with-audit \ %endif %if %{with inotify} ---with-inotify +--with-inotify \ %endif +--enable-anacron + make %{?_smp_mflags} %install @@ -80,6 +88,10 @@ mkdir -pm755 $RPM_BUILD_ROOT%{_sysconfdi install -m 755 cronie.init $RPM_BUILD_ROOT%{_initrddir}/crond install -m 644 crond.sysconfig $RPM_BUILD_ROOT%{_sysconfdir}/sysconfig/crond touch $RPM_BUILD_ROOT%{_sysconfdir}/cron.deny +install -m 644 contrib/regularly-jobs $RPM_BUILD_ROOT%{_sysconfdir}/regularly-jobs +install -c -m755 contrib/0hourly $RPM_BUILD_ROOT%{_sysconfdir}/cron.d/0hourly +mkdir -pm 755 $RPM_BUILD_ROOT%{_sysconfdir}/cron.hourly +install -c -m755 contrib/0anacron $RPM_BUILD_ROOT%{_sysconfdir}/cron.hourly/0anacron %clean rm -rf $RPM_BUILD_ROOT @@ -125,8 +137,21 @@ cp -a /var/lock/subsys/crond /var/lock/s %endif %config(noreplace) %{_sysconfdir}/sysconfig/crond %config(noreplace) %{_sysconfdir}/cron.deny +%config(noreplace) %{_sysconfdir}/regularly-jobs + +%files anacron +%defattr(-,root,root,-) +%{_sbindir}/anacron +%attr(0644,root,root) %{_sysconfdir}/cron.d/0hourly +%attr(0755,root,root) %{_sysconfdir}/cron.hourly/0anacron +%{_mandir}/man5/regularly-jobs.* +%{_mandir}/man5/anacrontab.* +%{_mandir}/man8/anacron.* %changelog +* Mon Jul 20 2009 Marcela Ma?l??ov? - 1.4-1 +- merge cronie and anacron + * Thu Jun 18 2009 Marcela Ma?l??ov? - 1.3-2 - 506560 check return value of access Index: sources =================================================================== RCS file: /cvs/pkgs/rpms/cronie/devel/sources,v retrieving revision 1.5 retrieving revision 1.6 diff -u -p -r1.5 -r1.6 --- sources 27 Apr 2009 10:22:22 -0000 1.5 +++ sources 20 Jul 2009 18:12:36 -0000 1.6 @@ -1 +1 @@ -dbb21448103e80c61d0a2c0f6ec2475c cronie-1.3.tar.gz +10728a81af9f5995a39bf541aaf14422 cronie-1.4.tar.gz -- Fedora-relnotes-content mailing list Fedora-relnotes-content at redhat.com https://www.redhat.com/mailman/listinfo/fedora-relnotes-content ----- End forwarded message ----- -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From stickster at gmail.com Wed Jul 22 11:54:17 2009 From: stickster at gmail.com (Paul W. Frields) Date: Wed, 22 Jul 2009 07:54:17 -0400 Subject: [mmaslano@fedoraproject.org: [relnotes] rpms/cronie/devel .cvsignore, 1.5, 1.6 cronie.spec, 1.18, 1.19 sources, 1.5, 1.6] In-Reply-To: <20090722072936.GJ12672@calliope.phig.org> References: <20090722072936.GJ12672@calliope.phig.org> Message-ID: <20090722115417.GE21921@localhost.localdomain> On Wed, Jul 22, 2009 at 12:29:36AM -0700, Karsten Wade wrote: > Well, will ya look at that! The *docs* keyword in a CVS commit log > still works. [...snip...] > Modified Files: > .cvsignore cronie.spec sources > Log Message: > *docs* > For better cooperation between cronie and anacron, cronie now include anacron as a subpackage. > Each hour cron executes scripts from cron.hourly which contains 0anacron executable. > 0anacron script checks whether the regular jobs - cron.daily, cron.weekly and cron.monthly > - were executed or not. The list of all regular jobs is in /etc/regular-jobs instead of > /etc/crontab. Manual pages mentioned options how to set up regularly-jobs to behave the > same way as in the previous versions of cron. [...snip...] Well, now I know why I saw the anacron package get dropped in the rel-eng Trac! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From eric at christensenplace.us Wed Jul 22 12:18:33 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 22 Jul 2009 08:18:33 -0400 Subject: Fedora Docs Meeting Reminder Message-ID: <1248265124.3521.17.camel@echristensen.tkctech.com> REMINDER: There will be a Fedora Docs Meeting today at 0001 UTC. The agenda can be found at: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting. If you have anything you'd like to discuss please add it to the agenda prior to 2330 UTC. Thanks, Eric From bugzilla at redhat.com Wed Jul 22 14:54:48 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 10:54:48 -0400 Subject: [Bug 164648] Need docs in more formats on web site In-Reply-To: References: Message-ID: <200907221454.n6MEsmFY001014@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=164648 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CURRENTRELEASE Flag|needinfo? | --- Comment #2 from Eric Christensen 2009-07-22 10:54:46 EDT --- Closing this one for now. We'll make it standard procedure to create all Publican-based guides in HTML (multi-page), HTML (single-page), and PDF. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From bugzilla at redhat.com Wed Jul 22 15:00:34 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 11:00:34 -0400 Subject: [Bug 504064] Publican migration In-Reply-To: References: Message-ID: <200907221500.n6MF0Y9K002272@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504064 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|needinfo? | --- Comment #2 from Eric Christensen 2009-07-22 11:00:33 EDT --- I think the RPM Guide is the only guide left to be transitioned. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Wed Jul 22 15:15:21 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 11:15:21 -0400 Subject: [Bug 508930] Move RPM Guide to wiki In-Reply-To: References: Message-ID: <200907221515.n6MFFL2e006638@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508930 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |DEFERRED --- Comment #2 from Eric Christensen 2009-07-22 11:15:20 EDT --- Guide has been adopted and is being Publicanized. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From bugzilla at redhat.com Wed Jul 22 22:46:56 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 18:46:56 -0400 Subject: [Bug 508382] Package Advanced Voting System for Zikula In-Reply-To: References: Message-ID: <200907222246.n6MMku6N001780@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508382 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|fedora-docs-list at redhat.com |eric at christensenplace.us QAContact|eric at christensenplace.us |fedora-docs-list at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. From bugzilla at redhat.com Wed Jul 22 22:46:13 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 18:46:13 -0400 Subject: [Bug 508379] Need to package "Simple Voting System" In-Reply-To: References: Message-ID: <200907222246.n6MMkDqR003272@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508379 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|fedora-docs-list at redhat.com |eric at christensenplace.us QAContact|eric at christensenplace.us |fedora-docs-list at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. From dlbewley at lib.ucdavis.edu Wed Jul 22 23:13:11 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 22 Jul 2009 16:13:11 -0700 Subject: Release Notes Meeting In-Reply-To: References: <1246998251.2310.34.camel@ericlaptop.christensenplace.us> <8FA0AA1630534751A9DE5EB47DD95E15@Aidan> <20090707211840.GI2867@localhost.localdomain> <1247009111.2310.35.camel@ericlaptop.christensenplace.us> Message-ID: <1248304391.3991.6.camel@tofu.lib.ucdavis.edu> On Mon, 2009-07-20 at 15:09 -0400, Eric Christensen wrote: > It would seem that this Thursday at 11:00 (EDT) (15:00 UTC) is the > best time for most of our main players to meet. Is this still good? I have a meeting at 9 Pacific, but I'll jump on #fedora-meeting at 8 as the meeting starts. Or maybe I'm confused. I don't see it listed here. http://fedoraproject.org/wiki/Docs_Project_meetings From eric at christensenplace.us Thu Jul 23 01:21:43 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 22 Jul 2009 21:21:43 -0400 Subject: Docs Meeting 2009-07-22 IRC log Message-ID: <1248312114.5597.0.camel@echristensen.tkctech.com> 00:01:38 #startmeeting Docs Project - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings#Thursday_July_23.2C_2009_.28Wed_US_Time.29 00:01:47 Who is here? 00:01:47 * Sparks 00:01:59 * jjmcd is onna fone 00:02:08 I'm here 00:02:22 * bcotton is here for a change 00:02:27 * laubersm 00:02:45 * rudi is here 00:04:05 * Sparks gives everyone a few more minutes to get here. 00:04:18 * danielsmw is here 00:05:58 * stickster 00:06:33 Okay, let's get started. 00:06:35 #topic Status on CMS (Zikula) <-- ke4qqq 00:06:56 So we had a Zikula planning meeting this morning... 00:07:17 and discovered that our deployment schedule is slipping because of problems we are having... 00:07:28 getting some of the modules packaged. 00:08:01 * stickster notes current status is at https://fedoraproject.org/wiki/Zikula#Module_status 00:08:02 One of the bigger problems is that these modules have snippets of code or skins or icons that are... 00:08:18 licensed under other-than-GPL licenses. 00:08:23 Thanks stickster. 00:08:42 The link that stickster posted is the current status of all the modules. 00:09:08 I plan on working on a couple of items tonight. 00:09:30 We also need to identify if there are other modules that are needed to stand up Zikula for the other projects. 00:09:33 * stickster did some work this afternoon, will try to resolve his other action item if time allows tonight 00:09:41 Does anyone have any questions? 00:09:54 What is the action item for identifying those modules? 00:09:59 Who is doing it? 00:10:37 We don't have that. 00:10:40 I think if we can identify the actionable task, it's easier for someone to put up their hand and say, "I'd like to help." 00:10:48 agrees 00:11:03 So I ask you, what is needed to do that identification? 00:11:18 (anyone can answer, really) 00:11:25 * stickster puts question out on table for consideration 00:11:39 I'm not sure. Maybe nothing. 00:11:42 Um 00:11:58 Who are the people involved outside Docs? 00:12:14 * stickster looks at list and sees Fedora Insight and Fedora Weekly News 00:12:23 mchua was working on the Marketing people for their foobar project 00:12:25 That's Marketing team, and News team, right? 00:12:29 yes 00:12:41 So how can we put them in a position to identify modules? 00:12:54 Point them to the website? 00:13:12 Well, maybe there's something we could do that's less... I don't know, flailing 00:13:13 Actually we probably need to sit down with them and help identify things they want to do. 00:13:18 Aha! 00:13:20 awesome 00:13:46 So that's a list that really *anyone* could make 00:13:54 Yes 00:14:09 If a project needs a calendar or something then we need to make sure that can happen. 00:15:08 Would anyone like to step up and help Marketing and News make these decisions? 00:16:16 * ianweller rolls in 00:16:26 perspectival: You're new here, what would *you* like to do? 00:16:53 grin; I'm madly busy preparing some statements right now 00:16:59 thanks for the offer but pass for the moment 00:17:12 OK, moving on then. 00:17:12 * mchua pokes head in as well 00:17:18 Hi mchua! 00:17:41 We were just saying, we probably need to have someone in Docs working with each of the teams looking to leverage Zikula 00:18:09 Because we'll want to compile a list of needs you have, elementary ways of displaying content 00:18:11 like "we need a calendar" 00:18:24 or "we need a daily-rotating headline" 00:18:26 for the record, I've got it on my plate before next tuesday to nail down specs for Fedora Insight's zikula stuff from the Marketing side... and I have stickster and ianweller as the Marketing <--> Docs interfaces... anything else we need? 00:18:27 or something like that. 00:18:34 a pony? 00:18:54 Ah, I guess that's me for your team then 00:18:57 and ianweller 00:19:02 So who's left? News? 00:19:09 Yeah 00:19:37 OK, that seems like the not-covered bit 00:19:59 stickster: I haven't met with anyone from that group. 00:20:28 I know JonRob is working with them a bit, might be good for someone here to round up with him and maybe Pascal Calarco, who I think said he'd be willing to meet with someone to discuss their needs 00:20:44 * stickster is trying to make sure that someone in that group knows something about Zikula, or at least knows someone who does 00:21:00 Sparks: Why don't you take this one then 00:21:20 #action Sparks to follow up with the News people about Zikula 00:21:31 Okay, anything else on the Zikula subject? 00:21:39 or maybe "to met with News people and solicit a list of their needs" 00:21:43 s/met/meet/ 00:21:53 Yeah, that too 00:22:01 * stickster thinks the more explanatory and concise the actions are, the easier it is to track them at the next meeting 00:22:37 #action Sparks to meet with News people and solicit a list of their needs 00:22:48 Okay, moving on. 00:22:52 * stickster stands down since munchkin bedtime is coming up 00:23:01 #topic Status on CC license rollout. <-- ianweller 00:23:04 * ke4qqq is here 00:23:08 sorry for being late 00:23:23 ianweller: Where are we on announcing to the world that we are changing licenses? 00:25:16 ianweller: Hello? 00:25:42 * stickster wonders if ianweller is still stuck on RH's guest net 00:25:46 Sparks: oh sorry :( 00:25:52 stickster: no i'm at the hotel 00:26:17 Sparks: we should be announcing to the world via a quasi-press release to CC and to fedora-announce-list i guess 00:26:26 i believe 00:26:38 * ianweller apologizes again for wasting meeting time 00:26:41 ianweller: When is this going to happen? 00:26:55 Sparks: when do you want it to happen 00:27:00 we just need to write something up and push it 00:27:13 and by "we" i mean "not me tomorrow or friday" 00:27:21 ianweller: Are we waiting on something to happen? Do we announce and then go through the process of changing stuff? 00:27:41 you can go either way, the way you said or the reverse 00:27:46 i would recommend the way you said 00:27:56 announce that we're committing license changes, hten actuallydo work 00:27:58 oh god i can't type 00:28:08 Actually, it really should be the other way around IMHO 00:28:20 You announce what you've done (or maybe even are in the process of doing) 00:28:37 Otherwise it's too easy to announce, find a blocker, and then people wonder why you didn't do what you said you'd do. 00:28:43 hmm 00:28:54 ianweller: can you get something written this weekend? 00:28:59 ianweller: What specifically is the action to change? 00:29:05 Sparks: that's funny, i'll try ;) 00:29:06 i.e. text in the wiki? 00:29:07 ianweller: I'm assuming that the wiki would be easy. 00:29:08 * ianweller adds it to his todo 00:29:12 yes wiki 00:29:13 What else? 00:29:18 Guides 00:29:29 otoh, if we want to give people a chance to object, we should announce it a bit ahead of time. i guess we're assuming that anyone who might care is on fedora-docs or fedora-legal? 00:29:31 Which means a change to the Fedora brand in Publian 00:29:32 i really don't know what all docs does that is being changed quite frankly. 00:29:38 bcotton: We've already done that. 00:29:38 s/Publian/Publican 00:29:43 bcotton: we've done thta for about a month i htink 00:29:44 think* 00:29:44 Sparks -- easy 00:29:45 oh 00:29:46 dear 00:29:46 god 00:29:50 give me typing lessons again 00:30:01 rudi: yeah, but then rebuilding all the guides... 00:30:08 Sparks: how about this 00:30:12 Sparks: can you guys create a rollout plan? 00:30:20 and then i can definitely write an announcement 00:30:23 Do we have to do that immediately, or just as we republish them? 00:30:37 #action Sparks to write rollout plan for license change 00:30:45 rudi: don't know 00:30:59 #action ianweller to write press release 00:31:15 ianweller: writing press release?! 00:31:45 onekopaka_laptop: i'd recommend some scrollback 00:31:56 is there anything else? 00:32:04 rudi: Can you help me with the Fedora-brand stuff? 00:32:14 i'd really just like to see an order in how everything has to be changed before we start doing it 00:32:15 Sparks -- love to. 00:32:19 so we can check things off as we go. 00:32:24 ianweller: I don't think so. Where are we going to push the release? 00:32:27 Sparks, I'll be happy to provide you with a sounding board as you develop that 00:32:39 Sparks: fedora-announce-list and mlinksva at CC 00:32:56 can you think of anything else 00:33:06 are there any documentation thinktanks or the like around the internet 00:33:08 #action rudi to help sparks on changing the fedora-brand in Publican for CC license 00:33:19 ianweller: how about a RH Press Release? 00:33:25 oh hey 00:33:26 i can pull that off 00:33:34 and/or i can make quaid do it 00:33:38 jjmcd: Cool 00:33:53 ianweller: You can MAKE quaid do that? Wow, impressive 00:34:04 * stickster has to run 00:34:09 well i can suggest it to him 00:34:15 and to some people with more clout than me 00:34:15 :) 00:34:29 like spevack 00:34:30 * Sparks doesn't know many people with more clout than ianweller 00:34:36 i am the wiki czar. 00:34:45 ok i think we're done on this subject, we've got good action items. 00:34:48 * Sparks hears thunder whenever ianweller says that 00:34:52 lol 00:34:55 Cool... Anyone else? 00:35:17 #topic Shared open-source style guide <--ke4qqq 00:35:24 #link https://www.redhat.com/archives/fedora-docs-list/2009-June/msg00163.html 00:35:31 ke4qqq: Any development on this? 00:35:53 someone should follow ianweller around with a recording of thunder and play it whenever he says "I am the wiki czar" 00:36:03 Sparks: sadly no - real life has gotten in the way of GTD 00:36:14 I'll try and fix that by tonight though 00:36:18 ke4qqq: understood. 00:36:33 that RL stuff can be a real pain 00:37:04 tell me about it 00:37:19 Okay, we'll follow up next week. 00:37:25 #topic Outstanding BZ Tickets 00:37:36 #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW 00:37:53 There are sixteen NEW tickets that have not been assigned. 00:38:34 danielsmw: Can we move the software-management-guide into the user guide? 00:38:36 there are some we just should close won'tfit 00:38:46 wontfix 00:39:19 ke4qqq: I agree but I think we should make sure that we make an effort to address all of them or at least make sure they've been fixed. 00:39:30 Sparks: yes, we can 00:39:49 danielsmw: Okay, I'll push those tickets (maybe one or two) to you, then. 00:39:52 k 00:40:29 danielsmw: Actually, one... :) 00:42:20 There are 69 total bugs that are either NEW or ASSIGNED. If you haven't looked at your ticket queue lately please do so and make sure you are working on these problems. 00:42:25 Anything else? 00:42:45 Sparks: lets spend some time post meeting working on doing something with NEW stuff 00:42:59 ke4qqq: Cool 00:43:11 Okay, moving on. 00:43:14 #topic Guide needs? 00:43:26 Anyone have guides that need some help? 00:43:39 Anyone want to help out with a guide? 00:43:49 I'd like to demote myself on the IG 00:44:01 ke4qqq: Denied 00:44:02 next? 00:44:11 #link https://fedoraproject.org/wiki/Docs_Project_meetings#Guides 00:44:32 The above link shows all our current guides and their status. Please keep this up-to-date. 00:45:17 ke4qqq: Do you need help or is RL catching up with you? 00:45:53 well a combination of things - I don't want to be a constraint - rudi is already doing the bulk of the work, and is effectively leading the guide 00:46:15 rudi: thoughts? 00:46:21 I still want to work on it, but figure those doing the bulk of the work should make the decisions, and that's def. rudi in this case 00:46:43 Well ke4qqq has never been a constraint! 00:47:08 Well, I'll let you two work that out. 00:47:18 I don't think ke4qqq has ever been confused with a speed bump 00:47:44 Anything else? 00:48:04 #topic New Guides 00:48:15 Installation Quick Start Guide 00:48:17 Anyone have a new guide or a new idea they'd like to discuss for a guide? 00:48:25 rudi: go! 00:48:48 There was some discussion about this in the lead-up to F11, and a lot more on f-d-l lately 00:49:07 I've now built the book 00:49:21 and have drafts available for review: 00:49:26 html is here: http://rlandmann.fedorapeople.org/IQSG/en-US/html-single/ 00:49:28 pdf is here: http://rlandmann.fedorapeople.org/IQSG/en-US/pdf/Installation_Quick_Start_Guide.pdf 00:49:48 I mentioned this on the list, but got zero feedback so far. 00:50:03 I'd like people to take a look and offer comments, in particular on the scope of the thing 00:50:11 Too much? Too little? Wrong focus? 00:50:25 how do u want to receive comments? 00:50:52 rudi: Maybe we can put it on the announce list to get others involved? Maybe some of the IRC support people? 00:51:07 Just keep in mind the constraint that I'm trying to maintain as much commonality with the text of the IG and other existing docs as possible, to ease the load on L10N in maintaining two separate but overlapping books 00:51:26 ke4qqq -- f-d-l is probably best 00:51:36 rudi: Do you want a BZ component for this guide? 00:51:43 Sparks -- yes please 00:52:10 #action Sparks to create BZ component for Installation Quick Start Guide 00:52:12 For the moment, I've directed the BZ to the install-guide component, but a separate component will ease confusion 00:53:04 Trac is here, for anyone who wants to join in : https://fedorahosted.org/installation-quick-start-guide/ 00:53:19 excellent 00:53:33 rudi: I'll take a look at it soon. 00:53:39 rudi: Anything else? 00:53:55 Nope -- that's it from me :) 00:54:00 rudi: Thank you 00:54:05 Sparks, the Virt Guide is still coming. I am just swamped 00:54:25 Tsagadai: Excellent. 00:54:26 I should have xml up by next week, hopefully 00:54:39 Tsagadai: Is in Trac? 00:54:47 Trac and git are set up 00:54:51 +1 00:55:10 Tsagadai: Do you want a BZ component for the Virt Guide? 00:55:14 could you make me a BZ component, hopefully Virtualization_Guide 00:55:33 #action Sparks to create a BZ component for Virtualization Guide 00:55:39 Tsagadai: Anything else? 00:55:55 from Tsagadai or anyone? 00:56:03 * Sparks needs to get his keys on this laptop so he can do all this work! 00:56:10 perspectival: From Tsagadai at the moment. 00:56:12 that's it for me for now. I will have lots of xml coming in soon 00:56:19 Tsagadai: Thank you 00:56:28 perspectival: You have something for us? 00:56:41 sure! 00:56:49 I mentioned the Deployment Guide a few weeks ago, and the goood news is that I've nearly got it all set up (and the unfortunate news is, of course, is that it's going to take another hour or so) 00:56:50 in view of these circumstances, I think what I'll do is announce the Deployment Guide on fedora-docs-list as early as tomorrow (it's rather late here) 00:57:09 let me do a quick intro as to what the Deployment Guide is about 00:57:33 I plan for the Fedora Deployment Guide to cover system administration tasks such as user administration, package management, and setting up network interfaces and various servers and services such as Apache, LDAP, OpenSSH, Samba, etc. 00:58:04 * Sparks thinks it sounds kin to the Desktop User Guide 00:58:23 but maybe for more of an enterprise crowd 00:58:25 I see (as of a few minutes ago) that I'll need to add this book to Docs_Project_meetings#Guides 00:58:28 I think it's very different from the UG 00:58:34 * nirik has a short thing if there is an open floor at the end. ;) 00:58:46 For the reason that Sparks just noted :) 00:58:56 nirik: There will be 00:59:04 perspectival: Yes, please add your guide there. 00:59:08 The question is, can it be structured so that translations can be borrowed from the UG, IG, etc? 00:59:11 I think that's probably a good description (more geared towards the enterprise crowd) 00:59:27 jjmcd -- translations can be borrowed from the RHEL deployment guide 00:59:33 that's correct 00:59:34 ahhhh better yet 00:59:36 already translated into 22 languages 00:59:50 * Sparks tries to remember the talk on Fedora for the Enterprise that someone did at the Raleigh FUDCON 00:59:55 huh?? FDG is already in 22 langs? 01:00:04 no -- RHEL DG 01:00:08 ahhh ok 01:00:14 ;D 01:00:35 this is goodness that we are thinking about these things 01:01:24 any questions from me at the moment? I'll provide a lot more info in an email tomorrow (including the current draft, how to get it and where to look at it, etc.) 01:01:24 Cool 01:01:35 perspectival: Excellent. 01:01:45 perspectival -- I guess this overlaps with the RPM guide to some extent 01:02:04 rudi: that's true, though I haven't had the chance to compare the respective info yet 01:02:11 perspectival: Yeah, get with bcotton and see if the two guides are similar 01:02:15 will put that on the GTDToDo list 01:02:23 ok! 01:02:25 I think there was some talk about revamping that; the revamp may be a duplication of effort... 01:02:26 will do 01:03:21 Anyone else have a new guide they'd like to discuss? 01:04:04 Okay, moving on 01:04:10 #topic All other business 01:04:17 nirik: You have something for us? 01:04:43 Yeah, we are looking for teachers for classes and more students for Fedora IRC CLassroom. 01:04:44 https://fedoraproject.org/wiki/Classroom 01:04:53 please consider teaching on docs topics sometime. ;) 01:05:17 nirik: Anything specific? 01:05:28 nope... anything you desire. ;) 01:05:44 and we are using a model now where you can just schedule your class when you can teach... 01:05:49 * jjmcd will consider a class for new beat writers 01:05:54 and we might do a weekend of classes near release time. 01:06:00 jjmcd: Very good idea. 01:06:08 just schedule 2 weeks in advance so we can advertise it. 01:06:32 ? 01:06:38 ke4qqq: Yes? 01:06:46 * ke4qqq will wait til nirik is done 01:06:55 thats all I had, just letting folks know. 01:07:03 Please see me or the classroom list if you have questions... 01:07:14 rudi: any movement on the RH style guide?? 01:07:37 Sorry ke4qqq -- I've been bogged down and haven't pursued this yet 01:07:44 no worries, same story here 01:07:51 I'll make sure I follow it up today 01:07:56 Oh, I have something (should have been in the guides discussion) 01:08:23 * rudi has something else too (when Sparks is done) 01:08:30 We had an open ticket from a few years ago... 01:08:50 asking for more formats of our guides. 01:09:02 * danielsmw has to split; peace. 01:09:17 So is it a problem to create html, html-single, and pdf for all our guides and put them on docs.fp.o? 01:09:21 danielsmw: See ya! 01:09:39 AFAIK, pdf doesn't work again 01:09:45 just a bit more work and clutter IMO 01:09:49 jjmcd: There's a rouge patch out there. 01:09:55 ah 01:10:04 jjmcd -- it's on my Fedorapeople page 01:10:11 we really should solve the clutter problem before adding more content - the 30 some odd languages in one format is enough. 01:10:27 ke4qqq, I thought mo was going to sort that for us 01:10:33 41 for RNs 01:10:40 jjmcd -- rogue patch: http://rlandmann.fedorapeople.org/xslthl-2.0.0-1.fc11.noarch.rpm 01:10:44 ke4qqq: http://docs.fedoraproject.org/selinux-user-guide/ 01:10:54 ^^^ not so cluttered. 01:10:55 jjmcd: didn't we tell her to hold off pending zikula 01:11:15 Yes, when Zikula comes in all this might be different 01:11:17 that's not bad 01:11:19 maybe you're right, as soon as we handed it to her it went off my radar 01:11:45 ke4qqq: Yeah, it's a lot clearer. I built that as a "try". Could be fixed up even more. 01:11:49 * rudi notes that the licence change may provide a good opportunity to publish extra formats... 01:11:57 ke4qqq: We always get requests for whatever isn't there. 01:12:03 +1 01:12:12 But only 3 languages, and no "iso" 01:12:27 no iso? 01:12:46 language codes 01:12:55 I put the language codes in there. 01:13:00 For RN's we have "as released" as well as most current. As release is "iso", I presume because it was on the live cd 01:13:25 Sparks: ignore me, I missed the parens 01:13:47 Okay... Now if I could translate "single" into all the different languages I'd truely be happy 01:14:38 rudi: You had something else? 01:14:54 Yeah; I've checked in Publicanized versions of the "minor" docs packaged with the RN; these are now in translation. 01:15:06 I didn't do the "homepage" doc because I didn't know what its future is, and don't want to waste translators' time. 01:15:14 I noticed. Thank you! 01:15:19 * rudi notes that the module is showing up as "deprecated" in Transifex 01:15:33 Is it time to pull the plug finally on this one? 01:15:37 jjmcd -- NP 01:15:56 I think we need to get with the maintainers of the "minor" browsers that use it 01:15:57 maybe 01:16:13 We got more browsers ... 01:17:24 Also; I think we need to come to a decision about whether all these need to be packaged with the RNs themselves; but I guess that's one for the RN packaging meeting -- do we have a firm time for that? 01:17:46 rudi: 1500z today. 01:17:54 rudi: Not sure if that's too late/early for you 01:18:25 Great -- that's 1AM for me, but I'll be there. I just didn't want to stay up for it unless I was sure that it was going ahead! 01:18:38 jjmcd: You gonna be there? 01:18:42 yep 01:18:53 I'll be there... So that's three of us! 01:18:58 lolz 01:19:22 #action Sparks to send out reminder about the RN meeting 01:19:32 Okay, anything else? 01:19:38 Not from me 01:19:42 Anyone? 01:20:10 Okay, thanks for everyone coming tonight. 01:20:14 #endmeeting From eric at christensenplace.us Thu Jul 23 01:24:24 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 22 Jul 2009 21:24:24 -0400 Subject: Docs Meeting 2009-07-23Summary Message-ID: <1248312265.5597.1.camel@echristensen.tkctech.com> ======================================================================================================================================= #fedora-meeting: Docs Project - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings#Thursday_July_23.2C_2009_.28Wed_US_Time.29 ======================================================================================================================================= Meeting started by Sparks at 00:01:38 UTC. The `full logs`_ are available. .. _`full logs`: fedora-meeting.2009-07-23-00.01.log.html Meeting log ----------- * **Status on CMS (Zikula) <-- ke4qqq** (Sparks-00:06:35_) * *ACTION*: Sparks to follow up with the News people about Zikula (Sparks-00:21:20_) * *ACTION*: Sparks to meet with News people and solicit a list of their needs (Sparks-00:22:37_) * **Status on CC license rollout. <-- ianweller** (Sparks-00:23:01_) * *ACTION*: Sparks to write rollout plan for license change (Sparks-00:30:37_) * *ACTION*: ianweller to write press release (ianweller-00:30:59_) * *ACTION*: rudi to help sparks on changing the fedora-brand in Publican for CC license (Sparks-00:33:08_) * **Shared open-source style guide <--ke4qqq** (Sparks-00:35:17_) * *LINK*: https://www.redhat.com/archives/fedora-docs-list/2009-June/msg00163.html (Sparks-00:35:24_) * **Outstanding BZ Tickets** (Sparks-00:37:25_) * *LINK*: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW (Sparks-00:37:36_) * **Guide needs?** (Sparks-00:43:14_) * *LINK*: https://fedoraproject.org/wiki/Docs_Project_meetings#Guides (Sparks-00:44:11_) * **New Guides** (Sparks-00:48:04_) * *ACTION*: Sparks to create BZ component for Installation Quick Start Guide (Sparks-00:52:10_) * *ACTION*: Sparks to create a BZ component for Virtualization Guide (Sparks-00:55:33_) * **All other business** (Sparks-01:04:10_) * *LINK*: https://fedoraproject.org/wiki/Classroom (nirik-01:04:44_) * *ACTION*: Sparks to send out reminder about the RN meeting (Sparks-01:19:22_) .. _Sparks-00:06:35: fedora-meeting.2009-07-23-00.01.log.html#l-13 .. _Sparks-00:21:20: fedora-meeting.2009-07-23-00.01.log.html#l-74 .. _Sparks-00:22:37: fedora-meeting.2009-07-23-00.01.log.html#l-80 .. _Sparks-00:23:01: fedora-meeting.2009-07-23-00.01.log.html#l-83 .. _Sparks-00:30:37: fedora-meeting.2009-07-23-00.01.log.html#l-133 .. _ianweller-00:30:59: fedora-meeting.2009-07-23-00.01.log.html#l-135 .. _Sparks-00:33:08: fedora-meeting.2009-07-23-00.01.log.html#l-148 .. _Sparks-00:35:17: fedora-meeting.2009-07-23-00.01.log.html#l-166 .. _Sparks-00:35:24: fedora-meeting.2009-07-23-00.01.log.html#l-167 .. _Sparks-00:37:25: fedora-meeting.2009-07-23-00.01.log.html#l-176 .. _Sparks-00:37:36: fedora-meeting.2009-07-23-00.01.log.html#l-177 .. _Sparks-00:43:14: fedora-meeting.2009-07-23-00.01.log.html#l-192 .. _Sparks-00:44:11: fedora-meeting.2009-07-23-00.01.log.html#l-198 .. _Sparks-00:48:04: fedora-meeting.2009-07-23-00.01.log.html#l-208 .. _Sparks-00:52:10: fedora-meeting.2009-07-23-00.01.log.html#l-226 .. _Sparks-00:55:33: fedora-meeting.2009-07-23-00.01.log.html#l-242 .. _Sparks-01:04:10: fedora-meeting.2009-07-23-00.01.log.html#l-287 .. _nirik-01:04:44: fedora-meeting.2009-07-23-00.01.log.html#l-290 .. _Sparks-01:19:22: fedora-meeting.2009-07-23-00.01.log.html#l-359 Meeting ended at 01:20:14 UTC. Action Items ------------ * Sparks to follow up with the News people about Zikula * Sparks to meet with News people and solicit a list of their needs * Sparks to write rollout plan for license change * ianweller to write press release * rudi to help sparks on changing the fedora-brand in Publican for CC license * Sparks to create BZ component for Installation Quick Start Guide * Sparks to create a BZ component for Virtualization Guide * Sparks to send out reminder about the RN meeting Action Items, by person ----------------------- * ianweller * ianweller to write press release * rudi * rudi to help sparks on changing the fedora-brand in Publican for CC license * Sparks * Sparks to follow up with the News people about Zikula * Sparks to meet with News people and solicit a list of their needs * Sparks to write rollout plan for license change * Sparks to create BZ component for Installation Quick Start Guide * Sparks to create a BZ component for Virtualization Guide * Sparks to send out reminder about the RN meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * Sparks (145) * stickster (46) * ianweller (44) * rudi (43) * ke4qqq (24) * jjmcd (18) * perspectival (17) * nirik (10) * Tsagadai (5) * danielsmw (4) * mchua (3) * bcotton (2) * onekopaka_laptop (2) * laubersm (1) Generated by `MeetBot`_ .. _`MeetBot`: http://wiki.debian.org/MeetBot From bugzilla at redhat.com Thu Jul 23 01:39:40 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 21:39:40 -0400 Subject: [Bug 430721] Additional Information Requested for Apache Setup In-Reply-To: References: Message-ID: <200907230139.n6N1deuE022948@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=430721 David Nalley changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |david at gnsa.us AssignedTo|kwade at redhat.com |dhensley at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 23 01:42:10 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 22 Jul 2009 21:42:10 -0400 Subject: [Bug 450331] lack of documentation on restoring from bare-metal (UUID problem) In-Reply-To: References: Message-ID: <200907230142.n6N1gAqt023758@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=450331 David Nalley changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |david at gnsa.us AssignedTo|danielsmw at gmail.com |dhensley at redhat.com --- Comment #5 from David Nalley 2009-07-22 21:42:09 EDT --- This sounds like it will be a nice fit for the upcoming Deployment Guide targeted at sysadmins, with the assumption that the component will change once the DG is listed in BZ. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From robert.buj at gmail.com Thu Jul 23 02:39:59 2009 From: robert.buj at gmail.com (Robert Antoni Buj Gelonch) Date: Thu, 23 Jul 2009 04:39:59 +0200 Subject: Self-Introduction: Message-ID: <584bf03c0907221939g3e3eecedw9bf329e4963a2d16@mail.gmail.com> # What other projects or writing have you worked on in the past? I have worked in Babelzilla, Officeshots, OpenSolaris, PC-BSD, Ubuntu & Wordpress extensions (Translation projects) # What level and type of computer skills do you have? I am Computer Science Engineer. # What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. system administrator, programmer # What makes you an excellent match for the project? I think that I can do it. I would like to translate it to catalan language. # GPG KEYID and fingerprint pub 1024D/B4623A0F 2009-07-05 Key fingerprint = DB34 728A 5B78 ECB1 727B 38E0 253E 78B4 B462 3A0F -- ca: M'agradaria millorar el m?n, per? D?u no em d?na el codi font! de: Ich w?rde gern die Welt verbessern, doch Gott gibt mir den Quellcode nicht! en: I would like to improve the world, but God not gives to me the source code! es: Me gustar?a mejorar el mundo, pero Dios no me da el c?digo fuente! From eric at christensenplace.us Thu Jul 23 11:42:16 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 23 Jul 2009 07:42:16 -0400 Subject: Self-Introduction: In-Reply-To: <584bf03c0907221939g3e3eecedw9bf329e4963a2d16@mail.gmail.com> References: <584bf03c0907221939g3e3eecedw9bf329e4963a2d16@mail.gmail.com> Message-ID: <1248349346.9331.4.camel@echristensen.tkctech.com> On Thu, 2009-07-23 at 04:39 +0200, Robert Antoni Buj Gelonch wrote: > # What other projects or writing have you worked on in the past? > I have worked in Babelzilla, Officeshots, OpenSolaris, PC-BSD, Ubuntu > & Wordpress extensions (Translation projects) > > # What level and type of computer skills do you have? > I am Computer Science Engineer. > > # What other skills do you have that might be applicable? User > interface design, other so-called soft skills (people skills), > programming, etc. > system administrator, programmer > > # What makes you an excellent match for the project? > I think that I can do it. I would like to translate it to catalan language. > > # GPG KEYID and fingerprint > pub 1024D/B4623A0F 2009-07-05 > Key fingerprint = DB34 728A 5B78 ECB1 727B 38E0 253E 78B4 B462 3A0F > > > -- > ca: M'agradaria millorar el m?n, per? D?u no em d?na el codi font! > de: Ich w?rde gern die Welt verbessern, doch Gott gibt mir den Quellcode nicht! > en: I would like to improve the world, but God not gives to me the source code! > es: Me gustar?a mejorar el mundo, pero Dios no me da el c?digo fuente! > Robert, Thanks for sending this along. It appears you want to be a translator and not a Docs creator/editor. Translators need to join L10N [1] as they have access to all the translation tools. [1] https://fedoraproject.org/wiki/L10n Thanks, Eric From sandeep.shedmake at gmail.com Thu Jul 23 12:51:56 2009 From: sandeep.shedmake at gmail.com (sandeep shedmake) Date: Thu, 23 Jul 2009 18:21:56 +0530 Subject: Looking for pointers wrt metrics for LISA QA 3.1 Message-ID: Hi, I wondered unlike Quality Assurance/QA metrics which exists for Software Development projects, are there any QA metrics defined for Localization QA ? Thereby, I came across two such specifications namely --- SAE J2450 and LISA QA 3.1. Metrics for SAE J2450 model is available at http://www.apex-translations.com/documents/sae_j2450.pdf, but I couldn't locate any such document for LISA QA 3.1 model. Any pointers/point-of-contact wrt "metrics for LISA QA 3.1 model/specifications" would be helpful. Thanks, sandeeps -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric at christensenplace.us Thu Jul 23 12:54:12 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 23 Jul 2009 08:54:12 -0400 Subject: REMINDER: Release Notes Meeting Message-ID: <1248353652.2702.4.camel@echristensen.tkctech.com> We'll have a Release Notes meeting at 1500UTC today. We'll meet in #fedora-meeting. The purpose of this meeting is to discuss the F12 Release Notes and discuss any changes from F11. Eric From eric at christensenplace.us Thu Jul 23 16:27:52 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 23 Jul 2009 12:27:52 -0400 Subject: Release Notes Meeting 2009-07-23 IRC log Message-ID: <1248366482.2702.13.camel@echristensen.tkctech.com> 15:02:17 #startmeeting Release Notes Meeting 15:02:22 Who is here? 15:02:23 * Sparks 15:02:25 * zoglesby is here 15:02:27 * rudi is here 15:02:42 * bcotton is here 15:02:57 * jjmcd is taking a break from spending the state's money 15:03:23 * laubersm found you 15:04:54 Okay... I'd like to discuss the following: 15:05:08 * laubersm goes to refill coffe mug before settling in for this hour of fun 15:05:29 1. How to improve on the F12 RNs 15:05:43 2. What products need to be generated. 15:05:55 3. Using Publican for the RNs 15:06:30 4. Training people to write beats. 15:06:44 laubersm: Hour? We've got this channel all day. 15:07:08 Anything else we need to discuss? 15:07:14 * zoglesby get coffe IV 15:07:38 * laubersm found only dregs and was too lazy to make more - but returned to this fun anyways 15:08:02 Probably we should discudd who the audience is before attempting to answer those questions 15:08:10 jjmcd: yes 15:08:12 sheesh the typing 15:08:58 anything else? 15:09:17 Packaging 15:09:32 As in, when and what 15:09:34 Influenced by 2 of course 15:09:40 Yeah 15:10:29 Okay, let's get started... 15:10:41 #topic Audience 15:10:48 I see 3 15:10:57 People who just installed and want to know what's new 15:11:06 People preparing to install 15:11:12 People looking for a new feature or fixed bug 15:11:24 Wouldn't the second one be the IG? 15:11:35 Not necessarily 15:11:51 For example, database changes almost always require you to do something before install 15:11:52 errr... shouldn't it be included in the IG 15:11:57 those won't be in the IG 15:12:00 True 15:12:11 So more of an upgrade guide 15:12:29 I think there is one more 15:12:33 Yeah, almost anything that needs a backup or something before upgrade needs to be captured 15:12:54 People that hear about Fedora and are trying to see what it has to offer 15:13:17 I often look at release notes when I hear about a new distro 15:13:33 Yeah, probably looking for more detail than the announcement 15:13:37 Okay, so I see this as: 15:14:00 The BIG RNs goes to the third group. 15:14:10 A "Welcome to Fedora ##" for the last 15:14:44 The "pretty" RN (from Marketing) for the first 15:14:47 I think welcome can also address the first group in an introductory way 15:14:51 yes 15:15:14 good point. Perhaps marketing should do the welcome to fedora xx 15:15:29 definitely 15:17:13 So we are already working on the "pretty" version with Marketing. 15:17:34 And we currently have the BIG RNs 15:17:35 I generally find most "users" - new or upgrading - think of wiki and IG and UG as resources more than the RN - they tend to think Release Notes are for the geeks 15:17:46 So we need to figure out the Upgrade guide 15:17:49 The RN can include links to those general resources - and should 15:18:01 UG = users guide 15:18:03 agreed 15:18:24 do we really need a separate upgrade guide? can't it be in the IG? 15:18:27 So the beat writers will need to be upgrade writers too, or at least help guide the upgrade writers 15:18:51 laubersm, I doubt if the experienced user will look at the install guide 15:18:53 Well, I think the IG should have information on upgrading 15:19:15 FWIW, the IG already details several different upgrade paths 15:19:47 jjmcd, I was thinking more of the reminders of good general practices - RN would still be for the "this time it is bar than needs to be reconfigured instead of foo" 15:19:58 But does it include things like "save your qle database to sql before upgrading and reimport after the upgrade"? 15:20:25 Yes, I don't see the upgrade guide as including all the version specific details 15:20:32 jjmcd -- no; and I think that's probably out of scope 15:20:33 jjmcd, if that is an everytime you upgrade the db than it should be in a general guide and not repeated with every RN 15:21:09 So beat writers talk about new stuff and also issues to upgrading 15:21:27 Yes, but most of the time you don't need to, seems like every third or fourth time with MYSQL, Postgres, and some others there are special things to do 15:21:39 But I agree, if its every time, then the upgrade guide 15:22:27 I see beat writers as listing all changes, but providing prose for "important" changes and upgrade issues 15:23:15 That way the change that you care about, but I don't see as important, is at least noted 15:23:48 remind me - who makes up the beat writers? some are docs team members but aren't some from other teams that just help with RN? 15:24:08 Mostly docs team members but not always 15:24:25 We generally seem to do better with team members 15:24:43 I ask because maybe docs members - or people more familiar with the many guides - should be reviewing to make sure RN stays trim and important stuff gets rediurected to the guides 15:24:57 it seems to me that we just haven't had time for that in the past - 15:25:02 even though the intent has been good 15:25:24 * laubersm prefers reviewing to writing by the way 15:25:25 I'm hoping to have more lists and less prose this time around 15:25:35 Should give us more opportunity to review 15:26:21 And less work for translators 15:26:37 and will the review period be as free form as last time or will it be a bullet on the docs team schedule (or in a wiki chart)? 15:27:09 I hope to take poelcat's schedule and add in some docs and l10n bullets 15:27:19 cool. 15:27:35 We never got the l10n notifications in there and we need that 15:27:40 Yeah, I think we need to make sure we get these beats done well ahead of time 15:28:44 I think if beat writers trade reviewing it will help the overall flow of all the RNs as well - and catch more duplication (or need for general docs tips) 15:28:57 Okay... I don't want to drag this meeting out... :) 15:29:00 laubersm: I agree. 15:29:14 So can we say that three "RNs" will make this work? 15:29:30 Most of that has to do with communications with other teams. Looking at the F11 beats, the only writer who wasn't a docs member at all was Chitlesh, although Jens I think is in the group, but not at the meetings etc 15:29:42 what three? 15:29:54 1) Big RNs 15:29:56 I think we had so much duplicate stuff last time cause on the last day 3 of of were writing all the stuf that didnt get done 15:29:59 How are we naming these so they catch the correct audience? 15:30:00 2) "Pretty RN" 15:30:08 3) Upgrade "Guide" 15:30:23 You don't see the "pretty RN" as chapter one of big rn? 15:30:44 The "Pretty RN" will be very graphical 15:30:50 ahhh good 15:30:52 kind of like a "newsletter" 15:30:59 a flyer 15:31:11 sounds like a bitch to translate 15:31:31 but we did it with IG if I recall 15:31:46 Not as long as people are careful to keep text out of the graphics 15:31:58 And rely on captions, or callouts 15:32:18 And yeah, the IG has about 70 images in each of about 35 localisations 15:32:35 So are we good with those three? 15:32:47 question fro rudi 15:33:03 did you do those with dot or something so that you could translate easily? 15:33:26 Yeah, where needed. 15:33:41 cool 15:33:57 I like it Sparks 15:34:26 #idea Three "RN" guides: big RN, "pretty" RN, and Upgrade Guide 15:34:30 jjmcd -- http://docs.fedoraproject.org/install-guide/f11/en-US/html/s1-guimode-textinterface-x86.html 15:35:31 Okay to move on? 15:35:33 Do we have any specific plan to keep down the bigness of the big RN? 15:35:45 tables 15:36:29 Hmmm -- tables might get L10N hating us for whole new reasons :) 15:36:36 I think that one of the big issues for 11 was the amount of info trans had to deal with if we add 2 more we need to cut some down 15:36:39 Nothing in the tables to translate 15:36:47 Oh OK. 15:37:05 Just that elements in lists and tables are very challenging 15:37:09 Jus package name, old version, new version link 15:37:29 Specifically intended to not need translation 15:37:38 lol 15:37:57 Without any description of what actually changed? 15:37:59 I think we can automate that to, 15:38:14 zoglesby, a lot of the prose was just fluff. Already automated ;-) 15:38:27 rudi, only "important" changes 15:38:33 OK 15:38:49 https://fedoraproject.org/wiki/User:Jjmcd/Drafts/Fedora_12_tables 15:39:06 Not organized by beats, and needs a lot of editing 15:39:35 sure, but yeah, I get the picture now 15:39:46 why do we have meetings again? Why not force jjmcd to 6S everything for us 15:40:24 +1 15:40:34 We still need ppl who can reed and spel gud 15:40:40 zodbot, because last time he built and rpm and left town and it had to be redone before he returned 15:40:53 arg... that was for zoglesby 15:40:55 this is more of a fedora change log then release notes 15:41:09 * laubersm relies on tab complete too much without looking 15:41:40 Well, we do need the change log. In my view, we still need prose for "important" changes, but this way someone looking for a feature or bugfix can see if it is there 15:41:47 laubersm: ah yes that was a good day 15:42:09 ANd that list is long because it is against rawhide. As we close in on release it will get shorter 15:42:17 zoglesby; true to some extent, but then, there was a lot of stuff in previous RNs that was basically "Package X has been upgraded from version 1.7 to 1.9" 15:42:19 jjmcd: very true, it takes care of one group 15:42:34 Yes, and the prose takes care of the others 15:42:49 ok 15:42:58 rudi, and that prose only provided useless work for translators 15:43:06 Yep. 15:43:12 jjmcd: Are you reviewig bug reports for stuff to go into the RN? 15:43:22 Yes, hit a bunch last week 15:43:33 How about a para on how to use a tool to find that list and not include it at all :) 15:43:51 One "content" bug I still needs more research 15:44:00 * laubersm thinks such lists reinvent the wheel and will always miss something 15:44:19 And the remaining RN bugs either need a lot of work or need to wait for something else 15:44:21 put a link to the fedora community site 15:44:29 laubersm, probably not a bad idea 15:45:02 jjmcd: Are people actually flagging items to be included in the RNs? 15:45:02 but there went your 0 trans :P 15:45:13 Sparks, generally no 15:45:25 jjmcd: Maybe we should encourage that and then query that. 15:45:40 I wonder how good an idea that is actually 15:45:56 For the person working on a package, any change is "important" 15:46:47 Although when you have someone like Chitlesh or Jens who sees the bigger picture, it is great when they can work on the prose 15:46:57 jjmcd, will the list at least be at the end - ie "other updates include:" so I don't have to scroll through it to get to the prose? 15:47:12 yes, that was my view - but by beat 15:47:22 So you get the database prose, then the list 15:47:33 ok 15:47:57 Problem is, the yum groups are all screwed up, so organizing the list by beat is going to be a bit of a job 15:48:12 That drafts page is by yum group 15:50:42 But as you said, perhaps we make a page that gets updated nightly for the list, or make the tool easy enough for people to use 15:51:11 That way you can see what changed from F11 to NOW rather than to the initial release of 12 15:51:46 +1 15:52:54 is there a php interface to sqlite? 15:53:10 * Sparks notes nine minutes left 15:53:45 Still have most agenda items left 15:53:51 Yes 15:54:08 yes sqlite or yes agenda? 15:54:13 yes agenda 15:55:08 What is the issue with Publican? I thought we had that answered. 15:55:19 Well... If you can do what you need to do then I'm fine. 15:55:36 I can't get the SRPMs to generate in koji. They fail 15:55:37 * jjmcd has no issue with Publican 15:55:55 The Beta for Publican 1.0 should be announced soon now 15:56:27 I've been manually building the SRPM, if Publican can do it right, great, but making the RPM isn't a biggie 15:57:10 I can't help with the SRPMs, but until 1.0 appears, we now have hackish fixes to most of the glitches in 0.44 up on the wiki 15:57:13 Well, hopefully the "new" version of Publican will fix the problems. 15:57:38 If we still include N docs in the RN RPM it doesn't matter anyway 15:57:49 rudi: the fedora wiki or publican wiki? 15:57:55 Fedora wiki 15:58:15 Even if there are glitches with the building the SRPM, I have no issues with publican - all items should be created with publican 15:58:24 https://fedoraproject.org/wiki/Publican#Publican_on_Fedora_Tips_and_Tweaks 15:58:25 * laubersm did not like the old toolchain adventure 15:58:41 * jjmcd agrees with laubersm 15:59:15 I'm afraid we need at least another meeting to answer the "what products" question though 15:59:29 jjmcd: That's cool. Is this time good with everyone? 15:59:46 * Sparks notes that it is awfully late/early for rudi 15:59:48 * rudi isn't crazy about it, but will turn up with enough warning :) 15:59:58 This time on Thursday is suboptimal but doable 16:00:05 2AM here in the middle of an Australian winter 16:00:18 rudi: thats me every docs meeting! 16:00:44 well not the winter part 16:00:49 :D 16:01:00 * jjmcd will probably be out of town the next few Wednesdays, tho, so Thursday is better than Wednesday 16:01:03 and I only wish I was in Australian 16:01:34 I will have a harder time next week - afternoon would be better when students are more likely to be doing labs instead of listening to me talk.... 16:01:38 Sparks: any time is good with me, if I have to I will use my phone and not talk so much 16:02:00 * laubersm is EDT when refering to afternoon 16:02:14 * Sparks is EDT, too 16:02:46 If you move to 2000Z you are starting to get into a semi-sensible morning time for rudi 16:03:17 * Sparks notes 2000z is drive time for us in EDT 16:03:38 Don't worry about me; I'm happy to work around you guys 16:03:52 rudi: Time and a half at 1A? 16:04:06 I wish! :) 16:04:08 lol 16:04:17 I miss shift-differential 16:04:49 Not me ... back when I got it, I was making $1.82 an hour 16:05:17 Okay, anything else we need to discuss today? 16:05:19 I missing getting paid for the amount of time I work not working 80 hour weeks and getting the same as everyone else working 40 16:06:21 Not discuss, but a thought to leave with people that we should perhaps try to get a package into rawhide rooner rather than later 16:06:41 I agree 16:06:41 indeed 16:07:00 +1 16:07:14 ECS will be able to help out with some of the heavy lifting content-wise, but not so much with the packaging 16:07:40 (and hopefully there will be less heavy lifting this time round anyway) 16:08:04 Okay, anything else? 16:08:40 Okay, while we didn't get through everything we did have a good discussion. 16:08:44 Good ideas 16:10:04 Okay, thanks for coming! 16:10:07 #endmeeting From awilliam at redhat.com Thu Jul 23 18:01:47 2009 From: awilliam at redhat.com (Adam Williamson) Date: Thu, 23 Jul 2009 11:01:47 -0700 Subject: REMINDER: Release Notes Meeting In-Reply-To: <1248353652.2702.4.camel@echristensen.tkctech.com> References: <1248353652.2702.4.camel@echristensen.tkctech.com> Message-ID: <1248372107.2863.28.camel@adam.local.net> On Thu, 2009-07-23 at 08:54 -0400, Eric Christensen wrote: > We'll have a Release Notes meeting at 1500UTC today. We'll meet in > #fedora-meeting. > > The purpose of this meeting is to discuss the F12 Release Notes and > discuss any changes from F11. Gack. I overslept and missed this. Sorry :( -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net From eric at christensenplace.us Thu Jul 23 18:22:50 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 23 Jul 2009 14:22:50 -0400 Subject: Removing inactive members from the Docs FAS Group Message-ID: <1248373380.2702.25.camel@echristensen.tkctech.com> The following members of the Docs FAS Group are showing as inactive in FAS. Is there any reason to NOT remove these users from the Docs group? zachfedora sopwith mumumu mcgiwer dpniner mattb csellers clennert mjbrej ddeutsch sfolkwil manix rmoreira splinux acapur rue cepxat drpixel gawain mbrennan naga bbcradio andrew kburtsev fcrhuser dtypald vmlinz jmtaylor denity kwade angelven mcisback rbianchi xiaoshao laong sfaure eitch ghenry anukul vglafirov shivakant jjesse Thanks, Eric From ricky at fedoraproject.org Thu Jul 23 18:35:43 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 23 Jul 2009 14:35:43 -0400 Subject: Allowed Content Message-ID: <20090723183543.GI5734@alpha.rzhou.org> Hey, I mentioned a few recent fedora-docs-list threads at the last IRC support operators[1], and they were generally very positive about some of the howto/knowledge base ideas that have been brought up. One concern that they brought up was whether we have a policy on what content can/cannot be on Fedora's wiki (or "official" Fedora docs), something more specific than http://fedoraproject.org/wiki/ForbiddenItems. One example that was brought up is that we currently have a howto for installing flash at http://fedoraproject.org/wiki/Flash, so there may be some current confusion about this. I will keep in touch with the IRC support operators team and see what allowed vs. not allowed topics are FAQs for them. Thanks, Ricky [1] http://meetbot.fedoraproject.org/fedora-meeting/2009-07-23/fedora-meeting.2009-07-23-16.30.log.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From awilliam at redhat.com Thu Jul 23 21:02:27 2009 From: awilliam at redhat.com (Adam Williamson) Date: Thu, 23 Jul 2009 14:02:27 -0700 Subject: Allowed Content In-Reply-To: <20090723183543.GI5734@alpha.rzhou.org> References: <20090723183543.GI5734@alpha.rzhou.org> Message-ID: <1248382947.2863.29.camel@adam.local.net> On Thu, 2009-07-23 at 14:35 -0400, Ricky Zhou wrote: > One example that was brought up is that we currently have a howto for > installing flash at http://fedoraproject.org/wiki/Flash, so there may be > some current confusion about this. This was discussed on test-list a while back, and the general feeling was that it was OK as long as it stressed free options and was explicit about the non-free-ness of the Adobe plugin. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net From stickster at gmail.com Thu Jul 23 21:37:06 2009 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 23 Jul 2009 17:37:06 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248373380.2702.25.camel@echristensen.tkctech.com> References: <1248373380.2702.25.camel@echristensen.tkctech.com> Message-ID: <20090723213706.GH3592@localhost.localdomain> On Thu, Jul 23, 2009 at 02:22:50PM -0400, Eric Christensen wrote: > The following members of the Docs FAS Group are showing as inactive in > FAS. Is there any reason to NOT remove these users from the Docs group? [...snip...] No reason you couldn't, but I'd suggest you send a courtesy note prior to the removal just to explain why they're being removed, and giving them a link to follow if they want to get involved again in the future. "Prior to" could be as little as immediately before. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From stickster at gmail.com Thu Jul 23 21:48:21 2009 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 23 Jul 2009 17:48:21 -0400 Subject: Allowed Content In-Reply-To: <20090723183543.GI5734@alpha.rzhou.org> References: <20090723183543.GI5734@alpha.rzhou.org> Message-ID: <20090723214821.GI3592@localhost.localdomain> On Thu, Jul 23, 2009 at 02:35:43PM -0400, Ricky Zhou wrote: > Hey, I mentioned a few recent fedora-docs-list threads at the last IRC > support operators[1], and they were generally very positive about > some of the howto/knowledge base ideas that have been brought up. > > One concern that they brought up was whether we have a policy on what > content can/cannot be on Fedora's wiki (or "official" Fedora docs), > something more specific than http://fedoraproject.org/wiki/ForbiddenItems. > > One example that was brought up is that we currently have a howto for > installing flash at http://fedoraproject.org/wiki/Flash, so there may be > some current confusion about this. > > I will keep in touch with the IRC support operators team and see what > allowed vs. not allowed topics are FAQs for them. > > Thanks, > Ricky > > [1] http://meetbot.fedoraproject.org/fedora-meeting/2009-07-23/fedora-meeting.2009-07-23-16.30.log.html Flash has a page because it is not illegal to use anywhere in the world that we know of, and the page provides up-front the suggestion that people try to use a FOSS implementation. Incidentally, it also does not impede other base functioning of the system that prevents effective debugging and troubleshooting. This is not true of encumbered add-ons like MP3, proprietary video drivers, and so on. Having said that, I'm not overjoyed about having a Flash page, and the reason I contributed so much to it myself was to make sure it was as clear and accurate as possible. I do recall there was discussion around the time of its creation, and would ask that before proposing any policy, the proposer should research that discussion. I would remove it to have a bright-line policy if required, but I do note that (1) it has first ranking on Google for "fedora flash", and (2) I'm pretty sure we've had a lot fewer Flash installation problems as a result. Those facts do not trump our mission, though, so if this page goes away, so be it. (The 2nd page is the unofficial Fedora FAQ which can just as easily serve this purpose.) The mission of Fedora is to advance free and open source software, which Flash is clearly not. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From eric at christensenplace.us Thu Jul 23 22:38:01 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 23 Jul 2009 18:38:01 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <20090723213706.GH3592@localhost.localdomain> References: <1248373380.2702.25.camel@echristensen.tkctech.com> <20090723213706.GH3592@localhost.localdomain> Message-ID: <1248388696.2702.26.camel@echristensen.tkctech.com> On Thu, 2009-07-23 at 17:37 -0400, Paul W. Frields wrote: > On Thu, Jul 23, 2009 at 02:22:50PM -0400, Eric Christensen wrote: > > The following members of the Docs FAS Group are showing as inactive in > > FAS. Is there any reason to NOT remove these users from the Docs group? > [...snip...] > > No reason you couldn't, but I'd suggest you send a courtesy note prior > to the removal just to explain why they're being removed, and giving > them a link to follow if they want to get involved again in the > future. "Prior to" could be as little as immediately before. Of course these are inactive accounts and thus their mail forwarding wouldn't work. From ricky at fedoraproject.org Fri Jul 24 00:00:16 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 23 Jul 2009 20:00:16 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248388696.2702.26.camel@echristensen.tkctech.com> References: <1248373380.2702.25.camel@echristensen.tkctech.com> <20090723213706.GH3592@localhost.localdomain> <1248388696.2702.26.camel@echristensen.tkctech.com> Message-ID: <20090724000016.GB27214@alpha.rzhou.org> On 2009-07-23 06:38:01 PM, Eric Christensen wrote: > Of course these are inactive accounts and thus their mail forwarding > wouldn't work. For what it's worth, it's simple to modify the script to print emails as well, although anybody that got their account inactivated would have recieved several emails in advance asking them to do the required password reset to stay active. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From stickster at gmail.com Fri Jul 24 03:02:24 2009 From: stickster at gmail.com (Paul W. Frields) Date: Thu, 23 Jul 2009 23:02:24 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <20090724000016.GB27214@alpha.rzhou.org> References: <1248373380.2702.25.camel@echristensen.tkctech.com> <20090723213706.GH3592@localhost.localdomain> <1248388696.2702.26.camel@echristensen.tkctech.com> <20090724000016.GB27214@alpha.rzhou.org> Message-ID: <20090724030224.GO3592@localhost.localdomain> On Thu, Jul 23, 2009 at 08:00:16PM -0400, Ricky Zhou wrote: > On 2009-07-23 06:38:01 PM, Eric Christensen wrote: > > Of course these are inactive accounts and thus their mail forwarding > > wouldn't work. > For what it's worth, it's simple to modify the script to print emails as > well, although anybody that got their account inactivated would have > recieved several emails in advance asking them to do the required > password reset to stay active. Worth quite a lot. I just wanted to make sure we weren't taking anyone by surprise. I see no reason to belabor the issue, then, since the previous notices should have got people's attention. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From bugzilla at redhat.com Fri Jul 24 15:47:30 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Fri, 24 Jul 2009 11:47:30 -0400 Subject: [Bug 503780] Fedora 12 Documentation Release BLOCKER In-Reply-To: References: Message-ID: <200907241547.n6OFlU3Z002710@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=503780 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|eric at christensenplace.us |fedora-docs-list at redhat.com QAContact|kwade at redhat.com |eric at christensenplace.us -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug. From kwade at redhat.com Fri Jul 24 20:59:26 2009 From: kwade at redhat.com (Karsten Wade) Date: Fri, 24 Jul 2009 13:59:26 -0700 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248373380.2702.25.camel@echristensen.tkctech.com> References: <1248373380.2702.25.camel@echristensen.tkctech.com> Message-ID: <20090724205926.GA7310@calliope.phig.org> On Thu, Jul 23, 2009 at 02:22:50PM -0400, Eric Christensen wrote: > The following members of the Docs FAS Group are showing as inactive in > FAS. Is there any reason to NOT remove these users from the Docs group? Would this inactivity cause them to be unable to edit the wiki? I presume so, but at least one name on the list (sfolkwil) I thought had contributed to one or both of the last sets of release notes (F9, F10). IMO, as long as people are able to come back at will (probably by re-introducing themselves, etc.), then it's really no worry, keep things clean, etc. - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From eric at christensenplace.us Fri Jul 24 21:04:45 2009 From: eric at christensenplace.us (Eric Christensen) Date: Fri, 24 Jul 2009 17:04:45 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <20090724205926.GA7310@calliope.phig.org> References: <1248373380.2702.25.camel@echristensen.tkctech.com> <20090724205926.GA7310@calliope.phig.org> Message-ID: <1248469491.2659.10.camel@echristensen.tkctech.com> On Fri, 2009-07-24 at 13:59 -0700, Karsten Wade wrote: > On Thu, Jul 23, 2009 at 02:22:50PM -0400, Eric Christensen wrote: > > The following members of the Docs FAS Group are showing as inactive in > > FAS. Is there any reason to NOT remove these users from the Docs group? > > Would this inactivity cause them to be unable to edit the wiki? I > presume so, but at least one name on the list (sfolkwil) I thought had > contributed to one or both of the last sets of release notes (F9, F10). > > IMO, as long as people are able to come back at will (probably by > re-introducing themselves, etc.), then it's really no worry, keep > things clean, etc. They can come back at any time. No one on the list is anyone that has been active in the Docs Project in some time (that I'm aware of). I think that when the account goes inactive then their password is expired and they wouldn't be able to edit the wiki or access anything else that is FAS related until they do a password reset. Eric From mike at l4m3.com Sat Jul 25 13:35:55 2009 From: mike at l4m3.com (Mike Danko) Date: Sat, 25 Jul 2009 09:35:55 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248373380.2702.25.camel@echristensen.tkctech.com> References: <1248373380.2702.25.camel@echristensen.tkctech.com> Message-ID: <1248528955.2945.2.camel@skrelnick> As others have mentioned, since they're inactive in FAS, there might be some hoop jumping to get a hold of them, but I can only assume that since the FAS accounts have been removed, they don't want to be involved, and can't work on things anyway. Dropping a FAS account is the quickest way to get un-involved I suppose. Does dropping your account release you from the CLA? If so, should you NOT contact these people? On Thu, 2009-07-23 at 14:22 -0400, Eric Christensen wrote: > The following members of the Docs FAS Group are showing as inactive in > FAS. Is there any reason to NOT remove these users from the Docs group? > > zachfedora > sopwith > mumumu > mcgiwer > dpniner > mattb > csellers > clennert > mjbrej > ddeutsch > sfolkwil > manix > rmoreira > splinux > acapur > rue > cepxat > drpixel > gawain > mbrennan > naga > bbcradio > andrew > kburtsev > fcrhuser > dtypald > vmlinz > jmtaylor > denity > kwade > angelven > mcisback > rbianchi > xiaoshao > laong > sfaure > eitch > ghenry > anukul > vglafirov > shivakant > jjesse > > Thanks, > Eric > From mike at l4m3.com Sat Jul 25 13:49:49 2009 From: mike at l4m3.com (Mike Danko) Date: Sat, 25 Jul 2009 09:49:49 -0400 Subject: Allowed Content In-Reply-To: <20090723214821.GI3592@localhost.localdomain> References: <20090723183543.GI5734@alpha.rzhou.org> <20090723214821.GI3592@localhost.localdomain> Message-ID: <1248529789.2945.15.camel@skrelnick> This is really tricky actually, and while being a Freedom loving software advocate, there are lots of reasons to at least have content available on how to use proprietary tools. This is a complex world, and systems we use are complex SYSTEMS. For example, in my day job I've been told I can only run qualified software on qualified hardware for doing certain tasks. By the time things are actually qualified for our applications, hardware is EOL'd and un-order-able. Is there any need to actually do things this way (at least in our applications)? Not at all. People aren't even aware that there are options to running Oracle on RHEL4 and using java 1.4.1. Ideally, yes, you'd want to use Free software on a Free system, but there are advantages, especially with "enterprise grade" applications, to using a Free system to run proprietary applications. I've been prepping a CC licensed book to getting started with database development on Fedora, maybe what I'm saying will make more sense when I have some available online. - Mike On Thu, 2009-07-23 at 17:48 -0400, Paul W. Frields wrote: > On Thu, Jul 23, 2009 at 02:35:43PM -0400, Ricky Zhou wrote: > > Hey, I mentioned a few recent fedora-docs-list threads at the last IRC > > support operators[1], and they were generally very positive about > > some of the howto/knowledge base ideas that have been brought up. > > > > One concern that they brought up was whether we have a policy on what > > content can/cannot be on Fedora's wiki (or "official" Fedora docs), > > something more specific than http://fedoraproject.org/wiki/ForbiddenItems. > > > > One example that was brought up is that we currently have a howto for > > installing flash at http://fedoraproject.org/wiki/Flash, so there may be > > some current confusion about this. > > > > I will keep in touch with the IRC support operators team and see what > > allowed vs. not allowed topics are FAQs for them. > > > > Thanks, > > Ricky > > > > [1] http://meetbot.fedoraproject.org/fedora-meeting/2009-07-23/fedora-meeting.2009-07-23-16.30.log.html > > Flash has a page because it is not illegal to use anywhere in the > world that we know of, and the page provides up-front the suggestion > that people try to use a FOSS implementation. Incidentally, it also > does not impede other base functioning of the system that prevents > effective debugging and troubleshooting. This is not true of > encumbered add-ons like MP3, proprietary video drivers, and so on. > > Having said that, I'm not overjoyed about having a Flash page, and the > reason I contributed so much to it myself was to make sure it was as > clear and accurate as possible. I do recall there was discussion > around the time of its creation, and would ask that before proposing > any policy, the proposer should research that discussion. I would > remove it to have a bright-line policy if required, but I do note that > (1) it has first ranking on Google for "fedora flash", and (2) I'm > pretty sure we've had a lot fewer Flash installation problems as a > result. > > Those facts do not trump our mission, though, so if this page goes > away, so be it. (The 2nd page is the unofficial Fedora FAQ which can > just as easily serve this purpose.) The mission of Fedora is to > advance free and open source software, which Flash is clearly not. > > -- > Paul W. Frields http://paul.frields.org/ > gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 > http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ > irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug > From bob at fedoraunity.org Sat Jul 25 13:53:24 2009 From: bob at fedoraunity.org (Robert 'Bob' Jensen) Date: Sat, 25 Jul 2009 13:53:24 +0000 (UTC) Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <18846851.9011248529826136.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <8163647.9031248530003739.JavaMail.root@zimbra.cbccgroup.com> ----- "Eric Christensen" wrote: > > They can come back at any time. No one on the list is anyone that > has > been active in the Docs Project in some time (that I'm aware of). > > I think that when the account goes inactive then their password is > expired and they wouldn't be able to edit the wiki or access anything > else that is FAS related until they do a password reset. > I hope you exercise due diligence in this matter. You already have screwed up along these lines in the past. You lost at least one contributor that time, I don't think losing more is a good idea. There seems to be a lot of this going on, removing people from groups. Is there a good reason for it? So what if someone is "inactive" maybe they could want to contribute something tomorrow or next month. Why should they have to do anything in order to do what they have been able to do before. Why is having inactive accounts such a big deal? If I was counting numbers I would rather be able to count "125 contributors, 12 are inactive" than "113 contributors" when we all know that a large part of that 113 have not done anything in docs in a long time if ever, they just happened to re-set their password. -- Bob ------------------------------------------------------------------------ | Robert 'Bob' Jensen || Fedora Unity Founder | | bob at fedoraunity.org || http://fedoraunity.org/ | | http://bjensen.fedorapeople.org/ | | http://blogs.fedoraunity.org/bobjensen | ------------------------------------------------------------------------ From mike at l4m3.com Sat Jul 25 14:13:27 2009 From: mike at l4m3.com (Mike Danko) Date: Sat, 25 Jul 2009 10:13:27 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <8163647.9031248530003739.JavaMail.root@zimbra.cbccgroup.com> References: <8163647.9031248530003739.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <1248531208.2945.16.camel@skrelnick> It's a good point there Bob. There's no compelling reason to clear them unless there's a lack of work to be done. On Sat, 2009-07-25 at 13:53 +0000, Robert 'Bob' Jensen wrote: > ----- "Eric Christensen" wrote: > > > > They can come back at any time. No one on the list is anyone that > > has > > been active in the Docs Project in some time (that I'm aware of). > > > > I think that when the account goes inactive then their password is > > expired and they wouldn't be able to edit the wiki or access anything > > else that is FAS related until they do a password reset. > > > > I hope you exercise due diligence in this matter. You already have screwed up along these lines in the past. You lost at least one contributor that time, I don't think losing more is a good idea. > > There seems to be a lot of this going on, removing people from groups. Is there a good reason for it? So what if someone is "inactive" maybe they could want to contribute something tomorrow or next month. Why should they have to do anything in order to do what they have been able to do before. Why is having inactive accounts such a big deal? If I was counting numbers I would rather be able to count "125 contributors, 12 are inactive" than "113 contributors" when we all know that a large part of that 113 have not done anything in docs in a long time if ever, they just happened to re-set their password. > > -- Bob > > ------------------------------------------------------------------------ > | Robert 'Bob' Jensen || Fedora Unity Founder | > | bob at fedoraunity.org || http://fedoraunity.org/ | > | http://bjensen.fedorapeople.org/ | > | http://blogs.fedoraunity.org/bobjensen | > ------------------------------------------------------------------------ > From eric at christensenplace.us Sat Jul 25 14:37:50 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 25 Jul 2009 10:37:50 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <8163647.9031248530003739.JavaMail.root@zimbra.cbccgroup.com> References: <8163647.9031248530003739.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <1248532680.2694.6.camel@echristensen.tkctech.com> On Sat, 2009-07-25 at 13:53 +0000, Robert 'Bob' Jensen wrote: > ----- "Eric Christensen" wrote: > > > > They can come back at any time. No one on the list is anyone that > > has > > been active in the Docs Project in some time (that I'm aware of). > > > > I think that when the account goes inactive then their password is > > expired and they wouldn't be able to edit the wiki or access anything > > else that is FAS related until they do a password reset. > > > > I hope you exercise due diligence in this matter. You already have screwed up along these lines in the past. You lost at least one contributor that time, I don't think losing more is a good idea. Bob, I neither screwed up nor did I loose any contributors last time. What I DID do is move people that weren't as active out of the sponsor role and put active members in. What this did was allow a mentoring process to be formalized. > > There seems to be a lot of this going on, removing people from groups. Is there a good reason for it? So what if someone is "inactive" maybe they could want to contribute something tomorrow or next month. Why should they have to do anything in order to do what they have been able to do before. Why is having inactive accounts such a big deal? If I was counting numbers I would rather be able to count "125 contributors, 12 are inactive" than "113 contributors" when we all know that a large part of that 113 have not done anything in docs in a long time if ever, they just happened to re-set their password. > > -- Bob -- Eric From eric at christensenplace.us Sat Jul 25 14:40:19 2009 From: eric at christensenplace.us (Eric Christensen) Date: Sat, 25 Jul 2009 10:40:19 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248531208.2945.16.camel@skrelnick> References: <8163647.9031248530003739.JavaMail.root@zimbra.cbccgroup.com> <1248531208.2945.16.camel@skrelnick> Message-ID: <1248532829.2694.9.camel@echristensen.tkctech.com> Well, if you are trying to get a good count of people that are in the group you want to clear out those that are obviously not contributing. Things change so if you are coming back after a five year hiatus we might want to re-educate you on new processes. Eric On Sat, 2009-07-25 at 10:13 -0400, Mike Danko wrote: > It's a good point there Bob. There's no compelling reason to clear them > unless there's a lack of work to be done. > > On Sat, 2009-07-25 at 13:53 +0000, Robert 'Bob' Jensen wrote: > > ----- "Eric Christensen" wrote: > > > > > > They can come back at any time. No one on the list is anyone that > > > has > > > been active in the Docs Project in some time (that I'm aware of). > > > > > > I think that when the account goes inactive then their password is > > > expired and they wouldn't be able to edit the wiki or access anything > > > else that is FAS related until they do a password reset. > > > > > > > I hope you exercise due diligence in this matter. You already have screwed up along these lines in the past. You lost at least one contributor that time, I don't think losing more is a good idea. > > > > There seems to be a lot of this going on, removing people from groups. Is there a good reason for it? So what if someone is "inactive" maybe they could want to contribute something tomorrow or next month. Why should they have to do anything in order to do what they have been able to do before. Why is having inactive accounts such a big deal? If I was counting numbers I would rather be able to count "125 contributors, 12 are inactive" than "113 contributors" when we all know that a large part of that 113 have not done anything in docs in a long time if ever, they just happened to re-set their password. > > > > -- Bob > > > > ------------------------------------------------------------------------ > > | Robert 'Bob' Jensen || Fedora Unity Founder | > > | bob at fedoraunity.org || http://fedoraunity.org/ | > > | http://bjensen.fedorapeople.org/ | > > | http://blogs.fedoraunity.org/bobjensen | > > ------------------------------------------------------------------------ > > > From wb8rcr at arrl.net Sat Jul 25 14:44:15 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Sat, 25 Jul 2009 10:44:15 -0400 Subject: Release Notes for Fedora 12 Message-ID: The Release Notes Beat page at: https://fedoraproject.org/wiki/Documentation_Beats has been updated to reflect Fedora 12. IF YOU WERE A FEDORA 11 BEAT WRITER Review the page, if you intend to write the same beat for Fedora 12 that you wrote for Fedora 11, remove the asterisk from your name. If you would like to contribute to an additional beat, add your name to that beat. IF YOU ARE A DEVELOPER Check the Developer PoC column for your name. If you are on the list, and will still be the point of contact for Fedora 12, remove the asterisk from your name. If you are not on the list, and would like to ensure that the area you are working in gets proper attention in the release notes, add your name. Multiple names are fine. Perhaps you felt that your particular area didn't get the attention it deserved in Fedora 11. Consider writing the beat yourself. Add your name to the Writer column. IF YOU WOULD LIKE TO CONTRIBUTE TO THE RELEASE NOTES Look through the beats for an area that interests you, and add your name to the Writer column. If there is already someone there, that is fine. Two (or more) heads are better than one. IF YOU ARE UNCERTAIN Feel free to contact me by email, via the fedora-docs-list, or on the #Fedora-Docs IRC channel. You don't need to be some sort of expert to contribute to the release notes. All it takes is an interest, and the ability to string a few words together into a coherent sentence. Even if you don't feel like you are a writer, that is fine; there will be plenty of editing and review opportunities. What we really need is for folks to capture the changes. --McD From bob at fedoraunity.org Sat Jul 25 14:55:00 2009 From: bob at fedoraunity.org (Robert 'Bob' Jensen) Date: Sat, 25 Jul 2009 14:55:00 +0000 (UTC) Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248532680.2694.6.camel@echristensen.tkctech.com> Message-ID: <24620147.9961248533700462.JavaMail.root@zimbra.cbccgroup.com> ----- "Eric Christensen" wrote: > Bob, > I neither screwed up nor did I loose any contributors last time. What > I > DID do is move people that weren't as active out of the sponsor role > and > put active members in. What this did was allow a mentoring process > to > be formalized. > Oh Eric, You did screw up, you did lose at least one contributor, me, and to top it off you never even apologised for your actions, this is why you will not find my name in FAS as a Fedora Docs contributor. You let Paul and Karsten apologize and try to cover with "oh he's new" kind of responses. You are not the judge of your screw ups others are, your opinion on if it was or was not a screw up is not relevant. -- Bob ------------------------------------------------------------------------ | Robert 'Bob' Jensen || Fedora Unity Founder | | bob at fedoraunity.org || http://fedoraunity.org/ | | http://bjensen.fedorapeople.org/ | | http://blogs.fedoraunity.org/bobjensen | ------------------------------------------------------------------------ From bob at fedoraunity.org Sat Jul 25 15:20:28 2009 From: bob at fedoraunity.org (Robert 'Bob' Jensen) Date: Sat, 25 Jul 2009 15:20:28 +0000 (UTC) Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <19867053.9991248535178558.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <31420511.10011248535228212.JavaMail.root@zimbra.cbccgroup.com> ----- "Robert 'Bob' Jensen" wrote: > Oh Eric, > > You did screw up, you did lose at least one contributor, me, and to > top it off you never even apologised for your actions, this is why you > will not find my name in FAS as a Fedora Docs contributor. You let > Paul and Karsten apologize and try to cover with "oh he's new" kind of > responses. You are not the judge of your screw ups others are, your > opinion on if it was or was not a screw up is not relevant. > I see that http://fedoraproject.org/wiki/Docs_Project_Steering_Committee still has not been updated in the 3 months since several of the Steering Committee at that time were "fired" or "demoted" with out a proper election as covered here http://fedoraproject.org/wiki/Docs_Project_Steering_Committee_elections_process Please take the time to update these pages and any others that may refer to elected leadership. -- Bob ------------------------------------------------------------------------ | Robert 'Bob' Jensen || Fedora Unity Founder | | bob at fedoraunity.org || http://fedoraunity.org/ | | http://bjensen.fedorapeople.org/ | | http://blogs.fedoraunity.org/bobjensen | ------------------------------------------------------------------------ From chriswfedora at cawllc.com Sat Jul 25 15:22:34 2009 From: chriswfedora at cawllc.com (Christopher A. Williams) Date: Sat, 25 Jul 2009 09:22:34 -0600 Subject: Allowed Content In-Reply-To: <1248529789.2945.15.camel@skrelnick> References: <20090723183543.GI5734@alpha.rzhou.org> <20090723214821.GI3592@localhost.localdomain> <1248529789.2945.15.camel@skrelnick> Message-ID: <1248535359.9617.26.camel@spikehome.spikelan.local> On Sat, 2009-07-25 at 09:49 -0400, Mike Danko wrote: > > On Thu, 2009-07-23 at 17:48 -0400, Paul W. Frields wrote: > > On Thu, Jul 23, 2009 at 02:35:43PM -0400, Ricky Zhou wrote: > > > Hey, I mentioned a few recent fedora-docs-list threads at the last IRC > > > support operators[1], and they were generally very positive about > > > some of the howto/knowledge base ideas that have been brought up. > > > > > > One concern that they brought up was whether we have a policy on what > > > content can/cannot be on Fedora's wiki (or "official" Fedora docs), > > > something more specific than http://fedoraproject.org/wiki/ForbiddenItems. > > > > > > One example that was brought up is that we currently have a howto for > > > installing flash at http://fedoraproject.org/wiki/Flash, so there may be > > > some current confusion about this. > > > > > > I will keep in touch with the IRC support operators team and see what > > > allowed vs. not allowed topics are FAQs for them. > > > > > > Thanks, > > > Ricky > > > > > > [1] http://meetbot.fedoraproject.org/fedora-meeting/2009-07-23/fedora-meeting.2009-07-23-16.30.log.html > > > > Flash has a page because it is not illegal to use anywhere in the > > world that we know of, and the page provides up-front the suggestion > > that people try to use a FOSS implementation. Incidentally, it also > > does not impede other base functioning of the system that prevents > > effective debugging and troubleshooting. This is not true of > > encumbered add-ons like MP3, proprietary video drivers, and so on. > > > > Having said that, I'm not overjoyed about having a Flash page, and the > > reason I contributed so much to it myself was to make sure it was as > > clear and accurate as possible. I do recall there was discussion > > around the time of its creation, and would ask that before proposing > > any policy, the proposer should research that discussion. I would > > remove it to have a bright-line policy if required, but I do note that > > (1) it has first ranking on Google for "fedora flash", and (2) I'm > > pretty sure we've had a lot fewer Flash installation problems as a > > result. > > > > Those facts do not trump our mission, though, so if this page goes > > away, so be it. (The 2nd page is the unofficial Fedora FAQ which can > > just as easily serve this purpose.) The mission of Fedora is to > > advance free and open source software, which Flash is clearly not. > This is really tricky actually, and while being a Freedom loving > software advocate, there are lots of reasons to at least have content > available on how to use proprietary tools. This is a complex world, and > systems we use are complex SYSTEMS. > > For example, in my day job I've been told I can only run qualified > software on qualified hardware for doing certain tasks. By the time > things are actually qualified for our applications, hardware is EOL'd > and un-order-able. Is there any need to actually do things this way (at > least in our applications)? Not at all. People aren't even aware that > there are options to running Oracle on RHEL4 and using java 1.4.1. > > Ideally, yes, you'd want to use Free software on a Free system, but > there are advantages, especially with "enterprise grade" applications, > to using a Free system to run proprietary applications. > > I've been prepping a CC licensed book to getting started with database > development on Fedora, maybe what I'm saying will make more sense when I > have some available online. (Re-ordered the thread to "compensate" for the top-post of the last poster...) I have hesitated to jump into this thread, having inadvertently kicked over a venerable hornet's nest the last time I did. That said, I do believe the status quo of the Flash page is appropriate to both the mission of Fedora and the pragmatic needs of the Fedora community. There is an important difference (as is eluded to in my signature for this post) between being on a mission advocating the use of Free and Open Source software, and being on a mission advocating the non-use of software that doesn't fall into that category. I believe Fedora Project's stated mission is, appropriately, aligned with the first and not the second. Someone (like Paul F.) please correct me if that's not true. It is an unavoidable truth for both proprietary software companies who have an established hate for the FOSS way, and for Free Software companies and organizations - even those with a hate for proprietary software, that there will always be a pragmatic need on the part of people using these systems to appropriately mix both classes of software on the same machine. Not allowing for this is to live in an ideological fantasy land, regardless of which side you take. Such an orientation will only cost all of us in the end. OK - I have dawned my asbestos suit once more. Flame away if you care to...! Cheers, Chris -- ==================================================== "Patriotism is when love of your own people comes first; nationalism, when hate for people other than your own comes first." --Charles de Gaulle From david.nalley at fedoraproject.org Sun Jul 26 02:46:13 2009 From: david.nalley at fedoraproject.org (David Nalley) Date: Sat, 25 Jul 2009 22:46:13 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <1248469491.2659.10.camel@echristensen.tkctech.com> References: <1248373380.2702.25.camel@echristensen.tkctech.com> <20090724205926.GA7310@calliope.phig.org> <1248469491.2659.10.camel@echristensen.tkctech.com> Message-ID: On Fri, Jul 24, 2009 at 5:04 PM, Eric Christensen wrote: > On Fri, 2009-07-24 at 13:59 -0700, Karsten Wade wrote: >> On Thu, Jul 23, 2009 at 02:22:50PM -0400, Eric Christensen wrote: >> > The following members of the Docs FAS Group are showing as inactive in >> > FAS. ?Is there any reason to NOT remove these users from the Docs group? >> >> Would this inactivity cause them to be unable to edit the wiki? ?I >> presume so, but at least one name on the list (sfolkwil) I thought had >> contributed to one or both of the last sets of release notes (F9, F10). >> >> IMO, as long as people are able to come back at will (probably by >> re-introducing themselves, etc.), then it's really no worry, keep >> things clean, etc. > > They can come back at any time. ?No one on the list is anyone that has > been active in the Docs Project in some time (that I'm aware of). > > I think that when the account goes inactive then their password is > expired and they wouldn't be able to edit the wiki or access anything > else that is FAS related until they do a password reset. > > Eric > We just did something similar in the Ambassadors. That said, one of the eventualities is that Infrastructure will remove all groups from the individual inactive account (I don't know the timeline on this, the last time I asked Mike, he didn't have a firm timeframe) The path of least resistance is to just wait on infrastructure and they'll take care of it. I'll note that other groups have a 'auto-expire' function that is even more rigid, and perhaps might be something we should look into. AIUI, one of those groups, Gnome, requires that every two years a contributor. must essentially 're-apply' and justify their continued membership in a given group. I want to say that Art does the same thing, but I may be accusing them of that because Mo told me that's what Gnome does. The other question that exists, is what does docs group membership mean. What benefits/responsibilities accrue to one holding such membership. If nothing, perhaps we should do away with the group altogether and just use the individual document FAS groups. From bugzilla at redhat.com Sun Jul 26 16:16:40 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 26 Jul 2009 12:16:40 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907261616.n6QGGe8E003686@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Bug 504066 depends on bug 512025, which changed state. Bug 512025 Summary: Need to package zikula News module https://bugzilla.redhat.com/show_bug.cgi?id=512025 What |Old Value |New Value ---------------------------------------------------------------------------- Resolution| |CURRENTRELEASE Status|ASSIGNED |CLOSED -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Sun Jul 26 16:16:39 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 26 Jul 2009 12:16:39 -0400 Subject: [Bug 512025] Need to package zikula News module In-Reply-To: References: Message-ID: <200907261616.n6QGGdju003670@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=512025 Paul W. Frields changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |CURRENTRELEASE Bug 512025 depends on bug 512027, which changed state. Bug 512027 Summary: Review Request: zikula-module-News - Manages news articles on your Zikula site https://bugzilla.redhat.com/show_bug.cgi?id=512027 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |ERRATA --- Comment #5 from Paul W. Frields 2009-07-26 12:16:39 EDT --- zikula-module-News-2.4.1-2.noarch is now in stable updates. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. From stickster at gmail.com Sun Jul 26 19:02:17 2009 From: stickster at gmail.com (Paul W. Frields) Date: Sun, 26 Jul 2009 15:02:17 -0400 Subject: [PATCH] Replace boot.iso guidance with netinst.iso guidance Message-ID: <1248634937-11896-1-git-send-email-stickster@gmail.com> The older boot.iso file is no longer included on the installation DVD as of F-11, and has been supplanted by netinst.iso, which is distributed at mirrors alongside the DVD image itself. --- en-US/Installer.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/en-US/Installer.xml b/en-US/Installer.xml index 3a98af5..964a3ff 100644 --- a/en-US/Installer.xml +++ b/en-US/Installer.xml @@ -78,10 +78,10 @@ -
- Updated <filename>boot.iso</filename> +
+ Updated <filename>netinst.iso</filename> - The Fedora installation CDs and DVD provide you with an image file, boot.iso, that you can burn to a CD and use to boot a system and start the installation process. Typically, you would do this prior to installing Fedora from a local hard drive or from a location on a network. You can now use the CD produced from the boot.iso image to start installation on a system that uses Unified Extensible Firmware Interface (UEFI). CDs produced from older versions of boot.iso only worked with systems that used Basic Input Output System (BIOS). + The Installation DVD no longer provides the boot.iso image file. Instead, the download mirrors that provide the DVD image file also provide a netinst.iso file. This file can be burnt to a CD and used to boot a system to start the installation process. Typically, you would do this prior to installing Fedora from a local hard drive or from a location on a network. You can now use the CD produced from the netinst.iso image to start installation on a system that uses Unified Extensible Firmware Interface (UEFI). CDs produced from older versions of boot.iso only worked with systems that used Basic Input Output System (BIOS).
-- 1.6.2.5 From stickster at gmail.com Sun Jul 26 21:24:03 2009 From: stickster at gmail.com (Paul W. Frields) Date: Sun, 26 Jul 2009 17:24:03 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <31420511.10011248535228212.JavaMail.root@zimbra.cbccgroup.com> References: <19867053.9991248535178558.JavaMail.root@zimbra.cbccgroup.com> <31420511.10011248535228212.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <20090726212403.GE5187@localhost.localdomain> On Sat, Jul 25, 2009 at 03:20:28PM +0000, Robert 'Bob' Jensen wrote: > I see that > http://fedoraproject.org/wiki/Docs_Project_Steering_Committee still > has not been updated in the 3 months since several of the Steering > Committee at that time were "fired" or "demoted" with out a proper > election as covered here > http://fedoraproject.org/wiki/Docs_Project_Steering_Committee_elections_process > Please take the time to update these pages and any others that may > refer to elected leadership. That's not correct. The page has been moved to the Archive, perhaps you didn't notice because of the wiki's redirection facility. Also, it has a banner at the top indicating it's been deprecated. Both of these things were done as requested when you last brought this subject up in April. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From bugzilla at redhat.com Mon Jul 27 03:23:11 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 26 Jul 2009 23:23:11 -0400 Subject: [Bug 513907] New: SRPMs fail to build in Koji Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: SRPMs fail to build in Koji https://bugzilla.redhat.com/show_bug.cgi?id=513907 Summary: SRPMs fail to build in Koji Product: Fedora Version: 11 Platform: All OS/Version: Linux Status: NEW Severity: urgent Priority: high Component: publican AssignedTo: jfearn at redhat.com ReportedBy: eric at christensenplace.us QAContact: extras-qa at fedoraproject.org CC: jfearn at redhat.com, fedora-docs-list at redhat.com, mmcallis at redhat.com Classification: Fedora Description of problem: SRPMs fail to build in Koji due to the following error: Processing files: fedora-security-guide-en-US-1.0-16.fc12.noarch error: Two files on one line: /usr/share/applications/Fedora error: File must begin with "/": Projectfedora-security-guide-en-US.desktop Version-Release number of selected component (if applicable): 0.44-0.fc11 Possible Fix: Remove the %{?vendoropt} from desktop-file-install %{?vendoropt} --dir=${RPM_BUILD_ROOT}%{_datadir}/applications %{name}.desktop or remove %{vendor} all together. I'll be testing this soon to see if I can provide a patch. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 03:43:54 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Sun, 26 Jul 2009 23:43:54 -0400 Subject: [Bug 513907] SRPMs fail to build in Koji In-Reply-To: References: Message-ID: <200907270343.n6R3hsXj003831@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #1 from Jeff Fearn 2009-07-26 23:43:53 EDT --- As I recall, and it has been a while, vendoropt was added during the review of publican as it is a required field. So removing it would seem to be the wrong thing. It looks to me like your package name is contains "Fedora Project" with a space, this is not a valid package name since spaces are not allowed in package names. Please attach the spec file so I can take a look at it. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From ccurran at redhat.com Mon Jul 27 07:35:08 2009 From: ccurran at redhat.com (Christopher Curran) Date: Mon, 27 Jul 2009 17:35:08 +1000 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <31420511.10011248535228212.JavaMail.root@zimbra.cbccgroup.com> References: <31420511.10011248535228212.JavaMail.root@zimbra.cbccgroup.com> Message-ID: <4A6D58AC.9090404@redhat.com> Robert 'Bob' Jensen wrote: > ----- "Robert 'Bob' Jensen" wrote: > >> Oh Eric, >> >> You did screw up, you did lose at least one contributor, me, and to >> top it off you never even apologised for your actions, this is why you >> will not find my name in FAS as a Fedora Docs contributor. You let >> Paul and Karsten apologize and try to cover with "oh he's new" kind of >> responses. You are not the judge of your screw ups others are, your >> opinion on if it was or was not a screw up is not relevant. >> >> > > I see that http://fedoraproject.org/wiki/Docs_Project_Steering_Committee still has not been updated in the 3 months since several of the Steering Committee at that time were "fired" or "demoted" with out a proper election as covered here http://fedoraproject.org/wiki/Docs_Project_Steering_Committee_elections_process Please take the time to update these pages and any others that may refer to elected leadership. > > -- Bob > > ------------------------------------------------------------------------ > | Robert 'Bob' Jensen || Fedora Unity Founder | > | bob at fedoraunity.org || http://fedoraunity.org/ | > | http://bjensen.fedorapeople.org/ | > | http://blogs.fedoraunity.org/bobjensen | > ------------------------------------------------------------------------ > > I'm not sure there is much need for a Steering Committee at all. We should just have more oarsman and sailors. Chris (Tsagadai) From stickster at gmail.com Mon Jul 27 12:10:27 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 27 Jul 2009 08:10:27 -0400 Subject: Removing inactive members from the Docs FAS Group In-Reply-To: <4A6D58AC.9090404@redhat.com> References: <31420511.10011248535228212.JavaMail.root@zimbra.cbccgroup.com> <4A6D58AC.9090404@redhat.com> Message-ID: <20090727121027.GC13895@localhost.localdomain> On Mon, Jul 27, 2009 at 05:35:08PM +1000, Christopher Curran wrote: > I'm not sure there is much need for a Steering Committee at all. We > should just have more oarsman and sailors. Which is precisely why that page has been marked obsolete and archived, IIRC. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From wb8rcr at arrl.net Mon Jul 27 12:32:32 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 27 Jul 2009 08:32:32 -0400 Subject: Release Notes Schedule Message-ID: <192D57B9304543F3BE49371BB709988B@Aidan> As I dug into John Poelstra's schedule in more detail, I noticed a few issues that I hadn't noticed in earlier reviews. Specifically, very long times on some short tasks with short times on some more difficult tasks, and tasks out of order. Since I don't have a really good feel for the guides, I put together what I thought was a more workable schedule for release notes only. Eric was going to look at guides. My strawman is at: http://jjmcd.fedorapeople.org/F12RN2a.html I fixed major milestones to the same dates that John had so hopefully we don't affect other teams. However, I did put a couple of L10N tasks on the list since they are tied closely to us. I have not, however, had any discussion with L10N as to whether these times make any sense at all to them. John suggested we get together in a Gobby/Talk meeting to get this schedule into sync with his. I think we need to get the guides schedule integrated with this and include a representative from L10N in that meeting. Because of the new definition of alpha and beta, our schedule looks a lot different than earlier releases. Specifically, since alpha should be "feature complete", we should have almost everything we need for release notes by alpha. That means the bulk of our work is between alpha and beta. However, since Beta should include more or less complete release notes, L10N will need time to translate them. That pushes Docs work forward some, meaning we will have a real scramble right around alpha, and L10N will have a pile of work just before beta. The upside is that the work before GA should be a little less onerous, and there should be little left to translate. If we can make our plan of a table for all changes and prose only for significant effort required to convert plus highlighting high-profile features, there should be a lot less prose to write (and translate) than previous releases. We will, however, need some pretty aggressive wiki gardening to allow us to convert to XML quickly. I would like everyone to take a really close look at this, and comment on it on this list. I think I have the major tasks identified, but it is always good to have more input. Thanks --McD From bugzilla at redhat.com Mon Jul 27 12:35:39 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 08:35:39 -0400 Subject: [Bug 513907] SRPMs fail to build in Koji In-Reply-To: References: Message-ID: <200907271235.n6RCZdiI011114@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #2 from Eric Christensen 2009-07-27 08:35:38 EDT --- Hi Jeff, Yeah, it's getting the "Fedora Project" from the vendoropt. The package name is Fedora-Security-Guide. SPEC: http://cvs.fedoraproject.org/viewvc/rpms/fedora-security-guide-en-US/devel/fedora-security-guide-en-US.spec?revision=1.4&view=markup Thanks, Eric -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From stickster at gmail.com Mon Jul 27 12:41:05 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 27 Jul 2009 08:41:05 -0400 Subject: Release Notes Schedule In-Reply-To: <192D57B9304543F3BE49371BB709988B@Aidan> References: <192D57B9304543F3BE49371BB709988B@Aidan> Message-ID: <20090727124105.GE13895@localhost.localdomain> On Mon, Jul 27, 2009 at 08:32:32AM -0400, John J. McDonough wrote: > As I dug into John Poelstra's schedule in more detail, I noticed a few > issues that I hadn't noticed in earlier reviews. Specifically, very long > times on some short tasks with short times on some more difficult tasks, > and tasks out of order. > > Since I don't have a really good feel for the guides, I put together what > I thought was a more workable schedule for release notes only. Eric was > going to look at guides. My strawman is at: > > http://jjmcd.fedorapeople.org/F12RN2a.html > > I fixed major milestones to the same dates that John had so hopefully we > don't affect other teams. However, I did put a couple of L10N tasks on > the list since they are tied closely to us. I have not, however, had any > discussion with L10N as to whether these times make any sense at all to > them. > > John suggested we get together in a Gobby/Talk meeting to get this > schedule into sync with his. I think we need to get the guides schedule > integrated with this and include a representative from L10N in that > meeting. > > Because of the new definition of alpha and beta, our schedule looks a lot > different than earlier releases. Specifically, since alpha should be > "feature complete", we should have almost everything we need for release > notes by alpha. That means the bulk of our work is between alpha and > beta. However, since Beta should include more or less complete release > notes, L10N will need time to translate them. That pushes Docs work > forward some, meaning we will have a real scramble right around alpha, and > L10N will have a pile of work just before beta. The upside is that the > work before GA should be a little less onerous, and there should be little > left to translate. > > If we can make our plan of a table for all changes and prose only for > significant effort required to convert plus highlighting high-profile > features, there should be a lot less prose to write (and translate) than > previous releases. We will, however, need some pretty aggressive wiki > gardening to allow us to convert to XML quickly. > > I would like everyone to take a really close look at this, and comment on > it on this list. I think I have the major tasks identified, but it is > always good to have more input. Hi John, Can you explain what the "Review f-r-n.html" tasks are for? I noticed that these take several days to a week and that L10n doesn't get the content until after that happens. Is this something that could be combined with the XML conversion so that L10n could have a longer time available to translate content? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From bugzilla at redhat.com Mon Jul 27 13:48:58 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 09:48:58 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907271348.n6RDmw1X029473@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #4 from Elio Maldonado Batiz 2009-07-27 09:48:57 EDT --- Created an attachment (id=355276) --> (https://bugzilla.redhat.com/attachment.cgi?id=355276) spec file for review as requested -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 13:52:18 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 09:52:18 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907271352.n6RDqIQU030140@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Elio Maldonado Batiz changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #355276|text/ascii |text/plain mime type| | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 13:52:57 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 09:52:57 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907271352.n6RDqvni012227@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #5 from Elio Maldonado Batiz 2009-07-27 09:52:56 EDT --- (In reply to comment #1) See attachment. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 13:50:50 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 09:50:50 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907271350.n6RDooB4011791@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Elio Maldonado Batiz changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #355276|application/octet-stream |text/ascii mime type| | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 13:39:14 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 09:39:14 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907271339.n6RDdEhT008686@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Elio Maldonado Batiz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaldona at redhat.com Summary|SRPMs fail to build in Koji |NSS debug-info RPM fails to | |build in Koji --- Comment #3 from Elio Maldonado Batiz 2009-07-27 09:39:13 EDT --- Corrected the bug summary to reflect the actual problem. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From wb8rcr at arrl.net Mon Jul 27 14:12:42 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 27 Jul 2009 10:12:42 -0400 Subject: Release Notes Schedule References: <192D57B9304543F3BE49371BB709988B@Aidan> <20090727124105.GE13895@localhost.localdomain> Message-ID: <0E09E85B5E6E498DBC0915CDA22B5427@Aidan> ----- Original Message ----- From: "Paul W. Frields" To: ; Sent: Monday, July 27, 2009 8:41 AM Subject: Re: Release Notes Schedule > Can you explain what the "Review f-r-n.html" tasks are for? I noticed > that these take several days to a week and that L10n doesn't get the > content until after that happens. Is this something that could be > combined with the XML conversion so that L10n could have a longer time > available to translate content? If we do a really good job of wiki grooming, we shouldn't even need that, but it seems like we always discover a bunch of problems at the last minute. I was hoping to avoid the last-minute changes that frustrate the translators so. HOWEVER, Sparks just informed me that I have the GA date wrong, so I need to go re-work that schedule. Don't know whether I was looking at the wrong schedule or just fat-fingered it, but it looks like we have an additional month. --McD From stickster at gmail.com Mon Jul 27 15:39:26 2009 From: stickster at gmail.com (Paul W. Frields) Date: Mon, 27 Jul 2009 11:39:26 -0400 Subject: Release Notes Schedule In-Reply-To: <0E09E85B5E6E498DBC0915CDA22B5427@Aidan> References: <192D57B9304543F3BE49371BB709988B@Aidan> <20090727124105.GE13895@localhost.localdomain> <0E09E85B5E6E498DBC0915CDA22B5427@Aidan> Message-ID: <20090727153926.GL17605@localhost.localdomain> On Mon, Jul 27, 2009 at 10:12:42AM -0400, John J. McDonough wrote: > > ----- Original Message ----- From: "Paul W. Frields" > To: ; > Sent: Monday, July 27, 2009 8:41 AM > Subject: Re: Release Notes Schedule > > >> Can you explain what the "Review f-r-n.html" tasks are for? I noticed >> that these take several days to a week and that L10n doesn't get the >> content until after that happens. Is this something that could be >> combined with the XML conversion so that L10n could have a longer time >> available to translate content? > > If we do a really good job of wiki grooming, we shouldn't even need that, > but it seems like we always discover a bunch of problems at the last > minute. I was hoping to avoid the last-minute changes that frustrate the > translators so. > > HOWEVER, Sparks just informed me that I have the GA date wrong, so I need > to go re-work that schedule. Don't know whether I was looking at the > wrong schedule or just fat-fingered it, but it looks like we have an > additional month. https://fedoraproject.org/wiki/Schedule FWIW, that's the overall calendar, but John's more detailed schedules are here: http://poelstra.fedorapeople.org/schedules/f-12/ (This info provided mainly to benefit those who might not know where to find these already.) -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From dhensley at redhat.com Mon Jul 27 18:44:13 2009 From: dhensley at redhat.com (Douglas Silas Hensley) Date: Mon, 27 Jul 2009 20:44:13 +0200 Subject: Project Start: New Updated Deployment Guide for the Upcoming Fedora 12! Message-ID: <4A6DF57D.30102@redhat.com> Greetings Fedora users and system administrators, I meant to announce this last week on fedora-docs-list, but the CC slipped my mind. Here's copy of the announcement I sent to deployment-guide-list at redhat.com. See the Deployment Guide wiki: https://fedorahosted.org/deploymentguide/wiki ...for details on joining this list. All are welcome. ORIGINAL ANNOUNCEMENT I'm proud to announce that I'll be heading a new project to update a new guide, the Fedora Deployment Guide, for the upcoming Fedora 12 release! The Fedora Deployment Guide covers system administration tasks such as package maintenance, user administration, printing, and setting up networks, printers, and services such as Apache, LDAP, OpenSSH, Samba, etc. You can see what's in it and the most current state of the upcoming Fedora 12 Deployment Guide here: http://dsilas.fedorapeople.org/Deployment_Guide/en-US/ The target for completion of this project is before Nov. 1, ahead of the GA target date for Fedora 12, which is currently Nov. 3. The project page for the Deployment Guide, which also tells you where to obtain the source files (which are in DocBook XML), is here: https://fedorahosted.org/deploymentguide/wiki We will definitely be accepting contributors; please contact me if you are able to help out. There is a Deployment Guide mailing list. To gain access to it, please send an email to the project maintainers (of whom I am one) with a brief introduction: https://www.redhat.com/mailman/listinfo/deployment-guide-list The Fedora Deployment Guide is written in DocBook XML and is published using the open source Publican build tool: https://fedorahosted.org/publican/ More details will follow next week (such as additions to the TOC). I hope to hear suggestions and opinions from you! Cheers, -- Douglas Silas Technical Writer | Red Hat, Inc. Purky?ova 99 | Brno, Czech Republic Office Direct Dial?62116 Brno Office?(+420) 532 294 111 ext. 10718 dhensley at redhat.com From bugzilla at redhat.com Mon Jul 27 18:53:50 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 14:53:50 -0400 Subject: [Bug 514046] New: Oracle-xe page for Spacewalk doesn't work Message-ID: Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: Oracle-xe page for Spacewalk doesn't work https://bugzilla.redhat.com/show_bug.cgi?id=514046 Summary: Oracle-xe page for Spacewalk doesn't work Product: Fedora Hosted Projects Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: Deployment_Guide AssignedTo: mhideo at redhat.com ReportedBy: mschwage at gmail.com QAContact: rlerch at redhat.com CC: fedora-docs-list at redhat.com Classification: Fedora Description of problem: Sorry about the classification of this. I didn't see Spacewalk anywhere in Bugzilla! Anyway, on the webpage https://fedorahosted.org/spacewalk/wiki/OracleXeSetup#Install, the install instructions don't work as advertised. There, it says "Configure the Oracle XE database by running # /etc/init.d/oracle-xe configure" This did not set the system/sys name correctly. Yes, I know, the oracle-xe command comes from Oracle themselves, but on my RHEL53 machine it just refused to set the password correctly. Did I try to do it 10 times or more? Yes I did, and it did not work at all. Did I fat finger my password every single lousy time I tried it? No I did not, for I was able to create my password as easy as you please using my workaround below. Version-Release number of selected component (if applicable): oracle-xe-univ-10.2.0.1-1.0 oracle-instantclient-basic-10.2.0.4-1 oracle-instantclient-sqlplus-10.2.0.4-1 How reproducible: Every time. Steps to Reproduce: 1. Do this on RHEL53 x86_64. Install the Oracle-XE software as listed. 2. Follow the instructions on https://fedorahosted.org/spacewalk/wiki/OracleXeSetup#Install, up to and including the "Test Your Connection with SQLPlus" part. 3. You fail to login. Actual results: Fail to login. Expected results: Successful login. Additional info: The workaround is to perform the following after running /etc/init.d/oracle-xe configure : su - oracle . /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/bin/oracle_env.sh /usr/lib/oracle/10.2.0.4/client64/bin/sqlplus /NOLOG CONNECT / AS SYSDBA alter user sys identified by password; alter user system identified by password; sqlplus64 'sys at xe as sysdba' -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From cpanceac at gmail.com Mon Jul 27 18:59:02 2009 From: cpanceac at gmail.com (cornel panceac) Date: Mon, 27 Jul 2009 21:59:02 +0300 Subject: Project Start: New Updated Deployment Guide for the Upcoming Fedora 12! In-Reply-To: <4A6DF57D.30102@redhat.com> References: <4A6DF57D.30102@redhat.com> Message-ID: 2009/7/27 Douglas Silas Hensley > Greetings Fedora users and system administrators, > > I meant to announce this last week on fedora-docs-list, but the CC slipped > my mind. Here's copy of the announcement I sent to > deployment-guide-list at redhat.com. See the Deployment Guide wiki: > > https://fedorahosted.org/deploymentguide/wiki > > ...for details on joining this list. All are welcome. > > ORIGINAL ANNOUNCEMENT > I'm proud to announce that I'll be heading a new project to update a new > guide, the Fedora Deployment Guide, for the upcoming Fedora 12 release! The > Fedora Deployment Guide covers system administration tasks such as package > maintenance, user administration, printing, and setting up networks, > printers, and services such as Apache, LDAP, OpenSSH, Samba, etc. > > You can see what's in it and the most current state of the upcoming Fedora > 12 Deployment Guide here: > > http://dsilas.fedorapeople.org/Deployment_Guide/en-US/ > > The target for completion of this project is before Nov. 1, ahead of the GA > target date for Fedora 12, which is currently Nov. 3. > > The project page for the Deployment Guide, which also tells you where to > obtain the source files (which are in DocBook XML), is here: > > https://fedorahosted.org/deploymentguide/wiki > > We will definitely be accepting contributors; please contact me if you are > able to help out. There is a Deployment Guide mailing list. To gain access > to it, please send an email to the project maintainers (of whom I am one) > with a brief introduction: > > https://www.redhat.com/mailman/listinfo/deployment-guide-list > > The Fedora Deployment Guide is written in DocBook XML and is published > using the open source Publican build tool: > > https://fedorahosted.org/publican/ > > More details will follow next week (such as additions to the TOC). > > I hope to hear suggestions and opinions from you! > > Cheers, > -- > Douglas Silas > Technical Writer | Red Hat, Inc. > Purky?ova 99 | Brno, Czech Republic > Office Direct Dial--62116 > Brno Office--(+420) 532 294 111 ext. 10718 > dhensley at redhat.com > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list > can rhn manage fedora systems? -- Linux counter #213090 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cpanceac at gmail.com Mon Jul 27 19:13:26 2009 From: cpanceac at gmail.com (cornel panceac) Date: Mon, 27 Jul 2009 22:13:26 +0300 Subject: Project Start: New Updated Deployment Guide for the Upcoming Fedora 12! In-Reply-To: References: <4A6DF57D.30102@redhat.com> Message-ID: 2009/7/27 cornel panceac > > 2009/7/27 Douglas Silas Hensley > > Greetings Fedora users and system administrators, >> >> I meant to announce this last week on fedora-docs-list, but the CC slipped >> my mind. Here's copy of the announcement I sent to >> deployment-guide-list at redhat.com. See the Deployment Guide wiki: >> >> https://fedorahosted.org/deploymentguide/wiki >> >> ...for details on joining this list. All are welcome. >> >> ORIGINAL ANNOUNCEMENT >> I'm proud to announce that I'll be heading a new project to update a new >> guide, the Fedora Deployment Guide, for the upcoming Fedora 12 release! The >> Fedora Deployment Guide covers system administration tasks such as package >> maintenance, user administration, printing, and setting up networks, >> printers, and services such as Apache, LDAP, OpenSSH, Samba, etc. >> >> You can see what's in it and the most current state of the upcoming Fedora >> 12 Deployment Guide here: >> >> http://dsilas.fedorapeople.org/Deployment_Guide/en-US/ >> >> The target for completion of this project is before Nov. 1, ahead of the >> GA target date for Fedora 12, which is currently Nov. 3. >> >> The project page for the Deployment Guide, which also tells you where to >> obtain the source files (which are in DocBook XML), is here: >> >> https://fedorahosted.org/deploymentguide/wiki >> >> We will definitely be accepting contributors; please contact me if you are >> able to help out. There is a Deployment Guide mailing list. To gain access >> to it, please send an email to the project maintainers (of whom I am one) >> with a brief introduction: >> >> https://www.redhat.com/mailman/listinfo/deployment-guide-list >> >> The Fedora Deployment Guide is written in DocBook XML and is published >> using the open source Publican build tool: >> >> https://fedorahosted.org/publican/ >> >> More details will follow next week (such as additions to the TOC). >> >> I hope to hear suggestions and opinions from you! > > >> >> Cheers, >> -- >> Douglas Silas >> Technical Writer | Red Hat, Inc. >> Purky?ova 99 | Brno, Czech Republic >> Office Direct Dial--62116 >> Brno Office--(+420) 532 294 111 ext. 10718 >> dhensley at redhat.com >> >> -- >> fedora-docs-list mailing list >> fedora-docs-list at redhat.com >> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list >> > > can rhn manage fedora systems? > the screenshots are from rhel, not fedora. and there's no up2date in fedora 12, afaict. > > > -- > Linux counter #213090 > -- Linux counter #213090 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Mon Jul 27 21:17:44 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 17:17:44 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907272117.n6RLHi5c027929@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #6 from Jeff Fearn 2009-07-27 17:17:43 EDT --- According to https://fedoraproject.org/wiki/Packaging/Guidelines#desktop-file-install_usage the vendor tag should only be used for existing packaging that use it ... so you need to remove it from the spec file. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 21:22:08 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 17:22:08 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907272122.n6RLM8KE028894@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #7 from Eric Christensen 2009-07-27 17:22:07 EDT --- I agree. That SPEC is how Publican generates it. So can it be removed? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 22:04:31 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 18:04:31 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907272204.n6RM4Vnv007548@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Elio Maldonado Batiz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kengert at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 22:25:14 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 18:25:14 -0400 Subject: [Bug 430721] Additional Information Requested for Apache Setup In-Reply-To: References: Message-ID: <200907272225.n6RMPEMp031771@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=430721 --- Comment #1 from Douglas Silas 2009-07-27 18:25:13 EDT --- This information is a part of the Fedora Deployment Guide, although it will need to be reviewed to assure F12 correctness. In progress. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 22:44:01 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 18:44:01 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907272244.n6RMi1JZ002550@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #8 from Elio Maldonado Batiz 2009-07-27 18:44:00 EDT --- I can change spec to follow the guidelines but this has nothing to do with the problem I reported. An email sent to release-engineering automatically created this bug report. ----- Original Message ----- From: "Dennis Gregorovic" To: "Elio Maldonado" Cc: "David Malcolm" , jorris at redhat.com, kengert at redhat.com, "Scott Haines" , "os-releng-list" Sent: Thursday, July 23, 2009 10:25:06 AM GMT -08:00 US/Canada Pacific Subject: Re: Changed Errata Request [RHBA-2009:8601-02] nss bug fix update On Mon, 2009-07-20 at 12:16 -0700, Elio Maldonado wrote: > > > > Correcting a prior reply and adding Release Enginnering as this problem seems to be caused by the rpm build tools. > > > > The URL for the latest report is > > https://errata.devel.redhat.com/rpmdiff/show/39254 > > Clicking on the Symbolic Links brings up > > https://errata.devel.redhat.com/rpmdiff/show/39254.?result_id=419473 > > which lists three dangling symbolic links. There are actually fifteen or dangling symbolic links as I was able to verify. Nothing wrong with rpmdiff as it just detects differences with the base for comparison. > > > > Kai and I investigated and found out that even the prior release had this problem with thirty one dangling symbolic links as per his inspection! > > > > I did the same build but on a RHEL-5 system and the problem does not happen there. Of course, the build must be done on a RHEL 4 machine as this is tne intended target but we needed to investigate and rule out differences in the spec file as the cause. The tool doing the copy is /usr/lib/rpm/find-debuginfo.sh. We believe this is a problem with the older older version of the rpm build tools that ships with RHEL-4. The find-debuginfo.sh doesn't seem to handle well the case where some files are copied twice which me must do in order to replace the softoken that normally comes with the latest NSS with the older softokn that's FIPS certified. If you wish more details Kai will be able to explain his diagnostic more clearly than I can. > > > > From our investigation we think that the problem is caused by the older version of the RPM build tools in RHEL-4. To get this fixed, we would need to get a bug filed against the RPM component and for that bug to get approved. Given that RHEL 4 is nearing its end of life and that this issue does not affect most packages, I think our best course of action is to live with the dangling symlinks. However, if the dangling symlinks present too much of a problem, we can see about getting RPM fixed. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 22:45:59 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 18:45:59 -0400 Subject: [Bug 513907] NSS debug-info RPM fails to build in Koji In-Reply-To: References: Message-ID: <200907272245.n6RMjxbZ015340@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #9 from Elio Maldonado Batiz 2009-07-27 18:45:58 EDT --- Sorry, it came out that way for lack of hard-coded newlines. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 27 23:20:37 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 19:20:37 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907272320.n6RNKbs9021969@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|NSS debug-info RPM fails to |fedora-security-guide-en-US |build in Koji |goes boom in koji -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 00:06:57 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:06:57 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280006.n6S06vUs018425@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Jens Petersen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petersen at redhat.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 00:14:21 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:14:21 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280014.n6S0ELaV019899@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #11 from Jens Petersen 2009-07-27 20:14:20 EDT --- I wonder what changed since http://koji.fedoraproject.org/koji/taskinfo?taskID=1416027 ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From wb8rcr at arrl.net Tue Jul 28 00:20:14 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Mon, 27 Jul 2009 20:20:14 -0400 Subject: Release Notes Schedule References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> Message-ID: ----- Original Message ----- From: "Paul W. Frields" To: ; Sent: Monday, July 27, 2009 11:39 AM Subject: Re: Release Notes Schedule > > https://fedoraproject.org/wiki/Schedule > > FWIW, that's the overall calendar, but John's more detailed schedules > are here: > > http://poelstra.fedorapeople.org/schedules/f-12/ > > (This info provided mainly to benefit those who might not know where > to find these already.) > Updated strawman at http://jjmcd.fedorapeople.org/F12RN4a.html I believe this is consistent with http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-tasks.html as far as major milestones go, but f-12-docs-tasks does have a number of issues which this is intended to correct. Again, please go through this, see whether it makes sense. I left the reviews in there, but by eliminating them we could give L10N a little more time, at the possible cost of having more updates later. This schedule does anticipate that the bulk of the release notes effort will be completed for beta, and the general availability release notes will simply be updates to reflect issues uncovered during beta. It remains to be seen how disciplined we can be about "feature complete". --McD From bugzilla at redhat.com Tue Jul 28 00:20:55 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:20:55 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280020.n6S0Kt9u000613@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #12 from Eric Christensen 2009-07-27 20:20:55 EDT --- Yeah, that's what I was wondering. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 00:24:54 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:24:54 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280024.n6S0Osuu021714@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #13 from Jeff Fearn 2009-07-27 20:24:54 EDT --- Clearly the vendor tag has changed from 'fedora' to 'Fedora Project'. (In reply to comment #7) > I agree. That SPEC is how Publican generates it. So can it be removed? That vendor stuff was only added because it was a fedora packaging requirement. Since there are no existing books being shipped in Fedora, my solution would be to pull it out entirely from the next version. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 00:32:48 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:32:48 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280032.n6S0WmmW023406@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #14 from Eric Christensen 2009-07-27 20:32:48 EDT --- I agree. I don't see the need for it, here. Is this something in the fedora "brand" or ??? I'd be happy to pull it out of the code and provide a patch if you can point me in the direction of the proper file. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 00:37:25 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:37:25 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280037.n6S0bP6D003585@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Elio Maldonado Batiz changed: What |Removed |Added ---------------------------------------------------------------------------- CC|emaldona at redhat.com | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 00:41:37 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 20:41:37 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280041.n6S0fbgv024857@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #15 from Jeff Fearn 2009-07-27 20:41:37 EDT --- (In reply to comment #14) > I agree. I don't see the need for it, here. > > Is this something in the fedora "brand" or ??? I'd be happy to pull it out of > the code and provide a patch if you can point me in the direction of the proper > file. It's in /usr/share/publican/xsl/dt_htmlsingle_spec.xsl You need to remove all references to vendor and vendoropt. Here is a diff: --- /usr/share/publican/xsl/dt_htmlsingle_spec.xsl 2009-03-27 12:12:05.000000000 +1000 +++ dt_htmlsingle_spec.xsl 2009-07-28 10:37:47.000000000 +1000 @@ -17,8 +17,6 @@ %if %{HTMLVIEW} %define viewer htmlview -%define vendor redhat- -%define vendoropt --vendor="redhat" %endif Name: - @@ -66,7 +64,7 @@ Terminal=false EOF -desktop-file-install %{?vendoropt} --dir=${RPM_BUILD_ROOT}%{_datadir}/applications %{name}.desktop +desktop-file-install --dir=${RPM_BUILD_ROOT}%{_datadir}/applications %{name}.desktop %clean rm -rf $RPM_BUILD_ROOT @@ -74,7 +72,7 @@ %files %defattr(-,root,root,-) %doc tmp//html-desktop/* -%{_datadir}/applications/%{?vendor}%{name}.desktop +%{_datadir}/applications/%{name}.desktop %changelog -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From ccurran at redhat.com Tue Jul 28 01:03:57 2009 From: ccurran at redhat.com (Christopher Curran) Date: Tue, 28 Jul 2009 11:03:57 +1000 Subject: Project Start: New Updated Deployment Guide for the Upcoming Fedora 12! In-Reply-To: References: <4A6DF57D.30102@redhat.com> Message-ID: <4A6E4E7D.7050503@redhat.com> cornel panceac wrote: > > > 2009/7/27 cornel panceac > > > > 2009/7/27 Douglas Silas Hensley > > > Greetings Fedora users and system administrators, > > I meant to announce this last week on fedora-docs-list, but > the CC slipped my mind. Here's copy of the announcement I sent > to deployment-guide-list at redhat.com > . See the Deployment > Guide wiki: > > https://fedorahosted.org/deploymentguide/wiki > > ...for details on joining this list. All are welcome. > > ORIGINAL ANNOUNCEMENT > I'm proud to announce that I'll be heading a new project to > update a new guide, the Fedora Deployment Guide, for the > upcoming Fedora 12 release! The Fedora Deployment Guide covers > system administration tasks such as package maintenance, user > administration, printing, and setting up networks, printers, > and services such as Apache, LDAP, OpenSSH, Samba, etc. > > You can see what's in it and the most current state of the > upcoming Fedora 12 Deployment Guide here: > > http://dsilas.fedorapeople.org/Deployment_Guide/en-US/ > > The target for completion of this project is before Nov. 1, > ahead of the GA target date for Fedora 12, which is currently > Nov. 3. > > The project page for the Deployment Guide, which also tells > you where to obtain the source files (which are in DocBook > XML), is here: > > https://fedorahosted.org/deploymentguide/wiki > > We will definitely be accepting contributors; please contact > me if you are able to help out. There is a Deployment Guide > mailing list. To gain access to it, please send an email to > the project maintainers (of whom I am one) with a brief > introduction: > > https://www.redhat.com/mailman/listinfo/deployment-guide-list > > The Fedora Deployment Guide is written in DocBook XML and is > published using the open source Publican build tool: > > https://fedorahosted.org/publican/ > > More details will follow next week (such as additions to the TOC). > > I hope to hear suggestions and opinions from you! > > > > Cheers, > -- > Douglas Silas > Technical Writer | Red Hat, Inc. > Purkyn(ova 99 | Brno, Czech Republic > Office Direct Dial?62116 > Brno Office?(+420) 532 294 111 ext. 10718 > dhensley at redhat.com > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > > > can rhn manage fedora systems? > > > the screenshots are from rhel, not fedora. > and there's no up2date in fedora 12, afaict. Bug fixes welcome. This is the idea behind developing documentation, it isn't perfect originally so it needs some work. You are more than welcome to help fix these issues. Chris From bugzilla at redhat.com Tue Jul 28 01:07:17 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 21:07:17 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280107.n6S17HBd029521@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 Jeff Fearn changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Fixed In Version| |1.0 Resolution| |NEXTRELEASE --- Comment #16 from Jeff Fearn 2009-07-27 21:07:17 EDT --- This change is in place for the next release. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 03:47:23 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 27 Jul 2009 23:47:23 -0400 Subject: [Bug 513907] fedora-security-guide-en-US goes boom in koji In-Reply-To: References: Message-ID: <200907280347.n6S3lNuB028857@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=513907 --- Comment #17 from Eric Christensen 2009-07-27 23:47:22 EDT --- Yeah, all is well here... Thanks! -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 28 04:08:05 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 28 Jul 2009 00:08:05 -0400 Subject: [Bug 514046] Oracle-xe page for Spacewalk doesn't work In-Reply-To: References: Message-ID: <200907280408.n6S4851K012811@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=514046 Jonathan Steffan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathansteffan at gmail.com Component|Deployment_Guide |Documentation Version|unspecified |0.5 AssignedTo|mhideo at redhat.com |jha at redhat.com Product|Fedora Hosted Projects |Spacewalk QAContact|rlerch at redhat.com |satellite-qa-list at redhat.co | |m --- Comment #1 from Jonathan Steffan 2009-07-28 00:08:04 EDT --- I've run into similar issues. The exact issue I ran into was the use of too long of a password and a password with an @ in it. This is a bug with the oracle code, and not Fedora/Spacewalk related, IMHO. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From noriko at redhat.com Tue Jul 28 04:31:27 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Tue, 28 Jul 2009 14:31:27 +1000 Subject: Release Notes Schedule In-Reply-To: References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> Message-ID: <4A6E7F1F.4010908@redhat.com> > Updated strawman at > http://jjmcd.fedorapeople.org/F12RN4a.html > > I believe this is consistent with > http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-tasks.html > as far as major milestones go, but f-12-docs-tasks does have a number > of issues which this is intended to correct. Again, please go through > this, see whether it makes sense. I left the reviews in there, but by > eliminating them we could give L10N a little more time, at the > possible cost of having more updates later. > > This schedule does anticipate that the bulk of the release notes > effort will be completed for beta, and the general availability > release notes will simply be updates to reflect issues uncovered > during beta. It remains to be seen how disciplined we can be about > "feature complete". Hello, I am noriko from FLP. Thank you for offering us to review rel-note schedule. I've gone through translation related entries. * 4.7 Translate f-r-n for beta Sep 6 to Sep 26 21d This seems not consistent with f-12-trans-tasks, which says Sep 9 to Sep 18. * 4.8 Build f-r-n.rpm for beta Sep 29 A question, there is 2 days blank between 4.7 and 4.8. What is this for? * 6.7 Translate f-r-n for GA Oct 20 to Oct 26 7d This seems not consistent with f-12-trans-tasks, which says Oct 9 to Oct 16. * Review translation not scheduled Please set up 'Review translation'. Since we translate PO file, so it is extremely helpful if docs team can build html for review before the deadline. * 7.4 Translate 0-day I understand that docs team has little window for Zero Day Update. But let me become devil this time as experiment. Is any chance that rel-note team can place this entry before GA Public Availability 3-Nov for inclusion? Just tiny window is fine. I can not guarantee at all how many translators can respond. That is all from me. noriko From mel at redhat.com Tue Jul 28 04:46:58 2009 From: mel at redhat.com (Mel Chua) Date: Tue, 28 Jul 2009 00:46:58 -0400 Subject: Almost-finalized: Marketing F12 schedule Message-ID: <4A6E82C2.1070402@redhat.com> I've updated the F12 schedule according to the meeting (https://www.redhat.com/archives/fedora-marketing-list/2009-July/msg00140.html) that Paul, John, and myself had today. https://fedoraproject.org/wiki/Marketing_F12_schedule We've got some dates and such to coordinate with various teams (cc'd here) before Monday in order to make sure our calendars sync up. One of the things we'll be talking about at the Marketing meeting tomorrow (https://fedoraproject.org/wiki/Marketing_meetings) is how to make sure that each Marketing + OtherTeam coordination happens this week - some of these connections already have delegates, others have people who probably should be, others are wide open. The notes below are very, *very* much drafts, and only starting points! It's also entirely possible that I've put *too* much in the notes below (that figuring out something shouldn't be Marketing's job, or its focus). Patches welcome. --Mel ---- Design: We should make sure we get you a release slogan in time, and give fast enough feedback/final-slogan turnaround based on your designs that you can make release buttons/banners with time to spare. Also need to see what sort of work we need to coordinate in order to make spiffy Ambassadors kits. Docs: We should commit to those 1-page shiny release notes you wanted, and find other good points during the cycle to check in with each other. We also need to talk (possibly with News) on who'd like to do what portions of talking points and in-depth feature profiles. (How can we market our documentation as awesome, too?) Ambassadors: We need to schedule a briefing for you folks to happen once the talking points are ready - but most importantly, we need to learn how we can listen to you better so that we can make the things you actually want and *need* to spread the word on the ground. What can we do? Websites: We should talk - potentially with Design - about how we're going to coordinate various webpage redesigns and revisions, and how our respective roles complement each other. News: We also need to talk (possibly with Docs) on who'd like to do what portions of talking points and in-depth feature profiles. We should also figure out what's going on with News and Marketing and Fedora Insight, so we can schedule in coordination times with other teams if needed. From noriko at redhat.com Tue Jul 28 05:09:47 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Tue, 28 Jul 2009 15:09:47 +1000 Subject: Almost-finalized: Marketing F12 schedule In-Reply-To: <4A6E82C2.1070402@redhat.com> References: <4A6E82C2.1070402@redhat.com> Message-ID: <4A6E881B.4090000@redhat.com> Mel Chua ????????: > I've updated the F12 schedule according to the meeting > (https://www.redhat.com/archives/fedora-marketing-list/2009-July/msg00140.html) > that Paul, John, and myself had today. > > https://fedoraproject.org/wiki/Marketing_F12_schedule > > We've got some dates and such to coordinate with various teams (cc'd > here) before Monday in order to make sure our calendars sync up. One > of the things we'll be talking about at the Marketing meeting tomorrow > (https://fedoraproject.org/wiki/Marketing_meetings) is how to make > sure that each Marketing + OtherTeam coordination happens this week - > some of these connections already have delegates, others have people > who probably should be, others are wide open. > > The notes below are very, *very* much drafts, and only starting > points! It's also entirely possible that I've put *too* much in the > notes below (that figuring out something shouldn't be Marketing's job, > or its focus). Patches welcome. > > --Mel > > ---- > > Design: We should make sure we get you a release slogan in time, and > give fast enough feedback/final-slogan turnaround based on your > designs that you can make release buttons/banners with time to spare. > Also need to see what sort of work we need to coordinate in order to > make spiffy Ambassadors kits. > > Docs: We should commit to those 1-page shiny release notes you wanted, > and find other good points during the cycle to check in with each > other. We also need to talk (possibly with News) on who'd like to do > what portions of talking points and in-depth feature profiles. (How > can we market our documentation as awesome, too?) > > Ambassadors: We need to schedule a briefing for you folks to happen > once the talking points are ready - but most importantly, we need to > learn how we can listen to you better so that we can make the things > you actually want and *need* to spread the word on the ground. What > can we do? > > Websites: We should talk - potentially with Design - about how we're > going to coordinate various webpage redesigns and revisions, and how > our respective roles complement each other. > > News: We also need to talk (possibly with Docs) on who'd like to do > what portions of talking points and in-depth feature profiles. We > should also figure out what's going on with News and Marketing and > Fedora Insight, so we can schedule in coordination times with other > teams if needed. > Hello, It might be stupid question, sorry, what is this for? Where is 'Localization'? noriko From cpanceac at gmail.com Tue Jul 28 06:12:00 2009 From: cpanceac at gmail.com (cornel panceac) Date: Tue, 28 Jul 2009 09:12:00 +0300 Subject: Project Start: New Updated Deployment Guide for the Upcoming Fedora 12! In-Reply-To: <4A6E4E7D.7050503@redhat.com> References: <4A6DF57D.30102@redhat.com> <4A6E4E7D.7050503@redhat.com> Message-ID: 2009/7/28 Christopher Curran > cornel panceac wrote: > >> >> >> 2009/7/27 cornel panceac > >> >> >> 2009/7/27 Douglas Silas Hensley > > >> >> Greetings Fedora users and system administrators, >> >> I meant to announce this last week on fedora-docs-list, but >> the CC slipped my mind. Here's copy of the announcement I sent >> to deployment-guide-list at redhat.com >> . See the Deployment >> >> Guide wiki: >> >> https://fedorahosted.org/deploymentguide/wiki >> >> ...for details on joining this list. All are welcome. >> >> ORIGINAL ANNOUNCEMENT >> I'm proud to announce that I'll be heading a new project to >> update a new guide, the Fedora Deployment Guide, for the >> upcoming Fedora 12 release! The Fedora Deployment Guide covers >> system administration tasks such as package maintenance, user >> administration, printing, and setting up networks, printers, >> and services such as Apache, LDAP, OpenSSH, Samba, etc. >> >> You can see what's in it and the most current state of the >> upcoming Fedora 12 Deployment Guide here: >> >> http://dsilas.fedorapeople.org/Deployment_Guide/en-US/ >> >> The target for completion of this project is before Nov. 1, >> ahead of the GA target date for Fedora 12, which is currently >> Nov. 3. >> >> The project page for the Deployment Guide, which also tells >> you where to obtain the source files (which are in DocBook >> XML), is here: >> >> https://fedorahosted.org/deploymentguide/wiki >> >> We will definitely be accepting contributors; please contact >> me if you are able to help out. There is a Deployment Guide >> mailing list. To gain access to it, please send an email to >> the project maintainers (of whom I am one) with a brief >> introduction: >> >> https://www.redhat.com/mailman/listinfo/deployment-guide-list >> >> The Fedora Deployment Guide is written in DocBook XML and is >> published using the open source Publican build tool: >> >> https://fedorahosted.org/publican/ >> >> More details will follow next week (such as additions to the TOC). >> >> I hope to hear suggestions and opinions from you! >> >> >> >> Cheers, >> -- Douglas Silas >> Technical Writer | Red Hat, Inc. >> Purkyn(ova 99 | Brno, Czech Republic >> Office Direct Dial?62116 >> Brno Office?(+420) 532 294 111 ext. 10718 >> dhensley at redhat.com >> >> -- fedora-docs-list mailing list >> fedora-docs-list at redhat.com >> To unsubscribe: >> https://www.redhat.com/mailman/listinfo/fedora-docs-list >> >> >> can rhn manage fedora systems? >> >> >> the screenshots are from rhel, not fedora. >> and there's no up2date in fedora 12, afaict. >> > > Bug fixes welcome. This is the idea behind developing documentation, it > isn't perfect originally so it needs some work. You are more than welcome to > help fix these issues. > > Chris > > thank you. what's the next step? > > > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list > -- Linux counter #213090 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wb8rcr at arrl.net Tue Jul 28 11:37:25 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Tue, 28 Jul 2009 07:37:25 -0400 Subject: Release Notes Schedule References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> Message-ID: <2C066D82202C4DC3B34889B3A394772E@Aidan> Noriko Thank you so much for your careful review ----- Original Message ----- From: "Noriko Mizumoto" To: "Fedora Translation Project List" Cc: Sent: Tuesday, July 28, 2009 12:31 AM Subject: Re: Release Notes Schedule > * 4.7 Translate f-r-n for beta Sep 6 to Sep 26 21d > This seems not consistent with f-12-trans-tasks, which says Sep 9 to Sep > 18. While I stuck with John's dates for the releases, I tried to maximize the time L10N had available. I wonder whether 9 days is sufficient. I would expect this cycle that the beta would be the bulk of the release notes (although I suppose that remains to be seen). > * 4.8 Build f-r-n.rpm for beta Sep 29 > A question, there is 2 days blank between 4.7 and 4.8. What is this for? No good reason > * 6.7 Translate f-r-n for GA Oct 20 to Oct 26 7d > This seems not consistent with f-12-trans-tasks, which says Oct 9 to Oct > 16. The later we can do this the better. Release notes seem to be the last thing on people's radar, and we tend to discover important changes late, so the later we can make the POTs the better. Also, the original schedule had some Docs tasks out of order. > * Review translation not scheduled > Please set up 'Review translation'. Since we translate PO file, so it is > extremely helpful if docs team can build html for review before the > deadline. That is a really excellent catch. I think we need to work on the mechanics of this, but it could have a number of advantages. > * 7.4 Translate 0-day > I understand that docs team has little window for Zero Day Update. But let > me become devil this time as experiment. Is any chance that rel-note team > can place this entry before GA Public Availability 3-Nov for inclusion? > Just tiny window is fine. I can not guarantee at all how many translators > can respond. My expectation was that on release day the 0-day changes would be available in English only, with an update rpm to follow the release. However, we are still discussing whether it makes sense to have a single rpm with six documents in 41 languages, so that may change. It might make more sense to delay the availability of the update rpm rather than try to push the POT creation earlier, thus missing late breaking changes. On the other end, we are going to try to be more proactive in hounding the developers for release notes input, so maybe we can reduce the number of those late changes. --McD From ian at ianweller.org Tue Jul 28 15:13:15 2009 From: ian at ianweller.org (Ian Weller) Date: Tue, 28 Jul 2009 10:13:15 -0500 Subject: python-mwlib, again Message-ID: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> This task has landed on my plate again. Does anybody have anything I can run a test with to make sure that the RPM in Fedora is updated and works? I need some content and some commands. :) -- Ian Weller "Why, a four-year-old could understand this report. Find me a four-year-old child. I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From herlo1 at gmail.com Tue Jul 28 15:31:45 2009 From: herlo1 at gmail.com (Clint Savage) Date: Tue, 28 Jul 2009 09:31:45 -0600 Subject: python-mwlib, again In-Reply-To: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> References: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> Message-ID: Ian, I need to set up a new mw instance somewhere in test for mediawiki-rss. Maybe we can coordinate to have a test instance of mw somewhere? Clint On Tue, Jul 28, 2009 at 9:13 AM, Ian Weller wrote: > This task has landed on my plate again. Does anybody have anything I can > run a test with to make sure that the RPM in Fedora is updated and > works? I need some content and some commands. :) > > -- > Ian Weller > ?"Why, a four-year-old could understand this report. > ? Find me a four-year-old child. > ? I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" > > -- > fedora-docs-list mailing list > fedora-docs-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-docs-list > From bugzilla at redhat.com Tue Jul 28 18:46:31 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 28 Jul 2009 14:46:31 -0400 Subject: [Bug 504066] CMS for docs.fp.org In-Reply-To: References: Message-ID: <200907281846.n6SIkVmm026821@bz-web2.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=504066 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |514301 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From ian at ianweller.org Tue Jul 28 19:07:15 2009 From: ian at ianweller.org (Ian Weller) Date: Tue, 28 Jul 2009 14:07:15 -0500 Subject: python-mwlib, again In-Reply-To: References: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> Message-ID: <20090728190704.GA2923@hovercraft.mobile.ianweller.org> On Tue, Jul 28, 2009 at 09:31:45AM -0600, Clint Savage wrote: > I need to set up a new mw instance somewhere in test for > mediawiki-rss. Maybe we can coordinate to have a test instance of mw > somewhere? > I don't really need a full test instance of MediaWiki, I just need some content to play with that is previously known to work. -- Ian Weller "Why, a four-year-old could understand this report. Find me a four-year-old child. I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From herlo1 at gmail.com Tue Jul 28 19:50:22 2009 From: herlo1 at gmail.com (Clint Savage) Date: Tue, 28 Jul 2009 13:50:22 -0600 Subject: python-mwlib, again In-Reply-To: <20090728190704.GA2923@hovercraft.mobile.ianweller.org> References: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> <20090728190704.GA2923@hovercraft.mobile.ianweller.org> Message-ID: On Tue, Jul 28, 2009 at 1:07 PM, Ian Weller wrote: > On Tue, Jul 28, 2009 at 09:31:45AM -0600, Clint Savage wrote: >> I need to set up a new mw instance somewhere in test for >> mediawiki-rss. ?Maybe we can coordinate to have a test instance of mw >> somewhere? >> > I don't really need a full test instance of MediaWiki, I just need some > content to play with that is previously known to work. > Okay, well I do need a mediawiki test instance, that's what I am saying. If you don't want to go that route, that's fine too. I just figured it would be easier to give you what you need. Clint From stickster at gmail.com Tue Jul 28 21:32:06 2009 From: stickster at gmail.com (Paul W. Frields) Date: Tue, 28 Jul 2009 17:32:06 -0400 Subject: python-mwlib, again In-Reply-To: <20090728190704.GA2923@hovercraft.mobile.ianweller.org> References: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> <20090728190704.GA2923@hovercraft.mobile.ianweller.org> Message-ID: <20090728213206.GJ517@localhost.localdomain> On Tue, Jul 28, 2009 at 02:07:15PM -0500, Ian Weller wrote: > On Tue, Jul 28, 2009 at 09:31:45AM -0600, Clint Savage wrote: > > I need to set up a new mw instance somewhere in test for > > mediawiki-rss. Maybe we can coordinate to have a test instance of mw > > somewhere? > > > I don't really need a full test instance of MediaWiki, I just need some > content to play with that is previously known to work. Only problem with that approach: How do we go back in time to ensure that something worked before? Here's what I would suggest you do: 1. Establish the dates when John J. McDonough did a previous import of release notes beats from the wiki into the git release-notes repository, using the change history there. 2. Get the wiki page content from the appropriate revision of one or more of the imported pages. You should be able to use those to validate. It would probably also be a good idea to set up a semi-permanent page for testing, watching for regressions, etc. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug From poelstra at redhat.com Tue Jul 28 22:26:27 2009 From: poelstra at redhat.com (John Poelstra) Date: Tue, 28 Jul 2009 15:26:27 -0700 Subject: Release Notes Schedule In-Reply-To: <2C066D82202C4DC3B34889B3A394772E@Aidan> References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan> Message-ID: <4A6F7B13.9000105@redhat.com> John J. McDonough said the following on 07/28/2009 04:37 AM Pacific Time: > Noriko > > Thank you so much for your careful review > > ----- Original Message ----- From: "Noriko Mizumoto" > To: "Fedora Translation Project List" > Cc: > Sent: Tuesday, July 28, 2009 12:31 AM > Subject: Re: Release Notes Schedule > >> * 4.7 Translate f-r-n for beta Sep 6 to Sep 26 21d >> This seems not consistent with f-12-trans-tasks, which says Sep 9 to >> Sep 18. > > While I stuck with John's dates for the releases, I tried to maximize > the time L10N had available. I wonder whether 9 days is sufficient. I > would expect this cycle that the beta would be the bulk of the release > notes (although I suppose that remains to be seen). > >> * 4.8 Build f-r-n.rpm for beta Sep 29 >> A question, there is 2 days blank between 4.7 and 4.8. What is this for? > > No good reason > >> * 6.7 Translate f-r-n for GA Oct 20 to Oct 26 7d >> This seems not consistent with f-12-trans-tasks, which says Oct 9 to >> Oct 16. > > The later we can do this the better. Release notes seem to be the last > thing on people's radar, and we tend to discover important changes late, > so the later we can make the POTs the better. Also, the original > schedule had some Docs tasks out of order. > >> * Review translation not scheduled >> Please set up 'Review translation'. Since we translate PO file, so it >> is extremely helpful if docs team can build html for review before the >> deadline. > > That is a really excellent catch. I think we need to work on the > mechanics of this, but it could have a number of advantages. > >> * 7.4 Translate 0-day >> I understand that docs team has little window for Zero Day Update. But >> let me become devil this time as experiment. Is any chance that >> rel-note team can place this entry before GA Public Availability 3-Nov >> for inclusion? Just tiny window is fine. I can not guarantee at all >> how many translators can respond. > > My expectation was that on release day the 0-day changes would be > available in English only, with an update rpm to follow the release. > However, we are still discussing whether it makes sense to have a single > rpm with six documents in 41 languages, so that may change. It might > make more sense to delay the availability of the update rpm rather than > try to push the POT creation earlier, thus missing late breaking > changes. On the other end, we are going to try to be more proactive in > hounding the developers for release notes input, so maybe we can reduce > the number of those late changes. > > --McD > This is a great discussion and it is really exciting to see different people asking the hard questions and looking for the holes that I used to try and do all on my own :) Unfortunately I've found that it is extremely hard (as you may be seeing already) to create a really solid schedule over email, particularly when more than one team is involved and questions have been raised in response to tasks or dates someone has previously suggested. I would like to propose that we meet on Gobby & FedoraTalk next. So far I have met with: Design, Release Engineering, Quality, and Marketing to go over the Fedora 12 schedule this way. I think everyone who attended those meetings would say they were tremendously efficient and helpful :-) Could someone set up a meeting time and date using www.whenisgood.net? I promise to add my availability and create a text version of the existing schedule that we can then hack through and update together on Gobby. It helps if I am there so I can capture the dependencies between the tasks and embed them in the TaskJuggler source file. Thanks, John From bruno at wolff.to Tue Jul 28 23:27:47 2009 From: bruno at wolff.to (Bruno Wolff III) Date: Tue, 28 Jul 2009 18:27:47 -0500 Subject: Release Notes Schedule In-Reply-To: <4A6F7B13.9000105@redhat.com> References: <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan> <4A6F7B13.9000105@redhat.com> Message-ID: <20090728232747.GC10861@wolff.to> On Tue, Jul 28, 2009 at 15:26:27 -0700, John Poelstra wrote: > > Unfortunately I've found that it is extremely hard (as you may be seeing > already) to create a really solid schedule over email, particularly when > more than one team is involved and questions have been raised in > response to tasks or dates someone has previously suggested. It may be kind of late to consider this, but maybe it would help to use taskjuggler to look at the timing for the release process. If it does work, you'd be able to mostly reuse the projects from release to release. I think it would also make it easier for groups to give feedback on their pieces while allowing the new information to be easily used for the whole project. From ian at ianweller.org Tue Jul 28 23:27:19 2009 From: ian at ianweller.org (Ian Weller) Date: Tue, 28 Jul 2009 18:27:19 -0500 Subject: python-mwlib, again In-Reply-To: <20090728213206.GJ517@localhost.localdomain> References: <20090728151315.GA3456@hovercraft.mobile.ianweller.org> <20090728190704.GA2923@hovercraft.mobile.ianweller.org> <20090728213206.GJ517@localhost.localdomain> Message-ID: <20090728232719.GA7018@hovercraft.mobile.ianweller.org> On Tue, Jul 28, 2009 at 05:32:06PM -0400, Paul W. Frields wrote: > 1. Establish the dates when John J. McDonough did a previous import of > release notes beats from the wiki into the git release-notes > repository, using the change history there. > > 2. Get the wiki page content from the appropriate revision of one or > more of the imported pages. > > You should be able to use those to validate. It would probably also > be a good idea to set up a semi-permanent page for testing, watching > for regressions, etc. > Can somebody get me the relevant page names and the date at which to check them? -- Ian Weller "Why, a four-year-old could understand this report. Find me a four-year-old child. I can't make head or tail out of it." -- Groucho Marx, "Duck Soup" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From poelstra at redhat.com Tue Jul 28 23:51:37 2009 From: poelstra at redhat.com (John Poelstra) Date: Tue, 28 Jul 2009 16:51:37 -0700 Subject: Release Notes Schedule In-Reply-To: <20090728232747.GC10861@wolff.to> References: <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan> <4A6F7B13.9000105@redhat.com> <20090728232747.GC10861@wolff.to> Message-ID: <4A6F8F09.4050607@redhat.com> Bruno Wolff III said the following on 07/28/2009 04:27 PM Pacific Time: > On Tue, Jul 28, 2009 at 15:26:27 -0700, > John Poelstra wrote: >> Unfortunately I've found that it is extremely hard (as you may be seeing >> already) to create a really solid schedule over email, particularly when >> more than one team is involved and questions have been raised in >> response to tasks or dates someone has previously suggested. > > It may be kind of late to consider this, but maybe it would help to use > taskjuggler to look at the timing for the release process. If it does work, > you'd be able to mostly reuse the projects from release to release. I think > it would also make it easier for groups to give feedback on their pieces > while allowing the new information to be easily used for the whole project. I've already been doing this for several releases :-) If you look at the source file you'll see very few hard coded dates. http://poelstra.fedorapeople.org/schedules/f-12/source/f-12.tjp The problem I've had is getting teams to do a detailed review of the dates and cross-team dependencies. The other difficulty is that each release the task methodology changes as teams tweak their processes and attempt to learn from the previous release. Due to the different nature of each team's work, there is very little reuse of task structure between the teams. Each release we've made the schedules a little tighter a little better, but it's feeling like Fedora 12 could be the "break out" release for making substantial progress! Check out this directory if you'd like to explore more: http://poelstra.fedorapeople.org/schedules/f-12/source/ John From eric at christensenplace.us Wed Jul 29 01:25:44 2009 From: eric at christensenplace.us (Eric Christensen) Date: Tue, 28 Jul 2009 21:25:44 -0400 Subject: New Bugzilla Products Message-ID: <1248830744.10699.56.camel@thunder> Two new Bugzilla products have been created in the Fedora Documentation component: virtualization-guide installation-quick-start-guide Thanks, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From noriko at redhat.com Wed Jul 29 02:25:13 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Wed, 29 Jul 2009 12:25:13 +1000 Subject: Release Notes Schedule In-Reply-To: <2C066D82202C4DC3B34889B3A394772E@Aidan> References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan> Message-ID: <4A6FB309.7010602@redhat.com> John J. McDonough ????????: > Noriko > > Thank you so much for your careful review > > ----- Original Message ----- From: "Noriko Mizumoto" > To: "Fedora Translation Project List" > Cc: > Sent: Tuesday, July 28, 2009 12:31 AM > Subject: Re: Release Notes Schedule > >> * 4.7 Translate f-r-n for beta Sep 6 to Sep 26 21d >> This seems not consistent with f-12-trans-tasks, which says Sep 9 to >> Sep 18. > > While I stuck with John's dates for the releases, I tried to maximize > the time L10N had available. I wonder whether 9 days is sufficient. I > would expect this cycle that the beta would be the bulk of the release > notes (although I suppose that remains to be seen). You are so sweet! It is glad to know that it's not typo but it will be happening with 21d than 9d. Thank you! > >> * 4.8 Build f-r-n.rpm for beta Sep 29 >> A question, there is 2 days blank between 4.7 and 4.8. What is this for? > > No good reason > >> * 6.7 Translate f-r-n for GA Oct 20 to Oct 26 7d >> This seems not consistent with f-12-trans-tasks, which says Oct 9 to >> Oct 16. > > The later we can do this the better. Release notes seem to be the last > thing on people's radar, and we tend to discover important changes > late, so the later we can make the POTs the better. Also, the original > schedule had some Docs tasks out of order. Understood. > >> * Review translation not scheduled >> Please set up 'Review translation'. Since we translate PO file, so it >> is extremely helpful if docs team can build html for review before >> the deadline. > > That is a really excellent catch. I think we need to work on the > mechanics of this, but it could have a number of advantages. > >> * 7.4 Translate 0-day >> I understand that docs team has little window for Zero Day Update. >> But let me become devil this time as experiment. Is any chance that >> rel-note team can place this entry before GA Public Availability >> 3-Nov for inclusion? Just tiny window is fine. I can not guarantee at >> all how many translators can respond. > > My expectation was that on release day the 0-day changes would be > available in English only, with an update rpm to follow the release. > However, we are still discussing whether it makes sense to have a > single rpm with six documents in 41 languages, so that may change. It > might make more sense to delay the availability of the update rpm > rather than try to push the POT creation earlier, thus missing late > breaking changes. On the other end, we are going to try to be more > proactive in hounding the developers for release notes input, so maybe > we can reduce the number of those late changes. Understood the situation. Let's see how it goes. Thank you again. noriko From noriko at redhat.com Wed Jul 29 02:28:59 2009 From: noriko at redhat.com (Noriko Mizumoto) Date: Wed, 29 Jul 2009 12:28:59 +1000 Subject: Release Notes Schedule In-Reply-To: <4A6F7B13.9000105@redhat.com> References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan> <4A6F7B13.9000105@redhat.com> Message-ID: <4A6FB3EB.9050406@redhat.com> John Poelstra ????????: > John J. McDonough said the following on 07/28/2009 04:37 AM Pacific Time: >> Noriko >> >> Thank you so much for your careful review >> >> ----- Original Message ----- From: "Noriko Mizumoto" >> To: "Fedora Translation Project List" >> Cc: >> Sent: Tuesday, July 28, 2009 12:31 AM >> Subject: Re: Release Notes Schedule >> >>> * 4.7 Translate f-r-n for beta Sep 6 to Sep 26 21d >>> This seems not consistent with f-12-trans-tasks, which says Sep 9 to >>> Sep 18. >> >> While I stuck with John's dates for the releases, I tried to maximize >> the time L10N had available. I wonder whether 9 days is sufficient. I >> would expect this cycle that the beta would be the bulk of the >> release notes (although I suppose that remains to be seen). >> >>> * 4.8 Build f-r-n.rpm for beta Sep 29 >>> A question, there is 2 days blank between 4.7 and 4.8. What is this >>> for? >> >> No good reason >> >>> * 6.7 Translate f-r-n for GA Oct 20 to Oct 26 7d >>> This seems not consistent with f-12-trans-tasks, which says Oct 9 to >>> Oct 16. >> >> The later we can do this the better. Release notes seem to be the >> last thing on people's radar, and we tend to discover important >> changes late, so the later we can make the POTs the better. Also, the >> original schedule had some Docs tasks out of order. >> >>> * Review translation not scheduled >>> Please set up 'Review translation'. Since we translate PO file, so >>> it is extremely helpful if docs team can build html for review >>> before the deadline. >> >> That is a really excellent catch. I think we need to work on the >> mechanics of this, but it could have a number of advantages. >> >>> * 7.4 Translate 0-day >>> I understand that docs team has little window for Zero Day Update. >>> But let me become devil this time as experiment. Is any chance that >>> rel-note team can place this entry before GA Public Availability >>> 3-Nov for inclusion? Just tiny window is fine. I can not guarantee >>> at all how many translators can respond. >> >> My expectation was that on release day the 0-day changes would be >> available in English only, with an update rpm to follow the release. >> However, we are still discussing whether it makes sense to have a >> single rpm with six documents in 41 languages, so that may change. It >> might make more sense to delay the availability of the update rpm >> rather than try to push the POT creation earlier, thus missing late >> breaking changes. On the other end, we are going to try to be more >> proactive in hounding the developers for release notes input, so >> maybe we can reduce the number of those late changes. >> >> --McD >> > > This is a great discussion and it is really exciting to see different > people asking the hard questions and looking for the holes that I used > to try and do all on my own :) > > Unfortunately I've found that it is extremely hard (as you may be > seeing already) to create a really solid schedule over email, > particularly when more than one team is involved and questions have > been raised in response to tasks or dates someone has previously > suggested. > > I would like to propose that we meet on Gobby & FedoraTalk next. So > far I have met with: Design, Release Engineering, Quality, and > Marketing to go over the Fedora 12 schedule this way. I think everyone > who attended those meetings would say they were tremendously efficient > and helpful :-) I am not good at those at all, but will try. Btw, irc is better option for me ;p noriko > > Could someone set up a meeting time and date using www.whenisgood.net? > I promise to add my availability and create a text version of the > existing schedule that we can then hack through and update together on > Gobby. It helps if I am there so I can capture the dependencies > between the tasks and embed them in the TaskJuggler source file. > > Thanks, > John > From ccurran at redhat.com Wed Jul 29 06:27:55 2009 From: ccurran at redhat.com (Christopher Curran) Date: Wed, 29 Jul 2009 16:27:55 +1000 Subject: New Bugzilla Products In-Reply-To: <1248830744.10699.56.camel@thunder> References: <1248830744.10699.56.camel@thunder> Message-ID: <4A6FEBEB.2030807@redhat.com> Eric Christensen wrote: > Two new Bugzilla products have been created in the Fedora Documentation > component: > > virtualization-guide > installation-quick-start-guide > > Thanks, > Eric > Rock on! -- Chris Curran Content Author II Phone: +61735148302 (UTC+10) 193 North Quay, Brisbane, Australia. Red Hat, Inc. From ankit at redhat.com Wed Jul 29 09:05:02 2009 From: ankit at redhat.com (Ankitkumar Rameshchandra Patel) Date: Wed, 29 Jul 2009 14:35:02 +0530 Subject: New Bugzilla Products In-Reply-To: <4A6FEBEB.2030807@redhat.com> References: <1248830744.10699.56.camel@thunder> <4A6FEBEB.2030807@redhat.com> Message-ID: <4A7010BE.9060206@redhat.com> Christopher Curran wrote: > Eric Christensen wrote: >> Two new Bugzilla products have been created in the Fedora Documentation >> component: >> >> virtualization-guide >> installation-quick-start-guide >> >> Thanks, >> Eric >> > Rock on! > Where can we find these two docs on fedoraproject.org? Btw, what's the difference between install-guide and installation-quick-start-guide? -- Regards, Ankit Patel http://www.indianoss.org/ http://www.ankit644.com/ From eric at christensenplace.us Wed Jul 29 12:14:10 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 29 Jul 2009 08:14:10 -0400 Subject: New Bugzilla Products In-Reply-To: <4A7010BE.9060206@redhat.com> References: <1248830744.10699.56.camel@thunder> <4A6FEBEB.2030807@redhat.com> <4A7010BE.9060206@redhat.com> Message-ID: <1248869650.2662.1.camel@thunder> On Wed, 2009-07-29 at 14:35 +0530, Ankitkumar Rameshchandra Patel wrote: > Christopher Curran wrote: > > Eric Christensen wrote: > >> Two new Bugzilla products have been created in the Fedora Documentation > >> component: > >> > >> virtualization-guide > >> installation-quick-start-guide > >> > >> Thanks, > >> Eric > >> > > Rock on! > > > > Where can we find these two docs on fedoraproject.org? > > Btw, what's the difference between install-guide and > installation-quick-start-guide? > > -- > Regards, > Ankit Patel > http://www.indianoss.org/ > http://www.ankit644.com/ > These two docs are in development now so they aren't available just yet. When they are you can find them at docs.fedoraproject.org. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From r.landmann at redhat.com Wed Jul 29 12:24:06 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Wed, 29 Jul 2009 22:24:06 +1000 Subject: New Bugzilla Products In-Reply-To: <4A7010BE.9060206@redhat.com> References: <1248830744.10699.56.camel@thunder> <4A6FEBEB.2030807@redhat.com> <4A7010BE.9060206@redhat.com> Message-ID: <4A703F66.7000807@redhat.com> On 07/29/2009 07:05 PM, Ankitkumar Rameshchandra Patel wrote: > Where can we find these two docs on fedoraproject.org? Neither is published on fedoraprojects.org just yet, although you can find a draft of the Installation Quick Start Guide here: http://rlandmann.fedorapeople.org/IQSG/en-US/html-single/ I hope to upload a copy to d.fp.o shortly. > Btw, what's the difference between install-guide and > installation-quick-start-guide? > About 240 pages in the PDF versions :) The Installation Guide documents the entire installation process in detail, with all of its many options. It also includes extensive technical background to help readers understand the choices that they might have to make at various stages of the process. The Installation Quick Start Guide covers the "path of least resistance" for a typical user ? downloading a live image, burning it to CD, and installing it on a typical desktop or notebook by pretty much using the default options all the way. This book is really just a condensed version of the Installation Guide, built largely from XML borrowed from the larger book (in order to lighten the load on localisation and general maintenance). Cheers Rudi From eric at christensenplace.us Wed Jul 29 21:59:47 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 29 Jul 2009 17:59:47 -0400 Subject: Fedora Docs Meeting Reminder Message-ID: <1248904787.2617.13.camel@thunder> REMINDER: There will be a Fedora Docs Meeting today at 0001 UTC. The agenda can be found at: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting If you have any additions to the agenda, please do them prior to 2330 UTC. Thanks, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From wb8rcr at arrl.net Wed Jul 29 23:56:44 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Wed, 29 Jul 2009 19:56:44 -0400 Subject: Release Notes Schedule References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan><4A6F7B13.9000105@redhat.com> <4A6FB3EB.9050406@redhat.com> Message-ID: <9B25474BCF0D4CDC854AEC0E79CDB862@Aidan> ----- Original Message ----- From: "Noriko Mizumoto" To: "For participants of the Documentation Project" Cc: "Fedora Translation Project List" Sent: Tuesday, July 28, 2009 10:28 PM Subject: Re: Release Notes Schedule John Poelstra ????????: > John J. McDonough said the following on 07/28/2009 04:37 AM Pacific Time: >> Noriko >> >> Thank you so much for your careful review >> >> ----- Original Message ----- From: "Noriko Mizumoto" >> To: "Fedora Translation Project List" >> Cc: >> Sent: Tuesday, July 28, 2009 12:31 AM >> Subject: Re: Release Notes Schedule >> >>> * 4.7 Translate f-r-n for beta Sep 6 to Sep 26 21d >>> This seems not consistent with f-12-trans-tasks, which says Sep 9 to Sep >>> 18. >> >> While I stuck with John's dates for the releases, I tried to maximize the >> time L10N had available. I wonder whether 9 days is sufficient. I would >> expect this cycle that the beta would be the bulk of the release notes >> (although I suppose that remains to be seen). >> >>> * 4.8 Build f-r-n.rpm for beta Sep 29 >>> A question, there is 2 days blank between 4.7 and 4.8. What is this for? >> >> No good reason >> >>> * 6.7 Translate f-r-n for GA Oct 20 to Oct 26 7d >>> This seems not consistent with f-12-trans-tasks, which says Oct 9 to Oct >>> 16. >> >> The later we can do this the better. Release notes seem to be the last >> thing on people's radar, and we tend to discover important changes late, >> so the later we can make the POTs the better. Also, the original schedule >> had some Docs tasks out of order. >> >>> * Review translation not scheduled >>> Please set up 'Review translation'. Since we translate PO file, so it is >>> extremely helpful if docs team can build html for review before the >>> deadline. >> >> That is a really excellent catch. I think we need to work on the >> mechanics of this, but it could have a number of advantages. >> >>> * 7.4 Translate 0-day >>> I understand that docs team has little window for Zero Day Update. But >>> let me become devil this time as experiment. Is any chance that rel-note >>> team can place this entry before GA Public Availability 3-Nov for >>> inclusion? Just tiny window is fine. I can not guarantee at all how many >>> translators can respond. >> >> My expectation was that on release day the 0-day changes would be >> available in English only, with an update rpm to follow the release. >> However, we are still discussing whether it makes sense to have a single >> rpm with six documents in 41 languages, so that may change. It might make >> more sense to delay the availability of the update rpm rather than try to >> push the POT creation earlier, thus missing late breaking changes. On the >> other end, we are going to try to be more proactive in hounding the >> developers for release notes input, so maybe we can reduce the number of >> those late changes. >> >> --McD >> > > This is a great discussion and it is really exciting to see different > people asking the hard questions and looking for the holes that I used to > try and do all on my own :) > > Unfortunately I've found that it is extremely hard (as you may be seeing > already) to create a really solid schedule over email, particularly when > more than one team is involved and questions have been raised in response > to tasks or dates someone has previously suggested. > > I would like to propose that we meet on Gobby & FedoraTalk next. So far I > have met with: Design, Release Engineering, Quality, and Marketing to go > over the Fedora 12 schedule this way. I think everyone who attended those > meetings would say they were tremendously efficient and helpful :-) I am not good at those at all, but will try. Btw, irc is better option for me ;p noriko > > Could someone set up a meeting time and date using www.whenisgood.net? I > promise to add my availability and create a text version of the existing > schedule that we can then hack through and update together on Gobby. It > helps if I am there so I can capture the dependencies between the tasks > and embed them in the TaskJuggler source file. > > Thanks, > John I think John has the right idea here, but I'm not sure I know who all the players need to be. --McD From bugzilla at redhat.com Thu Jul 30 00:38:30 2009 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Wed, 29 Jul 2009 20:38:30 -0400 Subject: [Bug 450331] lack of documentation on restoring from bare-metal (UUID problem) In-Reply-To: References: Message-ID: <200907300038.n6U0cUu7005663@bz-web1.app.phx.redhat.com> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=450331 Eric Christensen changed: What |Removed |Added ---------------------------------------------------------------------------- Component|desktop-user-guide |user-guide --- Comment #6 from Eric Christensen 2009-07-29 20:38:29 EDT --- Changed from desktop-user-guide to user-guide to help reduce confusion. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. From eric at christensenplace.us Thu Jul 30 00:58:44 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 29 Jul 2009 20:58:44 -0400 Subject: Docs Meeting 2009-07-30 IRC log Message-ID: <1248915524.2617.19.camel@thunder> 00:01:59 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:02:02 * ianweller 00:02:09 * rudi is here 00:02:10 #topic Roll Call 00:02:12 * Sparks 00:02:18 * jjmcd is here 00:02:24 * rudi jumped the gun earlier but is here 00:02:55 * ianweller doesn't care that he jumped the gun :) 00:03:03 * stickster 1/2 here 00:03:03 * radsy is here 00:03:07 ianweller: As long as you're here 00:03:19 stickster: which half? 00:03:45 I don't know, it's via gerrymandering 00:05:37 Okay, let's get started. 00:05:43 #topic Last week's action items 00:05:54 Sparks to follow up with the News people about Zikula 00:06:20 Okay, so I sent an email out to the News folks but I didn't really get a response back. I'll see if I can catch someone over there. 00:06:29 stickster: Is Max the lead there? 00:06:50 Sparks: Pascal Calarco is the person who agreed to help, I believe 00:07:56 #ACTION Sparks to follow up with Pascal Calarco from News to make sure we are including all packages necessary for Zikula for them. 00:08:10 Sparks to write rollout plan for license change 00:08:23 Hmmm... Yeah, didn't get to this one. 00:08:36 That's something we could use, fer sher 00:08:49 #action Sparks to write rollout plan for license change... 2nd alarm 00:08:54 * stickster will try to write a blog entry in the next day or two to try and drum up some PHP/JS help 00:09:02 ianweller to write press release 00:09:13 ianweller: I'm guessing you're waiting for my plan, right? 00:09:18 yeah a little bit. 00:09:21 Okay 00:09:28 rudi to help sparks on changing the fedora-brand in Publican for CC license 00:09:40 rudi: You going to be busy on Monday? 00:09:52 Sparks - I'll be available :) 00:10:08 rudi: Okay, I'll get with you after the meeting and setup some time with you. Thanks. 00:10:14 #action rudi to help sparks on changing the fedora-brand in Publican for CC license 00:10:14 NP 00:10:41 Sparks to create BZ component for Installation Quick Start Guide 00:10:43 done 00:10:51 Sparks to create a BZ component for Virtualization Guide 00:10:51 done 00:11:00 Sparks to send out reminder about the RN meeting 00:11:01 done 00:11:15 jjmcd: Do we need to meet again this week? I don't think we got throught everything last week 00:11:25 I think we do 00:11:32 Same bat time? 00:11:34 we hit one of I think 4 major topics 00:11:44 I kept it on my calendar just in case 00:11:57 When is it? Tomorrow at ??? 00:12:16 * rudi stocked up on Coke and Doritos :) 00:12:22 11E 00:12:35 So 1500 UTC 00:12:35 so 1500Z maybe 00:12:38 Okay. 00:13:00 Anyone have anything else from last week? 00:13:30 #topic Status on CMS (Zikula) <-- ke4qqq 00:13:42 #link https://fedoraproject.org/wiki/Zikula#Module_status 00:13:56 Okay, I don't think ke4qqq is here tonight... 00:14:02 so I'll just give a quick update. 00:14:29 The webpage listed above is a status page of all the Zikula modules that need to be packaged... 00:14:37 and what their hangups are. 00:14:47 * stickster may need to update his 00:14:58 We still have quite a few that are broken due to licensing issues. 00:15:31 * stickster just updated his entries on that list 00:16:04 I've been pushing my packages to F-10, F-11, F-12, and EL-5. F-10 is optional, I guess, but everyone that is packaging needs to push to EL-5 as well. 00:16:15 Yup, took care of mine yesterday and today 00:16:25 stickster: Is there anything else>? 00:16:42 One thing we're going to need to make a call on soon is changing "upstream to resolve" to "$FEDORA_PERSON to resolve" 00:17:11 Blocking on licensing is bad, and I think upstream's going to need our help here, something more than asking them to do it 00:17:33 I agree. 00:18:33 I'm going to just go through the three GPL-licensed editors and package them all. That way we have choices 00:18:59 Makes sense to me 00:19:10 * stickster knows tinymce by name 00:19:24 OK, moving on 00:19:39 #action? 00:19:50 stickster: Do you have time to go through the three packages that are license blocked and explain what exactly is blocking (icons, etc)? 00:20:09 #action Sparks to package the three GPL editors for Zikula 00:20:14 I think they're all explained in their respective bugs 00:20:17 but... 00:20:37 I know off the top of my head that Mediashare is blocked on LIghtboxXL 00:20:43 Which is a CC 2.5 licensed JS 00:21:06 And that same JS appears in at least one other module, I think it's Mediaattach 00:21:35 Content 00:21:56 MediaAttach says "multiple licensing issues". 00:22:08 Sorry, Content -- right. 00:22:18 What does it mean for our Zikula rollout without these packages? 00:22:25 For Mediaattach: https://bugzilla.redhat.com/show_bug.cgi?id=505938#c5 00:22:26 Bug 505938: medium, low, ---, fedora-docs-list, NEW, Need to package MediaAttach. 00:22:35 Umm, thanks for nuttin' buggbot 00:23:13 Sparks: Well, we can't submit files or other content that's not a written story, withot those modules, if I understand them correctly 00:23:22 i.e attaching RPMs wouldn't be possible 00:23:35 We also wouldn't be able to put up podcasts for Marketing/News 00:23:47 :( 00:24:13 Ah, menutree is the other one that has problems, although they look less horrible 00:24:21 stickster: So what do you propose? action? 00:24:22 So... important to get this done. 00:24:56 I think that several Docs folks who have some PHP/JS knowledge, or can gain it quickly, should agree to get together at a specific date to fix the problems 00:25:09 i.e. Take a Saturday or Sunday and plow through it over IRC 00:25:33 Any takers for assisting? 00:25:35 I'm going to do a blog post to see if we can get one or more PHP/JS persons to come by and help from the general community. 00:26:48 * stickster reminds everyone that they could help by blogging too 00:26:51 #action Stickster to blog to see if we can get some PHP/JS folks to help with out with some Zikula modules. 00:27:14 When the going gets hard... 00:27:36 okay, anything else for Zikula? 00:28:28 #topic Status on CC license rollout. <-- ianweller 00:28:34 ianweller: Umm... waiting on me, right? 00:28:41 afaik 00:28:51 #topic Shared open-source style guide <--ke4qqq 00:29:02 #link https://www.redhat.com/archives/fedora-docs-list/2009-June/msg00163.html 00:29:16 ke4qqq is going to quite busy these next few weeks/months. 00:29:24 Does anyone want to take on this project? 00:29:43 It should be a fun project and I'm sure ke4qqq will want to continue to help out. 00:29:53 I'm happy to take it on 00:29:58 I thought that laubersm and someone else had indicated interest as well 00:30:19 But it will probably be another week or two before I can do anything meaningful with it 00:30:20 * jjmcd anticipates being well entertained the next few months 00:30:51 stickster: Maybe, I don't remember. 00:31:23 * stickster thinks to himself, man, a list conversation would have helped us capture that, probalby. 00:31:25 *probably, even. 00:31:30 Well, this doesn't have to be a one or two person project 00:31:39 Not at all 00:31:50 I met some of the folks working on this when I was at Open Source Bridge -- they are good folks. 00:32:00 #action Sparks to put a note on the list about Shared Open-Source Style Guide 00:32:16 I know that my slackness in getting some of RH's internal material opened up has blocked this a little 00:33:20 Well, I don't know that the project has a good grasp on what needs to happen, etc. 00:33:28 I think they were going to setup a meeting somewhere. 00:34:28 Okay, I'll try to get a better footing on this topic before next week. 00:34:45 #topic Outstanding BZ Tickets 00:34:56 #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW 00:35:22 We are down to 10 NEW bugs. I think we knocked out a few of them last week after the meeting. 00:35:35 Let's see if we can get the rest at least assigned tonight. 00:35:44 Any volunteers to go through them? 00:37:11 * Sparks hears crickets 00:37:27 Didn't we already have one like 507999 00:37:48 In any case, that one is obviously mine 00:38:18 jjmcd -- yeah, I was sure that we did 00:38:27 But I couldn't find it either :) 00:39:09 and 514153 is simple needing release 00:39:36 .bug 184234 00:39:38 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184234 medium, medium, ---, kwade, NEW, A way to check the CVE/CAN status of a currently installed package. 00:39:39 Bug 184234: medium, medium, ---, kwade, NEW, A way to check the CVE/CAN status of a currently installed package. 00:39:45 Ummn.. yeah 00:40:05 So this is an OLD bug but one that is EXTREMELY important to US government/military users 00:40:48 Sparks: http://tinyurl.com/mrfcgp <-- blog post as ordered 00:40:50 Where can we put this? 00:41:17 stickster: Awesome! Now that's efficiency 00:41:34 Wasn't someone working on an enterprise-like guide? 00:41:54 That's the Fedora Deployment Guide 00:42:01 Hmmm... 00:42:09 perspectival has that one 00:42:11 This needs to go into a "user" guide but... 00:42:28 not the "I'm a noob" guide 00:42:51 Sparks: I believe I need a BZ component for the Deployment Guide 00:43:01 sorry to trouble you for more components ;-) 00:43:34 #action Sparks to create BZ component Deployment Guide 00:43:39 perspectival: No problem. 00:43:44 thanks 00:44:01 Okay... How about I accept this one and write it in the wiki somewhere? 00:45:10 #action Sparks to write up CVE checking/validation proceedures in the wiki 00:46:04 I do it enough at work... :) 00:46:14 Okay, moving on... 00:46:30 #topic Guide needs? 00:46:39 Anyone have a Guide that they need assistance with? 00:47:21 #topic New Guides 00:47:31 Okay, anyone have a new guide they'd like to share with us? 00:47:38 or a new guide idea? 00:47:59 Just saying that the IQSG is now in localisation and I should have a copy up on docs.fp.o very shortly 00:48:08 IQSG? 00:48:11 Oh 00:48:17 Installation Quick Start Guide 00:48:18 Installation Quick Start Guide 00:48:23 jinx! 00:48:29 That's awesome. 00:48:36 anyone else? 00:48:48 #topic All other business 00:48:53 Okay, does anyone have anything? 00:49:46 * Sparks thinks we might get out on-time/early tonight 00:50:14 quiet week at the docs project :) 00:50:16 I would like to mention one thing 00:50:40 I'll add a short update here too on what I'm working on 00:50:42 Currently I'm working on gathering an exhaustive list of all F11 new features that could or should be included in the Deployment Guide (done), ensure that these features should actually be listed in the DG (in progress), and then I'll determine where to add them (TOC, etc.), and: post this info to the deployment-guide-list; create placeholders in the DG for major new features (there's already a placeholder chapter for ABRT) 00:51:01 I'm also working on closing a number of bugs filed against the Deployment Guide 00:51:07 The Deployment Guide has the following major sections ("parts" in DocBook terminology): 00:51:14 I. Package Management: yum, rpm, etc. 00:51:14 II. Network-Related Configuration: interfaces, runlevels, services, BIND, apache, openssh, samba, dhcp, ftp, ldap 00:51:14 III. System Configuration: console access, sysconfig dir, date, time, keyboard, X, users, groups, printers, at, batch, cron and log files 00:51:14 IV. System Monitoring: oprofile, ABRT 00:51:15 V. Kernel and Driver Configuration: upgrading, modules, etc. 00:51:33 ** Note that (in contrast to the Red Hat Enterprise Linux Deployment Guide) information on file systems (setting them up, partitioning, lvm, luks, etc.) will not be in the scope of the Deployment Guide for Fedora 00:52:25 No? 00:52:30 Why not? 00:52:34 unfortunately not 00:52:47 * Sparks notes luks is covered fairly well in the Security Guide 00:53:12 it's out-of-scope for the guide that I'm writing 00:53:16 Okay 00:53:28 Well, that's cool 00:53:31 yeah 00:53:42 Anyone have any questions? 00:54:03 the Fedora DG will be huge even without the part on File Systems, etc. 00:54:12 that's all for me unless there are questions... 00:54:40 * rudi notes that its RHEL cousin is nearly 1000 pages long :) 00:54:52 Good reading there 00:55:49 Okay, anyone else? 00:56:56 5 00:56:57 4 00:56:59 3 00:57:06 Speak now or... 00:57:07 2 00:57:15 forever hold your peace 00:57:17 1 00:57:20 * perspectival is holding 00:57:22 #endmeeting -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From eric at christensenplace.us Thu Jul 30 00:59:23 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 29 Jul 2009 20:59:23 -0400 Subject: Docs Meeting 2009-07-30 Summary Message-ID: <1248915563.2617.20.camel@thunder> =================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings =================================================================================================== Meeting started by Sparks at 00:01:59 UTC. The `full logs`_ are available. .. _`full logs`: fedora-meeting.2009-07-30-00.01.log.html Meeting log ----------- * **Roll Call** (Sparks-00:02:10_) * **Last week's action items** (Sparks-00:05:43_) * *ACTION*: Sparks to follow up with Pascal Calarco from News to make sure we are including all packages necessary for Zikula for them. (Sparks-00:07:56_) * *ACTION*: Sparks to write rollout plan for license change... 2nd alarm (Sparks-00:08:49_) * *ACTION*: rudi to help sparks on changing the fedora-brand in Publican for CC license (Sparks-00:10:14_) * **Status on CMS (Zikula) <-- ke4qqq** (Sparks-00:13:30_) * *LINK*: https://fedoraproject.org/wiki/Zikula#Module_status (Sparks-00:13:42_) * *ACTION*: ? (stickster-00:19:39_) * *ACTION*: Sparks to package the three GPL editors for Zikula (Sparks-00:20:09_) * *ACTION*: Stickster to blog to see if we can get some PHP/JS folks to help with out with some Zikula modules. (Sparks-00:26:51_) * **Status on CC license rollout. <-- ianweller** (Sparks-00:28:28_) * **Shared open-source style guide <--ke4qqq** (Sparks-00:28:51_) * *LINK*: https://www.redhat.com/archives/fedora-docs-list/2009-June/msg00163.html (Sparks-00:29:02_) * *ACTION*: Sparks to put a note on the list about Shared Open-Source Style Guide (Sparks-00:32:00_) * **Outstanding BZ Tickets** (Sparks-00:34:45_) * *LINK*: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW (Sparks-00:34:56_) * *ACTION*: Sparks to create BZ component Deployment Guide (Sparks-00:43:34_) * *ACTION*: Sparks to write up CVE checking/validation proceedures in the wiki (Sparks-00:45:10_) * **Guide needs?** (Sparks-00:46:30_) * **New Guides** (Sparks-00:47:21_) * **All other business** (Sparks-00:48:48_) .. _Sparks-00:02:10: fedora-meeting.2009-07-30-00.01.log.html#l-4 .. _Sparks-00:05:43: fedora-meeting.2009-07-30-00.01.log.html#l-15 .. _Sparks-00:07:56: fedora-meeting.2009-07-30-00.01.log.html#l-20 .. _Sparks-00:08:49: fedora-meeting.2009-07-30-00.01.log.html#l-24 .. _Sparks-00:10:14: fedora-meeting.2009-07-30-00.01.log.html#l-34 .. _Sparks-00:13:30: fedora-meeting.2009-07-30-00.01.log.html#l-54 .. _Sparks-00:13:42: fedora-meeting.2009-07-30-00.01.log.html#l-55 .. _stickster-00:19:39: fedora-meeting.2009-07-30-00.01.log.html#l-73 .. _Sparks-00:20:09: fedora-meeting.2009-07-30-00.01.log.html#l-75 .. _Sparks-00:26:51: fedora-meeting.2009-07-30-00.01.log.html#l-100 .. _Sparks-00:28:28: fedora-meeting.2009-07-30-00.01.log.html#l-103 .. _Sparks-00:28:51: fedora-meeting.2009-07-30-00.01.log.html#l-106 .. _Sparks-00:29:02: fedora-meeting.2009-07-30-00.01.log.html#l-107 .. _Sparks-00:32:00: fedora-meeting.2009-07-30-00.01.log.html#l-121 .. _Sparks-00:34:45: fedora-meeting.2009-07-30-00.01.log.html#l-126 .. _Sparks-00:34:56: fedora-meeting.2009-07-30-00.01.log.html#l-127 .. _Sparks-00:43:34: fedora-meeting.2009-07-30-00.01.log.html#l-153 .. _Sparks-00:45:10: fedora-meeting.2009-07-30-00.01.log.html#l-157 .. _Sparks-00:46:30: fedora-meeting.2009-07-30-00.01.log.html#l-160 .. _Sparks-00:47:21: fedora-meeting.2009-07-30-00.01.log.html#l-162 .. _Sparks-00:48:48: fedora-meeting.2009-07-30-00.01.log.html#l-173 Meeting ended at 00:57:22 UTC. Action Items ------------ * Sparks to follow up with Pascal Calarco from News to make sure we are including all packages necessary for Zikula for them. * Sparks to write rollout plan for license change... 2nd alarm * rudi to help sparks on changing the fedora-brand in Publican for CC license * ? * Sparks to package the three GPL editors for Zikula * Stickster to blog to see if we can get some PHP/JS folks to help with out with some Zikula modules. * Sparks to put a note on the list about Shared Open-Source Style Guide * Sparks to create BZ component Deployment Guide * Sparks to write up CVE checking/validation proceedures in the wiki Action Items, by person ----------------------- * rudi * rudi to help sparks on changing the fedora-brand in Publican for CC license * Sparks * Sparks to follow up with Pascal Calarco from News to make sure we are including all packages necessary for Zikula for them. * Sparks to write rollout plan for license change... 2nd alarm * Sparks to package the three GPL editors for Zikula * Sparks to put a note on the list about Shared Open-Source Style Guide * Sparks to create BZ component Deployment Guide * Sparks to write up CVE checking/validation proceedures in the wiki * **UNASSIGNED** * ? * Stickster to blog to see if we can get some PHP/JS folks to help with out with some Zikula modules. People Present (lines said) --------------------------- * Sparks (118) * stickster (38) * perspectival (20) * rudi (16) * jjmcd (10) * ianweller (4) * buggbot (3) * radsy (1) Generated by `MeetBot`_ .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From ryanlerch at gmail.com Thu Jul 30 01:50:28 2009 From: ryanlerch at gmail.com (Ryan Lerch) Date: Thu, 30 Jul 2009 11:50:28 +1000 Subject: Writing Tasks Message-ID: <671a617b0907291850g56dd5ad2s61d889d765eae206@mail.gmail.com> Hi all, Is a list of possible writing tasks for fedora documentation listed anywhere? I am looking at jumping into doing some writing for fedora docs, and I am unsure where to start. What would be perfect is if there is a list of chapters or sections that i could research and document for an existing book that is in development. Does that exist anywhere? cheers, ryanlerch From mel at redhat.com Thu Jul 30 02:21:11 2009 From: mel at redhat.com (Mel Chua) Date: Wed, 29 Jul 2009 22:21:11 -0400 Subject: Almost-finalized: Marketing F12 schedule In-Reply-To: <4A6E881B.4090000@redhat.com> References: <4A6E82C2.1070402@redhat.com> <4A6E881B.4090000@redhat.com> Message-ID: <4A710397.7090501@redhat.com> (Marketing folks - this was asked on the Docs list in response to this email, so I thought it might be good to give a fuller explanation.) > Hello, > It might be stupid question, sorry, what is this for? > Where is 'Localization'? > noriko Thanks for the call-out - I should have been more clear when I sent out that email. This email was basically announcing the almost-final (it will be frozen on Monday) Marketing schedule of what we'll be working on for the F12 release. It's here: https://fedoraproject.org/wiki/Marketing_F12_schedule I sent it to several other lists (including Docs) because one of the things we want to make sure is that our schedule is OK for all the other teams we'll have to work with on a deliverable, or send a deliverable to. For instance, if Marketing is supposed to make 1-page release notes for Docs, a milestone for that should be on the Marketing F12 schedule, and Docs has to be happy with the date of that Marketing milestone, so we can get stuff to you on time. Not all the other teams were listed (for instance, as you pointed out, Localization wasn't mentioned) because we only have "deliverable due dates" for a few teams. We'll still be working with, listening to, and making stuff for all the other teams (and really, anyone working on Fedora who'd like Marketing help) - this list was just to make sure big schedule milestones all matched up. If you think we *should* have specific milestones for a team that isn't listed, please let us know! Hope that explains a bit - and please, let me know if I should be going about this differently, or explaining things better... I'm trying to go around to coordinate individually with the owners of the various team schedules, so things should be taken care of, but I also wanted to let others on the teams that we'll be working with know why they might at some point get stuff from Marketing, or see Marketing people show up at particular meetings, and that kind of thing. ;) --Mel From eric at christensenplace.us Thu Jul 30 03:18:43 2009 From: eric at christensenplace.us (Eric Christensen) Date: Wed, 29 Jul 2009 23:18:43 -0400 Subject: Writing Tasks In-Reply-To: <671a617b0907291850g56dd5ad2s61d889d765eae206@mail.gmail.com> References: <671a617b0907291850g56dd5ad2s61d889d765eae206@mail.gmail.com> Message-ID: <1248923923.13680.1.camel@thunder> On Thu, 2009-07-30 at 11:50 +1000, Ryan Lerch wrote: > Hi all, > > Is a list of possible writing tasks for fedora documentation listed > anywhere? I am looking at jumping into doing some writing for fedora > docs, and I am unsure where to start. > > What would be perfect is if there is a list of chapters or sections > that i could research and document for an existing book that is in > development. Does that exist anywhere? > > cheers, > ryanlerch > Ryan, There is always the Guide table[1]. [1] https://fedoraproject.org/wiki/Docs_Project_guides_table Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From sradvan at redhat.com Thu Jul 30 03:41:59 2009 From: sradvan at redhat.com (Scott Radvan) Date: Thu, 30 Jul 2009 13:41:59 +1000 Subject: Writing Tasks In-Reply-To: <1248923923.13680.1.camel@thunder> References: <671a617b0907291850g56dd5ad2s61d889d765eae206@mail.gmail.com> <1248923923.13680.1.camel@thunder> Message-ID: <20090730134159.5ac35bbf@redhat.com> On Wed, 29 Jul 2009 23:18:43 -0400 Eric Christensen wrote: > On Thu, 2009-07-30 at 11:50 +1000, Ryan Lerch wrote: > > Hi all, > > > > Is a list of possible writing tasks for fedora documentation listed > > anywhere? I am looking at jumping into doing some writing for fedora > > docs, and I am unsure where to start. > > > > What would be perfect is if there is a list of chapters or sections > > that i could research and document for an existing book that is in > > development. Does that exist anywhere? > > > > cheers, > > ryanlerch > > > > Ryan, > There is always the Guide table[1]. > > [1] https://fedoraproject.org/wiki/Docs_Project_guides_table > > Eric The guides table is without a doubt a good thing, but I'm thinking of someone coming from a new member's perspective who might be unsure of where to get started and sends a similar email to Ryan's. This table would be a pretty overwhelming thing for them to get their feet wet with. Ryan has a good idea - wondering if there is a way to divide things up and distribute tasks by section/chapter or at even more granular levels to quickly get new members more familiar with the content, the writing styles that are best, Publican itself and to give them an impression that even from the start, they are immediately having a positive impact on content. I think this would motivate new members to stick around and develop that writing into much larger, independent books. Thoughts? -- Scott Radvan Content Author, Platform (Installation and Deployment) Red Hat Asia Pacific (Brisbane) http://www.apac.redhat.com From eric at christensenplace.us Thu Jul 30 11:57:08 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 30 Jul 2009 07:57:08 -0400 Subject: Writing Tasks In-Reply-To: <20090730134159.5ac35bbf@redhat.com> References: <671a617b0907291850g56dd5ad2s61d889d765eae206@mail.gmail.com> <1248923923.13680.1.camel@thunder> <20090730134159.5ac35bbf@redhat.com> Message-ID: <1248955028.14233.2.camel@thunder> On Thu, 2009-07-30 at 13:41 +1000, Scott Radvan wrote: > On Wed, 29 Jul 2009 23:18:43 -0400 > Eric Christensen wrote: > > > On Thu, 2009-07-30 at 11:50 +1000, Ryan Lerch wrote: > > > Hi all, > > > > > > Is a list of possible writing tasks for fedora documentation listed > > > anywhere? I am looking at jumping into doing some writing for fedora > > > docs, and I am unsure where to start. > > > > > > What would be perfect is if there is a list of chapters or sections > > > that i could research and document for an existing book that is in > > > development. Does that exist anywhere? > > > > > > cheers, > > > ryanlerch > > > > > > > Ryan, > > There is always the Guide table[1]. > > > > [1] https://fedoraproject.org/wiki/Docs_Project_guides_table > > > > Eric > > The guides table is without a doubt a good thing, but I'm thinking of > someone coming from a new member's perspective who might be unsure of > where to get started and sends a similar email to Ryan's. > > This table would be a pretty overwhelming thing for them to get their > feet wet with. > > Ryan has a good idea - wondering if there is a way to divide things up > and distribute tasks by section/chapter or at even more granular levels > to quickly get new members more familiar with the content, the writing > styles that are best, Publican itself and to give them an impression > that even from the start, they are immediately having a positive impact > on content. > > I think this would motivate new members to stick around and develop > that writing into much larger, independent books. > > Thoughts? > > Yeah, that makes sense although I wonder how often a table like that would get updated to reflect actual. If someone looked at the guide table and saw the SELinux User guide they could contact you and say they were interested and you could then point them towards a section/chapter. --Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From ricky at fedoraproject.org Thu Jul 30 15:42:39 2009 From: ricky at fedoraproject.org (Ricky Zhou) Date: Thu, 30 Jul 2009 11:42:39 -0400 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <1247245998.2520.35.camel@thunder.christensenplace.us> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <1247240752.2520.28.camel@thunder.christensenplace.us> <20090710165742.GF3196@alpha.rzhou.org> <9f45b2730907101009x18b7a491y2e55ded93fbe8773@mail.gmail.com> <1247245998.2520.35.camel@thunder.christensenplace.us> Message-ID: <20090730154239.GC23791@alpha.rzhou.org> On 2009-07-10 01:13:18 PM, Eric Christensen wrote: > A quick start guide... Hmmm... Sorry if this is dumb of me, but I didn't notice http://docs.fedoraproject.org/installation-quick-start-guide/f11/en-US/html-single/ until just this moment. I think that's a massive improvement (in terms of friendliness to newbies) over what we currently present to new users from our get-fedora page. If we could put as much concentration on getting this translated as we do for the regular install guide, I think it'd be great to make this the main documentation link on the download page. Thanks, Ricky -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From eric at christensenplace.us Thu Jul 30 16:05:31 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 30 Jul 2009 12:05:31 -0400 Subject: Release Notes Meeting 2009-07-30 Log Message-ID: 15:05:01 #startmeeting Release Notes Meeting 15:05:44 #topic Roll Call 15:05:47 * Sparks 15:06:11 Ack - I totally forgot about this ;-) 15:06:22 * rudi is here 15:06:45 jjmcd: Yeah, me too. I was trying to figure out why rudi was still up! 15:06:54 lolz 15:07:05 * jjmcd was blogging on yesterday's meeting 15:08:12 #topic Last meeting 15:08:18 Okay from the last meeting I see... 15:08:32 that we agreed to use Publican for everything 15:08:53 that we needed three documents (right?) 15:09:21 3 formats? 15:09:28 three documents 15:09:34 1) "normal" RNs 15:09:50 2) "pretty" RNs (one-page by Marketing) 15:10:00 3) things to know about upgrading 15:10:04 Ahh yes, OK 15:10:25 The agenda from last week was: 15:10:32 1. How to improve on the F12 RNs 15:10:41 2. What products need to be generated. 15:10:53 3. Using Publican for the RNs 15:11:00 4. Training people to write beats. 15:11:23 Anything else we need to discuss? 15:11:44 Perhaps today we should address products 15:12:00 okay 15:12:10 #topic RN Products 15:12:10 We have agreement on 3 and last week we hit 1 15:12:36 Yes, and I've successfully gotten a Publican package into the repo now 15:12:57 So there are a few tweeks that need to be made but they aren't difficult 15:13:00 I think there is the question of what to produce for online, how to present it, and what is actually in fedora-release-notes.rpm 15:13:17 Yes 15:13:22 Yeah, getting the rpm actually built isn't a big deal IMO 15:13:32 So, IMO, we should provide the RN online in HTML, HTML-Single, and PDF 15:14:00 +1 -- I really don't think anyone will miss ZIP and TGZ if they're not there... 15:14:17 jjmcd: ? 15:14:19 But my question is what does that look like? The example you had wouldn't work for RN 15:14:39 What does what look like? 15:14:59 The web page where the user selects what he wants 15:15:05 Ahh 15:15:22 I think that ryanlerch has been working on that a little 15:15:27 Well, it will probably (hopefully) be in Zikula by then so this will be a moot point but... 15:15:50 Trying to work out how to tidy up the index page a bit 15:15:51 I made a table that can be seen at docs.fedoraproject.org/security-guide. 15:16:15 It isn't complete but is the basis for not having a complicated jumble 15:16:21 Does that really change anything? The user still needs to be faced with an incredible array of choices. 15:16:28 Well, that isn't terrubly useful 15:16:30 (ryanlerch is ECS's graphics go-to-guy) 15:16:43 Actually use http://docs.fedoraproject.org/selinux-user-guide/ 15:16:50 My table is jacked up, apparently 15:16:57 the security guide only has a few languages, not 12 releases, 42 languages, live versus now 15:17:15 Lots of choices isn't a problem. Being able to clearly see the choices is the problem 15:17:23 why 12 releases? 15:17:38 We keep RN's online for past releases 15:17:59 1512 products per release 15:18:12 Hold on... 15:18:20 I think it's really important to have that archival material important; but does it need to be right there in the face of the user who's probably looking for the latest stuff? 15:18:29 You have like a dozen for security-guide 15:18:30 We can group the different releases into their own tables and provide links to those at the top of the page... 15:18:37 rudi: I'll buy that 15:18:42 but how do you get 1512 products per release? 15:19:02 whoops, I added in the 12, forgot the 2 15:19:26 OK, only 252 15:19:34 How do you get 252? 15:20:14 42 langs times 3 formats times 2 (we keep the original for live as well as most reent) 15:20:49 Well, if we sort by language and each language has three options then it shouldn't be complicated. 15:21:02 sort language alphabetically 15:21:06 I'm not sure we really need that but it's what we've been doing 15:21:27 No, what I've seen is a jumble of language codes which is NOT user friendly 15:21:58 Hmmmm, with help from L10N we could have a language selection leading to a table of releases/formats 15:21:58 There is a BIG difference between the release-notes and the selinux-user-guide page 15:22:13 Yes, hundreds of docs verses a handful 15:22:35 But the way the RN languages are presented is not good 15:22:38 it is very confusing 15:22:55 I agree, but RN's presented like SG would be much worse 15:23:11 You can add every language you want to under the SELinux and everything will be easy to find 15:23:54 I'm not really thrilled with a 1000 line long list 15:24:06 But it wouldn't be 1000 lines 15:24:14 just 42 15:24:28 sorted alphabetically by language 15:24:51 So you choose the release on a separate page? 15:24:54 We'd put each release in it's own table to break it up 15:25:10 nah, just stack the tables with links to the table at the top of the page or something 15:25:17 Oh, no, a link to previous releases which looks like the current, that might work 15:25:19 but you could do separate pages 15:25:43 Or current-2 on the main page, and everything else on another page 15:25:48 sure 15:26:10 Might be interesting to break them all up on different pages just to see the hits 15:26:28 Yeah 15:27:04 Of course this is a near-pointless conversation if we do get Zikula stood up before then 15:27:23 Why? We still have the question as to how to present it 15:27:44 Yeah, but we might have a completely different set of ways to present it then 15:27:55 drop down menus and other sexy things 15:28:40 Well, I haven't played with Zikula enough, but it doesn't seem to make that much difference. Personally, I'm mostly hoping to get away from that stupid CVS ;-)) 15:29:14 Well, I think Zikula will automate a few things for us. 15:29:35 And we won't be waiting for hours while the docs.fp.o site updates 15:30:00 The release notes pages is already php, we could do drop downs and other goodies if we wanted 15:30:25 But it is kind of a pain to do anything when you have a bunch of character sets you can't read 15:30:35 We could... I'm just not that talented anymore. If someone wants to do it I say go for it. 15:30:40 Yes 15:31:00 I might forward this conversation to ryan when I see him in a few hours :) 15:31:40 :) 15:31:54 OK, I'll go play with something on my local zikula instance and see if a vison comes down from the heavens, but a single list of langs with a link to old stuff sounds like good possibility 15:32:27 Okay 15:32:50 rudi: good for you? 15:33:01 All good 15:33:31 #agreed a single list of langs with a link to old stuff sounds good for presentation on docs.fp.o 15:33:37 jjmcd: What's next? 15:33:42 OK, so what about f-r-n.rpm? Are we going to try to separate by lang? 15:33:45 Before we move on.... 15:33:54 rudi: Go ahead 15:34:03 I thought that we should probably talk about the "minor docs" 15:34:16 Yeah 15:34:32 * Sparks has always been confused by the "minor docs" 15:34:36 These are currently packaged with the release notes, but I really don't think that they belong there. 15:34:44 What are they? 15:34:48 And why are they there? 15:34:49 These are the docs that can't drink 15:34:53 lolz 15:34:59 Readme 15:35:00 Ha! 15:35:01 About Fedora 15:35:12 Readme-burning-isos 15:35:13 readme, readme-burning-isos, homepage, etc 15:35:15 readme-live-images 15:35:20 yeah 15:35:37 I understand the "About Fedora". Why the others? 15:35:51 Legacy, I presume 15:35:53 About-Fedora shows up in yelp, but I wonder how many people ever trip across the others 15:36:08 Should they be in yelp too? 15:36:28 Well... if we aren't presenting them in yelp why are they there? 15:36:39 In some ways, their scope makes them look lke ideal wiki contenders 15:36:43 Couldn't we integrate it into a guide better? 15:36:46 Currently they are text 15:36:52 But static docs lend themselves better to localisation 15:37:01 and these docs have been *extensively* localised 15:37:15 (I presume because they're short and therefore attractive projects) 15:37:40 Perhaps about-fedora contains links to these docs instead of putting them in the rpm 15:37:53 Well, can we either make them guides onto themselves or fold them into another guide 15:37:59 jjmcd: +1 15:38:10 jjmcd -- at the very most. 15:38:27 homepage is a different Q tho 15:38:36 What is homepage? 15:38:48 What you get when you open Galeon 15:39:03 or maybe its epiphany 15:39:04 A page that loads in certain browsers if you start the browser without a net connection 15:39:22 Ahhh 15:39:22 In at least one of them, you get it even if you have a connection 15:39:29 Heh 15:39:50 I think the connection thing used to be the case for firefox but isn't anymore 15:39:51 * Sparks notes that FF starts http://start.fedoraproject.org 15:39:52 I think it's awful; all it can do is confuse users into thinking that they're online, when they're really not 15:40:36 Well, I think it should be separate from the RNs 15:40:44 Sparks +1 15:40:55 I don't like bundling all this stuff together 15:40:57 We need to understand what browsers use it and why 15:41:01 And if Galeon or something else needs it; it should belong to that package 15:41:14 We need to identify the something else 15:41:20 If it's one browser I agree, but I think there are multiples 15:41:27 Or should be packaged up as a dependency for whoever needs/wants it. 15:41:48 (Or they should get their browsers to point to something more useful... this is 2009....) 15:41:59 Exactly, rudi 15:42:09 yes 15:42:33 But we need to identify the affected browsers and contact their developers 15:42:44 jjmcd: Want to handle that? 15:42:57 I guess I can do that 15:43:19 As for "About Fedora"... 15:43:26 #action jjmcd to determine the affected browsers and contact the developers for the homepage project 15:44:16 (sorry -- am I getting too far ahead?) 15:44:21 I've wanted an excise to see what browsers we have 15:44:52 lynx uses it even if you are connected 15:46:10 jjmcd: Yeah 15:46:19 rudi: Go ahead with the "About Fedora' 15:47:00 I can see the importance of that if it shows up in Yelp; but it doesn't really have anything to do with the RNs 15:47:45 I just wonder if there's a better home for it... 15:48:10 (With yelp itself if that's the only place people will ever see it?) 15:50:10 (And who would miss it if it wasn't even there?) 15:51:23 Well, mostly it's recruiting 15:52:09 I think it should be packaged separately 15:52:34 I think it has its place in the OS but it is separate from the RN 15:52:47 +1 15:53:16 f-r-n.rpm currently contains all the OS docs installed on the users system. Do we buy a lot by breaking it up into multiple packages? 15:53:53 Well, it may only be two packages (three if we have to keep homepage) 15:53:54 Well, that's less to download when there is an update of one piece 15:54:16 Yeah, but about-fedora and homepage are pretty tiny 15:54:35 We will add to the space we take on the live cd by breaking them up 15:55:07 How much space? Is it negligable? 15:55:25 Its pretty small, but then every byte on the LiveCD is precious 15:55:32 I agree 15:55:41 Who is in charge of the LiveCD project? 15:55:58 Dunno? Is that Jeroen? 15:56:47 I don't know. But if that is our blocker we should contact those folks 15:57:17 I gotta boogie here pretty soon, but I will go ahead and run a test to see what the price actually is 15:57:18 Well, if we can at least get the Live-Images and Burning-ISOs docs out of there this time around, that's a start :/ 15:57:20 DavidZeuthen 15:57:52 that's a new name to me. I think RelEng spends a lot of time stressing over it each release 15:57:58 rudi: That's true. removing those docs will reduce the overall size that we've been pushing 15:58:15 ...and, more importantly, complexity and redundancy... 15:58:18 jjmcd: Jeremy Katz and Douglas McClendon too 15:58:36 rudi: Yes 15:59:16 Maybe we add to Yelp an "Additional DOcumentation" topic that has links to install, security, etc 15:59:16 #action jjmcd to determine space differentials between the combined RN and the individual files in RPMs 15:59:26 jjmcd: +1 16:00:01 #idea break up all documents that are currently packaged as f-r-n.rpm into separate RPMs 16:00:27 #idea -- don't package any that we don't know that we have to 16:00:32 #idea move Readme-burning-isos and readme into a guide 16:00:48 anything else we need to capture? 16:01:01 I think that was it :) 16:01:05 OK, I gotta go, but I have a few action items (which I needed like a hole in the head) 16:01:12 That was my "wo minutes of minor docs hate" 16:01:12 :) 16:01:18 jjmcd -- before you run 16:01:29 ? 16:01:30 Just a heads up that I branched f12 tonight 16:01:34 cool 16:01:36 (In case you didn't see) 16:01:42 appreciate it 16:01:49 And loaded in some dummy content that you can pull down and build :) 16:02:34 OK, so master is sstill F11, but we will change that after the next update to get in changes and new translations 16:02:41 jjmcd: I'm going to do a blog on the beats here in a minute 16:02:44 Yeah 16:02:47 good deal 16:02:50 jjmcd: Is there a link to the beats for f12? 16:03:03 wiki/Documentation_Beats 16:03:12 cool 16:03:19 anything else? 16:03:37 Not from me :) 16:03:41 jjmcd: you? 16:03:45 nope 16:03:48 We seem to average one agenda item per hour :) 16:04:27 rudi: Yeah but we do get a lot done 16:04:28 :) 16:04:31 Okay... 16:04:34 #endmeeting From eric at christensenplace.us Thu Jul 30 16:08:07 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 30 Jul 2009 12:08:07 -0400 Subject: Release Notes Meeting 2009-07-30 Summary Message-ID: ======================================== #fedora-meeting-1: Release Notes Meeting ======================================== Meeting started by Sparks at 15:05:01 UTC. The `full logs`_ are available. .. _`full logs`: fedora-meeting-1.2009-07-30-15.05.log.html Meeting log ----------- * **Roll Call** (Sparks-15:05:44_) * **Last meeting** (Sparks-15:08:12_) * **RN Products** (Sparks-15:12:10_) * *AGREED*: a single list of langs with a link to old stuff sounds good for presentation on docs.fp.o (Sparks-15:33:31_) * *ACTION*: jjmcd to determine the affected browsers and contact the developers for the homepage project (Sparks-15:43:26_) * *ACTION*: jjmcd to determine space differentials between the combined RN and the individual files in RPMs (Sparks-15:59:16_) * *IDEA*: break up all documents that are currently packaged as f-r-n.rpm into separate RPMs (Sparks-16:00:01_) * *IDEA*: -- don't package any that we don't know that we have to (rudi-16:00:27_) * *IDEA*: move Readme-burning-isos and readme into a guide (Sparks-16:00:32_) .. _Sparks-15:05:44: fedora-meeting-1.2009-07-30-15.05.log.html#l-2 .. _Sparks-15:08:12: fedora-meeting-1.2009-07-30-15.05.log.html#l-9 .. _Sparks-15:12:10: fedora-meeting-1.2009-07-30-15.05.log.html#l-27 .. _Sparks-15:33:31: fedora-meeting-1.2009-07-30-15.05.log.html#l-107 .. _Sparks-15:43:26: fedora-meeting-1.2009-07-30-15.05.log.html#l-168 .. _Sparks-15:59:16: fedora-meeting-1.2009-07-30-15.05.log.html#l-202 .. _Sparks-16:00:01: fedora-meeting-1.2009-07-30-15.05.log.html#l-204 .. _rudi-16:00:27: fedora-meeting-1.2009-07-30-15.05.log.html#l-205 .. _Sparks-16:00:32: fedora-meeting-1.2009-07-30-15.05.log.html#l-206 Meeting ended at 16:04:34 UTC. Action Items ------------ * jjmcd to determine the affected browsers and contact the developers for the homepage project * jjmcd to determine space differentials between the combined RN and the individual files in RPMs Action Items, by person ----------------------- * jjmcd * jjmcd to determine the affected browsers and contact the developers for the homepage project * jjmcd to determine space differentials between the combined RN and the individual files in RPMs * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * Sparks (112) * jjmcd (70) * rudi (52) Generated by `MeetBot`_ .. _`MeetBot`: http://wiki.debian.org/MeetBot From r.landmann at redhat.com Thu Jul 30 16:11:41 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Fri, 31 Jul 2009 02:11:41 +1000 Subject: Need Feedback on HOWTO wiki created by /me. In-Reply-To: <20090730154239.GC23791@alpha.rzhou.org> References: <9f45b2730907100830h7fbe5577k67ac3d5e6fe4bb65@mail.gmail.com> <1247240752.2520.28.camel@thunder.christensenplace.us> <20090710165742.GF3196@alpha.rzhou.org> <9f45b2730907101009x18b7a491y2e55ded93fbe8773@mail.gmail.com> <1247245998.2520.35.camel@thunder.christensenplace.us> <20090730154239.GC23791@alpha.rzhou.org> Message-ID: <4A71C63D.8040804@redhat.com> On 07/31/2009 01:42 AM, Ricky Zhou wrote: > On 2009-07-10 01:13:18 PM, Eric Christensen wrote: > >> A quick start guide... Hmmm... >> > Sorry if this is dumb of me, but I didn't notice > http://docs.fedoraproject.org/installation-quick-start-guide/f11/en-US/html-single/ > until just this moment. That's OK -- it's only been live for a few hours :) > I think that's a massive improvement (in terms > of friendliness to newbies) over what we currently present to new users > from our get-fedora page. If we could put as much concentration on > getting this translated as we do for the regular install guide, I think > it'd be great to make this the main documentation link on the download > page. > > Not a bad idea, but links are cheap, so perhaps we could link to both? Localisation of this guide is well underway; partially because it's mostly built of strings taken from the "full" Installation Guide (and the "Live Images" doc) Thanks for the positive feedback! Cheers Rudi From eric at christensenplace.us Thu Jul 30 18:17:58 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 30 Jul 2009 14:17:58 -0400 Subject: Fwd: Czech translation of Fedora 11 Release Notes In-Reply-To: <4A71DD81.2000306@upcmail.cz> References: <4A71DD81.2000306@upcmail.cz> Message-ID: ---------- Forwarded message ---------- From: Josef Hru?ka Date: 2009/7/30 Subject: Czech translation of Fedora 11 Release Notes To: fedora-trans-list at redhat.com Hi, I am sorry to disturb all from the discussion on ?Fedora 12 Release Notes schedule but the Czech translation of F11 Release Notes is now on 90% and I ?have two three questions. Would it be possible to publish the Release Notes as a web page(s) on Fedora Project? At lease for "pre-view" purposes, to work on finalisation of the translation before official publication? How can I help or what I should do to happen this (publication on the FP web site)? Josef -- Fedora-trans-list mailing list Fedora-trans-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list John, Can you post this to docs.fp.o, please? Thanks, Eric From r.landmann at redhat.com Fri Jul 31 00:00:16 2009 From: r.landmann at redhat.com (Ruediger Landmann) Date: Fri, 31 Jul 2009 10:00:16 +1000 Subject: Czech translation of Fedora 11 Release Notes In-Reply-To: <4A71DD81.2000306@upcmail.cz> References: <4A71DD81.2000306@upcmail.cz> Message-ID: <4A723410.40509@redhat.com> On 07/31/2009 03:50 AM, Josef Hru?ka wrote: > Hi, > I am sorry to disturb all from the discussion on Fedora 12 Release > Notes schedule but the Czech translation of F11 Release Notes is now on > 90% and I have two three questions. > Would it be possible to publish the Release Notes as a web page(s) on > Fedora Project? At lease for "pre-view" purposes, to work on > finalisation of the translation before official publication? > Hi Josef -- and many, many thanks for your hard work on getting the Release Notes translated! I've just rebuilt the Czech version and pushed it to the docs.fedoraproject.org repo; it will become visible the next time that the webserver synchronises with the repo (sometime in the next few hours). I also corrected a small number of little XML errors that prevented the book from building properly. You can see them here: http://git.fedorahosted.org/git/docs/?p=docs/release-notes.git;a=commitdiff;h=d7e660d5fa987faac69ae0f5256ba506e4fb4381 I notice that you still have the cs.po file checked out through Transifex; if you check this back in, you'll over-write those changes, so you should either download a fresh copy of cs.po, or if you have made changes in your local copy that you haven't checked in yet, please fix those same errors in your local copy before uploading :) > How can I help or what I should do to happen this (publication on the FP > web site)? > > Getting from the po file submitted in Transifex to pages on the web site is a long, complicated, and frustrating process that involves wrestling with a couple of incompatible tools ;) You can get a feel for the first stages of the process here: https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00150.html -- with a correction here: https://www.redhat.com/archives/fedora-trans-list/2009-May/msg00169.html I seriously suggest that it's not worth learning this process unless you have a lot of time and need more pain in your life -- both the incompatible tools (Transifex and Publican) are about to have major upgrades soon that will make almost all of this irrelevant... Cheers Rudi From eric at christensenplace.us Fri Jul 31 02:33:53 2009 From: eric at christensenplace.us (Eric Christensen) Date: Thu, 30 Jul 2009 22:33:53 -0400 Subject: Zikula Help Message-ID: <1249007633.26667.4.camel@thunder> Paul wanted me to contact you guys to see if we could figure out a good time for us all to get together to work on the problems we are having with the Zikula modules. You can read about the problems by checking out bugs 492091, 505938, and 506038. Bug 511998 is also licensing related, but it?s easier to solve even by the unskilled (rip and replace some icons). Thanks again for stepping up! -- Thanks, Eric Christensen Fedora Docs Project Lead Fedora Talk: 5102043 Phone: 919-424-0063 x 5102043 E-Mail: sparks at fedoraproject.org SIP: sparks at talk.fedoraproject.org IRC: Sparks on freenode.net GPG Fingerprint: CA02 4ACA EB6C 1A76 F0D6 1127 7D04 D240 BD0C 14C1 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From poelstra at redhat.com Fri Jul 31 16:15:35 2009 From: poelstra at redhat.com (John Poelstra) Date: Fri, 31 Jul 2009 09:15:35 -0700 Subject: Release Notes Schedule In-Reply-To: <9B25474BCF0D4CDC854AEC0E79CDB862@Aidan> References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan><4A6F7B13.9000105@redhat.com> <4A6FB3EB.9050406@redhat.com> <9B25474BCF0D4CDC854AEC0E79CDB862@Aidan> Message-ID: <4A7318A7.5070304@redhat.com> John J. McDonough said the following on 07/29/2009 04:56 PM Pacific >> >> Could someone set up a meeting time and date using www.whenisgood.net? >> I promise to add my availability and create a text version of the >> existing schedule that we can then hack through and update together on >> Gobby. It helps if I am there so I can capture the dependencies >> between the tasks and embed them in the TaskJuggler source file. >> >> Thanks, >> John > > I think John has the right idea here, but I'm not sure I know who all > the players need to be. > > --McD > I think all we need is someone with a firm grasp of task details from both teams plus me. Paul Frields has also joined past meetings and has provided good insight. My approach lately has been to set up www.whenisgood.net with my availability and then encourage others to fill in theirs. We really should nail this down sometime next week. John From wb8rcr at arrl.net Fri Jul 31 17:34:15 2009 From: wb8rcr at arrl.net (John J. McDonough) Date: Fri, 31 Jul 2009 13:34:15 -0400 Subject: Release Notes Schedule References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan><4A6F7B13.9000105@redhat.com> <4A6FB3EB.9050406@redhat.com><9B25474BCF0D4CDC854AEC0E79CDB862@Aidan> <4A7318A7.5070304@redhat.com> Message-ID: <416AE8E0F24C4AC2A53FF917110B4C91@Aidan> ----- Original Message ----- From: "John Poelstra" To: "For participants of the Documentation Project" Sent: Friday, July 31, 2009 12:15 PM Subject: Re: Release Notes Schedule > John J. McDonough said the following on 07/29/2009 04:56 PM Pacific >>> >>> Could someone set up a meeting time and date using www.whenisgood.net? I >>> promise to add my availability and create a text version of the existing >>> schedule that we can then hack through and update together on Gobby. It >>> helps if I am there so I can capture the dependencies between the tasks >>> and embed them in the TaskJuggler source file. >>> >>> Thanks, >>> John >> >> I think John has the right idea here, but I'm not sure I know who all the >> players need to be. >> >> --McD >> > > I think all we need is someone with a firm grasp of task details from both > teams plus me. Paul Frields has also joined past meetings and has > provided good insight. My approach lately has been to set up > www.whenisgood.net with my availability and then encourage others to fill > in theirs. > > We really should nail this down sometime next week. Well, I think Eric and I can cover Docs, and our main point of contact is L10N. I don't have a good grasp on how that team works, but perhaps Dimitris and Noriko are the experts there. I just don't know. --McD From poelstra at redhat.com Fri Jul 31 18:33:56 2009 From: poelstra at redhat.com (John Poelstra) Date: Fri, 31 Jul 2009 11:33:56 -0700 Subject: Release Notes Schedule In-Reply-To: <416AE8E0F24C4AC2A53FF917110B4C91@Aidan> References: <192D57B9304543F3BE49371BB709988B@Aidan><20090727124105.GE13895@localhost.localdomain><0E09E85B5E6E498DBC0915CDA22B5427@Aidan> <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan><4A6F7B13.9000105@redhat.com> <4A6FB3EB.9050406@redhat.com><9B25474BCF0D4CDC854AEC0E79CDB862@Aidan> <4A7318A7.5070304@redhat.com> <416AE8E0F24C4AC2A53FF917110B4C91@Aidan> Message-ID: <4A733914.2010409@redhat.com> John J. McDonough said the following on 07/31/2009 10:34 AM Pacific Time: > > ----- Original Message ----- From: "John Poelstra" > To: "For participants of the Documentation Project" > > Sent: Friday, July 31, 2009 12:15 PM > Subject: Re: Release Notes Schedule > > >> John J. McDonough said the following on 07/29/2009 04:56 PM Pacific >>>> >>>> Could someone set up a meeting time and date using >>>> www.whenisgood.net? I promise to add my availability and create a >>>> text version of the existing schedule that we can then hack through >>>> and update together on Gobby. It helps if I am there so I can >>>> capture the dependencies between the tasks and embed them in the >>>> TaskJuggler source file. >>>> >>>> Thanks, >>>> John >>> >>> I think John has the right idea here, but I'm not sure I know who all >>> the players need to be. >>> >>> --McD >>> >> >> I think all we need is someone with a firm grasp of task details from >> both teams plus me. Paul Frields has also joined past meetings and >> has provided good insight. My approach lately has been to set up >> www.whenisgood.net with my availability and then encourage others to >> fill in theirs. >> >> We really should nail this down sometime next week. > > Well, I think Eric and I can cover Docs, and our main point of contact > is L10N. I don't have a good grasp on how that team works, but perhaps > Dimitris and Noriko are the experts there. I just don't know. > > --McD > Yes, we need someone from the translation team to volunteer and be available :) John From stickster at gmail.com Fri Jul 31 18:40:49 2009 From: stickster at gmail.com (Paul W. Frields) Date: Fri, 31 Jul 2009 14:40:49 -0400 Subject: Release Notes Schedule In-Reply-To: <4A733914.2010409@redhat.com> References: <20090727153926.GL17605@localhost.localdomain> <4A6E7F1F.4010908@redhat.com> <2C066D82202C4DC3B34889B3A394772E@Aidan> <4A6F7B13.9000105@redhat.com> <4A6FB3EB.9050406@redhat.com> <9B25474BCF0D4CDC854AEC0E79CDB862@Aidan> <4A7318A7.5070304@redhat.com> <416AE8E0F24C4AC2A53FF917110B4C91@Aidan> <4A733914.2010409@redhat.com> Message-ID: <20090731184049.GX3814@localhost.localdomain> On Fri, Jul 31, 2009 at 11:33:56AM -0700, John Poelstra wrote: > John J. McDonough said the following on 07/31/2009 10:34 AM Pacific Time: >> >> ----- Original Message ----- From: "John Poelstra" >> To: "For participants of the Documentation Project" >> >> Sent: Friday, July 31, 2009 12:15 PM >> Subject: Re: Release Notes Schedule >> >> >>> John J. McDonough said the following on 07/29/2009 04:56 PM Pacific >>>>> >>>>> Could someone set up a meeting time and date using >>>>> www.whenisgood.net? I promise to add my availability and create a >>>>> text version of the existing schedule that we can then hack >>>>> through and update together on Gobby. It helps if I am there so I >>>>> can capture the dependencies between the tasks and embed them in >>>>> the TaskJuggler source file. >>>>> >>>>> Thanks, >>>>> John >>>> >>>> I think John has the right idea here, but I'm not sure I know who >>>> all the players need to be. >>>> >>>> --McD >>>> >>> >>> I think all we need is someone with a firm grasp of task details from >>> both teams plus me. Paul Frields has also joined past meetings and >>> has provided good insight. My approach lately has been to set up >>> www.whenisgood.net with my availability and then encourage others to >>> fill in theirs. >>> >>> We really should nail this down sometime next week. >> >> Well, I think Eric and I can cover Docs, and our main point of contact >> is L10N. I don't have a good grasp on how that team works, but perhaps >> Dimitris and Noriko are the experts there. I just don't know. >> >> --McD >> > > Yes, we need someone from the translation team to volunteer and be > available :) Dimitris and Noriko are both members of the L10n steering group -- essentially, they are among the people who make sure things are moving apace in the overall L10n team. It's much the same function as John McDonough and Eric Christensen, among others, fulfill in Docs. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug