15:00:13 #startmeeting oVirt weekly sync meeting 15:00:13 Meeting started Wed Nov 16 15:00:13 2011 UTC. The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:21 #meetingname oVirt Weekly sync meeting 15:00:21 The meeting name has been set to 'ovirt_weekly_sync_meeting' 15:00:29 #chair pmyers cctrieloff quaid 15:00:29 Current chairs: cctrieloff pmyers quaid rbergeron 15:00:33 * rbergeron looks to pass around chair-age 15:00:48 #chair aliguori mdday_ 15:00:48 Current chairs: aliguori cctrieloff mdday_ pmyers quaid rbergeron 15:01:07 rbergeron: hm, that means I need to pay attention doesn't it? 15:01:09 #topic Gathering people... who's here? 15:01:17 rbergeron: here 15:01:31 pmyers: well, it's IRC, so, I think we all expect a certain degree of multi-tasking here ;) 15:01:35 :) 15:01:35 hey ryan. 15:01:36 * mburns lurking 15:01:39 rbergeron: here 15:01:53 rbergeron, here 15:01:59 * mdday_ present 15:02:02 * mestery almost said "hero" instead of here ... 15:02:07 * smoser is still here as 'smoser' 15:02:17 here 15:02:22 here 15:02:23 here 15:02:26 here 15:02:45 here 15:02:53 #info pmyers, rharper, mburns, mestery, mdday_, smoser, rbergeron, jimjag, dannf, cctrieloff, bazulay, MarkBaker present 15:03:06 coolio. If anyone else shows up, meetbot will usually log people who said things at the bottom of the meeting notes. 15:03:15 Moving onwards! 15:03:17 #topic Agenda 15:03:20 present 15:03:42 * quaid is here 15:03:43 I had a few things on the agenda for today - (1) press release status, board vs. project-planning mailing lists, upcoming event planning 15:03:51 * aliguori is here 15:03:53 rbergeron: shall we gather topic for the meeting and then work them. 15:03:53 and last but not least, moving towards first release 15:04:02 If anyone else has something, speak now :) 15:04:03 I would also like to add: 15:04:13 * sgordon here 15:04:13 #info gargya, aliguori, quaid are also present and awesome. 15:04:24 1.) do we open the list up to non subscription posts 15:04:55 2.) ftp / repo setup, want to get that done so we can get it up this week 15:04:57 #info Topics for today include: press release status, board vs. project-planning mailing lists, upcoming event planning, moving towards first release, opening up mailing list to non-subcriber posts 15:05:15 #info Topics also include: ftp / repo setup status & progress 15:05:28 #info sgordon also present 15:05:30 3.) We need feedback on release date, from SUSE and Canonical 15:05:47 we agreed that we would work the release date around the 16th. 15:05:54 #info Topics also include: Feedback on release date from SUSE and Canonical - around 16th. 15:05:57 any other topics? 15:06:11 we expedited IBM's review of the press release and now the PR staff is wondering what's holding further review up 15:06:22 * aglitke is here 15:06:27 Doesn't look like it, but feel free to yelp at the end if you have another topic. 15:06:32 #topic Press release status 15:06:55 cctrieloff: do we know where this is at? Last week, we were still waiting on a few people, but i haven't heard any updates. 15:06:59 on the PR side, I believe we have them all except cisco/intel from my last update which was yesterday 15:07:19 #info Have all PR signoffs except Cisco / Intel (as of yesterday) 15:07:33 cctrieloff: Do we need people from those companies to continue poking their PR reps? 15:07:50 * rbergeron eyes mestery ;) 15:07:56 mestery: do you know where we are from your side? 15:08:29 rbergeron: IBM had some minor edits - did you see those, and are the good? 15:09:01 mdday_: yes all looked good, SUSE also picked out on a few good edits. 15:09:11 mdday_: I'm not actually in the loop on those edits (unless you sent them directly to me and I missed them, which has been known to happen occasionally) :) but it looks like Carl saw them. 15:09:23 kerri has taken all the edits and has sent back out to all the PR orgs. 15:09:26 cctrieloff, rbergeron, thanks 15:09:35 rbergeron: will there be a final draft released to all ? 15:09:41 #info Both IBM and SUSE provided minor edits, which Kerri has taken into account and submitted back to the PR orgs. 15:09:43 rbergeron: with the latest edits? 15:10:10 edits where basically turning it from a multi company release to a project release, which is good for optics but will have a little less coverage on the wire 15:10:17 rharper: would you be interested in asking a mail on-list about that? Kerri shoudl be able to answer that, and I think it's a good idea. 15:10:22 :D 15:10:26 rbergeron: sure 15:10:28 but she's not here at the moment 15:10:39 rharper: awesome. (plus, I can use the power of action here, so people can see how to use it) 15:10:56 #action rharper to ask on-list about the prospects of sending out a final draft of the press release to everyone. 15:10:59 :) 15:11:29 just got next action from cisco, I'll follow up. 15:11:43 #action cctrieloff has next action from cisco, and will follow up re: press release 15:11:50 cctrieloff: do you want to follow up with Intel as well? 15:12:08 * rbergeron looks through the list of attendees for intel folks 15:12:08 Kerri has that one under control I believe. I'll check with her. 15:12:18 #action cctrieloff to follow up with kerri on intel status 15:12:23 okay. I think that wraps that one up. 15:12:31 #topic Board vs. Project-planning list 15:12:38 Okay, so this is my personal question, I suppose: 15:12:53 Do we want to continue sending meeting notices to project-planning, or are we largely switching over to the board list? 15:13:04 Since we're more or less off the ground here. 15:13:06 I think board list should just obsolete project-planning 15:13:08 * rbergeron seeks feedback 15:13:14 kwade: is everyone from planning on teh board list? 15:13:27 quaid: ^^ 15:13:32 pmyers: as long as we can move the subjects that are not board@ to e.g. arch@ 15:13:37 ack 15:13:51 anyone else? I'm +1 to that. 15:13:58 cctrieloff: I presume so but it would take a brief manual check 15:14:03 where do we want to coordinate events etc, on board list? 15:14:16 cctrieloff: maybe even an events or marketing list would make sense for that? 15:14:23 not YAML :) 15:14:25 cctrieloff: exactly, is that board@ or really arch@? 15:14:26 With weekly report-out to the board? 15:14:31 how about we just do it on users@ or smth 15:14:45 doing on users is a great idea. 15:14:48 Okay. 15:14:55 as long as the users don't mind :) 15:14:59 +1 to users 15:15:01 well, not here to object! 15:15:04 #agreed board list obsoletes project-planning list for meeting invites, etc. 15:15:07 let's do that and sunset the planning list 15:15:16 #agreed event coordination to go to users@ list. 15:15:23 #agreed sunset the planning list 15:15:35 #action quaid to verify that all users on project-planning are on board@ list. 15:15:38 Kosher? 15:15:42 * rbergeron looks around for anything she missed 15:15:55 #info Sunset means - block new subs but leave archives etc. up 15:16:03 3, 2, 1 .... 15:16:08 quaid: thanks for the clarification :) 15:16:20 #topic Upcoming Event Planning 15:16:32 A few notes here - 15:16:50 #info chris wright noted on-list that FOSDEM has a track for cloud/virt-ish things, that may be an option. 15:16:53 I failed to authenticate to a running guestOS through VNC, though set the password by setVmTicket rdsClient command. Any thing I may have missed? 15:17:20 * rbergeron will be honest and say she's been sort of out of the loop for the past week on the events-planning-list stuff with Fedora release, but is getting caught up, so looking for any input here or anything people wnat to urgently point out 15:17:42 I think FOSDEM is one we should plan to put some energy into 15:17:45 #info SCALE CFP closes tomorrow, if anyone wants to present in SoCal in January. 15:17:56 cctrieloff: apevec will be attending, so he can give preso on oVirt Node if need be 15:17:58 cctrieloff: I agree, it's a huge conference 15:18:05 apevec: you get to do double duty if you go to FOSDEM! 15:18:28 pmyers: can you ask him to submit something. I can help arm him with material if needed 15:18:42 #action quaid can submit The General oVirt Talk to SCALE if no one else is going 15:18:43 cctrieloff: you just asked him, he's on channel ;) 15:18:54 meaning, i have other things to submit, but will also do this one if no one else can 15:18:56 pmyers: :-) 15:19:19 quaid: thanks for volunteering for SCALE. 15:19:19 cctrieloff: can you send me link for the 'main ovirt preso' that I would use for FUDCON preso? 15:19:22 honestly, the more people we have submit, the better - if we get 2 or 3 people able to talk about different things, at least if only one is accepted, then we can consolidate 15:19:39 let's do this, let's get list of people going added to the wiki with the planning for events 15:19:41 quaid: I'm sure Ilan can probably accommodate that as well, I know he's looking for tracks in that area 15:19:44 yeah. 15:19:51 I'll add a wiki page for event planning. 15:19:57 (unless there already is one) 15:19:59 cctrieloff: I should be on the wiki already for FudCon Blacksburg 15:20:01 rbergeron: there is 15:20:06 DUDE, y'all rock 15:20:07 pmyers: I think we need to work from and modify the posted one; probably a good users@ discussion to work that out :) 15:20:11 man, i'm behind 15:20:11 yes. 15:20:12 quaid: ping 15:20:15 right 15:20:17 oschreib: pong 15:20:21 what I want to know is 'where is the posted one' 15:20:32 I hate searching and I'm sure someone has the 'right link' to the 'right preso' :) 15:20:34 #link http://www.ovirt.org/2011/11/01/workshop-underway-1-to-3-nov/ 15:20:36 #action quaid, pmyers to add to events wiki page 15:20:40 So we think we should plan a day track at FOSDEM. We should also plan a day track at KVM forum. 15:20:48 pmyers: it's in that post currently 15:20:56 thx 15:20:59 #info Should consider adding a day track at FOSDEM, KVM Forum 15:21:21 quaid: I don't see it 15:21:25 I got a pile of presentations forwarded to me instead of loaded on to the wiki directly, so there is still a small bit of mess to sort out from those 15:21:27 i see presos specific to node, vdsm, reports, etc 15:21:31 but not a high level overview deck 15:21:34 maybe a wiki page with "THIS IS THE LATEST VERSION OF THE STANDARD PRESO" or something like that would be useful. 15:21:39 rbergeron: +100 15:21:40 pmyers: ha! how did that happen ... 15:21:56 I think we should have our 'main decks' on a very visible page 15:21:56 there is not yet a standard preso, I think, but we're nearly three 15:22:00 s/three/there/ 15:22:01 KVM forum should include a lot of oVirt presos 15:22:03 rather than buried in workshop pages 15:22:03 pmyers: agreed 15:22:22 ok, let's take the "fix up the presentations situation" off-meeting 15:22:24 Okay, so, who has the ball on the "high level overview standard presentation" and getting it out and visible and whatnot 15:22:32 quaid: do you want to drive that discussion onlist? 15:22:39 rbergeron: http://ovirt.org/wiki/Outreach 15:22:47 ok, is everyone we need on users@? 15:22:59 #action quaid to drive "The Standard Presentation" for oVirt and making it available onlist 15:23:07 quaid: reject if you don't wnat that ball, i'm just trying to move along ;) 15:23:24 quaid: I think we need to double check the overlap of project-planning and users@ 15:23:24 rbergeron: iheim should have such a preso available 15:23:38 rbergeron: right 15:23:47 I can help on std preo, however I have PTO next week so I might not be the fastest one this time to do it 15:23:51 rbergeron: I'll keep that action 15:23:59 #info iheim may have such a presentation available 15:24:01 Okay 15:24:06 * rbergeron is going to mooooooove onwards 15:24:23 #topic Moving towards first release 15:24:23 rbergeron: I just added 'attending' column to http://ovirt.org/wiki/Outreach#Schedule 15:24:40 cctrieloff: you mentioned earlier that you were still looking for agreement from SUSE & Canonical? 15:24:44 On a release date? 15:24:50 pmyers: you rock 15:25:30 agraf_: ^^ how is it coming? 15:25:34 rbergeron, I think we are owe a list of what we will do by when 15:25:58 rbergeron, cctrieloff in this case we = canonical 15:26:02 MarkBaker: who is owing you? :) 15:26:16 MarkBaker: ya 15:26:35 MarkBaker: thanks, do you have an idea of when is a reasonable time to pin the first release? 15:26:55 rbergeron, let me try that again: Canonical owes the project a list of what we will do by when 15:27:07 ahhhhh 15:27:08 I see 15:27:18 ack. any idea of reasonable date yet? 15:27:24 I thought you meant you were owed a list of "what you'd have to do" to make an estimate 15:27:51 cctrieloff, we have plans to create n Ubnu based oVirt Node, port VDSM to Ubuntu Server and work on the client pieces 15:28:20 great, that would be a great first release. 15:28:57 Post UDS we are working out the resourcing for this and a whole raft of other stuff so I think it will be a few days before we can provide an estimte of when we will get this done. 15:28:59 MarkBaker: maybe the thing to do would be to set up a wiki page that describes what your steps/plans are? and a timeline? 15:29:02 MarkBaker: will the Ubuntu based oVirt Node be just normal packaged Ubuntu w/ vdsm added? Or are you also pursuing the black-box style Node that we have for Fedora? 15:29:31 pmyers: i suspect it will be normally packaged, w/ that packaged version used for a black-box style node 15:29:33 FWIW we have meetings on Friday and Monday to finalise so should be able to give a mch better update next week 15:29:40 cctrieloff: quick note, back to idea of creating a track at FOSDEM. Too late apparently to create tracks 15:29:52 there is a 2-day general virt track though 15:30:02 pmyers, it will be a lightweight Ubuntu image in the style of the Fedora black box 15:30:10 so you can propose talks for that, and you can propose talks for the lightning talks track 15:30:13 MarkBaker: ok sounds great 15:30:43 #action Markbaker to finalise with an update next week; still in meetings/discussion for estimations 15:30:49 MarkBaker: does that sound about right? 15:30:58 rbergeron, that is fine 15:31:01 cool. 15:31:09 Maybe let me turn the question around. Do we think we can get a first release out before Christmas? Let's create a release page and see if we can get it in this year. Always good to work to a date. 15:31:21 we can finalize next week once we have all the data in. 15:31:31 +1 15:31:35 Does anyone want to follow up with agraf_ ? 15:31:42 one other fosdem nnote, you can also requeest a table for a project if you want, that's still open too 15:32:07 * rbergeron nods 15:32:18 rbergeron: are you able to request a table for us. 15:32:22 cctrieloff: do you want to make a release page? 15:32:51 cctrieloff: i can, but the likelihood of me *manning* the table is pretty low, unless someone wants to send me to europe and also bribe sdake into not strangling me :) 15:32:58 rbergeron: FOSDEM and let's mail the list with the deadline for presso's and get as many people to submit as possible 15:33:24 rbergeron: I'll find a way to send you :-) that is if you want to go... 15:33:49 #action rbergeron to investigate table for FOSDEM, start figuring out deadlines for presetnations for various conferences 15:33:58 okay, back to releases 15:33:59 rbergeron: cctrieloff: do you want to make a release page? -- I think we should elect a release manager. 15:34:02 * rbergeron tries to keep the train on the tracks 15:34:18 * cdub agrees re: release manager 15:34:24 hey, cdub :) 15:34:33 hiya! 15:34:42 I think two actions from release: 15:34:53 * rbergeron nods 15:34:56 1.) create a release page for working release 15:35:14 2.) send mail to board and arch and to elect the release manager 15:35:33 I think that's fair. 15:35:43 rbergeron: hrm? 15:35:46 * rbergeron looks for other thoughts / agreement 15:36:18 oh, up there 15:36:24 agraf_: HAI ;) we were looking for feedback on SUSE & release schedule stf 15:36:26 stuff 15:36:30 * rbergeron slaps around her keyboard 15:36:52 cctrieloff: release manager is global but for overall oVirt umbrella releases right? 15:36:53 rbergeron: heh, yeah, so we have the engine working and vdsm packaged and responding 15:36:57 rbergeron: can't create VMs yet though 15:37:02 each subproject still can release on own cadence and with own process? 15:37:07 rbergeron: and don't have all the infrastructure stuff up yet 15:37:14 agraf_: yar, that's next in the agenda :) 15:37:29 pmyers: +1 to those definitions, fwiw :) 15:37:29 rbergeron: I'd assume we need at least 2 weeks to get anything working together 15:37:49 pmyers: global: i.e. coordinate the release, i.e. decide when it is done, bug people for build projects etc / sign of for each distro etc etc 15:37:50 maybe have one release person for each project, then they work together for overall release 15:37:56 rbergeron: but we're meeting in 20 minutes about ovirt after which i can tell you more details on what people think how long it'd take to get something opensuse based out 15:37:56 cctrieloff: +1 15:38:05 mburns: +1 as well 15:38:08 ahhh 15:38:23 each subproject should have a named person responsible for coordinating w/ global release mgr 15:38:36 features and a wrangler! ;) 15:38:44 probably a backup/secondary person for global manager 15:39:30 agraf_: are one or a few of you on infra@ovirt.org mailing list? 15:39:43 quaid: good question 15:40:01 quaid: I don't know tbh 15:40:02 agraf_: would appreciate input on how we do e.g. the repo directories, and that's an open topic atm 15:40:10 let's take the release date to the list (and work the waht needs to be done and hopefully agree we get it out before christmas) 15:40:12 okay, let's come to a conclusion here: Does someone wnant to write up a proposal to the list for release manager stuff, and how we think it should work, and hold it open for a day or two for comment before coming to a conclusion? 15:40:16 And release date stuff as well? 15:40:40 +1 to $someone 15:40:40 cctrieloff: do you want to work the release date discussion? and maybe pmyers the release manager discussion? 15:40:43 Or anyone? 15:40:44 and take the election of the global release manager to the list also, then each project can pick their coordinator. 15:40:50 * rbergeron looks for non-rht folks to volunteer 15:41:06 just to spread the love:D 15:41:39 anyone? :) 15:41:47 * rbergeron looks in her bag of cookies 15:41:48 someone that knows the code / impacts for the first one is fine, and then we rotate the position. 15:41:48 rbergeron: happy to start release mgr discussion unless someone else wants it 15:42:05 can you please elaborate a bit about the role of this global release manager ? 15:42:05 put it to the list so those not in teh meeting can also volenteer 15:42:13 #action pmyers to start release manager discussion onlist 15:42:14 cctrieloff: +1 15:42:18 rbergeron: which list? 15:42:20 board? 15:42:25 arch 15:42:28 ack 15:42:39 #action cctrieloff to take release date discussion to list (arch@ list, release manager discussion on arch@ list as well) 15:42:41 or arch and board is fine 15:42:42 * mdday_ will work off-line to see if someone from IBM can do this 15:42:44 :D 15:42:57 mdday_: thanks 15:43:01 cctrieloff: ^^ ? 15:43:12 #action mdday_ to work off-line to see if someone from IBM can do this (release manager) 15:43:37 okay, we have two more topics 15:43:48 #topic Opening up mailing list(s) to non-subscriber posts 15:43:51 Thoughts? 15:44:00 um 15:44:02 I replied on that topic 15:44:10 just so folks are aware of the greater extent of the inbound spam 15:44:12 quaid: yes, but carl added it as an agenda topic :) 15:44:18 i.e. lots and growing 15:44:28 quaid: dor indicated qemu lists did not have spam issue 15:44:33 rbergeron: sure, my reply was coincident, just referencing :) 15:44:35 why would we be worse off than that list? :) 15:44:40 pmyers: perhaps they have spam filters that work? 15:44:42 quaid: maybe we need to do some blacklisting 15:44:46 What I have been doing on teh lists I moderate is if I get a real post, I auto-subscribe the person. 15:44:47 quaid: so let's get those filters :) 15:44:59 cctrieloff: or add that person to the recipient filters 15:45:00 cctrieloff: that works fine as well 15:45:09 I usually at least add it to the okay-to-post list. 15:45:14 pmyers: we need someone to volunteer to make that happen :) 15:45:17 we are getting about ~30 spam messages a day already to the lists I moderate, so no keen on opening them up 15:45:27 ouch 15:45:29 yeah, it's ugly 15:45:29 i.e. -1 to open lists if it means I have to setup spam filters :) 15:45:30 didn't realize it was that bad 15:45:34 sure, but moderating them will get harder 15:45:38 so you need some filters 15:45:50 how often do we get non-list people sending important messages? 15:45:51 the best way I know of filtering spam is forwarding all email to gmail and then forward back from there and accepting only from the known gmail account :) 15:46:00 quaid: cross posts generate a lot of that 15:46:06 over time people will realize they need to subscribe 15:46:10 abaron_wfh: +1 :) 15:46:14 pmyers: I agree with cctrieloff that people should be sub'd if they want to discuss 15:46:19 they will, but there is always some 15:46:19 so they can see the replies 15:46:20 that is what I've seen with the ASF lists I moderate 15:46:25 or someone has a one off request for say infra 15:46:29 and doesnt want to subscribe 15:46:34 quaid - the first email by any person is before they register. like carl, i auto approve them for future emails even if they don't subscribe 15:46:44 sgordon: that's what the moderator queue is for 15:46:53 In 6 months time, we can turn the lists to auto reject and stop moderating 15:47:02 they don't have to subscribe, just need moderator to ack them as senders for their first email 15:47:03 quaid, yes but i was responding to the comment that over time people learn to subscribe 15:47:09 sgordon: and people should know that lists tend NOT to accept non-subscribers posts, anyway, so relying upon moderators is a fool's quest 15:47:17 quaid, they should but they dont 15:47:26 we still get mails on fedora-docs from people who are unsubbed 15:47:34 and it's been around for how many years? 15:47:37 * rbergeron nods 15:47:45 well, in today's world, we can't spend all our time moderating for the few who refuse to subscribe to their own discussions. 15:47:45 same for cloud list @ fp.o 15:47:52 quaid, again that is why you need filters 15:47:55 and then just open it 15:48:08 sgordon: so you are volunteering for that? :) 15:48:18 okay, why don't we do this: get filters (need volunteer), give it a trial run, and if it's too much spam, turn it off? 15:48:22 i believe someone else suggested it ;) 15:48:24 I'm concerned that our infra is already pretty streteched 15:48:45 not that we don't have enough hands (we don't, but that's not the problem), it's that we need a few more weeks of getting organized 15:48:47 well who is adminning the mailman instance? 15:49:00 me 15:49:02 me 15:49:02 what's the big deal with moderator automatically subscribing anyone who sends a valid email and is not subd? 15:49:02 and now oschreib 15:49:15 abaron_wfh: +1 or just add to recipient filter 15:49:18 abaron_wfh: that is what I do 15:49:27 abaron_wfh: that you have to filter through every spam mail to see if it's kosher.... is sometimes painful 15:49:40 sgordon: but we just added oschreib, he and I haven't worked together before, so we're figuring out all the details still on infra@ 15:49:52 so if the consensus is what rbergeron suggested, we need a few weeks to get to that 15:49:56 by painful i mean, "need to keep on top of it, and god forbid if you go on vacation" 15:49:58 rbergeron: this did not come from the moderators, they haven't complained yet. 15:50:01 rbergeron: abaron_wfh: I don't spam comes in batches, so anything in bacthes I toss. 15:50:07 abaron_wfh, yet ;) 15:50:22 sgordon: I'm a moderator 15:50:29 it's usually not the moderators that complain, it's the one person whose mail didn't get seen/passed through :) 15:51:00 we can also just add a few more moderators if people want to volenteer. and then track and see how it goes. 15:51:12 cctrieloff: +1 15:51:17 cctrieloff: +1 from me as well 15:51:18 i think that sounds reasonable 15:51:40 #agreed add more moderators to help spread the load of approving mails nd see how it goes 15:51:59 quaid: do you want to spam (haha) the lists to see if anyone wnats to volunteer as a moderator? 15:52:08 or sgordon? 15:52:09 #action Infra team will continue to study spam filter solutions 15:52:19 +1 to sgordon 15:52:21 sure i am happy to do that 15:52:23 people are tired of seeing my email 15:52:33 which list, board? 15:52:43 #actoin sgordon to ask lists for additional moderation volunteers 15:52:45 arch@ at least 15:52:50 * mestery doesn't think anyone is tired of seeing email from quaid. 15:52:55 that's the cross-project discussion list 15:53:06 #action sgordon to ask lists for additional moderation volunteers (to arch@ list) 15:53:15 mestery: yeah, but if I'm always asking for stuff, people learn to leave my emails to read until later :) 15:53:22 Okay, moving on! 15:53:42 #topic FTP / Repo Setup status 15:53:48 I think this is the last agenda item 15:53:51 rbergeron: I'm willing to moderate arch 15:54:12 abaron_wfh: can you get with quaid on that? :) 15:54:28 cctrieloff: do you have any comments re: ftp/repo setup status 15:54:35 do we have general agreement on the proposal from quaid on FTP setup? 15:54:41 nearly I think 15:54:44 the setup is just a few minutes 15:54:48 but I wanted to get the details right 15:55:00 cctrieloff: I'd like to hear from different distros, though 15:55:26 #action quaid to ask someone from SUSE and Canonical to comment about the repo setup details 15:55:33 I think calling it repo and the add dir for repo/nightly repo/release etc etc 15:55:40 cctrieloff: not repo 15:55:46 repo is specific to format of packages 15:55:54 agraf_: MarkBaker dannf : http://lists.ovirt.org/pipermail/infra/2011-November/000096.html 15:55:54 mburns had suggestion for alternate name 15:56:00 * mburns said release 15:56:01 but otherwise +1 to quaid's plan 15:56:04 agraf_: MarkBaker: ^^ 15:56:13 how about releases/repo/foo 15:56:16 quaid: +1 15:56:17 so releases/nightly 15:56:22 releases/? 15:56:25 so in releases/ is repo/ and version/ and nightly/ etc. 15:56:34 repo should be further down 15:56:44 as the type of repo likely depends on distribution 15:56:53 * rbergeron notes that she has to step away for about 3 minutes, if someone wants ot handle actioning and agreeing and so forth 15:56:56 ok, so we DON'T have consensus :) 15:57:08 well we have consensus on top level i think 15:57:11 releases/ 15:57:14 sgordon: right, so what is the structure that is generic at the top, then customizable as you get in to it? 15:57:15 releases/nightly 15:57:18 yeah 15:57:21 are we able to get consensus on IRC now.. 15:57:24 sgordon: +1 agreed, consensus on that 15:57:32 so it might for example end up being releases/1.0/fedora/ 15:57:35 just for example 15:57:39 but we can flesh that out later 15:57:48 +1 15:57:49 so let's drop the repo word 15:57:55 /releases and /releases/nightly would get us started 15:57:56 it's not needed,it's just a yum convention 15:58:19 ok, so I think we're back to what mburns suggested 15:58:22 we still need to iron out internally, but i suspect canonical will use a ppa in launchpad 15:58:23 so we definitely need another repo for Ubuntu pieces 15:58:24 so we just need links 15:58:34 dannf: yep 15:58:57 do we have anyone from SuSE handy? 15:59:04 dannf: ok, but it would be good to have something there in case people are going through the directory tree; maybe at the minimum README.Ubuntu 15:59:28 rbergeron: I'll take the chair of the meeting from here 15:59:30 agraf_: any feedback on FTP structure for SUSE 15:59:53 ok, i can finish up with him after the meeting 16:00:00 we are nearly agreed :) 16:00:03 yeah, a readme sounds reasonable 16:00:10 quaid, README.ubuntu makes sense. 16:01:08 ok, I still have the action to follow-up with agraf_ et al, so will do so today soonest 16:01:22 then we'll get the directory and yum repo done by COB my time 16:01:36 anything else on this topic for now? 16:01:45 otherwise, the thread is still open on list for the moment. 16:02:01 * rbergeron returns 16:02:21 and if that's it, we're about to be done 16:02:35 awesome, i'm just in time 16:02:36 LOL 16:02:38 #topic Final closing bits ... 16:02:46 anyone have anything final before we close the meeting? 16:03:24 looks like we are done 16:03:31 I'm good 16:03:37 Thanks everyone for coming :) 16:03:40 nothing here 16:03:48 * rbergeron will ship out meeting logs 16:04:04 and ... 16:04:05 3... 16:04:07 2... 16:04:13 * rbergeron eats a slice of delicious bacon 16:04:16 ....1. 16:04:16 rbergeron: Error: "...1." is not a valid command. 16:04:22 OH, NOW. 16:04:27 #endmeeting