meetingminutes August 2014

meetingminutes@lists.stg.fedoraproject.org

22 participants
38 discussions

APAC meeting summary/minutes | August 30, 2014 - 04:00 UTC
by Sarup Banskota 30 Aug '14

30 Aug '14

Hello everyone, We had a regular APAC bi-weekly meeting, where we went over updates and tickets by contributors from our region. I've included links to the minutes & logs in this email, please have a look at them. Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-08-30/apac_ambassadors… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-08-30/apac_ambassadors… Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-08-30/apac_ambassadors… Thanks, have a great day! Sarup

1 0

Summary of EPEL Meeting 2014-08-29
by Stephen John Smoogen 29 Aug '14

29 Aug '14

======================== #epel: EPEL (2014-08-29) ======================== Meeting started by smooge at 16:00:13 UTC. The full logs are available athttp://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014… . Meeting summary --------------- * meet and greets (smooge, 16:01:04) * meet and greets (smooge, 16:01:31) * Agenda (smooge, 16:04:22) * 1) Meet and Greets (smooge, 16:04:38) * 2) Agenda (smooge, 16:04:45) * 3) EPEL 7 out of beta (smooge, 16:04:54) * 4) EPEL.<stuff> discussion (smooge, 16:05:06) * 5) Open Flood (smooge, 16:05:17) * 6) End meeting (smooge, 16:05:24) * EPEL 7 out of beta (smooge, 16:05:37) * Bodhi needs to get some work done still (smooge, 16:07:20) * updates do not work correctly yet but will soon. (smooge, 16:07:31) * EPEL.<stuff> discussion (smooge, 16:17:22) * ACTION: Jeff_S and dgilmore and others to discuss .rpmsave issue (smooge, 16:20:11) * AGREED: EPEL short term governance team members: smooge, nirik, dgilmore, and Evolution (smooge, 16:29:35) * moving discussion of governance structure and policy to mailing list. Votes to finalize anything that feels need a vote will be next weeks meeting (smooge, 16:49:13) * Open Flood. (smooge, 16:49:47) * ACTION: Add time in testing to policy discussion on mailing list (smooge, 16:57:59) * Thanks for coming everyone. See you on the list. (smooge, 17:13:57) Meeting ended at 17:14:12 UTC. Action Items ------------ * Jeff_S and dgilmore and others to discuss .rpmsave issue * Add time in testing to policy discussion on mailing list Action Items, by person ----------------------- * dgilmore * Jeff_S and dgilmore and others to discuss .rpmsave issue * Jeff_S * Jeff_S and dgilmore and others to discuss .rpmsave issue * **UNASSIGNED** * Add time in testing to policy discussion on mailing list People Present (lines said) --------------------------- * smooge (97) * Jeff_S (43) * dgilmore (42) * nirik (33) * kbsingh (31) * maxamillion (26) * avij (8) * bstinson (6) * zodbot (3) * orionp (2) * Ussat (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Minutes: http://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-0… Minutes (text): http://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-0… Log: http://meetbot.fedoraproject.org/epel/2014-08-29/epel_weekly_meeting.2014-0… -- Stephen J Smoogen.

1 0

Re: [FZH] Fedora Chinese Meeting Minutes (2014-08-29)
by Zamir Sun 29 Aug '14

29 Aug '14

Forward to the meetingminutes list 于 2014/8/29 23:29, Ray Dobie 写道: > Hi all, > > The IRC meeting minutes today are available at the links below. > Thanks everyone for attending the meeting. > In the meeting we mainly talked about FUDCon （reimbursement, Videos, > Event Reports, Slides，Feedback Survey，Fedora Badge ）, fedocal , Fedora > 21 L10N, Ambassadors and upcoming offline events. Please review the > proposed ideas and actions. > > > The next IRC meeting will be held on next Friday (2014-09-05). > Please come and join the discussion if you can! > > - Minutes: http://meetbot.fedoraproject.org/fedora-zh/2014-08-29/fedora-zh.2014-08-29-… > > - Minutes (text): > http://meetbot.fedoraproject.org/fedora-zh/2014-08-29/fedora-zh.2014-08-29-… > > - Log: http://meetbot.fedoraproject.org/fedora-zh/2014-08-29/fedora-zh.2014-08-29-… > > ================== > #fedora-zh Meeting > ================== > > > Meeting started by alick at 13:03:19 UTC. The full logs are available > athttp://meetbot.fedoraproject.org/fedora-zh/2014-08-29/fedora-zh.2014-08-2… > . > > > > Meeting summary > --------------- > * Roll Call 报到 (alick, 13:03:37) > > * FUDCon Reimbursement (alick, 13:13:53) > * ACTION: alick ask about FAD reimbursement (alick, 13:15:37) > > * FUDCon Videos (alick, 13:16:13) > * LINK: https://fedorahosted.org/videos/report/1 (alick, 13:17:12) > * LINK: https://fedorahosted.org/videos/ticket/3 (alick, 13:17:42) > * LINK: http://vimeo.com/fedoraproject (alick, 13:21:07) > * LINK: https://www.youtube.com/fedoraproject (alick, 13:21:24) > > * FUDCon Event Reports (alick, 13:21:46) > * LINK: > https://wp-awesome.rhcloud.com/2014/08/23/fudcon-apac-2014-report/ > (alick, 13:22:20) > > * FUDCon Slides (alick, 13:23:11) > * LINK: https://fedoraproject.org/wiki/FUDCon:Beijing_2014#Schedule > (alick, 13:23:32) > * ACTION: zsun alick complete the slides links of GNOME.Asia and > FUDCon APAC (alick, 13:25:43) > > * FUDCon Feedback Survey (alick, 13:27:59) > * ACTION: alick send tiansworld coscup's survey report as reference > (alick, 13:29:26) > * ACTION: tiansworld make a better survey report (alick, 13:29:33) > > * Fedora Badge for FUDCon (alick, 13:30:09) > * LINK: https://fedoraproject.org/wiki/FUDCon:Beijing_2014/Badge > (alick, 13:30:20) > * ACTION: alick notify badge deadline on weibo (alick, 13:31:50) > > * fedocal (Fedora Calendar) (alick, 13:32:06) > * LINK: https://fedorahosted.org/fedocal/ticket/131 (alick, > 13:32:22) > > * Offline Events (alick, 13:34:33) > * LINK: https://fedoraproject.org/wiki/Hanoi_SFD_2014 (alick, > 13:34:54) > * LINK: http://wiki.softwarefreedomday.org/2014/China/ (alick, > 13:35:59) > > * Fedora 21 L10N (alick, 13:42:18) > * LINK: > https://fedorapeople.org/groups/schedule/f-21/f-21-trans-tasks.html > (alick, 13:42:32) > * i18n test day - 2nd September 2014 (Tuesday) [1] (alick, 13:47:22) > * l10n test day - 9th September 2014 (Tuesday) [2] (alick, > 13:47:36) > > * Ambassadors (alick, 13:50:51) > * 就是 noriko > 在列表发的邮件。我转发的目的是告诉大家，有机会去测试zanata，有bug往上报。至于最后的决定，什么都不知道的话决定就是盲目的。 > (tiansworld, 13:57:08) > * LINK: https://fedoraproject.org/wiki/User:Tvvocold (alick, > 14:00:59) > * LINK: http://googlo.cf (tvvocold, 14:06:10) > * LINK: https://fedoraproject.org/wiki/Zh?rd=Zh/ (alick, 14:07:49) > * LINK: http://paste.fedoraproject.org/ (alick, 14:09:45) > * LINK: https://fedoraproject.org/wiki/User:Cicku (alick, 14:13:10) > > Meeting ended at 14:18:50 UTC. > > > > > Action Items > ------------ > * alick ask about FAD reimbursement > * zsun alick complete the slides links of GNOME.Asia and FUDCon APAC > * alick send tiansworld coscup's survey report as reference > * tiansworld make a better survey report > * alick notify badge deadline on weibo > > > > > Action Items, by person > ----------------------- > * alick > * alick ask about FAD reimbursement > * zsun alick complete the slides links of GNOME.Asia and FUDCon APAC > * alick send tiansworld coscup's survey report as reference > * alick notify badge deadline on weibo > * tiansworld > * alick send tiansworld coscup's survey report as reference > * tiansworld make a better survey report > * zsun > * zsun alick complete the slides links of GNOME.Asia and FUDCon APAC > * **UNASSIGNED** > * (none) > > > > > People Present (lines said) > --------------------------- > * alick (122) > * zsun (36) > * tvvocold (35) > * zodbot (31) > * BadGirl (20) > * endle (12) > * tonghuix (8) > * KAIO (6) > * isyangxin (3) > * tiansworld (2) > * zhtx (1) > * xielingyun__ (1) > * biergaizi (0) > > > > > Generated by `MeetBot`_ 0.1.4 > > .. _`MeetBot`: http://wiki.debian.org/MeetBot > -- > Fedora中文郵件列表：https://admin.fedoraproject.org/mailman/listinfo/chinese > -- Zamir SUN zsun(a)fedoraproject.org zsun in #fedora-zh #openshift on freenode.net

