January 2014 - meetingminutes - Fedora mailing-lists

Summary of yesterday's (1/15/2014) cloud WG meeting
by Sam Kottler 16 Jan '14

16 Jan '14

Thanks everyone who was able to make it to the meeting yesterday! For those who weren't able to make it, here are few important links: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeting… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeting… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeting… Log (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeting… Here's a summary of the meeting (link to the HTML and text versions above): 17:01:57 <samkottler> #startmeeting cloud WG weekly meeting 17:01:57 <zodbot> Meeting started Wed Jan 15 17:01:57 2014 UTC. The chair is samkottler. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:57 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:02:08 <jzb> howdy 17:02:25 <samkottler> #chair rbergeron mattdm number80 geppetto jzb 17:02:25 <zodbot> Current chairs: geppetto jzb mattdm number80 rbergeron samkottler 17:02:45 <samkottler> welcome to 2014's first official meeting :-) 17:02:58 * samkottler wonders if special guest davidstrauss is gonna join us 17:03:30 <samkottler> #topic rollcall 17:03:45 <jzb> jzb is here 17:03:48 <samkottler> \o/ 17:03:53 <number80> .fasinfo hguemar 17:03:55 <zodbot> number80: User: hguemar, Name: HaÃ¯kel GuÃ©mar, email: karlthered(a)gmail.com, Creation: 2006-07-18, IRC Nick: number80, Timezone: Europe/Paris, Locale: en, GPG key ID: 41CF9CEA, Status: active 17:03:58 <zodbot> number80: Approved Groups: +packager cla_fedora cla_done fedorabugs ambassadors cla_fpca gitbeefymiracle 17:03:59 <samkottler> .hellowmynameis skottler 17:04:04 <samkottler> .hellomynameis skottler 17:04:06 <zodbot> samkottler: skottler 'Sam Kottler' <skottler(a)redhat.com> 17:04:11 * samkottler struggles 17:04:22 <jzb> .hellomynameis jzb 17:04:22 <mattdm> .fasinfo mattdm 17:04:27 <zodbot> jzb: jzb 'Joe Brockmeier' <jzb(a)zonker.net> 17:04:30 <zodbot> mattdm: User: mattdm, Name: Matthew Miller, email: mattdm(a)mattdm.org, Creation: 2005-04-13, IRC Nick: mattdm, Timezone: US/Eastern, Locale: en, GPG key ID: 72CF3A1B, Status: active 17:04:33 <zodbot> mattdm: Approved Groups: @gitdockerfiles gitspin-kickstarts +gitspins @gitcloud-image-service fi-apprentice gitcloud-kickstarts cla_done fedorabugs packager ambassadors cla_fedora cla_fpca 17:04:41 <jzb> hey! finally found a way to get it to limit to matching my username... 17:05:05 <number80> i didn't knew that command too :) 17:05:29 <rbergeron> .hellomynameis slim_shady 17:05:31 <zodbot> rbergeron: Sorry, but you don't exist 17:05:32 <geppetto> .hellomynameis geppetto 17:05:35 <rbergeron> darnit 17:05:37 <zodbot> geppetto: Sorry, but you don't exist 17:05:42 <geppetto> cool :) 17:05:44 <mattdm> lol 17:05:49 <sgallagh> geppetto: Has to be your FAS ID 17:06:04 <samkottler> this meeting has entered the land of meta 17:06:08 <sgallagh> .hellomynameis sgallagh 17:06:10 <zodbot> sgallagh: sgallagh 'Stephen Gallagher' <sgallagh(a)redhat.com> 17:06:19 <geppetto> .hellomynameis james 17:06:21 <zodbot> geppetto: james 'James Antill' <james.antill(a)redhat.com> 17:07:14 <samkottler> #topic PRD update and pending issues 17:07:23 <samkottler> it's due on the 20th 17:07:38 <mattdm> it's looking a lot better than it was a week ago! 17:07:39 <samkottler> and there are still some things we need to talk with the server WG about, sgallagh is here so maybe we should do that now? 17:07:55 <samkottler> yep, it's definitely shaping up 17:08:02 <samkottler> I've been trying to spend an hour or so per day on it 17:08:14 <mattdm> awesome. 17:08:42 <mattdm> I'm for starting with talking iwth sgallagh re server/cloud 17:08:48 * number80 gives a kudos to samkottler 17:08:51 <samkottler> we need to figure out the features we're gonna support 17:09:12 <samkottler> the use cases are mostly done, which was a big hurdle 17:10:01 <rbergeron> features to support or features to enable to enable the .. use cases 17:10:02 <mattdm> Do we want to try to hash out some specific thigns while we have everyone here 17:10:11 <mattdm> or should we look at some of the bigger picture things? 17:10:26 <samkottler> rbergeron: yes 17:10:35 <rbergeron> i'm not opposed, though it might be useful to know if any of those things are influenced by the server-ish stuff sgallagh is here for? 17:10:36 <samkottler> both 17:10:49 <samkottler> yeah, let's talk to sgallagh first :-) 17:10:55 <mattdm> sgallagh go! 17:10:57 * sgallagh feels honored 17:11:34 <number80> go sgallagh // right syntax 17:11:39 <sgallagh> The Server WG had its hopefully-final PRD meeting yesterday. We invited jzb and number80 to represent Cloud interests 17:11:59 * sgallagh really wants to make a Zork joke right now 17:12:46 <jzb> sgallagh: what's stopping you? 17:13:19 <sgallagh> I'm stuck in a maze of twisty cubicles, all alike... 17:13:51 <sgallagh> Ok, so there was a lot of discussion yesterday about where the dividing line is for things like OpenStack and OpenShift 17:15:15 <mattdm> I think that right now at least, cloud is focused on guest images and excludes openstack execution nodes 17:15:25 <sgallagh> that was our sense as well 17:15:39 <mattdm> that might change in the future, but leaves "runs in virt" as a common thread 17:15:58 <sgallagh> we proposed that OpenStack nodes should be a Server Role, possibly contributed by this group 17:16:17 <sgallagh> but "owned" by server 17:16:39 <samkottler> I think that's always been the assumption 17:16:48 <samkottler> the hypervisor'ish stuff would be owned by server 17:17:03 <mattdm> any dissent? speak now. :) 17:17:32 <sgallagh> That's been my assumption, but there was a lot of discussion about it yesterday 17:18:09 <sgallagh> It's also ambiguous where "managing an OpenShift deployment" belongs. 17:18:10 <jzb> sgallagh: more or less, though I sort of envisoned OpenStack nodes as closer to the server side than cloud side. 17:18:39 <sgallagh> jzb: I agree, but it's fair to say that the implementation will need to involve Cloud heavily 17:18:53 <jzb> sgallagh: indeed 17:19:15 <mattdm> I thik there's room to have some overlap. You can do e.g., a web server or web application in _either_ a cloud paradigm (<-bingo!) or the traditional server way. 17:19:22 <sgallagh> Why don't we turn the conversation around a bit. I had jzb and number80 in our meeting to answer our questions. Why don't you raise your own for us. 17:19:32 <jzb> yay! 17:19:38 * jzb tries to think of a stumper 17:20:05 <sgallagh> Where do you guys see ambiguity in our missions? 17:20:08 <rbergeron> ask something about configuration management or orchestration tools :) 17:20:19 <jzb> that is a good Q 17:20:28 <sgallagh> rbergeron: Config management is clearly in our laps 17:20:51 <sgallagh> "Orchestration tools" is a harder question 17:21:09 <rbergeron> I think the biggest source of ambiguity is that people equate "openstack" (and all the others) with cloud and i can see how that might be cause for misdirected questions. 17:21:09 <mattdm> sgallagh I think some of the ambiguity is that we're both doing "here's a base thing which can be adapted for different roles". 17:21:12 <samkottler> stuff like mesos blurs the lines 17:21:16 <sgallagh> We've got a use case for orchestration of containers, but that's not a complete answer 17:21:17 <mattdm> rbergeron that too 17:21:38 <mattdm> for server, it's the base platform plus application stacks 17:21:46 <mattdm> for cloud it's... well, possibly the same thing. 17:21:47 <sgallagh> "Server Roles" 17:22:26 <rbergeron> Logging? Things like checkpoint/restore? Storage (gluster or other cloud-ish storage)? Are we going to try and ... match up where we can on things? Or... "you can go your own wayyyyyyyyyyyy" 17:23:13 <sgallagh> logging is a much more complex question than a single word. 17:23:25 <samkottler> I think we can safely draw the line at 'do you need this thing on a physical machine' 17:23:32 <samkottler> logging is a yes and storage is a yes 17:23:35 <sgallagh> Checkpoint/restore is probably not all that useful to Cloud images, since you're aiming for mostly-disposable anyway, yes? 17:23:37 <samkottler> at least in my view 17:23:47 <mattdm> sgallagh right 17:23:50 <samkottler> yeah 17:24:01 <jzb> samkottler: if the users are doing it right 17:24:01 <mattdm> I think we want to keep the line more at cattle/pets than hw/virt 17:24:01 <rbergeron> sgallagh: processes running and such? i don't know 17:24:09 <samkottler> although people run stuff like...database servers in the cloud, too 17:24:10 <rbergeron> moving vm's and such 17:24:10 <jzb> sorry that was for sgallagh 17:24:26 <jzb> sgallagh: from working on CloudStack, I found a lot of questions around snapshotting/restore. 17:24:50 <samkottler> people do care about their instances being easy to restore 17:24:54 <number80> (sorry, got disturbed by coworkers) 17:24:59 <jzb> sgallagh: it's also used a lot to create a golden image. Spin one up, modify, then snapshot -> template 17:25:04 <samkottler> even just from a convenience perspective 17:25:13 <samkottler> jzb: :/ but yeah, common 17:25:34 <mattdm> but we expect the cloud env to hande that, right? 17:25:40 <jzb> in other words, ideally, no - we generally not care. In the real world, we do. 17:25:44 <jzb> mattdm: yes. 17:25:48 <samkottler> it's a hypervisor thing anyhow 17:26:09 <number80> yup 17:26:10 <jzb> samkottler: it's a hz thing except that the IaaS exposes the hz features. 17:26:17 <sgallagh> I'm not sure the PRDs need to be exhaustive either 17:26:26 <rbergeron> jzb: ah, that's a dandy point there 17:26:33 <sgallagh> It's probably worth noting that individual implementation goals can be solved through collaboration 17:27:04 <samkottler> jzb: like in the case where a guest requests a snapshot of itself? 17:27:14 <sgallagh> I'm not sure it's sensible or feasible to enumerate every possible aspect of the implementation. 17:27:30 * rbergeron needs to snapshot/restore her soda. where did it disappear to? ugh 17:27:39 <jzb> samkottler: I was thinking when a user uses the API or UI to create one. 17:27:53 <rbergeron> sgallagh: just trying to make sure we're not missing anything significant in overlap so just suggesting All The Things 17:27:54 <sgallagh> I view "ownership" of these areas as more of shepherding than dictating. 17:27:57 <samkottler> let's move on with the general understanding of were the line stands 17:27:59 <jzb> samkottler: again, I ran into a lot of users who basically used the IaaS as Advanced Virtualization 17:27:59 <mattdm> sgallagh +1 17:28:03 <number80> sgallagh: +1 17:28:06 <jzb> sgallagh: +1 17:28:45 <mattdm> If we can do it without confusion, I would like to steer users who are interested in IaaS-as-server-in-the-sky towards using Fedora Server rather than the cloud image 17:28:52 <sgallagh> I'm sure as hell not going to make a decision on a major change to hypervisor tech without consulting this team, for example. 17:28:52 <mattdm> but that might be hard to message. 17:28:57 <samkottler> do we want to do a vote on the line or just move forward with everyone in agreement? 17:29:21 <jzb> mattdm: I always looked at it as, they can start using the tool the wrong way and learn to do it right 17:29:21 <sgallagh> Just as one more aside: 17:29:36 <sgallagh> One thing that came up yesterday that I'd like to have buy-in from both sides is this: 17:29:38 <jzb> mattdm: so if they adopt OpenStack/CloudStack/Euca, it makes it easier to learn the right habits eventually. 17:30:09 <sgallagh> We need to share a "Universe" package repository, so that if someone installs the base cloud image, they will be able to "yum install fedora-server-release" and have any and all capabilities that Server offers (such as Roles) 17:30:46 <sgallagh> The subtext being: we are not producing disparate Fedora repositories (excepting the install media) 17:31:02 <mattdm> Okay, that's an interesting one. Maybe we should make that explicit in the PRD? 17:31:03 <number80> separate repositories would only make things worse (think RPM hell dependencies) 17:31:18 <mattdm> I mean, yes, I think there needs to be a universal repo 17:31:33 <mattdm> the question is: is going from cloud base -> server an expected normal path? 17:31:35 <geppetto> sgallagh: So is the intention that people can/will be able to install multiple *-release packages? 17:31:35 <jzb> sgallagh: as yesterday, agreed 17:31:52 <jzb> sgallagh: I think there may have been some accidental FUD that the idea of separate repos even surfaced. 17:31:53 <mattdm> what about the other way around? (I think it might be okay to define this as a one-way path) 17:31:55 <sgallagh> geppetto: I don't want to make a general statement on that. 17:32:14 <sgallagh> I'm fine with "Cloud can become Server" and not the reverse (or Server->Workstation, etc.) 17:32:14 <mattdm> you can adopt one of your cattle as a pet. but you can't really send your kitty out to live in the herd. 17:32:40 <sgallagh> mattdm: My parents told me they sent my dog to the farm. Are you telling me they lied? 17:33:24 <sgallagh> jzb: Right, but the separate repos is related, but not the whole statement I was just making. 17:33:36 <geppetto> sgallagh: Why not server => cloud? 17:33:56 <jzb> mattdm: my cats agree 17:34:11 <samkottler> server to cloud makes perfect sense IMO 17:34:12 <sgallagh> geppetto: I'm not ruling it out. But I don't know if I see obvious value there, unless I misunderstand your target 17:34:18 <rbergeron> i may be confused here - i sort thought people were like 17:34:20 <rbergeron> moving from the server 17:34:21 <rbergeron> to the cloud 17:34:34 <samkottler> rbergeron: well the intermediate is just taking a server and putting it on kvm/xen 17:34:43 <rbergeron> samkottler: right, babysteps 17:34:58 * samkottler thinks a server to cloud path is necessary 17:35:03 <sgallagh> My initial statement was merely this: You want to virtualize/containerize/stick in public IaaS some of your critical infra. 17:35:09 <samkottler> which basically involves virtio drivers, cloud-init, whatever else 17:35:25 <number80> sgallagh: you mean having a p2v like tool ? 17:35:29 <sgallagh> You can spin up the Amazon Fedora Cloud instance and then easily make that become a Server instance with the frameworks we provide 17:35:48 <sgallagh> number80: Really not talking that level of detail at the moment. 17:36:10 <number80> ok 17:36:14 <mattdm> this is traditional server -> server-in-the-sky. that's fine, but server-in-the-sky isn't necessarily Fedora Cloud 17:36:17 <mattdm> is my thinking. 17:36:18 <sgallagh> Merely that a machine (virtual or not) installed from the Cloud Image can *become* a "full" Server install simply through yum/dnf/packagekit 17:36:45 <mattdm> in order to really migrate to take advantage of cloud computing, you rearchitect. 17:37:01 <number80> my POV is that fedora-cloud is basically a trimmed-down image on which you can install whatever "role" you wish too 17:37:12 <sgallagh> mattdm: Well, no matter what, you'll still probably want a fairly traditional Domain Controller and DNS environment 17:37:18 <sgallagh> But that's a different discussion 17:37:47 <jzb> number80: agreed, but there may also be roles that make sense only in the cloud. 17:37:49 <mattdm> number80 and Fedora Cloud provides some cloud-computing-focused roles, and a way to go to fedora server for roles that aren't necessarily covered but still always useful 17:37:59 <number80> jzb: +1 17:38:29 <samkottler> so assuming here's a universe what makes so directly separating the roles necessary? 17:38:53 <samkottler> I guess my disconnect is why I wouldn't say...install freeipa on a cloud instance just like I would on a regular box in a DC 17:39:25 <sgallagh> samkottler: You can. But we're (Server) going to be doing some additional packaging work to make role deployment simpler 17:39:25 <mattdm> okay, so: do we want to tie this more closely together and share the roles? 17:39:38 <sgallagh> But it's going to require additional infrastructure that you may or may not want. 17:39:52 <samkottler> sgallagh: ah okay that makes more sense now 17:40:15 <samkottler> so it'd basically expose comps to you or something? 17:40:22 <samkottler> whatever, I get the point, no need to dive so deep 17:40:26 <rbergeron> what are the pieces of a "role" exactly? 17:40:32 <rbergeron> wait, i'm slower than samkottler 17:40:33 <sgallagh> samkottler: Things like interaction with the Cockpit Project so that you could deploy the role with minimal interaction (just answer three questions and go) 17:40:36 <rbergeron> (obviously) 17:40:59 <rbergeron> is a role == set of packages known to work in a specific way? 17:41:05 <rbergeron> together to do something? 17:41:11 <sgallagh> rbergeron: Essentially yes. 17:41:22 <sgallagh> Though our definition of "set of packages" is currently intentionally vague 17:41:42 <sgallagh> Because people get hung up on packaging==rpm 17:41:56 <rbergeron> how does it overlap with something like ... heat templates 17:42:07 <sgallagh> FYI: https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_Doc… 17:42:12 <jzb> sgallagh: role == software required for a specific task? 17:42:22 <sgallagh> jzb: That's a better description, yes 17:42:36 <rbergeron> or .. docker containers for various pieces of things 17:42:43 <samkottler> rbergeron: it wouldn't orchestrate across-server stuff 17:42:50 <samkottler> just on a single node 17:42:57 <sgallagh> rbergeron: docker containers is one possible packaging implementation (and is being considered) 17:43:58 <rbergeron> samkottler: yeah, but i am just wondering about how to make the "known templating things" out there - which are basically all defining roles of some sort, just implementing them in ways where they can (or can't) be auto-magically scaled 17:44:46 <rbergeron> the perennial wordpress example - do we want a wordpress role (if that's what we're sort of thinking) to look the same as a heat template for wordpress, etc 17:44:49 <samkottler> rbergeron: wouldn't that be closer to config management's realm? 17:44:51 <rbergeron> or not really concerned with that at that point 17:45:10 <rbergeron> samkottler: "best tool for the job" - people are gonna do it however they want :) 17:45:32 <samkottler> I guess separating cfg mgmt from one-time ops isn't really something that you do in say...docker land 17:45:40 <sgallagh> rbergeron: Wordpress is probably not the sort of Role we'd (Server) be most interested in. 17:46:09 <sgallagh> From the Use Cases section of our PRD: Examples may include: FreeIPA Domain Controller, BIND DNS, DHCP, Database server, iSCSI target, File/Storage server, OpenStack Hypervisor Node. 17:46:14 <rbergeron> sgallagh: i know, it's just a sample example . 17:46:36 <sgallagh> I'm pretty much entirely disinterested in treating specific applications as Server Roles 17:46:51 <sgallagh> (others on the WG may have a different opinion on that matter) 17:46:54 <rbergeron> i'm not going to be cruel and bring up triple-o :) 17:47:18 * sgallagh looks forward to quintuple-o. It's the next logical step, right? 17:47:20 <samkottler> rbergeron: SCORN 17:47:30 <rbergeron> okay, i think i get the picture 17:47:32 <rbergeron> sorry to be all questiony 17:47:44 <sgallagh> Questions now are more useful than questions in six months. 17:47:45 * mattdm thinks questiony is very helpful 17:48:37 <mattdm> here's an idea: what if we make server-in-the-sky one of the fedora cloud spins? 17:48:59 <mattdm> right now, we (tentatively) have a generic base, docker, and big data 17:49:00 * rbergeron was going to bring up load balancing but i think we can skip-it 17:49:08 <rbergeron> hmm 17:49:23 <samkottler> but what do you run on the server in the sky? 17:49:28 <mattdm> we could also have one that's basically got the server role-enablement stuff in place. 17:49:30 <samkottler> is it a db server or a IPA server or what 17:49:37 <sgallagh> mattdm: We were probably going to request help implementing this. It's one of our preferred delivery mechanisms. 17:49:52 <sgallagh> samkottler: "Yes" 17:50:12 <number80> how server and server-in-the-sky roles will be different ? 17:50:13 <mattdm> samkottler it's still also a base, but a base tailored for running the Fedora Server roles. 17:50:13 <samkottler> I guess the other issue is that one of the things we might have is a custom kernel build so it might just be bloated 17:50:56 * samkottler will have to think more about what it'd actually look like 17:51:11 <number80> samkottler: didn't the kernel team said that maintaining multiples kernels would be a PITA for them ? 17:51:32 <samkottler> in the meantime we can force people to to ephemeralize data by having jwb remove fsync from our kernel build 17:52:04 <jwb> done 17:52:19 <sgallagh> number80: Yes, they did. I think they were okay with breaking up the module subpackages, but not actual custom kernels. jwb? 17:52:36 <jwb> yeah. i'm already working on splitting up the packaging 17:52:42 <jwb> i have kernel-core and kernel-drivers 17:52:57 <jwb> kernel-core is what you guys keep saying should be the small thing, without actually telling me what you need in it. 17:53:13 <jwb> so right now, it literally just has the contents the kernel RPM puts in /boot. 17:53:21 <jwb> which... won't really work for anyone 17:53:28 <jwb> so. discuss. then inform. 17:53:53 <samkottler> we should probably include a general list of kernel requirements in the PRD 17:54:00 <jwb> \o/ 17:54:26 <samkottler> I think most of the requirements will be 'rip out this giant pile of drivers' 17:54:32 <jwb> (small caveat: it's not actually working perfectly yet, but i am workign on it at least) 17:54:37 <samkottler> so core won't be affected 17:54:43 * number80 gotta go or he'll be ear-raped by the office alarm 17:54:46 <rbergeron> should those kernel requirements inc. networking/ovs-type stuff? 17:54:49 <mattdm> jwb I can help make that more specific. Is there a bug or other place to help track what should actually be in there? 17:54:56 * rbergeron doesn't know that she's seeen networky-stuff anywhere really 17:55:16 <samkottler> rbergeron: I think ovs is in the server realm? 17:56:00 <jwb> mattdm, no bug. we could create one, or just use the kernel list. i have a new copr project i'm going to use to get people to test builds. 17:56:12 <jwb> rbergeron, ovs? 17:56:18 <jwb> oh, open-vswitch? 17:56:18 <samkottler> jwb: openvswitch 17:56:38 <jwb> yeah, we build that. i figured that and the virtio stuff would be good things to have in -core, but beyond that... 17:57:08 <jwb> and if this grows beyond "core", we can call it "base" instead 17:57:25 <mattdm> jwb hah 17:57:32 <rbergeron> samkottler: i do'nt know what's actually needed to be enabled where, but ... i'm pretty sure you would use it to manage gusests / connect them to each other in various ways? 17:58:04 <jwb> mattdm, i wasn't intending a dig. but it would be hard to say e.g. ovs is really "core" functionality 17:59:07 <jwb> and if you get to "do we want a firewall?" then you just grabbed a ton of netfilter drivers, etc 17:59:19 <jwb> which is why i would like you to tell me what you want :) 17:59:35 <jwb> because if it winds up being most of what we already have... then the exercise is rather pointless 17:59:39 <rbergeron> samkottler: http://www.itworld.com/virtualization/335244/rhev-upgrade-saga-rhel-kvm-and… 17:59:40 <samkottler> mattdm: I can work with you on kernel requirements 18:00:00 <mattdm> sounds good. 18:00:37 <rbergeron> anyway: i don't know my head from my ass on this but if it hasn't been thought about at all it might be worth thinking about . or consulting with someone 18:00:57 <rbergeron> who is more in-depth in ovs/neutron/open daylight land 18:01:04 <rbergeron> (mestery, cdub, etc) 18:01:53 * rbergeron shuts up 18:02:05 <mattdm> e.g. also not me. :) 18:02:17 <jwb> you cloud people have names that are amazing at not describing wtf they do 18:02:20 <mattdm> oh look. fesco time! i will keep this window open 18:02:24 * samkottler doesn't know enough about SDN to actually make decisions 18:02:27 <mattdm> jwb openstack is the WORST 18:02:36 <mattdm> it's got some sort of horrible name virus 18:02:52 <rbergeron> lol 18:03:01 <samkottler> jwb: openvswitch is the most descriptive 18:03:04 <samkottler> and it's still crap 18:03:09 <jwb> samkottler, was just going to say that 18:03:21 <jwb> need magic cloud decoder ring 18:03:40 <jwb> anyway, i'm awaiting further direction/discussion 18:03:49 <jwb> and i'd be happy to start spitting out copr builds 18:03:51 <samkottler> jwb: it's simple really...hook your heat up to your nova to route with your neutron to connect to cinder 18:04:02 <samkottler> welp, computers are bad 18:04:11 <jwb> at least they all have something to do with temperature! 18:04:30 * rbergeron notes that heat makes clouds rise (deploy, whatever), but i may have been involved with that naming 18:04:49 <rbergeron> ANYWAY 18:05:02 <samkottler> rbergeron: heat makes it rain 18:05:04 * rbergeron notes the time and things in the interest of decision making or otherwise 18:05:19 <samkottler> okay yeah let's keep it moving 18:05:36 <samkottler> any more PRD stuff that's pressing? 18:05:47 <samkottler> #action mattdm and samkottler to work on getting kernel requirements together for the PRD 18:07:17 <samkottler> bueller? 18:08:03 <samkottler> #topic open floor 18:08:24 <jzb> Nothing here. 18:08:28 <samkottler> so with the centos news and such, there is going to be a cloud SIG for centos 18:08:37 <samkottler> do we want to have some representation with them? 18:08:45 <jzb> samkottler: yes, I think we do. 18:08:57 <samkottler> jzb: twas kind of a loaded question 18:09:15 <samkottler> I've seen the idea of a shared cloud SIG between fedora and centos 18:09:18 <samkottler> what do people think of that? 18:10:01 <jzb> samkottler: would the scope be similar? 18:10:05 <rbergeron> that sounds epic. 18:10:07 <rbergeron> oh, sorry 18:10:09 <rbergeron> LOL 18:10:25 <samkottler> rbergeron++ 18:10:31 <samkottler> jzb: yeah I believe so 18:10:32 <jzb> rbergeron: I see what you did there. 18:10:39 <samkottler> centos might have some good guidance for us 18:10:45 <samkottler> they already build lots of divergent kernels and stuff 18:10:55 <jzb> true true 18:11:23 <jzb> samkottler: what do we need to do to make that happen? 18:11:37 <jwb> samkottler, actually, not lots 18:11:43 <jwb> i've been poking at them 18:11:46 <samkottler> jzb: I guess the big thing is just for people to be looking for convos on centos-devel 18:11:51 <samkottler> and make sure you're subscribed 18:12:15 <jzb> OK 18:12:28 <jwb> at least in my initial conversations, most of their kernels are still based on RHEL with the xen one being the only one i've found that actually diverged at a base kernel level (3.10 iirc) 18:12:36 <jwb> and their reasons were decent 18:12:41 * jwb shuts up 18:13:09 <samkottler> jwb: they have someone from citrix who manages the 3.10 builds? 18:13:17 <samkottler> the core team doesn't do it 18:13:34 <jwb> samkottler, yep 18:13:57 <samkottler> gotcha 18:14:02 <samkottler> well that's all I've got for the open floor 18:14:14 <samkottler> more PRD work to be done, but we're getting closer 18:14:27 <samkottler> jzb: rbergeron: mattdm: number80: geppetto: anything else? 18:14:38 <geppetto> nope 18:14:57 <jzb> samkottler: nope 18:15:09 <samkottler> #endmeeting ========================================== #fedora-meeting-1: cloud WG weekly meeting ========================================== Meeting started by samkottler at 17:01:57 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-15/fedora-meeting… . Meeting summary --------------- * rollcall (samkottler, 17:03:30) * PRD update and pending issues (samkottler, 17:07:14) * ACTION: mattdm and samkottler to work on getting kernel requirements together for the PRD (samkottler, 18:05:47) * open floor (samkottler, 18:08:03) Meeting ended at 18:15:09 UTC. Action Items ------------ * mattdm and samkottler to work on getting kernel requirements together for the PRD Action Items, by person ----------------------- * mattdm * mattdm and samkottler to work on getting kernel requirements together for the PRD * samkottler * mattdm and samkottler to work on getting kernel requirements together for the PRD * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * samkottler (89) * sgallagh (59) * rbergeron (48) * mattdm (44) * jzb (35) * jwb (30) * number80 (15) * zodbot (13) * geppetto (6) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Meeting minutes Env-and-Stacks WG meeting (2014-01-14)
by Marcela Mašláňová 15 Jan '14

