Hi all,
The IRC meeting minutes tonight are available at the link [1]. Thanks
everyone for attending the meeting.
In the meeting we mainly talked about plans for offline gather up in
April, FUDCon APAC 2014 bid, FPWiki Zh pages clean up, and L10N status.
The next IRC meeting will be held on next Friday (2013-04-05). Please
come and join the discussion if you can! Note the beginning time of the
meeting has been changed to 21:00(UTC+8).
1.
http://meetbot.fedoraproject.org/fedora-zh/2013-03-29/fedora-zh.2013-03-29-…
=============================================
#fedora-zh: Fedora Chinese Meeting 2013-03-29
=============================================
Meeting started by alick at 13:04:31 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-zh/2013-03-29/fedora-zh.2013-03-29-…
.
Meeting summary
---------------
* 点名 (alick, 13:04:56)
* 四月线下活动征集 (alick, 13:11:22)
* IDEA: 非一线城市可以考虑和当地 LUG 等组织联合活动 (alick, 13:15:04)
* IDEA: 考虑办次以 Linux 安全 为主题的线下活动 (alick, 13:25:45)
* FUDCON APAC 2014 举办申请 (alick, 13:26:27)
* LINK:
http://lists.fedoraproject.org/pipermail/chinese/2013-March/012721.html
(alick, 13:27:44)
* LINK:
http://www.weibo.com/lsh511744?from=profile&wvr=5&loc=infdomain
(alick, 13:29:28)
* ACTION: alick to talk about the deadline of bid proposal in ML
(alick, 13:39:05)
* FPWiki Zh 页面的整理更新 (alick, 13:44:10)
* LINK: https://fedoraproject.org/wiki/Zh/zh-cn (alick, 13:44:44)
* HELP: FPWiki Zh/ 页面需更新 (alick, 13:48:42)
* 中文翻译 (alick, 13:49:24)
* LINK:
https://fedora.transifex.com/projects/p/fedora/r/fedora-main/l/zh_CN/
(alick, 13:55:48)
* Fedora 19 软件翻译阶段 2013-03-19 到 2013-04-23 (alick, 13:56:31)
Meeting ended at 14:03:13 UTC.
Action Items
------------
* alick to talk about the deadline of bid proposal in ML
Action Items, by person
-----------------------
* alick
* alick to talk about the deadline of bid proposal in ML
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* alick (77)
* zsun (24)
* zodbot (7)
* BadGirl (6)
* Robin_cheese_Lee (5)
* tiansworld (5)
* microcai (5)
* chengshiding (5)
* diseng (3)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Alick
Fedora 18 (Spherical Cow) user
https://fedoraproject.org/wiki/User:Alick
=====================
#fedora-meeting: i18n
=====================
Meeting started by tagoh_ at 06:03:09 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-28/i18n.2013-03-28-…
.
Meeting summary
---------------
* agenda and roll call (tagoh_, 06:03:10)
* LINK: https://fedoraproject.org/wiki/I18N/Meetings/2013-03-28
(tagoh_, 06:03:10)
* Upcoming schedule (tagoh_, 06:09:08)
* 2013-04-02 Software String Freeze (tagoh_, 06:09:08)
* 2013-04-02 Alpha Change Deadline (tagoh_, 06:09:09)
* 2013-04-11 Test_Day:2013-04-11_Translation_(l10n) (tagoh_,
06:09:09)
* 2013-04-16 Alpha Release (tagoh_, 06:09:09)
* Outstanding topic (tagoh_, 06:14:11)
* #16: Improving testcases/matrix for i18n test day (tagoh) (tagoh_,
06:14:11)
* LINK: https://fedorahosted.org/i18n/ticket/16 (tagoh_, 06:14:11)
* LINK:
https://fedoraproject.org/wiki/Test_Day:2013-05-02_Localization_(i18n)
(tagoh_, 06:15:09)
* ACTION: dueno to create a draft test case for ibus-hangul (tagoh_,
06:20:25)
* ACTION: epico to create a draft test case for zh-TW (tagoh_,
06:22:20)
* #18: F19 i18n docbeats (tagoh) (tagoh_, 06:25:47)
* LINK: https://fedorahosted.org/i18n/ticket/18 (tagoh_, 06:25:47)
* LINK: https://fedoraproject.org/wiki/Documentation_I18n_Beat
(tagoh_, 06:25:55)
* Open Floor (tagoh_, 06:30:50)
* LINK:
http://cgit.freedesktop.org/wayland/weston/tree/protocol/input-method.xml
(epico, 06:36:05)
Meeting ended at 06:43:32 UTC.
Action Items
------------
* dueno to create a draft test case for ibus-hangul
* epico to create a draft test case for zh-TW
Action Items, by person
-----------------------
* dueno
* dueno to create a draft test case for ibus-hangul
* epico
* epico to create a draft test case for zh-TW
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tagoh_ (58)
* epico (9)
* juhp (8)
* mfabian (6)
* zodbot (4)
* dueno (2)
* paragan (1)
* pravins (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
============================================
#fedora-meeting: Infrastructure (2013-03-28)
============================================
Meeting started by nirik at 19:00:00 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-28/infrastructure.2…
.
Meeting summary
---------------
* welcome y'all (nirik, 19:00:01)
* New folks introductions and Apprentice tasks (nirik, 19:02:16)
* LINK: http://infrastructure.fedoraproject.org/cgit (skvidal,
19:07:03)
* Applications status / discussion (nirik, 19:09:01)
* LINK: https://github.com/fedora-infra/rube ! (lmacken, 19:09:35)
* Sysadmin status / discussion (nirik, 19:27:07)
* Private Cloud status update / discussion (nirik, 19:30:38)
* Upcoming Tasks/Items (nirik, 19:33:28)
* 2013-03-19 to 2013-03-26 - koji update (nirik, 19:33:38)
* 2013-03-29 - spring holiday. (nirik, 19:33:38)
* 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik,
19:33:38)
* 2013-04-15 - remove legacy-openid (nirik, 19:33:38)
* 2013-04-16 F19 alpha release (nirik, 19:33:39)
* 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik,
19:33:40)
* 2013-05-21 F19 beta release (nirik, 19:33:41)
* 2013-05-31 end of 1st quarter (nirik, 19:33:42)
* 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik,
19:33:44)
* 2013-06-25 F19 FINAL release (nirik, 19:33:46)
* Open Floor (nirik, 19:40:47)
* 2013-04-04 Send email to folks who have been using legacy-openid to
notify about sunset (puiterwijk, 19:40:49)
* LINK: https://fedoraproject.org/wiki/Infrastructure_FedoraBugzilla
(skvidal, 19:51:35)
* LINK:
https://fedoraproject.org/wiki/Infrastructure_FedoraHosted_Version2_Notes
(skvidal, 19:51:46)
Meeting ended at 20:00:28 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (115)
* skvidal (74)
* puiterwijk (29)
* herlo (22)
* abadger1999 (19)
* lmacken (15)
* threebean (10)
* biker (10)
* dgilmore (9)
* frankly3d (8)
* linuxmania (7)
* cyberworm54 (5)
* zodbot (4)
* jerzyr (4)
* tflink (2)
* kalev (2)
* relrod (1)
* smooge (1)
* fchiulli (1)
* ricky (0)
* mdomsch (0)
* CodeBlock (0)
--
19:00:00 <nirik> #startmeeting Infrastructure (2013-03-28)
19:00:00 <zodbot> Meeting started Thu Mar 28 19:00:00 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:01 <nirik> #meetingname infrastructure
19:00:01 <nirik> #topic welcome y'all
19:00:01 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean
19:00:01 <zodbot> The meeting name has been set to 'infrastructure'
19:00:01 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean
19:00:15 * relrod here, sort of
19:00:16 * puiterwijk is around
19:00:30 * skvidal is here
19:00:43 * lmacken lurking
19:00:49 <frankly3d> here
19:00:55 <fchiulli> fchiulli is listening
19:01:16 <nirik> morning everyone. will wait another min for folks to wander in before starting.
19:01:35 * threebean is here
19:01:49 * herlo is here
19:02:16 <nirik> #topic New folks introductions and Apprentice tasks
19:02:25 <nirik> any new folks? or apprentices with questions?
19:02:35 <frankly3d> How do you know where to go, if looking for freemedia, do you chance hosted0* hosted1* . Looked here but no signpost per say
19:02:51 <frankly3d> Duh: http://infrastructure.fedoraproject.org/infra/docs/
19:03:48 * dgilmore is here
19:03:49 <skvidal> frankly3d: go for what?
19:03:52 <nirik> well, depends on for what. ;)
19:03:54 <skvidal> hosted is all on hosted02
19:03:58 <skvidal> (for example)
19:04:13 <frankly3d> The backend for the trac?
19:04:21 <nirik> yeah, that would be on hosted02...
19:04:53 <skvidal> frankly3d: what were you wondering about in trac?
19:04:56 <nirik> it somewhat depends on what you are trying to look at or change...
19:05:10 <frankly3d> trac.ini
19:05:11 <nirik> trac is on there... as well as git repos.
19:05:38 <frankly3d> how large is infra git?
19:05:38 <nirik> frankly3d: would be under /srv/web/trac/projects/
19:06:00 <nirik> git repos are under /srv/git/ I don't think the infra one is all that big, dunno off hand.
19:06:21 <puiterwijk> most of infra stuff is not actually on hosted though. most is on lockbox in /git
19:06:51 <skvidal> puiterwijk: and the public git repos are available via cgit and git://
19:07:02 <puiterwijk> skvidal: ah ok
19:07:03 <skvidal> http://infrastructure.fedoraproject.org/cgit
19:07:09 <puiterwijk> yeah, indeed
19:07:13 * herlo lubs cgit
19:07:19 <nirik> frankly3d: does that help? happy to answer more questions in #fedora-admin after the meeting... :)
19:07:22 <puiterwijk> but just wanted to note that hosted02 doesn't contain most infra git repo stuff
19:07:27 <skvidal> I'd love it more if it didn't get its cache hosed from time to time
19:07:41 <frankly3d> Yes, I'll have more when I get lost.
19:07:55 <puiterwijk> skvidal: I have added a cron that fixes that, right? or are there more broken ones?
19:08:02 <nirik> happy to help direct you. Or others will if I'm not around. ;)
19:08:17 <nirik> ok, any other new folks or questions?
19:08:19 <skvidal> puiterwijk: which cron job is this? on hosted or on lockbox?
19:08:28 <puiterwijk> skvidal: on hosted
19:08:34 <skvidal> puiterwijk: sure
19:08:40 <puiterwijk> could move it also to lockbox with your permission/request?
19:08:49 <skvidal> puiterwijk: let's talk about this outside of this meeting
19:08:56 <puiterwijk> sure
19:09:01 <nirik> #topic Applications status / discussion
19:09:10 <nirik> any application news or plans to discuss?
19:09:35 <lmacken> https://github.com/fedora-infra/rube !
19:09:47 <lmacken> we need help writing more tests
19:09:51 <threebean> :P
19:10:02 <nirik> ah yes, I need to play with that some more. ;) Very nice work tho!
19:10:10 <lmacken> and eventually hooking it up to status.fp.o :)
19:10:46 <nirik> hum, not sure how that would work out...
19:11:34 <nirik> although another thought occurs to me: could we have it send in fedmsg when it runs tests? then we could have something that says "user foo ran rube and saw failed for test bar" and we know to look or retest or ask them if they need help?
19:11:51 <threebean> hm, the original idea was just to run it by hand. but with that x virtual frame buffer stuff we could potentially turn it into a nagios check or something like that
19:12:01 <lmacken> not outside of infra... but if we run it within jenkins, it could potentially fire off messages
19:12:25 <nirik> lots of possibilities. ;)
19:12:40 <lmacken> indeed :)
19:13:14 <nirik> cool.
19:13:21 <threebean> hey, so pingou has been hacking on a new interface to fedora-tagger -> http://blog.pingoured.fr/index.php?post/2013/03/27/GNOME-tagger
19:13:41 <nirik> I'll note that tomorrow is a holiday for many, and next tuesday we enter into alpha freeze, so do look at any changes you would like to get in before then...
19:14:26 <threebean> he (re)wrote the json api in the process and it feels really solid - much more solid than it was.
19:14:29 <nirik> ah ha. Nice!
19:14:42 <abadger1999> I'm going to try to push an alpha of python-fedora to infra... alpha because I'm not satisfied with the api we're trying to implement for otp yet.
19:14:58 <threebean> I'm still playing catch-up to update the existing js frontend to use his api, but it's coming along.
19:15:04 <lmacken> abadger1999: will that have python3 support? :)
19:15:23 <lmacken> threebean, pingou: gnome-tagger looks schweet
19:15:40 <kalev> probably not the best time and place to say this, but ... I have a trivial patch I'd like to get in to Bodhi: https://fedorahosted.org/bodhi/ticket/708
19:16:00 <abadger1999> lmacken: python3 python-fedora doesn't make much sense right now.... there's too much that it depends on that is python2 only (like TG1)
19:16:11 <nirik> kalev: no worries. :) it's an ok time to chime in...
19:16:13 <abadger1999> lmacken: are you thinking of kitchen?
19:16:19 <lmacken> kalev: cool, I'll have a look at that tonight
19:16:26 <kalev> lmacken: awesome, thanks!
19:16:36 <lmacken> abadger1999: ah yes, kitchen. and python-fedora at some point though
19:16:58 <abadger1999> lmacken: yeah, kitchen: if that worked out for you -- it should still just need documentation updates.
19:17:13 <abadger1999> lmacken: python-fedora.... big lot of other things that need to go python3 first or...
19:17:21 <abadger1999> Port all of our stuff off of TG1
19:18:00 <linuxmania> hi guys
19:18:02 <threebean> on the kitchen->py3 port, I lifted a finger on the docs but didn't get much further: https://github.com/fedora-infra/kitchen/commits/feature/py3-finalize
19:18:02 * lmacken nods
19:18:03 <linuxmania> i am late.
19:18:50 <nirik> linuxmania: no worries. ;)
19:19:07 <linuxmania> nirik, nice to see you again!
19:19:31 <abadger1999> threebean: Cool.
19:19:31 <nirik> ok, any other application news? or shall we move on?
19:19:39 <linuxmania> what are we talking about now?
19:19:50 <abadger1999> threebean: maybe that would be something we could have a vfad about.
19:20:23 <skvidal> abadger1999: given the reply to my email about vfads
19:20:26 <herlo> linuxmania: /topic
19:20:27 <skvidal> abadger1999: I suspect that won't ever happen
19:20:28 <abadger1999> threebean: Really the two things it takes are -- 1) time without outside distractions and 2) people to write the docs and test the advice under python3
19:20:45 * threebean nods
19:21:53 <linuxmania> herlo, thanks i see.
19:22:07 <herlo> :)
19:22:43 <puiterwijk> oh, a last app thing: I split the authentication part from FAS-OpenID, so that it is less strictly tied to FAS, and more pluggable
19:22:55 <puiterwijk> and I am currently working on a BrowserID implementation
19:23:05 <puiterwijk> (for FAS-OpenID)
19:23:17 <nirik> that will be nice I think...
19:23:24 <jerzyr> yes
19:23:27 <nirik> no idea how much traction it will get overall, but nice to support it.
19:23:45 <linuxmania> herlo, so how should I starting reading the code and programming?
19:24:06 <abadger1999> puiterwijk: is browserid the same as mozilla persona or different?
19:24:11 <lmacken> same
19:24:13 <herlo> linuxmania: let's address those in #fedora-admin if you like
19:24:15 * lmacken learned that today :)
19:24:29 <nirik> abadger1999: same thing... browserid is the low level protocol, persona is the implementation (I think)
19:24:43 <linuxmania> herlo, OK.
19:24:54 <puiterwijk> abadger1999: persona is Mozilla's implementation of BrowserID
19:24:54 <abadger1999> puiterwijk: cool. At pycon I met a mozilla guy, dan callahan that would be happy to talk about it if you need any input.
19:24:55 <herlo> lmacken: isn't that TIL :)
19:24:56 * lmacken listening to @lxt from mozilla give a talk right now, and sitting next to one of the guys who admid'd browserid
19:25:14 <puiterwijk> abadger1999: ah cool, could you give me his email or IRC handle?
19:25:28 <nirik> we can also test with hyperkitty, which supports logging in via it.
19:25:33 <abadger1999> puiterwijk: yep. I'll dig it out and get it to you in a pm
19:25:34 <lmacken> herlo: indeed :)
19:25:39 <puiterwijk> abadger1999: thanks :)
19:26:44 <nirik> cool. Related to that we are testing trac openid on trac instances... hopefully to move to it there soon.
19:27:04 <puiterwijk> nirik: wanted to note that in sysadmin part :)
19:27:07 <nirik> #topic Sysadmin status / discussion
19:27:09 <nirik> cool. Related to that we are testing trac openid on trac instances... hopefully to move to it there soon.
19:27:11 <nirik> :)
19:27:13 <puiterwijk> heh
19:27:14 <puiterwijk> :)
19:27:25 <puiterwijk> it is currently live on the infra trac
19:27:28 <nirik> this will allow us to get rid of mod_auth_pg
19:27:33 <nirik> (at least there)
19:27:50 <skvidal> \o/
19:27:53 <skvidal> |
19:27:54 <nirik> Lets see... in other sysadmin news...
19:28:04 <puiterwijk> skvidal: cool one! :)
19:28:15 * skvidal is happy that mod_auth_pg can go away
19:28:23 <nirik> we have budget numbers for the coming year, smooge and I are poking at them to see what we can/cannot do based on what we wanted to do, etc.
19:28:47 <skvidal> what systems are phasing out this year?
19:28:54 <nirik> There's been some net issues of late... possibly related to that big DOS going on.
19:29:31 <nirik> skvidal: dunno. I think we hope to renew most of them... we will be replacing some tho
19:30:07 <nirik> anything else from the sysadmin side of things?
19:30:22 <smooge> skvidal, I can give you an estimated list in a short while
19:30:30 <skvidal> nirik: cool, thx
19:30:38 <nirik> #topic Private Cloud status update / discussion
19:30:42 <nirik> any cloudy news?
19:30:50 <skvidal> migrated over to openstack entirely
19:30:53 <biker> hey all
19:31:05 <nirik> skvidal: cool. ;)
19:31:10 <skvidal> and next week we can start taking a couple more compute nodes to add to the openstack cluster
19:31:12 <nirik> morning biker
19:31:21 <skvidal> nirik: we can also take the most of the rest of the ips if we want
19:31:22 <nirik> skvidal: sounds good.
19:31:31 <skvidal> nirik: I think we should keep a small subset out
19:31:33 <skvidal> and 2 machines
19:31:36 <nirik> oh yeah, not sure how easy it will be to add to the floating net, but we can look at it.
19:31:38 <skvidal> so we can test out new layouts
19:31:42 <nirik> yep. agreed.
19:31:46 <skvidal> nirik: if we can add a second range
19:31:48 <skvidal> of floating ips
19:31:55 <skvidal> which I _THINK_ is possible
19:31:59 <skvidal> then we could add a /64 there
19:32:04 <nirik> I think adding is possible, but editing existing was a pain last time I tried
19:32:39 <skvidal> nirik: then let's tack on 64 or so ips
19:33:00 <nirik> sure, we can poke at it and see how best to add them
19:33:12 <skvidal> no other cloudy news I can think o
19:33:22 * nirik neither.
19:33:28 <nirik> #topic Upcoming Tasks/Items
19:33:38 <nirik> #info 2013-03-19 to 2013-03-26 - koji update
19:33:38 <nirik> #info 2013-03-29 - spring holiday.
19:33:38 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
19:33:38 <nirik> #info 2013-04-15 - remove legacy-openid
19:33:39 <nirik> #info 2013-04-16 F19 alpha release
19:33:40 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
19:33:41 <nirik> #info 2013-05-21 F19 beta release
19:33:42 <nirik> #info 2013-05-31 end of 1st quarter
19:33:44 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
19:33:46 <nirik> #info 2013-06-25 F19 FINAL release
19:33:48 <nirik> I don't know what the status of that koji update is. ;(
19:33:55 <nirik> we should ping mattdm and see whats going on.
19:34:02 <skvidal> nirik: it must be finished ;)
19:34:09 <skvidal> mattdm on koji?
19:34:19 <nirik> well, this is to add the cloud image support stuff.
19:34:22 <skvidal> oh
19:34:24 <skvidal> I see
19:34:30 <nirik> I guess we could also just ask upstream koji folks the status.
19:34:34 <skvidal> nod
19:34:37 <nirik> dgilmore might have heard something.
19:34:47 <dgilmore> there was some testing going on
19:34:51 <dgilmore> but its not done
19:35:14 <nirik> is it gonna make it before tuesday?
19:35:48 <nirik> I guess we could do a freeze break for the update, but I would sure prefer not to. ;)
19:36:27 <nirik> also, everyone note that tomorrow is at least a RH holiday, so don't expect lots of people around working on things.
19:36:50 <dgilmore> nirik: no idea
19:37:00 <nirik> ok.
19:37:09 <dgilmore> i know oz has friday and monday off
19:37:10 <nirik> anything else anyone would like to schedule or note?
19:37:41 <skvidal> dgilmore: so we're switching to an img creator that takes money and fridays off?!
19:37:49 <skvidal> oh wait- you mean australia, don't you. :)
19:38:20 <puiterwijk> nirik: maybe one thing to schedule: we might want to send a mass-email to anyone who has used legacy-openid before sunset date?
19:38:27 <dgilmore> skvidal: yes australia
19:38:49 <nirik> puiterwijk: not a bad idea. ;) Perhaps closer to sunset date? say a week or so before?
19:38:50 <dgilmore> pretty sure other countries have easter monday off also
19:38:54 <puiterwijk> nirik: (I have made it keep a log distinct from the syslog for that purpose)
19:38:59 <nirik> or early next week.
19:39:01 <skvidal> dgilmore: I was being silly
19:39:06 <puiterwijk> sure, works for me
19:39:15 <dgilmore> skvidal: ;) i know
19:39:43 <puiterwijk> nirik: 04-04-2013? :)
19:40:14 <puiterwijk> or would that be too late?
19:40:16 <nirik> sure.
19:40:22 <nirik> works for me
19:40:47 <nirik> #topic Open Floor
19:40:49 <puiterwijk> #info 2013-04-04 Send email to folks who have been using legacy-openid to notify about sunset
19:40:56 <nirik> any items for open floor? questions, comments?
19:41:02 <biker> nirik, yeah
19:41:17 <biker> the same as last week,., i hope there are more people now that fudcon is over :p
19:41:24 <skvidal> pycon
19:41:24 <nirik> :)
19:41:25 <biker> pycon *
19:41:26 <skvidal> not fudcon
19:41:27 <skvidal> but yah
19:41:27 <biker> yeah :p
19:41:35 <nirik> biker: ask away...
19:41:42 * herlo also has something
19:42:04 * skvidal has one more item too
19:42:32 <biker> so i want to participate on the google summer of code helping the fedora infrastructure,., so if anyone has an idea of what does could be done or what it is needed, i would like to hear and help (:
19:43:00 <skvidal> is fedora trying to get into GSoC this year?
19:43:39 <biker> skvidal, im not sure,., but they have done it every year,., and fedora also has the fedora on gsoc 2013 wiki
19:43:44 <puiterwijk> skvidal: Fedora itself is according to wiki, but none of the infra stuff has any mentors...
19:43:50 <biker> altough i think they jsut changed 2012 to 2013
19:44:05 <skvidal> who is running the gsoc show for fedora this year?
19:44:12 <skvidal> who is our lead on it?
19:44:23 <abadger1999> I think so. I think bckurera is going to manage it again.
19:44:25 <nirik> I think it's been submitted... but none of them have been announced yet.
19:44:35 <abadger1999> But -- I don't know if we have anyone who is ready to mentor in infra.
19:44:43 * nirik doesn't really have time at this time.
19:44:46 <puiterwijk> skvidal: according to wiki: Buddhike Kurera(Bckurera)
19:45:03 <skvidal> nirik: I'm with you there
19:45:21 <abadger1999> threebean, you up for mentoring someone in GSoC this year?
19:45:23 * puiterwijk also doesn't have time for that
19:45:28 <nirik> pingou suggested we do a team thing...
19:45:36 <skvidal> no idea what that means
19:45:47 <nirik> ie, get several people to mentor the same person... so mentor duties can be spread out.
19:45:49 <threebean> abadger1999: I was going to mentor for http://gnome.org/OPW which is at the same time
19:46:08 <threebean> sorry - https://live.gnome.org/OutreachProgramForWomen
19:46:48 <tflink> from my experience as a mentor for GSoC last year, having multiple people helps - even if they aren't officially part of GSoC
19:47:10 <abadger1999> Well... hmm.... biker We can ask o nthe infra mailing list if there's other people in infra not here at present that would be willing to mentor.
19:47:28 * nirik thinks biker was also interested in ideas of things to work on too.
19:47:28 <biker> abadger1999, that would be great (:
19:47:29 <skvidal> sounds like a plan
19:47:30 <abadger1999> but hte core team seems like they might be overcommitted right now.
19:47:32 <tflink> the official load from GSoC wasn't bad - the hard part was answering questions and helping get stuff done
19:47:46 <skvidal> abadger1999: overcommitted is an understatement
19:47:50 <dgilmore> tflink: ive decided to not at all be involved with GSoC this year
19:48:03 <abadger1999> So you might need to adapt to the needs of what the specific mentor is interested in mentoring for.
19:48:34 <abadger1999> biker: Are you on the infrastructure(a)lists.fp.o mailing list? I'll send an email there right after the meeting.
19:48:59 <nirik> thanks abadger1999 / biker. :) good luck...
19:49:05 <nirik> herlo: you had something?
19:49:08 <herlo> Anyone ever looked at this https://github.com/klaussilveira/gitlist as a replacement for trac, similar to suggestions of gitlabhq. It's php though, so I don't know if it's even worth looking at. The screenshots are nice...
19:49:12 <herlo> nirik: I did
19:49:14 <biker> abadger1999, ill subscribe right now (: thanks a lot to everytone (:
19:49:14 <herlo> :)
19:49:24 * nirik hasn't looked at that before
19:49:38 <herlo> I don't really know if we're actually still discussing replacing trac, but I know it was a topic at FUDCon
19:49:48 <herlo> I was thinking about setting this up for myself anyway.
19:49:54 <nirik> problem is that lacks some things we need...
19:50:04 <nirik> no wiki? no ticketing system?
19:50:10 <herlo> nirik: yeah, I was kind of wondering about that too...
19:50:14 <skvidal> nirik: no users..
19:50:27 <skvidal> does it even have logins?
19:50:30 <herlo> just thought I'd throw it out there
19:50:30 <skvidal> or is it just a better cgit?
19:50:37 <nirik> we can take a look tho. ;)
19:50:42 <skvidal> herlo: not being derisive - I just couldn't tell from looking at it
19:50:57 <herlo> skvidal: yeah, me neither. I was going to hav ea look if people were interested
19:51:04 <herlo> I could give feedback in a couple meetings from now
19:51:06 <skvidal> herlo: please
19:51:08 <nirik> sure, sounds good.
19:51:08 <skvidal> by all means
19:51:12 <nirik> thanks herlo
19:51:13 <herlo> nice
19:51:14 <herlo> np
19:51:23 <nirik> skvidal: you have something?
19:51:30 <skvidal> wanted to mention these items
19:51:33 <skvidal> we typed these up last week
19:51:35 <skvidal> https://fedoraproject.org/wiki/Infrastructure_FedoraBugzilla
19:51:36 <skvidal> and
19:51:43 <nirik> ah, yeah.
19:51:46 <skvidal> https://fedoraproject.org/wiki/Infrastructure_FedoraHosted_Version2_Notes
19:52:02 <skvidal> both of them are things we've been thinking about for THE FUTURE
19:52:07 <skvidal> constructive input is welcome
19:52:12 * nirik nods.
19:52:18 <skvidal> also
19:52:30 <nirik> look for more discussion on those as we get more input and ideas, etc.
19:52:32 <skvidal> if anyone here has good, hands-on, experience with pgpoolII in production
19:52:40 <skvidal> or any other db replication/HA system
19:52:53 <skvidal> please consider yourself invited to tell us all about your experiences
19:53:05 <nirik> yep. That would be lovely.
19:53:15 <skvidal> the more handson the better
19:53:19 <skvidal> the more experience the better
19:53:28 <skvidal> especially when it comes to failure modes
19:53:38 <skvidal> and how they resynchronize in the event of a failure
19:53:49 * herlo read handson as hanson and was confuzled for a moment wondering why we were talking about a boy band
19:53:57 <skvidal> mmmm bop
19:53:59 <herlo> lol
19:54:02 <nirik> ha.
19:54:03 <herlo> you know you sang it
19:54:06 <herlo> :D
19:54:14 <skvidal> nirik: that's all I had
19:54:17 <nirik> Any other items for open floor from anyone?
19:54:18 <cyberworm54> man finally i caught you guys
19:54:19 <nirik> thanks skvidal
19:54:25 <nirik> hey cyberworm54.
19:54:26 <skvidal> cyberworm54: ?
19:54:50 <cyberworm54> saving time really mess up the meeting time for me
19:55:19 <cyberworm54> I've check at 1 pm est 2pm and I assume it is 3pm est
19:55:28 <nirik> cyberworm54: yeah, it's anoying to me too. ;)
19:55:36 <nirik> anyhow, did you have anything to bring up or discuss?
19:55:42 <frankly3d> Apologies have to go whingin child
19:56:28 <nirik> frankly3d: no worries. ;)
19:56:32 * nirik notes we are almost out of time
19:56:58 * cyberworm54 knows now it is ath 3PM EST
19:57:38 <jerzyr> I'll be looking nirik contact ...
19:57:41 <skvidal> cyberworm54: need tardis
19:57:58 <nirik> jerzyr: ?
19:58:03 <jerzyr> yes :)
19:58:18 <nirik> what are you looking for from me?
19:58:32 * nirik isn't sure if he's forgotten something he was supposed to do or what...
19:59:01 <jerzyr> after ..
19:59:37 <nirik> well, I will definitely be around... ;)
19:59:46 * nirik will close out the meeting in a few here if nothing else.
19:59:51 <cyberworm54> Well I guess I will just read the log when posted in the infra mail list
20:00:25 <nirik> Thanks for coming everyone!
20:00:28 <nirik> #endmeeting
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-03-27/fedora-meeting…
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-27/fedora-meeting…
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-27/fedora-meeting…
Paul
===================================================
#fedora-meeting-1: Fedora ARM weekly status meeting
===================================================
Meeting started by pwhalen at 20:00:33 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-27/fedora-meeting…
.
Meeting summary
---------------
* 0) Status of ACTION items from our previous meeting (pwhalen,
20:02:43)
* LINK:
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-20/fedora-meeting…
(pwhalen, 20:02:51)
* -RESOLVED- pwhalen and mlangsdorf are working on the highbank issues
- Issue turned out to be HW related. (pwhalen, 20:03:02)
* -COMPLETE- pbrobinson will update 3.9 kernel config over weekend and
spin out a new test build (pwhalen, 20:03:13)
* LINK:
http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=130599
(pwhalen, 20:03:25)
* pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
(pwhalen, 20:03:49)
* ACTION: pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
(pwhalen, 20:04:30)
* 1) Problem Packages (pwhalen, 20:05:45)
* tog-pegasus, mongodb, some ruby apps are the top issues (bconoboy,
20:08:03)
* mongodb bz #921226: It now builds but the resulting rpms do not
function (bconoboy, 20:12:44)
* - ruby packages fixed : rubygem-nokogiri, rubygem-gherkin,
rubygem-ffi, ruby-korundum (pwhalen, 20:17:14)
* AGREED: jcapik and colleagues are awesome for fixing them
(bconoboy, 20:17:31)
* being analyzed : rubygem-RedCloth (pwhalen, 20:17:38)
* 2) F19: uImage load addresses with unified kernel (pwhalen, 20:18:32)
* We will use bootz wherever possible for F19 (bconoboy, 20:29:59)
* Currently bootz is not an option for armada-xp, but this is being
checked on with Marvell (bconoboy, 20:30:14)
* Bootz may or may not be an option for omap, this needs to be
investigated further (bconoboy, 20:30:29)
* Whether or not omap can use bootz, some image post-processing will
be necessary due to providing board specific MLO binaries
(bconoboy, 20:30:55)
* 3) Open Floor (pwhalen, 20:31:45)
* LINK:
http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=130599
(pwhalen, 20:40:35)
Meeting ended at 20:46:47 UTC.
Action Items
------------
* pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
Action Items, by person
-----------------------
* pbrobinson
* pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bconoboy (50)
* pwhalen (39)
* dmarlin (30)
* jonmasters (15)
* dgilmore (14)
* zodbot (12)
* fossjon (9)
* jcapik (8)
* masta (7)
* ctyler (4)
* j_dulaney (3)
* ahs3 (2)
* oatley (2)
* pbrobinson (0)
=================================================
#fedora-blocker-review: f19alpha-blocker-review-3
=================================================
Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-…
Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-…
Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-…
Meeting summary
---------------
* Roll Call (tflink, 16:01:05)
* Introduction (tflink, 16:08:31)
* 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:08:44)
* We'll be following the process outlined at: (tflink, 16:08:51)
* LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(tflink, 16:08:52)
* The bugs up for review today are available at: (tflink, 16:08:57)
* LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink,
16:08:57)
* The criteria for release blocking bugs can be found at: (tflink,
16:09:07)
* LINK:
https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria
(tflink, 16:09:07)
* Up for review today, we have: (tflink, 16:09:40)
* 16 Proposed Blockers (tflink, 16:09:52)
* 8 Accepted Blockers (tflink, 16:09:52)
* 3 Proposed Freeze Exceptions (tflink, 16:09:52)
* 1 Accepted Freeze Exceptions (tflink, 16:09:52)
* (926913) rescue mode fails with traceback (tflink, 16:12:25)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=926913 (tflink,
16:12:25)
* Proposed Blocker, anaconda, POST (tflink, 16:12:25)
* AGREED: 926913 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "The rescue mode of the installer must start
successfully and be able to detect and mount an existing default
installation." (tflink, 16:16:49)
* (924138) Cannot set password for root during text-mode installation
(tflink, 16:17:00)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924138 (tflink,
16:17:04)
* Proposed Blocker, anaconda, VERIFIED (tflink, 16:17:06)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=926900#c1
(robatino, 16:18:44)
* this bug is already VERIFIED, skipping review since we're not in
freeze yet (tflink, 16:20:56)
* (924162) Software selection checking doesn't work. (tflink, 16:21:18)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924162 (tflink,
16:21:18)
* Proposed Blocker, anaconda, NEW (tflink, 16:21:18)
* AGREED: 924162 - RejectedBlocker - This does not hit any of the
alpha release criteria as it requires the user to ignore dep errors
and proceed with the install and is thus rejected as a release
blocking bug for Fedora 19 alpha (tflink, 16:28:41)
* (926916) anaconda can't report traceback to bugzilla (tflink,
16:28:57)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=926916 (tflink,
16:28:57)
* Proposed Blocker, anaconda, NEW (tflink, 16:28:57)
* AGREED: 926916 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "The installer must be able to report failures to
Bugzilla, with appropriate information included." (tflink,
16:32:15)
* (928279) anaconda doesn't start on LiveCD (in Gnome) (tflink,
16:32:31)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928279 (tflink,
16:32:31)
* Proposed Blocker, anaconda, NEW (tflink, 16:32:31)
* AGREED: 928279 - While this sounds like it has potential to be a
release blocking issue, we need more details before making a final
decision - will revisit when more details are available (tflink,
16:42:09)
* (928303) F19 KDE contains F18 artwork (tflink, 16:42:21)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928303 (tflink,
16:42:21)
* Proposed Blocker, distribution, NEW (tflink, 16:42:21)
* AGREED: 928303 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "The default desktop background must be different
from that of the two previous stable releases" (tflink, 16:46:30)
* (927967) initial-setup is not included in default install (tflink,
16:46:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=927967 (tflink,
16:46:47)
* Proposed Blocker, distribution, MODIFIED (tflink, 16:46:47)
* AGREED: 927967 - AcceptedBlocker - Violates the following F19
release criterion as firstboot has been retired: "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, 16:54:35)
* (928353) FF 32b crashes for a number of web pages (tflink, 16:54:49)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928353 (tflink,
16:54:50)
* Proposed Blocker, firefox, NEW (tflink, 16:54:50)
* AGREED: 928353 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "It must be possible to run the default web
browser and a terminal application from all release-blocking desktop
environments." (tflink, 16:59:44)
* (923364) [3.7.92] Despite moving mouse in Black Screen(Blank Screen),
gnome-shell doesn't switch to unlock screen (tflink, 17:02:10)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923364 (tflink,
17:02:13)
* Proposed Blocker, gnome-shell, NEW (tflink, 17:02:16)
* AGREED: 923364 - RejectedBlocker - While this is annoying, it is
possible to workaround by pressing esc or disabling screen lock. As
such, it does not violate any of the F19 alpha release criterion and
is rejected as a release blocking bug for F19 alpha (tflink,
17:07:57)
* (924031) initial-setup-graphical.service fails (tflink, 17:08:10)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924031 (tflink,
17:08:11)
* Proposed Blocker, initial-setup, POST (tflink, 17:08:11)
* it isn't clear whether it's a good idea for initial-setup to have a
package-level dep on anaconda, the exact method of fixing will
require more conversation with devs (tflink, 17:12:59)
* AGREED: 924031 - AcceptedBlocker - Violates the following F19 alpha
release criterion for the KDE spin: "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, 17:14:36)
* (928228) global name 'ROOT_PATH' is not defined (tflink, 17:14:57)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928228 (tflink,
17:14:58)
* Proposed Blocker, python-blivet, NEW (tflink, 17:14:58)
* AGREED: 928228 - AcceptedBlocker - Violates the following F19 alpha
release criterion for installs to bare-metal: "The installer must be
able to complete an installation to a single disk using automatic
partitioning." (tflink, 17:25:28)
* (922988) python-blivet not creating /sys and /run on /mnt/sysimage
(tflink, 17:25:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922988 (tflink,
17:25:50)
* Proposed Blocker, python-blivet, MODIFIED (tflink, 17:25:52)
* AGREED: 922988 - RejectedBlocker - The hacks in place are enough to
make this not a release blocking issue for F19 alpha and thus, this
bug is rejected as a blocker for F19 alpha (tflink, 17:31:14)
* (919374) /var/run not created with var_run_t leading to many boot
avc's (tflink, 17:31:28)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919374 (tflink,
17:31:31)
* Proposed Blocker, selinux-policy, MODIFIED (tflink, 17:31:34)
* AGREED: 919374 - AcceptedBlocker - Violates the following F19 alpha
release criterion for DVD and netinstall installs: "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, 17:41:05)
* (924500) kvm f19 guest reports "BUG: bad unlock balance detected"
(backtrace) when using vnc/cirrus on f17 host (tflink, 17:41:15)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924500 (tflink,
17:41:18)
* Proposed Blocker, xorg-x11-drivers, NEW (tflink, 17:41:20)
* AGREED: 924500 - RejectedBlocker - Running on virt is not an alpha
release criteria and later comments make it sound like this might
not be so widespread (tflink, 17:45:02)
* (924494) kvm f19 guest xorg segfault with spice/qlx on f17 hosts
(tflink, 17:48:07)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924494 (tflink,
17:48:10)
* Proposed Blocker, xorg-x11-drivers, NEW (tflink, 17:48:12)
* AGREED: 924494 - RejectedBlocker - Virt-only bugs do not qualify as
blockers for F19 alpha (tflink, 17:51:26)
* (928339) systemd[1]: Failed to mount /run: No such file or directory
(tflink, 17:51:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928339 (tflink,
17:51:50)
* Proposed Blocker, systemd, NEW (tflink, 17:51:53)
* AGREED: 928339 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "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:01:28)
* ACTION: tflink or adamw to finish secretarializing from a previous
meeting and reject 894110 as a proposed FE (tflink, 18:03:40)
* (920380) Graphical menu screen garbled on thinkpad T400 (tflink,
18:03:50)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=920380 (tflink,
18:03:50)
* Proposed Freeze Exceptions, grub2, NEW (tflink, 18:03:50)
* AGREED: 920380 - RejectedFreezeException - There is no proposed fix
and no clear idea on how to fix this issue. Rejected as freeze
exception for F19 alpha, please re-propose if there is a fix
imminently available. (tflink, 18:13:07)
* (923547) Packages listed as 'optional' in comps being pulled into F19
live composes (tflink, 18:13:20)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923547 (tflink,
18:13:23)
* Proposed Freeze Exceptions, yum, NEW (tflink, 18:13:25)
* AGREED: 923547 - AcceptedFreezeException - This causes oversized
isos and while this isn't a release blocking issue for Alpha, it is
for beta and would be good to get it fixed now if possible (tflink,
18:20:23)
* (919935) enblend FTBFS due to doc/texinfo related issues (tflink,
18:20:55)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919935 (tflink,
18:20:56)
* Accepted Blocker, enblend, NEW (tflink, 18:20:56)
* AGREED: 919935 - RejectedBlocker - While still a serious issue, the
components of this which were blocking the release of F19 alpha have
been solved (enblend has been built and pulled into TC2). Thus, this
is no longer considered a release blocking bug for F19 alpha
(tflink, 18:29:35)
* (924248) repoclosure failure on 19 Alpha TC1 DVDs (enblend) (tflink,
18:29:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924248 (tflink,
18:29:50)
* Accepted Blocker, enblend, NEW (tflink, 18:29:53)
* this has been reported as fixed with TC2, can be closed (tflink,
18:30:25)
* (917246) gdm-simple-slave crashes on login attempt (tflink, 18:30:35)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=917246 (tflink,
18:30:35)
* Accepted Blocker, gnome-shell, MODIFIED (tflink, 18:30:36)
* no movement on this bug in a week (tflink, 18:31:41)
* some disagreement on where the bug should be fixed - in comps by
adding gnome-session-xsession or if GDM should be able to survive
without an existing session (tflink, 18:32:45)
* still waiting for feedback from desktop team on possible fix
(tflink, 18:33:16)
* AGREED: 917246 - RejectedBlocker - This symptom is no longer present
after gnome-session-xsession was added to the comps group. Thus,
this is no longer considered severe enough to block release of F19
alpha (tflink, 18:37:30)
* (923951) yum is getting stuck in urlgrabber (tflink, 18:37:34)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923951 (tflink,
18:37:37)
* Accepted Blocker, python-urlgrabber, NEW (tflink, 18:37:39)
* progress is being made, an initial root cause has been proposed
(tflink, 18:39:14)
* (924256) repoclosure failure on 19 Alpha TC1 DVDs (resteasy) (tflink,
18:39:52)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924256 (tflink,
18:39:55)
* Accepted Blocker, resteasy, NEW (tflink, 18:39:57)
* still broken in TC2 (tflink, 18:40:08)
* resteasy has been FTBFS in rawhide since 2013-02-22 (tflink,
18:41:34)
* ACTION: adamw to check into resteasy dep errors on tomcat6 and
whether it needs to be removed (tflink, 18:47:52)
* (924244) repoclosure failure on 19 Alpha TC1 DVDs (rubygem-rails)
(tflink, 18:48:13)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924244 (tflink,
18:48:16)
* Accepted Blocker, rubygem-rails, MODIFIED (tflink, 18:48:19)
* this was fixed in TC2, bug can be closed (tflink, 18:48:40)
* (924258) repoclosure failure on 19 Alpha TC1 DVDs (rubygem-railties)
(tflink, 18:49:40)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=924258 (tflink,
18:49:43)
* Accepted Blocker, rubygem-railties, MODIFIED (tflink, 18:49:46)
* this has been fixed in F19 alpha TC2, can be closed (tflink,
18:50:05)
* (928302) setroubleshoot-server-3.2.3-1.fc19.i686 requires
setools-libs-python >= 3.3.7-19 (tflink, 18:50:39)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=928302 (tflink,
18:50:42)
* Accepted Blocker, setroubleshoot, MODIFIED (tflink, 18:50:44)
* this has been reported to be fixed in newest setroubleshoot but not
yet in a TC (tflink, 18:51:25)
* can likely be closed after the next TC build (tflink, 18:51:34)
* Open Floor (tflink, 18:52:11)
Meeting ended at 19:12:27 UTC.
Action Items
------------
* tflink or adamw to finish secretarializing from a previous meeting and
reject 894110 as a proposed FE
* adamw to check into resteasy dep errors on tomcat6 and whether it
needs to be removed
Action Items, by person
-----------------------
* adamw
* tflink or adamw to finish secretarializing from a previous meeting
and reject 894110 as a proposed FE
* adamw to check into resteasy dep errors on tomcat6 and whether it
needs to be removed
* tflink
* tflink or adamw to finish secretarializing from a previous meeting
and reject 894110 as a proposed FE
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tflink (270)
* adamw (163)
* kparal (89)
* brunowolff (51)
* jreznik (20)
* smooge (8)
* zodbot (5)
* robatino (5)
* satellit_e (4)
* nirik (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
======================
#fedora-meeting: FAmNA
======================
Meeting started by dan408 at 01:00:52 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-27/famna.2013-03-27…
.
Meeting summary
---------------
* Roll Call (dan408, 01:01:05)
* Announcements (dan408, 01:03:26)
* Budget (dan408, 01:07:05)
* LINK:
https://docs.google.com/spreadsheet/ccc?key=0ApBrbq5j6NbOdG0zQzVvR3VqQ05NaE…
(dan408, 01:08:25)
* FAmNA approves $500 to sponsor SELF (inode0, 01:12:26)
* ACTION: herlo to make a report on ticket (masta, 01:25:19)
* Open Floor (dan408, 01:31:17)
* LINK: https://fedoraproject.org/wiki/LinuxFest_Northwest_(LFNW)_2013
(rbergeron, 01:57:20)
Meeting ended at 02:03:42 UTC.
Action Items
------------
* herlo to make a report on ticket
Action Items, by person
-----------------------
* **UNASSIGNED**
* herlo to make a report on ticket
People Present (lines said)
---------------------------
* dan408 (116)
* masta (67)
* award3535 (62)
* inode0 (43)
* rbergeron (27)
* suehle (20)
* zodbot (11)
* nb (4)
* inode1 (2)
* adamw (0)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As promised, I'm catching up on sending out meeting summaries. The notes below
will cover the most recent 25 March meeting as well as last week's 18 March
meeting.
- - 18 March 2013 -
We talked about the progress towards changing our publishing platform. It was
generally decided that Rudi had things well in hand, but that we'd like to
know what was going on. Lnovich offered to track him down.
I brought up a thread on devel@ containing a proposal for a help center
desktop application, which you can read at
http://lists.fedoraproject.org/pipermail/devel/2013-March/180093.html or
https://fedoraproject.org/wiki/Design/Help_Center_Idea . I expressed concern
that unvalidated content from ask.fp.o would take semantic precedence over
curated content from the docs writers, and urged the other members to comment
on the proposal with their own thoughts.
The group graciously accepted nagging about Release Note beats.
jreznik asked us to review his comments on the docs list, and the wiki page
for the changes process. The general feeling has been that we would like help
with raw content, and want developers to know don't expect polish.
The meeting ended a bit late, apologies to the QA team. Zodbot asked us to
read some links as the meeting closed:
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-18/docs_project_age…http://meetbot.fedoraproject.org/fedora-meeting/2013-03-18/docs_project_age…
- - 25 March 2013 -
The new publishing platform was on the table again. lnovich spoke with Rudi
about it, as did I. The end result will give us a very simple and effective
publishing process that our RH contributors will probably find familiar. If I'm
recalling it correctly, some magic of publican and git combines to allow us to
publish a single translation of a document with a single command, nicely
wrapping up the RPM packaging process, building in git, and installing to
production in one go.
rbergeron stopped by, and we touched on the Changes/Feature process. [ I'm
still not sure of the appropriate name for it! ] We need to make a point to
validate the information we pull out of the Feature pages into the beats at
each release stage, because the former is dynamic and the latter has been...
less dynamic.
shaiton valiantly volunteered to clean up the duplicate language teams on
transifex. It looks like much of that has been completed by the time I sat
down to write the summary - thanks shaiton!
The logs are available for your review at:
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-25/fedora_docs.2013…http://meetbot.fedoraproject.org/fedora-meeting/2013-03-25/fedora_docs.2013…
- Afterthoughts -
If you can't make it to the meeting, please use the list!
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRUUGSAAoJEL1wZM0+jj2ZX24H/j19yAwuFAiB5R0yU56zhpi4
/HlRHjtUHaEe4KuO82Qajki4E4Icp/z4NfcABAKZ5lAfOGZKuLl1j0VPPzBxx5/G
rxzBQMuR+6dKOdkhqSMKvi4lByxmVEtXaC3HLA00IlPY5BSGflVZr4iHQZSZdvKX
zpKbtil5K1BaP3FJ48q2MRQyP0ex77sLLTGIMZjmgkVrvk5XSqEnnI8vcIJBLUCj
/9RLbMXea6epQk/eqCAueC87eMNJb9oa/B/adkQNMNuOfyWy9ocmgH+4hD3HrlqW
p5YUk6eUJdzdL7K+B1WEFrkewxnMkuh0aqB6eOFX6JT4iteXQiOKz7b/Nlsev/k=
=7U7n
-----END PGP SIGNATURE-----
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20130325
Next meeting is scheduled for 2013-04-01 at 1500 UTC in #fedora-meeting.
If you have topics you think we should bring up at the
meeting, please add them to the Wiki page at
https://fedoraproject.org/wiki/QA/Meetings/20130401 . Thanks!
TOPIC: Previous meeting follow-up
=======================================================================
* adamw to work with developers on getting F19 images to
bootable state - this was done: TC1 is bootable
* adamw to work out a fallback plan with desktop team if we
cannot get working images by Wednesday - this was done: Test
Day went ahead with F19 images
TOPIC: Fedora 19 Alpha status
=======================================================================
* Bug #923951[1] is a major development/testing roadblock
* TC1 DVD install fails on dependency issues, so we need a TC2
soon without those
* We need to ensure we do all the tests that don't require
network install at least, on TC2
TOPIC: Test Days
=======================================================================
* 2013-03-21 GNOME Test Day[2] went ahead with working
F19-based images, attendance was better than 3.4 and 3.6 but
still below where it could be: try to improve outside
publicity for future events
* kparal suggests that the scope of the GNOME Test Day has
gotten wider than a single day can really cover and suggests
splitting future events into multiple days
* kparal and martix will look after System Certificates Test
Day[3] planning
TOPIC: Open floor
=======================================================================
* tflink still working on getting the blocker proposal webapp
into production, it's on staging now but still a couple of
bugs to fix
ACTION ITEMS
=======================================================================
* adamw to request a TC2 as soon as it's clear we can compose
one without critical dep issues
* kparal to talk to martix and ensure System Certificates Test
Day page[3] will be in shape and ready to go ahead for
Thursday, or delay the event
1. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=923951
2. https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8
3. https://fedoraproject.org/wiki/Test_Day:2013-03-28_System_Certificates
4. https://lists.fedoraproject.org/pipermail/test/2013-March/114305.html
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20130318
Next meeting is scheduled for 2013-03-25 at 1500 UTC in #fedora-meeting.
If you have topics you think we should bring up at the
meeting, please add them to the Wiki page at
https://fedoraproject.org/wiki/QA/Meetings/20130325 . Thanks!
TOPIC: Previous meeting follow-up
=======================================================================
* jreznik to ink in the proposed image schedule, and add a Test
Day entry - this was done: QA[1], release engineering[2]
TOPIC: Fedora 19 Alpha status
=======================================================================
* We discussed the current state of F19 test images: potential
issues in image compose, dracut, selinux and
gnome-initial-setup, adamw and anaconda team investigating
* We noted that both TC1 and GNOME Test Day images were
required soon
TOPIC: Criteria re-design
=======================================================================
* There was general agreement to give adamw's revised Alpha[3]
and Beta[4] criteria a try for F19
TOPIC: Test Days
=======================================================================
* We agreed to look at a fallback plan of building GNOME 3.8
images on Fedora 18 if workable Fedora 19 images were not
possible for the GNOME Test Day
TOPIC: Open floor
=======================================================================
* tflink would be AFK at Pycon much of the week
ACTION ITEMS
=======================================================================
* adamw to work with developers on getting F19 images to
bootable state
* adamw to work out a fallback plan with desktop team if we
cannot get working images by Wednesday
1. http://fedorapeople.org/groups/schedule/f-19/f-19-quality-tasks.html
2. http://fedorapeople.org/groups/schedule/f-19/f-19-releng-tasks.html
3. https://lists.fedoraproject.org/pipermail/test/2013-March/114198.html
4. https://lists.fedoraproject.org/pipermail/test/2013-March/114305.html
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Hi all,
The IRC meeting minutes tonight are available at the link [1]. Thanks
everyone for attending the meeting.
In the meeting we mainly talked about tomorrow's offline gather up in
Beijing, FUDCon APAC 2014 bid. We also voted the beginning time of
IRC meetings from now on and decided to move it to 21:00(UTC+8).
The next IRC meeting will be held on next Friday (2013-03-29). Please
come and join the discussion if you can! Note the change of the
beginning time!
1.
http://meetbot.fedoraproject.org/fedora-zh/2013-03-22/fedora-zh.2013-03-22-…
==================
#fedora-zh Meeting
==================
Meeting started by alick at 12:00:31 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-zh/2013-03-22/fedora-zh.2013-03-22-…
.
Meeting summary
---------------
* 点名 (alick, 12:01:22)
* FUDCON APAC 2014 举办申请 (alick, 12:08:30)
* IDEA: 大家对各个申办地的观点都是很客观的,但每个城市都有不同的优缺
点,所以找不出完美的选择 (endle, 12:25:15)
* IDEA: 我建议先总结下影响申办的主要因素 (zsun, 12:25:27)
* IDEA: 不妨有共识的人组成一个小组(比如北京组,上海组),然后总结一个
自己支持的城市书面的评价。在此基础上再进行下一步的讨论
(endle, 12:26:57)
* IDEA: 我们应该想应该哪里举办,而不是哪里不应该举办。 (alick, 12:28:24)
* IDEA: 对申办城市选择意见相同的人自发组成小组 (endle, 12:31:38)
* 三月线下活动(BJGUG 社区联合活动) (alick, 12:32:51)
* 北京GNOME用户组三月活动之开源社区大联盟 (alick, 12:33:37)
* LINK: http://www.bjgug.org/node/692 (alick, 12:34:14)
* 时 间: 2013年3月23日 周六 14:00~17:00 (alick, 12:34:26)
* 地 点: 北京 图灵文化发展有限公司,北京市朝阳区北苑路13号院1号楼领地
OFFICE C座603室 (alick,
12:34:35)
*
地图:http://lisp.org.cn/wiki/_media/lisp/event/tuling-
address.jpg?cache=
(alick, 12:34:52)
* gbraad 可能也去呀 (alick, 12:37:23)
* 日程:14:45-15:30 Fedora社区 (alick, 12:39:05)
* 关于 IRC 会议起始时间的投票 (alick, 12:41:07)
* IDEA: 把时间推迟半小时, 8:30-9:30能不能好一点? (endle, 12:45:56)
* 投票今后的IRC会议起始时间点:1)20:00 2)20:30 3)21:00 (alick, 12:54:03)
* 投票结果:1) 0 票 2) 3 票 3) 5 票 (alick, 13:12:01)
* 今后的IRC会议起始时间点定为 21:00 (alick, 13:13:17)
* ACTION: alick to notify the change in ML (alick, 13:13:48)
Meeting ended at 13:16:31 UTC.
Action Items
------------
* alick to notify the change in ML
Action Items, by person
-----------------------
* alick
* alick to notify the change in ML
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* alick (124)
* endle (34)
* zsun (33)
* microcai (15)
* zodbot (13)
* liangsuilong (6)
* Robin_cheese_Lee (6)
* diseng (6)
* endle___ (6)
* BadGirl (3)
* kaio (3)
* fracting (2)
* gfrog (1)
* kingheaven (1)
* CyrusYzGTt (0)
* cswiii (0)
* gbraad (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Alick
Fedora 18 (Spherical Cow) user
https://fedoraproject.org/wiki/User:Alick
============================================
#fedora-meeting: Infrastructure (2013-03-21)
============================================
Meeting started by nirik at 19:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-21/fedora_marketing…
.
Meeting summary
---------------
* welcome y'all (nirik, 19:00:01)
* New folks introductions and Apprentice tasks. (nirik, 19:02:12)
* Applications status / discussion (nirik, 19:07:52)
* LINK: https://github.com/fedora-infra/rube (relrod, 19:08:42)
* selenium test suite for stg hosts:
https://github.com/fedora-infra/rube (nirik, 19:10:12)
* blockbugs moving into staging (nirik, 19:10:19)
* new fedora-tagger v2.0 work starting. (nirik, 19:10:29)
* Sysadmin status / discussion (nirik, 19:21:08)
* LINK:
https://fedoraproject.org/wiki/Infrastructure_FedoraHosted_Version2_Notes
(skvidal, 19:24:28)
* Private Cloud status update / discussion (nirik, 19:39:41)
* Upcoming Tasks/Items (nirik, 19:40:13)
* 2013-03-19 to 2013-03-26 - koji update (nirik, 19:40:25)
* 2013-03-29 - spring holiday. (nirik, 19:40:25)
* 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik,
19:40:25)
* 2013-04-15 - remove legacy-openid (nirik, 19:40:25)
* 2013-04-16 F19 alpha release (nirik, 19:40:26)
* 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik,
19:40:27)
* 2013-05-21 F19 beta release (nirik, 19:40:28)
* 2013-05-31 end of 1st quarter (nirik, 19:40:30)
* 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik,
19:40:32)
* 2013-06-25 F19 FINAL release (nirik, 19:40:33)
* Open Floor (nirik, 19:41:12)
Meeting ended at 19:52:23 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (124)
* skvidal (76)
* pingou (46)
* biker (30)
* zodbot (8)
* relrod (8)
* suehle (6)
* jerzyr (6)
* puiterwijk (3)
* maayke (1)
* smooge (1)
* abadger1999 (0)
* lmacken (0)
* threebean (0)
* ricky (0)
* mdomsch (0)
* dgilmore (0)
* CodeBlock (0)
--
19:00:01 <nirik> #startmeeting Infrastructure (2013-03-21)
19:00:01 <zodbot> Meeting started Thu Mar 21 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:01 <nirik> #topic welcome y'all
19:00:01 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean
19:00:01 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean
19:00:09 * skvidal is here
19:00:11 * relrod here
19:00:21 * maayke is here
19:00:25 * puiterwijk is around-ish (just don't expect too intelligent answers from me ;) )
19:00:58 <smooge> sort of here
19:01:17 * nirik will another min for folks to wander in...
19:01:29 * pingou here
19:02:12 <nirik> #topic New folks introductions and Apprentice tasks.
19:02:28 <nirik> any new folks want to introduce themselves? or have questions?
19:02:40 * skvidal notes the infra team appears to be full of sick people
19:02:44 * skvidal moves away from all of them
19:02:51 <nirik> :)
19:03:04 <jerzyr> yes :)
19:03:39 <pingou> skvidal: sick ?
19:03:47 <nirik> hey jerzyr. Welcome. Care to send us a one line intro?
19:03:48 <skvidal> pingou: smooge and puiterwijk
19:03:55 <skvidal> pingou: both under the weather
19:03:58 <nirik> are you interested in sysadmin or application development?
19:03:58 <jerzyr> short bio: for 10 years, I teach students algorithms and data structures
19:04:10 <pingou> oh
19:04:16 <jerzyr> sorry :)
19:04:32 <skvidal> jerzyr: you're fine!
19:04:38 <jerzyr> ;)
19:04:46 <skvidal> jerzyr: so you were a teacher for 10yrs - now what do you do?
19:05:19 <jerzyr> I'm looking for practice as a consultant to developers
19:05:56 <zodbot> suehle: Error: Can't start another meeting, one is in progress.
19:05:59 <suehle> #meetingname Fedora Marketing
19:05:59 <zodbot> The meeting name has been set to 'fedora_marketing'
19:06:00 <suehle> doh
19:06:04 <skvidal> suehle: no
19:06:06 <nirik> suehle: oops.
19:06:06 <skvidal> :)
19:06:11 <skvidal> suehle: are we overlapping?
19:06:20 <nirik> suehle: we didn't switch for DST, but you folks did?
19:06:22 <suehle> Yeah, but I doubt there's a swarm waiting.
19:06:28 <suehle> nirik, ooooh
19:06:46 <suehle> Well, if there's anyone here who actually wants to talk to me about marketing, I'll move over to #fedora-meeting-1
19:06:53 <skvidal> suehle: thank you
19:06:55 <suehle> nirik, it's entirely possible that didn't even occur to me :)
19:07:03 <nirik> jerzyr: welcome again. I can point you at sysadmin stuff after the meeting over in #fedora-admin... most of our app developer types are at pycon this week, but they hang out in #fedora-apps.
19:07:18 <nirik> suehle: yeah, we can move next week if you want us too... whatever works. ;)
19:07:52 <nirik> #topic Applications status / discussion
19:07:59 <nirik> any app/devel news this week?
19:08:08 <nirik> (again, many folks are at pycon...)
19:08:40 <relrod> threebean started working on a selenium test suite for our staging infra, it's pretty neat
19:08:42 <relrod> https://github.com/fedora-infra/rube
19:08:43 <nirik> I've been working a bit on getting blockerbugs app moved into staging.
19:09:07 <nirik> but it needs db setup, and proxy setup and I've not had time to poke at it much
19:09:24 <pingou> I've pushed to github a new branch for fedora-tagger, basically the basis for fedora-tagger v2.0
19:09:51 <nirik> cool.
19:09:57 <pingou> it comes with its own API (that's what is there atm), handles tagging and rating, change a little bit the db scheme
19:10:12 <nirik> #info selenium test suite for stg hosts: https://github.com/fedora-infra/rube
19:10:15 <pingou> threebean wants to port the UI to it soonish
19:10:19 <nirik> #info blockbugs moving into staging
19:10:29 <nirik> #info new fedora-tagger v2.0 work starting.
19:10:39 <nirik> cool.
19:10:40 <pingou> and the idea would be to integrate this with the gnome-app store that rhughsie is working on
19:10:56 <nirik> ok.
19:11:05 * nirik keeps meaning to read up on that, but hasn't yet
19:11:05 <pingou> otherwise, more copr, more pkgdb2, a surprise for next week and fedocal is in stg :)
19:11:18 <skvidal> pingou: wait
19:11:20 <skvidal> hold on
19:11:22 <skvidal> a surprise?
19:11:25 <pingou> yes :)
19:11:29 * skvidal dislikes surprises
19:11:50 <pingou> it's kinda ready for a 1.0 but I'm waiting for threebean to be there to reveal it :)
19:11:55 <nirik> a good surprise I hope. ;)
19:12:03 <pingou> I don't think you will dislike it :)
19:12:22 <pingou> (well, I certainly hope so at least!)
19:12:23 <relrod> that's what they always say. ;)
19:12:37 <skvidal> yes...
19:12:39 <skvidal> I see
19:12:40 <pingou> suspens... :)
19:13:04 <skvidal> okay moving along
19:13:06 <nirik> relrod: random memory... what happened to that php auth thing we were going to try and use for wiki and gallery? did we just decide to look at moving to openid ?
19:13:24 * nirik feels bad we haven't gotten anything moving with gallery.
19:13:46 <skvidal> what is gallery _for_ again?
19:13:55 <relrod> nirik: Well I haven't done much with it recently (I might move it to the fedora-infra org and pick back up on it again) - but if we want to look at doing openid for Gallery instead, that's fine too
19:13:59 <nirik> pics at events.
19:14:04 <nirik> suehle and spot wanted it.
19:14:06 <skvidal> nirik: ah
19:14:26 <nirik> If we can, that might move us forward quicker and also just be nicer.
19:14:48 * nirik doesn't know the state of openid for wiki / gallery, but we can look.
19:15:09 <nirik> ok, any other application/devel news?
19:15:13 <relrod> nirik: There's no maintained/decent openid thing for Gallery, afaik - we can probably dep on another openid php library and write whatever it needs to link that library to gallery.
19:15:22 <nirik> ok.
19:15:31 <nirik> hopefully that wouldn't be _too_ much work
19:15:37 <relrod> indeed
19:15:39 <biker> what about using Persona?
19:15:51 <relrod> hah, that was just mentioned in -noc a few hours ago
19:15:56 <pingou> biker: w/ fas account ?
19:16:04 <biker> pingou, .fas rugebiker
19:16:06 <nirik> biker: we are looking into it...
19:16:21 <biker> .fas rugebiker
19:16:22 <nirik> biker: puiterwijk thinks it might be not too hard to add it...
19:16:23 <zodbot> biker: rugebiker 'Ruben Guerra Marin' <rguerra.marin(a)gmail.com>
19:16:45 <pingou> I don't follow ther
19:16:47 <pingou> +E
19:16:59 <nirik> pingou: mozilla is pushing a web auth thing called 'persona'
19:17:10 <nirik> we may be able to add support for it to our fas-openid...
19:17:21 <biker> pingou, https://www.mozilla.org/en-US/persona/
19:17:23 <puiterwijk> nirik: fedora-idprovider ;)
19:17:39 <nirik> sorry, another similar service anyhow. ;)
19:17:43 <pingou> I know what is personna, but then it's no longer linked to FAS, no?
19:17:50 <puiterwijk> actually the same, but renamed :)
19:17:51 <biker> for what i have read, persona is going more serious than openid
19:18:22 <skvidal> 'more serious'?
19:18:24 <pingou> or do we want to run our own persona server and link it to FAS ?
19:18:25 * nirik shrugs. I don't know if it will take off, but if we can easily provide support for it, it might be handy for those sites that add support for it.
19:18:28 * skvidal has no idea what that means in this context
19:18:45 <nirik> pingou: yes, a provider, like our fas-openid provides openid based on fas
19:18:53 <pingou> ok
19:19:00 <pingou> now I get it :)
19:19:06 <biker> oo,., i dont know if we can make like our own persona server
19:19:07 <skvidal> lwn had an article on it today
19:19:07 <nirik> "publisher" I guess they call it
19:19:21 <skvidal> biker: that's the whole point
19:19:33 * nirik nods.
19:19:36 <pingou> +1
19:19:48 <skvidal> so we can use apps using persona for auth
19:19:59 <skvidal> it's why we have an openid provider
19:20:01 <nirik> so, the entire idea is that we provide a personal publisher, so you can login to any persona enabled site by using your @fedoraproject.org address.
19:20:04 <pingou> like hypertitty :)
19:20:24 <biker> sweet (:
19:20:27 <nirik> pingou: yep.
19:20:31 <pingou> your @fedoraproject.org address and your FAS password
19:20:38 <nirik> right.
19:20:53 <skvidal> pingou: s/ti/ki/
19:21:02 <pingou> skvidal: indeed
19:21:02 <nirik> ok, shall we move on to exciting sysadmin news ?
19:21:08 <nirik> #topic Sysadmin status / discussion
19:21:09 <skvidal> oh yes, lets
19:21:20 <nirik> so, the fun has been fedorahosted.org this week.
19:21:29 <skvidal> 'the fun'
19:21:47 <skvidal> I 'think' I will 'talk' in 'quotes' for the rest of the 'meeting'
19:21:48 <nirik> basically it's been having load issues and isn't happy.
19:21:53 <nirik> 'yes'
19:22:07 * nirik hears skvidal talking like william shatner.
19:22:09 <pingou> skvidal: just """ now and close them at the end ;)
19:22:21 <nirik> anyhow, we have done some things to get the load back down to usable.
19:22:22 <skvidal> but I need ironic emphasis
19:22:31 <nirik> it's not great, but it should be usable right now.
19:22:40 <skvidal> nirik: it'sa darn-sight better than it was
19:22:48 <skvidal> so here's what we did
19:22:58 <skvidal> we look in gluster volume top hosted read|write|etc
19:23:00 <nirik> we are syncing all the data off it, then are going to have an outage in the next few days to move it to using ext4 directly without gluster.
19:23:17 <skvidal> oh sure - if you want to say it all quickly :)
19:23:24 <pingou> splitting ?
19:23:47 <skvidal> pingou: ?
19:23:48 <skvidal> what do you mean?
19:24:13 <pingou> do we take advantage of this and start splitting some of the project to another instance?
19:24:22 <nirik> pingou: yeah, thats the next part.
19:24:25 <skvidal> so that brings up the PLANS
19:24:28 <skvidal> https://fedoraproject.org/wiki/Infrastructure_FedoraHosted_Version2_Notes
19:25:04 <nirik> ideally the idea is that we get things seutp so we can split things by project.
19:25:15 <nirik> and have project1 and project2 on different machines, or the same...
19:25:28 <nirik> it's going to take some work to get there, but I think it's a good thing to do.
19:25:52 <skvidal> nirik: what about your other suggestion?
19:26:16 <nirik> Not sure. My other suggestion was more short term: just make a massive single instance and move everything to it.
19:26:24 <nirik> that doesn't help us scale at all
19:26:34 <nirik> but it would be simple, no changes...
19:26:48 <nirik> also, it would mean a spof for hosted.
19:26:56 <nirik> (which to be fair we currently have now too)
19:27:37 <nirik> I guess I'd like to try and finish the short term stuff and look at the list and then decide next week or so what we want to do
19:28:22 <nirik> thoughts? rants?
19:28:39 <skvidal> nirik: so I have a fear
19:28:46 <skvidal> on both things
19:29:08 <pingou> thought and rant ?
19:29:10 <skvidal> 1. if we don't move something around and stabilize it that next week we will have a NEW fire and all-hands on that
19:29:33 <nirik> well, I am hoping moving to the raw storage will help it a lot...
19:29:40 <skvidal> 2. that we're not changing things ENOUGH
19:29:41 <nirik> but I could be wrong.
19:29:42 <skvidal> in the v2
19:29:59 <pingou> skvidal: are you thinking cloud?
19:30:04 <nirik> yeah, that could be true.
19:30:09 <skvidal> pingou: no
19:30:14 <skvidal> pingou: I was actually thinking gitolite
19:30:18 <skvidal> or something like it
19:30:28 <skvidal> right now for commits we have local shell accounts
19:30:33 <skvidal> and normal unix groups
19:30:42 <skvidal> and that doesn't scale very well..
19:30:45 <pingou> oh, I thought we were using gitolite
19:30:46 <nirik> One thing is that we have been approaching it I think (or at least I have) more from a 'this is what we have, how do we safely migrate this to split it out' instead of 'hey, how would I setup to host 100 git projects with trac'
19:31:16 <skvidal> but nirik made a good a point that we're not seeing a lot of new projects being added at hosted in the recent past
19:31:22 <nirik> yeah, our ssh wrapper is... arcane.
19:31:34 <nirik> gitolite would be much much much better
19:31:46 <skvidal> nirik: so... that's fair - my argument was that if we break things out to project.fh.o - that we can try new things on new projects
19:31:49 <skvidal> nirik: or on test projects
19:31:54 <skvidal> w/o ripping up a lot of the infra
19:32:14 <skvidal> so our ssh wrapper exists afaict
19:32:18 <skvidal> b/c we support non-git repos
19:32:25 <skvidal> svn, bzr, hg
19:32:27 <nirik> right. and to be fair we wanted to do this for a long time, but we got it working 'good enough' that we put it lower pri, and... never got to it. ;)
19:32:46 <nirik> also true...
19:33:04 <pingou> as a side note, we convinced our only bzr user to move away from bzr at the last FUDCon :)
19:33:13 <skvidal> pingou: there are still remaining projects
19:33:22 <skvidal> pingou: notably only to move him to github :)
19:33:41 <pingou> skvidal: yes, still not sure how I feel about that part :s
19:33:51 <skvidal> anyway - that's immaterial
19:33:57 <skvidal> we have a number of svn and hg repos, too
19:34:01 <skvidal> some of them active
19:34:09 <nirik> so, I dunno... I guess I'd like more time to ponder on it... there doesn't seem to be a clear winner in my mind.
19:34:11 <skvidal> though, to be fair, the hg repo looks like a project graveyard
19:34:20 <skvidal> nirik: what do you mean clear-winner?
19:34:26 <skvidal> nirik: winner in which discussion?
19:35:07 <skvidal> nirik: so - we do have the scm-named CNAMES - so we can always walk away from the ssh-wrapper that way
19:35:17 <nirik> well, between: just do enough to split projects but otherwise keep setup, or just make a bigger one and leave things exactly the same, or put more work in it and do gitolite, etc.
19:35:44 <skvidal> nirik: and to be fair - that may be the simplest way to break these up git.fedorahosted.org (one big instance) and others.fedorahosted.org (other instance -not-so-big)
19:35:55 <nirik> yeah, thats an option too.
19:36:16 <skvidal> nirik: so I really do think that if we don't change things NOW we'll get it 'working' and we will never have the time to go back to it
19:36:18 <skvidal> EVER
19:36:23 <nirik> then we could be more flexable on the git one.
19:36:23 <skvidal> it's not like we have any spare hours
19:36:31 <nirik> yep. That is very true.
19:36:49 <nirik> on the other hand, we do have lots of things to work on, so how much work on this is important...
19:36:49 <skvidal> and we still need to COMPLETE the clouds
19:36:58 <skvidal> nirik: agreed
19:36:58 <nirik> yeah
19:37:23 <skvidal> nirik: if you want to get this moving and re-approach it later that's fine
19:37:30 <skvidal> nirik: but make the call one way or the other
19:38:02 <nirik> sure. I'd just like to ponder on it possibly over weekend... been fighting the fire enough to not have had time to think about the big picture
19:38:19 <skvidal> fair enough
19:38:43 <nirik> and hopefully it will be stable enough to do that. ;)
19:39:20 <nirik> ok, any other sysadminy news?
19:39:41 <nirik> #topic Private Cloud status update / discussion
19:39:52 <nirik> I think we have done nothing really cloud wise this week. ;)
19:39:59 <nirik> see above hosted doom.
19:40:13 <nirik> #topic Upcoming Tasks/Items
19:40:25 <nirik> #info 2013-03-19 to 2013-03-26 - koji update
19:40:25 <nirik> #info 2013-03-29 - spring holiday.
19:40:25 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
19:40:25 <nirik> #info 2013-04-15 - remove legacy-openid
19:40:26 <nirik> #info 2013-04-16 F19 alpha release
19:40:27 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
19:40:28 <nirik> #info 2013-05-21 F19 beta release
19:40:30 <nirik> #info 2013-05-31 end of 1st quarter
19:40:32 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
19:40:33 <nirik> #info 2013-06-25 F19 FINAL release
19:40:36 <nirik> anything anyone wants to schedule or note?
19:41:01 <biker> i wanna say something on the open floor (if there is one) :P
19:41:07 <nirik> yep... coming up. ;)
19:41:12 <nirik> #topic Open Floor
19:41:16 <nirik> go ahead. ;)
19:41:17 <pingou> 2013-06-30 pingou's end of work
19:41:20 <biker> hehe thanks :P
19:41:33 <nirik> pingou: ?
19:41:39 <biker> well ive been a fedora ambassador since last year,., but im also a student,., and i would like to participate on the google summer of code
19:41:55 <biker> and it would be great to help in the fedora infrastructure (:
19:42:01 <pingou> nirik: hopefully at that time I'll have my thesis submitted and I can start actually working
19:42:10 <nirik> pingou: ah ha. Cool.
19:42:17 <nirik> biker: ah. great. ;)
19:42:22 <pingou> biker: cool
19:42:33 <nirik> biker: there was talk on our list not long back about doing some kind of team mentoring...
19:42:34 <pingou> biker: any ideas on what you would like to do ?
19:42:45 <biker> so on the fedora wiki ideas,., there is this one: Implement a unit test framework for fedpkg and rpkg
19:43:21 <biker> that sound great (: but if someone has a better idea in that i could work,., .. (:
19:43:49 <pingou> unfortunately the contact disapeared for this subject apparently
19:44:08 <pingou> yeah, it was Jesse
19:44:17 <pingou> .whoowns fedpkg
19:44:17 <zodbot> pingou: ausil
19:44:42 <biker> damn hehe,., so any other projects or ideas you may have,., i can check them (
19:44:42 <pingou> biker: you should contact ausil for this subject and see with him if he is still interested
19:44:43 <biker> (:
19:44:47 <nirik> yeah, dgilmore doesn't have time to mentor
19:45:06 <biker> pingou, okok thanks (:
19:45:09 <nirik> (at least I am pretty sure)
19:45:16 <nirik> anyhow, you could also ask on the list...
19:45:17 <biker> any other project that could be done? (:
19:45:24 <pingou> biker: what do you like ?
19:45:35 <pingou> I'm sure we can find a bunch of projects :D
19:46:28 <biker> pingou, i know python (and some django), C, QT, java, some php
19:46:59 <nirik> biker: you might ask over in #fedora-apps, (but probibly monday would be best)
19:47:03 <pingou> biker: and you like more web app dev, desktop application dev, CLI, library work ?
19:47:34 <biker> nirik, ,., thanks (: ill try then on monday. is there a meeting or monday or just more people? :P
19:47:46 <nirik> biker: many folks are gone to pycon this week.
19:47:51 <nirik> they should be back next week
19:47:57 <biker> nirik, o okok (:
19:48:06 <biker> pingou, humm well i dont like a lot web app dev :P
19:48:10 <nirik> hopefully we can find something interesting for you. ;)
19:48:12 <biker> but for the others i can try on (:
19:48:18 <biker> nirik, :D
19:48:37 <nirik> ok, anything else for open floor?
19:48:46 <biker> i havent done much coding for opensource, so i dont know if web app, or cli, or library :p
19:49:04 <pingou> fedocal in stg, testers welcome :)
19:49:12 <biker> im studying EE, so i also know a lot of microcontrollers, some hardware and stuff (:
19:49:20 <nirik> pingou: I've not had a chance to look at that redirect issue. ;(
19:49:37 <pingou> nirik: me neither :(
19:49:53 <pingou> nirik: but all the rest seems to work fine
19:49:55 <nirik> biker: we don't do too much direct hardware work. :)
19:50:23 <biker> nirik, yeah i know, but maybe i could try to do a driver or something (: though i still dont know how to make drivers :P
19:50:49 <nirik> biker: most of that work is done upstream in the kernel community... and we just use their hard work.
19:50:59 <biker> oo okok (:
19:51:29 <biker> so yeah,., ill ask next week on #fedora-apps,.,
19:51:39 <nirik> great. :) Thanks for coming biker.
19:51:51 <biker> thanks to all (:
19:51:56 <biker> ill try to be here next meeting (:
19:51:57 <nirik> and welcome again jerzyr
19:52:03 <jerzyr> thx
19:52:07 <nirik> everyone welcome. :)
19:52:19 <nirik> lets continue over in #fedora-admin, #fedora-apps or #fedora-noc. ;)
19:52:23 <nirik> #endmeeting
Thanks to those who were able to join us for the weekly status meeting today. For those that were unable, the minutes are posted below:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-20/fedora-meeting…
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-20/fedora-meeting…
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-20/fedora-meeting…
Paul
===================================================
#fedora-meeting-1: Fedora ARM weekly status meeting
===================================================
Meeting started by pwhalen at 20:00:23 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-20/fedora-meeting…
.
Meeting summary
---------------
* 0) Status of ACTION items from our previous meeting (pwhalen,
20:02:07)
* - COMPLETE - ahs3 to do another package scan this evening for
aarch64 patching, send to the list for review (pwhalen, 20:02:36)
* - INPROGRESS - pbrobinson/dgilmore to provide feedback on aarch64
patches (pwhalen, 20:03:28)
* bug is https://bugzilla.redhat.com/show_bug.cgi?id=922257 Alias is
ARM64 (pbrobinson, 20:09:55)
* 1) Problem Packages (pwhalen, 20:10:19)
* java still outstanding- devs say it will be done by end of week
(bconoboy, 20:11:38)
* py-pillow is fixed (bconoboy, 20:11:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922770
(pbrobinson, 20:12:21)
* LINK: tog-python is broken,
https://bugzilla.redhat.com/show_bug.cgi?id=922770 (bconoboy,
20:12:43)
* Other misc broken packages: (bconoboy, 20:13:01)
* LINK: javasqlite:
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1584679
(bconoboy, 20:13:04)
* LINK: pure:
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1498064
(bconoboy, 20:13:05)
* LINK: OpenImageIO:
http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1606987
(bconoboy, 20:13:05)
* If you know Ruby please ping pbrobinson (bconoboy, 20:14:32)
* ACTION: pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
(bconoboy, 20:15:50)
* 2) Aarch64 patching (pwhalen, 20:16:18)
* 3) Creating test candidate images for F19 (pwhalen, 20:17:43)
* livemedia-creator in f19 is broken meaning we cannot use it to make
f19 images (bconoboy, 20:19:10)
* Using fedora 18's livemedia-creator to make f19 images results in
problems due to the emerging unified kernel (bconoboy, 20:19:46)
* F19 kernel will be unified except for tegra (bconoboy, 20:25:13)
* IDEA: Let's just use a unified kernel for F19 (bconoboy, 20:29:47)
* IDEA: Anything not in unified is treated as a remix (bconoboy,
20:30:00)
* agree on unified only f19 kernel (jonmasters, 20:30:09)
* Unified kernel will minimally support omap, highbank, mvebu,
vexpress (a9), possibly vexpress a15 (bconoboy, 20:35:05)
* AGREED: The spins-kickstarts repo will be used to generate official
f19 images- get your changes in! (bconoboy, 20:41:54)
* 4) Open Floor (pwhalen, 20:44:11)
* 3.8.x has gone out to stable. The vexpress version needs F19's qemu
to boot. Some highbank issues in 3.8. (bconoboy, 20:46:51)
* ACTION: pwhalen and mlangsdorf are working on the highbank issues-
every reason to expect a speedy recovery (bconoboy, 20:47:22)
* ACTION: pbrobinson will update 3.9 kernel config over weekend and
spin out a new test build (bconoboy, 20:52:15)
* AGREED: pbrobinson is a man of action (bconoboy, 20:53:05)
* goal for new 3.9 test build is to resolve usb driver conflicts
between omap and mvebu (bconoboy, 20:53:56)
Meeting ended at 20:55:02 UTC.
Action Items
------------
* pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
* pwhalen and mlangsdorf are working on the highbank issues- every
reason to expect a speedy recovery
* pbrobinson will update 3.9 kernel config over weekend and spin out a
new test build
Action Items, by person
-----------------------
* mlangsdorf
* pwhalen and mlangsdorf are working on the highbank issues- every
reason to expect a speedy recovery
* pbrobinson
* pbrobinson to post a list of leaf packages to arm(a)lists.fp.o
* pbrobinson will update 3.9 kernel config over weekend and spin out a
new test build
* pwhalen
* pwhalen and mlangsdorf are working on the highbank issues- every
reason to expect a speedy recovery
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* bconoboy (91)
* pbrobinson (79)
* pwhalen (30)
* dgilmore (25)
* j_dulaney (24)
* jonmasters (23)
* masta (18)
* zodbot (14)
* dmarlin (13)
* ctyler (6)
* jsmith (5)
* mlangsdorf (4)
* jcapik (4)
* nirik (2)
* ahs3 (2)
* fossjon (1)
===================================
#fedora-meeting: FESCO (2013-03-20)
===================================
Meeting started by nirik at 18:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-20/fesco.2013-03-20…
.
Meeting summary
---------------
* init process (nirik, 18:00:02)
* #1095 Fedora 20 schedule proposal (nirik, 18:01:55)
* LINK: https://fedorahosted.org/fesco/ticket/1095 (nirik, 18:01:55)
* AGREED: approve schedule aiming as 2013-11-12, with explicit dates
listed as 'no earlier then', and start the announcement with "will
be adjusted out based on changes submitted by deadline" (+6, -1, 0)
(nirik, 18:08:50)
* #1094 tomcat6 deprecation (fasttrack) (nirik, 18:09:25)
* LINK: https://fedorahosted.org/fesco/ticket/1094 (nirik, 18:09:26)
* ACTION: nirik to close ticket out. (nirik, 18:10:27)
* #1098 F19 Features - Progress on Feature Freeze (nirik, 18:10:34)
* LINK: https://fedorahosted.org/fesco/ticket/1098 (nirik, 18:10:34)
* AGREED: drop ns-3 and kolab as features for F19. Suggest they
target F20. (+6, 0) (nirik, 18:15:55)
* rawhide inheritance (nirik, 18:16:38)
* LINK: https://fedorahosted.org/fesco/ticket/1005 (nirik, 18:16:46)
* LINK: https://fedorahosted.org/fesco/ticket/1099 (nirik, 18:16:48)
* AGREED: proposal to Postpone inheritance cut-off to Alpha Freeze
rejected (0,-6,0) (nirik, 18:24:06)
* #1102 Release name issues (nirik, 18:24:14)
* LINK: https://fedorahosted.org/fesco/ticket/1102 (nirik, 18:24:15)
* AGREED: leave name as is, fix issues as they arise (+6,0,0) (nirik,
18:31:36)
* next weeks chair (nirik, 18:31:44)
* ACTION: t8m to chair next week (nirik, 18:32:14)
* Open Floor (nirik, 18:32:18)
* LINK:
http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?id=5457175a725720384…
(Viking-Ice, 18:34:12)
Meeting ended at 18:43:25 UTC.
Action Items
------------
* nirik to close ticket out.
* t8m to chair next week
Action Items, by person
-----------------------
* nirik
* nirik to close ticket out.
* t8m
* t8m to chair next week
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (88)
* jreznik (20)
* mitr (19)
* pjones (14)
* notting (14)
* abadger1999 (13)
* Viking-Ice (12)
* zodbot (10)
* jwb (8)
* adamw (4)
* t8m (3)
* drago01 (2)
* mmaslano (0)
* sgallagh (0)
--
18:00:01 <nirik> #startmeeting FESCO (2013-03-20)
18:00:01 <zodbot> Meeting started Wed Mar 20 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:02 <nirik> #meetingname fesco
18:00:02 <nirik> #chair abadger1999 jwb mitr mmaslano notting nirik pjones t8m sgallagh
18:00:02 <nirik> #topic init process
18:00:02 <zodbot> The meeting name has been set to 'fesco'
18:00:02 <zodbot> Current chairs: abadger1999 jwb mitr mmaslano nirik notting pjones sgallagh t8m
18:00:09 <mitr> Hello all
18:00:20 * abadger1999 can pay attention every so often
18:00:27 <pjones> hello.
18:00:30 * notting is here
18:00:36 <jwb> hi
18:00:53 * jreznik lurks
18:01:22 <nirik> I think sgallagh and mmaslano are both out today.
18:01:47 <jreznik> nirik: yep, marcela is still out
18:01:47 <nirik> so, I guess lets go ahead and get started.
18:01:55 <nirik> #topic #1095 Fedora 20 schedule proposal
18:01:55 <nirik> .fesco 1095
18:01:55 <nirik> https://fedorahosted.org/fesco/ticket/1095
18:02:03 <zodbot> nirik: #1095 (Fedora 20 schedule proposal) – FESCo - https://fedorahosted.org/fesco/ticket/1095
18:02:31 <nirik> so, did we come up with any brilliant plans on this since last meeting?
18:02:43 * jreznik thinks we are still stuck with not accepted proposal
18:03:08 <nirik> well, the issue is: do we make a schedule (even tenative) without knowing what will be in it.
18:03:10 <notting> nirik: only the ones to move our new unicode world from the release name to the release number.
18:03:41 * nirik proposes a feature for Fedora e^(i*pi)
18:04:11 <jreznik> nirik: chicken - egg - without saying how much time we will give to the teams...
18:04:25 <notting> nirik: nah. our release processes are already irrational, the number should be too
18:04:27 <mitr> nirik: Marcela is +1 in the ticket for a proposal that got +4 the last time...
18:04:34 * nirik looks
18:04:56 <nirik> mitr: that is a new proposal...
18:05:12 <jreznik> nirik: that's actually more "details provided" for the previous one
18:05:31 <nirik> oh I see...
18:05:32 <abadger1999> I'm worried that we'll slip into the holidays again with this schedule but I don't have a better idea if we want to do a regular full Fedora release.
18:05:38 <abadger1999> You can count me as a +1
18:05:40 <pjones> nirik: or maybe e^(i*pi)+1?
18:05:59 <nirik> pjones: I'd love to see what breaks with a fedora-0 ;)
18:06:28 <nirik> so, then I guess we pass that schedule... sorry pjones. You can tell us 'I told you so' now.
18:06:41 <pjones> abadger1999: the issue isn't so much worries about the dates themselves as worrying that by agreeing to them all now we're committing the same mistakes as we did for F18.
18:07:00 <nirik> so, that would be:
18:07:06 <nirik> approve schedule aiming as 2013-11-12, with explicit dates listed as 'no earlier then', and start the announcement with "will be adjusted out based on changes submitted by deadline"
18:07:11 <jreznik> or ubuntu-20
18:07:43 <jreznik> nirik: yep, I think it's a compromise similar to what we did with f19, just a little bit more clear
18:07:49 <nirik> assuming no one else wishes to change their votes? speak now.
18:08:03 <abadger1999> pjones: Well... yeah, I don't have an answer for that problem either.
18:08:36 <abadger1999> :-(
18:08:42 <notting> nirik: i can be +1 to that
18:08:50 <nirik> #agreed approve schedule aiming as 2013-11-12, with explicit dates listed as 'no earlier then', and start the announcement with "will be adjusted out based on changes submitted by deadline" (+6, -1, 0)
18:09:06 <nirik> anything else on this? or moving on...
18:09:25 <nirik> #topic #1094 tomcat6 deprecation (fasttrack)
18:09:26 <nirik> .fesco 1094
18:09:26 <nirik> https://fedorahosted.org/fesco/ticket/1094
18:09:29 <zodbot> nirik: #1094 (tomcat6 deprecation (fasttrack)) – FESCo - https://fedorahosted.org/fesco/ticket/1094
18:09:36 <nirik> the submitter said this can be closed now.
18:09:46 <nirik> I will just do that unless anyone has any further issues here...
18:09:53 <abadger1999> mitr: btw, I think Marcela voted the last time (in ticket)
18:10:05 <notting> hooray for things that sort themselves out
18:10:16 <nirik> yeah, always nice.
18:10:18 <abadger1999> yay
18:10:23 <mitr> abadger1999: yes, but we changed the proposal
18:10:27 <nirik> #action nirik to close ticket out.
18:10:34 <nirik> #topic #1098 F19 Features - Progress on Feature Freeze
18:10:34 <nirik> .fesco 1098
18:10:34 <nirik> https://fedorahosted.org/fesco/ticket/1098
18:10:36 <zodbot> nirik: #1098 (F19 Features - Progress on Feature Freeze) – FESCo - https://fedorahosted.org/fesco/ticket/1098
18:11:35 <nirik> so where are we here?
18:11:57 <jwb> we're at the point where we drop stuff
18:12:14 * nirik nods
18:12:30 <jwb> which is basically kolab and ns-3 at this point?
18:12:57 <jreznik> the list of postponed features is quite big
18:13:09 <nirik> jwb: looks like.
18:13:16 <jreznik> jwb: I have not received any update for ns-3 at all
18:13:18 <jwb> jreznik, they already moved them themselves. that's good.
18:13:40 <jwb> proposal: drop ns-3 and kolab as features for F19. Suggest they target F20.
18:13:40 <jreznik> jwb: well, I convinced them to do so :) to make it easier for fesco :)
18:13:45 <jwb> excellent
18:13:56 <nirik> jwb: +1
18:14:02 <jreznik> cwickert promised updates but... so I'm +1
18:14:06 <notting> jwb: +1
18:14:24 <notting> they're both leafy features, so if they come back tomorrow we *can* reconsider, but yeah - defer to f20
18:14:24 <mitr> +1. (We can perhaps reconsider later if they do make F19 and are expected to be sufficiently tested.)
18:14:43 <nirik> right, they can come back for an exception.
18:15:07 <nirik> other votes?
18:15:08 <abadger1999> +1
18:15:18 <jreznik> there are more leaf features that could get exception later, for now it was easier and safer to postpone
18:15:41 * pjones reads
18:15:47 <pjones> jwb: +1
18:15:55 <nirik> #agreed drop ns-3 and kolab as features for F19. Suggest they target F20. (+6, 0)
18:16:36 <nirik> So, we had enough votes on this to decide in ticket, but I thought I would have a topic in case others wished to vote or had additional comments:
18:16:38 <nirik> #topic rawhide inheritance
18:16:46 <nirik> #1005 At f19 branching time, drop inheritance in rawhide
18:16:46 <nirik> https://fedorahosted.org/fesco/ticket/1005
18:16:47 <nirik> .fesco 1005
18:16:47 <nirik> and
18:16:47 <nirik> #1099 Postpone inheritance cut-off to Alpha Freeze
18:16:48 <nirik> https://fedorahosted.org/fesco/ticket/1099
18:16:50 <nirik> .fesco 1099
18:16:50 <zodbot> nirik: #1005 (At f19 branching time, drop inheritance in rawhide) – FESCo - https://fedorahosted.org/fesco/ticket/1005
18:16:53 <zodbot> nirik: #1099 (Postpone inheritance cut-off to Alpha Freeze) – FESCo - https://fedorahosted.org/fesco/ticket/1099
18:17:13 <nirik> so, any additional thoughts or comments? or are we all set here?
18:18:31 * nirik listens to the crickets chirp. ;)
18:18:36 <notting> i like the idea of later inheritance breaks because i'm lazy.
18:18:47 <jwb> i don't care either way
18:18:49 <notting> but i don't care enough that we should drastically change policy for it.
18:19:21 <nirik> I understand lazy... but I think this way is also nicer... I mean f19 and rawhide aren't really the same after branch...
18:19:51 <nirik> perhaps we revisit next cycle and see if we can do anything better.
18:19:53 <jreznik> nirik: +1 and I actually never used inheritance
18:20:04 <mitr> If anybody wanted to save work, a script that kicks of both builds and even reports a diff of the build.logs (potentially ignoring "f19"/"f20" differences) should be easy enough to write.
18:20:21 <nirik> mitr: yeah.
18:20:29 <nirik> ok, moving along then...
18:20:35 <mitr> Conceptually I strongly prefer having the build system and branches consistent
18:20:43 * nirik does too
18:20:58 <pjones> mitr: likewise
18:21:05 <mitr> Do we want a pro forma vote, or is that -4 in the ticket considered sufficient?
18:21:38 <nirik> mitr: theres -5 in ticket 1099...
18:21:52 <notting> I can be -1 too
18:22:18 <mitr> nirik: comment#4 if vondruch quoting abadger1999
18:22:37 <pjones> you meant "is", right?
18:22:40 <nirik> oh indeed.
18:22:47 <mitr> pjones: yes, sorry
18:22:52 <pjones> still, looks like we're at -6 now?
18:23:01 <nirik> so, with nottings -1 we are at -5...
18:23:09 * pjones was counting himself
18:23:15 <nirik> sorry, yeah, -6
18:24:06 <nirik> #agreed proposal to Postpone inheritance cut-off to Alpha Freeze rejected (0,-6,0)
18:24:14 <nirik> #topic #1102 Release name issues
18:24:14 <nirik> .fesco 1102
18:24:15 <nirik> https://fedorahosted.org/fesco/ticket/1102
18:24:19 <zodbot> nirik: #1102 (Release name issues) – FESCo - https://fedorahosted.org/fesco/ticket/1102
18:25:02 <mitr> Do we have a reason to believe there will be many bugs?
18:25:17 <jwb> i think pjones fixed 3 yesterday
18:25:33 <pjones> jwb: which means we have reason to believe we won't have those 3.
18:25:40 <jreznik> abrt guys fixed abrt one
18:26:02 <pjones> still, the real question is: how many alpha blocker bugs will we have?
18:26:14 <nirik> indeed.
18:26:14 <jreznik> but it caused for example issue with pillow due to python unicode handling
18:26:23 <pjones> and I think it's starting to look like there was a quick rush of them, but they've mostly subsided.
18:26:36 <mitr> I don't see this as a reason to panic... yet
18:26:53 <pjones> yeah, I think it was just a scary change that caused some dramatic breakage up front, but wasn't actually too bad
18:26:58 <nirik> I don't think we will really know until we get further testing things.
18:27:06 <mitr> Perhaps we could stay with the current name for Alpha, and decide to revert at the change freeze time if it would look like it would affect the schedule?
18:27:20 <notting> the spec defines that os-release is in unicode, correct?
18:27:20 <abadger1999> jreznik: only sorta true -- it caused python3 to ftbfs
18:27:20 <nirik> mitr: yeah, that was my thought.
18:27:28 <nirik> notting: yep.
18:27:36 <nirik> well, if by 'spec' you man 'man os-release'
18:27:39 <mitr> 2 weeks should also be enough time to fix a few issues
18:27:43 <adamw> right now the state of pre-alpha images is that we don't have a non-live image which can complete an install, and basically only I have a live image which installs
18:27:44 <abadger1999> jreznik: and pillow needed python3 rebuilt to fix a different bug
18:27:50 <jreznik> abadger1999: ok
18:27:55 <adamw> and I have not tested that any further than 'it reaches the desktop' really
18:27:58 <adamw> so it's a hard question to answer.
18:28:19 <adamw> fixing the single quote _ought_ to reduce the possible number and severity of issues, though, so thanks pjones.
18:28:42 <abadger1999> notting: yep -- os-release is supposed to be utf-8. But os-release is also a different format (key-value vs a single string)
18:29:03 <jreznik> adamw: yep, I think the quote one is really the top one...
18:29:39 <jreznik> abadger1999: but makes sense to have same rule for os-release and fedora-release at least for encoding
18:29:46 <abadger1999> jreznik: +1
18:30:11 <nirik> hey t8m
18:30:29 <nirik> so, really I think we should keep trying to fix things and if it seems like thats causing massive pain, revisit.
18:30:32 <notting> proposal: leave name as is, fix issues as they arise
18:30:37 <pjones> notting: +1
18:30:40 <t8m> heya
18:30:48 <nirik> +1
18:30:52 <mitr> notting: +1
18:30:55 <notting> (as-is == with currently-in-tree apostrophe change, just for reference)
18:31:02 <abadger1999> +1
18:31:06 <t8m> +1 if it does not cause slippage
18:31:34 * notting is +1 (obviously)
18:31:36 <nirik> #agreed leave name as is, fix issues as they arise (+6,0,0)
18:31:44 <nirik> #topic next weeks chair
18:31:47 <nirik> who wants the fun?
18:31:54 <t8m> nirik, I can do
18:32:08 <nirik> cool. thanks.
18:32:14 <nirik> #action t8m to chair next week
18:32:18 <nirik> #topic Open Floor
18:32:21 <nirik> anything for open floor?
18:33:32 <Viking-Ice> what's the default logger now that journal persistancy has been enabled by default ?
18:33:38 <jreznik> nirik: just one thing related to schedule - I'd like to have a draft of "changes" template and process ready soon - to announce it together, hope for next meeting for you
18:34:12 <Viking-Ice> http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?id=5457175a725720384…
18:34:32 <nirik> Viking-Ice: rsyslog is still enabled and default, if someone wants to propose a f20 feature to change that, feel free.
18:34:39 <nirik> jreznik: cool.
18:35:08 <Viking-Ice> nirik, I just want to fix things before rsyslog gets disable I wanted to start doing that a year ago hence my packaging proposal
18:35:16 <Viking-Ice> at that time
18:35:30 <Viking-Ice> trying to work ahead of the inevitable
18:35:35 <jreznik> nirik: sorry for delays, I'm trying to sync with docs, not many luck with marketing, I'll push harder
18:36:22 <nirik> no worries.
18:37:09 <nirik> ok, anything else?
18:37:41 <drago01> Viking-Ice: flip it in rawhide?
18:37:59 <drago01> Viking-Ice: enough time to work things out ... we already branched
18:38:12 * nirik would like to see a feature proposal with the changes and scope and such...
18:38:12 <Viking-Ice> drago01, need the fpc proposal approved it's on ice since journal is not the "default"
18:38:37 <Viking-Ice> in fact it makes no sense enable journal persistancy ( from my pov ) until it is
18:38:42 <nirik> and confirm all the issues folks noted last time it was proposed are handled in some way
18:39:18 <mitr> Viking-Ice: You can (rpm -e rsyslog) in F18 already and test that if you are interested
18:39:56 <Viking-Ice> mitr, I just want to start fixing packaging log files in the distribution
18:39:57 <mitr> (don't take that as a +1 to the change from me :) )
18:40:13 <Viking-Ice> after all the affected components are around 600
18:40:18 <Viking-Ice> it takes time ;)
18:40:18 <mitr> Viking-Ice: I have no idea what that means, sorry
18:40:50 <Viking-Ice> mitr, as so many things packages are not depending on rsyslog
18:41:34 <mitr> Viking-Ice: All of 2 packages on F18
18:41:47 <nirik> anyhow, can we continue this out of meeting?
18:41:48 <Viking-Ice> mitr, there should be around 600 ;)
18:42:02 <mitr> nirik: yes. sorry
18:42:18 <nirik> if nothing else, will close in a minute then.
18:43:23 <nirik> thanks everyone.
18:43:25 <nirik> #endmeeting
=================================================
#fedora-blocker-review: f19alpha-blocker-review-2
=================================================
Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-…
Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-…
Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-20/f19alpha-…
Meeting summary
---------------
* Roll Call (tflink, 16:00:13)
* Introduction (tflink, 16:06:52)
* LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(tflink, 16:07:47)
* LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink,
16:08:18)
* LINK:
https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria
(tflink, 16:08:36)
* 11 Proposed Blockers (tflink, 16:08:59)
* 1 Accepted Blockers (tflink, 16:08:59)
* 2 Proposed Freeze Exceptions (tflink, 16:08:59)
* 1 Accepted Freeze Exceptions (tflink, 16:08:59)
* (922988) virtio modules (and possibly others?) missing from installed
system's initramfs after a Fedora 19 live (pre-Alpha TC1) install
(tflink, 16:10:34)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922988 (tflink,
16:10:37)
* Proposed Blocker, anaconda, NEW (tflink, 16:10:40)
* AGREED: 922988 - We're not 100% clear on the impact of this bug.
Once we have more data on its impact, we can make a decision WRT its
impact (tflink, 16:22:33)
* (923459) F19 pre-Alpha TC1 network installs stop at "Starting package
installation process" (anaconda is stuck in a loop between writev and
recvfrom) (tflink, 16:23:56)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923459 (tflink,
16:23:59)
* Proposed Blocker, anaconda, NEW (tflink, 16:24:02)
* AGREED: 923459 - AcceptedBlocker - Violates the following F19 alpha
release criteria for network sources "When using the dedicated
installer images, the installer must be able to use either HTTP or
FTP repositories (or both) as package sources." (tflink, 16:27:42)
* (922991) dracut hook pre-pivot runs before mount hook (tflink,
16:27:54)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922991 (tflink,
16:27:54)
* Proposed Blocker, dracut, MODIFIED (tflink, 16:27:54)
* AGREED: 922991 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "The installer must be able to download and use
an installer update image from an HTTP server." (tflink, 16:31:41)
* (921896) Single quote in f19 release name breaks grub2, probably other
stuff (tflink, 16:32:04)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=921896 (tflink,
16:32:07)
* Proposed Blocker, fedora-release, NEW (tflink, 16:32:09)
* AGREED: 921896 - AcceptedBlocker - Violates the following F19 alpha
release criteria as soon as the kernel is updated post-install
"After firstboot is completed and on subsequent boots, a graphical
install must boot to a log in screen where it is possible to log in
to a working desktop as the user created during firstboot."
(tflink, 16:38:42)
* (919374) /var/run not created with var_run_t leading to many boot
avc's (tflink, 16:39:19)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919374 (tflink,
16:39:22)
* Proposed Blocker, filesystem, ASSIGNED (tflink, 16:39:25)
* AGREED: 919374 - While this sounds like it could be a blocker, we
want to wait until it has been reproduced by at least one other
person before accepting it as a blocker for F19 alpha (tflink,
16:45:50)
* (923501) gnome-initial-setup is not visible on first boot after
install (tflink, 16:46:18)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=923501 (tflink,
16:46:21)
* Proposed Blocker, gdm, NEW (tflink, 16:46:23)
* the criteria need to be updated to cover both firstboot and
gnome-initial-experience (tflink, 16:53:08)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922951 covers the
other fail. (adamw, 16:53:55)
* AGREED: 923501 - AcceptedBlocker - Violates the following F19 alpha
release criterion (substituting gnome-initial-experience for
firstboot) A system installed with a graphical package set must boot
to the 'firstboot' utility on the first boot after installation.
(tflink, 16:56:51)
* (922951) gnome-initial-setup is enabled by default (and presently
crashes) (tflink, 16:57:23)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922951 (tflink,
16:57:26)
* Proposed Blocker, gnome-initial-setup, NEW (tflink, 16:57:28)
* AGREED: 922951 - While this seems as it it would be a blocker, we
suspect that it has been fixed. If it isn't fixed already, will
revisit at the next meeting (tflink, 17:03:55)
* (922885) make sure gnome-initial-setup.service doesn't start on LiveCD
(tflink, 17:04:14)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922885 (tflink,
17:04:17)
* Proposed Blocker, gnome-initial-setup, POST (tflink, 17:04:19)
* LINK: https://git.gnome.org/browse/gnome-initial-setup/log/
(adamw, 17:06:15)
* this has already been fixed, verified and will be closed (tflink,
17:07:46)
* (922955) GNOME Shell fails to start if gnome-screensaver is not
installed (it is not in our default groups) (tflink, 17:10:17)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922955 (tflink,
17:10:20)
* Proposed Blocker, gnome-shell, NEW (tflink, 17:10:22)
* this bug has been fixed and will be closed shortly (tflink,
17:16:50)
* (917246) gdm-simple-slave crashes on login attempt (tflink, 17:17:05)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=917246 (tflink,
17:17:06)
* Proposed Blocker, gnome-shell, NEW (tflink, 17:17:06)
* AGREED: 917246 - AcceptedBlocker - Violates the following F19 alpha
release criterion: "After firstboot is completed and on subsequent
boots, a graphical install must boot to a log in screen where it is
possible to log in to a working desktop as the user created during
firstboot." (tflink, 17:30:27)
* (921914) Lorax should disable dracut's 'hostonly' mode when generating
images (tflink, 17:30:46)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=921914 (tflink,
17:30:49)
* Proposed Blocker, lorax, NEW (tflink, 17:30:52)
* 921914 has been fixed and can be closed (tflink, 17:36:40)
* (922335) enter not accepted in unlock screen anymore (tflink,
17:37:32)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=922335 (tflink,
17:37:32)
* Proposed Freeze Exceptions, gnome-shell, NEW (tflink, 17:37:32)
* note that this has already been closed (tflink, 17:40:13)
* (919935) enblend FTBFS due to doc/texinfo related issues (tflink,
17:43:08)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919935 (tflink,
17:43:08)
* Accepted Blocker, enblend, NEW (tflink, 17:43:08)
* this is still being worked out, leaving out kipi-plugins from the
TC1 build is an option (tflink, 17:46:56)
* Open Floor (tflink, 17:50:47)
* the next version of the blocker tracking app will be hitting fedora
infra staging soon (hopefully this friday) (tflink, 17:51:25)
Meeting ended at 18:02:38 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tflink (165)
* adamw (145)
* kparal (60)
* jreznik (36)
* pjones (7)
* zodbot (5)
* satellit_e (2)
* nirik (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
======================
#fedora-meeting: FAmNA
======================
Meeting started by masta at 01:00:17 UTC. The full logs are available
athttp://meetbot.fedoraproject.org/fedora-meeting/2013-03-20/famna.2013-03-…
.
Meeting summary
---------------
* === FAmNA Roll Call === (masta, 01:00:17)
* === Announcements === (masta, 01:03:49)
* === Tickets === (masta, 01:04:46)
* LINK: https://fedorahosted.org/famna/report/9 (masta, 01:04:47)
* Northeast LinuxFest 2013, March 16 - 17, Harvard (dan408, 01:13:12)
* LINK: https://fedorahosted.org/famna/ticket/49 (dan408, 01:15:45)
* ticket #48 & #49 to be closed as soon as they have event reports
(masta, 01:19:15)
* ACTION: rbergeron to update ticket (dan408, 01:22:13)
* == Who will be the next FAmNA meeting chair? == (masta, 01:23:49)
* == Open Floor === (masta, 01:28:22)
* ACTION: dan408 to have a time and date to vote on for a new official
meeting time if not the same one (dan408, 01:51:27)
Meeting ended at 02:00:08 UTC.
Action Items
------------
* rbergeron to update ticket
* dan408 to have a time and date to vote on for a new official meeting
time if not the same one
Action Items, by person
-----------------------
* dan408
* dan408 to have a time and date to vote on for a new official meeting
time if not the same one
* rbergeron
* rbergeron to update ticket
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dan408 (157)
* chanchito (55)
* masta (46)
* award3535 (38)
* inode0 (22)
* rbergeron (18)
* davdunc (10)
* zodbot (9)
* dramsey (3)
* nb (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi all,
The IRC meeting minutes tonight are available at here [1]. Thanks
everyone for attending the meeting.
In the meeting we mainly talked about offline gather up in Beijing in
March, translation task, FUDCON 2014 bid. The next IRC meeting will be
held on next Friday (2013-03-22). Please come and join the discussion if
you can!
[1]
http://meetbot.fedoraproject.org/fedora-zh/2013-03-15/fedora-zh.2013-03-15-…
=============================================
#fedora-zh: Fedora Chinese Meeting 2013-03-15
=============================================
Meeting started by alick at 12:01:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-zh/2013-03-15/fedora-zh.2013-03-15-…
.
Meeting summary
---------------
* 点名 (alick, 12:01:48)
* 翻译 (alick, 12:16:31)
* LINK: https://fedoraproject.org/wiki/L10N/Guide/zh-cn (alick,
12:16:47)
* LINK:
http://fedorapeople.org/groups/schedule/f-19/f-19-trans-tasks.html
(alick, 12:21:06)
* 目前主要任务还是翻译文档和维基页 (alick, 12:23:46)
* ACTION: endle will check the l10n progress of UEFI Guide (alick,
12:34:11)
* 三月线下活动(BJGUG 社区联合活动) (alick, 12:36:20)
* LINK:
https://mail.gnome.org/archives/gnome-cn-list/2013-March/msg00020.html
(alick, 12:38:22)
* 北京GNOME用户组三月活动之开源社区大联盟 (alick, 12:40:45)
* 时间: 2013.3.23 13:00-17:00 (alick, 12:40:57)
* 地点:朝阳区北苑路13号院1号楼领地OFFICE C座603室 (alick, 12:41:37)
* FUDCON APAC 2014 申办 (alick, 12:51:45)
* IDEA: contact kaio, gbraad, and RH Beijing about FUDCON bid (alick,
13:00:53)
Meeting ended at 13:03:11 UTC.
Action Items
------------
* endle will check the l10n progress of UEFI Guide
Action Items, by person
-----------------------
* endle
* endle will check the l10n progress of UEFI Guide
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* alick (101)
* liangsuilong (39)
* zsun (22)
* BinLi_i (17)
* zodbot (14)
* endle (13)
* gfrog (10)
* diseng (7)
* microcai (6)
* BinLi (5)
* BadGirl (4)
* qzhou (1)
* AndChat|366225 (1)
* CyrusYzGTt (0)
* gbraad (0)
* kingheaven (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Alick
Fedora 18 (Spherical Cow) user
https://fedoraproject.org/wiki/User:Alick
============================================
#fedora-meeting: Infrastructure (2013-03-14)
============================================
Meeting started by nirik at 19:00:01 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-14/infrastructure.2…
.
Meeting summary
---------------
* welcome y'all (nirik, 19:00:02)
* New folks introductions and Apprentice tasks (nirik, 19:04:49)
* Applications status / discussion (nirik, 19:10:06)
* fedocal is moving to staging. (nirik, 19:10:24)
* blockerbugs qa app is moving to staging. (nirik, 19:10:33)
* currently we have a temporary openid provider setup for the old uri,
will disappear soon (puiterwijk, 19:12:12)
* relrod making a dev gitlab instance to look at. (nirik, 19:16:49)
* Sysadmin status / discussion (nirik, 19:20:10)
* LINK: https://github.com/mpdehaan/ansible-commander (nirik,
19:23:49)
* Private Cloud status update / discussion (nirik, 19:27:12)
* Upcoming Tasks/Items (nirik, 19:32:55)
* 2013-03-12 to 2013-03-21 pycon (nirik, 19:33:12)
* 2013-03-19 to 2013-03-26 - koji update (nirik, 19:33:12)
* 2013-03-29 - spring holiday. (nirik, 19:33:12)
* 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik,
19:33:12)
* 2013-04-15 - remove legacy-openid (nirik, 19:33:12)
* 2013-04-16 F19 alpha release (nirik, 19:33:13)
* 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik,
19:33:15)
* 2013-05-21 F19 beta release (nirik, 19:33:16)
* 2013-05-31 end of 1st quarter (nirik, 19:33:18)
* 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik,
19:33:20)
* 2013-06-25 F19 FINAL release (nirik, 19:33:22)
* Open Floor (nirik, 19:34:16)
* help needed for coprs (nirik, 19:34:42)
* coprs helpers see pingou or skvidal in #fedora-apps to help out.
(nirik, 19:35:16)
Meeting ended at 19:41:46 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (76)
* skvidal (62)
* pingou (20)
* puiterwijk (12)
* swa_work (11)
* linuxmania (10)
* relrod (6)
* zodbot (4)
* axil42 (4)
* jerrycan321 (2)
* smooge (1)
* SmootherFrOgZ (1)
* abadger1999 (0)
* lmacken (0)
* threebean (0)
* ricky (0)
* mdomsch (0)
* dgilmore (0)
* CodeBlock (0)
--
19:00:01 <nirik> #startmeeting Infrastructure (2013-03-14)
19:00:01 <zodbot> Meeting started Thu Mar 14 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:02 <nirik> #meetingname 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> The meeting name has been set to 'infrastructure'
19:00:02 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean
19:00:40 * skvidal is here
19:00:42 <relrod> here
19:00:48 * puiterwijk is finally around again
19:01:14 * pingou here
19:02:02 * nirik waits a minute for people to come in.
19:02:23 <swa_work> hi all
19:03:29 <linuxmania> that we say "here" means we are here to attend the meeting?
19:03:35 <linuxmania> hi everybody
19:03:37 <nirik> you can. ;)
19:04:01 * swa_work here
19:04:49 <nirik> #topic New folks introductions and Apprentice tasks
19:05:05 <nirik> any new folks want to say hi and introduce themselves? or anyone have questions or comments?
19:05:12 * SmootherFrOgZ is around
19:05:40 <linuxmania> yes, i am a newbie. I would like to introduce myself to everyone.
19:06:06 <jerrycan321> Hi - I'm new here, and just here to see what happens and where I can help.
19:06:22 <nirik> welcome linuxmania and jerrycan321. Are you more interested in sysadmin type tasks or application development ?
19:07:06 <linuxmania> could you please describe those two in more details?
19:07:27 <smooge> is here but distracted
19:07:49 <nirik> sysadmin's do scripting and managing running hosts, app development is working on the applications we run... pkgdb, etc...
19:08:03 <nirik> it's perfectly fine to be interested in both. ;)
19:08:15 <jerrycan321> Either are of interest, but I have not been a programmer for quite a while. I guess sysadmin, then I can get to see where things might need fixing, and go from there.
19:08:29 <linuxmania> got it. I think i like app development more.
19:08:58 <nirik> cool.
19:09:18 <nirik> see me in #fedora-meeting or the apps folks in #fedora-apps after the meeting and we can point you in the right direction.
19:09:27 <nirik> note that many of our apps folks are at pycon right now...
19:09:36 <puiterwijk> nirik: I think you meant #fedora-admin? ;)
19:09:45 <nirik> sorry, yes.
19:10:06 <nirik> #topic Applications status / discussion
19:10:17 <nirik> ok, probibly not too much here this week, but a few things...
19:10:24 <nirik> #info fedocal is moving to staging.
19:10:33 <nirik> #info blockerbugs qa app is moving to staging.
19:10:35 <pingou> I got some work done this week(-end), fedocal, pkgdb2, taggerapi
19:10:46 <swa_work> I'd like to introduce myself; my name is Steven Acres, I've been a Solaris/Linux sysadmin for 10 yrs and was actively involved with the OpenSolaris project as well
19:11:14 <linuxmania> ok, no problem. I will see you at #fedora-admin, nirik.
19:11:20 <pingou> btw skvidal there is a question where your input would be nice on copr-devel about the interest of having a hash for the api login (in addition to the api token)
19:11:39 <skvidal> pingou: I'll take a look - I didn't see it before
19:11:44 <pingou> skvidal: thanks
19:11:46 <nirik> swa_work: welcome!
19:11:54 <swa_work> thanks nirik !
19:12:11 <nirik> swa_work: you also interested in the sysadmin side of things? or apps too?
19:12:12 <puiterwijk> #info currently we have a temporary openid provider setup for the old uri, will disappear soon
19:12:19 <pingou> together with threebean and hughsie, we've been working on taggerapi: http://209.132.184.171/
19:12:46 <pingou> eventually, the current tagger will come on the top of this api
19:13:14 <swa_work> nirik, more sysadmin ; I can roll rpms, etc. when needed
19:13:20 <pingou> and this api supports rating in addition to tagging
19:14:17 <swa_work> although I've not worked with koji or buildsystems as such
19:14:40 <swa_work> well ..the opensuse abit when I was with Novell/Platespin
19:14:40 <nirik> cool.
19:15:01 <nirik> swa_work: we just mostly keep koji running along... not much internal development on it. ;)
19:15:08 <nirik> any other application news?
19:15:25 <relrod> I'm working on ansible gitlab playbooks for skvidal :P
19:15:26 <axil42> greetings:)
19:15:35 <skvidal> s/skvidal/fedora/
19:15:53 <puiterwijk> one request for anyone
19:15:54 <relrod> well, s/for/as asked by/
19:15:56 <relrod> ;)
19:15:57 <nirik> yeah, will be nice to prevew it.
19:16:06 <puiterwijk> in case there are any problems with FAS-OpenID, please redirect those to me ;)
19:16:18 <relrod> skvidal: sorry, wasn't trying to pin it on you or anything
19:16:25 <skvidal> relrod: :)
19:16:28 <skvidal> relrod: not upset
19:16:33 <nirik> puiterwijk: I've not see any issues since we setup the legacy provider. ;)
19:16:35 <skvidal> relrod: I was being flippant :)
19:16:44 <skvidal> relrod: no worries
19:16:46 <puiterwijk> nirik: I did, today a question on askbot ;)
19:16:49 <nirik> #info relrod making a dev gitlab instance to look at.
19:16:57 <nirik> puiterwijk: oh? where at?
19:17:01 <swa_work> apologies for not introducing myself first the infra list; my work has been hectic lately
19:17:07 <puiterwijk> nirik: https://ask.fedoraproject.org/question/23922/i-cant-logging-using-fedora-ac…
19:17:20 <nirik> swa_work: no problem, we all very much understand that. ;)
19:17:37 <swa_work> cool, thanks
19:17:38 <nirik> puiterwijk: ah yeah, that was an old one and I modified my answer, it had the incorrect link in it.
19:17:53 <nirik> or wait, thats a different one
19:17:53 <puiterwijk> nirik: your answer?
19:18:08 <puiterwijk> yeah, I asked them to contact me
19:18:23 <axil42> swa_work: you are Harish?
19:19:54 <nirik> puiterwijk: there was another question about how to login with openid... and I had the old url in my answer, someone mentioned it to me and I edited it.
19:20:02 <nirik> anyhow, shall we move on...
19:20:04 <puiterwijk> nirik: ah, ok
19:20:07 <puiterwijk> sure
19:20:10 <nirik> #topic Sysadmin status / discussion
19:20:13 <swa_work> no axil42 ; Steven Acres http://blog.swatteksystems.com ; swa on fas
19:20:23 <nirik> lets see...
19:20:44 <axil42> oh sorry, thought you were the guy who sent to the list about gsoc and gitlab
19:21:02 <swa_work> np, I knew who you meant ;D
19:21:20 <nirik> not too much sysadmin news I can recall. ;) We are poking at ansible some more to get it up to speed
19:21:21 <axil42> Basically I'm here for this reason :)
19:21:37 <skvidal> nirik: speaking of that
19:21:43 <nirik> There were some important updates to puppet and such, which got applied.
19:21:59 <skvidal> I had lunch with mdehaan today. we spoke about ansible commander some - which should be seeing an alpha release very soon
19:22:13 <nirik> excellent. Thats the web management? or ?
19:23:49 <nirik> https://github.com/mpdehaan/ansible-commander
19:24:21 <skvidal> nirik: it's more than web
19:24:24 <skvidal> it is a web interface
19:24:26 <skvidal> which is _fine_
19:24:30 <skvidal> but the idea is this
19:24:43 <skvidal> web interface commits to a git repo from the interface for playbook editing, etc
19:24:51 <skvidal> but also is a scheduler for playbook executions
19:25:10 <skvidal> so you can say 'run these playbooks every N hours, in parallel'
19:25:21 <nirik> nice.
19:25:27 <skvidal> so the web app
19:25:36 <skvidal> will have(does?) have a rest api
19:25:45 <nirik> excellent.
19:25:46 <skvidal> so telling it to do things from a cli should be possible
19:25:51 * pingou likes
19:26:37 <nirik> nice. Look forward to it.
19:26:59 <skvidal> me too
19:27:12 <nirik> #topic Private Cloud status update / discussion
19:27:12 <skvidal> the licensing on it is opensource - not sure which one yet
19:27:19 <skvidal> but I was assured nothing offensive :)
19:27:20 <nirik> excellent.
19:27:25 <nirik> skvidal: oh, how does it do auth?
19:27:27 <nirik> or does it?
19:27:34 <skvidal> nirik: I have no idea :) - probably apache does it?
19:27:38 <skvidal> I know the app base is django?
19:27:39 <skvidal> so..
19:27:42 <pingou> :'(
19:27:47 <skvidal> pingou: why is that sad?
19:27:49 <pingou> sorry :)
19:28:04 <relrod> according to the readme, it's gplv3, fwiw
19:28:50 <skvidal> relrod: that may or may not be the most current
19:28:54 <skvidal> but it probably is
19:29:04 <skvidal> I didn't ask which github branch was the right one
19:29:08 <nirik> ok, any cloud news this week? I think we are pretty much migrated to the openstack cloudlet aside from a few stragglers.
19:29:23 <skvidal> nirik: stragglers are left
19:29:34 <skvidal> nirik: the jenkins issue with the external ips
19:29:48 <skvidal> is still outstanding - beagles - in openstack team inside is looking at it - no resolution yet
19:30:02 <skvidal> we can step around it using the internal ips for sshing into the hosts
19:30:05 <skvidal> which works just fine
19:30:05 <pingou> skvidal: btw, why is only the el6 node concerned? different cloudlet b/w el and fedora builder?
19:30:14 <skvidal> pingou: we have 4 compute nodes
19:30:21 <skvidal> if 2 instances
19:30:23 <skvidal> are on the same node
19:30:31 <skvidal> then they cannot talk to one another using their EXTERNAL ip
19:30:36 <skvidal> they CAN using their INTERNAL ip
19:30:38 <skvidal> so
19:30:41 <skvidal> jenkins-master
19:30:45 <skvidal> and jenkins-el6
19:30:49 <skvidal> happen to be on the same compute node
19:30:53 <skvidal> that's why it is happening
19:30:55 <pingou> ok
19:30:58 <skvidal> pingou: does that explain it?
19:31:26 <nirik> I still need to go over whats left on our 'move to production' list.
19:31:28 <pingou> and the problem is to determine at build time if two instances are on the same node or not to adjust the IP accordingly, right?
19:31:30 <nirik> I'll try and do that soon.
19:31:39 <skvidal> pingou: we can just use the internal ip
19:31:46 <skvidal> pingou: but in the long run that's not a fabulous solution
19:31:54 <skvidal> b/c afaict I cannot assign floating internal ips
19:31:55 <pingou> skvidal: yes
19:31:57 <skvidal> so they are consistent
19:32:05 <skvidal> pingou: but if you'd like it working right now
19:32:09 <skvidal> I can just change the ips in thje jenkins config
19:32:13 <skvidal> and it will just work
19:32:14 <skvidal> poof
19:32:35 <nirik> seems like a ok workaround for now
19:32:35 <pingou> skvidal: one project is using the el6 builder, so yes, we should update the IP in the config file
19:32:40 <skvidal> pingou: wilco
19:32:42 <skvidal> doing right now
19:32:46 <pingou> skvidal: thanks
19:32:48 <nirik> excellent. :)
19:32:55 <nirik> #topic Upcoming Tasks/Items
19:33:08 <nirik> ready for info-dump:
19:33:12 <nirik> #info 2013-03-12 to 2013-03-21 pycon
19:33:12 <nirik> #info 2013-03-19 to 2013-03-26 - koji update
19:33:12 <nirik> #info 2013-03-29 - spring holiday.
19:33:12 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
19:33:12 <nirik> #info 2013-04-15 - remove legacy-openid
19:33:13 <nirik> #info 2013-04-16 F19 alpha release
19:33:15 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
19:33:16 <nirik> #info 2013-05-21 F19 beta release
19:33:18 <nirik> #info 2013-05-31 end of 1st quarter
19:33:20 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
19:33:22 <nirik> #info 2013-06-25 F19 FINAL release
19:33:24 <nirik> anything else folks would like to schedule, note or amend?
19:33:33 <pingou> end of quarter is past?
19:33:55 <pingou> nm, it is
19:34:08 <nirik> yep
19:34:16 <nirik> #topic Open Floor
19:34:25 <nirik> any one have anything for open floor?
19:34:30 <nirik> questions, comments, suggestions, ?
19:34:33 <skvidal> we need help in coprs
19:34:36 <skvidal> if any of the new folks
19:34:39 <skvidal> want to work on an app
19:34:42 <nirik> #info help needed for coprs
19:34:43 <skvidal> and are familiar with python
19:34:56 <skvidal> PLEASE come by #fedora-apps and yell at me or pingou
19:35:05 <pingou> skvidal: we need to document the code and the workflow :)
19:35:16 <nirik> #info coprs helpers see pingou or skvidal in #fedora-apps to help out.
19:35:22 <skvidal> pingou: yes
19:35:26 <skvidal> pingou: I agree
19:35:41 <nirik> FYI, copr's is a setup to let people build collections of packages...
19:35:43 <linuxmania> skvidal, i would like to help, but i never try using python before.
19:36:25 <linuxmania> and do you think if i start learning python, my skills could be solid enough to contribute the project?
19:37:22 <linuxmania> i am not sure. But if you think it is not a very difficult language, i think i will give it a try.
19:38:02 <puiterwijk> linuxmania: python is a pretty easy language if you have already programmed in another language ;)
19:38:07 <pingou> linuxmania: if you have some programming experience and know the basis of object oriented, python shouldn't be to hard
19:39:33 <nirik> ok, anything further, or shall we call it a meeting?
19:40:36 <linuxmania> pingou, puiterwijk. thank you both, then i will find some tutorial and see what it looks like.
19:40:54 <nirik> linuxmania: feel free to ask in #fedora-apps for pointers too.
19:41:44 <nirik> thanks for coming everyone!
19:41:46 <nirik> #endmeeting
Thanks to those who were able to join us for the weekly status meeting today. For those that were unable, the minutes are posted below:
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-13/fedora-meeting…
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-13/fedora-meeting…
Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-13/fedora-meeting…
Paul
===================================================
#fedora-meeting-1: Fedora ARM weekly status meeting
===================================================
Meeting started by pwhalen at 20:00:52 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-13/fedora-meeting…
.
Meeting summary
---------------
* 0) Status of ACTION items from our previous meeting (pwhalen,
20:03:45)
* - INPROGRESS - pbrobinson/bconoboy investigating tog-pegasus -
testsuite hangs, needs a BZ filed (pwhalen, 20:04:07)
* - INPROGRESS - bconoboy and dmarlin to do before/after patchify
builds on critical path packages to demonstrate safety - Patches
posted to the list for feedback (pwhalen, 20:04:37)
* - bconoboy to write fesco ticket (waiting on package analysis)
(pwhalen, 20:05:00)
* - COMPLETE - jonmasters to followup with what Debian and OpenSuSE
did for automated patching - They did not automate patching.
(pwhalen, 20:05:12)
* - INPROGRESS - jonmasters to reply to the fedora list with his dtb
idea (pwhalen, 20:05:54)
* LINK:
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-06/fedora-meeting…
(masta, 20:06:01)
* 1) Problem Packages (pwhalen, 20:08:54)
* problem packages - tog-pegasus, java, python-pillow (pwhalen,
20:13:18)
* 2) Aarch64 patching (pwhalen, 20:17:04)
* bconoboy sent aarch64 patches to pbrobinson and dgilmore for
feedback. (pwhalen, 20:21:50)
* ACTION: pbrobinson/dgilmore to provide feedback on aarch64 patches
(pwhalen, 20:22:09)
* ACTION: ahs3 to do another package scan this evening for aarch64
patching, send to the list for review (pwhalen, 20:25:51)
* 3) Creating test candidate images for F19 (pwhalen, 20:28:51)
* 4) Release Criteria - changes required for ARM (pwhalen, 20:31:24)
* LINK:
https://fedoraproject.org/wiki/User:Adamwill/Draft_alpha_criteria_sandbox
(pwhalen, 20:32:27)
* 5) Open Floor (pwhalen, 20:40:11)
Meeting ended at 20:44:36 UTC.
Action Items
------------
* pbrobinson/dgilmore to provide feedback on aarch64 patches
* ahs3 to do another package scan this evening for aarch64 patching,
send to the list for review
Action Items, by person
-----------------------
* ahs3
* ahs3 to do another package scan this evening for aarch64 patching,
send to the list for review
* dgilmore
* pbrobinson/dgilmore to provide feedback on aarch64 patches
* pbrobinson
* pbrobinson/dgilmore to provide feedback on aarch64 patches
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pwhalen (54)
* ahs3 (11)
* zodbot (9)
* bconoboy (8)
* masta (6)
* nirik (5)
* dmarlin (4)
* jonmasters (3)
* oatley (1)
* pbrobinson (0)
* ctyler (0)
* dgilmore (0)
=================================================
#fedora-blocker-review: f19alpha-blocker-review-1
=================================================
Minutes: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-13/f19alpha-…
Minutes (text): http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-13/f19alpha-…
Log: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-13/f19alpha-…
Meeting summary
---------------
* Roll Call (tflink, 17:02:30)
* Introduction (tflink, 17:08:58)
* 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, 17:09:08)
* We'll be following the process outlined at: (tflink, 17:09:16)
* LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
(tflink, 17:09:16)
* The bugs up for review today are available at: (tflink, 17:09:22)
* LINK: http://qa.fedoraproject.org/blockerbugs/current (tflink,
17:09:22)
* The criteria for release blocking bugs can be found at: (tflink,
17:09:28)
* LINK:
https://fedoraproject.org/wiki/Fedora_19_Alpha_Release_Criteria
(tflink, 17:09:28)
* Up for review today, we have: (tflink, 17:09:53)
* 2 Proposed Blockers (tflink, 17:09:59)
* 0 Accepted Blockers (tflink, 17:09:59)
* 1 Proposed Freeze Exceptions (tflink, 17:09:59)
* 0 Accepted Freeze Exceptions (tflink, 17:09:59)
* (919743) gdm unusable on old video card (tflink, 17:10:48)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=919743 (tflink,
17:10:48)
* Proposed Blocker, gdm, NEW (tflink, 17:10:48)
* for F19, firstboot is now called initial setup (tflink, 17:15:31)
* AGREED: 919743 - We suspect that this is a more general problem not
limited to older graphics hardware - will revisit at the next
meeting after more triage work has been done (tflink, 17:27:03)
* (909473) Fail whale page appears after logging in (tflink, 17:27:20)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=909473 (tflink,
17:27:20)
* Proposed Blocker, gnome-shell, NEW (tflink, 17:27:20)
* AGREED: 909473 - RejectedBlocker, AcceptedFreezeException - With
gnome 3.8, the non-3d-accelerated option is being removed and
blacklisted cards don't fallback to llvmpipe making them unusable
with gnome. While not quite an alpha issue due to the limited amount
of hw affected, a tested fix would be considered after F19 alpha
freeze (tflink, 17:44:30)
* (894110) The "standard" comps group could use a bit of spring cleaning
(tflink, 17:46:12)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=894110 (tflink,
17:46:15)
* Proposed Freeze Exceptions, comps, NEW (tflink, 17:46:17)
* AGREED: 894110 - RejectedFreezeException - This bug does not meet
the requirements of a FE and should be tracked like a normal bug.
(tflink, 17:50:07)
* Open Floor (tflink, 17:50:23)
Meeting ended at 17:57:57 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* tflink (96)
* jreznik (30)
* adamw (27)
* kparal (15)
* nirik (12)
* zodbot (4)
* satellit_e (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20130311
Next meeting is scheduled for 2013-03-18 at 1500 UTC in #fedora-meeting.
If you have topics you think we should bring up at the
meeting, please add them to the Wiki page at
https://fedoraproject.org/wiki/QA/Meetings/20130318 . Thanks!
TOPIC: Previous meeting follow-up
=======================================================================
* adamw to push the blocker meeting changes live this week -
this was done[1], and the next review meeting will be in
#fedora-blocker-review. nirik will make #fedora-bugzappers
redirect to #fedora-qa for now
* viking-ice or adamw to file a trac ticket for the
smoke-test-for-spins idea - this was done by adamw[2]
* adamw to propose RATS/TC1 dates on the list - this was done[3]
and would be discussed later
* tflink to announce first blocker meeting for wednesday, and
get blocker bug tracker app ready - meeting was cancelled due
to lack of bugs, but the app is ready
* jreznik to pencil in QA changes as discussed - this was done,
we will finalize the changes during the meeting
* adamw to draft up changes to the test day process docs to
accommodate test days being on any day, test day co-ordinator
to ensure they're balanced out - this was put into production
immediately[4] as it turned out to be a small change
TOPIC: Fedora 19 schedule
=======================================================================
* The proposed image compose schedule for Fedora 19[5] was
acceptable to all, jreznik will make it 'final'
TOPIC: Test Days
=======================================================================
* We'll need to do some special care and feeding of a KDE test
day image for this week
* Other proposed topics left till next week
TOPIC: Criteria re-design
=======================================================================
* adamw's proposal[6] was discussed: generally positive response
* There was some discussion of numbering the criteria,
j_dulaney withdrew the suggestion
* pwhalen raised the topic of 'ARM friendliness', adam said
he'd been working with that in mind to ensure the revamped
criteria are easily applicable to ARM when it goes primary
* adamw planned to keep working on refining the re-design
TOPIC: Open floor
=======================================================================
* nirik noted his proposal to create a tracker bug for major
Rawhide bugs[7] and proposal to revamp the Rawhide wiki
page[8]. Both were generally positively received
ACTION ITEMS
=======================================================================
* jreznik to ink in the proposed image schedule, and add a Test
Day entry
1. https://lists.fedoraproject.org/pipermail/test/2013-March/114175.html
2. https://fedorahosted.org/fedora-qa/ticket/363
3. https://lists.fedoraproject.org/pipermail/test/2013-March/114176.html
4. https://lists.fedoraproject.org/pipermail/test/2013-March/114194.html
5. https://lists.fedoraproject.org/pipermail/test/2013-March/114176.html
6. https://lists.fedoraproject.org/pipermail/test/2013-March/114198.html
7. https://lists.fedoraproject.org/pipermail/test/2013-March/114231.html
8. https://lists.fedoraproject.org/pipermail/devel/2013-March/179597.html
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We had a meeting today, here are some highlights:
- - jreznik wants out input on the planning process at
https://fedoraproject.org/wiki/User:Mmaslano/Feature_process . Please reply to
his last mail to the list with any thoughts.
- - When we figure out how our publishing process is going to work, we will have
to document it.
- - The F19 schedule is out, and we are part of it. Please work it into your
personal calendaring solution.
- - We're getting closer to shipping RPMs in the user repos, but the best way to
do so is debatable.
- - Sparks is liberating a lot of security related articles and such.
- - Fedora Magazine is happening, somewhere.
The overview is at:
http://meetbot.fedoraproject.org/fedora-
meeting/2013-03-11/https:fedoraproject.orgwikidocs_project_meetings.2013-03-11-14.01.html
Logs and text in:
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-11/
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRPfkXAAoJEL1wZM0+jj2ZZrQH/jXY//mYa3xo/zS2dY171rbB
dLapLHKX6Z3/H8NrUvXAUltp9Ena2rAckoS4NIlBH1WiUAHUIAXmiy1TvNgaw492
Da+Ag6ovPryiqvWVhpYIMdMELTyCexFr+MSNck9yEP1Tn7mYa8qVAToevYj7e4Py
M2gz5ottEABaz2kjhn/LZ2RYNsFm8md3h6Nx/xIyQsFs+tHAkJJLP4Bm0BKF/wWH
1vjrawGZgAIG506mYQ69t8hREgv4HRHOtzHSKpMl9J44iU8BHdjlWek+PhtOY85K
6LGkWjaBm9ZtgH6P0NNDHKSrKuN3bAP0xsUqcRgKGpMPxk6eD71Cyu++QhYnmYM=
=N513
-----END PGP SIGNATURE-----
============================================
#fedora-meeting: Infrastructure (2013-03-07)
============================================
Meeting started by nirik at 18:59:59 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-03-07/infrastructure.2…
.
Meeting summary
---------------
* welcome everyone (nirik, 18:59:59)
* New folks introductions and Apprentice tasks (nirik, 19:02:28)
* new folks would be advised to look into ansible. (nirik, 19:11:09)
* Applications status / discussion (nirik, 19:11:16)
* fas-openid is now in production. Thanks puiterwijk. :) (nirik,
19:11:42)
* fedmsg starting to be enabled for secondary arch compose processes.
(nirik, 19:12:30)
* fedmsg-notify blog post out there, hopefully more consumers (nirik,
19:14:03)
* LINK: https://admin.fedoraproject.org/haproxy/proxy01 (lmacken,
19:14:18)
* LINK: http://lewk.org/blog/fedmsg-notify.html (pingou, 19:14:19)
* Sysadmin status / discussion (nirik, 19:24:17)
* ssmoogen reinstalled proxy01 as x86_64... (nirik, 19:25:18)
* smooge is waiting to find out if physical memory arrived in PHX2 so
we can give it to systesm (ssmoogen, 19:30:38)
* Private Cloud status update / discussion (nirik, 19:34:17)
* moving things into openstack cloudlet (nirik, 19:36:13)
* will move some compute nodes from the other cloudlet over to it, and
then have 2 nodes to continue testing other things with. (nirik,
19:36:53)
* Upcoming Tasks/Items (nirik, 19:39:33)
* 2013-03-07 remove inactive apprentices. (nirik, 19:39:38)
* 2013-03-12 to 2013-03-21 pycon (nirik, 19:39:39)
* 2013-03-19 to 2013-03-26 - koji update (nirik, 19:39:39)
* 2013-03-29 - spring holiday. (nirik, 19:39:39)
* 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik,
19:39:39)
* 2013-04-16 F19 alpha release (nirik, 19:39:40)
* 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik,
19:39:41)
* 2013-05-21 F19 beta release (nirik, 19:39:43)
* 2013-05-31 end of 1st quarter (nirik, 19:39:45)
* 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik,
19:39:47)
* 2013-06-25 F19 FINAL release (nirik, 19:39:49)
* Open Floor (nirik, 19:40:38)
* idea: do some vfads and focus on specific areas to get them done.
(nirik, 19:42:41)
Meeting ended at 20:03:41 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (117)
* skvidal (98)
* abadger1999 (38)
* lmacken (30)
* pingou (24)
* threebean (14)
* blackdeerranger (9)
* KasumiNinja (7)
* ssmoogen (5)
* zodbot (4)
* Adran (4)
* mdomsch (3)
* cyberworm54 (3)
* maayke (2)
* samkottler (1)
* SmootherFrOgZ (1)
* puiterwijk (1)
* smooge (0)
* ricky (0)
* dgilmore (0)
* CodeBlock (0)
--
18:59:59 <nirik> #startmeeting Infrastructure (2013-03-07)
18:59:59 <zodbot> Meeting started Thu Mar 7 18:59:59 2013 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:59:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:59:59 <nirik> #meetingname infrastructure
18:59:59 <zodbot> The meeting name has been set to 'infrastructure'
18:59:59 <nirik> #topic welcome everyone
18:59:59 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean
19:00:00 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean
19:00:21 <nirik> who all is around for a infrastructure meeting?
19:00:23 * lmacken
19:00:35 * cyberworm54 here
19:00:37 * abadger1999 here
19:00:40 <blackdeerranger> here
19:00:41 * maayke here
19:00:48 <KasumiNinja> KasumiNinja here
19:01:11 * threebean is here
19:01:24 * nirik will wait another min for folks to wander in.
19:02:03 * pingou
19:02:22 <nirik> ok, I guess we can go ahead and dive in. ;)
19:02:28 <nirik> #topic New folks introductions and Apprentice tasks
19:02:42 <nirik> any new folks want to introduce themselves? or apprentices with questions?
19:02:50 <blackdeerranger> me
19:02:52 <KasumiNinja> I'm new
19:03:06 <ssmoogen> here
19:03:12 * SmootherFrOgZ is here
19:03:21 <mdomsch> hola
19:03:27 <KasumiNinja> I work as a sysadmin and like to help fedora with sysadmin tasks
19:03:34 <nirik> blackdeerranger / KasumiNinja: welcome. ;)
19:03:39 <blackdeerranger> :)
19:03:47 <KasumiNinja> :-)
19:04:03 <nirik> blackdeerranger: are you also interested in sysadmin side of things? or more application development?
19:04:07 <KasumiNinja> I have no programming experience
19:04:21 <blackdeerranger> I typed my introduction here: http://paste.fedoraproject.org/4574/80565136/
19:04:45 <blackdeerranger> I´m interested in sysadmin tasks
19:04:59 <nirik> one thing I'd like to mention here... I sent out my regular fi-apprentice feedback email and got some email back that highlighted how self driven we require people to be...
19:05:02 <blackdeerranger> I´m not a software developer
19:05:37 <nirik> cool.
19:06:13 <cyberworm54> http://paste.fedoraproject.org/4574/80565136/
19:06:19 <cyberworm54> oops sorry :)
19:06:22 <nirik> I'm wondering if we want to try and change that focus any, or if there are ways to better communicate it to new folks so they don't get confused when no one is assigning them specific tasks and asking for updates all the time.
19:07:16 <nirik> perhaps I will start a discussion on the list around that, just wanted to mention it here.
19:07:18 <blackdeerranger> As I unterstand it is a good staring point to join "fi-apprentice "
19:07:22 <maayke> nirik: I will send you email tomorrow :)
19:07:28 <nirik> blackdeerranger: yeah.
19:07:33 <blackdeerranger> good
19:08:09 <nirik> the thing is that we are not setup to do heavy mentoring... so joining usually means the new person has to be very focused on just going and doing things and bugging people.
19:08:22 <KasumiNinja> works fine for me
19:08:25 * samkottler is just getting here
19:09:00 <skvidal> something worth mentioning
19:09:06 <nirik> anyhow, will post a thread to the list about it. ;) just brainstorming.
19:09:08 <skvidal> given where fedora infra is going with config mgmt and c&c
19:09:15 <skvidal> anyone interested in the sysadmin side of things
19:09:27 <skvidal> would be best served by going to ansible.cc
19:09:35 <skvidal> and trying it out for themselves to be familiar
19:09:44 <nirik> absolutely. ;)
19:09:54 <skvidal> we have lots of examples at: http://infrastructure.fedoraproject.org/cgit/ansible.git/tree/
19:10:08 <skvidal> but our examples are going to increasingly get more complicated, I suspect :)
19:10:28 <nirik> they always do.
19:10:29 <skvidal> so KasumiNinja, blackdeerranger: probably worth familiarizing yourself with this tool
19:10:55 <blackdeerranger> sounds interesting - thanks
19:11:09 <nirik> #info new folks would be advised to look into ansible.
19:11:16 <nirik> #topic Applications status / discussion
19:11:29 <KasumiNinja> great I'll look into it
19:11:29 <nirik> any exciting application side news this week or upcoming?
19:11:38 * pingou has mainly be bothering threebean
19:11:42 <nirik> #info fas-openid is now in production. Thanks puiterwijk. :)
19:11:43 <pingou> been*
19:11:51 <skvidal> KasumiNinja, blackdeerranger: great
19:11:53 <pingou> \ó/ well done puiterwijk
19:12:06 <threebean> we *just* got our first fedmsg message out of the secondary arch compose process
19:12:10 <abadger1999> Three cheers for puiterwijk :-)
19:12:16 <threebean> puiterwijk++
19:12:30 <nirik> #info fedmsg starting to be enabled for secondary arch compose processes.
19:12:48 <abadger1999> puiterwijk and I also discussed oauth to some length. I'm organizing that into a message to send to the list.
19:12:57 <lmacken> I announced the fedmsg-notify today, so we'll hopefully see a lot more consumers
19:13:08 <abadger1999> An oauth server is what I think his next project is going to be.
19:13:19 <lmacken> I also fixed some long-standing push ordering bugs in the bodhi masher last week
19:13:36 <nirik> lmacken: yeah. Great post. ;)
19:13:41 <lmacken> thanks ☺
19:13:48 * Adran is here (late)
19:14:03 <nirik> #info fedmsg-notify blog post out there, hopefully more consumers
19:14:07 <pingou> nice lmacken
19:14:12 <nirik> lmacken: do we have any way to tell how many consumers there are?
19:14:18 <lmacken> https://admin.fedoraproject.org/haproxy/proxy01
19:14:19 <lmacken> and 02
19:14:19 <pingou> #link http://lewk.org/blog/fedmsg-notify.html
19:14:28 <lmacken> fedmsg-raw-zmq-outbound
19:14:29 <nirik> cool.
19:14:48 <pingou> lmacken: where is your blog plugin?
19:14:56 <lmacken> pingou: hrm?
19:15:02 <nirik> abadger1999: related. Have we given any thought about further expanding our 2 factor stuff to web apps or other places? Or haven't really explored that yet.
19:15:07 <abadger1999> mdomsch: Question -- is python-GeoIP still needed for mirrormanager? I noticed that it was orphaned in Fedora/EPEL.
19:15:11 <pingou> lmacken: I saw tour twitter feed on your blog and I went... :)
19:15:45 <abadger1999> nirik: yes -- SmootherFrOgZ has been working up a patch to do 2-factor login to fas and support in python-fedora to take advantage of that.
19:15:53 <mdomsch> abadger1999: yep - largely used. I'll have to go adopt it
19:15:58 <abadger1999> nirik: I think that'll give us the first step.
19:16:28 <nirik> abadger1999: ah ha. I was confused as to what that work was about. Good.
19:16:38 <abadger1999> mdomsch: Cool. If you need help, feel free to add me as a comaintainer and I'll put it on my once a cycle, look for updates list.
19:16:43 <nirik> note that also fas-openid has that PAPE plugin we could use for openid consuming applications.
19:16:49 <abadger1999> nirik: His work will be a first step.
19:17:03 <abadger1999> There's lots of other things that need to happen before it's "real"
19:17:21 <abadger1999> ie: at first we'll have both the single factor and 2-factor login.
19:17:28 <nirik> sure, yeah
19:17:36 <abadger1999> so you could circumvent by simply going to the other login page.
19:17:58 <abadger1999> But first we get it working, then we make it mandatory for some people.
19:18:08 * nirik nods.
19:18:16 <abadger1999> So -- continuing to make progress :-)
19:18:20 <lmacken> not sure if it was talked about last week, but we hit yet an issue with our tg1 apps where they would just silently block all requests. It happened after some dns change, but hopefully this change will fix it in the future. https://github.com/fedora-infra/python-fedora/pull/18
19:18:20 <nirik> also, that would only be yubikey?
19:18:49 <abadger1999> nirik: yeah -- since fas only knows about yubikey at this point.
19:18:54 <nirik> lmacken: ah yes, thanks for finding that. ;) We should try and get that fix rolled out to production...
19:18:58 <abadger1999> It's another thing we'll have to do to get this good to go.
19:19:13 <Adran> abadger1999: I might poke you later, I'd be interested in seeing if Google Authenticator could work, maybe I can work on something.
19:19:44 <abadger1999> Adran: cool. It should. We just have to integrate it more tightly with fas (we have basically a separate google authenticator setup right now)
19:19:54 <Adran> Ah.
19:20:01 <skvidal> Adran: could work where? we have support for google auth in totpcgi - it's available - just not integrated to fas
19:20:05 <skvidal> Adran: yes - what abadger1999 said :)
19:20:22 <nirik> so, next week is fudcon... how many of you will be out there?
19:20:24 <Adran> skvidal: Right. Maybe it can be integrated? :)
19:20:51 <threebean> nirik: s/fudcon/pycon/
19:20:58 <threebean> I'll be there :)
19:21:00 <nirik> yeah, sorry, brain failure. ;)
19:21:01 <lmacken> me too
19:21:50 <nirik> so, suggestion: we may want to be cautious about application changes tomorrow/the weekend... just so things are not possibly unstable with all you folks gone. ;)
19:22:37 <nirik> and hopefully you all have safe travels. :)
19:22:55 <nirik> any other application news?
19:23:10 <threebean> pingou started a really good conversation with hughsie about integrating tagger with AppStream
19:23:30 <threebean> and he's already written some code for it today.
19:23:38 <threebean> Pretty exciting. :)
19:23:40 <nirik> cool. I saw some of that.
19:23:46 <nirik> I haven't looked at appstream yet much...
19:24:17 <nirik> #topic Sysadmin status / discussion
19:24:25 <abadger1999> I'll be there
19:25:03 <nirik> so, lets see... not too much on the sysadmin side that I can recall in detail. ;)
19:25:14 <skvidal> nirik: a few things
19:25:18 <nirik> #info ssmoogen reinstalled proxy01 as x86_64...
19:25:27 <nirik> (which is good, since it now matches all the other proxies)
19:25:32 <ssmoogen> and I think it worked
19:25:32 <skvidal> 1. we've been moving ahead on the ansible conversion
19:25:46 * mdomsch is going to need mmbapp01 to be x86_64 too due to s3cmd memory usage
19:25:59 <skvidal> 2. I've added a path lookup plugin to ansible that will allow us to have lookups for staging then production like we do now in puppet
19:26:19 <threebean> nice!
19:26:31 <pingou> very nice
19:26:36 <nirik> skvidal: yep. :) we need to test out some workflow there/make some simple playbooks for simple hosts to test things out.
19:26:48 <nirik> mdomsch: :( oh well... we can do that.
19:26:51 <skvidal> 3. more things moving into openstack and we're already running into limits of our available resources
19:27:11 <pingou> oh :(
19:27:14 <skvidal> I have 4 more instances to finish transitioning and then we can start moving systems over to increase the available resources
19:27:30 <skvidal> which is great b/c that should double our available resources
19:28:01 <skvidal> nirik: for later - we might consider tinkering with multiple availability zones and osuosl02
19:28:04 <nirik> and add cinder volumes from each of the compute nodes.
19:28:15 <nirik> yep. That would be great.
19:29:02 <nirik> so, that bug that lmacken mentioned earlier... I was wondering, should we make app servers depend on their local proxy ?
19:29:19 <nirik> right now they hit admin.fedoraproject.org, which is dns round robin for all of them.
19:29:28 <nirik> but if they talked to their local proxy it might be faster.
19:29:36 <nirik> and also if that proxy is down, then likely they are too.
19:29:59 <lmacken> so appX->proxyX?
19:30:34 <nirik> yeah.
19:30:38 <ssmoogen> #info smooge is waiting to find out if physical memory arrived in PHX2 so we can give it to systesm
19:30:42 <nirik> app01/02/03/04 would hit proxy01
19:31:32 <nirik> anyhow, it's a thought. I don't think it's urgent.
19:31:46 <skvidal> nirik: query on this
19:32:04 <skvidal> would it make more sense for us to pursue the above? or for us to pursue breaking all the apps out?
19:32:36 <nirik> well, the above is pretty trivial if we want to do it. ;) Breaking apps out is still a longer term thing we really must do, IMHO.
19:32:54 <skvidal> nirik: fair enough..
19:33:02 <skvidal> if the proxies were running next to the app servers
19:33:07 <skvidal> like on the same hw
19:33:10 <skvidal> I';m inclined to say yes
19:33:22 <nirik> and I think breaking apps out kinda wants ansible to be ready to handle those apps.
19:33:25 <skvidal> but we don't really want an outage on proxy01 to kill the app servers
19:33:35 <nirik> yeah, true.
19:33:50 <nirik> well, lets leave it for now...
19:34:17 <nirik> #topic Private Cloud status update / discussion
19:34:20 <abadger1999> About the private cloud -- does this mean we're going to just use openstack going forward?
19:34:24 <nirik> we already hit on some of this above...
19:34:33 <skvidal> abadger1999: so right now here is what we have discussed
19:34:43 <skvidal> abadger1999: 1. moving the instances we have over to openstack
19:34:54 <skvidal> 2. moving 2 of the compute nodes over to openstack for additional resources
19:35:04 <skvidal> 3. taking the remaining 2 machines for other prototyping/testing
19:35:22 <skvidal> whether 3 is of openstack or of $something_else is really up to later discussion/decision
19:35:32 <abadger1999> <nod>
19:36:03 <ssmoogen> would adding another proxy to phx2 help?
19:36:07 <abadger1999> Okay so it seems like our "production" services are moving openstack but we're still testing out the alternatives ?
19:36:13 <nirik> #info moving things into openstack cloudlet
19:36:53 <nirik> #info will move some compute nodes from the other cloudlet over to it, and then have 2 nodes to continue testing other things with.
19:37:08 <nirik> abadger1999: yeah, or possibly we will use the other 2 to test the next openstack version...
19:37:14 <abadger1999> <nod>
19:38:08 <nirik> I think we can knock a bunch of things off our 'need to figure out before production' list now too.
19:38:24 <nirik> I'll look at cleaning up the wiki page on that, since I think we solved or decided many of them
19:38:50 <nirik> anything else on cloudlets?
19:39:04 <skvidal> no - but I had something for openfloor when that happens
19:39:28 <nirik> ok
19:39:33 <nirik> #topic Upcoming Tasks/Items
19:39:38 <nirik> #info 2013-03-07 remove inactive apprentices.
19:39:39 <nirik> #info 2013-03-12 to 2013-03-21 pycon
19:39:39 <nirik> #info 2013-03-19 to 2013-03-26 - koji update
19:39:39 <nirik> #info 2013-03-29 - spring holiday.
19:39:39 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
19:39:40 <nirik> #info 2013-04-16 F19 alpha release
19:39:41 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
19:39:43 <nirik> #info 2013-05-21 F19 beta release
19:39:45 <nirik> #info 2013-05-31 end of 1st quarter
19:39:47 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
19:39:49 <nirik> #info 2013-06-25 F19 FINAL release
19:39:51 <nirik> anything anyone would like to schedule or note?
19:40:11 <nirik> we have a little less than a month until alpha freeze.
19:40:38 <nirik> #topic Open Floor
19:40:42 <nirik> skvidal: you had something?
19:40:45 <skvidal> yah
19:40:53 <skvidal> something I was thinking about
19:40:53 <pingou> I sent somethings about jenkins, feedbacks welcome :)
19:41:01 <skvidal> in any given week we're all working on a billion things
19:41:06 <nirik> pingou: yeah, I have it marked to reply to. ;) Thanks.
19:41:15 <skvidal> and I was wondering if there was any thought to doing something like a virtual fad week
19:41:26 <skvidal> where we intend to focus on a few tasks and get them done
19:41:31 <nirik> skvidal: focusing on one area?
19:41:33 <pingou> sounds nice
19:41:34 <nirik> yeah.
19:41:35 <skvidal> right
19:41:39 <skvidal> we all are on irc
19:41:42 <skvidal> and most of the time all day long
19:41:55 <nirik> I think that kind of thing is very effective if we plan exactly what we want to try and do.
19:41:55 <skvidal> it seems like it would be very possible to schedulea vfad
19:41:57 <pingou> and most of us in a close timezone :)
19:42:00 <nirik> and make sure the needed people are available
19:42:09 <skvidal> hell, tie us toigether using a google hangout if need be
19:42:18 * threebean nods
19:42:20 <skvidal> but announce that we will be focused on one thing
19:42:28 <skvidal> and unavailable for random-ass pings
19:42:41 <nirik> #info idea: do some vfads and focus on specific areas to get them done.
19:42:48 <skvidal> I liked that we were able to knock out a specific problem last year for the 2fa fad
19:42:57 <skvidal> and I think we should try it w/o the relocation
19:43:10 <skvidal> so what subjects would be things we could knock out?
19:43:20 <nirik> application logging?
19:43:27 * lmacken was just about to say that :P
19:43:30 <pingou> 2fa app wise
19:43:30 <threebean> perfect
19:43:53 <lmacken> breaking apps out
19:43:53 <skvidal> what else?
19:44:13 <threebean> ansible migration
19:44:43 <pingou> CLI logins for our web-app
19:44:47 <nirik> fedorahosted-ng
19:44:58 <pingou> but that comes back to the discussion abadger1999 wants to start :)
19:45:15 <lmacken> IDS
19:45:26 <pingou> IDS?
19:45:31 <lmacken> intrusion detection system
19:45:46 <pingou> ah, cool
19:45:48 * skvidal is making a list
19:45:51 <nirik> identify and plan how to get rid of our SPOF.
19:45:56 <skvidal> the db?
19:46:04 <skvidal> db-replication
19:46:11 <nirik> db's are a big one.
19:46:18 <pingou> spof?
19:46:19 <nirik> there might be other things tho.
19:46:24 <skvidal> single point of failure
19:46:26 <abadger1999> <nod> I'd love to have some FADs on 2-fa and oauth.
19:46:27 <nirik> sorry, single point of failure.
19:46:34 <abadger1999> oauth needs some discussion first.
19:47:08 <abadger1999> 2-fa is closer to having a solid plan where a FAD type setting would really help
19:47:42 <skvidal> okay that's a good list start
19:47:43 <abadger1999> lmacken, for app logging -- do we know how to fix the problems we have?
19:48:04 * abadger1999 still hasn't found any reason we aren't getting all tracebacks in our logs.
19:48:35 <lmacken> abadger1999: I didn't know tracebacks were not appearing. Could be a few things.
19:48:49 <lmacken> I'd love to experiment with https://github.com/ryanpetrello/canary
19:49:12 <abadger1999> lmacken: that's like my number 1 problem with app logging since 2007 or so :-)
19:49:18 <pingou> spof?
19:49:20 <pingou> sorry
19:49:25 <lmacken> hmm, probably a simple ini or wsgi config tweak honestly
19:49:36 <nirik> getting all the data is a good first step, then to fix/reduce so it only tells us about real errors...
19:49:36 <ssmoogen> single point of failure
19:49:41 <skvidal> pingou: places where if that server/service dies then everything dies
19:49:52 <skvidal> nirik: I'll add another item to our list
19:49:53 <skvidal> nirik: nagios
19:50:01 <nirik> I know some apps really send a ton of stuff... I think fas sends to error_log on every successfull login.
19:50:18 <nirik> yeah. I have done some work on nagios, but there is more to plan out and do.
19:50:25 <pingou> skvidal: I hit arrow up/enter in the wrong window, sorry for the noise
19:50:37 <skvidal> pingou: oh - I thought you were still wondering what that means
19:50:57 <abadger1999> lmacken: I would think so... but I know you've looked at it a ton of times nad we've only succeeded in over logging things that we don't care about :-/
19:51:47 <nirik> I'd love to get to the point where someone says "hey, I just hit $app and got a 500" and we can easily see a traceback to attach to a ticket about it. ;)
19:52:02 <skvidal> so
19:52:05 <lmacken> abadger1999: potential pycon hackfest item :)
19:52:05 <skvidal> wrt app logging
19:52:10 <skvidal> it seems, to me, somewhat obvious
19:52:14 <skvidal> that if we break out app servers
19:52:18 <skvidal> logging becomes A LOT simpler
19:52:21 <nirik> yep.
19:52:22 <skvidal> doesn't it?
19:52:34 <nirik> if the log is from foobarapp01 it's likely caused by foobarapp
19:52:34 <threebean> yup
19:52:35 <skvidal> since isolating the logs for tagger won't involve sifting through a bunch of other logs
19:52:41 <abadger1999> skvidal: for some definition of a lot.
19:52:44 <abadger1999> yeah
19:52:45 <skvidal> (tagger was just an example)
19:52:51 <abadger1999> that's about 1/3 of the problem i think.
19:53:09 <skvidal> abadger1999: what are the other 2/3rds?
19:53:12 <lmacken> centralizing
19:53:13 <lmacken> analyzing
19:53:30 <abadger1999> another 1/3 is getting logs consolidated per service rather than per host.
19:53:32 <lmacken> realtime notifications of Bad Errors
19:53:46 <lmacken> trending
19:53:53 <abadger1999> ie: fas is its on boxes but it's still hard to search for the traceback because it could be on fas1,2,3
19:54:08 <abadger1999> *on its own boxes
19:54:20 <skvidal> okay - a couple of things to note - with our existing logging configuration on log02
19:54:26 <skvidal> right now we have 2 major logging groups
19:54:27 <pingou> load balancing makes it harder for sure
19:54:27 <skvidal> per-host
19:54:28 <skvidal> and merged
19:54:38 <skvidal> there is nothing stopping us from grouping those logs, too
19:54:43 <skvidal> ie: fas
19:54:46 * nirik nods
19:54:47 <skvidal> apps
19:55:02 <lmacken> hookup up the SyslogHandler for each app is still on the TODO
19:55:04 <skvidal> so you'd end up with consolidated syslogs/app logs int /var/log/groups/fas/
19:55:49 <abadger1999> skvidal: It's syslog based for the apache logs? So we can have a single log file for a service? Because that would be really nice.
19:55:59 <skvidal> abadger1999: well we have the app log now
19:56:34 <skvidal> which is only for apps which are using it
19:56:42 <nirik> which isn't many
19:56:42 <lmacken> bodhi in stg atm, iirc
19:56:43 <skvidal> istr it is local4
19:56:54 <skvidal> (that's the log facility)
19:56:57 * lmacken hasn't had cycles to wrap that up
19:57:09 <skvidal> yes local4
19:57:16 <skvidal> abadger1999: so we have 2 options there
19:57:25 <lmacken> (documented here: https://fedoraproject.org/wiki/Infrastructure/AppBestPractices#Centralized_…)
19:57:41 <skvidal> 1. setup apache on the app servers to emit all error logs to logger on local4
19:57:52 <skvidal> 2. figure out a nicer way to setup apache/our apps
19:58:00 <skvidal> (or something in between)
19:58:08 <skvidal> I'd like to suggest one more avenue
19:58:11 <skvidal> that will require testing
19:58:13 <skvidal> and discussion
19:58:24 <skvidal> but is this - if there is a non-syslog mechanism for getting apache logs off of systems
19:58:33 <skvidal> let's hear about it
19:59:05 <nirik> we could also work on reducing our syslogs....
19:59:21 <skvidal> for example if there is a way to use 0mq to emit logs sanely
19:59:27 <skvidal> and to integrate it at the apache layer
19:59:37 <skvidal> I'd be inclined to pay attention to it, personally.
19:59:50 <skvidal> but
19:59:52 <skvidal> 1. it needs to work
19:59:57 <lmacken> where sanely == reliably w/o risk of losing messages
19:59:58 * puiterwijk is finally home and online
19:59:58 <skvidal> 2. be fairly reliable under load
20:00:05 <skvidal> lmacken: :)
20:00:09 <nirik> yeah.
20:00:23 <skvidal> lmacken: it can lose a few - but ideally the ring buffer that rsyslog uses would be the most desireable
20:01:00 <lmacken> sounds like a logging vfad would be a good idea ☺
20:01:01 <nirik> skvidal: so, can you post your vfad list and thoughts around those to the list and we can look at picking one and scheduling it?
20:01:13 * nirik nods. logging seems popular
20:01:17 * lmacken going to Monitorama after PyCon, so may have more ideas later this month
20:01:22 <skvidal> nirik: yes
20:01:34 <nirik> thanks.
20:01:34 <abadger1999> nirik: careful though -- logging is only popular because it's such a pain :-)
20:01:39 <nirik> indeed.
20:01:55 <skvidal> it's only a pain for you crazy kids and your new-fangled webapps ;)
20:02:00 <skvidal> :)
20:02:00 <nirik> ok, any other open floor items before we close out?
20:02:23 <threebean> hm, I'd put a vote in for splitting appservers first. It might make fixing logging easier.
20:02:26 <abadger1999> I think for logging -- we should have a plan (like: reconfigure all apps to log to syslog local4). Then the vfad concentrates on doing that plan.
20:02:57 <nirik> yeah.
20:02:58 <pingou> +
20:03:38 <nirik> ok, thanks for coming everyone. Do continue on #fedora-admin, #fedora-apps, and #fedora-noc.
20:03:41 <nirik> #endmeeting
Howdy,
Minutes from today's meeting follow below.
Had a really interesting conversation - though I think we didn't quite
get through much of the agenda :) We did discuss some categories,
things already packaged, etc. - I'm on duty to make a sub-wiki-page so
we can collectively document some of these things.
Also had some talk around packaging Apache Bigtop as well as the
intersections with that community - as many of their folks apparently
use Fedora (YAY).
Anyway: Keep your intros, thoughts coming - I suspect we'll be
gathering more humans in the coming weeks.
Thanks for coming!
-Robyn
Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-07/big_data_sig.2…
Full logs: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-07/big_data_sig.2…
===============================
#fedora-meeting-1: Big Data SIG
===============================
Meeting started by rbergeron at 16:59:44 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-03-07/big_data_sig.2…
.
Meeting summary
---------------
* Who's around for fun? (rbergeron, 17:00:05)
* present: rbergero, tflink (rbergeron, 17:01:15)
* present: witlessb (rbergeron, 17:01:45)
* present: threebean, zoglesby, samkottler, jsmith (rbergeron,
17:02:18)
* Agenda for today's first meeting :D (rbergeron, 17:03:49)
* LINK:
http://lists.fedoraproject.org/pipermail/bigdata/2013-March/000003.html
(rbergeron, 17:04:32)
* Agenda looks like: What this is all about, what do we have, what
don't we have, what is anyone here interested in doing :)
(rbergeron, 17:05:09)
* What's the Big Data SIG all about? (rbergeron, 17:05:57)
* loosely quoting from o'reilly: "If the size of your data is part of
the problem, it's Big Data." (rbergeron, 17:07:57)
* IDEA: one part of it is getting a decent setup; other part is
understanding tools and approaches needed (rbergeron, 17:11:42)
* IDEA: two pieces you hear most about in Big Data seem to be massive
storage, & parallel computing (hadoop, column databases, etc)
(rbergeron, 17:12:16)
* IDEA: another component is online processing or online analysis -
predicting what is trending before its had time to hit disk
(rbergeron, 17:13:29)
* IDEA: for ex. - idea that google can predict flu outbreaks faster
than public health agencies by watcihng search terms; financial
tools as well apply to concept (rbergeron, 17:15:49)
* IDEA: another ex. of stream processing is twitter analytics -
looking for emerging topics in twitter streams (rbergeron,
17:16:52)
* What are the buckets or categories, and what do we have? (rbergeron,
17:18:21)
* IDEA: orchestration, batch processing, stream processing are
categories that come to mind - orch (zookeeper), batch (hadoop,
disco), stream (storm) (rbergeron, 17:21:23)
* IDEA: storage is another category (rbergeron, 17:22:25)
* IDEA: full hadoop stack seems to be thought of as useful foundation
layer for some types of work, but HDFS is getting attention as weak
spot, with nosql dbs and gluster being used as alternatives
(rbergeron, 17:23:00)
* hdfs is part of the hadoop project; one can install hdfs without
using the mapreduce part (rbergeron, 17:28:05)
* lots of java libraries, servers like tomcat (used by solr, oozie)
are already in (rbergeron, 17:44:01)
* IDEA: we have pandas (not the animal, http://pandas.pydata.org) -
useful for data analysis, not really big data (rbergeron, 17:49:40)
* ACTION: rbergeron to add a sub-page of packges we have (unless
someone beats me to it) (rbergeron, 17:50:18)
* IDEA: interest in disco - seems to be more python-friendly than
hadoop (though we are aware that there are python wrappers for
hadoop) (rbergeron, 18:08:03)
* spring is packaged - could package spring-hadoop (rbergeron,
18:11:24)
* ACTION: bmahe to expound on openjdk/bug filing, as well as the wide
world of bigtop packaging, as time permits :) (rbergeron, 18:12:51)
* Operation Agenda: Yeah... (rbergeron, 18:15:50)
* ACTION: rbergeron to prod in meeting notes to get people to talk re:
what would we like to do (we==they) (rbergeron, 18:23:54)
Meeting ended at 18:26:13 UTC.
Action Items
------------
* rbergeron to add a sub-page of packges we have (unless someone beats
me to it)
* bmahe to expound on openjdk/bug filing, as well as the wide world of
bigtop packaging, as time permits :)
* rbergeron to prod in meeting notes to get people to talk re: what
would we like to do (we==they)
Action Items, by person
-----------------------
* bmahe
* bmahe to expound on openjdk/bug filing, as well as the wide world of
bigtop packaging, as time permits :)
* rbergeron
* rbergeron to add a sub-page of packges we have (unless someone beats
me to it)
* rbergeron to prod in meeting notes to get people to talk re: what
would we like to do (we==they)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* rbergeron (163)
* bmahe (59)
* tflink (36)
* ctyler (27)
* threebean (8)
* zodbot (5)
* witlessb (4)
* samkottler (1)
* zoglesby (1)
* jsmith (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20130304
Next meeting is scheduled for 2013-03-11 at 1600 UTC in #fedora-meeting.
If you have topics you think we should bring up at the
meeting, please add them to the Wiki page at
https://fedoraproject.org/wiki/QA/Meetings/20130311 . Thanks!
TOPIC: Previous meeting follow-up
=======================================================================
* adamw to push 'automatic blocker' proposal to production -
this was done[1]
* adamw to try and gather a bit more feedback on blocker
process changes this week - dgilmore is okay with the
changes, no objections from devel or fesco
* viking-ice or adamw to file a trac ticket for the smoke
test-for-spins idea - not done yet, put back on the agenda
for next week
* tflink to take a look at the question of tracking qa tool
discussion and bugs/tickets and make a broad proposal about
what to do - proposals made[2] and discussion is underway
* We agreed to go with the simplest option of keeping one
trac instance and CCing ticket mails to the appropriate
list with the defaultcc plugin
* viking-ice noted he is working on a proposal to replace trac
with rt[3]
TOPIC: Test Days
=======================================================================
* After discussion of the pros and cons, we decided to make it
clearer that test days can happen on any day (not just
Thursdays)
* Other proposed topics left till next week
TOPIC: Open floor
=======================================================================
* jreznik changed the QA calendar for F19[4] to show blocker
meetings on Wednesdays
* We noted that blocker bug meetings should be starting up
already, and discussed scheduling of RATS and TC composes
ACTION ITEMS
=======================================================================
* adamw to push the blocker meeting changes live this week
* viking-ice or adamw to file a trac ticket for the smoke
test-for-spins idea
* adamw to propose RATS/TC1 dates on the list
* tflink to announce first blocker meeting for wednesday, and
get blocker bug tracker app ready
* jreznik to pencil in QA changes as discussed
* adamw to draft up changes to the test day process docs to
accommodate test days being on any day, test day co-ordinator
to ensure they're balanced out
1. https://lists.fedoraproject.org/pipermail/test/2013-February/114004.html
2. https://lists.fedoraproject.org/pipermail/test/2013-February/113997.html
3. http://www.bestpractical.com/rt/
4. http://fedorapeople.org/groups/schedule/f-19/f-19-quality-tasks.html
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.ne
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A two for one summary today, as I catch up on sending you the minutes:
4 March 2013
- -------------------------------------
Meeting started by randomuser` at 14:01:57 UTC (full logs).
Meeting summary
roll call (randomuser`, 14:02:19)
ACTION: items (randomuser`, 14:06:00)
action items (randomuser`, 14:06:12)
Sponsorship of docs.fedoraproject.org (randomuser`, 14:07:13)
https://bugzilla.redhat.com/show_bug.cgi?id=611891 (randomuser`, 14:08:54)
Docs Infrastructure (randomuser`, 14:13:43)
Outstanding Bugs (randomuser`, 14:19:36)
http://tinyurl.com/lbrq84 (randomuser`, 14:19:45)
open floor (randomuser`, 14:22:17)
Meeting ended at 14:30:06 UTC (full logs).
Action items
items
People present (lines said)
randomuser` (31)
iambryan (6)
zodbot (3)
suehle (2)
zoglesby (2)
lnovich (2)
Sparks (1)
bcotton (1)
jjmcd (1)
Capesteve (1)
- ---------Full logs at http://meetbot.fedoraproject.org/fedora-
meeting/2013-03-04/https:fedoraproject.orgwikidocs_project_meetings.2013-03-04-14.01.log.txt
25 Feb 2013
- ------------------------------------------------------------
Meeting summary
Roll Call (randomuser`, 14:02:10)
Follow up on last week's action items (randomuser`, 14:08:37)
Docs Infrastructure (randomuser`, 14:09:26)
Beat Assignments (randomuser`, 14:14:22)
http://fedoraproject.org/wiki/Category:Documentation_beats (randomuser`,
14:14:28)
Docs Infrastructure (randomuser`, 14:17:56)
Outstanding Bugs (randomuser`, 14:22:04)
http://tinyurl.com/lbrq84 (randomuser`, 14:22:18)
Sparks' bug corner (randomuser`, 14:25:12)
http://tinyurl.com/agh4mg6 (randomuser`, 14:25:33)
ACTION: sgordon to mail docs list to begin discussion of sponsorship banners
at docs.fp.o (randomuser`, 14:40:08)
Open Floor Discussion (randomuser`, 14:42:44)
http://immanetize.fedorapeople.org/release-notes.spec (randomuser`, 14:53:37)
Meeting ended at 15:02:33 UTC (full logs).
Action items
sgordon to mail docs list to begin discussion of sponsorship banners at
docs.fp.o
Action items, by person
sgordon
sgordon to mail docs list to begin discussion of sponsorship banners at
docs.fp.o
People present (lines said)
randomuser` (72)
sgordon (39)
Sparks_too (12)
iambryan (9)
zodbot (6)
Sparks (4)
bcotton (4)
nb (1)
chuckf (1)
pkovar (1)
- --------Full logs at http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-25/fedora_docs_project_meeting_https:fedoraproject.orgwikidocs_project_meetings.2013-02-25-14.01.log.txt
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRNLeYAAoJEL1wZM0+jj2ZM3YIAIBfjyOnXet6VuncOYisYIbB
iteX9UDaqfEdG3yy+/0tgQEisakaeiVrFYMXIZb9v65WyNFnXkTXenxAZdywYlBU
CyaKhna5v2OECyJkH+S/0DuHUmI2xWP2X1gF0r19wqQ2vY6/L2xdpdhpKhim3YXI
YWKFBRBfo1x6MNuEJ9K+N2xWLDhoHjRkWLJPXr22cetxEsSklfqy5rG0lYleDreQ
346rFf7/ftumpLlY45M+5b/wMDsLshPg5OxvNMsdSp1/GVtl8ORhMpoI3w5ZbGCl
50ZnIXyGi16x+ewyOtlWTpZIB19/8RKs79qo4//V3PhKz/ZlqOMyKzZl+iIh0nE=
=ekgV
-----END PGP SIGNATURE-----
Hi all,
The IRC meeting minutes tonight are available at here[1]. Thanks
everyone for attending the meeting.
In the meeting we mainly talked about offline gather up in Beijing in
March and some translation issues. The next IRC meeting will be held on
next Friday (2013-03-08). Please come and join the discussion if you
can!
[1]
http://meetbot.fedoraproject.org/fedora-zh/2013-03-01/fzug_irc_meeting_2013…
Meeting started by alick at 12:02:18 UTC (full logs).
Meeting summary
点名 (alick, 12:05:04)
检查之前会议的actions (alick, 12:11:43)
lovenemesis (Tommy) 已经贴出调查结果了 (alick, 12:13:42)
http://lists.fedoraproject.org/pipermail/ambassadors/2013-February/020900.h…
(alick, 12:17:15)
线下活动 (alick, 12:22:41)
IDEA: 3月份搞一次线下活动 (alick, 12:23:41)
http://lisp.org.cn/wiki/lisp/event/2013-meetup (alick, 12:32:21)
IDEA: 有一两个talk就行 (alick, 12:37:14)
ACTION: cicku ask BJGUG about offline events in March (alick,
12:45:07)
翻译问题讨论 (alick, 12:45:18)
https://fedorahosted.org/fedora-apac/ticket/56 ? (kital, 12:48:37)
Meeting ended at 13:03:31 UTC (full logs).
Action items
cicku ask BJGUG about offline events in March
People present (lines said)
alick (109)
zsun (40)
kingheaven (22)
microcai (20)
zodbot (18)
BadGirl (7)
Robin_cheese_Lee (6)
kital (5)
xiyoulaoyuanjia (1)
CyrusYzGTt (0)
Generated by MeetBot 0.1.4.
--
Alick
Fedora 18 (Spherical Cow) user
https://fedoraproject.org/wiki/User:Alick