1 0

FAMNA Meeting Minutes 8-28-2014
by Andrew Ward 28 Aug '14

28 Aug '14

All, Please read the meeting minutes from our last meeting. Summarizing the upcoming events and a couple of new events that that came up. Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-08-29/famna.2014-08-29… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-08-29/famna.2014-08-29… Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-08-29/famna.2014-08-29… v/r -- Andrew Ward award3535(a)fedoraproject.org award3535(a)tds.net award3535(a)gmail.com

1 0

Fedora Cloud (Atomic) & Infra meeting 26 August 2014
by Joe Brockmeier 28 Aug '14

28 Aug '14

Apologies for being tardy in sending this out. =============== #atomic Meeting =============== Meeting started by jzb at 20:09:50 UTC. The full logs are available at http://meetbot.fedoraproject.org/atomic/2014-08-26/atomic.2014-08-26-20.09.… . Meeting summary --------------- * F21 composes (jzb, 20:10:17) * looks like there is a TC4 for Atomic (jzb, 20:10:42) * LINK: http://dl.fedoraproject.org/pub/alt/stage/21-Alpha-TC4/Cloud/Images/x86_64/ (jzb, 20:10:47) * ACTION: nirik when we have a viable Atomic TC nirik will make sure it's announced. (jzb, 20:13:44) * ACTION: jzb once we have a viable Atomic TC jzb will try to arrange a test day (jzb, 20:14:12) * ACTION: jzb research test case possibilities for Atomic (jzb, 20:21:00) * any new business? (jzb, 20:24:35) Meeting ended at 20:29:20 UTC. Action Items ------------ * nirik when we have a viable Atomic TC nirik will make sure it's announced. * jzb once we have a viable Atomic TC jzb will try to arrange a test day * jzb research test case possibilities for Atomic Action Items, by person ----------------------- * jzb * jzb once we have a viable Atomic TC jzb will try to arrange a test day * jzb research test case possibilities for Atomic * nirik * nirik when we have a viable Atomic TC nirik will make sure it's announced. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jzb (37) * dustymabe (11) * nirik (10) * stickster (4) * zodbot (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Summary/Minutes from today's Fedora Infrastructure meeting (2014-08-28)
by Kevin Fenzi 28 Aug '14

28 Aug '14