15 Jan '14

=============================================== #fedora-meeting: env and stacks wg (2014-01-14) =============================================== Meeting started by mmaslano at 16:04:30 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-14/env_and_stacks.2… . Meeting summary --------------- * init process (mmaslano, 16:08:53) * AGREED: add tjanez vission and mission statement (+7,-0,0) (mmaslano, 16:21:13) * ACTION: tjanez will add section about vision and mission statement (mmaslano, 16:22:00) * schedule will contain dates, not the actual PRD (mmaslano, 16:37:52) * ACTION: abadger1999 to send out RFC about the SCL direction (abadger1999, 17:36:26) Meeting ended at 17:47:34 UTC. Action Items ------------ * tjanez will add section about vision and mission statement * abadger1999 to send out RFC about the SCL direction Action Items, by person ----------------------- * abadger1999 * abadger1999 to send out RFC about the SCL direction * tjanez * tjanez will add section about vision and mission statement * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * abadger1999 (48) * tjanez (48) * mmaslano (33) * hhorak (23) * pkovar (15) * drieden (15) * jwb (8) * zodbot (6) * samkottler (3) * pkovar1 (1) * pingou (1) * bkabrda (0) * juhp (0) * handsome_pirate (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

FAmNA Jan 14th 2014
by Jon 14 Jan '14

