Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-06-11 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.

 Local time information (via. rktime):

2015-06-11 09:00 Thu US/Pacific             PDT
2015-06-11 12:00 Thu US/Eastern             EDT
2015-06-11 16:00 Thu UTC <-
2015-06-11 17:00 Thu Europe/London          BST
2015-06-11 18:00 Thu Europe/Paris          CEST
2015-06-11 18:00 Thu Europe/Berlin         CEST
2015-06-11 21:30 Thu Asia/Calcutta          IST
------------------new day----------------------
2015-06-12 00:00 Fri Asia/Singapore         SGT
2015-06-12 00:00 Fri Asia/Hong_Kong         HKT
2015-06-12 01:00 Fri Asia/Tokyo             JST
2015-06-12 02:00 Fri Australia/Brisbane     EST


 Links to all tickets below can be found at: 

https://fedorahosted.org/fpc/report/13

= Followups =

#topic #281     New Python Macros for Easier Packaging
.fpc 281
https://fedorahosted.org/fpc/ticket/281

#topic #508     New GID for openstack-neutron
.fpc 508
https://fedorahosted.org/fpc/ticket/508

#topic #513     Use python -Es in shbang
.fpc 513
https://fedorahosted.org/fpc/ticket/513

#topic #533     Distinguish between packaging modules and applications
                in python packaging
.fpc 533
https://fedorahosted.org/fpc/ticket/533

#topic #539     Procedure for approving package review process exceptions
.fpc 539
https://fedorahosted.org/fpc/ticket/539

= 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/13

 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. 


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to