============================================ #fedora-meeting: Infrastructure (2014-08-28) ============================================ Meeting started by nirik at 18:00:11 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-08-28/infrastructure.2… . Meeting summary --------------- * aloha (nirik, 18:00:11) * New folks introductions and Apprentice tasks. (nirik, 18:01:38) * Freeze reminder (nirik, 18:12:14) * Applications status / discussion (nirik, 18:13:52) * fedocal, pkgdb2 bugfix releases this week (nirik, 18:17:16) * nuancier release with lots of changes. (nirik, 18:17:27) * fedimg work ongoing (nirik, 18:17:39) * Sysadmin status / discussion (nirik, 18:23:42) * pkgs01.stg now in ansible and running rhel7 (nirik, 18:24:53) * fixed a bunch of hosts monday that are still in puppet that were stuck. ;( (nirik, 18:25:52) * nagios/alerts recap (nirik, 18:27:39) * Upcoming Tasks/Items (nirik, 18:33:17) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 18:33:17) * Open Floor (nirik, 18:36:03) Meeting ended at 18:39:52 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (70) * pingou (32) * oddshocks (18) * danielbruno (7) * mirek-hm (7) * lanica (6) * Neldogz (5) * zodbot (5) * smooge (3) * vgologuz (3) * threebean (2) * lmacken (1) * bwood09 (1) * danofsatx (1) * relrod (1) * puiterwijk (0) * abadger1999 (0) * mdomsch (0) * dgilmore (0) -- 18:00:11 <nirik> #startmeeting Infrastructure (2014-08-28) 18:00:11 <zodbot> Meeting started Thu Aug 28 18:00:11 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:11 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:11 <nirik> #meetingname infrastructure 18:00:11 <zodbot> The meeting name has been set to 'infrastructure' 18:00:11 <nirik> #topic aloha 18:00:11 <nirik> #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:00:11 <zodbot> Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:00:17 * pingou here 18:00:21 * bwood09 is here 18:00:32 * oddshocks here 18:00:34 * danielbruno here 18:00:35 * lmacken 18:00:51 * mirek-hm is here 18:00:58 <Neldogz> neldogz is here 18:01:30 * threebean is here 18:01:36 <nirik> cool. Lets go ahead and dive on in then... 18:01:38 <nirik> #topic New folks introductions and Apprentice tasks. 18:01:45 <nirik> any new folks want to intrduce themselves? 18:01:53 <nirik> or apprentices with questions/comments/ideas? 18:02:05 <smooge> here 18:02:21 <nirik> hey smooge 18:02:31 <danielbruno> I have some questions about the Apprentice tasks 18:02:35 * danofsatx present for accounting purposes 18:02:38 <nirik> danielbruno: fire away. ;) 18:02:41 <Neldogz> hello by any chance are there any openings in the Fedora Infrastructure team for volunteers? I have a few hours a week that I would love to dedicate to this team and the Fedora Project. 18:03:02 * lanica is here for the infra meeting. 18:03:29 <nirik> Neldogz: see http://fedoraproject.org/wiki/Infrastructure/GettingStarted and yes, always looking for folks to help out... are you more interested in sysadmin tasks? or application development? 18:03:30 <danielbruno> so, I read the documentations.. and I would like to know a good point to start 18:03:45 <danielbruno> if I have to ask in the channel 18:04:30 <Neldogz> hi nirik; mostly in systems administration. I do have experience with RHEL and Fedora. I would love to learn more about how these work in a corporate environment. I am pretty good with monitoring, documentation and up for anythign that is needed. 18:04:34 <nirik> danielbruno: well, best bets are to look at the easyfix tickets and pick something you are interested in and start working on it... and/or hang out in our channels and when you see an interesting to you discussion chime in and ask if you can help out. ;) 18:05:14 <nirik> if there's specific areas you are interested in we might be able to come up with some more targeted things... :) 18:05:38 <danielbruno> great! :) 18:05:45 <nirik> Neldogz: ok, welcome. we have an apprentice program (see link off that getting started page) if you are interested in it, I can add you after the meeting... see me in #fedora-admin. 18:06:06 <Neldogz> great! would love to join fi-apprentice 18:06:12 <Neldogz> see you in #fedora-admin 18:06:27 <nirik> cool. ;) 18:06:58 <nirik> I will also see about filing some more easyfix tickets... haven't done any new ones for a bit. 18:07:28 <danielbruno> nirik, I have looked at the easyfix and i'm interested in some tasks 18:07:28 <vgologuz> hi all 18:08:08 <nirik> danielbruno: cool. Do comment in those tickets and/or ask the person who filed them if they are around on irc... 18:08:15 <nirik> morning vgologuz 18:08:34 <vgologuz> I've recently joined Copr project, and would like (in some time) to learn about fedora infrastructure 18:08:41 <danielbruno> nirik, ok.. I will :) 18:09:01 <nirik> vgologuz: great. :) I can also add you to our apprentice group if you like... see me after the meeting in #fedora-admin. 18:09:37 <vgologuz> nirik, great ) 18:10:05 <mirek-hm> I will try to learn vgologuz as much as I know about ansible.git, playbooks and FedoraCloud 18:10:25 <mirek-hm> s/learn/teach/ 18:12:04 <nirik> great. 18:12:06 * nirik just had a laptop lockup. sorry for the delay. 18:12:14 <nirik> #topic Freeze reminder 18:12:44 <nirik> So, just a reminder that we are freeze now. Any frozen hosts should not be modified without a patch with 2 +1s from sysadmin-main or releng. 18:12:58 * pingou was the first one to forgot about it 18:13:04 <pingou> it has been so long since the last one :) 18:13:37 <nirik> yeah, I know. ;) 18:13:44 <nirik> see the mail on the list for more details. ;) 18:13:52 <nirik> #topic Applications status / discussion 18:14:04 <nirik> any applications news/status this week? 18:14:08 <lanica> Everything is frozen besides stg? 18:14:10 <lanica> Sorry for the lateness 18:14:34 <pingou> new fedocal released earlier this week, bug fix mainly 18:14:50 <pingou> new pkgdb2 released as well, bugfix again 18:14:59 <pingou> new nuancier released, quite some changes on that one :) 18:15:15 <oddshocks> Fedimg is installed on fedimg01.stg. Working out some Comcast internet problems this moment (I'm currently tethered to my phone 'net), but once they're resolved I'm gonna find out if it's properly doing the thing 18:15:20 <pingou> and elections just got a new election type: irc which offers +1/0/-1 18:15:29 <pingou> work from nerdsville 18:15:35 <oddshocks> (finally got permissions stuff with my sudo access to fedimg01.stg worked out.. I think) 18:15:47 <oddshocks> /s/i think// 18:16:01 <pingou> oddshocks: ansible? 18:16:50 <nirik> lanica: there's a script in ansible called 'freezelist' it will show the ones frozen/not. 18:17:02 <nirik> there are some non stg hosts that also aren't frozen. 18:17:03 <lanica> nirik: thanks! 18:17:16 <nirik> #info fedocal, pkgdb2 bugfix releases this week 18:17:27 <nirik> #info nuancier release with lots of changes. 18:17:39 <nirik> #info fedimg work ongoing 18:17:41 <oddshocks> pingou: what about it? I'm not 100% clear on what the issue was, nirik and smooge resolved it for me 18:18:07 <oddshocks> pingou: i didn't install fedimg with ansible yet, if that's what you're asking. just `rpm -i`'d the rpm 18:18:19 <pingou> oddshocks: that was my question :) 18:18:21 * relrod checks in late, sorry 18:18:27 <oddshocks> I need to figure this ansible stuff out though. I have little to no experience with it sad to say 18:18:31 <oddshocks> relrod: hey 18:18:39 <pingou> oddshocks: installing it via a playbook might have solved the problem there :) 18:18:40 <nirik> oddshocks: we can walk you through it. 18:18:45 <oddshocks> nirik: awesome, thanks :) 18:18:47 <oddshocks> pingou: ahh 18:19:00 <smooge> oddshocks, none of us know how it works. I have 3 voudou dolls which help me 18:19:05 <oddshocks> nirik: pingou: TBH I'm not even 100% clear on which things I should be doing with ansible, and what it can do for me 18:19:06 <pingou> oddshocks: feel free to ping wrt ansible 18:19:09 <oddshocks> smooge: haha 18:19:14 <oddshocks> pingou: cool 18:19:19 <pingou> oddshocks: install rpm, configuration file 18:19:41 <pingou> oddshocks: basically everything that's needed to drop the VM and build a new one working out-of-the-box 18:20:05 <pingou> oddshocks: getting one of those woudou dolls from smooge is a good idea ;-) 18:20:28 <nirik> basically if we had to reinstall the machine today, ansible would let us get it back to the same exact working state. 18:20:33 <oddshocks> pingou: ah that makes sense. 18:20:44 <oddshocks> nirik: right, so yeah just installing the fedimg rpm and putting fedimg.cfg in /etc/ 18:20:54 <pingou> nirik: are we doing cloud on kvm? :) 18:20:55 <oddshocks> and likely starting the fedimg relay if it doesn't do so already 18:21:10 <oddshocks> nirik: I'll also ping you soon this week about internal openstack uploading if you'd like 18:21:13 <pingou> oddshocks: sounds nice and simple, shouldn't be too hard to do with ansible :) 18:21:17 <nirik> oddshocks: sounds good. 18:21:24 <nirik> pingou: our cloud uses kvm, yes? 18:21:55 <mirek-hm> yes, OS use kvm 18:21:56 <pingou> nirik: I meant more our stg/prod boxes, we're always "ready" to turn one down and rebuild one, sounds cloudy :) 18:22:16 <nirik> pingou: kinda, but more persistent I think... 18:22:29 <pingou> hopefully :) 18:22:35 <nirik> and more decentralized 18:22:48 <pingou> that's very true 18:23:06 <nirik> any other application news? 18:23:24 <nirik> I'm gonna try and ping abompard next week when he's back about moving more forward on hyperkitty 18:23:35 * pingou looks forward 18:23:42 <nirik> #topic Sysadmin status / discussion 18:23:50 <nirik> lets see... 18:24:19 <nirik> I got bochecha's pkgs migration to ansible commited and made a new pkgs01.stg 18:24:31 <nirik> There's more work we need to do on it, but I think it's coming along nicely. 18:24:53 <nirik> #info pkgs01.stg now in ansible and running rhel7 18:25:08 <pingou> w/ it we're moving to gitolite3 18:25:39 * nirik nods. 18:25:40 <pingou> is that the remaining work you were thinking about or are there also other things? 18:25:52 <nirik> #info fixed a bunch of hosts monday that are still in puppet that were stuck. ;( 18:26:01 <nirik> yeah, mostly gitolite3 and lots of testing. 18:26:08 <pingou> +1 on testing 18:26:29 <nirik> cgit isn't working right for some reason yet. 18:26:30 <pingou> note: the gitolite configuration cron/task isn't on (or working) atm 18:27:02 <nirik> yeah. 18:27:25 <nirik> So, given the freeze we can work on stg stuff and documentation and planning. ;) 18:27:30 <pingou> \ó/ 18:27:39 <nirik> #topic nagios/alerts recap 18:27:40 <mirek-hm> I proceed with Openstack installatation. networking is hopefully fixed (although after reset it need manual intervention via console :( ) and I'm currently fighting with one problem in packstack. 18:27:59 <nirik> mirek-hm: great. ;) so it's getting close? 18:28:05 <mirek-hm> yes 18:28:19 <pingou> I've been working with releng to drop the pkgdb2branch script 18:28:20 <mirek-hm> it is my priority now 18:28:59 <nirik> awesome. we still need to hook in storage... but hopefully that won't be too bad 18:29:12 <pingou> the idea is to replace that script by another that checks all git for their branches vs the branches they should have according to pkgdb and adjust the git accordingly 18:29:30 <pingou> so that's one more thing changing with the move of pkgs01 to el7 :) 18:30:06 <nirik> .tiny https://admin.fedoraproject.org/nagios/cgi-bin//summary.cgi?report=1&displa… 18:30:14 <zodbot> nirik: http://tinyurl.com/m3v3a5x 18:30:59 <nirik> most of our alerts continue to be network related... but I've found that it's likely openvpn getting saturated. 18:31:13 <nirik> I've not isolated what traffic is causing it yet, but will keep looking. 18:31:21 <pingou> threebean: and I are thinking about giving a trial for datanommer/datagrepper on a mongodb backend, that might help with datagrepper's response time 18:32:17 <nirik> ok. I wonder also if moving that db to rhel7 and newer postgres could help 18:32:29 <pingou> could be also 18:33:17 <nirik> #topic Upcoming Tasks/Items 18:33:17 <nirik> https://apps.fedoraproject.org/calendar/list/infrastructure/ 18:33:26 <nirik> anything upcoming anyone would like to schedule or note? 18:34:00 <smooge> not from me 18:34:10 <threebean> pingou: yeah, we should really follow up with yograterol on that. he has actual experience with mongo and is interested in helping with FI 18:34:57 <nirik> we should make sure we know what we are getting into before we move to it, but trying things seems like a great first step . 18:35:30 <pingou> threebean: +1 but I haven't seen him on irc recently :( 18:36:03 <nirik> #topic Open Floor 18:36:10 <nirik> anyone have anything for open floor? 18:36:20 <nirik> questions, ideas, favorate cartoons? 18:37:38 <oddshocks> I like The Boondocks 18:37:42 <lanica> noc01/nagios mod_auth_openid issue -- looks to be a cobination of a bug in mod_auth_openid and libopkele. One patch, already in existance for mod_auth_openid fixes part of the issue. Once I can find some time, I can do some more testing and validate the fix for libopkele. I probably need to submit a bug report for libopkele if it does not already exist. 18:37:50 <lanica> DuckTales perhaps? 18:38:10 <nirik> lanica: awesome. Thanks for tracking that down... it's an anoying bug. ;) 18:38:17 * nirik likes bob's burgers. 18:39:07 <nirik> alright, will close out in a minute if nothing more. 18:39:49 <nirik> Thanks for coming everyone! 18:39:52 <nirik> #endmeeting