14 Jan '14

====================== #fedora-meeting: FAmNA ====================== Meeting started by masta at 02:02:00 UTC. The full logs are available athttp://meetbot.fedoraproject.org/fedora-meeting/2014-01-15/famna.2014-01-… . Meeting summary --------------- * === FAmNA Roll Call === (masta, 02:02:00) * === Announcements === (masta, 02:05:37) * === Tickets === (masta, 02:09:39) * LINK: https://fedorahosted.org/famna/report/9 (masta, 02:09:40) * Ticket #68 - FAmNA Meeting Organization (masta, 02:10:31) * === New swag ideas === (masta, 02:13:35) * LINK: https://fedoraproject.org/wiki/Swag_vendors (inode0, 02:39:06) * ACTION: masta to engage on the t-shirts (masta, 02:48:17) * === open floor === (masta, 02:52:48) Meeting ended at 03:04:08 UTC. Action Items ------------ * masta to engage on the t-shirts Action Items, by person ----------------------- * masta * masta to engage on the t-shirts * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * masta (73) * inode0 (57) * award3535 (34) * kk4ewt (9) * zodbot (8) * wrnash1 (6) * nb (5) --Jon Disnard irc: masta fas: parasense

1 0

Re: [Ambassadors] REMINDER French Fedora Meeting Today #fedora-meeting-1
by Emmanuel Seyman 14 Jan '14

14 Jan '14

* Reminder [14/01/2014 08:30] : > > Ce mail est un rappel pour la réunion de la communauté francophone, > qui aura lieu ce mardi (14 janvier) à 21h00 heure de Paris sur > IRC (freenode) #fedora-meeting-1 . Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-14/fedora-fr.2014… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-14/fedora-fr.2014… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-14/fedora-fr.2014… Emmanuel

1 0

Server WG Meeting Minutes (2014-01-14)
by Stephen Gallagher 14 Jan '14

14 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =================================================================== #fedora-meeting-1: Server Working Group Weekly Meeting (2014-01-14) =================================================================== Meeting started by sgallagh at 15:59:51 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-14/fedora-meeting… . Meeting summary - --------------- * roll call (sgallagh, 16:00:00) * PRD Draft (sgallagh, 16:06:04) * LINK: https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_Doc… (sgallagh, 16:07:13) * Positioning relative to Fedora Cloud (sgallagh, 16:08:33) * AGREED: remove use-case 7, move OpenStack Hypervisor Node reference to proposed Roles list (sgallagh, 16:55:00) * AGREED: Use case 8 remains as written (sgallagh, 17:08:38) * Use Case 6: Env/Stacks and deployment of frameworks (sgallagh, 17:09:14) * AGREED: drop "easy deployment of a framework" from our charter (sgallagh, 17:20:05) * FIXME for headless operation (sgallagh, 17:20:30) * AGREED: New use-case: "10. The user must be able to install and manage Fedora Server in a headless mode where the display framework is inactive." (sgallagh, 17:31:29) * Open Floor (sgallagh, 17:31:51) Meeting ended at 17:42:38 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * sgallagh (146) * simo (95) * davidstrauss (54) * mitr (52) * jzb (37) * mizmo (37) * nirik (35) * adamw (12) * tuanta (10) * zodbot (9) * number80 (4) * Evolution (3) * danofsatx (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLVd3IACgkQeiVVYja6o6OI3gCeJ7+P7P6HhMfqflZpgYudwZNW iwYAnRmdMkq3BDv6uXXt8Et3V2aU06Zl =7f+Y -----END PGP SIGNATURE-----

