===================================
#fedora-meeting: FESCO (2013-02-13)
===================================
Meeting started by mmaslano at 18:00:20 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-02-13/fesco.2013-02-13…
.
Meeting summary
---------------
* init process (mmaslano, 18:00:36)
* #896 Refine feature process (mmaslano, 18:03:17)
* ACCEPTED: the new planning process was approved with change of name
from features to changes (+7,-0,0) (mmaslano, 18:18:34)
* #980 Add "activate contingency" points to the features process
(mmaslano, 18:19:24)
* ACCEPTED: We have an "check for contingency" point now. 1)
Document/emphasize that this is when FESCo will decide on activating
the contingency. 2) We recognize that deviations from that point
will happen, but we don't establish a detailed policy for them at
this time. 3) Close ticket, unless there are other changes.
(+5,-0,0) (mmaslano, 18:44:56)
* #1005 At f19 branching time, drop inheritance in rawhide (mmaslano,
18:45:08)
* #988 F19 Feature: System Configuration Shell -
https://fedoraproject.org/wiki/Features/SystemConfigurationShell
(mmaslano, 19:03:10)
* AGREED: Defer 1 week, asking 1) the people who will implement this
to add themselves as co-owners, 2) to explicitly answer relationship
to OpenLMI (even if it is "separate and distinct"), and auto-close
on no response. (+7,-0,0) (mmaslano, 19:17:13)
* #1036 F19 Feature: Enterprise / distributed two-factor authentication
-
https://fedoraproject.org/wiki/Features/EnterpriseTwoFactorAuthentication
(mmaslano, 19:17:27)
* AGREED: reject feature; let feature owners reopen and resubmit when
they are interested (+5,-0,0) (mmaslano, 19:22:27)
* #1040 F19 Feature: firewalld Lockdown -
https://fedoraproject.org/wiki/Features/FirewalldLockdown (mmaslano,
19:22:38)
* AGREED: firewalld lockdown feature was accepted (+5.5,-0,0)
(mmaslano, 19:37:42)
* #1085 2013-02-13 meeting feature voting (mmaslano, 19:37:56)
* AGREED: all features from new business are accepted "en bloc"
(+5,-0,0) (mmaslano, 19:45:10)
* Next week's chair (mmaslano, 19:45:31)
* mitr will be chairman next week (mmaslano, 19:47:57)
* Open Floor (mmaslano, 19:48:05)
* LINK:
http://lists.fedoraproject.org/pipermail/devel/2013-February/178226.html
(abadger1999, 19:56:00)
* LINK: https://admin.fedoraproject.org/pkgdb/acls/name/biosdevname
(mitr, 19:58:41)
Meeting ended at 20:13:21 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mmaslano (63)
* mitr (58)
* nirik (55)
* abadger1999 (40)
* notting (24)
* jreznik (23)
* jwb (22)
* zodbot (11)
* pjones (11)
* mattdm (9)
* dgilmore (7)
* fedora_richie (3)
* drago01_ (2)
* sgallagh (0)
* t8m (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
======================
#fedora-meeting: FAmNA
======================
Meeting started by masta at 02:00:11 UTC. The full logs are available
athttp://meetbot.fedoraproject.org/fedora-meeting/2013-02-13/famna.2013-02-…
.
Meeting summary
---------------
* === FAmNA Roll Call === (masta, 02:00:15)
* === Announcements === (masta, 02:04:21)
* === Tickets === (masta, 02:05:57)
* LINK: https://fedorahosted.org/famna/report/9 (masta, 02:05:59)
* ACTION: rbergeron to look into the booth situation for pycon
(masta, 02:31:38)
* need help with LFNW, please tag the ticket if you are interested
(masta, 02:37:25)
* ACTION: rbergeron to own the LFNW event (masta, 02:43:51)
* ACTION: masta to poke rbergeron about the status in like 2 days
(masta, 02:44:09)
* ACTION: inode0 to send aforementioned floating mail to robyn
(rbergeron, 02:45:06)
* LINK: http://www.linuxfestnorthwest.org/sponsorship (masta,
02:45:43)
* Fedora will likely be a Silver sponsor for LFNW (masta, 02:48:27)
* == Who will be the next FAmNA meeting chair? == (masta, 02:49:05)
* == Open Floor === (masta, 02:50:32)
Meeting ended at 03:04:16 UTC.
Action Items
------------
* rbergeron to look into the booth situation for pycon
* rbergeron to own the LFNW event
* masta to poke rbergeron about the status in like 2 days
* inode0 to send aforementioned floating mail to robyn
Action Items, by person
-----------------------
* inode0
* inode0 to send aforementioned floating mail to robyn
* masta
* masta to poke rbergeron about the status in like 2 days
* rbergeron
* rbergeron to look into the booth situation for pycon
* rbergeron to own the LFNW event
* masta to poke rbergeron about the status in like 2 days
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* masta (83)
* rbergeron (66)
* chanchito (49)
* inode0 (25)
* nb (17)
* abadger1999 (14)
* zodbot (11)
* j_dulaney (8)
* dramsey (3)
* kdas_ (3)
* MarkDude (2)
--
-Jon Disnard
fas: parasense
irc: masta
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There were some technical issues at the start of today's meeting, so the logs
will be incomplete. I've pasted the log directly from my client in addition to
the logs captured by meetbot.
Minutes: http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-11/fedora_docs_https:fedoraproject.orgwikidocs_project_meetings.2013-02-11-14.22.html
Minutes (text): http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-11/fedora_docs_https:fedoraproject.orgwikidocs_project_meetings.2013-02-11-14.22.txt
Log: http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-11/fedora_docs_https:fedoraproject.orgwikidocs_project_meetings.2013-02-11-14.22.log.html
- ----------------------------------------------------------------------------------------------
<Sparks> randomuser`: Meeting?
* tjikkun_work (~tjikkun@2a00:d10:2:1:a6ba:dbff:fef3:f431) has joined
<Sparks> #startmeeting Docs Project Meeting - Agenda:
https://fedoraproject.org/wiki/Docs_Project_meetings
<nirik> alas, we are working on zodbot. ;(
<puiterwijk> Sparks: meetbot is currently unavailable yet. I'm looking at it
now with Kevin
<Sparks> puiterwijk: Ya
<Sparks> #meetingname Fedora Docs
<Sparks> #topic Roll Call!
* Sparks is here
* Penguiniator is here (new member)
<randomuser`> sorry, distracted
* jreznik_ is now known as jreznik
* Sparks notes that nirik is working on zodbot and a git problem on
fedorahosted at the moment.
* pkovar is here
* Sparks hands the meeting over to randomuser`
<randomuser`> thanks, Sparks
<randomuser`> we'll wait a moment more for roll call
* bcotton (~bcotton(a)sheldon.rcac.purdue.edu) has joined
<randomuser`> #topic Follow up on last week's action items
<bcotton> hey randomuser` did you #startmeeting?
<randomuser`> bcotton, zodbot is MIA
* UnCleJack is here
<randomuser`> i'll have to do it manually
* threebean checks in #fedora-admin about zodbot
<bcotton> randomuser`: ah, okay. Good luck! (RIP Zodbot)
<puiterwijk> threebean: me and Kevin are working on it in -noc
<Sparks> threebean: They know
<randomuser`> I sent out a big pile of nag emails re: beats last night, and
responses are already trickling in
<threebean> puiterwijk: I see that now.. I just wandered in ;)
<randomuser`> Sparks, you were following up with infra?
<Sparks> Umm
<Sparks> randomuser`: For the Koji tag?
<randomuser`> "Sparks to follow up with RELENG on the additional repo and tags
in Koji"
<randomuser`> yeah
<randomuser`> #info
https://fedoraproject.org/wiki/Docs_Project_meetings#11_February_2013
<Sparks> I checked with Dennis and he was going to get back with me but had a
day off last week so I kinda missed him, I think.
<Sparks> I think he said he has created the tag and the repo and was testing
some things.
<Sparks> EOF
<randomuser`> okay, thanks
<randomuser`> I saw rudi is working on publican 3 for us,
http://lists.fedoraproject.org/pipermail/docs/2013-February/014825.html
* mmello (~Marcelo(a)186.215.54.218) has joined
<Sparks> Yes! Shouldn't be long now!
<randomuser`> Sparks, I can take the weekly nagging off the agenda if you'd
like to bring it up when appropriate
<Sparks> Sure, just create a topic for it as this will live for another few
weeks.
<randomuser`> will do, thanks
<randomuser`> #topic New Contributors
<randomuser`> I'd like to welcome Penguiniator and UnCleJack to the group
<Penguiniator> randomuser`, thanks
<UnCleJack> :-) thanks
<randomuser`> We're around if you have any questions, of course
* jduncan (~jduncan(a)pool-71-176-228-243.rcmdva.fios.verizon.net) has joined
<Sparks> Woot! Fresh meat!
<randomuser`> I mentioned a bacon chocolate cupcake recruiting bounty on the
list a while ago, and I plan on claiming it as their sponsor
<lnovich> randomuser - all yours
<UnCleJack> well, ive talked to Sparks about contributing to the security
guide, and told him i'll work on it on the weekend, but turns out i just need
some more time getting used to docbook & wrokflow, before i'm of any use
* movl has quit (Read error: No route to host)
<randomuser`> I think the best approach to start is to write it out, and worry
about the markup after
<Sparks> UnCleJack: If you make changes and send them to me in a patch I'll fix
the DocBook. :)
<UnCleJack> Sparks, That would be great :-D
<randomuser`> okay, enough picking on the new guys
<UnCleJack> Sparks, but please let me know what i did wrong, so i can learn
and send quality patches ;-)
<Sparks> UnCleJack: Content is the hard part. Tags are easy once you get use
to them.
* dwmw2_gone is now known as dwmw2
<Sparks> UnCleJack: Oh, I won't hold back. :)
* mdomsch (~mdomsch(a)cpe-70-116-14-133.austin.res.rr.com) has joined
<UnCleJack> Sparks, just the way i like it ;-O
<lnovich> i think getting content is the hard part as you can't just make this
all up
<chuckf> randomuser`: would you like me to see if I can get my meetbot to run
in here for the meeting?
<chuckf> or is it too late?
<Sparks> lnovich: Have you read the Security Guide? Clearly I can make up a
lot of stuff.
* zodbot (supybot@fedora/bot/zodbot) has joined
<randomuser`> chuckf, I think it's a moot point at this stage
<Sparks> chuckf: I think we've been using the tags for zodbot so maybe if we
run the logs through it will make the minutes?
<chuckf> randomuser`: okay
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRGQmqAAoJEL1wZM0+jj2ZFxoH/RjtVsXvrC8SUflEeWwkHapQ
mRUEztOsxu2EEw4a7GjU8LdZnsZ/FM5DvuffBDSO7tgFH2lQ4qBx5KZq1SzL1AZ1
aopm/WDSHTjJvVUPIuqdiimcIlUtQGNydOvu+1il3nSBk7u0BR/YFIdsZHS7dxKC
KI09e/WK+8G9evUwUHZGQrqYLNr16uQcvTnG3Px+uLHpvAeoc71GW9tWNdwyUaSO
1rKWwYEwnQ2NPuxrE/x8BBrnd4+4V/qlZ64mCxsC9qthkFB+52XM764hgeCq5uxf
u4JuUyvj90y+FXbApGVWY4C5rSl+RGqDiK8wxPSCuS/EAZunzfkhlf4E2RBfjeE=
=H5wS
-----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 continue talking about post-party actions and regular
events plans. Please work on action items and contribute your ideas on
details (time, place, topics) of the next offline activity.
The next IRC meeting will be held on next Friday (2013-02-15). Please
come and join the discussion if you can!
[1]
http://meetbot.fedoraproject.org/fedora-zh/2013-02-08/fedora-zh.2013-02-08-…
--
Alick
Fedora 18 (Spherical Cow) user
https://fedoraproject.org/wiki/User:Alick
============================================
#fedora-meeting: Infrastructure (2013-02-07)
============================================
Meeting started by nirik at 19:00:00 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2013-02-07/infrastructure.2…
.
Meeting summary
---------------
* welcome to all (nirik, 19:00:01)
* New folks introductions and Apprentice tasks. (nirik, 19:01:50)
* Applications status / discussion (nirik, 19:07:35)
* OpenID ID for FAS-OpenID:
http://<username>.id.stg.fedoraproject.org/ (puiterwijk, 19:08:54)
* will work out a theme/skin for fas-openid and then ask for wider
testing soon. (nirik, 19:23:00)
* datanommer to be updated in stg and tested by threebean /
housewifehacker1 (nirik, 19:23:20)
* jenkins will get a faq doc and then more widespread testing.
(nirik, 19:23:49)
* askbot upgrade being prepped in stg. (nirik, 19:24:45)
* bodhi update for prod soon with bugfixes (nirik, 19:25:14)
* Sysadmin status / discussion (nirik, 19:26:29)
* Private Cloud status update / discussion (nirik, 19:44:05)
* Upcoming Tasks/Items (nirik, 19:47:14)
* 2013-02-08 mass rebuild for f19 starts. (nirik, 19:47:35)
* 2013-02-11 pkgdb update. (nirik, 19:47:35)
* 2013-02-18 to 2013-02-19 smooge on site at phx2. (nirik, 19:47:35)
* 2013-02-28 end of 4th quarter (nirik, 19:47:35)
* 2013-03-29 - spring holiday. (nirik, 19:47:36)
* 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze (nirik,
19:47:37)
* 2013-04-16 F19 alpha release (nirik, 19:47:38)
* 2013-05-07 to 2013-05-21 BETA infrastructure freeze (nirik,
19:47:40)
* 2013-05-21 F19 beta release (nirik, 19:47:42)
* 2013-06-11 to 2013-06-25 FINAL infrastructure freeze. (nirik,
19:47:44)
* 2013-06-25 F19 FINAL release (nirik, 19:47:46)
* Open Floor (nirik, 19:50:35)
* LINK: http://mm3test.fedoraproject.org/hyperkitty/ (pingou,
19:52:23)
Meeting ended at 20:00:20 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nirik (142)
* puiterwijk (38)
* pingou (34)
* skvidal (31)
* abadger1999 (23)
* lmacken (17)
* threebean (16)
* abompard (11)
* mattdm (10)
* mdomsch (7)
* cmullead (6)
* zodbot (5)
* dkanbier (3)
* relrod (2)
* SmootherFrOgZ (2)
* housewifehacker1 (1)
* maayke (1)
* ianweller (1)
* ausmarton (1)
* herlo (1)
* ricky (0)
* CodeBlock (0)
* smooge (0)
* dgilmore (0)
--
19:00:00 <nirik> #startmeeting Infrastructure (2013-02-07)
19:00:00 <zodbot> Meeting started Thu Feb 7 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 <zodbot> The meeting name has been set to 'infrastructure'
19:00:01 <nirik> #topic welcome to 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:07 * skvidal is here
19:00:08 <nirik> welcome everyone.
19:00:09 * puiterwijk
19:00:13 * mattdm is here
19:00:15 * pingou is here
19:00:22 * maayke is here
19:00:31 * relrod is here
19:00:42 * threebean is here
19:00:55 * abadger1999 here
19:01:01 * nirik will wait a min more for folks to wander in. ;)
19:01:05 <ausmarton> hi
19:01:11 * herlo is here
19:01:15 * mdomsch
19:01:44 * lmacken
19:01:47 <nirik> ok, lets go ahead and get started. ;)
19:01:50 <nirik> #topic New folks introductions and Apprentice tasks.
19:02:01 <nirik> any new folks like to say hi? or apprentices have questions or commends?
19:02:03 <nirik> comments even
19:02:08 <cmullead> !
19:02:31 <nirik> cmullead: go ahead...
19:03:08 <cmullead> I am new to the group. I have been a user/admin of Red Hat/Fedora for many years
19:03:25 <cmullead> and I thought it was time to give something back
19:03:29 <nirik> welcome.
19:03:29 <cmullead> eof
19:03:42 <nirik> are you more interested in sysadmin type tasks? or application development? or both? :)
19:03:59 <cmullead> system admin
19:04:33 <nirik> cool. ;) See me after the meeting over in #fedora-admin and I can point you in the right direction to get started. ;)
19:04:34 <housewifehacker1> This is my first meeting. Im an intern with Gnome OPW program working on datanommer with threebean
19:04:48 <cmullead> ok
19:04:49 <nirik> welcome housewifehacker1.
19:05:10 * nirik is very much looking forward to datanommer. ;)
19:05:16 <pingou> \ó/
19:05:28 <skvidal> ah ha! that answers a question I had about your nick
19:05:32 <skvidal> housewifehacker1: welcome
19:05:52 <skvidal> hmmm actually it doesn't really answer my question
19:06:01 <skvidal> but it is a not an interesting or useful question
19:06:11 <threebean> :)
19:06:21 <abadger1999> :-)
19:06:22 <nirik> ok, any other new folks? Please do let us know if we can assist or direct you in helping out any. Thanks for contributing.
19:06:46 <nirik> #topic Applications status / discussion
19:06:48 <dkanbier> this is my first meeting as well. I'm a sysadmin willing to give something back to the community. I applied to the bug zappers group but would like to help out on anything infrastructure related as well.
19:06:53 <nirik> #undo
19:06:54 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0xd333e10>
19:07:24 <nirik> dkanbier: welcome. Please do also see me after the meeting in #fedora-admin and I can point you in the right direction... ;)
19:07:35 <dkanbier> will do :)
19:07:35 <nirik> #topic Applications status / discussion
19:07:44 <nirik> ok, any application news from this week/upcoming?
19:08:04 <puiterwijk> I want to call out for testers for FAS-OpenID again ,if I may?
19:08:08 <pingou> copr-cli progressed over the week-end (even with a very interesting fosdem)
19:08:09 <nirik> puiterwijk: please do.
19:08:17 * mdomsch fixed several bugs in MM 1.4 in staging; getting to the point where I need to start running cronjobs against live data to find more bugs
19:08:25 <pingou> jenkins-master is also asking for testers
19:08:34 <puiterwijk> as I have not yet received any comments on FAS-OpenID last week, I would like to again ask for testers
19:08:52 <pingou> puiterwijk: smooth for me
19:08:53 <nirik> should we perhaps send out a devel-announce post asking for more testers? or is that too widespread?
19:08:54 <puiterwijk> #info OpenID ID for FAS-OpenID: http://<username>.id.stg.fedoraproject.org/
19:09:00 <lmacken> pingou: I'd like to migrate bodhi & kitch over at some point
19:09:04 <lmacken> **kitchen
19:09:13 <pingou> lmacken: sounds great
19:09:20 <puiterwijk> nirik: I think that's a bit too wide
19:09:23 <skvidal> pingou: have you or slavek tried out copr-fe against it?
19:09:31 <lmacken> pingou: is there an easy way to migrate jobs?
19:09:32 <skvidal> or a test of copr-fe
19:09:37 <pingou> skvidal: I didn't :]
19:09:45 <nirik> puiterwijk: ok, how about infra list?
19:09:53 <puiterwijk> nirik: that would be a good one, I think
19:09:54 <pingou> skvidal: just against local (and not for build)
19:09:59 <skvidal> nod
19:10:14 <pingou> lmacken: I copy/pasted from jenkins to cloud when I did it for fedocal/f-r
19:10:33 <lmacken> pingou: cool
19:10:55 <pingou> lmacken: the only thing to take care of is 1 build = 1 python
19:10:58 <pingou> builder*
19:11:09 <puiterwijk> nirik: do you want me to send it after the meeting?
19:11:14 <nirik> puiterwijk: please do.
19:11:16 <puiterwijk> (or do you want to do yourself?)
19:11:24 <puiterwijk> sure, will do
19:11:53 <nirik> pingou: perhaps a jenkins post too... ?
19:12:26 <pingou> nirik: I wanted to write down a wiki page on what's our idea of use-case for jenkins
19:12:37 <pingou> but yeah after a general announcement is a good idea
19:12:41 <nirik> thats also a good idea. agreed.
19:13:18 <threebean> so, housewifehacker1 has put a ton of improvements into datanommer and we're looking to upgrade the instance in staging soon
19:13:24 <nirik> mdomsch: I think early next week I might try and split out mm mirrorlists to ther own servers. Or should I wait on that until 1.4 is in prod?
19:13:27 <threebean> here's our todo list for it https://github.com/fedora-infra/datanommer/issues/27
19:13:34 <pingou> cool threebean housewifehacker1
19:13:47 <mdomsch> nirik: we can split them out first
19:14:04 <nirik> mdomsch: ok. I would think it would be pretty easy...
19:14:18 <mdomsch> should be
19:14:22 <threebean> if I'm not around and she happens to need help with various fi-apprentice things, any extra help or advice would be appreciated.
19:14:39 <nirik> My door/irc client is always open. ;)
19:14:47 <abadger1999> nirik: devel would be fine for fa-openid mail I think, devel-announce is supposed to be even lower volume, though.
19:15:20 <puiterwijk> abadger1999: so you think the email should go to devel or devel-announce?
19:15:24 <nirik> sure, but this seemed like a one off announcement. ;)
19:15:27 <abadger1999> puiterwijk: devel
19:15:33 <abadger1999> not devel-announce
19:15:45 <nirik> but devel sounds fine to me too
19:15:51 <puiterwijk> ah ok. but not just infra?
19:15:52 <pingou> shouldn't wait for the design to announce it?
19:16:14 <threebean> (lastly, on datanommer.. the upshots to the latest changes are three-fold: 1) we get a smooth upgrade path for the DB with python-alembic, 2) we get an API we need to write datagrepper, and 3) we get some CLI scripts we need for nice nagios checks )
19:16:19 <abadger1999> dvel-announce is for people who are too cranky to subscribe to devel :-/
19:16:44 * SmootherFrOgZ is here now.
19:17:00 <abadger1999> pingou: fine with that too -- if we want testing now, though, I think most of hte infra people are already aware
19:17:05 <nirik> threebean / housewifehacker1: question: how is the db looking for datanommer so far? is it growing very big? should we split it in prod? or we don't know yet?
19:17:26 <nirik> pingou: on jenkins? or fas-openid?
19:17:32 <pingou> nirik: openid
19:18:06 <nirik> ok, I'm fine waiting on a design writeup on those, I agree it would be good to have. more so on jenkins...
19:18:12 <puiterwijk> I tend to agree with pingou on that, but maybe someone could help me with getting the design
19:18:15 <threebean> nirik: don't know yet -- we haven't checked.
19:18:34 <pingou> nirik: you want a fedora design for jenkins??
19:18:50 <puiterwijk> I could use help either with getting the design team a kick or with a temporary design until they are finally done
19:18:59 <nirik> oh I see. I was misunderstanding 'design' here.
19:19:10 <nirik> you are talking about theme/appearance?
19:19:12 <threebean> nirik: oh, that's not true. A dump was 236M back at the end of january.
19:19:15 <pingou> nirik: yes
19:19:21 * ianweller is here
19:19:38 <nirik> I was talking about a wiki page with 'here's what this is, and how you can use it, and what problems it solves, etc'
19:19:52 <relrod> puiterwijk: I can probably whip up at least a temporary design for it, poke me after the meeting.
19:20:17 <puiterwijk> relrod: ok, thanks :) (design would have been ready about two weeks back, but they're "still busy"...)
19:20:29 <abadger1999> threebean: If it's postgres, point me at it and I can get numbers for you.
19:20:30 <nirik> so, if we ask for testing we can point people at that and they can see how it's used, etc
19:20:49 <abadger1999> threebean: or a df -k /var/lib/pgsql should do it if it's the only database on that server.
19:20:54 <pingou> nirik: +1, that's kind of my idea for jenkins
19:21:10 <threebean> abadger1999: it is.. I'll check here in a moment.
19:21:56 <nirik> pingou: yeah. with how to add things, what things we can't add, etc.
19:22:21 <pingou> nirik: I'll send it around for review/comments before I announce it :)
19:22:27 <nirik> sounds good.
19:22:43 <nirik> with fas-openid, it's much less a issue because thats "anywhere you want to use openid" :)
19:23:00 <nirik> #info will work out a theme/skin for fas-openid and then ask for wider testing soon.
19:23:02 <puiterwijk> <nod>
19:23:20 <nirik> #info datanommer to be updated in stg and tested by threebean / housewifehacker1
19:23:31 <threebean> abadger1999: its db01.phx2.fp.o.. so, there are other dbs there.
19:23:49 <nirik> #info jenkins will get a faq doc and then more widespread testing.
19:24:06 <nirik> Any other application news or plans?
19:24:18 <threebean> oh, I've been fighting with askbot in stg with fedmsg plans.
19:24:26 * lmacken planning a bodhi update this week. masher changes only.
19:24:31 <abadger1999> threebean: k. I'll get it with a query
19:24:33 <threebean> sorting out fedora/epel django packaging issues for most of the week.
19:24:45 <nirik> #info askbot upgrade being prepped in stg.
19:24:49 <lmacken> threebean and I have also been fighting with a mod_wsgi+fedmsg threading issue recently
19:24:51 <nirik> threebean: thanks a lot for that. ;(
19:25:14 <nirik> #info bodhi update for prod soon with bugfixes
19:25:20 <pingou> threebean: if there is anything special it might be good to talk with Aurélien since HK is django
19:25:29 <pingou> might prevent us from having the problem later
19:26:21 <nirik> ok, moving on then...
19:26:22 * threebean nods
19:26:29 <nirik> #topic Sysadmin status / discussion
19:26:50 <nirik> So, we hopefully have some arm machines being racked today. Will need to get them up and running.
19:26:59 <pingou> arg on apps, HK has made some really nice progress last week
19:27:00 <lmacken> nice!
19:27:20 <nirik> Hopefully we can use a few of them for infra stuff too, which will be nice.
19:27:32 <SmootherFrOgZ> \o/
19:27:33 <puiterwijk> nirik: need help on the arm boxes?
19:27:36 <nirik> pingou: cool. I really want it to be ready. :)
19:27:37 <lmacken> pingou: wrt HK, we need to change the login form to https
19:27:55 <pingou> lmacken: mentionned, forgot to open a ticket for that though
19:28:04 <nirik> puiterwijk: well, we first need network and such. ;) Hopefully it will be pretty easy to get them setup
19:28:23 <puiterwijk> nirik: hehe, would be useful I guess yeah
19:28:25 <nirik> I'd like to discuss a bit a few bigger picture plans...
19:28:34 <nirik> a) splitting out apps from app servers.
19:28:50 <nirik> I'm going to start on this likely next week... with mirrorlist server.
19:29:12 <nirik> but at the end of it, it would be nice if we had no need for app boxes...
19:29:19 <skvidal> +billion
19:29:28 <nirik> does anyone have concerns or questions about that being the way to go? :)
19:29:37 <lmacken> which cloud are we going to migrate the apps to?
19:29:47 <skvidal> are we migrating to the cloud?
19:29:51 <nirik> no cloud yet, just seperate instances
19:29:54 <skvidal> I thought we were just going to split out instances
19:30:02 <lmacken> okay
19:30:12 <nirik> so, make mirrorlist01 02 03 in phx2 and move that to those, etc.
19:30:28 <abadger1999> threebean, nirik: datanommer on db01 is currently 305MB
19:30:41 <abadger1999> select pg_database_size('datanommer');
19:30:50 <nirik> Down the road / rhel7 or something we might be able to use containers for smaller apps
19:31:03 <nirik> but thats someday/sidetrack
19:31:17 <abadger1999> nirik: works for me.
19:31:44 <threebean> abadger1999: we're looking at a rate of ~1GB/year
19:31:51 <nirik> short term this means more instances, but hopefully they can be smaller and help us with debugging/prevent one thing from messing up another
19:31:59 <abadger1999> nirik: you going to just work on separating the web front ends right now? (db's at a later date)?
19:32:07 <nirik> abadger1999: yeah.
19:32:14 <abadger1999> cool.
19:32:23 <nirik> I still hope someday we can figure out a better way to replicate/deal with dbs
19:32:28 <lmacken> do we still plan on sticking with i686 vms?
19:32:38 <puiterwijk> nirik: I have a replication setup in cloud I believe
19:32:39 <abadger1999> nirik: oh something else to think about --
19:32:53 <nirik> lmacken: good question. we could try 64bit again... but the memory thing is anoying.
19:32:57 <abadger1999> nirik: If we go with openid everywhere, I believe we'll be able to have SSO but different domains.
19:33:13 <lmacken> nirik: yeah :\
19:33:29 <puiterwijk> abadger1999: completely correct
19:33:31 <nirik> is there any new/cool way around it? perhaps we should ask dmalcolm again?
19:33:37 <abadger1999> ie: packages.apps.fedoraproject.org, ask.fedoraproject.org, pkgdb.fedoraproject.org, etc will all be transparently logged into because of openid.
19:33:44 <nirik> puiterwijk: cool. write it up and we can discuss it on list?
19:33:55 <pingou> abadger1999: I do like that idea :)
19:33:57 <puiterwijk> nirik: sure, will try to find the servers back again :)
19:34:02 <puiterwijk> abadger1999: +1
19:34:05 <lmacken> nirik: I don't think there is any way around it (PyObject pointers double in size on 64bit). I'll ask dmalcolm though to make sure.
19:34:25 <nirik> rhel doesn't ship 32bit python on x86_64 do they?
19:34:42 <abadger1999> lmacken: there are ways but -- not as in, "oh, I'll just patch this and[...]"
19:35:10 <lmacken> nirik: not sure
19:35:17 <nirik> yeah, I don't think so.
19:35:18 <puiterwijk> nirik: I believe they actually do, I'll check
19:35:32 <puiterwijk> nirik: they do
19:35:33 <nirik> anyhow, worth looking into before we build a bunch of servers. ;)
19:35:42 <abadger1999> it would require changing CPython data structures. One thing dmalcolm might know, though, is whether we could run on an alternate interpreter and gain memory.
19:35:49 <nirik> but then if we use that, we need to build our stack of packages against that?
19:36:14 <abadger1999> and if we're split out, we might be able to try that on just a few apps which have a compatible stack.
19:36:20 * lmacken asked dave about it in #fedora-python
19:36:34 <puiterwijk> nirik: RHEL does ship 32-bit python on x86_64
19:36:35 <nirik> cool. lets continue looking at this out of meeting?
19:36:39 <skvidal> nirik: so.. .about building a bunch of servers..
19:36:54 <abadger1999> nirik: <nod> -- Anyhow -- I don't htink any of the potential solutions would be ready in time for this split to multiple app servers.
19:36:54 <nirik> puiterwijk: yeah, but how many of the things we need are either noarch or have a 32bit version?
19:36:55 <skvidal> nirik: the koji builders are spun up using ansible + kickstart
19:37:19 <skvidal> nirik: we could think about implementing the new app-specific instances like that
19:37:25 <skvidal> nirik: ie - puppetless
19:37:26 <nirik> skvidal: an _excellent_ segway into my next topic...
19:37:31 <nirik> b) migration to ansible
19:37:33 <abadger1999> So if memory is our constraint, I think we should stick with 32bit and think about 64bit+other solution in a year or more.
19:37:43 <nirik> abadger1999: fair enough
19:37:54 <pingou> dmalcolm | dmalcolm: or rather: yes: it will use nearly double the ram
19:38:11 <nirik> so, I think we need to whip up a plan for our ansible migration... and I can work on that. Then start working away at the little parts...
19:38:14 <threebean> skvidal: exciting prospect
19:38:28 <nirik> short term we need:
19:38:32 <skvidal> nagios
19:38:44 <skvidal> it'd be nice to have fas-push
19:38:46 <nirik> yeah, nagios was my c) topic. ;)
19:39:01 <nirik> it would be nice to move builder ansible repo into main ansible repo
19:39:02 <skvidal> the cron runner stuff - which is on my plate and something I'm actively working on both parts of
19:39:06 <nirik> yep.
19:39:17 <skvidal> agreed on moving builder ansible into main ansible
19:39:56 <skvidal> if anyone wants to do that and work on it
19:40:01 <nirik> we will end up with some machines puppet and newer stuff ansible, but I think thats ok for migrating... and we can keep converting away until we get to where we can have a flag day for the rest.
19:40:04 <skvidal> and I'm the blocking point
19:40:08 <skvidal> don't block on me
19:40:10 <skvidal> yell at me
19:40:18 <skvidal> and take on the process
19:40:24 <skvidal> we have lots of builders
19:40:34 <skvidal> and taking one out to test a new rebuild playbook from the main repo
19:40:39 <skvidal> is super-duper easy
19:40:42 <nirik> skvidal: I can look at doing the new mirrorlist boxes via ansible... that should possibly get us a global/whatever conversion to base others on
19:41:08 * mdomsch may need a 64-bit box for s3-mirror
19:41:08 <skvidal> nirik: I think I need to look at global again - istr it is full of crap
19:41:28 <skvidal> nirik: and by that I mean - it has a bunch of completely unnecessary system changes in it
19:41:29 <nirik> skvidal: yes, we should only convert over the parts that make sense. ;)
19:41:33 <skvidal> nod
19:41:41 <nirik> this is a good chance to clean that junk up
19:41:44 <skvidal> okay - sorry for telling you a bunch of things you already know :)
19:41:48 <nirik> mdomsch: sad that it takes so much mem
19:41:55 <nirik> not at all. :)
19:42:08 <nirik> ok, so c) on my list is 'redo nagios'
19:42:08 <mdomsch> nirik: it's tracking nearly 1M files
19:42:26 <nirik> mdomsch: yeah, understandable. ;(
19:42:51 <mdomsch> 2M really, as it does so on each end
19:42:56 <nirik> I'm going to whip up a mail on nagios and we can come up with a design... anyone interested in helping welcome.
19:43:46 <nirik> ok, any other sysadminy stuff folks had?
19:44:05 <nirik> #topic Private Cloud status update / discussion
19:44:22 <nirik> so, we need/want to update and reboot clouds... possibly next week?
19:44:22 <puiterwijk> nirik: I'm interested in helping with nagios
19:44:31 <nirik> puiterwijk: excellent. ;)
19:44:49 <dkanbier> me too, quite some experience with zabbix
19:44:51 <nirik> also, I'm interested in knocking off anything we have left before calling them production.
19:45:18 <nirik> dkanbier: cool.
19:45:26 <puiterwijk> nirik: so all current instances will get killed?
19:45:43 <nirik> puiterwijk: yep. we will need to restart them all.
19:45:54 <puiterwijk> nirik: restart or terminate?
19:46:17 <nirik> terminated. ;)
19:46:23 <nirik> since hosts will get rebooted.
19:46:36 <puiterwijk> ok
19:46:50 <nirik> but we will provide notice on that, etc.
19:47:01 <puiterwijk> ah ok, great.
19:47:14 <nirik> #topic Upcoming Tasks/Items
19:47:25 <nirik> we now have an actual schedule for f19... so I added it in:
19:47:35 <nirik> #info 2013-02-08 mass rebuild for f19 starts.
19:47:35 <nirik> #info 2013-02-11 pkgdb update.
19:47:35 <nirik> #info 2013-02-18 to 2013-02-19 smooge on site at phx2.
19:47:35 <nirik> #info 2013-02-28 end of 4th quarter
19:47:36 <nirik> #info 2013-03-29 - spring holiday.
19:47:37 <nirik> #info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
19:47:38 <nirik> #info 2013-04-16 F19 alpha release
19:47:40 <nirik> #info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
19:47:42 <nirik> #info 2013-05-21 F19 beta release
19:47:44 <nirik> #info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
19:47:46 <nirik> #info 2013-06-25 F19 FINAL release
19:47:51 <nirik> anything folks would like to schedule or note?
19:47:53 <mattdm> yes
19:48:01 <nirik> mattdm: fire away. ;)
19:48:10 <mattdm> The cloud feature asks for a koji update in there at the end of march
19:48:29 <mattdm> (cloud image build feature)
19:48:46 <nirik> ah ha.
19:48:47 <nirik> ok.
19:48:57 <mattdm> Specifically given the current schedule, sometime between March 19th and March 26th.
19:49:03 <mattdm> Which isn't a huge window, I know.
19:49:12 <nirik> mattdm: do you want me to pencil it in at a specific date? or ... ok.
19:49:37 <mattdm> It a little bit depends on the actual koji code development.
19:49:53 <nirik> yeah.
19:49:58 <nirik> ok, will add it in. ;)
19:50:01 <mattdm> March 26th is chosen as 1 week before alpha freeze, and it kinda works back from there.
19:50:10 <mattdm> thanks. that's all. :)
19:50:20 <nirik> ok, keep us posted. ;)
19:50:26 <mattdm> yep, i will.
19:50:35 <nirik> #topic Open Floor
19:50:42 <nirik> anyone have anything for open floor...
19:50:57 <abompard> almost made it this time... :/
19:51:13 <nirik> pingou: say, whats the status of fedocal?
19:51:30 <nirik> abompard: welcome. ;) whats the word on hyperkitty/mm3? ;)
19:51:33 <abompard> hey everyone, just joining late to say hello :-)
19:51:37 <pingou> nirik: I have some RFE do cover, need to start packaging it
19:52:02 <abompard> nirik: progress ! mm3test should be up-to-date, much debugging today thanks to pingou
19:52:08 <pingou> nirik: basically, still in 0.1.0-alpha but little bugs were reported, so either it works fine or few people tested it :)
19:52:23 <pingou> http://mm3test.fedoraproject.org/hyperkitty/
19:52:32 <nirik> pingou: thats another one I think we could move to wider testing soon/stg?
19:52:37 <pingou> it has in-thread reply!
19:52:46 <pingou> nirik: it would be nice for sue
19:53:38 <pingou> lmacken: https://fedorahosted.org/hyperkitty/ticket/38
19:54:14 <nirik> abompard: can you add openid to the login auth?
19:54:18 <nirik> or is that planned.
19:55:03 <abompard> nirik: hmm, I'm not sure we should open any type of auth, I'd rather keep it to the email providers and browserid
19:55:12 <abompard> nirik: since it's a mailing-list app
19:55:26 <lmacken> pingou: thanks!
19:55:30 <abompard> nirik: I need to make sure an email will be provided
19:55:30 <pingou> abompard: fas provides openid, so does google/yahoo
19:56:00 <puiterwijk> abompard: when you would configure it for FAs-OpenID, you're sure the user has a working email
19:56:00 <nirik> we can get email from fas openid I think...
19:56:05 * nirik nods.
19:56:07 <abompard> pingou: I know, but any openid provider does not provide an email address (it's the other way around)
19:56:26 <puiterwijk> abompard: FAS-OpenID provides email addresses
19:56:31 <puiterwijk> abompard: and even if it wouldn
19:56:35 <pingou> puiterwijk: HK isn't fedora specific
19:56:41 <puiterwijk> ah ok
19:57:01 <puiterwijk> sorry, then I was misled by the demo I got linked to last week ;)
19:57:05 <nirik> can't you ask for email in the openid request and fail if you don't get one back?
19:57:09 <puiterwijk> yes
19:57:30 <puiterwijk> you can say that you require an email address, and the openid protocol will abort if the provider doesn't want to give it
19:57:32 <nirik> but of course someone could send foo(a)bar.com...
19:57:53 <abompard> nirik: why not, I also must be sure that the openid provider validates the email adress
19:57:55 <puiterwijk> nirik: then that's the provider providing that email. most providers check it
19:58:02 <abompard> or you could impersonate anyone
19:58:36 <puiterwijk> abompard: in that case, we have the provider url and blacklist him?
19:58:39 <nirik> wlel, it's already pretty easy to do with smtp, but yeah, there's issues.
19:58:54 <nirik> anyhow, openid would be nice if we can figure a good way to do it.
19:59:14 <threebean> abompard: I love HK, btw. nice work.
19:59:15 <abompard> nirik: true. But the user has settings here, like his password that you could reset, etc.
19:59:20 <abompard> threebean: thanks !
19:59:40 <nirik> yeah.
19:59:53 <nirik> ok, we are almost out of time now. any last minute open floor items?
20:00:17 <nirik> ok, thanks for coming everyone. ;)
20:00:20 <nirik> #endmeeting
As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20130204
Next meeting is scheduled for 2013-02-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/20130211 . Thanks!
TOPIC: Criteria revision
=======================================================================
* adamw planning to draft a plan for improved presentation of
the release criteria. tflink suggests moving the criteria out
of the wiki could help, but for F19 for now it's likely to
stay in wiki
* Ideas to keep in mind as part of the plan:
* kparal - draw a line between simple explanations and
lawyerish complex clauses
* kparal/viking-ice - define terms that we're familiar with
but a general reader may not be
* tflink - ensure there's short text for each criterion for
IRC meeting purposes
* kparal - group the criteria (installation, desktop,
networking...)
* kparal - link to background info on each criterion (esp.
discussion when it was created)
* kparal - some mechanism for tagging criteria - "I hate when
I search for PXE, but it is called "network boot" or
similar"
TOPIC: Test Case Revision
=======================================================================
* adamw suggested expanding the upgrade test case set a little
* viking-ice suggested identifying hw-dependent and
non-hw-dependent test cases in the matrices
* kparal said we should finish revising the partitioning
criteria
* adamw thought we could come up with a set of common
partitioning operation test cases
* kparal suggested an explicit Secure Boot criterion
* We should try and get as much criteria revision and test case
revision done before Alpha as possible
TOPIC: Fedora 19 Feature list review
=======================================================================
* Already listed as features of potential concern from last
week's meeting:
* Features/NewFirstboot[1]
* Features/SyslinuxOption[2]
* Features/SystemdPredictableNetworkInterfaceNames[3]
* Features/YumGroupsAsObjects[4]
* Features/FixNetworkNameResolution[5]
* Features/ReplaceMySQLwithMariaDB[6] looks significant but we
do not currently have planned testing for MySQL
* tflink suggested that a comprehensive MySQL benchmark tool
could act as a compatibility checker if we could find such
a thing
* viking-ice said we should ensure F18->F19 upgrades
accomplish the mysql->mariadb switch smoothly
* If mysql is to still be available in F19, we should check
it can be installed and used
* On Features/SystemdPredictableNetworkInterfaceNames - we
should check behaviour of firewalld and libvirt, particularly
on upgrades; check 'em1' is still used for most onboard
adapters
* Features/KScreen[7] may impact KDE validation in a small way
* Features/SyslinuxOption[8] would be worth doing some optional
testing on at least: viking-ice suggested it should be a
supported kickstart option
TOPIC: Open Floor
=======================================================================
N/A
ACTION ITEMS
=======================================================================
* adamw to draft up a proposal for revising the presentation of
the release criteria
* adamw to draft up a kickstart criterion for f19
1. https://fedoraproject.org/wiki/Features/NewFirstboot
2. https://fedoraproject.org/wiki/Features/SyslinuxOption
3. https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceN…
4. https://fedoraproject.org/wiki/Features/YumGroupsAsObjects
5. https://fedoraproject.org/wiki/Features/FixNetworkNameResolution
6. https://fedoraproject.org/wiki/Features/ReplaceMySQLwithMariaDB
7. https://fedoraproject.org/wiki/Features/KScreen
8. https://fedoraproject.org/wiki/Features/SyslinuxOption
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
Hello folks,
As always, today is the APAC bi-weekly meeting and we had a great one.
I'd like to thank everyone for coming. The logs can be found at:
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2013-02-02/apac.2013-02-02-…
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2013-02-02/apac.2013-02-02-…
Here are the minutes of the meeting:
===================================================
#fedora-meeting: Fedora APAC Ambassadors 2013-02-02
===================================================
Meeting started by dramsey at 03:59:31 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-02-02/apac.2013-02-02-…
.
Meeting summary
---------------
* Roll call (tuanta, 04:00:06)
* LINK:
https://fedoraproject.org/wiki/Meeting:APAC_Ambassadors_2013-02-02#Agenda
(dramsey, 04:00:37)
* News from FAmSCo (tuanta, 04:02:27)
* FY2014 starts March 1 2013 (FranciscoD, 04:06:13)
* All budget figures should be available before FY2014 starts
(FranciscoD, 04:06:55)
* Indonesia team cancelled their bids (FranciscoD, 04:11:05)
* PH offers hosting a FAD instead of FUDCon (azneita, 04:11:27)
* APAC does not have plans for a FUDCon at the moment (FranciscoD,
04:11:45)
* ACTION: FranciscoD get in touch with asmartgoat, kaio (FranciscoD,
04:13:52)
* udinnet may bid for a FUDCon Sri Lanka next year. Needs to discuss
it with the Sri Lanka team (FranciscoD, 04:20:41)
* Review action items from last meeting (dramsey, 04:22:01)
* LINK: https://fedorahosted.org/fedora-apac/ticket/43 (dramsey,
04:25:03)
* LINK: https://fedorahosted.org/fedora-apac/ticket/59 (dramsey,
04:26:26)
* LINK:
http://ankursinha.fedorapeople.org/fudcon_plan/FUDCon%20organization%20plan…
(dramsey, 04:26:33)
* APAC Events: plans, status, reports (dramsey, 04:28:44)
* LINK: http://fedoraproject.org/wiki/F18_release_events (dramsey,
04:28:53)
* FranciscoD regrets having to leave the meeting (FranciscoD,
04:29:40)
* udinnet: Bckurera and myself have a plan to make some f18 media
(dramsey, 04:32:08)
* Fedora Malayasia will be having a FAD on 23rd Feb, 2013 (MavJS,
04:35:18)
* LINK: http://fedora.my/blog/fedora-activity-day-kl-openshift
(MavJS, 04:35:28)
* What is the status for the remaining APAC's FY2013 Budget?
(dramsey, 04:41:20)
* I am very proud of the APAC'ers doing Release Events. We did it
"again" and had the most Release Events for the regions. Â :)Â Fedora
Release Events (dramsey, 04:41:28)
* APAC'ers do you need any swag? What do you need to succeed?
(dramsey, 04:41:42)
* LINK:
https://fedoraproject.org/wiki/Ambassadors/APAC/Budget/Taiwan_Budget_FY2014
(zerng07, 04:43:28)
* LINK:
https://fedoraproject.org/wiki/Ambassadors/APAC/Budget/Taiwan_Budget_FY2014
(dramsey, 04:47:17)
* zerng07, needs input from Tuan and Buddhike (dramsey, 04:47:31)
* ACTION: FAmSCo Help review zerng07's request. (dramsey, 04:47:50)
* Trac tickets (dramsey, 04:48:23)
* Miscellaneous (dramsey, 04:50:20)
* LINK: https://www.googlesciencefair.com/en/2013/ (dramsey,
04:50:30)
* Food for your thoughts and share with others who may want to
participate in the Google Science Far 2013 for students age 13 to
18. (dramsey, 04:50:36)
* Open Floor (dramsey, 04:51:12)
* udinnet will chair next meeting (azneita, 04:52:05)
Meeting ended at 04:53:03 UTC.
Action Items
------------
* FranciscoD get in touch with asmartgoat, kaio
* FAmSCo Help review zerng07's request.
Action Items, by person
-----------------------
* FranciscoD
* FranciscoD get in touch with asmartgoat, kaio
* zerng07
* FAmSCo Help review zerng07's request.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dramsey (104)
* tuanta (44)
* udinnet (40)
* FranciscoD (36)
* azneita (35)
* MavJS (23)
* zerng07 (19)
* zodbot (15)
* arifiauo (3)
* udinnet_ (1)
--
Kind Regards,
Ye Myat Kaung
MavJS @ freenode.nethttp://www.mavjs.org
Fedora Ambassador & Malaysia Contributor
https://fedoraproject.org/wiki/User:Mavjs
7BFA DB9D D509 94AC 115B 1A0E E435 A5E3 A738 392D