8:54 a.m.
======================================================================================================
#fedora-meeting: Security Team Meeting - Agenda:
https://fedoraproject.org/wiki/Security_Team_meetings
======================================================================================================
Meeting started by d-caf at 14:21:47 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2016-02-11/fedora_securit...
.
Meeting summary
---------------
* Roll Call (d-caf, 14:22:13)
* Participants are reminded to make liberal use of #info #link #help
in order to make the minutes "more better" (d-caf, 14:27:09)
* Follow up on last week's tasks (d-caf, 14:27:29)
* ACTION: pjp to give a status update on security policy in the wiki
(carried over) (d-caf, 14:28:10)
* ACTION: Sparks to figure out how FST members can get access to
Fedora security bugs (carried over) (d-caf, 14:28:19)
* ACTION: Sparks to follow up on meeting locations to verify their
availability. (carried over) (d-caf, 14:28:30)
* Fedora Security Team FAD (d-caf, 14:31:00)
* Sparks going to press ahead with the 4 March date and use the 11
March date as a backup for the FAD. (d-caf, 14:32:16)
* Outstanding BZ Tickets (d-caf, 14:33:15)
* Open floor discussion/questions/comments (d-caf, 14:44:56)
* LINK:
https://lists.fedoraproject.org/archives/list/security-team@lists.fedorap...
(d-caf, 14:46:12)
Meeting ended at 14:47:25 UTC.
Action Items
------------
* pjp to give a status update on security policy in the wiki (carried
over)
* Sparks to figure out how FST members can get access to Fedora security
bugs (carried over)
* Sparks to follow up on meeting locations to verify their availability.
(carried over)
Action Items, by person
-----------------------
* **UNASSIGNED**
* pjp to give a status update on security policy in the wiki (carried
over)
* Sparks to figure out how FST members can get access to Fedora
security bugs (carried over)
* Sparks to follow up on meeting locations to verify their
availability. (carried over)
People Present (lines said)
---------------------------
* d-caf (41)
* linuxmodder (9)
* zodbot (5)
* Astradeus (2)
14:21:47<d-caf> #startmeeting Security Team Meeting - Agenda:
https://fedoraproject.org/wiki/Security_Team_meetings
14:21:47<zodbot> Meeting started Thu Feb 11 14:21:47 2016 UTC. The chair is d-caf.
Information about MeetBot at http://wiki.debian.org/MeetBot.
14:21:47<zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:21:47<zodbot> The meeting name has been set to
'security_team_meeting_-_agenda:_https://fedoraproject.org/wiki/security_team_meetings'
14:22:03<d-caf> #meetingname Fedora Security Team
14:22:03<zodbot> The meeting name has been set to 'fedora_security_team'
14:22:13<d-caf> #topic Roll Call
14:22:21 * d-caf
14:22:47<linuxmodder> .hello corey84
14:22:48<zodbot> linuxmodder: corey84 'Corey Sheldon'
<sheldon.corey(a)gmail.com>
14:24:41<linuxmodder> Sparks ?
14:25:02<d-caf> I believe he is out all month
14:25:09<d-caf> Astradeus: You still there?
14:26:25<linuxmodder> seems not :(
14:26:59<d-caf> ok, then...
14:27:09<d-caf> #info Participants are reminded to make liberal use of #info #link
#help
in order to make the minutes "more better"
14:27:29<d-caf> #topic Follow up on last week's tasks
14:27:55<d-caf> There was no real meeting last week, and old tasks are those not
here, and I ahve not heard updates
14:28:10<d-caf> #action pjp to give a status update on security policy in the wiki
(carried over)
14:28:19<d-caf> #action Sparks to figure out how FST members can get access to
Fedora
security bugs (carried over)
14:28:30<d-caf> #action Sparks to follow up on meeting locations to verify their
availability. (carried over)
14:28:33<Astradeus> d-caf: only partly :/
14:29:00<d-caf> Astradeus: understood
14:29:09<d-caf> Anyone know of any udpates on he above action?
14:30:48<d-caf> ok, moving on
14:30:56<d-caf> #topic Fedora Security Team FAD
14:31:00<d-caf> #topic Fedora Security Team FAD
14:31:34<d-caf> Sparks actually took on an action last time, on this but I
haven't heard anything yet, anyone else have an udpate?
14:32:16<d-caf> #info Sparks going to press ahead with the 4 March date and use the
11
March date as a backup for the FAD.
14:33:08<d-caf> and continueing on..
14:33:15<d-caf> #topic Outstanding BZ Tickets
14:34:27<d-caf> I don't have the nice summary that sparks usually does but
mhayden did run the numbers this morning
14:34:47<d-caf> +Tickets by Severity-+-------+---------+
14:34:47<d-caf> | Severity | Tickets | Owned | Unowned |
14:34:47<d-caf> +----------+---------+-------+---------+
14:34:47<d-caf> | medium | 480 | 39 | 441 |
14:34:47<d-caf> | low | 182 | 13 | 169 |
14:34:50<d-caf> | high | 57 | 20 | 37 |
14:34:52<d-caf> +----------+---------+-------+---------+
14:35:23<linuxmodder> at least that high number is droppign
14:40:06<d-caf> still a lot of work there
14:40:31<d-caf> an there was that recent one that hit the mailing list, which
appears it was never communicated to redhat/fedora before public annouce?
14:41:50<linuxmodder> missed that one in the recent ml flood from several sub
projects
14:42:22<d-caf> Yes, did the mailing list get hosed up or something?
14:42:33<d-caf> noticed a nearly 24 hour delay in my response
14:43:10<linuxmodder> mailman had some funky-ness last week iirc
14:43:19<linuxmodder> or was it hyperkitty can't recall
14:44:11<d-caf> anything else bug related?
14:44:19<linuxmodder> not that I've seen
14:44:56<d-caf> #topic Open floor discussion/questions/comments
14:45:01<d-caf> Ok, anything else?
14:45:43<linuxmodder> nah not from me
14:46:00<d-caf> Oh, the vulnerability that came in late was this thread:
https://lists.fedoraproject.org/archives/list/security-team@lists.fedorap...
14:46:12<d-caf> #link
https://lists.fedoraproject.org/archives/list/security-team@lists.fedorap...
14:46:32<d-caf> ok, well, guess that's it
14:47:15<Astradeus> maybe the issue with the fedora-release would be something to
discuss?
14:47:25<d-caf> #endmeeting