1 0

Fedora Marketing Meeting Notes. Recap will be on the Fedora Magazine
by Chris A. Roberts 13 Jan '14

13 Jan '14

<zodbot> Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora_marketing… <zodbot> Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora_marketing… <zodbot> Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora_marketing… Chris Roberts Fedora Marketing https://fedoraproject.org/wiki/User:Chrisroberts

1 0

2013-01-13 Fedora QA Devel Meeting Minutes
by Tim Flink 13 Jan '14

13 Jan '14

====================================== #fedora-blocker-review: fedoraqa-devel ====================================== After much fun with finding an open channel for the meeting, we did get through a bunch of stuff. At the moment, no more meetings are planned and we will schedule more as needed/appropriate. Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-… Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-… Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-01-13/fedoraqa-… Meeting summary --------------- * Roll Call (tflink, 17:12:50) * Taskotron Status (tflink, 17:19:29) * Taskotron Phase 1 is due to be delivered 2014-03-01 (tflink, 17:20:07) * LINK: https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase… (tflink, 17:20:35) * phase 0 is mostly complete, tickets need a bit of updating, still (tflink, 17:21:46) * LINK: https://phab.qadevel.cloud.fedoraproject.org/T7 (tflink, 17:21:54) * Depcheck rewrite status (tflink, 17:24:47) * LINK: https://bitbucket.org/fedoraqa/depcheck-mk-2 (handsome_pirate, 17:25:30) * initial depcheck scenarios have been coded up (tflink, 17:27:38) * LINK: https://bitbucket.org/fedoraqa/depcheck_scenarios (tflink, 17:27:44) * current depcheck-mk-2 code is passing some of the depcheck scenarios, rest are being worked on (tflink, 17:29:58) * Documentation (tflink, 17:35:32) * LINK: https://phab.qadevel.cloud.fedoraproject.org/T39 (tflink, 17:37:11) * roshi is looking into using dexy (tflink, 17:40:01) * LINK: http://dexy.it (tflink, 17:40:09) * ACTION: roshi to write up comparison between dexy and sphinx, send out to list when complete (tflink, 17:55:38) * Taskotron Tasks/Checks (tflink, 17:56:32) * initial tasks will be the checks from AutoQA PUATP (minus depcheck, which is being rewritten) (tflink, 17:57:18) * the target checks for phase 1 are: rpmlint, upgradepath, depcheck (mk 2) (tflink, 18:01:30) * ACTION: tflink to move repoclosure to later phase in wiki docs (tflink, 18:02:27) * LINK: https://phab.qadevel.cloud.fedoraproject.org/T15 (tflink, 18:05:14) * LINK: https://phab.qadevel.cloud.fedoraproject.org/T14 (tflink, 18:05:26) * possible checks for a future phase: repoclosure, rpmguard, abicheck (tflink, 18:10:25) * Taskotron Runner (tflink, 18:11:11) * demo code is public, but incomplete (tflink, 18:12:59) * LINK: https://bitbucket.org/fedoraqa/libtaskotron-demo (tflink, 18:13:15) * ACTION: tflink to move repo from libtaskotron-demo to libtaskotron (tflink, 18:17:05) * Fedora Beaker Installation (tflink, 18:20:56) * LINK: https://lists.fedoraproject.org/pipermail/infrastructure/2014-January/01388… (tflink, 18:24:42) * Devops and Infrastructure (tflink, 18:32:08) * LINK: http://phabricator.org/ (tflink, 18:35:31) * LINK: https://phab.qadevel.cloud.fedoraproject.org/ (tflink, 18:35:46) * LINK: https://qadevel-stg.cloud.fedoraproject.org/builds/ (tflink, 18:37:16) * LINK: https://bitbucket.org/tflink/fedoraqa-ansible (tflink, 18:41:22) * ACTION: tflink to update playbooks and docs so that folks can setup dev systems (tflink, 18:44:22) * Coding Policy/Strategy Going Forward (tflink, 18:47:59) * LINK: http://nvie.com/posts/a-successful-git-branching-model/ (tflink, 18:50:25) * LINK: https://github.com/nvie/gitflow (tflink, 18:50:35) * LINK: http://python-future.org/index.html (tflink, 18:54:07) * Short Term Plans (tflink, 18:56:12) * get a new demo system up and running to start testing taskotron as a whole (tflink, 18:56:39) * get docs and planning done (tflink, 18:56:48) * continue with the work described earlier (checks, runner etc.) (tflink, 18:57:07) * Open Floor (tflink, 18:59:22) Meeting ended at 19:04:11 UTC. Action Items ------------ * roshi to write up comparison between dexy and sphinx, send out to list when complete * tflink to move repoclosure to later phase in wiki docs * tflink to move repo from libtaskotron-demo to libtaskotron * tflink to update playbooks and docs so that folks can setup dev systems Action Items, by person ----------------------- * roshi * roshi to write up comparison between dexy and sphinx, send out to list when complete * tflink * tflink to move repoclosure to later phase in wiki docs * tflink to move repo from libtaskotron-demo to libtaskotron * tflink to update playbooks and docs so that folks can setup dev systems * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * tflink (225) * handsome_pirate (53) * kparal (36) * roshi (30) * Viking-Ice (15) * mkrizek (10) * shisatum (5) * zodbot (5) * danofsatx (4) * adamw (1) * pschindl (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

FAmSCo meeting minutes 2013-01-13
by Jiri Eischmann 13 Jan '14

13 Jan '14

Hi, we had another FAmSCo meeting today. 6 out of 7 members attended. We mainly discussed: * Fedora elections for F21 cycle * Budget drafts for the fiscal year 2015 * How Fedora.NEXT will affect ambassadors * FUDCons in LATAM and APAC You can find more in the meeting minutes: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-13/famsco.2014-01… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-13/famsco.2014-01… Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-13/famsco.2014-01… The next meeting will on Jan 20th. Jiri

1 0

2014-01-13 - Fedora QA Meeting - minutes
by Adam Williamson 13 Jan '14

13 Jan '14

================================== #fedora-meeting: Fedora QA meeting ================================== Meeting started by adamw at 16:00:59 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora-qa.2014-0… . Meeting summary --------------- * Roll call (adamw, 16:01:09) * Previous meeting follow-up (adamw, 16:09:13) * "adamw to send a mail to test@ about the ten year t-shirt thing" - clearly, that happened: https://lists.fedoraproject.org/pipermail/test/2014-January/120006.html (adamw, 16:09:36) * EOL process handling (adamw, 16:12:48) * there has been a bit of a debate about the EOL (end-of-life) process, which is documented on the Wiki in a QA-ish space (Bugzappers), but which in practice has been handled by the program manager (adamw, 16:13:36) * thread started at https://lists.fedoraproject.org/pipermail/devel/2013-December/193094.html (adamw, 16:15:58) * LINK: https://fedoraproject.org/wiki/End_of_life_SOP does list it under Bugzappers, so we need to straighten that out whichever way it goes. (adamw, 16:25:54) * LINK: http://johnpoelstra.com/five-months-of-bug-triage/ is interesting (adamw, 16:33:51) * https://fedoraproject.org/wiki/End_of_life_SOP still shows the bug closure to be the responsibility of 'Bugzappers' (adamw, 16:36:55) * http://johnpoelstra.com/five-months-of-bug-triage/ implies the history of the EOL process - it was developed as part of the Bugzappers effort and originally done by poelcat with his Bugzappers hat on, not his Program Manager hat (adamw, 16:37:34) * LINK: https://fedorahosted.org/fesco/ticket/1198 (jreznik, 16:39:17) * EOL scripts are available at https://git.fedorahosted.org/cgit/fedora-project-schedule.git/tree/scripts/… (adamw, 16:40:06) * viking-ice's suggestions that QA should own the process and perhaps drop the closing of bugs on EOL releases is noted but not supported by a consensus (adamw, 16:50:38) * ACTION: adamw to summarize the discussion for a fesco ticket note on https://fedorahosted.org/fesco/ticket/1198 (adamw, 16:58:41) * 10 year anniversary t-shirt (adamw, 16:59:09) * open floor (adamw, 17:04:18) * it's fine to propose blockers for f21 already (adamw, 17:07:55) Meeting ended at 17:09:02 UTC. Action Items ------------ * adamw to summarize the discussion for a fesco ticket note on https://fedorahosted.org/fesco/ticket/1198 Action Items, by person ----------------------- * adamw * adamw to summarize the discussion for a fesco ticket note on https://fedorahosted.org/fesco/ticket/1198 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * adamw (91) * cmurf (51) * jreznik (41) * Viking-Ice (38) * roshi (18) * kparal (14) * tflink (7) * danofsatx (6) * zodbot (4) * jsmith (4) * yachironi (2) * mkrizek (1) * pwhalen (1) * pschindl (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora Docs Meeting Summary 13Jan2013
by Pete Travis 13 Jan '14

13 Jan '14

==================================================================================================== #fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings ==================================================================================================== Meeting started by randomuser at 14:00:18 UTC. The full logs are available athttp://meetbot.fedoraproject.org/fedora-meeting/2014-01-13/fedora_docs.20… . Meeting summary --------------- * Roll Call (randomuser, 14:00:18) * Guide Status (randomuser, 14:07:19) * pbokoc has updated IG for f20 and is prepping POTs now (randomuser, 14:07:53) * LINK: https://fedoraproject.org/wiki/Category:Docs_Project_tasks?rd=Docs_Project_… (randomuser, 14:14:03) * If you have or want tasks, use the tasks page (randomuser, 14:14:15) * Capesteve is creating a Networking Guide, starting with Networking content from Sysadmin guide (randomuser, 14:26:04) * LINK: https://git.fedorahosted.org/cgit/docs/power-management-guide.git/plain/pot… (pbokoc, 14:26:22) * Publican4 thing (randomuser, 14:30:43) * Docs FAD (randomuser, 14:36:40) * nb nominates randomuser to continue as docs lead (nb, 14:48:09) * ACTION: randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling (randomuser, 14:49:51) * bz tickets (randomuser, 14:51:21) Meeting ended at 15:00:17 UTC. Action Items ------------ * randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling Action Items, by person ----------------------- * randomuser * randomuser to send mail to list regarding 21MAR-23MAR FAD scheduling * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * randomuser (86) * pbokoc (25) * Sparks (19) * yruseva (13) * jjmcd (9) * misc (7) * lnovich (6) * nb (6) * zodbot (4) * Capesteve (4) * pkovar (2) * gomix (1) * jhradilek (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fedora Release Engineering meeting summary for 2014-01-13
by Dennis Gilmore 13 Jan '14