1 0

Summary/Minutes from today's irc support sig meeting (2014-08-28)
by Kevin Fenzi 28 Aug '14

28 Aug '14

============================================= #fedora-meeting: IRC Support SIG (2014-08-28) ============================================= Meeting started by nirik at 17:00:25 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-08-28/irc-support-sig.… . Meeting summary --------------- * init process (nirik, 17:00:25) * Week in review (nirik, 17:03:16) * Open Floor (nirik, 17:06:55) Meeting ended at 17:10:46 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (19) * Sonar_Gal (5) * zodbot (3) * Neldogz (3) * otaylor (1) -- 17:00:25 <nirik> #startmeeting IRC Support SIG (2014-08-28) 17:00:25 <zodbot> Meeting started Thu Aug 28 17:00:25 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:25 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:25 <nirik> #meetingname irc-support-sig 17:00:25 <zodbot> The meeting name has been set to 'irc-support-sig' 17:00:25 <nirik> #topic init process 17:00:51 * Sonar_Gal 17:00:53 <nirik> anyone around for a quick irc support sig meeting? 17:02:14 <Sonar_Gal> nirik, looks like everyone is napping 17:02:26 <nirik> nap sure sounds good. ;) 17:02:33 <Neldogz> hello everyone 17:02:39 <nirik> hey Neldogz 17:03:14 <nirik> I guess lets do a quick meeting... 17:03:16 <nirik> #topic Week in review 17:03:32 <nirik> anyone have anything from the previous few weeks? common problems peoepl are seeing, etc? 17:03:45 <Sonar_Gal> Same as any other week 17:04:24 <nirik> yeah, nothing too much stood out, aside from a user with lots and lots of issues who finally did get helped... but many hours of effort. ;) 17:06:51 <nirik> alrighty 17:06:55 <nirik> #topic Open Floor 17:07:01 <nirik> anything else anyone would like to bring up? 17:07:39 <otaylor> /part 17:08:04 <nirik> we may want to move to just having meetings if there's something to discuss. ;) 17:08:07 <Sonar_Gal> nothing I can think of 17:08:13 <Neldogz> By any chance are there any openings in the Fedora Infrastructure team for volunteers? I have a few hours a week that I would love to dedicate to this team and the Fedora Project. 17:08:36 <nirik> Neldogz: absolutely, but that meeting is not for about 52minutes... at 18UTC. ;) 17:08:45 <Neldogz> got it thank you! 17:09:14 <nirik> :) 17:09:58 <Sonar_Gal> nirik, I agree hasn't been busy enough or problems to have weekly. May want to see about a monthly meeting then if needed can do a every 2 week 17:10:11 <nirik> Sonar_Gal: yeah, thats a good plan. 17:10:43 <nirik> alright. thanks for coming Sonar_Gal. :) (and Neldogz ) 17:10:46 <nirik> #endmeeting

1 0

Workstation Abridged Meeting Minutes 2014-08-27
by Josh Boyer 27 Aug '14

27 Aug '14

Hi All, Below are some abridged meeting minutes from today's meeting. Due to Freenode netsplitting several times, there are fragments of conversation in the logs and it was a very confusing meeting overall. While this wasn't any fault of the WG's or Fedora, we do apologize and hopefully next week will come together better. We did manage, however briefly, to come together to agree on adopting the proposed guidelines for Apps and Launchers for Workstation. For now these are Workstation specific an used as guidelines for picking default apps. There is a strong desire to see how much commonality can be found across the project for this, so I'll start a separate thread to kick off that discussion. If anyone has any questions, please let us know. We'll be doing an out-of-cycle meeting next Wednesday at the same time and place to address some of the other items. In the meantime, we will be discussing the higher priority issues on the list. josh =========================================== #fedora-meeting: Fedora Workstation Meeting =========================================== Meeting started by jwb at 15:00:18 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-08-27/workstation.2014… . Meeting summary --------------- * init (jwb, 15:00:19) * Apps and Launchers Guidelines (jwb, 15:03:49) * LINK: https://fedoraproject.org/wiki/User:Elad/Draft_app_guidelines (jwb, 15:04:13) * LINK: https://people.gnome.org/~tobiasmue/hig3/icons-and-artwork.html#application… (aday, 15:17:54) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1131248 -- bug concerning some issues on java packages (stickster, 15:18:29) * AGREED: adopt guidelines for Workstation (jwb, 15:46:33) * jwb to start discussion with other products/WGs (jwb, 15:46:48) Meeting ended at 15:49:07 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * elad661 (61) * jwb (58) * cwickert (39) * cschalle (29) * kalev (17) * stickster (14) * juhp_ (14) * mclasen (12) * aday (9) * drago01 (9) * otaylor (8) * zodbot (6) * mclasen_ (2) * sgallagh (2) * nirik (1) * hadess (1) * ryanlerch (0) * juhp (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Sumary/Minutes from today's FESCo Meeting (2014-08-27)
by Kevin Fenzi 27 Aug '14

27 Aug '14

