Summary/Minutes from today's Fedora Infrastructure meeting (2013-04-04)
by Kevin Fenzi
============================================
#fedora-meeting: Infrastructure (2013-04-04)
============================================
Meeting started by nirik at 19:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-04-04/infrastructure...
.
Meeting summary
---------------
* welcome y'all (nirik, 19:00:02)
* New folks introductions and Apprentice tasks. (nirik, 19:01:18)
* Applications status / discussion (nirik, 19:04:33)
* Sysadmin status / discussion (nirik, 19:20:15)
* LINK: http://infrastructure.fedoraproject.org/infra/docs/arm.txt
(nirik, 19:21:27)
* LINK:
http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playlets/RE...
(skvidal, 19:32:04)
* LINK: http://paste.fedoraproject.org/6712/10399613/ (skvidal,
19:33:20)
* Private Cloud status update / discussion (nirik, 19:34:10)
* Freezes (nirik, 19:40:26)
* Upcoming Tasks/Items (nirik, 19:51:21)
* 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik,
19:51:35)
* 2013-04-15 - remove legacy-openid (nirik, 19:51:36)
* 2013-04-15 - announce openid change on hosted. (nirik, 19:51:36)
* 2013-04-16 F19 alpha release (nirik, 19:51:36)
* 2013-04-17 - switch to new sigul servers. (nirik, 19:51:36)
* 2013-04-19 - switch hosted to openid (nirik, 19:51:37)
* 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik,
19:51:38)
* 2013-05-21 F19 beta release (nirik, 19:51:40)
* 2013-05-31 end of 1st quarter (nirik, 19:51:42)
* 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik,
19:51:44)
* 2013-06-25 F19 FINAL release (nirik, 19:51:46)
* Open Floor (nirik, 19:52:34)
Meeting ended at 19:58:14 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (139)
* skvidal (106)
* abadger1999 (36)
* pingou (20)
* threebean (16)
* oddshocks (7)
* zodbot (4)
* dgilmore (4)
* fchiulli (2)
* lmacken (2)
* smooge (2)
* Smoother1rOgZ (1)
* relrod (1)
* rossdylan (1)
* ricky (0)
* mdomsch (0)
* CodeBlock (0)
--
19:00:01 <nirik> #startmeeting Infrastructure (2013-04-04)
19:00:01 <zodbot> Meeting started Thu Apr 4 19:00:01 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:01 <nirik> #meetingname infrastructure
19:00:01 <zodbot> The meeting name has been set to 'infrastructure'
19:00:02 <nirik> #topic welcome y'all
19:00:02 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean
19:00:02 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean
19:00:19 * skvidal is here
19:00:25 * pingou here
19:00:26 * lmacken here for 15m
19:00:33 * relrod here
19:00:37 * threebean is here
19:00:52 * fchiulli is listening
19:01:18 <nirik> #topic New folks introductions and Apprentice tasks.
19:01:19 <smooge> is here
19:01:29 <nirik> any new folks or apprentices with questions or comments?
19:01:41 <nirik> oddshocks: you wanted to introduce yourself? ;)
19:01:44 * oddshocks is new!
19:01:52 <threebean> :P
19:02:09 <oddshocks> Hey everyone, I just sent out a mailing list introduction, I'm an IT student and free software hacker from RIT hoping to get involved with things around here :)
19:02:17 <oddshocks> potential Red Hat intern for the Summer
19:02:19 <skvidal> oddshocks: welcome
19:02:21 <oddshocks> nice to meet you all :)
19:02:23 <lmacken> welcome :)
19:02:28 <rossdylan> hye oddshocks :p
19:02:28 <nirik> welcome oddshocks
19:02:30 <pingou> nice, welcome :)
19:02:38 <nirik> you more interested in sysadmin or software devel?
19:03:35 <oddshocks> I'm still kinda on the fence, but systems administration catches my eye a bit more
19:03:51 <nirik> sure, you could also help out in both time and focus permitting. ;)
19:04:16 <oddshocks> I like writing code and I also like working with systems, so yeah
19:04:20 <nirik> anyhow, welcome and do see us after the meeting in #fedora-admin / #fedora-apps and we can point you at where to get started.
19:04:27 <oddshocks> Perfect, thanks!
19:04:33 <nirik> #topic Applications status / discussion
19:04:46 <nirik> any applications news? Note that we are in alpha freeze right now.
19:04:55 <abadger1999> wanna talk about gsoc here or open floor?
19:05:18 * pingou worked on pkgdb2 still
19:05:21 <nirik> either way. ;)
19:05:24 <pingou> I let threebean mention tagger :)
19:05:32 * threebean mentions tagger
19:05:47 * nirik will have a seperate topic about freeze discussions after apps/sysadmin ones.
19:06:01 <threebean> :P
19:06:11 <pingou> that was easy ;)
19:06:28 <abadger1999> GSoC is Google Summer of Code. It's coming up soon and Fedora has applied. We've already had students interested in working on infra come to find us in irc. What we really need to pull this off, though, is mentors.
19:06:30 <threebean> tagger dev work is getting close to something we could put in staging. early next week at the earliest.
19:06:52 <nirik> cool.
19:07:04 <nirik> abadger1999: yeah, most of us are pretty strapped for time tho. ;(
19:07:13 <abadger1999> Most of the usual suspects are busy this year (lmacken, myself, nirik, skvidal, pingou, etc).
19:07:15 <pingou> threebean: btw we should update the dev instance with the python-fedora from abadger1999 so we can start checking it
19:07:27 <skvidal> abadger1999: additionally i'm a terrible mentor
19:07:33 <threebean> pingou: oh yeah, let's set that up in #fedora-apps post meeting
19:07:45 <pingou> threebean: cool
19:07:49 <pingou> skvidal: really? :)
19:07:59 <nirik> abadger1999: some of the items are not really directly needing mentors from us... the gitlab thing could well be mostly packaging.
19:08:01 <abadger1999> I sent a request to the infra list for mentors to raise their hands if they want to work on something but so far no replies.
19:08:02 <skvidal> pingou: no need for you to mock
19:08:07 <abadger1999> <nod>
19:08:18 <threebean> ...chain.py!
19:08:47 <abadger1999> nirik: although... being useful to infra would make it more likely to be accepted.
19:08:51 <pingou> wrt GSoC: tbh, there has been some people that looked very motivated, it kind of makes me want to help them
19:08:58 <abadger1999> <nod>
19:09:01 <nirik> it's a bit difficult in that ideas on the page are submitted by anyone without infra really looking or saying they would like them. Perhaps next year we could be more proactive and prune ideas to ones we really would like and that might get more mentors involved.
19:09:21 <abadger1999> Yeah, biker has showed up a number of times and been pretty enthusiastic.
19:09:40 <pingou> skvidal: honestly, I wasn't
19:09:46 <nirik> yeah, agreed.
19:09:49 <abadger1999> He wondered about doing a unittesting GSoC... I'd be willing to partially mentor that.
19:10:03 <nirik> biker was also interested in any other ideas too... wasn't set on the ideas page ones.
19:10:07 <skvidal> pingou: SSSSSSSSSSSSSURRE you weren't :)
19:10:08 <abadger1999> <nod>
19:10:13 <pingou> skvidal: no really :)
19:10:32 <pingou> GSoC: pkgdb2? Elections?
19:10:32 <nirik> I've seen a lot of interest in gitlab and unit testing for fedpkg...
19:10:48 <pingou> start porting to ansible?
19:11:02 <pingou> MirrorManager?
19:11:02 <abadger1999> elections, fchiulli is managing... pretty far along -- but from the hours that he's available I don't htink he can mentor.
19:11:31 <nirik> I don't think mdomsch has time to mentor for mm... and not sure anyone else is up to speed enough yet.
19:11:33 * fchiulli is not available much during the day. Nights vary
19:11:49 <abadger1999> mirrormanager needs a new driver since mdomsch has less time. Without a driver, gsoc contributions are likely to not get merged.
19:11:58 <abadger1999> <nod>
19:12:19 <nirik> would anyone be willing to co-mentor with abadger1999 on unittesting?
19:12:21 <abadger1999> ansible would be good -- but that would need a sysadmin mentor... and you guys are all pretty tapped, right?
19:12:23 <nirik> perhaps thats one we could do?
19:13:21 <pingou> abadger1999: well I did work quite a bit trying to port MM to TG2
19:13:23 <nirik> the problem with the ansible side is that a lot of it is just deciding how we want to organize things... I'm not sure what GSoC folks could do there until we have more things in place and then not sure how exciting it would be. and yeah, time...
19:13:30 <abadger1999> <<nod>
19:13:40 <abadger1999> pingou: Want to take ownership?
19:14:01 <nirik> we still need to get mm1.4 into production.
19:14:06 <nirik> and fix issues with it.
19:14:06 <abadger1999> pingou: heh -- if you aren't careful, you'll end up with ownership of pkgdb as well ;-)
19:14:18 <pingou> abadger1999: I can deal w/ pkgdb more than MM :)
19:14:36 <pingou> abadger1999: but don't think you're out of the loop ;-)
19:14:50 <abadger1999> darn! ;-)
19:15:25 <nirik> so, where does that leave us? ;)
19:15:30 <abadger1999> anyhow -- if anyone wants to step up to mentor, I can co-mentor unittesting python-fedora and some other things.
19:15:50 <abadger1999> can't do it alone.
19:15:57 <pingou> pkgdb2 is an option?
19:16:08 <dgilmore> nirik: it would be awesome for some mm love
19:16:31 <nirik> sure, but without a driver on it, not sure GSoC would help us any
19:16:46 <dgilmore> yeah
19:16:53 <abadger1999> pingou: yes and no. If you want to mentor that I can help you --- but I wouldn't want to be primary mentor for that this summer.
19:16:54 * Smoother1rOgZ is around
19:17:26 <pingou> abadger1999: and I shouldn't (not that I wouldn't)
19:17:30 <abadger1999> hehe :-)
19:17:34 <abadger1999> understood :-)
19:17:50 <nirik> ok, well, lets keep discussing and see if we can offer anything...
19:17:54 <nirik> any other application news?
19:18:10 <abadger1999> python-fedora alpha is in infra; surprisingly stable.
19:18:21 <threebean> cool :) stg or prod?
19:18:22 <abadger1999> I just sent a change request to fix a few bugs.
19:18:28 <abadger1999> threebean: prod
19:18:30 <threebean> awesome
19:18:50 <abadger1999> working on a pkgdb update (pingou's slimming of the api and db)
19:18:51 <nirik> cool.
19:18:58 <abadger1999> will go to stg next week I hope
19:19:00 <nirik> that would be after alpha?
19:19:04 <nirik> (for prod
19:19:05 <nirik> )
19:19:16 <abadger1999> and figuring out how to make otp fit into the python-fedora api
19:19:22 <abadger1999> nirik: correct.
19:19:25 <nirik> fun times. ;)
19:19:41 <threebean> good news: I've heard no negative feedback after tuesday's freeze break request - http://lists.fedoraproject.org/pipermail/infrastructure/2013-April/012724...
19:19:42 <nirik> ok, moving along to sysadmin...
19:19:53 <nirik> threebean: yeah, seems ok, but the None's are weird.
19:19:57 * threebean nods
19:20:14 <threebean> those are omitted from the ircbot messages in git... coming down the pipe.
19:20:15 <nirik> #topic Sysadmin status / discussion
19:20:35 <nirik> threebean: yeah
19:20:41 <nirik> so, on the sysadmin side of things...
19:21:08 <nirik> we have 3/4ths of our arm SOC's on line and I will be redoing the other one soon when switch ports are changed on it.
19:21:18 <nirik> I created a sop for dealing with the arm socs:
19:21:27 <nirik> http://infrastructure.fedoraproject.org/infra/docs/arm.txt
19:21:56 <dgilmore> nirik: :) many thanks
19:22:11 <nirik> no problem. Nice to see them finally cranking away.
19:22:36 <nirik> I will likely request a freeze break in a bit for updating postgresql... might need a short outage for it.
19:23:21 <nirik> bnfs01 (our backup storage box) is hosed again. smooge was looking into it.
19:23:41 <nirik> we are finalizing our new netapp storage now, hopefully will have some in a while.
19:23:54 <smooge> it is not looking good
19:24:01 <nirik> smooge: ;(
19:24:22 <nirik> any other sysadmin stuff?
19:24:29 * skvidal has been working on ansible-y stuff
19:24:38 <skvidal> the cron-runner
19:24:40 <abadger1999> postgres update -- no dump and reload needed right?
19:24:41 <nirik> oh, I was thinking we should add monitoring for the arm boxes at some point. I might file a ticket on that and let someone else do it. ;)
19:24:46 <skvidal> the freezes thing (which uncovered a bug)
19:24:51 <nirik> abadger1999: correct. just update and restart
19:24:56 <abadger1999> cool.
19:25:34 <nirik> skvidal: so, were we going to do cron there? or triggered by commit? (or jury still out)?
19:25:45 <skvidal> nirik: well the script is the same, ultimately
19:25:52 <skvidal> so...
19:25:58 <nirik> yeah.
19:25:59 <skvidal> one way or the other we need to be able to say
19:26:09 <skvidal> 'these hosts or groups' - run the playbook for them and don't overlap
19:26:14 <nirik> I don't know if we can get ansible to say 'this commit affects these hosts'
19:26:17 <skvidal> run them forked off - multiple in parallel at a time
19:26:25 <nirik> yeah.
19:26:26 <skvidal> nirik: we can for playbooks, we can't, easily, for files
19:26:46 <nirik> ah. ok.
19:26:48 <skvidal> nirik: for tasks it is.... theoretically... possible - but there will be a lot of grepping involved
19:26:56 <pingou> speaking of ansible, do we finally have an idea how we want to handle stg/prod?
19:27:08 <nirik> yeah, we will just need to look at where we want to draw the line probibly.
19:27:36 <nirik> pingou: we did come up with a plan. ;) But it's not sure yet that it will work, so we need to test it...
19:27:41 <skvidal> :)
19:27:50 <nirik> basically similar to how we do it in puppet... a path for things.
19:28:05 <skvidal> that plugin should work - right now the issue is this
19:28:16 <nirik> skvidal: that was pulled into 1.1? or no?
19:28:20 <skvidal> nirik: pretty sure
19:28:22 <skvidal> lemme verify
19:28:37 <skvidal> yep
19:28:40 <skvidal> first_found lookup plugin
19:28:58 <skvidal> so - there are 2 things here, really
19:29:08 * nirik did update lockbox01 to 1.1
19:29:23 <skvidal> the playlets idea that I came up with is.... not very attractive unless we can make it easy to use in an existing playbook
19:29:42 <skvidal> in many case we can make-do w/o needing those playlets - just with included tasks
19:29:55 <skvidal> but I'm trying to figure out which cases where tasks will make it more confusing to use
19:29:56 <nirik> yeah.
19:30:11 <skvidal> in most of the cases I can think of
19:30:11 <nirik> yeah, I figure we will need to try things and adjust.
19:30:20 <skvidal> it's just where the variable includes would be ugly in every playbook
19:30:24 <skvidal> and you really just want to say
19:30:37 <skvidal> "you know that last group of hosts you ran against?"
19:30:48 <skvidal> "run this playbook over here, against them and only them"
19:31:38 <skvidal> if anyone wants to talk about this with me sometime
19:31:47 <skvidal> I think I could really use someone to bounce this back and forth with
19:32:04 <skvidal> http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playlets/RE...
19:32:06 <skvidal> this is the idea
19:32:18 <threebean> cool -- I'll queue it up for reading
19:32:24 <skvidal> and then
19:32:41 <nirik> yeah, lots of ways to do things... ;)
19:33:20 <skvidal> http://paste.fedoraproject.org/6712/10399613/
19:33:36 <nirik> ok, lets keep poking at it. ;) I'd like to add arm-releng to ansible repo soon so I can try and work out in reality how things will look
19:33:45 <skvidal> yah
19:33:59 <skvidal> did we already do cloud stuff?
19:34:00 <nirik> any other sysadmin stuff anyone has?
19:34:03 <nirik> not yet. ;)
19:34:05 <skvidal> ok
19:34:10 <nirik> #topic Private Cloud status update / discussion
19:34:14 <nirik> now. go! :)
19:34:18 <skvidal> heh
19:34:28 <skvidal> so I'd like to add a new ip range to the openstack cloudlet
19:34:42 <nirik> sounds good. are we ready to add more compute nodes too?
19:34:42 <skvidal> I'm almost positive that the command I want to run won't break the existing network ip range ;)
19:34:47 <skvidal> nirik: we are
19:35:02 <nirik> if it does... oh well, we do the best we can. ;)
19:35:02 <skvidal> fed-cloud05 and 07 need to be reformatted
19:35:16 <skvidal> but they are not doing anything now
19:35:33 <skvidal> so anyone in sysadmin-main who would like to kick them should feel free
19:35:47 <nirik> cool.
19:35:59 <skvidal> also
19:36:02 <nirik> adding compute nodes is super easy too... nova.conf and a few packages and away you go.
19:36:16 <skvidal> 01 and 03 should be ready to be turned over to grizzly if anyone would like to do that
19:36:29 <nirik> excellent.
19:36:32 <skvidal> this is sorta-cloud
19:36:52 <skvidal> I played with systemd-nspawn a bit and what it can do
19:37:12 <nirik> oh yeah. f18?
19:37:16 <skvidal> and I think if anyone would like to tinker with infrastructure/scripting/etc for that on a big fedora 18 cloud instance
19:37:27 <skvidal> it would be something that will eventually be useful to us
19:37:31 <skvidal> us == fedora infra
19:37:37 <nirik> yeah, I agree.
19:37:45 <skvidal> it is also completely bluesky afaict
19:37:51 <skvidal> so if you want to noodle around with it
19:37:54 * nirik nods.
19:37:58 <threebean> bluesky?
19:38:07 <skvidal> threebean: go, play, doesn't matter if nothing comes of it
19:38:10 <skvidal> threebean: no constraints
19:38:15 <nirik> not ready for real use right now, by someday... perhaps...
19:38:24 <threebean> ok, thanks
19:38:29 <skvidal> so a nspawn is a container
19:38:35 <skvidal> forming one up is easy
19:38:47 <nirik> I think the big things around it would be: managing them, and networking.
19:38:51 <skvidal> yum --installroot=/some/path install @core
19:39:09 <skvidal> systemd-nspawn -D /some/path -b
19:39:17 <skvidal> and then you're in the chroot, lickety-split
19:39:51 <nirik> yep.
19:40:00 <skvidal> anyway - if anyone wants to do that
19:40:04 <skvidal> yell at one of us
19:40:10 <skvidal> and we can spin up an f18 instance quickly
19:40:20 <nirik> sounds good.
19:40:26 <nirik> #topic Freezes
19:40:29 <skvidal> brrr
19:40:35 <nirik> so, we are in a freeze for alpha now...
19:40:43 <nirik> and the topic came up how we determine whats frozen, etc.
19:40:47 <nirik> (see post on list)
19:41:29 <nirik> would anyone like to make a case for more hosts NOT being frozen than dev/stg ? or some way to decide those?
19:41:48 <skvidal> nirik: there's one example of a host-specifically marked as freezes:false
19:41:51 <skvidal> people03.fedoraproject.org
19:42:01 <skvidal> adding additional ones like that to the inventory is really easy
19:42:22 <skvidal> nirik: actually - this brings up a question
19:42:32 <skvidal> nirik: right now we have the inventory inside the public ansible repo
19:42:33 <nirik> sure... but I was meaning from a standpoint of critera.
19:42:38 <abadger1999> for alpha/beta or final or both?
19:42:45 <skvidal> abadger1999: I think for all
19:42:50 <nirik> abadger1999: both, either... ;)
19:43:07 <nirik> I'd like to have a critera we can hold a host up to and see if it should be frozen or not.
19:43:26 <nirik> a very simple one would be: is the host *stg* or *dev* ?
19:43:35 <nirik> but that means a lot more things are frozen than were before.
19:43:55 <abadger1999> yeah... I don't really like mor ethings frozen.
19:44:10 <skvidal> nirik: I think there is room for more non-distro-releasing-impacting things being unfrozen
19:44:29 <skvidal> people, hosted, hosted-lists,
19:44:31 <nirik> yeah, but what critera can we use. ;)
19:44:34 <skvidal> the items you mentioned in your email
19:44:38 <nirik> I posted some other attempts...
19:44:42 <skvidal> nirik: 'does it impact the ability to release the distro'
19:44:54 <nirik> well, hosted actually does impact the distro. ;)
19:45:07 <skvidal> nirik: how?
19:45:07 <nirik> comps is pulled from there.
19:45:40 <skvidal> sigh
19:45:43 <abadger1999> comps isn't mirrored into a package?
19:45:50 <nirik> anyhow, we could continue discussion on list too. :)
19:45:57 <abadger1999> i guess its repodata so no.. :-(
19:46:02 <nirik> abadger1999: no, it's pulled from git by composes...
19:46:09 <nirik> also spin-kickstarts is there.
19:46:25 <nirik> now, we could look at moving those, but right now they are there. ;0
19:46:42 <nirik> brb
19:47:22 <skvidal> yah.... I see
19:47:31 * skvidal grumbles...
19:47:34 <skvidal> okay fine
19:47:40 <skvidal> hosted-lists!
19:47:42 <dgilmore> nirik: and branched is pulled from git on fedorahosted nightly
19:48:06 <nirik> yeah, rel-eng repo too...
19:48:27 <skvidal> so - back to my earlier question
19:48:35 <nirik> anyhow, lets continue that discussion on list... for purposes of this alpha freeze, we just keep using the picture. ;)
19:48:37 <skvidal> do we want to split out the inventory subdir of the ansible repo - into its own repo
19:48:47 <nirik> skvidal: what does that get us?
19:48:51 <skvidal> so we can have people editing the inventory who might not be able to commit to ansible itself
19:49:13 <nirik> not sure thats a very common thing is it?
19:49:18 <skvidal> true enough
19:49:28 <skvidal> this is why I ask these things ;)
19:49:30 <nirik> I'd prefer to keep number of repos down if we can. ;)
19:50:05 <nirik> commit on ansible is going to be the same as commit on puppet right?
19:50:15 <nirik> which is what... sysadmin?
19:50:20 <skvidal> lemme look
19:50:34 <skvidal> yes
19:50:34 <skvidal> sysadmin
19:50:36 <skvidal> yah
19:50:38 <skvidal> you're right
19:50:43 <skvidal> I withdraw the suggestions
19:51:12 <nirik> :) of course they must be in a group that has shell on lockbox01 too...
19:51:21 <nirik> #topic Upcoming Tasks/Items
19:51:33 <nirik> here's what I have for upcoming:
19:51:35 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
19:51:36 <nirik> #info 2013-04-15 - remove legacy-openid
19:51:36 <nirik> #info 2013-04-15 - announce openid change on hosted.
19:51:36 <nirik> #info 2013-04-16 F19 alpha release
19:51:36 <nirik> #info 2013-04-17 - switch to new sigul servers.
19:51:37 <nirik> #info 2013-04-19 - switch hosted to openid
19:51:38 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
19:51:40 <nirik> #info 2013-05-21 F19 beta release
19:51:42 <nirik> #info 2013-05-31 end of 1st quarter
19:51:44 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
19:51:46 <nirik> #info 2013-06-25 F19 FINAL release
19:51:48 <nirik> any other items people would like to schedule or note?
19:52:34 <nirik> #topic Open Floor
19:52:41 <nirik> anyone have items for open floor?
19:52:58 <skvidal> nirik: one question
19:53:24 <skvidal> nirik: what were the future points for determining what to do with hosted
19:53:31 <skvidal> nirik: and making it more-better
19:53:44 <skvidal> as in - it's running right now
19:53:46 <nirik> yeah... so I think we decided on at least a short term plan...
19:53:51 <skvidal> do we just sit on it?
19:53:57 <skvidal> ah - okay -
19:54:02 <nirik> well, we could do that too I guess...
19:54:10 <nirik> I was thinking we could move it to osuosl02...
19:54:28 <nirik> (or at least all the git ones)
19:54:31 <skvidal> okay - so that's something we do plan to do.
19:54:40 <skvidal> did you decide if you wanted osuosl02 to be cloud-y or not?
19:55:15 <nirik> I was really on the fence there. I think cloud would be nice from a 'figure more stuff out' with it, but on the other hand, I don't know how much time we want to spend on hosted really...
19:55:40 <nirik> Ideally we can get it to a stablish thing and not have to deal with it again for a while.
19:56:11 <nirik> let me try and write up a plan and we can tweak it and see what all of it we want to do.
19:56:11 <skvidal> nirik: so... what does that mean?
19:56:13 <skvidal> ok
19:56:18 <skvidal> sounds round
19:56:19 <nirik> I can put it on that hosted wiki page with all the ideas.
19:56:21 <skvidal> thank you
19:56:45 <nirik> hosted02 is running ok now, but I think I'd like to move it anyhow, even if we do nothing else but move it.
19:57:19 <skvidal> cool
19:57:32 * nirik adds to his list. ;)
19:57:37 <nirik> ok, anything else ?
19:58:08 <nirik> ok, thanks for coming everyone!
19:58:09 <threebean> not from me :)
19:58:14 <nirik> #endmeeting
11 years
- 1
- 0
Summary/Minutes from today's irc support sig meeting (2013-04-04)
by Kevin Fenzi
=============================================
#fedora-meeting: IRC Support SIG (2013-04-04)
=============================================
Meeting started by nirik at 18:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-04-04/irc-support-si...
.
Meeting summary
---------------
* init process (nirik, 18:00:01)
* Week in review (nirik, 18:03:16)
* #140 failed to address a response to a user's question, then attacked
the user (nirik, 18:06:36)
* LINK: https://fedorahosted.org/irc-support-sig/ticket/140 (nirik,
18:06:55)
* #141 Ops too quick to "quiet" a user, Fedora Project should be ashamed
of IRC (nirik, 18:11:34)
* LINK: https://fedorahosted.org/irc-support-sig/ticket/141 (nirik,
18:11:43)
* Open Floor (nirik, 18:15:50)
Meeting ended at 18:18:46 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (42)
* DiscordianUK (14)
* StillBob (13)
* kk4ewt (4)
* zodbot (3)
* dan408 (2)
* oddshocks (2)
* jerzyr (2)
* maayke (1)
--
18:00:01 <nirik> #startmeeting IRC Support SIG (2013-04-04)
18:00:01 <zodbot> Meeting started Thu Apr 4 18:00:01 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:01 <nirik> #meetingname irc-support-sig
18:00:01 <nirik> #topic init process
18:00:01 <zodbot> The meeting name has been set to 'irc-support-sig'
18:00:13 * StillBob
18:00:19 * DiscordianUK is
18:02:14 <nirik> ok, I guess lets go ahead and dive in.
18:02:18 * maayke is here
18:02:24 * oddshocks waves
18:02:38 * nirik notes this is the irc support sig meeting, infra is in about an hour.
18:02:47 <nirik> despite the fact that I run them both. :)
18:02:57 <oddshocks> cool :)
18:03:16 <nirik> #topic Week in review
18:03:22 <StillBob> The Fedora™ Board meeting is in #fedora-meeting-1
18:03:36 <nirik> anyone have items from the past few weeks to note? any common issues or things people are hitting?
18:04:11 <jerzyr> hi
18:04:12 <DiscordianUK> Yes I see lots of folks wanting gnome 3.8
18:04:15 <nirik> I'd like to note again that for people having problems with the f18 installer, you should point them at https://fedoraproject.org/wiki/Anaconda/NewInstaller as it has a good overview of things, especially the storage area.
18:04:32 <DiscordianUK> which won't be till f19
18:04:34 <nirik> DiscordianUK: yeah, unfortunately I don't know of a side repo with it for f18.
18:04:51 <DiscordianUK> Likewise
18:05:24 <nirik> well, we can keep eyes out for it. ;)
18:05:30 <nirik> anything else to note?
18:05:33 * DiscordianUK nods
18:06:31 <nirik> ok, lets go on to tickets?
18:06:36 <nirik> #topic #140 failed to address a response to a user's question, then attacked the user
18:06:55 <nirik> https://fedorahosted.org/irc-support-sig/ticket/140
18:07:12 <nirik> I don't know what we can learn from this one. The user was answered by many people.
18:07:22 <nirik> no one really seemed to be attacked to me.
18:07:49 <nirik> I guess one thing is the comment about engrish.
18:08:01 <nirik> we should avoid that kind of thing.
18:08:04 <dan408> ssdd?
18:08:05 <dan408> ;p
18:08:06 <DiscordianUK> I don't think the OP was attacked
18:08:31 <StillBob> The user did not get the answer they wanted so the system is broken.
18:08:37 <DiscordianUK> He is very young and seeking attention in my opinion
18:09:19 <nirik> sure, so, lets close this with a thanks for the feedback and all try and avoid engrish like comments...
18:09:27 * DiscordianUK nods about the engrish thing
18:10:04 <nirik> shall we move on?
18:10:12 <DiscordianUK> Yes
18:10:18 <nirik> the next ticket was filed earlier this week, shall we look at it now, or wait for next meeting?
18:10:32 <StillBob> Lets just deal with it now...
18:10:44 <DiscordianUK> let's do that
18:11:02 <StillBob> Technically it should wait a week but I don't see a practical reason to do so.
18:11:28 <nirik> yeah.
18:11:34 <nirik> #topic #141 Ops too quick to "quiet" a user, Fedora Project should be ashamed of IRC
18:11:43 <nirik> https://fedorahosted.org/irc-support-sig/ticket/141
18:11:51 <nirik> I added my thoughts to the ticket earlier.
18:11:56 <StillBob> AS did I
18:12:21 <nirik> anyhow, I think this is an unfortunate case of a user who gets very mad very quickly...
18:12:28 <nirik> over not much
18:12:51 <StillBob> The user has a history going back several years with preconceived opinions of Fedora™ and the Fedora™ Community
18:12:54 <DiscordianUK> I agree with you on this nirik
18:13:21 <nirik> I suggested they try other support channels as well... but they say that they hate all fedora support, so not sure if they will do so.
18:13:52 <DiscordianUK> There is little we can do about other channels
18:14:00 <nirik> so, I would say close with thanks for the feedback, try other support channels, do try and relax some.
18:14:09 <kk4ewt> +!
18:14:11 <kk4ewt> !
18:14:11 <DiscordianUK> +1
18:14:13 <kk4ewt> !1
18:14:14 <nirik> right, my point is that they are tarring everything with the same brush
18:14:45 <nirik> there's not much overlap between irc and mailing list support, but yet they find them both horrible? perhaps it's something other than the support means.
18:14:47 <StillBob> Yup... thanks for shopping...
18:14:48 <nirik> ke4qqq: ?
18:15:34 <StillBob> nirik: I think kk4ewt was trying to say "+1" to close it and move on
18:15:42 <kk4ewt> yep
18:15:45 <nirik> ah, ok. ;)
18:15:50 <nirik> #topic Open Floor
18:15:59 <nirik> any items for open floor ? suggestions?
18:16:12 <StillBob> The Fedora™ Board meeting is in #fedora-meeting-1
18:16:19 <DiscordianUK> I have nothing
18:17:07 <nirik> ok, will close out in about a minute if nothing else.
18:17:56 <nirik> oh, would someone like to close tickets? if not, I can do it later.
18:18:07 <StillBob> Sure, I can do it...
18:18:18 <nirik> cool. thank you.
18:18:24 * StillBob will try to be as polite and nice as possible...
18:18:30 <StillBob> ;)
18:18:31 <jerzyr> :)
18:18:36 <nirik> StillBob: good luck. ;)
18:18:41 <nirik> thanks for coming everyone!
18:18:46 <nirik> #endmeeting
11 years
- 1
- 0
i18n meeting summary (2013-04-04)
by Akira TAGOH
=====================
#fedora-meeting: i18n
=====================
Meeting started by tagoh_ at 06:01:53 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-04-04/i18n.2013-04-0...
.
Meeting summary
---------------
* agenda and roll call (tagoh_, 06:01:54)
* LINK: https://fedoraproject.org/wiki/I18N/Meetings/2013-04-04
(tagoh_, 06:01:55)
* Upcoming schedule (tagoh_, 06:07:05)
* 2013-04-11 [[Test_Day:2013-04-11_Translation_(l10n)]]
(tagoh_, 06:07:06)
* 2013-04-16 Alpha Release (tagoh_, 06:07:06)
* Outstanding topics (tagoh_, 06:08:56)
* #16: Improving testcases/matrix for i18n test day (tagoh) (tagoh_,
06:08:56)
* LINK: https://fedorahosted.org/i18n/ticket/16 (tagoh_, 06:08:56)
* #18: F19 i18n docbeats (tagoh) (tagoh_, 06:14:24)
* LINK: https://fedorahosted.org/i18n/ticket/18 (tagoh_, 06:14:24)
* Open Floor (tagoh_, 06:32:12)
Meeting ended at 06:40:18 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tagoh_ (44)
* fujiwarat (5)
* Alam (4)
* zodbot (3)
* anish_ (3)
* mfabian (2)
* dueno (2)
* pravins (2)
* paragan (1)
* juhp (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
11 years
- 1
- 0
Fedora ARM Weekly Status Meeting Minutes 2013-04-03
by Paul Whalen
Thanks to those that were able to join for the status meeting today, for those unable the minutes
are posted below:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-04-03/fedora-meeti...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-04-03/fedora-meeti...
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-04-03/fedora-meeti...
Paul
===================================================
#fedora-meeting-1: Fedora ARM weekly status meeting
===================================================
Meeting started by pwhalen at 20:00:10 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-04-03/fedora-meeti...
.
Meeting summary
---------------
* 0) Status of ACTION items from our previous meeting (pwhalen,
20:01:46)
* LINK:
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-27/fedora-meeti...
(pwhalen, 20:01:46)
* -INPROGRESS- pbrobinson to post a list of leaf packages to
arm(a)lists.fp.o (pwhalen, 20:02:22)
* 1) Problem Packages (pwhalen, 20:04:48)
* from last week tog-pegasus, mongodb, being analyzed :
rubygem-RedCloth (pwhalen, 20:06:29)
* tog-pegasus - one test hangs, otherwise it builds and passes tests,
still under investigation (pwhalen, 20:07:05)
* ACTION: pwhalen to work with pbrobinson to publish weekly problem
package reports (pwhalen, 20:14:00)
* jstribny is still investigating rubygem-RedCloth (pwhalen,
20:14:47)
* 2) A10 Support in Fedora 19 (pwhalen, 20:15:52)
* ACTION: masta, j_dulaney, oatley to try upstream kernel on a10
devices (pwhalen, 20:24:01)
* 3) Generating the 'boot.scr' for release - Gruboot? Anaconda Library?
(pwhalen, 20:25:17)
* LINK: Magic boot.scr generator needs testing, get it at
http://people.fedoraproject.org/~blc/fedora-arm/gru-boot/
(bconoboy, 20:41:48)
* trimslice, highbank, armadaxp, beagle* and panda* believed to be
supported (bconoboy, 20:42:14)
* send all feedback to bconoboy or the arm list (bconoboy, 20:42:31)
* 4) F19 Alpha image creation (pwhalen, 20:43:48)
* Anyone with time and expertise in debugging python wanting to help
with LMC (Live Media Creator) on F19, please ping David Marlin
(dmarlin) (jonmasters, 20:46:52)
* ACTION: j_dulaney to find out what the plan is for Primary
Architecture for using Live Media Creator (LMC) vs. other tools and
the longer term strategy (jonmasters, 20:56:03)
* live media creator will hopefully be used for f19 image creation
(bconoboy, 21:08:30)
* backup plan is to port arm support into appliance-creator
(bconoboy, 21:08:54)
* 5) Open Floor (pwhalen, 21:10:09)
* ACTION: bconoboy to draft message to devel-announce requesting
aarch64 config.guess/sub support go into f19 (bconoboy, 21:14:06)
* LINK: http://koji.fedoraproject.org/koji/hosts (dgilmore,
21:14:57)
Meeting ended at 21:19:29 UTC.
Action Items
------------
* pwhalen to work with pbrobinson to publish weekly problem package
reports
* masta, j_dulaney, oatley to try upstream kernel on a10 devices
* j_dulaney to find out what the plan is for Primary Architecture for
using Live Media Creator (LMC) vs. other tools and the longer term
strategy
* bconoboy to draft message to devel-announce requesting aarch64
config.guess/sub support go into f19
Action Items, by person
-----------------------
* bconoboy
* bconoboy to draft message to devel-announce requesting aarch64
config.guess/sub support go into f19
* j_dulaney
* masta, j_dulaney, oatley to try upstream kernel on a10 devices
* j_dulaney to find out what the plan is for Primary Architecture for
using Live Media Creator (LMC) vs. other tools and the longer term
strategy
* masta
* masta, j_dulaney, oatley to try upstream kernel on a10 devices
* oatley
* masta, j_dulaney, oatley to try upstream kernel on a10 devices
* pbrobinson
* pwhalen to work with pbrobinson to publish weekly problem package
reports
* pwhalen
* pwhalen to work with pbrobinson to publish weekly problem package
reports
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bconoboy (98)
* dgilmore (75)
* dmarlin (48)
* jonmasters (42)
* pwhalen (31)
* j_dulaney (28)
* masta (27)
* nirik (22)
* zodbot (12)
* ctyler (10)
* fossjon (9)
* jcapik (2)
* oatley (1)
* pbrobinson (0)
11 years
- 1
- 0
F19 Alpha Blocker Bug Review #4 Minutes
by Tim Flink
=================================================
#fedora-blocker-review: f19alpha-blocker-review-4
=================================================
Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alph...
Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alph...
Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alph...
Meeting summary
---------------
* Roll Call (tflink, 16:01:40)
* LINK: http://www.what-if.xkcd.com/37/ (adamw, 16:07:04)
* Introduction (tflink, 16:07:54)
* Our purpose in this meeting is to review proposed blocker and
nice-to-have bugs and decide whether to accept them, and to monitor
the progress of fixing existing accepted blocker and nice-to-have
bugs. (tflink, 16:07:59)
* We'll be following the process outlined at: (tflink, 16:08:07)
* LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(tflink, 16:08:07)
* The bugs up for review today are available at: (tflink, 16:08:13)
* LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink,
16:08:13)
* The criteria for release blocking bugs can be found at: (tflink,
16:08:21)
* LINK:
https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria
(tflink, 16:08:21)
* Up for review today, we have: (tflink, 16:08:50)
* 12 Proposed Blockers (tflink, 16:08:58)
* 8 Accepted Blockers (tflink, 16:08:58)
* 1 Proposed Freeze Exceptions (tflink, 16:08:58)
* 2 Accepted Freeze Exceptions (tflink, 16:08:58)
* (928287) anaconda crashing to black screen at end of Fedora 19 Alpha
install (tflink, 16:10:10)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928287 (tflink,
16:10:13)
* Proposed Blocker, anaconda, POST (tflink, 16:10:15)
* AGREED: 928287 - AcceptedBlocker - Violates the following F19 alpha
release criteria: "When using the dedicated installer images, the
installer must be able to complete an installation using the text,
graphical and VNC installation interfaces." (tflink, 16:17:42)
* (929373) No Swap Install of some DE {Gnome , XFCE } in arch x8664
fails at package xml-common (tflink, 16:17:52)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=929373 (tflink,
16:17:55)
* Proposed Blocker, anaconda, NEW (tflink, 16:17:58)
* AGREED: 929373 - RejectedBlocker - While not ideal, this is a bit on
the self-inflicted side to be considered a release blocking bug (low
memory, no swap). A warning @ install time would be nice but not
required for alpha. Re-propose as FE for F19 final. (tflink,
16:30:46)
* (947261) AttributeError: 'module' object has no attribute
'memInstalled' (anaconda fails to boot with 512mb ram in TEXT MODE)
(tflink, 16:30:56)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=947261 (tflink,
16:30:59)
* Proposed Blocker, anaconda, NEW (tflink, 16:31:01)
* AGREED: 946261 - RejectedBlocker - This this only has a really bad
effect on the case of 512MB RAM text installs, all other configs
which would pass the anaconda memory check work, and thus, is not a
release blocking issue for F19 alpha. Would consider FE if
developers are interested in fixing for F19 alpha (adamw, 16:50:32)
* (927922) root account accessible without password when administrator
user is created but no root passwd set (tflink, 16:50:43)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=927922 (tflink,
16:50:46)
* Proposed Blocker, anaconda, NEW (tflink, 16:50:48)
* AGREED: 927922 - RejectedBlocker AcceptedFreezeException - While
this is an issue, issues with root logins on a local machine don't
seem severe enough to be release-blocking at alpha since root ssh
logins would not be allowed. However, a tested fix would be
considered for pulling during Freeze. If this is not fixed by final,
please re-propose as final blocker. (tflink, 17:07:26)
* (928279) anaconda doesn't start on LiveCD (in Gnome) (tflink,
17:09:38)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928279 (tflink,
17:09:38)
* Proposed Blocker, anaconda, NEW (tflink, 17:09:38)
* LINK: https://dl.dropbox.com/u/95286161/Fedora%2019%20xfce_.png
(akshayvyas, 17:17:01)
* AGREED: 928279 - AcceptedBlocker - Violation of the following F19
alpha criterion for some bare metal installs (not sure the exact
trigger, seems to be enough to not be too hw specific): "The
installer must run when launched normally from the release-blocking
images." (tflink, 17:19:47)
* (947616) anaconda validate architecture from remote installation
sources (one can boot X86_64 dvd media and install a 32-BIT one via
NFS Installation Source) (tflink, 17:20:00)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=947616 (tflink,
17:20:03)
* Proposed Blocker, anaconda, NEW (tflink, 17:20:06)
* AGREED: 947616 - RejectedBlocker - While the result did not match
the initial intentions, the installation was successful and produced
a bootable system. (tflink, 17:23:11)
* (928982) Bootloader install fails on UEFI install to clean VM: "failed
to set new efi boot target" (tflink, 17:23:42)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928982 (tflink,
17:23:45)
* Proposed Blocker, anaconda, NEW (tflink, 17:23:47)
* AGREED: 928982 - AcceptedBlocker - Violates the following F19 alpha
release criterion for uEFI systems: "When using the dedicated
installer images, the installer must be able to complete an
installation using the text, graphical and VNC installation
interfaces." (tflink, 17:26:49)
* (929289) user account created in anaconda is ignored in
gnome-initial-setup (tflink, 17:27:00)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=929289 (tflink,
17:27:03)
* Proposed Blocker, gnome-initial-setup, NEW (tflink, 17:27:06)
* AGREED: 929289 - RejectedBlocker, AcceptedFreezeException - While
not severe enough to block the release of F19 alpha, it is a polish
issue and an annoyance. A tested fix would be considered past
freeze. (tflink, 17:39:51)
* (946964) after default install of 19 Alpha TC3 in KVM, can't log in
from gdm (tflink, 17:40:06)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=946964 (tflink,
17:40:09)
* Proposed Blocker, gnome-shell, NEW (tflink, 17:40:11)
* AGREED: 946964 - It's unclear how widespread this issue is, will
re-evaluate when there is more data on how many users are affected
(tflink, 17:56:35)
* (929403) initial-setup-graphical.service is not enabled by default, so
initial-setup does not run after install (KDE, LXDE, Xfce...)
(tflink, 17:56:42)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=929403 (tflink,
17:56:45)
* Proposed Blocker, initial-setup, NEW (tflink, 17:56:47)
* note that while the criteria have not yet been updated - firstboot
encompasses initial-setup and gnome-initial-setup (tflink,
18:03:55)
* AGREED: 929403 - AcceptedBlocker - Violates the following F19 alpha
release criteria for KDE: "A system installed with a graphical
package set must boot to the 'firstboot' utility on the first boot
after installation. The firstboot utility must be able to create a
working user account." (tflink, 18:05:28)
* (928994) Installer doesn't create /run directory leading to boot
failure (tflink, 18:05:53)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928994 (tflink,
18:05:56)
* Proposed Blocker, LiveCD - KDE, NEW (tflink, 18:05:58)
* AGREED: this is likely a dupe of #928339 but it should be tested
with TC3 or the pending TC4 before closing as a dupe - will revisit
if this turns out not to be a duplicate (tflink, 18:11:58)
* (922988) python-blivet not creating /sys and /run on /mnt/sysimage
(tflink, 18:12:51)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922988 (tflink,
18:12:54)
* Proposed Blocker, python-blivet, MODIFIED (tflink, 18:12:56)
* an accepted blocker was marked as a duplicate of this bug and the
acceptedblocker should have transferred - does not need to be
re-evaluated (tflink, 18:19:42)
* (928704) gnome-terminal crashes when new profile (or profile edit) is
requested (tflink, 18:20:31)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928704 (tflink,
18:20:34)
* Proposed Freeze Exceptions, gnome-terminal, MODIFIED (tflink,
18:20:36)
* AGREED: 928704 - While not critical enough to block the release of
F19 alpha, it would be nice to fix this before release. A tested fix
would be considered after freeze (tflink, 18:26:21)
* (926913) rescue mode fails with traceback (tflink, 18:27:37)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=926913 (tflink,
18:27:37)
* Accepted Blocker, anaconda, MODIFIED (tflink, 18:27:37)
* this is now ON_QA - we have a build and just need a new spin to test
it (tflink, 18:29:10)
* (928353) firefox i686 crashes for a number of web pages (tflink,
18:29:23)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928353 (tflink,
18:29:23)
* Accepted Blocker, firefox, NEW (tflink, 18:29:23)
* a build with the workaround described in bug is available: (tflink,
18:33:13)
* LINK: http://koji.fedoraproject.org/koji/buildinfo?buildID=408680
(tflink, 18:33:26)
* request update for the xulrunner build so that it can be included in
the next TC (tflink, 18:33:58)
* (929054) repoclosure failure on 19 Alpha TC3 DVDs (libmateui)
(tflink, 18:36:13)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=929054 (tflink,
18:36:16)
* Accepted Blocker, libmateui, MODIFIED (tflink, 18:36:18)
* the problematic package has been retired, the problem should be
fixed (tflink, 18:37:42)
* confirm fix with TC4 and close if it is fixed (tflink, 18:38:45)
* (926916) anaconda can't report traceback to bugzilla (tflink,
18:38:58)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=926916 (tflink,
18:38:58)
* Accepted Blocker, libreport, ASSIGNED (tflink, 18:38:59)
* the problem has been identified, devs are figuring out where to fix
the issue (tflink, 18:41:11)
* patch has been sent, still needs to be reviewed (tflink, 18:41:26)
* related to https://bugzilla.redhat.com/show_bug.cgi?id=929181
(tflink, 18:41:38)
* (947680) Bogus dependency on "seavgabios" in qemu-1.4.0-7.fc19
(tflink, 18:45:58)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=947680 (tflink,
18:46:02)
* Accepted Blocker, qemu, MODIFIED (tflink, 18:46:04)
* this bug changed to ON_QA since the list was generated (tflink,
18:46:35)
* fix is available, needs testing and karma (tflink, 18:46:49)
* (924256) repoclosure failure on 19 Alpha TC1 DVDs (resteasy) (tflink,
18:47:04)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924256 (tflink,
18:47:07)
* Accepted Blocker, resteasy, NEW (tflink, 18:47:10)
* there is a new package which will fix this (jboss-servlet-2.5-api)
(tflink, 18:48:26)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=947519 (tflink,
18:48:41)
* there should be a build available later today (tflink, 18:48:58)
* (928303) F19 KDE contains F18 artwork (tflink, 18:50:00)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928303 (tflink,
18:50:00)
* Accepted Blocker, schroedinger-cat-kde-theme, MODIFIED (tflink,
18:50:00)
* this bug went to ON_QA during the meeting (tflink, 18:50:35)
* a fix is available, needs testing after TC4 spin (tflink, 18:50:48)
* Open Floor (tflink, 18:51:01)
* will decide whether it's worth scheduling another blocker review
meeting for friday later today or tomorrow (tflink, 18:54:39)
* will schedule blocker review meeting for after monday's qa meeting
to check status (tflink, 18:55:08)
Meeting ended at 18:58:28 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tflink (239)
* adamw (136)
* jreznik (68)
* kparal (54)
* brunowolff (37)
* akshayvyas (21)
* robatino (13)
* zodbot (11)
* satellit_e (3)
* nirik (1)
* satellit (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
11 years
- 1
- 0
FAmNA Meeting (02 April 2013)
by inode0
======================
#fedora-meeting: FAmNA
======================
Meeting started by inode0 at 01:00:12 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-04-03/famna.2013-04-...
.
Meeting summary
---------------
* Roll Call (inode0, 01:00:28)
* LINK:
https://fedoraproject.org/wiki/Fedora_Ambassadors_Steering_Committee?rd=F...
(dan408, 01:05:14)
* Announcements (inode0, 01:05:21)
* LINK: http://2013.texaslinuxfest.org/cfp <--- extended through this
Friday (inode1, 01:06:26)
* LINK: http://www.southeastlinuxfest.org/rfp2013/form.html <--- this
one needs to be done by next Monday (inode1, 01:07:34)
* tickets (dan408, 01:09:02)
* Regional Budget FY14 (inode0, 01:10:39)
* LINK: https://fedoraproject.org/wiki/FY14_Budget (inode0,
01:11:10)
* LINK: http://fedoraproject.org/wiki/Northeast_Linuxfest_2013
(inode0, 01:18:27)
* LINK:
https://docs.google.com/spreadsheet/ccc?key=0ApBrbq5j6NbOdG0zQzVvR3VqQ05N...
(dan408, 01:35:32)
* this was from FADNA2013 (dan408, 01:35:42)
* Tickets (inode0, 01:40:25)
* LINK: https://fedorahosted.org/famna/report/9 (inode0, 01:40:27)
* LINK: http://www.petfinder.com/shelters/NC35.html <--- maybe, I
haven't researched this yet (inode0, 01:46:14)
* LINK: http://www.tigerworld.us/donations.html (suehle, 01:49:04)
* Open Floor (inode0, 01:53:59)
Meeting ended at 02:12:29 UTC.
John
11 years
- 1
- 0
FAmSCo meeting minutes 2013-04-01
by Jiri Eischmann
No fooling today,
FAmSCo held a meeting. The only topic was adjusting our regional budget draft to the budget reality. If you want to know more, read the minutes:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-2/2013-04-01/famsco.2013-...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-2/2013-04-01/famsco.2013-...
Log: http://meetbot.fedoraproject.org/fedora-meeting-2/2013-04-01/famsco.2013-...
The next meeting will be on Mon April 8th.
Jiri
11 years
- 1
- 0