13 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ========================= #fedora-meeting-1 Meeting ========================= Meeting started by dgilmore at 16:34:47 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-13/releng.2014-01… . Meeting summary - --------------- * , roll call (dgilmore, 16:35:03) * tickets (dgilmore, 16:41:00) * LINK: https://fedorahosted.org/rel-eng/report/10 (dgilmore, 16:41:08) * epel7 (dgilmore, 16:43:51) * SCM admins (dgilmore, 16:50:26) * LINK: http://infrastructure.fedoraproject.org/infra/docs/scmadmin.txt (abadger1999, 16:55:16) * ACTION: dgilmore to reach out and invite scmadmins to join releng (dgilmore, 16:57:24) * rawhide changes (dgilmore, 17:06:44) * LINK: https://apps.fedoraproject.org/releng-dash/ (nirik, 17:10:33) * LINK: http://meetbot.fedoraproject.org/meetbot/meetbot/meetbot/teams/discussion_o… (nirik, 17:12:55) * todo list (dgilmore, 17:18:34) * please file tickets in trac for things that need doing (dgilmore, 17:21:23) * LINK: https://fedorahosted.org/fedora-infrastructure/ticket/3358 (abadger1999, 17:21:36) * open floor (dgilmore, 17:25:54) * places for releng work (dgilmore, 17:28:49) * open floor again (dgilmore, 17:35:23) * LINK: http://209.132.184.188/ (nirik, 17:44:34) Meeting ended at 17:48:44 UTC. Action Items - ------------ * dgilmore to reach out and invite scmadmins to join releng Action Items, by person - ----------------------- * dgilmore * dgilmore to reach out and invite scmadmins to join releng * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dgilmore (128) * nirik (49) * abadger1999 (18) * janeznemanic (14) * masta (11) * tflink (4) * sharkcz (4) * zodbot (3) * tyll_ (3) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJS1CdlAAoJEH7ltONmPFDRMvYQAKKUvQc364iyNDSomCwdVdVd tAMJi/R6+/kTpiw0K3ncG6YgKfR6XJFU2wXnuBDYuOcWpowGz5OjmTeCpCxfroPb fselmH1SHetOx/KEdq8jnFDL0x/xj4Ko0Apy7ZHdiKkmyvMkb3IBpQsV78P7zUl2 aPUYyaVuUXvvVFV5sLoGRGdjeL5q2chiB2Po+XrLdXvodmqkk0uWNNnzu43IAIMd x50G5gEg7/YAw3HbW5h6/ClupB0Ut+G7pT6lgbVRvGByyTxC4hQBSfE0W/LYegLW 3/uI7Z81DCZkLs7ooWeAVn8TU2DD26ThGhYpPgxbTPqHlsT34yuOJgsKUT70JLNu UMJHVXr7o34g4bU5lqNJWekewHtB8xLpzFh+eEvolp9PUhhOJa2oaju2DzhV5ggY IMi1YivQz4nCU6geAYIz4xzgLuxJxUXwSe8ncAtVBKwnNPPt+/yEWQfqRDbJgTWJ 24r6ZsuGn89pi7x0NeC3L//5t2ff90ia3xnqI/P3Lnb9yhp5Dm4+xuOim6AaO4/5 aPtjHNg4ii6FSAyioSrfwEtlmy5IRabdw/YtyVjvCb3jpCE2LWkz3jpHbNNsoIVP qYw6NnkYZbGy2lBtXHdZhub4eMxn2zOcKZJDTqxJe5cMbwtjFdkS+ucfm6AZqOJJ 6Ir0X1IaJ3a+hmjpL6M1 =ygLA -----END PGP SIGNATURE-----

1 0

Fedora Chinese Meeting Minutes (2014-01-10)
by Alick Zhao 10 Jan '14

10 Jan '14

Hi all, The IRC meeting minutes tonight are available at the links below. Thanks everyone for attending the meeting. In the meeting we talked about FUDCon bid progress, F20 Release Party, L10N, and others. Please review the proposed ideas and actions. The next IRC meeting will be held on next Friday (2014-01-17). Please come and join the discussion if you can! * Minutes: http://meetbot.fedoraproject.org/fedora-zh/2014-01-10/fedora-zh.2014-01-10-… * Minutes (text): http://meetbot.fedoraproject.org/fedora-zh/2014-01-10/fedora-zh.2014-01-10-… * Log: http://meetbot.fedoraproject.org/fedora-zh/2014-01-10/fedora-zh.2014-01-10-… ================== #fedora-zh Meeting ================== Meeting started by alick at 13:02:53 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-zh/2014-01-10/fedora-zh.2014-01-10-… . Meeting summary --------------- * 报到 Who's here? (alick, 13:03:09) * FUDCON APAC 2014 Bid (alick, 13:09:47) * LINK: https://fedoraproject.org/wiki/FUDCon:Bid_for_Beijing_2014 (alick, 13:09:58) * zsun 帮忙更新了亚洲/大洋洲的机票信息 (alick, 13:12:47) * 申办提交截止日期为 1 月中旬 (alick, 13:13:25) * IDEA: 我们应该本周末提交申请。 (alick, 13:13:39) * ACTION: alick push organizers to update hotel, budget info by this weekend (alick, 13:19:49) * F20 Release Party (alick, 13:20:33) * LINK: https://fedoraproject.org/wiki/Release_Party_F20_Shanghai (alick, 13:20:44) * LINK: https://www.surveymonkey.com/s/6NRZNYJ (alick, 13:23:52) * ACTION: RobberPhex write event report for relparty Shanghai (alick, 13:23:59) * 北京站活动的调查问卷将于几个小时后关闭，请还没填写的尽快填写！ (alick, 13:25:17) * LINK: https://www.surveymonkey.com/s/P96HCPM (alick, 13:25:25) * 线下活动 (alick, 13:28:10) * LINK: http://huiyi.csdn.net/module/meeting/meeting/info/680/community?project_id=… (alick, 13:28:35) * EFD 活动时间 1 月 18 日，地点国科大中关村园区 (alick, 13:29:46) * ACTION: dongfengweixiao recreate sticker design and share it publicly (alick, 13:30:39) * ACTION: tonghuix create localized sticker design (alick, 13:31:12) * L10N 中文翻译 (alick, 13:32:05) * TIP: IRC 中需要插话可以用 ! 号，有疑问可以用 ? 号，之后详细表达。 (alick, 13:33:13) * IDEA: 保留 git 仓库的术语表，并继续维护，作为项目全局术语表，收录全局性的、通用的条目。 (alick, 13:38:16) * LINK: https://fedorahosted.org/chinese-glossary/wiki/WikiStart (alick, 13:40:27) * ACTION: alick mail to list about idea on glossary updates (alick, 13:45:14) * BUG 评选 (alick, 13:47:16) * 自由讨论 (alick, 13:51:42) * LINK: http://help.weibo.com/ask/q/20688669 (isyangxin1, 13:57:17) Meeting ended at 14:04:47 UTC. Action Items ------------ * alick push organizers to update hotel, budget info by this weekend * RobberPhex write event report for relparty Shanghai * dongfengweixiao recreate sticker design and share it publicly * tonghuix create localized sticker design * alick mail to list about idea on glossary updates Action Items, by person ----------------------- * alick * alick push organizers to update hotel, budget info by this weekend * alick mail to list about idea on glossary updates * tonghuix * tonghuix create localized sticker design * **UNASSIGNED** * RobberPhex write event report for relparty Shanghai * dongfengweixiao recreate sticker design and share it publicly People Present (lines said) --------------------------- * alick (76) * isyangxin (14) * zodbot (8) * BadGirl (8) * biergaizi (7) * isyangxin1 (1) * tonghuix (0) * tiansworld (0) * zsun_mob (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2013-01-09 @ 16:00 UTC - Fedora QA Devel Meeting Minutes
by Tim Flink 09 Jan '14

09 Jan '14

================================= #fedora-meeting-2: fedoraqa-devel ================================= We didn't quite get through everything today, so we'll continue after the QA meeting on Monday. I'll be sending an announcement for that meeting shortly. Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-09/fedoraqa-devel… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-09/fedoraqa-devel… Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-09/fedoraqa-devel… Meeting summary --------------- * Roll Call (tflink, 16:01:31) * Current Project Status (tflink, 16:06:34) * Not much is going on with blockerbugs for the short term - we're waiting to see how f21 and/or fedora.next shape out before working on any new features beyond the small changes ready for review (tflink, 16:08:54) * LINK: https://phab.qadevel.cloud.fedoraproject.org/project/view/1/ (tflink, 16:11:22) * Current Status and Plans - resultsdb and testdays (tflink, 16:19:33) * the reduced re-implementation for resultsdb is up and running at http://resultsdb.qa.fedoraproject.org/resultsdb (tflink, 16:21:57) * resultsdb browsing is available at: http://resultsdb.qa.fedoraproject.org/resultsdb_frontend/ (tflink, 16:22:22) * resultsdb API docs are at: http://docs.resultsdb.apiary.io/ (tflink, 16:22:45) * the new resultsdb is (comparing to the old concept) quite simplified on the data level - we stripped all the un-used tables from the old concept, and adapted the data to what we actually used with the autoqa reporting (tflink, 16:28:11) * old and new resultsdb schema displayed at: https://fedoraproject.org/wiki/AutoQA_resultsdb_schema (tflink, 16:29:18) * Current Status - Testday App (tflink, 16:38:15) * the testdays app is IMHO quite self-confined, and I have no immediate goals for changing what it does (apart of bug-fixes). This is because it's using the 'old' resultsdb, and uses TurboGears2 (tflink, 16:40:28) * The plans for the future are to re-write it with Flask & New Resultsdb but it is (at the moment) quite low-priority (tflink, 16:42:29) * Current Status - Support Tools (tflink, 16:43:31) * the main support tools that we have are phabricator (code review, issue tracking etc.) and buildbot (in progress)/ jenkins (existing, not quite working) for ci (tflink, 16:47:03) * phabricator is deployed at https://phab.qadevel.cloud.fedoraproject.org/ (tflink, 16:47:22) * LINK: http://phabricator.org/ (Viking-Ice, 16:47:46) * ACTION: tflink to write up docs on code review with phabricator (tflink, 16:49:01) * buildbot for qa project CI is deployed to staging at https://qadevel-stg.cloud.fedoraproject.org/builds/ (tflink, 16:51:59) * there is still work to do on buildbot so that we have CI and hopefully autogenerated and autodeployed docs for qa devel projects (tflink, 16:56:57) * Priorities (tflink, 17:00:36) * AGREED: As we have a longer break between releases for now, automation is a higher priority because it is more disruptive and needs to be done soon (tflink, 17:16:42) * Fedoraproject Beaker Instance Status (tflink, 17:17:26) * we have a dev instance of beaker deployed at https://beaker-dev.fedoraproject.org/bkr/ (tflink, 17:18:11) * due to security concerns, it is currently locked down by IP (tflink, 17:18:29) * ACTION: kparal and tflink to sync up on beaker.fp.o status and come up with some ideas on moving forward (tflink, 17:29:49) * Taskotron status (tflink, 17:29:52) * The hope was to have taskotron phase 0 (https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase…) done by now (tflink, 17:30:47) * task description format was proposed and sent out to qa-devel@. response has been mostly positive and it is ready to start moving forward (tflink, 17:31:36) * initial fedmsg reliability investigation indicates that it will be reliable enough to use for automation scheduling but we should continue to keep an eye on it (tflink, 17:32:27) * LINK: https://phab.qadevel.cloud.fedoraproject.org/T2 (tflink, 17:32:43) * there was a proof-of-concept system running in the fedora cloud, but it seems to be having issues ATM (tflink, 17:37:54) * The big remaining task for phase 0 is discussion/investigation into notifications (tflink, 17:39:25) * the proof-of-concept runner does work locally and does produce output to the console, it can't report to resultsdb (yet) and needs some refactoring (tflink, 17:40:29) * ACTION: tflink to finish notificaitons email and send it out to qa-devel@ (tflink, 17:42:28) * depcheck scenarios have been drafted up and fake rpms have been coded up for testing (tflink, 17:45:34) * LINK: https://bitbucket.org/fedoraqa/depcheck_scenarios (tflink, 17:47:26) * Deadlines and Milestones (tflink, 17:49:04) * Current deadline for taskotron phase 1 is 2013-03-01 (tflink, 17:49:25) * LINK: https://fedoraproject.org/wiki/User:Tflink/taskotron_development_plan#Phase… (tflink, 17:49:47) * Meetings (tflink, 17:55:59) * ACTION: tflink to schedule followup meeting after monday's qa meeting (tflink, 17:58:37) * Open Floor (tflink, 17:58:57) Meeting ended at 18:06:44 UTC. Action Items ------------ * tflink to write up docs on code review with phabricator * kparal and tflink to sync up on beaker.fp.o status and come up with some ideas on moving forward * tflink to finish notificaitons email and send it out to qa-devel@ * tflink to schedule followup meeting after monday's qa meeting Action Items, by person ----------------------- * kparal * kparal and tflink to sync up on beaker.fp.o status and come up with some ideas on moving forward * tflink * tflink to write up docs on code review with phabricator * kparal and tflink to sync up on beaker.fp.o status and come up with some ideas on moving forward * tflink to finish notificaitons email and send it out to qa-devel@ * tflink to schedule followup meeting after monday's qa meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * tflink (231) * Viking-Ice (64) * handsome_pirate (34) * kparal (30) * jskladan (23) * zodbot (7) * mkrizek (6) * croberts (5) * roshi (2) * pschindl (2) * nirik (1) * satellit (1) * danofsatx (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Summary/Minutes from today's FPC Meeting (2014-01-09 17:00 - 18:35 UTC)
by James Antill 09 Jan '14