=================================== #fedora-meeting: FESCO (2014-08-27) =================================== Meeting started by nirik at 17:00:10 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-08-27/fesco.2014-08-27… . Meeting summary --------------- * init process (nirik, 17:00:10) * #1178 Fedora 21 scheduling strategy (nirik, 17:04:02) * LINK: https://fedorahosted.org/fesco/ticket/1178 (nirik, 17:04:02) * #1322 F21 Changes - Progress on Changes Freeze (nirik, 17:07:35) * LINK: https://fedorahosted.org/fesco/ticket/1322 (nirik, 17:07:35) * will update changes for next meeting and see if any are in danger. (nirik, 17:10:34) * server database role probibly will be retargeted at f22 (nirik, 17:10:46) * #1332 retire orphan packags after 4 weeks instead of once per release (nirik, 17:12:26) * LINK: https://fedorahosted.org/fesco/ticket/1332 (nirik, 17:12:26) * AGREED: allow retiring of non stable release packages after they are orphaned for 6 weeks. (+7,0,0) (nirik, 17:26:33) * #1336 - 32 bit ppc support (nirik, 17:26:42) * LINK: https://fedorahosted.org/fesco/ticket/1336 (nirik, 17:26:43) * LINK: https://fedoraproject.org/wiki/Architectures (nirik, 17:35:57) * AGREED: any arch that wants to call itself fedora needs to build up and host their own infrastructure, along with building up enough packages to show that they can do a working remix of fedora. Then request that FESCo consider them as a secondary arch (+7,0,0) (nirik, 17:41:06) * Next weeks chair (nirik, 17:41:15) * sgallagh to chair next week (nirik, 17:44:48) * Open Floor (nirik, 17:45:21) * LINK: http://pootle.translatehouse.org was mentioned... but anyhow, I am ok with them doing what they think is best. The history with transifex makes me sad to be moving things... oh well. (nirik, 17:50:28) * AGREED: FESCo is fine with https://fedoraproject.org/wiki/L10N_Move_To_Zanata ; please schedule the upstream project migration to happen after F21 final release is approved. (+7,0,0) (nirik, 17:53:16) Meeting ended at 18:01:30 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * nirik (96) * dgilmore (50) * jwb (44) * mitr (31) * sgallagh (25) * thozza (23) * t8m (20) * jreznik_ (9) * zodbot (8) * kalev (8) * mmaslano (0) * mattdm (0) -- 17:00:10 <nirik> #startmeeting FESCO (2014-08-27) 17:00:10 <zodbot> Meeting started Wed Aug 27 17:00:10 2014 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:10 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:00:10 <nirik> #meetingname fesco 17:00:10 <nirik> #chair dgilmore jwb kalev mattdm mitr mmaslano nirik sgallagh t8m thozza 17:00:10 <nirik> #topic init process 17:00:10 <zodbot> The meeting name has been set to 'fesco' 17:00:10 <zodbot> Current chairs: dgilmore jwb kalev mattdm mitr mmaslano nirik sgallagh t8m thozza 17:00:32 * sgallagh is doing double-duty in the blocker bugs meeting right now 17:00:34 <kalev> hello hello 17:01:07 <thozza> hy 17:01:09 <thozza> hi 17:01:23 <jwb> i'm in a meeting i can't get out of. apologies, it was supposed to be over but i will be late 17:02:03 <mitr> Hello 17:02:48 * nirik will wait another min for more folks to arrive 17:03:50 <nirik> ok, I guess we have quorum... barely. ;) 17:04:02 <nirik> #topic #1178 Fedora 21 scheduling strategy 17:04:02 <nirik> .fesco 1178 17:04:02 <nirik> https://fedorahosted.org/fesco/ticket/1178 17:04:04 <zodbot> nirik: #1178 (Fedora 21 scheduling strategy) – FESCo - https://fedorahosted.org/fesco/ticket/1178 17:04:08 <nirik> so, we should be going into freeze today. 17:04:19 <nirik> I see jreznik_ already bumped the schedule a week. 17:04:34 <nirik> Do we want to do anything here? or leave it as it is? 17:04:34 * jreznik_ is here 17:05:05 <jreznik_> nirik: yeah, I bumped it - it was the only way how to make sure we have at least somehow correct dates on web (it's automatically parsed) 17:05:13 <jreznik_> do we need any other corrections? 17:05:28 <t8m> Hi all, I am sorry for being late 17:05:29 <jreznik_> I don't think anybody raised any big concern 17:05:59 <nirik> yeah, I'm ok with it as it is... note that more slipping would drop us into thanksgiving for release... 17:06:01 <nirik> (in the us) 17:07:18 <nirik> ok, will move on then if no one has changes here... 17:07:35 <nirik> #topic #1322 F21 Changes - Progress on Changes Freeze 17:07:35 <nirik> .fesco 1322 17:07:35 <nirik> https://fedorahosted.org/fesco/ticket/1322 17:07:37 <zodbot> nirik: #1322 (F21 Changes - Progress on Changes Freeze) – FESCo - https://fedorahosted.org/fesco/ticket/1322 17:07:40 <jreznik_> I'm aware of it and there's possibility we will collide with thanksgiving 17:07:42 <nirik> jreznik_: any news here? 17:08:00 <jreznik_> nirik: no news but as we are now frozen, I'll do another round of nagging 17:08:14 <jreznik_> I'm just updating ChangeSet with changes 17:08:16 * dgilmore is here 17:08:25 <nirik> anything we need to punt to f22? 17:08:56 <sgallagh> nirik: Arguably this would be the point where we punt the DB Role for Server. 17:09:17 <nirik> yeah, I just have had no time to look into it... ;( 17:09:18 <jreznik_> sgallagh: if yes, let me know 17:09:21 <nirik> I'd be ok doing that. 17:09:36 <nirik> which of course doesn't mean we can't work on it... 17:10:00 <jreznik_> with vacations, I hadn't much time for changes, will make sure it's in a good shape for the next week 17:10:19 <nirik> ok. 17:10:21 <sgallagh> Well, it's not going to be on the Alpha DVD, that's for sure. 17:10:34 <nirik> #info will update changes for next meeting and see if any are in danger. 17:10:46 <nirik> #info server database role probibly will be retargeted at f22 17:11:05 <nirik> anything else here today? 17:12:26 <nirik> #topic #1332 retire orphan packags after 4 weeks instead of once per release 17:12:26 <nirik> .fesco 1332 17:12:26 <nirik> https://fedorahosted.org/fesco/ticket/1332 17:12:28 <zodbot> nirik: #1332 (retire orphan packags after 4 weeks instead of once per release) – FESCo - https://fedorahosted.org/fesco/ticket/1332 17:12:34 <nirik> so there was some discussion about this on list... 17:12:40 <nirik> but it didn't seem to reach a consensus. 17:13:22 <dgilmore> main reason we dont do it more often traditionally has been that we can not remove things from the GA tree 17:13:34 <dgilmore> which make some of it really difficult to implement 17:13:47 <mitr> Retiring anything from released branches is out of the questino IMHO 17:13:52 * jwb is here now 17:14:04 <nirik> agreed 17:14:06 <sgallagh> Well, in theory we *could* have something like the fedora-release package carry around "Obsoletes:" for packages that are retired. 17:14:14 <dgilmore> but doing rawhide/branched more often I dont see a big issue with 17:14:43 <nirik> sgallagh: that sort of thing has been proposed a number of times and gotten shot down. 17:15:19 <t8m> I think the 4 weeks is slightly too short interval though 17:15:34 <thozza> the 4 weeks period was perceived as too short in general 17:15:38 <thozza> from the discussion 17:15:44 <sgallagh> I also wonder if we could solve this problem better through more automation 17:15:53 <mitr> I’m quite in favor of doing rawhide (not sure about branched) more frequently (not sure about 4 weeks), but that depends on someone implementing the tools and the process. 17:16:11 <sgallagh> The ownership change mails are nice, but maybe also automatically-CC all the dependencies when something is orphaned? 17:16:16 <nirik> I think tyl was offering to work on the tools. 17:16:28 <dgilmore> mitr: i believe till who proposed it is looking at writing tooling to do it 17:16:45 * nirik can't type today, yeah, till 17:16:54 <mitr> nirk, dgilmore: ah. That makes it much better. 17:17:10 <dgilmore> he wanted to make sure it was okay to do 17:17:22 <nirik> so, what time period do we think might be more acceptable? 6 weeks? 8? 17:17:32 <thozza> One of the reasons in the ticket was that we often don't know why the package was orphaned when retiring it 17:17:36 <jwb> i'd say 6 17:17:48 <thozza> there was no mechanism last time I orphaned a package to say why 17:17:56 <thozza> are we going to add this too? 17:18:00 <nirik> there is now. ;) 17:18:07 <thozza> to make the decision easier 17:18:09 <t8m> I'd prefer 8 weeks but 6 is OK 17:18:12 <nirik> when you use fedpkg to orphan it asks you. 17:18:30 <mitr> both 6 and 8 is fine with me, slight preference for 6 17:18:51 <nirik> hum, or perhaps that was just discussed and isn't implemented yet. 17:18:55 <nirik> but I agree we want that too. 17:19:03 <dgilmore> thozza: fedpkg retire now requires a reason 17:19:11 <dgilmore> thozza: and its the only way to retire a package now 17:19:14 <nirik> yeah, but not sure orphan does 17:19:34 <thozza> retire yes, but in the ticket the complain was about orphaning 17:19:35 <nirik> but we could make pkgdb ask. 17:19:45 <dgilmore> orphan doesnt require a reason 17:20:13 <thozza> that what makes the decision if to retire hard based on till's ticket 17:20:17 <thozza> sometimes 17:20:39 <thozza> i think it would be worth of adding a reason also for orphaning 17:20:40 <nirik> well, it means sometimes we would retire because 'orphaned for 6 weeks' 17:20:46 <nirik> which isn't very descriptive. 17:21:28 <nirik> but I guess sometimes we wouldn't really know... old maintainer could just not have time 17:21:44 <jwb> i don't think the orphan reason matters tbh 17:21:59 <jwb> i think "this was sitting there for 6 weeks and nobody cared to take it" is reason enough 17:22:09 <t8m> I suppose main reason for orphaning is that the maintainer does not want to maintain the package anymore 17:22:40 <nirik> or could be they were inactive and their packages were orphaned by fesco, or ... lots of things. 17:22:57 <jwb> nirik, again, doesn't matter. nobody picked it up in the interim 17:23:10 <mitr> jwb: “there is a critical security bug I don’t know how to fix, and upstream hasn’t made a release in 2 years”, or “the last upstream release turned this from a QR code generator into a pony gallery” would be interesting to know about 17:23:12 <t8m> If the maintainer thinks the package is not worth maintaining because it is "bad" he should retire it 17:23:13 <thozza> jwb: I agree, but it can discourage new maintainer from taking the package because he might not know what was the problem with it 17:23:16 <t8m> directly 17:23:29 <thozza> but I agree it it not the thing we have to have 17:23:30 <mitr> t8m: true 17:23:43 <thozza> t8m: I agree 17:23:51 * nirik nods. 17:24:37 <nirik> proposal: allow retiring of non stable release packages after they are orphaned for 6 weeks. 17:24:43 <jwb> +1 17:24:47 <mitr> nirik: +1 17:24:54 <t8m> nirik, +1 17:24:57 <kalev> +1 17:25:23 <dgilmore> +1 17:25:48 <sgallagh> +1 17:26:28 <thozza> +1 17:26:33 <nirik> #agreed allow retiring of non stable release packages after they are orphaned for 6 weeks. (+7,0,0) 17:26:42 <nirik> #topic #1336 - 32 bit ppc support 17:26:42 <nirik> .fesco 1336 17:26:43 <nirik> https://fedorahosted.org/fesco/ticket/1336 17:26:44 <zodbot> nirik: #1336 (32 bit ppc support) – FESCo - https://fedorahosted.org/fesco/ticket/1336 17:27:21 <nirik> so, what do we need to decide here? ;) 17:28:12 <mitr> Actually reading this now, this is “someone might ask FESCo for a decision in the future“ thing? 17:28:16 <dgilmore> how an arch that doesnt want to be maintained by the secondary arch team should be supported if another group wants to 17:28:36 <jwb> simply put: they do it themselves 17:28:40 <dgilmore> mitr: well, its a down the road but highly likely thing 17:28:42 <jwb> (imho) 17:28:58 <nirik> yeah, it sounds like there's no actual work really to look at yet? 17:29:05 <t8m> I don't think there is much to decide. Basically all the concerns with reintroducing ppc32 are quite obvious and if anyone would want to reintroduce it they would have to solve them. 17:29:08 <jwb> i suspect very much that this might be a good precendent for if/when we decide to drop i686 though 17:29:11 <mitr> I _have_ seen a sudden surge in ppc(32) bugs recently, but IIRC nothing to do with composes 17:29:11 <sgallagh> My stance is that they should become a Fedora Remix. End of story. 17:29:16 <dgilmore> the decision can be delyaed 17:29:27 <dgilmore> but some thought on how it should be done I think is needed 17:29:30 <nirik> jwb: could be. 17:29:42 <jwb> t8m, on the other hand, i'd really like to drop ppc32 support from kernel.spec 17:29:43 <mitr> sgallagh: Probably. The case for supporting 32-bit is decreasing every year. 17:29:57 <dgilmore> mitr: there has been no 32 bit ppc composes since f18 17:30:00 <jwb> i've waited patiently to do so, but i'm not interested in waiting longer 17:30:10 * nirik has a ppc32 box. It has F12 I think on it and has been powered off since then. I can't see much use for turning it on personally. ;) 17:30:41 <dgilmore> jwb: im all for it going away 17:30:42 <nirik> dgilmore: install media hasn't been made since f12 I think too right? or around then... 17:30:49 <mitr> Just to be explicit: What about 32-bit userspace on ppc64? Are we supporting that at all? 17:31:00 <t8m> jwb, in theory, if someone came up and said that he would maintain the ppc32 support in kernel, would you accept it? 17:31:08 <dgilmore> nirik: some was made for f18, but no one in the community stepped up to test of fix bugs 17:31:14 <dgilmore> I think it didnt actually work 17:31:21 <t8m> jwb, or you don't want the ppc32 there in any case? 17:31:27 <dgilmore> mitr: no its gone 17:31:42 <jwb> t8m, someone said they were going to. they said that months ago. no ppc32 infrastructure exists still 17:31:57 <jwb> t8m, so if someone showed up and pointed me to a koji instance that was acutally running, i'd add it back in 17:32:13 <dgilmore> jwb: i believe thats the guy that sent an email to the ppc list last week introducing himself 17:32:21 <t8m> jwb, then it is no problem and you can drop it 17:32:33 <jwb> dgilmore, yeah, same guy. still no running infrastructure 17:33:16 <dgilmore> proposal: any arch that wants to call itself fedora needs to build everything on their own, show that they can do a remix of fedora. then request that FESCo consider them as a secondary arch 17:33:25 <jwb> i don't want to get into a pattern of "oh, i'll wait 3 more weeks because someone sent an email" 17:33:33 <nirik> If secondary arch and kernel folks don't see their effort as viable, not sure fesco should override. 17:33:41 <dgilmore> jwb: right, because he sent that email I filed this ticket 17:33:47 <mitr> dgilmore: That sounds like an unexpected overreach/generalization 17:33:57 <dgilmore> so we can say to him this is what you have to do if you want it to happen. 17:34:15 <jwb> mitr, i don't think it is. i think it's a formalization of what has already happened. 3 times now. 17:34:23 <dgilmore> mitr: perhaps. I know there is people working to get Fedora bootstrapped on mips 17:34:42 <jwb> ppc/ppc64 started in my basement. armv7 started at seneca. aarch64 started outside of fedora as well 17:34:44 <t8m> dgilmore, +1 17:34:54 <dgilmore> having something viable and working, i don't think is too much toa sk 17:34:55 <mitr> jwb: Actually, AFAIK in most cases the secondary Koji was maintained by Fedora Infra long before secondary arch had full feature parity. 17:34:57 <dgilmore> to ask 17:35:02 <jwb> mitr, no 17:35:06 <sgallagh> Yeah, I think codifying dgilmore's approach makes some sense 17:35:20 <dgilmore> mitr: none of the secondary koji's are maintained by infra 17:35:27 <mitr> And we've had the ARM debate about whether primary architecture promotion implies other maintainers fixing build failures, which implies that there _were_ build failures 17:35:33 <t8m> mitr, the Fedora Remix does not have to have "full feature parity" to be considered 17:35:45 <t8m> mitr, I don't see anything like this in the dgilmore's proposal 17:35:46 <nirik> dgilmore: I think we have this somewhat already codified. 17:35:48 <jwb> mitr, the bootstrap for all of the arches was started elsewhere. after it was proven somewhat viable and active, hardware was added to the fedora datacenter. none of it is maintained by fedora infra 17:35:57 <nirik> https://fedoraproject.org/wiki/Architectures 17:36:23 <mitr> t8m: I read "build everything on their own" as "all packages that exist" 17:36:28 <dgilmore> the main difference i see in the ppc32 case is that the ppc team does not want to maintain it 17:36:29 <nirik> although it needs updating. 17:36:40 <nirik> yeah, this is a special case I guess. 17:37:29 <dgilmore> mitr: that doesnt have to be the case, none of the arches have all packages that exist in fedora on them 17:37:47 <dgilmore> mitr: there is arm only packages that just do not exist on x86 17:37:47 <t8m> dgilmore, could you replace the 'build everything" with something more precise in your proposal? 17:37:52 <mitr> dgilmore: Good, that was my main objection to that working / the thing I saw as an overreach 17:38:11 <nirik> mitr: infra doesn't maintain really the aarch64/ppc/s390 stuff... I would actually like to start doing so more actively, but right now they maintain their own machines. 17:38:46 <thozza> what about "build everything on their own"/"build selected feature set on their own" ? 17:38:49 <mitr> nirik: My mistake—I always understood “in Phoenix” and “maintained by Fedora infra” to be the same thing. 17:39:29 <nirik> mitr: well, we can get to them and power them off, etc... :) but yeah. 17:39:32 <dgilmore> proposal: any arch that wants to call itself fedora needs to build up and host their own infrastructure, along with building up enough packages to show that they can do a working remix of fedora. Then request that FESCo consider them as a secondary arch 17:39:47 <mitr> thozza: I guess the minimum we want is “bootstrap on their own”, and what we actually want is something in the middle—“build a realistic installable image” 17:40:09 <thozza> mitr: sure, it was just rough idea 17:40:15 <dgilmore> thozza: mitr: really the build everything was more about their infrastructure. hopefully the newer proposal is clearer 17:40:16 <t8m> dgilmore, +1 17:40:31 <mitr> dgilmore: Works for me (… as a default/starting point; someone proposing an arch would probably want to come discuss the specifics in any case). +1 17:40:37 <jwb> +1 17:40:39 <nirik> sure, +1 17:40:42 <dgilmore> mitr: right 17:40:52 <thozza> dgilmore: +1 17:40:57 <sgallagh> dgilmore: +1 17:41:06 <nirik> #agreed any arch that wants to call itself fedora needs to build up and host their own infrastructure, along with building up enough packages to show that they can do a working remix of fedora. Then request that FESCo consider them as a secondary arch (+7,0,0) 17:41:15 <nirik> #topic Next weeks chair 17:41:21 <nirik> who wants the mic next week? 17:41:34 <sgallagh> And by extension, any package removed from Fedora proper that wanted to revitalize itself should have to re-enter through the same process? 17:41:50 <jwb> sgallagh, uh... 17:41:52 <jwb> what? 17:41:55 <nirik> sgallagh: ? 17:41:57 <sgallagh> s/package/arch/ 17:41:59 <sgallagh> Sorry 17:42:03 <jwb> oh 17:42:09 <dgilmore> sgallagh: yes 17:42:13 <jwb> we have a process for that 17:42:15 <t8m> sgallagh, I think it is implicit 17:42:19 <jwb> but yeah, kind of implied 17:42:22 <nirik> yeah. 17:42:41 <mitr> sgallagh: “by default”, though taking shortcuts by reusing stuff that already exists (like existing servers in existing racks that noone else needs) would I hope be permissible. 17:42:49 <nirik> I would also hope if we demoted say... i686... we would be clear what criteria it would need to be secondary/etc. 17:42:50 <jwb> wait, sorry. strike my process comment. i was thinking of something else 17:42:54 <jwb> still implied though 17:43:24 <jwb> nirik, if we do that i would hope we'd go a step further and line it up before we demoted 17:43:25 <dgilmore> nirik: I do think we need to look at a plan to demote i686 to secondary status 17:43:42 <jwb> nirik, lots of lead time, deprecate in release N, demote in release N+1 or N+2 17:43:50 <dgilmore> assuming that there is people wanting to keep 32 bit x86 around longer term 17:43:50 <nirik> sure. 17:44:01 <jwb> because just dropping it like we did ppc makes it 10x harder to bring back 17:44:04 <nirik> I'd be happy to see it go. ;) 17:44:20 * sgallagh is in the "burn it down and salt the earth" crowd, personally 17:44:28 <nirik> anyhow, next week chair? anyone? 17:44:35 <sgallagh> I'll take it. It's been a whie. 17:44:37 <sgallagh> *while 17:44:39 <mitr> dgilmore: I wonder. With all the talk about being a fractured platform that breaks apps, the 32-bit userspace (not booting in 32-bit) might be worth maintaining for a very long time. But that’s for some other time. 17:44:41 <jwb> (actually, ppc might have been doen that way and nobody cared enough to pick it up until after the fact. i can't remember) 17:44:48 <nirik> #info sgallagh to chair next week 17:44:50 <nirik> thanks sgallagh 17:45:10 <jwb> mitr, they already stopped supporting that 2 releases gao 17:45:12 <jwb> er, ago 17:45:21 <nirik> #topic Open Floor 17:45:25 <mitr> jwb: I was talking about 686 17:45:29 <jwb> mitr, ah! 17:45:33 <mitr> For open floor: Anything on #1334 (Zanata)? 17:45:57 <nirik> mitr: my understanding is that they wanted to keep discussing in ticket... since this is a bad time for them... 17:46:04 <t8m> I am OK with the transfer to Zanata for F22 17:46:43 <mitr> nirik: My guess is that bringing it up on the meeting might actually collect the +5 necessary way quicker than just reminding everyone in the ticket. 17:47:06 <sgallagh> This might be more a rel-eng question, but how are we feeling about Alpha? We identified several new blockers today at the review. Should we setting expectations? 17:47:15 <nirik> I'm happy to let translators do what they think is best... although I feel a bit uneasy that may not have been a full evaluation of alternatives... 17:47:29 <nirik> mitr: sure, true. 17:47:48 <dgilmore> nirik: same 17:48:14 <sgallagh> nirik: Sensible (with the obvious qualification of "within Fedora's Foundations and mission" 17:48:36 <mitr> nirik: More or less, yes. 17:48:43 <sgallagh> i.e. I don't love the idea of automating Google Translate or Bing! 17:48:51 <sgallagh> (not that this is on the table) 17:48:58 <dgilmore> sgallagh: Im confident we can build and deliver something, I honestly expect that Beta will look different to Alpha, as we will learn some lessons and have issues to fix along the way 17:49:15 <mitr> AFAICT our concern is primarily the scheduling, and even that only for the few dozen packages that are Fedora-native 17:49:18 <sgallagh> dgilmore: I meant more in terms of time-scale 17:49:34 <dgilmore> sgallagh: really depends on the bugs and how long they take to fix 17:49:40 * sgallagh nods 17:49:55 <dgilmore> sgallagh: the compose side being the big blocker is gone for now 17:49:59 <sgallagh> BTW, thanks and congratulations on getting out TC4 17:50:28 <nirik> http://pootle.translatehouse.org was mentioned... but anyhow, I am ok with them doing what they think is best. The history with transifex makes me sad to be moving things... oh well. 17:50:28 <dgilmore> still got some tweaking to go, but it's getting there 17:51:02 <dgilmore> nirik: I know that OLPC uses pootle 17:51:25 <t8m> it's slightly confusing talking about two topics at once :) 17:51:30 <nirik> zanata does have interested developers already working with the community. 17:51:34 <dgilmore> t8m: true 17:51:52 <mitr> proposal: FESCo is fine with https://fedoraproject.org/wiki/L10N_Move_To_Zanata ; please schedule the upstream project migration to happen after F21 final release is approved. 17:51:59 <nirik> so, any other votes on the 1334 ticket? or shall we vote in ticket/discuss more next week? 17:52:26 <t8m> mitr, +1 17:52:33 <sgallagh> mitr: +1 17:52:41 <nirik> mitr: +1 17:52:48 <thozza> mitr: +1 17:52:49 <kalev> mitr: +1 17:53:04 <dgilmore> +1 17:53:16 <nirik> #agreed FESCo is fine with https://fedoraproject.org/wiki/L10N_Move_To_Zanata ; please schedule the upstream project migration to happen after F21 final release is approved. (+7,0,0) 17:53:27 <nirik> any other open floor topics? 17:54:03 * thozza will be on vacation for next 2 weeks... so will not attend the next two meetings 17:54:19 <kalev> regarding possibly demoting i686, we could try and do it step by step 17:54:28 <kalev> like ship only x86_64 install images for F24 or whatever, but at the same time still build everything for i686 too to keep multilib support 17:54:37 <kalev> and then, in a later release (F25? or F26?) it would allow us to drop the i686 kernel and really force even the upgraders to x86_64 17:54:56 <jwb> we could do all kinds of alternatives too 17:55:11 <dgilmore> kalev: perhaps. we should talk to OLPC as thier x86 hardware is all 32 bit only 17:55:23 <dgilmore> so we should make sure that we continue to support them 17:55:39 <jwb> dgilmore, they don't use our kernel 17:55:39 <dgilmore> there is a ton of options for what we can do 17:55:40 <kalev> definitely -- also, if we keep building stuff but don't roll our own images, they'll still be able to ship their custom images 17:55:49 <dgilmore> jwb: not yet, but i have heard they plan to down the road 17:56:06 <jwb> i'd like to see an interim step where we only install the 64bit kernel on 64bit CPUs. userspace could still be 32-bit 17:56:13 <thozza> is there a way how to migrate actual i686 Fedora to x86_64? 17:56:14 <mitr> I think we will have to expect quite a few contributors interested in keeping i686 going, with varying / currently unknown ability to actually do it. 17:56:21 <jwb> thozza, yes. reinstall ;) 17:56:36 <thozza> jwb: that's what I was afraid of 17:56:42 <mitr> thozza: It would be highly desirable to build one, yes. 17:56:57 <jwb> mitr, i'm not sure about that 17:57:12 <dgilmore> jwb: that should be doable. just need to work with releng and anaconda teams to make it happen 17:57:21 <nirik> I would hope the number of people who install i686 fedora on x86_64 hardware is small,but I could be wrong. 17:57:27 <mitr> jwb: I think we could _survive_ the migration without it, but it would be painful for many people 17:57:54 <jwb> nirik, surprisingly not. lots of people love PAE for some unknown reason 17:57:57 <nirik> we can also look and see how well the centos 7 i386 effort goes. 17:58:16 <nirik> jwb: sad 17:58:22 <jwb> nirik, i would expect it to go much more poorly than a well planned fedora demotion 17:58:30 <jwb> because they literally have to bootstrap from nothing. 17:58:35 <nirik> true enough 17:59:13 <nirik> does anyone want to take on coming up with some proposals around i686 ? 17:59:37 <jwb> people hate me enough as it is. i'll be happy for someone else to lead there. maybe the server WG? 17:59:55 <nirik> or base... but sure. 17:59:59 * dgilmore needs to run and pick up daughter from school 18:00:05 * kalev needs to run too. 18:00:12 <nirik> anyhow, anything else for open floor? 18:00:38 <nirik> will close in a minute or so. 18:00:49 <sgallagh> Nothing from me 18:01:30 <nirik> #endmeeting

