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