09 Jan '14

====================== #fedora-meeting-1: fpc ====================== Meeting started by abadger1999 at 16:59:29 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-09/fpc.2014-01-09… . Meeting summary --------------- * Roll Call (abadger1999, 16:59:35) * #339 software collections in Fedora (abadger1999, 17:07:57) * LINK: https://fedorahosted.org/fpc/ticket/339 (abadger1999, 17:08:03) * LINK: https://fedoraproject.org/w/index.php?title=User%3AToshio% 2FSCL_Guidelines_%28draft%29&diff=366334&oldid=364381 (abadger1999, 17:09:22) * LINK: https://bitbucket.org/osmanov/pecl-ev/src/30589504e7cbe14445053682e42c07f7d… (RemiFedora, 17:27:23) * #369 Guidance on dealing with the bundled libev in perl-EV (abadger1999, 17:33:04) * Proposal to allow libev-source (with conditions -- see summary in ticket) approved. (+1:6, 0:0, -1:0) (abadger1999, 17:41:56) * Proposal to allow libev-source (with conditions -- see summary in ticket) approved. (+1:7, 0:0, -1:0) (abadger1999, 17:43:13) * #375 Update to the Addon Packages naming guidelines for Python 3 Modules (abadger1999, 17:43:22) * LINK: https://fedorahosted.org/fpc/ticket/375 (abadger1999, 17:44:09) * 374 Ada guidelines changes for Comfignat and runpaths (abadger1999, 17:59:06) * LINK: https://fedorahosted.org/fpc/ticket/374 (abadger1999, 17:59:11) * Latest GNAT_add_rpath changes approved (+1:6, 0:0, -1:1) (abadger1999, 18:08:09) * #377 tmpfiles.d guidelines update (abadger1999, 18:09:09) * LINK: https://fedorahosted.org/fpc/ticket/377 (abadger1999, 18:09:56) * Proposal to use systemd-tmpfiles --create and not have packages specify the directories under /var/lock in rpm's %files rejected. Vote to approve the proposal was (+1:0, 0:0, -1:5) (abadger1999, 18:30:53) * Open Floor (abadger1999, 18:31:04) Meeting ended at 18:36:47 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * abadger1999 (100) * geppetto (30) * tibbs|w (18) * limburgher (14) * RemiFedora (14) * racor (10) * Rathann (10) * Rombobeorn (8) * zodbot (7) * SmootherFrOgZ (5) * tibbsphone (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Summary/Minutes from today's irc support sig meeting (2014-01-09)
by Kevin Fenzi 09 Jan '14

09 Jan '14

============================================= #fedora-meeting: IRC Support SIG (2014-01-09) ============================================= Meeting started by nirik at 18:00:22 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-09/irc-support-sig.… . Meeting summary --------------- * init process (nirik, 18:00:22) * Week(s) in review (nirik, 18:03:52) * ticket #165: EvilBob excessive complaining about my away nick changer (nirik, 18:06:30) * revisit 'excessive' nick change policy (nirik, 18:09:22) * ACTION: nirik to write up new plan for nick change policy (nirik, 18:17:31) * Open Floor (nirik, 18:17:36) Meeting ended at 18:24:26 UTC. Action Items ------------ * nirik to write up new plan for nick change policy Action Items, by person ----------------------- * nirik * nirik to write up new plan for nick change policy * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (33) * Khaytsus (10) * zodbot (3) * kc8hfi (3) * triad (1) -- 18:00:22 <nirik> #startmeeting IRC Support SIG (2014-01-09) 18:00:22 <zodbot> Meeting started Thu Jan 9 18:00:22 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:22 <nirik> #meetingname irc-support-sig 18:00:22 <nirik> #topic init process 18:00:22 <zodbot> The meeting name has been set to 'irc-support-sig' 18:00:45 <nirik> any folks around for a irc support sig meeting? 18:01:14 * Khaytsus burps 18:01:21 <kc8hfi> i'm here, watchin 18:01:50 * nirik will wait a few min for folks. 18:03:39 <nirik> ok, I guess lets go ahead 18:03:52 <nirik> #topic Week(s) in review 18:04:18 <nirik> anything to bring up from over the holidays or recently? 18:04:24 <nirik> common bugs, issues, etc? 18:04:44 <nirik> it seemed overall pretty quiet. 18:04:56 <nirik> f20 went out pretty smoothly aside from a few hiccups right at release. 18:06:30 <nirik> #topic ticket #165: EvilBob excessive complaining about my away nick changer 18:06:32 <triad> hanging around; don't know what the topic means exactly 18:06:54 <nirik> this ties into the next topic as well somewhat 18:07:45 <nirik> triad: well, this group organizes support and management of #fedora... so the previous topic was to see if anyone had issues to bring up that they had seen a lot of recently. 18:08:57 <nirik> anyhow, I spoke my thoughts in this ticket already... I think we just close it at this point peding changes in the overall policy 18:09:03 <Khaytsus> The noise _from_ nick chnages has exceeded the actual nick changes recently. 18:09:14 <nirik> Khaytsus: yeah, thats the next topic. 18:09:22 <nirik> #topic revisit 'excessive' nick change policy 18:09:31 <Khaytsus> Some common sense needs to be employed when giving warnings 18:09:34 <nirik> so, our current policy is somewhat vuage and subjective. 18:09:55 <nirik> in particular some folks feel 'once' is 'excessive and anoying 18:10:17 <nirik> I think thats crazy. :) 18:10:33 <nirik> so, I guess we should draft a change and get folks to discuss/agree with it. 18:10:57 <Khaytsus> If it's happpening frequently, sure, put an end to it. If it happens once or once a day. It's noise, disruption, and just plane looks bad to yell at the user about it. 18:11:02 <nirik> we don't really have enough of us here today to change anything now, but I would like to soon. 18:11:11 <Khaytsus> plain.. ahem 18:11:25 <kc8hfi> plane, plain! 18:11:26 <nirik> I was thinking... 5 times in an hour 18:11:34 <nirik> the plane! the plane! 18:11:43 * Khaytsus walks on his knees 18:11:54 * Khaytsus coughs 18:12:18 <nirik> 5 times -> warn/tell them to stop, another time, kick/temp ban 18:12:59 <nirik> but I can file a ticket on it. 18:13:09 * kc8hfi doesn't see anything wrong with that 18:13:59 <Khaytsus> Everyone 20 minutes seems like it's condusive to auto away nick changes, which we'd ideally avoid. But otherwise tracking frequency isn't easy I suppose. 18:15:04 <nirik> yeah. 18:16:45 <Khaytsus> I'd +1 5/hr over 1 ever, no question :) 18:17:05 <nirik> yeah, 18:17:31 <nirik> #action nirik to write up new plan for nick change policy 18:17:36 <nirik> #topic Open Floor 18:17:42 <nirik> any items for open floor? 18:19:44 <nirik> alright then... will close out in a minute if nothing else. 18:20:38 <Khaytsus> :) 18:24:26 <nirik> #endmeeting

1 0

EMEA ambassadors meeting minutes 2013-01-08
by Jiri Eischmann 08 Jan '14

08 Jan '14

Hi, we had another regional meeting. 15 ambassadors attended and the meeting lasted 1 hour and 30 minutes. If you'd like to know more, read the minutes: Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/emea_ambassadors… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/emea_ambassadors… Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/emea_ambassadors… The next meeting will be on January 22nd. Meet you in two weeks! Jiri

1 0

Fedora Latam Ambassadors Meeting log / Registrs de la reunion de embajadores de Fedora Latam 2014-01-08
by alejandro perez 08 Jan '14

08 Jan '14

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/fedora_latam_amb… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/fedora_latam_amb… Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/fedora_latam_amb…

1 0

Fedora ARM Status Meeting Minutes 2014-01-08
by Paul Whalen 08 Jan '14

08 Jan '14

