Schedule for Thursday's FPC Meeting (2015-01-08 17:00 UTC), Followup:15 New:7
James Antill
james at fedoraproject.org
Wed Jan 7 19:25:00 UTC 2015
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-01-08 17:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2015-01-08 09:00 Thu US/Pacific PST
2015-01-08 12:00 Thu US/Eastern EST
2015-01-08 17:00 Thu UTC <-
2015-01-08 17:00 Thu Europe/London <-
2015-01-08 18:00 Thu Europe/Paris CET
2015-01-08 18:00 Thu Europe/Berlin CET
2015-01-08 22:30 Thu Asia/Calcutta IST
------------------new day----------------------
2015-01-09 01:00 Fri Asia/Singapore SGT
2015-01-09 01:00 Fri Asia/Hong_Kong HKT
2015-01-09 02:00 Fri Asia/Tokyo JST
2015-01-09 03:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/13
= Followups =
(needed policy, feature not accepted yet)
#topic #466 recommend Privatedevices and PrivateNetwork in systemd
guidelines
.fpc 466
https://fedorahosted.org/fpc/ticket/466
(needinfo, just package dep?)
#topic #468 Temporary modernizr packing exception for kimchi
.fpc 468
https://fedorahosted.org/fpc/ticket/468
(needs info. don't want all containers to need static ids)
#topic #474 Allocating a soft static uid and gid 389 for dirsrv
.fpc 474
https://fedorahosted.org/fpc/ticket/474
(needs policy)
#topic #475 Suggested Changes for Python Guidelines for F22
.fpc 475
https://fedorahosted.org/fpc/ticket/475
(minor policy changes needed, speak to orionp)
#topic #478 Proposal: Package Guidelines: DevAssistant Assistant packages (DAP)
.fpc 478
https://fedorahosted.org/fpc/ticket/478
(add examples for common libs.)
#topic #480 Packaging guidelines for consistent PKCS#11 usage
.fpc 480
https://fedorahosted.org/fpc/ticket/480
(explain host-independent, and fix name)
#topic #481 static uids systemd-network, systemd-timesync, systemd-resolve
.fpc 481
https://fedorahosted.org/fpc/ticket/481
= Ye Ancient tickets (zombie followups) =
#topic #126 bundling exception for scintilla
.fpc 126
https://fedorahosted.org/fpc/ticket/126
#topic #202 Application for exemption from "No bundling" rule: Gargoyle
.fpc 202
https://fedorahosted.org/fpc/ticket/202
#topic #221 Bundling exception request: numptyphysics and Box2D
.fpc 221
https://fedorahosted.org/fpc/ticket/221
#topic #235 exception for bundling a library into uif2iso package
.fpc 235
https://fedorahosted.org/fpc/ticket/235
#topic #304 asking for bundling exception for the package "rubygem-rdiscount"
.fpc 304
https://fedorahosted.org/fpc/ticket/304
#topic #338 %doc and %_pkgdocdir duplicate files and cause conflicts
.fpc 338
https://fedorahosted.org/fpc/ticket/338
#topic #381 Bundling exception for python-matplotlib fonts
.fpc 381
https://fedorahosted.org/fpc/ticket/381
#topic #412 Please change the packaging guidelines to include packaging
policy regarding systemd timer units
.fpc 412
https://fedorahosted.org/fpc/ticket/412
= Ye Ancient tickets (new) =
#topic #208 Please add policy regarding socket activated services
.fpc 208
https://fedorahosted.org/fpc/ticket/208
#topic #209 Please define policy regarding instantiated application
services
.fpc 209
https://fedorahosted.org/fpc/ticket/209
#topic #443 Requesting Bundling exception for Love (liblove sub package)
.fpc 443
https://fedorahosted.org/fpc/ticket/443
= New business =
#topic #484 Minor PHP Guidelines update (for PSR-4)
.fpc 484
https://fedorahosted.org/fpc/ticket/484
#topic #486 help2man
.fpc 486
https://fedorahosted.org/fpc/ticket/486
#topic #488 [RFC] Please update Python_Eggs packaging guidelines
.fpc 488
https://fedorahosted.org/fpc/ticket/488
#topic #489 Ruby guidelines: Updates for Minitest 5
.fpc 489
https://fedorahosted.org/fpc/ticket/489
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/12
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
More information about the devel
mailing list