1 0

Re: Agenda for Env-and-Stacks WG meeting (2014-08-26)
by Marcela Mašláňová 26 Aug '14

26 Aug '14

============================================ #fedora-meeting: Env and Stacks (2014-08-26) ============================================ Meeting started by mmaslano at 13:00:13 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-08-26/env-and-stacks.2… . Meeting summary --------------- * follow up from we learnt on Flock (mmaslano, 13:01:55) * ACTION: hhorak will send a proposal for every WG to send a short summary time to time to other WGs directly, so we all stay tuned (hhorak, 13:10:25) * ACTION: mmaslano will continue in writiing status of env and stacks WG (mmaslano, 13:11:38) * EPEL/epic proposal (mmaslano, 13:11:51) * LINK: https://lists.fedoraproject.org/pipermail/epel-devel/2014-March/009320.html (juhp_, 13:36:27) * ACTION: juhp_ will chat with smooge about epel/epic proposal and what should Env and Stack WG do about it (mmaslano, 14:02:06) Meeting ended at 14:16:36 UTC. Action Items ------------ * hhorak will send a proposal for every WG to send a short summary time to time to other WGs directly, so we all stay tuned * mmaslano will continue in writiing status of env and stacks WG * juhp_ will chat with smooge about epel/epic proposal and what should Env and Stack WG do about it Action Items, by person ----------------------- * hhorak * hhorak will send a proposal for every WG to send a short summary time to time to other WGs directly, so we all stay tuned * juhp * juhp_ will chat with smooge about epel/epic proposal and what should Env and Stack WG do about it * juhp_ * juhp_ will chat with smooge about epel/epic proposal and what should Env and Stack WG do about it * mmaslano * mmaslano will continue in writiing status of env and stacks WG * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * juhp_ (57) * mmaslano (38) * hhorak (30) * langdon (11) * bkabrda (6) * zodbot (5) * vpavlin (4) * pingou (4) * sicampbell (1) * bkabrda1 (1) * pkovar (1) * samkottler (0) * tjanez (0) * juhp (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

meetingminutes August 2014