Thanks to those that were able to join us for the status meeting today, for those unable the minutes are posted below: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeting… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeting… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeting… ============================================ #fedora-meeting-1: Fedora ARM status meeting ============================================ Meeting started by pwhalen at 21:01:22 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-08/fedora-meeting… . Meeting summary --------------- * 1a) Aarch64 - Status Update (pwhalen, 21:03:00) * koji builds are running now- pbrobinson driving builds (bconoboy, 21:04:37) * Numerous bugs being worked through- mariadb is pressing (bconoboy, 21:07:04) * More builders being added this month (bconoboy, 21:08:54) * 2a) F21 - Hardware Support Goals (pwhalen, 21:13:27) * 3.13 kernel feature set is similar to 3.12, no new hardware specifically tested yet (bconoboy, 21:20:38) * Note to BBB users: 3.12 kernel will make BBB video work on F20 release (bconoboy, 21:21:07) * 3.12.7 will be the one to go with (pbrobinson, 21:21:32) * 2b) F21 - Installation Images (pwhalen, 21:27:34) * LINK: Hans' proposed kernel patch plan needs attention https://lists.fedoraproject.org/pipermail/kernel/2013-December/004752.html (bconoboy, 21:32:48) * 4) Open Floor (pwhalen, 21:35:47) * LINK: https://lists.fedoraproject.org/pipermail/qa-devel/2014-January/000599.html (handsome_pirate, 21:36:30) Meeting ended at 21:49:57 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pbrobinson (69) * bconoboy (50) * dgilmore (38) * hrw (29) * handsome_pirate (22) * pwhalen (21) * jwb (13) * masta (12) * zodbot (12) * ctyler (4) * jcapik (3) * ahs3 (2) * dmarlin (1) * agreene (1) * msalter (0) * jdisnard (0) * jonmasters (0) * ddd (0)

1 0

FAmNA Meeting (04 Jun 2013)
by inode0 07 Jan '14

07 Jan '14

====================== #fedora-meeting: famna ====================== Meeting started by inode0 at 02:02:24 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-08/famna.2014-01-08… . Meeting summary --------------- * Roll Call (inode0, 02:02:46) * Announcements (inode0, 02:06:12) * Agenda (inode0, 02:13:39) * LINK: https://fedorahosted.org/famna/report/9 (inode0, 02:13:46) * AGREED: Initial funding for TXLF 2014 as described in ticket 69 approved. (inode0, 02:28:16) * LINK: https://fedoraproject.org/wiki/TXLF_2014 (inode0, 02:28:58) * AGREED: Get a new set of vertical banners for events. (inode0, 02:34:01) * Open Floor (inode0, 02:42:28) * LINK: https://fedorahosted.org/famnarequests/ (inode0, 02:51:46) Meeting ended at 02:52:08 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * inode0 (71) * award3535 (30) * dan408_ (25) * kk4ewt (23) * handsome1pirate (23) * suehle (14) * ParadoxGuitarist (12) * zodbot (8) * rbergeron (7) John

1 1

Re: [Ambassadors] REMINDER French Fedora Meeting Today #fedora-meeting-1
by Emmanuel Seyman 07 Jan '14

07 Jan '14

* Reminder [07/01/2014 08:30] : > > Ce mail est un rappel pour la réunion de la communauté francophone, qui aura > lieu ce mardi ( 7 janvier) à 21h00 heure de Paris sur IRC (freenode) > #fedora-meeting-1 . Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-07/fedora-meeting… or http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-07/fedora-meeting… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-07/fedora-meeting…

1 0

Server WG Meeting Minutes (2014-01-07)
by Stephen Gallagher 07 Jan '14

07 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =================================================================== #fedora-meeting-1: Server Working Group Weekly Meeting (2014-01-07) =================================================================== Meeting started by sgallagh at 16:01:05 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2014-01-07/fedora-meeting… . Meeting summary - --------------- * roll call (sgallagh, 16:01:18) * Server Role Requirements (sgallagh, 16:05:38) * LINK: https://www.piratepad.ca/p/serverwg-roles-proposal (mizmo, 16:10:13) * LINK: https://pad.riseup.net/p/serverwg-roles-proposal (davidstrauss, 16:10:47) Meeting ended at 17:37:40 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * sgallagh (146) * simo (91) * mizmo (66) * mitr (55) * rdoty (34) * davidstrauss (27) * nirik (26) * zodbot (9) * adamw (5) * tuanta (5) * jwb (4) * Evolution (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLMO9sACgkQeiVVYja6o6MfSwCfdfthKvaVcQ/IzsOt+oUdJnL/ upwAnRm6QQFZFBeipEGIgfgYErD4GdDG =Lz4r -----END PGP SIGNATURE-----

1 0

Re: Agenda for today's Env-and-Stacks WG meeting (2013-12-17)
by Marcela Mašláňová 07 Jan '14

07 Jan '14

============================================ #fedora-meeting: env and stacks (2014-01-07) ============================================ Meeting started by mmaslano at 13:00:41 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-07/env_and_stacks.2… . Meeting summary --------------- * init process (mmaslano, 13:01:15) * PRD (mmaslano, 13:04:16) * https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD (mmaslano, 13:04:20) * ACTION: tomorrow will be finished first draft (mmaslano, 14:17:39) Meeting ended at 14:17:43 UTC. Action Items ------------ * tomorrow will be finished first draft Action Items, by person ----------------------- * **UNASSIGNED** * tomorrow will be finished first draft People Present (lines said) --------------------------- * tjanez (42) * juhp_ (37) * mmaslano (28) * samkottler (14) * hhorak (10) * bkabrda (6) * pkovar (5) * pingou (4) * zodbot (4) * pkovar1 (2) * sochotni (2) * hhorak1 (1) * abadger1999 (0) * juhp (0) * handsome_pirate (0) 13:00:41 <mmaslano> #startmeeting env and stacks (2014-01-07) 13:00:41 <zodbot> Meeting started Tue Jan 7 13:00:41 2014 UTC. The chair is mmaslano. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:41 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:00:51 <mmaslano> #meetingname env and stacks 13:00:51 <zodbot> The meeting name has been set to 'env_and_stacks' 13:01:07 <mmaslano> #chair abadger1999 pkovar tjanez samkottler bkabrda handsome_pirate hhorak juhp 13:01:07 <zodbot> Current chairs: abadger1999 bkabrda handsome_pirate hhorak juhp mmaslano pkovar samkottler tjanez 13:01:15 <mmaslano> #topic init process 13:01:18 * samkottler is here 13:01:28 <juhp_> hi 13:01:31 <tjanez> Hi 13:02:19 <bkabrda> hi 13:02:22 <pkovar> hi there 13:02:53 <mmaslano> hi guys 13:02:57 <hhorak1> Hi 13:04:16 <mmaslano> #topic PRD 13:04:20 <mmaslano> #info https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD 13:06:05 <mmaslano> did you have time to read it? 13:06:30 <samkottler> I've gone through it a bit, I think one big gap is that we don't have user stories 13:06:44 <mmaslano> feel free to define them 13:07:40 <tjanez> samkottler: I was thinking about it since I had a homework last to time to summarize the Big Data SIG use case 13:08:42 <tjanez> Should we have an additional section in the PRD for Use cases? 13:08:52 <tjanez> Or should we emulate Personas? 13:09:58 <juhp_> probably use cases would be ok? 13:11:31 <hhorak> I guess use cases could be part of the particular taks' definition, I don't think we have some general group use cases, do we? 13:12:06 <pkovar> hhorak, +1 13:13:49 <tjanez> hhorak, your proposal is probably ok for simpler use cases, but a more complex description of, for example, what the Big Data SIG wishes from our WG should be described separately 13:15:04 <bkabrda> tjanez: but if the Big Data SIG wants that, they should provide use cases and we should think about how we solve them, right? 13:16:11 <mmaslano> tjanez: if I remember correctly, they wanted scl 13:16:21 <tjanez> bkabrda, agreed. That's why I was in favor of having a separate section in the PRD. 13:17:30 <tjanez> mmaslano, they want a way to provide language ecosystems in fedora that aligns w/ how the language itself is used 13:17:37 <juhp_> I think the PRD tasks list looks pretty good - though maybe a bit ambitious of one year :) 13:17:47 <juhp_> of = for 13:18:11 <tjanez> SCLs are a part of the solution 13:18:11 <hhorak> tjanez: if these use cases are covered by more tasks, then yes. But I don't think we have such general use cases right now. 13:18:26 <mmaslano> tjanez: I'm not against their usecase, but I guess we don't have time to create so many Personnas as Server did 13:18:48 <tjanez> Ok, I agree it would look a bit odd to only have one use case 13:19:12 <mmaslano> tjanez: feel free to add it. I don't think we have people for doing more 13:19:13 <tjanez> in that case it would be better to put it as an example under one task 13:20:11 <mmaslano> samkottler: do you have more usecases on your mind? 13:20:24 <mmaslano> samkottler: um user stories? 13:20:28 <samkottler> I think the main ones from my perspective are: 13:20:37 <samkottler> 1) the big data stuff they've asked for 13:20:50 <samkottler> 2) the 'developer who deploys code' use case 13:21:12 <samkottler> 3) people who want to redistribute applications using SCL 13:21:32 <samkottler> there are a lot more, but those are the main overview ones 13:24:05 <mmaslano> samkottler: can you add it there? 13:24:20 <tjanez> I agree that the PRD task lisk is pretty big. Do we want to eliminate the tasks that we deem not to important / out-of-scope or do we want to put "everything we came up with" in the PRD? 13:24:21 <samkottler> mmaslano: yeah, I'll write up my thoughts on it after the meeting 13:24:43 <samkottler> tjanez: I think we can remove very specific stuff and just make it high level 13:25:16 <tjanez> samkottler, I have something for the big data stuff user story in mind. Want me to take it? 13:25:28 <samkottler> tjanez: sounds good 13:25:37 <samkottler> or we can talk after and figure out where things overlap and go from there 13:25:38 <juhp_> samkottler, I agree good to have user stories to motivate the task list 13:26:25 <tjanez> samkottler, ok 13:26:41 <hhorak> tjanez: Some kind of highlighting was also on my mind -- at least labeling some tasks as important and consider the rest as nice to have 13:26:49 <juhp_> there might be some user stories in the Workstation PRD too - eg developers wanting latest stacks etc 13:27:02 <samkottler> well the PRD shouldn't really be a task list, it should be a document showing our purpose 13:27:10 <samkottler> tasks can be defined completely outside of that 13:27:15 <juhp_> true 13:27:52 <tjanez> hhorak, yes that would be good. We don't want to promise too much and then underdeliver 13:28:54 <hhorak> samkottler: I agree, but what we have that is actually what I'd expect, just call it differently than "tasks", maybe "goals"? 13:29:09 <samkottler> hhorak: +1 to goals 13:29:15 <juhp_> I will probably re-read the draft Workstation PRD and can try to pick out any potential user stories for this WG at the same time 13:29:16 <tjanez> samkottler, I agree with you that our PRD should also include a paragraph about the general purpose of our WG 13:30:06 <juhp_> yeah Goals sounds better probably 13:30:19 <tjanez> +1 for goals 13:30:51 <juhp_> we can break out more detail tasks etc latter based on the Goals list :) 13:32:23 <tjanez> Regarding the purpose/aim of our WG, I have two proposals: 13:32:29 <tjanez> Our WG incubates ideas, some will be later abandoned, some will be re-iterated and formalized and then put into Fedora *proper* (we also need to define Fedora *proper*) 13:32:35 <tjanez> 2) We are working on enabling new things (including new ways to get Fedora, new things that are Fedora) 13:32:45 <tjanez> Both are from our previous IRC meetings 13:36:36 <juhp_> I missed the last meetings last month so may be missing some context, but personally I feel more excited and motivated by (2) 13:37:45 <hhorak> tjanez: I understand "proper" as "stable" 13:39:37 <juhp_> do we have a deadline for the current scoping/planning phase or for the "PRD" at least? 13:40:02 <hhorak> juhp_ I guess the deadline is on Monday 13:40:20 <juhp_> ok right 13:40:28 <tjanez> hhorak, "stable" is probably also too vague. I was thinking more in terms of "Officially released and endorsed (supported?) by the Fedora Project." 13:40:32 <pkovar> yep, it should be jan 13 13:41:20 <juhp_> official Fedora 13:42:10 <hhorak> tjanez: juhp_: that seems fine to me 13:42:31 <juhp_> so we probably need a draft ready within the next couple of days for final review? 13:43:06 <mmaslano> yes 13:44:23 <tjanez> Should we leave the task list as it is and work on polishing the PRD or do we want to shorten it, pick focus? 13:45:56 <mmaslano> tjanez: mostly there are listed tasks, which have dedicated developer 13:45:57 <bkabrda> tjanez: I'm for shortening. let's leave out the things that are marked as "out of scope" (CI, scl-utils v2) 13:47:48 <hhorak> bkabrda: I'd rather leave it there, maybe move it to special category "out of scope", since otherwise somebody can come up with the same topic in a year again and again, while not knowing that it is out of scope.. 13:48:22 <pkovar> yes, that makes sense 13:48:44 <bkabrda> hhorak: sounds good 13:48:51 <pkovar> i think a special section at the bottom can't hurt 13:49:42 <juhp_> so should we add a Goals section? 13:50:18 <tjanez> juhp_, I though we want to rename the Tasks section to Goals 13:51:50 <juhp_> yes 13:51:57 <juhp_> just checking :) 13:52:36 <tjanez> ok :) 13:52:57 <mmaslano> so, when do you plan to finish it? 13:53:12 <mmaslano> because we should approve it before saying it's okay 13:53:19 <juhp_> right 13:54:04 <juhp_> we might need a couple of rounds of drafts - time is certainly short 13:55:14 <hhorak> If we want to label some tasks/goals as our priority, I'd propose those that have some requirement already: taskotron, scls, copr, documentation for scl 13:55:38 <juhp_> +1 13:56:10 <mmaslano> +1 13:56:14 <tjanez> hhorak, +1 13:56:48 <juhp_> I like some of the Automation stuff too 13:57:49 <juhp_> but I agree focusing is good 13:58:06 <tjanez> If pingou plans on working on "Automated package review tools", we could also mark that as a pripority 13:58:18 <juhp_> ah yeah 14:00:35 <tjanez> Some parts of the Tasks/Goals list seem to terse to me (e.g. Build systems, SCL). Does anyone share that opinion? 14:01:20 <juhp_> so can we have a final draft ready by Thursday so we can all vote/approve it by Friday hopefully? 14:01:26 <juhp_> tjanez, I tend to agree 14:02:00 <juhp_> probably good to reword some of it after changing Tasks to Goals 14:02:15 <tjanez> juhp_, +1 for Thursday 14:03:22 <juhp_> or is Thu too late? well maybe we need a initial draft for review tomorrow? 14:03:58 <tjanez> juhp_, yes, we need to polish the wording and make it understandable for someone not coming from our WG (Fedora even). 14:03:58 <mmaslano> I'm fine with Thursday, but I already wrote what I want 14:04:44 <juhp_> mmaslano, okay :) 14:06:03 <juhp_> mmaslano, it is ok for us to edit that page right? :) 14:06:36 <mmaslano> right 14:06:47 <tjanez> I don't know enough about the details of the Build systems, SCLs and CI, but I would ask someone knowledgeable to expand and clarify those parts 14:07:20 <juhp_> probably good if people can post to the mailing list after making larger changes to it anyway - I will try to keep an eye on the page and also help with editing 14:07:38 <juhp_> tjanez, +1 14:07:53 <tjanez> CI is probably not critical, since it will be put in the Out-of-scope section, right 14:08:03 <pkovar1> (i can also help with editing) 14:08:04 <pingou> tjanez: my idea was about moving the packge review off bugzilla and integrate it with fedora-review, so "tools" might be a little excessive :) 14:08:43 <tjanez> pingou, thanks for dropping in :) 14:08:47 <pingou> sure thing 14:08:55 <mmaslano> pingou: sounds lovely 14:09:18 <pingou> mmaslano: gotta say, I've had the idea for a little while :] 14:09:19 <tjanez> well, feel free to edit that part of the PRD. I wrote it based on the email by sochotni 14:10:14 <tjanez> I put a general term "Automated package review tools" in the PRD, since PRDs are suppose to be general 14:10:35 <juhp_> and for things we think should be changed/updated/expanded maybe good to post specific suggestions/question to the ml to get attention 14:10:47 <pingou> tjanez: well that part seems like a nice TODO list for the tool :D 14:11:22 <tjanez> pingou: yes, I agree :) 14:12:23 <tjanez> juhp_: yes, it's probably best to highlight the "controversial" parts and discuss them on the ML 14:13:03 <mmaslano> could someone finish meeting instead of me? I have to go to another meeting 14:13:49 <tjanez> mmaslano, I can finish it, just tell me where to find a cheat-sheet for the commands 14:13:50 <juhp_> tjanez, right or like you said things one is unsure about 14:14:25 * bkabrda needs to go, too 14:14:51 <sochotni> tjanez: https://wiki.debian.org/MeetBot 14:15:13 <sochotni> at least I think so :-0 14:15:25 <tjanez> sochotni, thanks 14:16:11 <tjanez> Well, do we agree that the first draft should be ready tomorrow? 14:16:16 <mmaslano> +1 14:16:20 <tjanez> And the final draft on Thursday 14:16:25 <juhp_> +1 14:16:31 <hhorak> +1 14:16:32 <juhp_> sounds good to me 14:16:35 <bkabrda> +1 14:16:47 <mmaslano> or do you want to close meeting right now? 14:16:55 <tjanez> +1 14:17:00 <tjanez> mmaslano, you can close 14:17:04 <juhp_> +1 14:17:13 <pkovar1> +1 14:17:39 <mmaslano> #action tomorrow will be finished first draft 14:17:43 <mmaslano> #endmeeting

