--- Log opened Wed Nov 14 09:59:53 2007 | ||
-!- Topic for #fedora-meeting: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel for meeting schedule | 10:03 | |
-!- Topic set by couf [n=bart@fedora/couf] [Tue Nov 13 15:32:37 2007] | 10:03 | |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting (1500UTC) | 10:03 | |
-!- dwmw2_gone is now known as dwmw2_BOS | 10:04 | |
wwoods | rdieter, nirik, mether, rmw, Lovechild: ping | 10:04 |
---|---|---|
-!- spevack_ is now known as spevack | 10:05 | |
wwoods | and f13 / jeremy / other multi-diciplinary folks: also ping | 10:05 |
rdieter | here (kinda sorta) | 10:05 |
f13 | yo | 10:05 |
wwoods | rdieter: cool | 10:05 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | Schedule changes for F9 | 10:05 | |
wwoods | So yes - I'm writing an email to fedora-test-list about the proposed changes | 10:05 |
-!- tibbs [n=tibbs@fedora/tibbs] has joined #fedora-meeting | 10:05 | |
wwoods | to make sure everyone's aware (there was brief mention of it last month but I still hear references to "test1" etc) | 10:06 |
wwoods | Is everyone aware of / cool with the propose changes/schedule? | 10:06 |
wwoods | those are http://fedoraproject.org/wiki/ReleaseEngineering/DevelopmentChangesProposal | 10:06 |
wwoods | and http://poelstra.fedorapeople.org/schedules/f9/f9-tasks-overview.html | 10:06 |
wwoods | the only thing I've found that I'm still unsure about is that the Alpha release is still two months after Final | 10:07 |
f13 | wwoods: the Alpha was an idea to have /something/ that is known to at least be installable as a jump off point for the development cycle. | 10:07 |
wwoods | right | 10:07 |
f13 | but we don't care much about other than it installing and getting updates afterward, so we're not doing a blocking freeze for it. it's just a named snapshot | 10:08 |
f13 | (with a little extra time to make sure it happens) | 10:08 |
wwoods | like I said, in the past we've gottin (deserved) bad press for putting out a half-baked release that lacks most of the stuff promised | 10:08 |
wwoods | I think calling it "Alpha" and increasing awareness that test releases are just rawhide snapshots is good | 10:08 |
wwoods | but also - sanity check - there's more time for rawhide development now than in previous cycles, right? | 10:09 |
f13 | yes | 10:09 |
f13 | there is no blocking freeze for test1, that adds a week~ there | 10:09 |
wwoods | now that we're doing the early branching and such the devs actually get some time before F8 final to work on stuff | 10:09 |
f13 | plus add to that the amount of time we early branched and branched during F8 that added a month~ | 10:09 |
wwoods | yeah, that's reasonable. I do think we're already seeing serious progress in f9 rawhide | 10:10 |
wwoods | a lot moreso than previous ones | 10:10 |
wwoods | as long as we believe that to be the intended effect of process changes and not just a happy fluke | 10:10 |
rdieter | folks realize they can't wait (me included). :) | 10:10 |
wwoods | then I'm happy relying on that | 10:10 |
f13 | yeah | 10:10 |
f13 | I do want to better deal with a month+ of buildup for that first rawhide build. | 10:11 |
f13 | eventually I want to get to the piont where during teh final freeze, we're composing the release tree to a different location, and letting Rawhide continue on to the next release. | 10:11 |
wwoods | my only other comment about the schedule: I'm gonna be doing family stuff the week of PR1, so I need someone to take the bug-herding hat while I'm gone | 10:12 |
wwoods | f13: that would be totally sweet. | 10:12 |
f13 | We'll use mirror manager to do some fun redirects for us to try and capture most people for release testing, you'd have to opt-out and into Rawhide again to get those bits. | 10:12 |
f13 | wwoods: I don't think we can realistically get there for 9, but maybe !10 | 10:12 |
wwoods | so we're planning on doing the repo shuffle to pin rawhide to the final release again? | 10:13 |
wwoods | (I liked that a lot) | 10:13 |
f13 | yes, I liked that too | 10:13 |
f13 | we'll better plan it to avoid zomg no signed packages. | 10:13 |
wwoods | can you make sure that gets on the schedule and do an announcement so people know when it's coming | 10:13 |
f13 | yes | 10:14 |
wwoods | yeah, exactly | 10:14 |
wwoods | any other comments about the schedule changes? one less test release to test, yay | 10:14 |
f13 | well, if we have a signing server and are automatically signing things with a key, that should take care of itself. | 10:14 |
f13 | they'll at least have /a/ key. | 10:14 |
wwoods | rdieter: when is kde4 stuff landing? in time for F9Alpha? | 10:14 |
f13 | wwoods: I'm pretty sure you're going to have one less arch to care about. | 10:14 |
f13 | wwoods: but the tradeoff looks to be one more install method. | 10:15 |
rdieter | wwoods: we're about 35% there roughly now, should get most of it in by then (cross fingers) | 10:15 |
wwoods | here's hopin' | 10:15 |
wwoods | some QA-specific stuff to discuss | 10:15 |
wwoods | I don't think we're gonna create bugzilla versions for alpha/beta | 10:15 |
wwoods | the reasoning is: Test Releases Are Rawhide Snapshots | 10:16 |
f13 | srsly? | 10:16 |
f13 | are we going to remove all the existing ones? | 10:16 |
wwoods | so report your dang bugs against 'rawhide' | 10:16 |
-!- mizmo [i=duffy@nat/redhat/x-f0982a828406e361] has joined #fedora-meeting | 10:16 | |
wwoods | I'd like to, yes | 10:16 |
wwoods | but I may be a bit overzealous here | 10:16 |
f13 | I'm on board if we remove the existing ones, otherwise we're just going to get a bunch of misfires. | 10:16 |
f13 | (and people filing bugs about there being no version to file bugs against) | 10:16 |
wwoods | I'm amazed at how many bugs we get filed against 'f6test3' still | 10:17 |
wwoods | seriously? f6test3? | 10:17 |
* wwoods shakes head | 10:17 | |
* poelcat +1 to removing all the unneeded versions | 10:18 | |
f13 | wwoods: actually I think by some twist of fuckness, a brand new bugzilla user creating a new bug for Fedora gets f6test3 as the default version :/ | 10:18 |
wwoods | f13: I think you're right | 10:18 |
wwoods | but I don't know why | 10:18 |
f13 | wwoods: we really need to make sure that brand new users get the right version, but I don't know how to fix that | 10:18 |
wwoods | I'll follow up with dkl about that | 10:18 |
wwoods | probably assume (latest stable) unless their browser tells us otherwise | 10:19 |
wwoods | further about rawhide: I've proposed changing the 'devel' version to 'rawhide' | 10:19 |
wwoods | which I think is only sensible | 10:19 |
poelcat | wwoods: are you going to talk to him about removing the extra versions too? I don't mind working with dkl to merge everything | 10:19 |
wwoods | but there's a further proposal which suggests that we name releases at the *start* of the cycle and use that name instead of "rawhide" | 10:20 |
f13 | wwoods: I don't think that should effect bugzilla | 10:20 |
wwoods | so we'd call it "werewolf" as a codename up until release, and then the name would change to F8 | 10:20 |
f13 | wwoods: the only reasonable rational I heard for naming early was so that artwork and such can be made to fit before deadlines. | 10:20 |
wwoods | right, it just makes it a little confusing as there'd be no "werewolf" version in bz | 10:21 |
rdieter | and marketing... | 10:21 |
f13 | we may also use the codename as the pre-release staging directory as well. | 10:21 |
wwoods | well, it helps with marketing/branding as well | 10:21 |
poelcat | but then you have to keep monkeying with bugzilla | 10:21 |
f13 | but I'm still very much in the 'file it against Rawhide' camp. | 10:21 |
poelcat | couldn't the bugzilla start page help this? | 10:21 |
poelcat | or is that project dead? | 10:21 |
rdieter | maybe use bz label something like f8-werewolf ? then, no renaming is required. | 10:22 |
-!- LetoTo [n=paul@193.110.157.17] has joined #fedora-meeting | 10:22 | |
wwoods | well, we want to avoid the ambiguity of having "f8" and "f8-werewolf" | 10:22 |
rdieter | ok | 10:22 |
wwoods | it's possible we could segment off rawhide this way | 10:22 |
-!- Lovechild [n=david@about/unixlove/Lovechild] has joined #fedora-meeting | 10:22 | |
wwoods | have rawhide (moonshine), rawhide (werewolf), ... | 10:23 |
f13 | eeew | 10:23 |
wwoods | but.. yeah | 10:23 |
wwoods | poelcat: bugzilla start page is still a good idea - we even have bugz.fedoraproject.org | 10:23 |
wwoods | which, while having a silly name, has useful redirects | 10:24 |
wwoods | e.g. try http://bugz.fedoraproject.org/yelp | 10:24 |
rdieter | kewl | 10:25 |
wwoods | so having a front page on that site (rather than having it redirect straight to regular bz) could be useful | 10:25 |
Lovechild | oh that will come in handy.. still not optimal but way better than what I do currently | 10:25 |
wwoods | that also gives you links to the bodhi/koji/pkgdb pages for that package | 10:25 |
wwoods | it's pretty nice | 10:25 |
wwoods | heh | 10:25 |
wwoods | anyway I think probably playing silly games with bugzilla versions and rawhide is not the most useful thing | 10:26 |
wwoods | more useful would just be spending more time triaging and recruiting/training more triagers | 10:26 |
poelcat | wwoods: i'll file a ticket with dkl's group to merge all the versions and change devel to rawhide... posting to fedora-devel first | 10:26 |
wwoods | poelcat: awesome, that'd be great. thank you. | 10:26 |
* poelcat was also wondering if we should put some bug days on the schedule | 10:27 | |
rdieter | yes! | 10:27 |
poelcat | plan them in advance | 10:27 |
wwoods | oh sure! | 10:27 |
wwoods | what day of the week would be best? | 10:28 |
poelcat | which would give us incentive to clean up bugzilla, get start page tweaked, and other howto file bugs docs cleaned up | 10:28 |
Lovechild | sounds way to sane.. everyone knows that frantically crying in the last minute is a far superior plan | 10:28 |
wwoods | and who can cover .eu / .au | 10:28 |
wwoods | by the way, the F8-thisweek bug link is in the topic for #fedora-qa: http://rdr.to/gc | 10:28 |
Lovechild | I'm .eu citizen, I guess that means I volunteer | 10:29 |
rdieter | frantic_crying: +1 :) | 10:29 |
wwoods | (407 new bugs on F8 this week.. weeeeee) | 10:29 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | Bug Days | 10:29 | |
rdieter | spin: more users -> more feedback/bugs. yay | 10:29 |
wwoods | indeed! | 10:30 |
Lovechild | yeah could be worse... could be zero bugs | 10:30 |
poelcat | fridays? | 10:30 |
wwoods | a lot of these bugs are simple things - nvidia (CLOSED CANTFIX), stuff on the CommonBugs page | 10:30 |
wwoods | bad CD burns, etc | 10:30 |
poelcat | not ever friday, but is friday a good day? | 10:30 |
wwoods | Friday's OK with me | 10:30 |
poelcat | how about first one on 30-NOV ? | 10:30 |
wwoods | I should do some metrics on bug reporting and figure out whether people do them over the weekend or during the week more | 10:31 |
wwoods | I should *also* figure out a way to keep score on bug triaging etc. like GNOME does | 10:31 |
f13 | Since we do snapshot releases on Fridays, do you want to do them on Monday? | 10:31 |
wwoods | f13: that's sensible | 10:32 |
poelcat | then we smack down the easy stuff right away | 10:32 |
f13 | gives people a chance to pick up the latest snapshot over the weekend and verify | 10:32 |
Lovechild | f13: that seems like a good idea, give people the weekend to download and burn the snapshot - if they hit bad bugs we are there to triage on mondays | 10:32 |
wwoods | yeah, my gut feeling is that bug reporting goes up on the weekends (and triaging goes down) | 10:33 |
poelcat | on the other hand friday i could pay more attention than on friday | 10:33 |
poelcat | than on monday | 10:33 |
wwoods | so Monday makes some sense | 10:33 |
Lovechild | unless you want to dedicate your weekend to Fedora as well :) | 10:33 |
poelcat | both sounds interesting, but probably too ambitious | 10:33 |
wwoods | let's start with Mondays | 10:34 |
wwoods | and if it really starts to pick up steam we can talk about adding Friday | 10:34 |
Lovechild | maybe this needs a nice little page telling people to download the snapshot over the weekend and please join us on IRC monday? | 10:35 |
wwoods | bug triage is an art, but it can be taught.. we need to create some teaching tools and stuff | 10:35 |
* poelcat votes for starting on 19-NOV | 10:35 | |
lmacken | wwoods: bugday! | 10:35 |
poelcat | wwoods: all we need is wiki pages to start | 10:35 |
wwoods | poelcat: indeed | 10:36 |
poelcat | wwoods: if you can send me the existing page URLs I'll include with my post about changing the versions in bz | 10:37 |
Lovechild | and a nice call for help on -test | 10:37 |
poelcat | and announce bug day at the same time | 10:37 |
wwoods | poelcat: existing pages for what, triage stuff? there's bugzapper stuff in the wiki | 10:37 |
wwoods | long-untouched | 10:37 |
* wwoods sad about that, but making amends | 10:37 | |
wwoods | Lovechild: definitely | 10:37 |
poelcat | wwoods: whatever makes sense to point people to in order to get started with bug triage... read up in advance | 10:37 |
wwoods | okay, quick vote: Bug Days on Mondays, starting 19-nov-2007 | 10:37 |
f13 | +1 | 10:38 |
lmacken | +1 | 10:38 |
rdieter | +1 | 10:38 |
Lovechild | +1 | 10:38 |
* wwoods +1, obvy | 10:38 | |
wwoods | okay, if no one is opposed..? | 10:38 |
poelcat | +1 | 10:38 |
wwoods | decided: Bug Days on Mondays, starting 19-nov-2007 | 10:39 |
lmacken | I think the coolest part about our last big bug day was that we had incentives/prizes | 10:39 |
wwoods | poelcat: http://fedoraproject.org/wiki/BugZappers is a good place to start | 10:39 |
wwoods | lmacken: which one was that? | 10:39 |
Lovechild | lmacken: bribing people.. excellent idea | 10:39 |
lmacken | The first one I think? Jack put it on. | 10:39 |
lmacken | 2 years ago | 10:39 |
poelcat | wwoods: what IRC channel will we hold it in? | 10:39 |
wwoods | But how did you measure performance? | 10:39 |
wwoods | poelcat: #fedora-qa, I think | 10:40 |
lmacken | bz activity :) | 10:40 |
lmacken | I just pinged jack to try and get more details | 10:40 |
lmacken | hopefully we can get him on board with it again | 10:40 |
wwoods | yeah, I'm curious about how you weight scoring for closing bugs vs. reassigning things to the proper places vs. other triaging stuff | 10:40 |
wwoods | I'd love to have an automated system watching that stuff and keeping score | 10:41 |
wwoods | once we get pretty good at keeping score we can start giving prizes | 10:41 |
wwoods | but then you have incentive for people to game the system and blecch | 10:42 |
wwoods | anyway, I'd rather have that problem to worry about than the "nobody triages bugs and everything sucks" problem | 10:42 |
wwoods | oh, quick diversion | 10:42 |
Lovechild | well I suspect it will be easy to just make a decision as to bug zapper of the week manually for the first while | 10:42 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | fedora-qa-list | 10:42 | |
wwoods | Lovechild: ooh, good point | 10:42 |
Lovechild | all this statistics crap is likely overkill for the first long time | 10:43 |
wwoods | I'm proposing (officially) that we close fedora-qa-list and move qa discussion to -test-list or -devel-list as appropriate | 10:43 |
wwoods | the spam:post ratio for -qa-list is something like 15:1 | 10:43 |
* wwoods filters all the spam. it ain't pretty | 10:43 | |
lmacken | I think we should kill the test update notifications as well.. or at least throw them somewhere other than test-list | 10:44 |
poelcat | lmacken: +1 | 10:44 |
lmacken | I'm planning on teaching bodhi about RSS feeds this week | 10:44 |
wwoods | yeah, agreed | 10:44 |
Lovechild | we can reopen the list if it's grows or the qa stuff drowns on the other lists? | 10:44 |
wwoods | Lovechild: absolutely | 10:44 |
wwoods | mostly it would just save me some maintenance/admin time | 10:44 |
poelcat | wwoods: can you simply disable it so it can be brought back if desired? | 10:44 |
Lovechild | I'm some what worried about the trade off in terms of requiring qa people to read high volume lists | 10:44 |
wwoods | poelcat: that's a good thought, I'll look into that | 10:45 |
wwoods | well, I think qa people should definitely be on -test-list | 10:45 |
wwoods | -devel-list is optional IMHO | 10:45 |
wwoods | if we can get the notifications off -test-list that would be even better | 10:45 |
Lovechild | I'm on both and keeping on top of it all is rather a big task | 10:45 |
wwoods | Lovechild: agreed | 10:45 |
-!- mefoster [n=mef@dhcp-110-104.inf.ed.ac.uk] has quit [Remote closed the connection] | 10:45 | |
wwoods | I skim the headers now and then but I generally don't read them in detail | 10:46 |
wwoods | FWN is a great help in this regard | 10:46 |
Lovechild | I imagine people with less time to waste than me would be dissuaded from doing QA by it | 10:46 |
-!- mefoster [n=mef@dhcp-110-104.inf.ed.ac.uk] has joined #fedora-meeting | 10:46 | |
f13 | oh yeah, does anybody think having testing update notifications go to test-list is a good idea? | 10:46 |
wwoods | Lovechild: do you think it would be reasonable if you were just on -test-list and the automatic notifications were moved? | 10:47 |
f13 | I think we can get them fed oout via rss instead. | 10:47 |
lmacken | RSS + anonymous feedback in bodhi | 10:47 |
wwoods | f13: I think having them go *somewhere* is a good idea, but -test-list isn't the place | 10:47 |
poelcat | send them to fedora-qa-list | 10:47 |
poelcat | ;-) | 10:47 |
wwoods | ha | 10:47 |
-!- mefoster [n=mef@dhcp-110-104.inf.ed.ac.uk] has quit [Remote closed the connection] | 10:47 | |
wwoods | yeah maybe I'll lock it down so only automated stuff can mail -qa-list | 10:47 |
Lovechild | the update messages really should go on -test so people can easily comment on them.. not that they seem to do so. | 10:48 |
wwoods | and we can move the notifications there | 10:48 |
-!- mefoster [n=mef@dhcp-110-104.inf.ed.ac.uk] has joined #fedora-meeting | 10:48 | |
Lovechild | but it's probably no worse than asking people to subscribe to a second mailing list.. using -test and -devel does have the upside of having greater visibility | 10:49 |
wwoods | yeah, I think the update notifications are just noise | 10:49 |
wwoods | esp. if we have anonymous commenting in bodhi | 10:49 |
f13 | yeah, I think the feedback needs to be done in bodhi, not the list | 10:49 |
lmacken | update feedback in bodhi, bugs in bugzilla.. then what is left for test-list? questions? | 10:50 |
wwoods | questions, discussion, planning | 10:50 |
lmacken | ah gotcha.. yeah, esp if qa-list is going away | 10:50 |
Lovechild | I like -test for early warning, basic bug confirmation | 10:50 |
wwoods | the *useful* stuff that goes on in -test-list these days | 10:51 |
wwoods | yeah | 10:51 |
wwoods | it's a good place for testers to be like "have you guys seen this?" | 10:51 |
wwoods | a future feature for triaging is going to be adding tags to the whiteboard field | 10:51 |
wwoods | so we can have an auto-updated page of Current Hot Bugs / Common Dupes / etc | 10:51 |
Lovechild | also having a list keeps the social aspect of QA intact which is always nice | 10:52 |
wwoods | yeah, the social aspect is important | 10:52 |
wwoods | so, yes, we'll keep -test-list as the qa discussion group | 10:52 |
Lovechild | I mean I wouldn't be doing QA if it wasn't fun and wwoods didn't boost my massively inflated ego occasionally | 10:53 |
wwoods | move update notifications to -qa-list or drop entirely? | 10:53 |
lmacken | +1 for dropping | 10:53 |
Lovechild | couldn't they be just an rss feed - seems more like the thing to do, encourage mildly couragous testers to run with updates-testing enabled | 10:53 |
wwoods | Lovechild: oh, there's no question about the RSS feed | 10:53 |
lmacken | RSS and `bodhi --testable` / `bodhi -s testing` should suffice | 10:54 |
wwoods | maybe we'll drop the update notifications when we get RSS support in bodhi? | 10:54 |
lmacken | sounds good | 10:54 |
lmacken | I'm planning to do that hopefully today or tomorrow | 10:54 |
lmacken | along with making it public | 10:54 |
wwoods | making bodhi public? rad. how long 'til anon commenting? or.. actually I guess we don't *need* that immediately | 10:55 |
wwoods | what group(s) do you need to be in to comment in bodhi? | 10:55 |
lmacken | there's a TurboGears captcha widget that i'm going to try and use | 10:55 |
wwoods | that'd be a good way of tracking who's in QA | 10:55 |
wwoods | ah nice | 10:55 |
wwoods | yeah, allowing anon commentary would be very good | 10:56 |
lmacken | and bodhi keeps people in the loop as well.. if you've commented on an update, you'll be notified of all other comments/changes | 10:56 |
wwoods | okay, so: shut -qa-list and stop update notifications on -test-list once we have RSS support in bodhi | 10:56 |
f13 | wwoods: sounds like a great Trac ticket set 9: | 10:56 |
f13 | (: | 10:56 |
f13 | wwoods: we have a rel-eng Trac now, filing a ticket for making those things happen (minus the email list shut down) would be awesome. | 10:57 |
wwoods | cool, will do | 10:58 |
wwoods | Oh! crud. I'm out of town next week - grandmother's memorial / thanksgiving | 10:59 |
wwoods | so I won't be around Monday for Bug Day | 10:59 |
Lovechild | I'm sure we can cover for you | 11:00 |
poelcat | wwoods: i'll be around | 11:00 |
wwoods | awesome | 11:00 |
wwoods | I'll try to pop in if I get some internets but it's not likely | 11:00 |
-!- sergiopr [n=sergiopr@halmax.fis.ucm.es] has joined #fedora-meeting | 11:00 | |
wwoods | okay. anything else? | 11:00 |
-!- wwoods changed the topic of #fedora-meeting to: Fedora QA Meeting | Open Floor | 11:00 | |
-!- clarkbw [i=clarkbw@nat/redhat/x-c1bbd3281ea4948e] has joined #fedora-meeting | 11:01 | |
lmacken | https://hosted.fedoraproject.org/projects/bodhi/wiki/CLI#Viewingwhattestingupdatesyouhaveinstalled | 11:02 |
lmacken | we should encourage people to use it! :) | 11:02 |
wwoods | Okay then! I'm gonna mail -test-list about development changes and Bug Day, and file a ticket about killing notifications on -test-list | 11:02 |
lmacken | easy way to see what you could be testing, and provide useful information to us | 11:02 |
wwoods | poelcat was going to talk to dkl about getting rid of Fntestn versions | 11:03 |
wwoods | (and we're not gonna use 'em in the future) | 11:03 |
wwoods | bug days are Mondays, starting Nov. 19 | 11:03 |
wwoods | we're closing -qa-list | 11:03 |
wwoods | I think that's all the decisions we made? | 11:03 |
f13 | wwoods: fwiw I think you need to run your bugzilla changes through FESCo | 11:04 |
wwoods | oh, and I guess we're officially endorsing the proposed changes? | 11:04 |
wwoods | f13: okay then | 11:04 |
poelcat | i think periodic bug days, but not every monday | 11:04 |
-!- ke4qqq [n=ke4qqq@64.89.94.194.nw.nuvox.net] has joined #fedora-meeting | 11:04 | |
Lovechild | indeed.. oh and can we finally get that ics calendar for qa activity? | 11:04 |
poelcat | Lovechild: yes, I can do those in taskjuggler | 11:04 |
poelcat | but I need items for the schedule :) | 11:04 |
wwoods | I think I had a google calendar at some point | 11:05 |
wwoods | poelcat: meetings on Wednesdays at 1500UTC, Bug Days.. let's say every other Monday, for now? | 11:05 |
poelcat | Lovechild: http://poelstra.fedorapeople.org/schedules/f9/f9.ics | 11:05 |
poelcat | wwoods: i was thinking announce one at a time to create some buzz | 11:05 |
wwoods | and then there's things like freezes and snapshot releases | 11:06 |
wwoods | poelcat: nice. yeah, let's do that. | 11:06 |
-!- spoleeba [n=one@fedora/Jef] has joined #fedora-meeting | 11:06 | |
wwoods | Okay then, I don't want to take any more of your time, so.. thanks folks! | 11:07 |
-!- wwoods changed the topic of #fedora-meeting to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel for meeting schedule | 11:07 | |
--- Log closed Wed Nov 14 11:07:52 2007 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!