1 0

Fedora Marketing Meeting 6/1/13 Minutes
by Zacharias Mitzelos 06 Jan '14

06 Jan '14

Hey all, We had another Marketing meeting today, you can read the meeting minutes below: Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-06/fedora-meeting.2… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-01-06/fedora-meeting.2… Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-01-06/fedora-meeting.2… Warm Regards, Zacharias (mitzie)

1 0

FAmSCo meeting minutes 2013-01-06
by Jiri Eischmann 06 Jan '14

06 Jan '14

Hi, we had another FAmSCo meeting today. 5 out of 7 members attended. Main points from the meeting: * Christop Wickert will be the wrangler for FAmSCo elections. The nomination phase will be from Jan 8th to 13th. * Deadline for final versions of regional budgets for fiscal year 2015 is January 31st. * The only bid for FUDCon LATAM 2014 is Managua, Nicaragua. Flock 2014 will be in Prague. You find more in the minutes: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-06/famsco.2014-01… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-06/famsco.2014-01… Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2014-01-06/famsco.2014-01… The next meeting will be on January 13th. Meet you next week! Jiri

1 0

2014-01-06 - Fedora QA Meeting - minutes
by Adam Williamson 06 Jan '14

06 Jan '14

>From this week onwards, we have agreed to abandon the laboriously hand-edited minutes and per-meeting Wiki pages. From now on, we will simply send out the MeetBot-generated meeting minutes, and link to those from the https://fedoraproject.org/wiki/QA/Meetings . Future minutes emails will contain the bare text format minutes generated by Meetbot, as seen below. I'd actually quite like to use the HTML format minutes - http://meetbot.fedoraproject.org/fedora-meeting/2014-01-06/fedora-qa.2014-0… - as they're much easier to read, but anti-HTML-email sentiment is so embedded by now that this is likely impractical. ================================== #fedora-meeting: Fedora QA meeting ================================== Meeting started by adamw at 16:00:04 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-06/fedora-qa.2014-0… . Meeting summary --------------- * Roll call (adamw, 16:00:11) * Previous meeting follow-up (adamw, 16:11:20) * "adamw to send fedup/thinp post-mortem email" - I sent one - https://lists.fedoraproject.org/pipermail/test/2013-December/119820.html - but didn't cover the thinp bug, whoops (adamw, 16:13:20) * QA/Join page revision (adamw, 16:20:12) * LINK: https://lists.fedoraproject.org/pipermail/test/2014-January/119890.html (adamw, 16:20:41) * roshi and danofsatx came up with a proposal for a revised QA/Join page (adamw, 16:20:54) * roshi will send out a new draft based on list feedback (adamw, 16:21:18) * general agreement to try and avoid mentioning 'bugzappers' and 'proven testers' directly to avoid confusion (adamw, 16:22:56) * seems like everyone's happy with the current approach to the rewrite, thanks for the work roshi and danofsatx (adamw, 16:24:50) * Meeting minutes (adamw, 16:27:14) * currently we keep meeting minutes in a hand-written format at https://fedoraproject.org/wiki/QA/Meetings (adamw, 16:30:39) * the wiki meeting pages are usually created before the meeting and in theory can be edited to add something to the agenda (adamw, 16:34:03) * AGREED: from 2014 on, we'll drop the manual handling of meeting minutes and do it all via meetbot (adamw, 16:35:41) * side note: kparal has added the meeting schedule to fedocal for 2014 (adamw, 16:36:41) * fedocal link for QA: https://apps.fedoraproject.org/calendar/QA/ (adamw, 16:38:08) * open floor (adamw, 16:40:07) * LINK: http://tools.ietf.org/html/rfc2445 (cmurf, 16:40:13) * LINK: http://tools.ietf.org/html/rfc6868 (cmurf, 16:41:15) * Viking-Ice points out Matthew Miller's mail about plans for 2014, https://lists.fedoraproject.org/pipermail/devel/2014-January/193401.html (adamw, 16:43:58) * ACTION: adamw to send a mail to test@ about the ten year t-shirt thing (adamw, 17:00:13) * once again, we all registered concern at the direction of the Fedora.next project and its implications for testing given the apparent broadening of the scope of deliverables without a plan in place for testing (adamw, 17:04:30) Meeting ended at 17:05:52 UTC. Action Items ------------ * adamw to send a mail to test@ about the ten year t-shirt thing Action Items, by person ----------------------- * adamw * adamw to send a mail to test@ about the ten year t-shirt thing * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * adamw (123) * handsome_pirate (70) * cmurf (63) * Viking-Ice (55) * roshi (50) * tflink (40) * jokerdino (23) * kparal (22) * danofsatx (20) * brunowolff (17) * nirik (14) * zodbot (8) * pingou (4) * satellit (4) * jreznik (4) * nb (2) * mkrizek (1) * pwhalen (1) * satellit_e (1) * pschindl (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

meetingminutes January 2014