Schedule for Monday's FESCo Meeting (2018-08-20)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2018-08-20 15:00 UTC'


Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =
Title of issue
https://pagure.io/fesco/issue/###
DECISION (+X, Y, -Z)

= Followups =

#topic #1935 Remove packages which has a consistent bad security
record from the distribution.
.fesco 1935
https://pagure.io/fesco/issue/1935

= New business =

#topic #1955 Let's get rid of filedeps (FESCo edition)
.fesco 1955
https://pagure.io/fesco/issue/1955

#topic #1962 F29 Change: Cloud Provider Image Updates
.fesco 1962
https://pagure.io/fesco/issue/1962

#topic #1964 Nonresponsive maintainer: wolnei (kio-gdrive)
.fesco 1964
https://pagure.io/fesco/issue/1964

#topic #1967 Fedora 29 incomplete changes
.fesco 1967
https://pagure.io/fesco/issue/1967

#topic #1968 Proposed F30 Schedule
.fesco 1968
https://pagure.io/fesco/issue/1968

#topic #1969 Nonresponsive maintainer: dbmacartney
.fesco 1969
https://pagure.io/fesco/issue/1969

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/O2F4L5M2C3LUXPFSIIQD63LLM4XPLZG7/

Schedule for Friday's FESCo Meeting (2018-05-25)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
   http://fedoraproject.org/wiki/UTCHowto

or run:
   date -d '2018-05-25 15:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1890 updating the FTBFS cleanup policy
.fesco 1890
https://pagure.io/fesco/issue/1890

#topic #1892 F29 Self Contained Change: MySQL 8
.fesco 1892
https://pagure.io/fesco/issue/1892

= New business =

#topic #1893 Non-responsive maintainer for libinvm-i18n,libinvm-cli,
libinvm-cim
.fesco 1893
https://pagure.io/fesco/issue/1893

#topic #1894 F29 System Wide Change: Let's Label Our Variants!
.fesco 1894
https://pagure.io/fesco/issue/1894

#topic #1896 Election policy unclear on self-nomination
.fesco 1896
https://pagure.io/fesco/issue/1896

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DM3J7LRCTDUSGJLYECCJX7JV7QTLSCLE/

Re: removal of python2-firewall

[Adam Miller]

On Wed, May 23, 2018 at 4:52 PM Miro Hrončok  wrote:

> On 23.5.2018 22:51, Martin Bukatovic wrote:
> > What do you think? Do we want to continue dropping python2 modules and
> > encourage people to reconfigure ansible to run under python 3 while
> > shipping ansible with python 2 or do we want to keep python2 modules
> > used by ansible available, even thouhg this is not easy to track right
> > now?

> I think that we can drop them from Fedora 29, where Ansible switches to
> Python 3:

> https://fedoraproject.org/wiki/Changes/Ansible_python3_default

> Removal from Fedora 28 was indeed a bad move, however, as said, the
> maintainer here probably had no idea that it may break Ansible, since
> the dependency is not tracked.

+1 - Once Fedora 29 lands, I think that makes sense.


> Do we need to reintroduce it?


I think from a Fedora user perspective, it would be nice to reintroduce it
for Fedora 28 just because Ansible is still shipping python2 by default.
Retiring python2-firewall in Fedora 29 makes sense given the impending
change to Ansible being python3 only. However from an upstream Ansible
perspective, if there is a strong case not to re-introduce it in Fedora
then I don't have a hard preference because it's relatively easy to direct
users to the module documentation informing them of the change and the need
to use python3 mode (which is now even more clear on the specific issue
thanks to the results of the bugzilla referenced previously in this thread).

-AdamM

> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> python-devel mailing list -- python-devel@lists.fedoraproject.org
> To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/FGNAZCSIEDSHU5RF5BLZASBP4NYSGS7S/
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/message/NSCBZQT6AFJG65L4E3KAHM55ANQLNAP2/

Schedule for Friday's FESCo Meeting (2018-04-20)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2018-04-20 15:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1868 Change the Changes template
.fesco 1868
https://pagure.io/fesco/issue/1868

#topic #1872 Disable Test Gating requirements until more UI is enabled
.fesco 1872
https://pagure.io/fesco/issue/1872

#topic #1876 Please orphan all LXQt packages / nonresponsive
maintainer heliocastro
.fesco 1876
https://pagure.io/fesco/issue/1876

= New business =

#topic #1880 Request to take over a package - 3+ weeks have passed
.fesco 1880
https://pagure.io/fesco/issue/1880

#topic #1882 F28 Self Contained Change: java-openjdk 10 - rolling
release for Short Term Support releases of OpenJDK
.fesco 1882
https://pagure.io/fesco/issue/1882

#topic #1883 Request for rebase of libdnf/dnf after Fedora 28 GA
.fesco 1883
https://pagure.io/fesco/issue/1883

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2018-01-19)

[Adam Miller]

  (+1:7, -1:0, +0:0)  (maxamillion, 17:39:05)

* #1831 F28 System Wide Change: OpenLDAP defaults to use only Shared
  System Certificates  (maxamillion, 17:39:24)
  * LINK: https://pagure.io/fesco/issue/1831   (maxamillion, 17:39:24)
  * AGREED: APPROVE - F28 System Wide Change: OpenLDAP defaults to use
only Shared System Certificates (+1:7, -1:0, +0:0)  (maxamillion,
17:41:35)

* #1832 F28 System Wide Change: OpenLDAP without Non-threaded Libraries
  (maxamillion, 17:41:52)
  * LINK: https://pagure.io/fesco/issue/1832   (maxamillion, 17:41:52)
  * AGREED: APPROVE - F28 System Wide Change: OpenLDAP without
Non-threaded Libraries (+1:7, -1:0, +0:0)  (maxamillion, 17:46:08)

* #1833 F28 System Wide Change: Replace glibc's libcrypt with libxcrypt
  (maxamillion, 17:46:20)
  * LINK: https://pagure.io/fesco/issue/1833   (maxamillion, 17:46:21)
  * AGREED: APPROVE - F28 System Wide Change:  Replace glibc's libcrypt
with libxcrypt  (+1:7, -1:0, +0:0)  (maxamillion, 17:52:04)

* #1834 F28 System Wide Change: Rename "nobody" user  (maxamillion,
  17:52:20)
  * LINK: https://pagure.io/fesco/issue/1834   (maxamillion, 17:52:20)
  * AGREED: APPROVE - F28 System Wide Change:  Rename "nobody" user
(+1:6,  +0.5:1, -1:0, +0:0)  (maxamillion, 18:02:26)

* Next week's chair  (maxamillion, 18:03:05)
  * jforbes to Chair meeting on February 2 as many FESCo members will be
away next Friday  (maxamillion, 18:04:40)
  * ACTION: jforbes to Chair meeting on February 2 as many FESCo members
will be away next Friday  (maxamillion, 18:04:55)

* Open Floor  (maxamillion, 18:04:59)
  * We're still in the middle of elections if anyone hasn't voted yet
(maxamillion, 18:05:38)

Meeting ended at 18:07:36 UTC.




Action Items

* jforbes to Chair meeting on February 2 as many FESCo members will be
  away next Friday




Action Items, by person
---
* jforbes
  * jforbes to Chair meeting on February 2 as many FESCo members will be
away next Friday
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (204)
* bowlofeggs (54)
* dgilmore (53)
* jforbes (42)
* nirik (41)
* jsmith (38)
* zodbot (35)
* otaylor (30)
* sgallagh (29)
* kalev (29)
* langdon (10)
* mattdm (10)
* puiterwijk (7)
* kalev-afk (2)
* rdieter (1)
* Southern_Gentlem (1)
* tyll (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


On Thu, Jan 18, 2018 at 2:13 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2018-01-19 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = New business =
>
> = New business =
>
> #topic #1767 F28 Self Contained Changes
> .fesco 1767
> https://pagure.io/fesco/issue/1767
>
> #topic #1803 F28 System Wide Change: Reduce Initial Setup Redundancy
> .fesco 1803
> https://pagure.io/fesco/issue/1803
>
> #topic #1814 F28 System Wide Change: Anaconda Modularization
> .fesco 1814
> https://pagure.io/fesco/issue/1814
>
> #topic #1815 F28 System Wide Change: Make authselect default tool
> instead of authconfig
> .fesco 1815
> https://pagure.io/fesco/issue/1815
>
> #topic #1816 F28 System Wide Change: Glibc collation update and sync with cldr
> .fesco 1816
> https://pagure.io/fesco/issue/1816
>
> #topic #1817 F28 System Wide Change: golang 1.10
> .fesco 1817
> https://pagure.io/fesco/issue/1817
>
> #topic #1818 F28 System Wide Change: Kerberos in Python modernization
> .fesco 1818
> https://pagure.io/fesco/issue/1818
>
> #topic #1819 F28 System Wide Change: Removal of Sun RPC Interfaces from glibc
> .fesco 1819
> https://pagure.io/fesco/issue/1819
>
> #topic #1822 F28 System Wide Change: AArch64 Server Promotion
> .fesco 1822
> https://pagure.io/fesco/issue/1822
>
> #topic #1823 F28 System Wide Change: mpfr-4.0.0
> .fesco 1823
> https://pagure.io/fesco/issue/1823
>
> #topic #1824 F28 System Wide Change: Binutils version 2.29.1
> .fesco 1824
> https://pagure.io/fesco/issue/1824
>
> #topic #1825 F28 System Wide Change: Add-On Modularity
> .fesco 1825
> https://pagure.io/fesco/issue/1825
>
> #topic #1826 F28 System Wide Change: Boost 1.66 upgrade
> .fesco 1826
> https://pagure.io/fesco/issue/1826
>
> #topic #1827 F28 System Wide Change: GCC8
> .fesco 1827
> https://pagure.io/fesco/issue/1827
>
> #topic #1828 F28 System Wide Change: The GNU C Library version 2.27
> .fesco 1828
> https://pagure.io/fesco/issue/1828
>
> #topic #1829 F28 System 

Schedule for Friday's FESCo Meeting (2018-01-19)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2018-01-19 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= New business =

= New business =

#topic #1767 F28 Self Contained Changes
.fesco 1767
https://pagure.io/fesco/issue/1767

#topic #1803 F28 System Wide Change: Reduce Initial Setup Redundancy
.fesco 1803
https://pagure.io/fesco/issue/1803

#topic #1814 F28 System Wide Change: Anaconda Modularization
.fesco 1814
https://pagure.io/fesco/issue/1814

#topic #1815 F28 System Wide Change: Make authselect default tool
instead of authconfig
.fesco 1815
https://pagure.io/fesco/issue/1815

#topic #1816 F28 System Wide Change: Glibc collation update and sync with cldr
.fesco 1816
https://pagure.io/fesco/issue/1816

#topic #1817 F28 System Wide Change: golang 1.10
.fesco 1817
https://pagure.io/fesco/issue/1817

#topic #1818 F28 System Wide Change: Kerberos in Python modernization
.fesco 1818
https://pagure.io/fesco/issue/1818

#topic #1819 F28 System Wide Change: Removal of Sun RPC Interfaces from glibc
.fesco 1819
https://pagure.io/fesco/issue/1819

#topic #1822 F28 System Wide Change: AArch64 Server Promotion
.fesco 1822
https://pagure.io/fesco/issue/1822

#topic #1823 F28 System Wide Change: mpfr-4.0.0
.fesco 1823
https://pagure.io/fesco/issue/1823

#topic #1824 F28 System Wide Change: Binutils version 2.29.1
.fesco 1824
https://pagure.io/fesco/issue/1824

#topic #1825 F28 System Wide Change: Add-On Modularity
.fesco 1825
https://pagure.io/fesco/issue/1825

#topic #1826 F28 System Wide Change: Boost 1.66 upgrade
.fesco 1826
https://pagure.io/fesco/issue/1826

#topic #1827 F28 System Wide Change: GCC8
.fesco 1827
https://pagure.io/fesco/issue/1827

#topic #1828 F28 System Wide Change: The GNU C Library version 2.27
.fesco 1828
https://pagure.io/fesco/issue/1828

#topic #1829 F28 System Wide Change: The GNU C Library version 2.27
.fesco 1829
https://pagure.io/fesco/issue/1829

#topic #1830 F28 System Wide Change: NIS switching to new libnsl to support IPv6
.fesco 1830
https://pagure.io/fesco/issue/1830

#topic #1831 F28 System Wide Change: OpenLDAP defaults to use only
Shared System Certificates
.fesco 1831
https://pagure.io/fesco/issue/1831

#topic #1832 F28 System Wide Change: OpenLDAP without Non-threaded Libraries
.fesco 1832
https://pagure.io/fesco/issue/1832

#topic #1833 F28 System Wide Change: Replace glibc's libcrypt with libxcrypt
.fesco 1833
https://pagure.io/fesco/issue/1833

#topic #1834 F28 System Wide Change: Rename "nobody" user
.fesco 1834
https://pagure.io/fesco/issue/1834

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out today[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

Note that the "latest" tag currently points to "27" and the "rawhide"
tag currently points to "28", if no tag is provided in your pull
command then it will always default to "latest"

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25

Updated/Released Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are releasing for the f26 and f27 namespaces.)

registry.fedoraproject.org/f27/kubernetes-master:0-2.f27container
registry.fedoraproject.org/f27/kubernetes-master:0
registry.fedoraproject.org/f27/kubernetes-master
registry.fedoraproject.org/f27/kubernetes-node:0-2.f27container
registry.fedoraproject.org/f27/kubernetes-node:0
registry.fedoraproject.org/f27/kubernetes-node
registry.fedoraproject.org/f27/kubernetes-scheduler:0-2.f27container,
registry.fedoraproject.org/f27/kubernetes-scheduler:0,
registry.fedoraproject.org/f27/kubernetes-scheduler,
registry.fedoraproject.org/f27/kubernetes-apiserver:0-2.f27container,
registry.fedoraproject.org/f27/kubernetes-apiserver:0,
registry.fedoraproject.org/f27/kubernetes-apiserver,
registry.fedoraproject.org/f27/kubernetes-proxy:0-2.f27container,
registry.fedoraproject.org/f27/kubernetes-proxy:0,
registry.fedoraproject.org/f27/kubernetes-proxy,
registry.fedoraproject.org/f27/kubernetes-controller-manager:0-2.f27container,
registry.fedoraproject.org/f27/kubernetes-controller-manager:0,
registry.fedoraproject.org/f27/kubernetes-controller-manager,
registry.fedoraproject.org/f27/kubernetes-kubelet:0-2.f27container,
registry.fedoraproject.org/f27/kubernetes-kubelet:0,
registry.fedoraproject.org/f27/kubernetes-kubelet


registry.fedoraproject.org/f26/kubernetes-scheduler:0-5.f26container
registry.fedoraproject.org/f26/kubernetes-scheduler:0
registry.fedoraproject.org/f26/kubernetes-scheduler
registry.fedoraproject.org/f26/nodejs:0-5.f26container
registry.fedoraproject.org/f26/nodejs:0
registry.fedoraproject.org/f26/nodejs
registry.fedoraproject.org/f26/kubernetes-apiserver:0-5.f26container
registry.fedoraproject.org/f26/kubernetes-apiserver:0
registry.fedoraproject.org/f26/kubernetes-apiserver
registry.fedoraproject.org/f26/tools:0-4.f26container
registry.fedoraproject.org/f26/tools:0
registry.fedoraproject.org/f26/tools
registry.fedoraproject.org/f26/httpd:0-1.f26container
registry.fedoraproject.org/f26/httpd:0
registry.fedoraproject.org/f26/httpd
registry.fedoraproject.org/f26/php:0-5.f26container
registry.fedoraproject.org/f26/php:0
registry.fedoraproject.org/f26/php
registry.fedoraproject.org/f26/kubernetes-proxy:0-5.f26container
registry.fedoraproject.org/f26/kubernetes-proxy:0
registry.fedoraproject.org/f26/kubernetes-proxy
registry.fedoraproject.org/f26/redis:0-5.f26container
registry.fedoraproject.org/f26/redis:0
registry.fedoraproject.org/f26/redis
registry.fedoraproject.org/f26/s2i-base:1-12.f26container
registry.fedoraproject.org/f26/s2i-base:1
registry.fedoraproject.org/f26/s2i-base
registry.fedoraproject.org/f26/etcd:0-9.f26container
registry.fedoraproject.org/f26/etcd:0
registry.fedoraproject.org/f26/etcd
registry.fedoraproject.org/f26/flannel:0-8.f26container
registry.fedoraproject.org/f26/flannel:0
registry.fedoraproject.org/f26/flannel
registry.fedoraproject.org/f26/kubernetes-controller-manager:0-5.f26container
registry.fedoraproject.org/f26/kubernetes-controller-manager:0
registry.fedoraproject.org/f26/kubernetes-controller-manager
registry.fedoraproject.org/f26/python-classroom:0.3-5.f26container
registry.fedoraproject.org/f26/python-classroom:0.3
registry.fedoraproject.org/f26/python-classroom
registry.fedoraproject.org/f26/mongodb:0-5.f26container
registry.fedoraproject.org/f26/mongodb:0
registry.fedoraproject.org/f26/mongodb
registry.fedoraproject.org/f26/mirrormanager2-mirrorlist:0.7.3-12.f26container
registry.fedoraproject.org/f26/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f26/mirrormanager2-mirrorlist
registry.fedoraproject.org/f26/waiverdb:0-7.f26container
registry.fedoraproject.org/f26/waiverdb:0
registry.fedoraproject.org/f26/waiverdb
registry.fedoraproject.org/f26/cockpit:135-15.f26container
registry.fedoraproject.org/f26/cockpit:135
registry.fedoraproject.org/f26/cockpit
registry.fedoraproject.org/f26/docker-distribution:2.5.1-5.f26container
registry.fedoraproject.org/f26/docker-distribution:2.5.1
registry.fedoraproject.org/f26/docker-distribution
registry.fedoraproject.org/f26/mariadb:10.1-13.f26container
registry.fedoraproject.org/f26/mariadb:10.1
registry.fedoraproject.org/f26/mariadb

Summary/Minutes for today's FESCo meeting (2017-11-03)

[Adam Miller]

===
#fedora-meeting: FESCO (2017-11-03)
===


Meeting started by maxamillion at 16:00:41 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-11-03/fesco.2017-11-03-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:43)

* Follow Ups  (maxamillion, 16:04:09)

* #1786 Non-responsive maintainer: jcapik  (maxamillion, 16:04:13)
  * LINK: https://pagure.io/fesco/issue/1786   (maxamillion, 16:04:14)
  * AGREED: Proposal: Wait until Post F27 GA to orphan jcapik's packages
(+1:7, +0:0, -1:0)  (maxamillion, 16:19:26)

* #1788 Default path for root is inconsistent between su - and sudo
  (maxamillion, 16:19:36)
  * LINK: https://pagure.io/fesco/issue/1788   (maxamillion, 16:19:37)
  * AGREED: Proposal: Discuss on the mailing list and in ticket, vote at
next week's FESCo meeting based on feedback (+1:7, +0:0, -1:0)
(maxamillion, 16:54:37)

* #1789 F28 System Wide Change: NSS Default File Format SQL
  (maxamillion, 16:54:43)
  * LINK: https://pagure.io/fesco/issue/1789   (maxamillion, 16:54:44)
  * AGREED: Approved: F28 System Wide Change: NSS Default File Format
SQL (+1:7, +0:0, -1:0)  (maxamillion, 16:58:05)

* Next week's chair  (maxamillion, 16:58:16)
  * bowlofeggs to chair next week's FESCo Meeting 2017-11-10
(maxamillion, 16:58:49)

* Open Floor  (maxamillion, 16:58:53)
  * LINK:

https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee#Meetings
(tyll, 17:01:30)

Meeting ended at 17:08:30 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (88)
* nirik (40)
* bowlofeggs (29)
* jforbes (29)
* tyll (24)
* kalev (22)
* zodbot (15)
* jsmith (8)
* sgallagh (1)
* dgilmore (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



On Fri, Nov 3, 2017 at 2:53 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> On Thu, Nov 2, 2017 at 2:52 PM, Jan Kurik <jku...@redhat.com> wrote:
>> There is one more issue I would like to ask FESCo to review:
>>
>> #topic Proposal for 3 week freeze
>> .fesco 1790
>> https://pagure.io/fesco/issue/1790
>
> My apologies, this was missed for todays meeting.
>
> -AdamM
>
>>
>> Thanks,
>> Jan
>>
>> On Thu, Nov 2, 2017 at 8:28 PM, Adam Miller
>> <maxamill...@fedoraproject.org> wrote:
>>> Following is the list of topics that will be discussed in the
>>> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
>>> irc.freenode.net.
>>>
>>> To convert UTC to your local time, take a look at
>>>   http://fedoraproject.org/wiki/UTCHowto
>>>
>>> or run:
>>>   date -d '2017-11-03 16:00 UTC'
>>>
>>>
>>> Links to all issues below can be found at:
>>> https://pagure.io/fesco/report/meeting_agenda
>>>
>>> = Follow Ups =
>>>
>>> #topic #1786 Non-responsive maintainer: jcapik
>>> .fesco 1786
>>> https://pagure.io/fesco/issue/1786
>>>
>>> = New business =
>>>
>>> #topic #1788 Default path for root is inconsistent between su - and sudo
>>> .fesco 1788
>>> https://pagure.io/fesco/issue/1788
>>>
>>> #topic #1789 F28 System Wide Change: NSS Default File Format SQL
>>> .fesco 1789
>>> https://pagure.io/fesco/issue/1789
>>>
>>>
>>> = Open Floor =
>>>
>>> For more complete details, please visit each individual
>>> issue.  The report of the agenda items can be found at
>>> https://pagure.io/fesco/report/meeting_agenda
>>>
>>> If you would like to add something to this agenda, you can
>>> reply to this e-mail, file a new issue at
>>> https://pagure.io/fesco, 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
>>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>
>>
>>
>> --
>> Jan Kuřík
>> Platform & Fedora Program Manager
>> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2017-11-03)

[Adam Miller]

On Thu, Nov 2, 2017 at 2:52 PM, Jan Kurik <jku...@redhat.com> wrote:
> There is one more issue I would like to ask FESCo to review:
>
> #topic Proposal for 3 week freeze
> .fesco 1790
> https://pagure.io/fesco/issue/1790

My apologies, this was missed for todays meeting.

-AdamM

>
> Thanks,
> Jan
>
> On Thu, Nov 2, 2017 at 8:28 PM, Adam Miller
> <maxamill...@fedoraproject.org> wrote:
>> Following is the list of topics that will be discussed in the
>> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
>> irc.freenode.net.
>>
>> To convert UTC to your local time, take a look at
>>   http://fedoraproject.org/wiki/UTCHowto
>>
>> or run:
>>   date -d '2017-11-03 16:00 UTC'
>>
>>
>> Links to all issues below can be found at:
>> https://pagure.io/fesco/report/meeting_agenda
>>
>> = Follow Ups =
>>
>> #topic #1786 Non-responsive maintainer: jcapik
>> .fesco 1786
>> https://pagure.io/fesco/issue/1786
>>
>> = New business =
>>
>> #topic #1788 Default path for root is inconsistent between su - and sudo
>> .fesco 1788
>> https://pagure.io/fesco/issue/1788
>>
>> #topic #1789 F28 System Wide Change: NSS Default File Format SQL
>> .fesco 1789
>> https://pagure.io/fesco/issue/1789
>>
>>
>> = Open Floor =
>>
>> For more complete details, please visit each individual
>> issue.  The report of the agenda items can be found at
>> https://pagure.io/fesco/report/meeting_agenda
>>
>> If you would like to add something to this agenda, you can
>> reply to this e-mail, file a new issue at
>> https://pagure.io/fesco, 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
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
>
> --
> Jan Kuřík
> Platform & Fedora Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2017-11-03)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-11-03 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Follow Ups =

#topic #1786 Non-responsive maintainer: jcapik
.fesco 1786
https://pagure.io/fesco/issue/1786

= New business =

#topic #1788 Default path for root is inconsistent between su - and sudo
.fesco 1788
https://pagure.io/fesco/issue/1788

#topic #1789 F28 System Wide Change: NSS Default File Format SQL
.fesco 1789
https://pagure.io/fesco/issue/1789


= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2017-10-13)

[Adam Miller]

On Thu, Oct 12, 2017 at 3:43 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-10-13 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> These are considered followups because we didn't have a meeting last week and
> they were on the agenda then
>
> #topic #1779 Consider fedora-* initscript units
> .fesco 1779
> https://pagure.io/fesco/issue/1779
>
> #topic #1780 F28 System Wide Change: Annobin
> .fesco 1780
> https://pagure.io/fesco/issue/1780
>
> = New business =
>
> #topic #1767 F28 Self Contained Changes - Facter 3
> .fesco 1767
> https://pagure.io/fesco/issue/1767#comment-471878
>
> #topic #1775 f27 modular server release planning
> .fesco 1775
> https://pagure.io/fesco/issue/1775
>
> #topic #1780 F28 System Wide Change: Annobin
> .fesco 1780
> https://pagure.io/fesco/issue/1780
>
> #topic #1781 qt5-qtwebengine maintainership, kde-sig access rights
> .fesco 1781
> https://pagure.io/fesco/issue/1781
>
> #topic #1782 use of updates-testing for testing of non-update software
> .fesco 1782
> https://pagure.io/fesco/issue/1782
>
> #topic #1783 Firefox 57 and the Updates Policy
> .fesco 1783
> https://pagure.io/fesco/issue/1783
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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.

===
#fedora-meeting: FESCO (2017-10-13)
===


Meeting started by maxamillion at 16:01:43 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-10-13/fesco.2017-10-13-16.01.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:01:46)

* Follow Ups  (maxamillion, 16:04:23)

* #1779 Consider fedora-* initscript units  (maxamillion, 16:04:28)
  * LINK: https://pagure.io/fesco/issue/1779   (maxamillion, 16:04:28)
  * LINK:

https://pagure.io/fork/zbyszek/fedora-release/c/c0dbaabb816ac181e79f07244dc461f4ef65d86d
(nirik, 16:06:21)
  * AGREED: Proposal: Based on latest BZ update, ask if FESCo is still
needed in the process and defer to next week if needed (+1:8, -1:0,
+0:0)  (maxamillion, 16:21:41)

* #1780 F28 System Wide Change: Annobin  (maxamillion, 16:21:48)
  * LINK: https://pagure.io/fesco/issue/1780   (maxamillion, 16:21:49)
  * LINK: https://pagure.io/releng/issue/7069 doesn'thave comments from
releng yet either  (bowlofeggs, 16:26:52)
  * AGREED: APPROVED: F28 System Wide Change: Annobin (+1:8, -1:0, +0:0)
(maxamillion, 16:31:11)

* New Business  (maxamillion, 16:31:40)

* #1767 F28 Self Contained Changes - Facter 3  (maxamillion, 16:31:42)
  * LINK: https://pagure.io/fesco/issue/1767#comment-471878
(maxamillion, 16:31:42)
  * LINK: https://docs.puppet.com/facter/3.0/release_notes.html "
(jsmith, 16:33:31)
  * AGREED: Self Contained Changes - Facter 3 (+1:7, -1:0, +0:1)
(maxamillion, 16:37:06)

* #1775 f27 modular server release planning  (maxamillion, 16:37:18)
  * LINK: https://pagure.io/fesco/issue/1775   (maxamillion, 16:37:18)
  * AGREED: : Add a presumed one-week slip to be the Rain Date; slip
Final if that isn't achieved. (+1:8, -1:0, +0:0)  (maxamillion,
16:43:24)

* #1781 qt5-qtwebengine maintainership, kde-sig access rights
  (maxamillion, 16:43:36)
  * LINK: https://pagure.io/fesco/issue/1781   (maxamillion, 16:43:36)
  * AGREED: Proposal: We add KDE SIG as a comaintainer. In general, it
will require 2 KDE SIG members to approve a Pull Request. In the
event that Kevin still refuses, an additional 2 may overrule him.
(+1:8, -1:0, +0:0)  (maxamillion, 17:33:26)

* #1782 use of updates-testing for testing of non-update software
  (maxamillion, 17:34:18)
  * LINK: https://pagure.io/fesco/issue/1782   (maxamillion, 17:34:19)
  * jforbes will create a Policy change proposal to be voted on next
week  (maxamillion, 17:41:53)

* #1783 Firefox 57 and the Updates Policy  (maxamillion, 17:42:42)
  * LINK: https://pagure.io/fesco/issue/1783   (maxamillion, 17:42:43)
  * AGREED: firefox 57beta is removed from f25/f26 updates-testing but
stays in f27/rawhide. When final it out, ma

Schedule for Friday's FESCo Meeting (2017-10-13)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-10-13 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

These are considered followups because we didn't have a meeting last week and
they were on the agenda then

#topic #1779 Consider fedora-* initscript units
.fesco 1779
https://pagure.io/fesco/issue/1779

#topic #1780 F28 System Wide Change: Annobin
.fesco 1780
https://pagure.io/fesco/issue/1780

= New business =

#topic #1767 F28 Self Contained Changes - Facter 3
.fesco 1767
https://pagure.io/fesco/issue/1767#comment-471878

#topic #1775 f27 modular server release planning
.fesco 1775
https://pagure.io/fesco/issue/1775

#topic #1780 F28 System Wide Change: Annobin
.fesco 1780
https://pagure.io/fesco/issue/1780

#topic #1781 qt5-qtwebengine maintainership, kde-sig access rights
.fesco 1781
https://pagure.io/fesco/issue/1781

#topic #1782 use of updates-testing for testing of non-update software
.fesco 1782
https://pagure.io/fesco/issue/1782

#topic #1783 Firefox 57 and the Updates Policy
.fesco 1783
https://pagure.io/fesco/issue/1783

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Schedule for Tomorrow's FESCo Meeting (2017-09-15)

[Adam Miller]

On Thu, Sep 14, 2017 at 11:37 AM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-09-15 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> #topic 32 bit UEFI Support
> (doesn't have a FESCo Ticket but was brough up last meeting)
> .link https://bugzilla.redhat.com/show_bug.cgi?id=1474861
> .link https://fedoraproject.org//wiki/Changes/32BitUefiSupport
>
> #topic #1737 Proposal: i686 SIG needs to be functional by F27
> .fesco 1737
> https://pagure.io/fesco/issue/1737
>
> #topic #1760 F27 approved Changes not in MODIFIED status (considered
> as not testable)
> .fesco 1760
> https://pagure.io/fesco/issue/1760
>
> #topic #1773 F27 Changes not in ON_QA status (<100% completed)
> .fesco 1773
> https://pagure.io/fesco/issue/1773

One more to add to follow-ups as more information came to light since
our previous decision was made:

#topic #1770 Allow PRs for non-packagers
.fesco 1770
https://pagure.io/fesco/issue/1770

>
> = New business =
>
> #topic #1767 F28 Self Contained Changes
> .fesco 1767
> https://pagure.io/fesco/issue/1767
>
> #topic #1774 Treat Developer-only Stream for Fedora Atomic Host as
> non-Released Fedora artifacts
> .fesco 1774
> https://pagure.io/fesco/issue/1774
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Tomorrow's FESCo Meeting (2017-09-15)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-09-15 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic 32 bit UEFI Support
(doesn't have a FESCo Ticket but was brough up last meeting)
.link https://bugzilla.redhat.com/show_bug.cgi?id=1474861
.link https://fedoraproject.org//wiki/Changes/32BitUefiSupport

#topic #1737 Proposal: i686 SIG needs to be functional by F27
.fesco 1737
https://pagure.io/fesco/issue/1737

#topic #1760 F27 approved Changes not in MODIFIED status (considered
as not testable)
.fesco 1760
https://pagure.io/fesco/issue/1760

#topic #1773 F27 Changes not in ON_QA status (<100% completed)
.fesco 1773
https://pagure.io/fesco/issue/1773

= New business =

#topic #1767 F28 Self Contained Changes
.fesco 1767
https://pagure.io/fesco/issue/1767

#topic #1774 Treat Developer-only Stream for Fedora Atomic Host as
non-Released Fedora artifacts
.fesco 1774
https://pagure.io/fesco/issue/1774

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[no subject]

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out today[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

(Note that the "latest" tag currently points to "26" and the "rawhide"
tag currently points to "28", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:28
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25

registry.fedoraproject.org/fedora-minimal:latest
registry.fedoraproject.org/fedora-minimal:rawhide
registry.fedoraproject.org/fedora-minimal:28
registry.fedoraproject.org/fedora-minimal:27
registry.fedoraproject.org/fedora-minimal:26
registry.fedoraproject.org/fedora-minimal:25

Updated/Released Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are releasing for the f25 and f26 namespaces.)

registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/nodejs:0-8.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/httpd:0-10.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/php:0-7.f25container
registry.fedoraproject.org/f25/php:0
registry.fedoraproject.org/f25/php
registry.fedoraproject.org/f25/container-engine:0-3.f25container
registry.fedoraproject.org/f25/container-engine:0
registry.fedoraproject.org/f25/container-engine
registry.fedoraproject.org/f25/kubernetes-proxy:0-18.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/redis:0-8.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-18.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mongodb:0-7.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-10.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/waiverdb:0-3.f25container
registry.fedoraproject.org/f25/waiverdb:0
registry.fedoraproject.org/f25/waiverdb
registry.fedoraproject.org/f25/cockpit:135-13.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/mariadb:10.1-16.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/ruby:0-11.f25docker
registry.fedoraproject.org/f25/ruby:0
registry.fedoraproject.org/f25/ruby
registry.fedoraproject.org/f25/s2i-base:1-16.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/flannel:0.1-15.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel
registry.fedoraproject.org/f25/kubernetes-master:0.1-20.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/toolchain:1-14.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-node:0.1-17.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-kubelet:0-17.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/docker:0-7.f25container
registry.fedoraproject.org/f25/docker:0
registry.fedoraproject.org/f25/docker


registry.fedoraproject.org/f26/kubernetes-scheduler:0-2.f26container
registry.fedoraproject.org/f26/kubernetes-scheduler:0
registry.fedoraproject.org/f26/kubernetes-scheduler
registry.fedoraproject.org/f26/nodejs:0-3.f26container
registry.fedoraproject.org/f26/nodejs:0
registry.fedoraproject.org/f26/nodejs

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out today[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

(Note that the "latest" tag currently points to "26" and the "rawhide"
tag currently points to "28", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:28
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25

registry.fedoraproject.org/fedora-minimal:latest
registry.fedoraproject.org/fedora-minimal:rawhide
registry.fedoraproject.org/fedora-minimal:28
registry.fedoraproject.org/fedora-minimal:27
registry.fedoraproject.org/fedora-minimal:26
registry.fedoraproject.org/fedora-minimal:25

Updated/Released Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are releasing for the f25 and f26 namespaces.)

registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/nodejs:0-8.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/httpd:0-10.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/php:0-7.f25container
registry.fedoraproject.org/f25/php:0
registry.fedoraproject.org/f25/php
registry.fedoraproject.org/f25/container-engine:0-3.f25container
registry.fedoraproject.org/f25/container-engine:0
registry.fedoraproject.org/f25/container-engine
registry.fedoraproject.org/f25/kubernetes-proxy:0-18.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/redis:0-8.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-18.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mongodb:0-7.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-10.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/waiverdb:0-3.f25container
registry.fedoraproject.org/f25/waiverdb:0
registry.fedoraproject.org/f25/waiverdb
registry.fedoraproject.org/f25/cockpit:135-13.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/mariadb:10.1-16.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/ruby:0-11.f25docker
registry.fedoraproject.org/f25/ruby:0
registry.fedoraproject.org/f25/ruby
registry.fedoraproject.org/f25/s2i-base:1-16.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/flannel:0.1-15.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel
registry.fedoraproject.org/f25/kubernetes-master:0.1-20.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/toolchain:1-14.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-node:0.1-17.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-kubelet:0-17.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/docker:0-7.f25container
registry.fedoraproject.org/f25/docker:0
registry.fedoraproject.org/f25/docker


registry.fedoraproject.org/f26/kubernetes-scheduler:0-2.f26container
registry.fedoraproject.org/f26/kubernetes-scheduler:0
registry.fedoraproject.org/f26/kubernetes-scheduler
registry.fedoraproject.org/f26/nodejs:0-3.f26container
registry.fedoraproject.org/f26/nodejs:0
registry.fedoraproject.org/f26/nodejs

Schedule for Friday's FESCo Meeting (2017-08-25)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-08-25 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1763 Fedora Modules Guidelines and Process
.fesco 1763
https://pagure.io/fesco/issue/1763

#topic #1765 Proposed Fedora 28 schedule
.fesco 1765
https://pagure.io/fesco/issue/1765

= New business =

#topic #1761 Update of "Fedora Release Live Cycle" and "Changes / Policy"
.fesco 1761
https://pagure.io/fesco/issue/1761

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [Modularity]: Service levels and EOL expectations?

[Adam Miller]

On Tue, Aug 8, 2017 at 10:21 AM, Matthew Miller
 wrote:
> On Tue, Aug 08, 2017 at 10:38:15AM -0400, Przemek Klosowski wrote:
>> >Yeah, that would get crazy fast. The 6 month granularity proposal
>> >should help*some*, and we should probably go into this carefully.
>>
>> Technically, the SL for the module could have the narrow meaning
>> referring to the module only, and the tools could follow the chain
>> of dependencies and display it as:
>>
>> Service Level: 6 months (effective SL: 3 months/EOL: 2017-11-08 due
>> to dependency on openSSL)
>
> Ouch. Yes, but I think that that should be a warning sent to the module
> maintainers (and collectively to devel list) rather than show to end
> users.
>

I think this data needs to be displayed to users. As a sysadmin, I
would absolutely want that information available to me similar to how
I am able to check/view security update information with 'dnf
updateinfo'.

-AdamM

>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [Ambassadors] Elections July/August 2017 to FESCo, Council, FAmSCo - Campaign period has started

[Adam Miller]

On Mon, Jul 31, 2017 at 7:25 PM, Jan Kurik  wrote:
> The Nomination period of Elections to Council [1], FESCo [2] and
> FAmSCo [3] is now over.
> The list of nominees follows:
>
> == Council (1 open seat) ==
> * Justin W. Flory (jwf / jflory7)
> * Langdon White (langdon)
> * Nick Bebout (nb)
> * Dennis Gilmore (dgilmore / ausil)
> * Till Maas (tyll / till)
>
> == FESCo (4 open seats) ==
> * Dominik Mierzejewski (Rathann/rathann)
> * Stephen Gallagher (sgallagh/sgallagh)
> * Randy Barlow (bowlofeggs/bowlofeggs)
> * Dennis Gilmore (dgilmore / ausil)
> * Till Maas (tyll / till)
>

I would like to run for FESCo again, but was out of town and in the
mountains without internet connectivity during the nomination time
period. Upon recommendation of jkurik I have filed a ticket with
Fedora Council requesting an exception be granted to add me to the
ballot and submit this email with statement of intent as well as a
link to the ticket I filed.

https://pagure.io/Fedora-Council/tickets/issue/131

Thank you,
-AdamM

> == FAmSCo (3 open seats) ==
> * Itamar Reis Peixoto (itamarjp/itamarjp)
> * Alex Oviedo Solis (alexove/alexove)
> * Eduardo Echeverria (echevemaster/echevemaster)
> * Eduard Lucena (x3mboy)
> * Sumantro Mukherjee (sumantro / sumantrom)
> * Andrew Ward (award3535)
> * Daniel Lara (danniel/Danniel)
> * Sirko Kemter (gnokii/gnokii)
> * Ben Williams (Southern_Gentlem/jbwillia)
> * Nick Bebout (nb/nb)
>
>
> Nominees can now start with their own campaign, to attract people in
> the Fedora community. I am also going to work with nominees and with
> people from CommOps team to prepare Community Blog for publishing
> answers from nominees on collected questions in the Election's
> Questionnaire [4].
>
> I wish all the nominees good luck and a lot of fun during the campaign period.
>
> [1] https://fedoraproject.org/wiki/Council/Nominations
> [2] https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
> [3] https://fedoraproject.org/wiki/FAmSCo_nominations
> [4] https://fedoraproject.org/wiki/Elections/Questionnaire
>
> Regards,
> Jan
> --
> Jan Kuřík
> Platform & Fedora Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
> ___
> ambassadors mailing list -- ambassad...@lists.fedoraproject.org
> To unsubscribe send an email to ambassadors-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out today[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25

Updated/Released Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are releasing for the f25 and f26 namespaces.)

registry.fedoraproject.org/f25/ruby:0-10.f25docker
registry.fedoraproject.org/f25/ruby:0
registry.fedoraproject.org/f25/ruby
registry.fedoraproject.org/f25/kubernetes-master:0.1-18.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/kubernetes-kubelet:0-16.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/redis:0-7.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-17.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/container-engine:0-2.f25container
registry.fedoraproject.org/f25/container-engine:0
registry.fedoraproject.org/f25/container-engine
registry.fedoraproject.org/f25/cockpit:135-12.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/postgresql:0-1.f25docker
registry.fedoraproject.org/f25/postgresql:0
registry.fedoraproject.org/f25/postgresql
registry.fedoraproject.org/f25/postgresql:0-1.f25docker
registry.fedoraproject.org/f25/postgresql:0
registry.fedoraproject.org/f25/postgresql
registry.fedoraproject.org/f25/mongodb:0-6.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/php:0-6.f25container
registry.fedoraproject.org/f25/php:0
registry.fedoraproject.org/f25/php
registry.fedoraproject.org/f25/s2i-base:1-15.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/docker:0-6.f25container
registry.fedoraproject.org/f25/docker:0
registry.fedoraproject.org/f25/docker
registry.fedoraproject.org/f25/nodejs:0-7.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-17.f25container
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-15.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-17.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-node:0.1-16.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-proxy:0-17.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/waiverdb:0-2.f25container
registry.fedoraproject.org/f25/waiverdb:0
registry.fedoraproject.org/f25/waiverdb
registry.fedoraproject.org/f25/httpd:0-9.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/toolchain:1-13.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-17.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-9.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/flannel:0.1-15.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel


registry.fedoraproject.org/f26/nodejs:0-2.f26container
registry.fedoraproject.org/f26/nodejs:0
registry.fedoraproject.org/f26/nodejs
registry.fedoraproject.org/f26/mariadb:10.1-10.f26container
registry.fedoraproject.org/f26/mariadb:10.1
registry.fedoraproject.org/f26/mariadb
registry.fedoraproject.org/f26/redis:0-2.f26container

Summary/Minutes from today's FESCo Meeting (2017-07-21)

[Adam Miller]

On Fri, Jul 21, 2017 at 8:26 AM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-07-21 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> #topic #1741 - F27 System Wide Change: Graphical Applications as Flatpaks
> .fesco 1741
> https://pagure.io/fesco/issue/1741
>
> = New business =
>
> #topic #1736 - Don't automatically close security bugs on Fedora EOL
> .fesco 1736
> https://pagure.io/fesco/issue/1736
>
> #topic #1737 - Proposal: i686 SIG needs to be functional by F27
> release date or we drop i686 kernel from F28
> .fesco 1737
> https://pagure.io/fesco/issue/1737
>
> #topic #1748 - F27 System Wide Change: No More i686 Kernels
> .fesco 1748
> https://pagure.io/fesco/issue/1748
>
> #topic #1743 - F27 System Wide Change: NSS Default File Format SQL
> .fesco 1743
> https://pagure.io/fesco/issue/1743
>
> #topic #1744 - F27 System Wide Change: NSS signtool deprecation
> .fesco 1744
> https://pagure.io/fesco/issue/1744
>
> #topic #1745 - F27 System Wide Change: Switch OpenLDAP from NSS to OpenSSL
> .fesco 1745
> https://pagure.io/fesco/issue/1745
>
> #topic #1746 - F27 System Wide Change: Reduce Initial Setup Redundancy
> .fesco 1746
> https://pagure.io/fesco/issue/1746
>
> #topic #1747 - F27 System Wide Change: RPM 4.14
> .fesco 1747
> https://pagure.io/fesco/issue/1747
>
> #topic #1749 - F27 Self Contained Change: VirtualBox Guest Integration
> .fesco 1749
> https://pagure.io/fesco/issue/1749
>
> #topic #1750 - Decide if EOL is one month after release, four weeks,
> or something else
> .fesco 1750
> https://pagure.io/fesco/issue/1750
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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.

===
#fedora-meeting: FESCO (2017-07-21)
===


Meeting started by maxamillion at 16:00:04 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-07-21/fesco.2017-07-21-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:07)

* Follow Ups  (maxamillion, 16:04:04)

* #1741 - F27 System Wide Change: Graphical Applications as Flatpaks
  (maxamillion, 16:04:04)
  * LINK: https://pagure.io/fesco/issue/1741   (maxamillion, 16:04:10)
  * LINK:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ABWHDCTSPNCMOJYYTT4UZ3HCWVGCNLSR/
(jforbes, 16:11:21)
  * AGREED: - APPROVED: F27 System Wide Change: Graphical Applications
as Flatpaks (+1:6, +0:0, -1:0) (Includes a +1 in ticket from absense
FESCo member)  (maxamillion, 16:34:38)

* New Business  (maxamillion, 16:34:50)

* #1736 - Don't automatically close security bugs on Fedora EOL
  (maxamillion, 16:34:50)
  * LINK: https://pagure.io/fesco/issue/1736   (maxamillion, 16:34:51)
  * AGREED: wait another week, ask for input from program manager and
what work needs to be done with EOL scripts (+1:5, +0:0, -1:0)
(maxamillion, 16:46:27)

* #1737 - Proposal: i686 SIG needs to be functional by F27 release date
  or we drop i686 kernel from F28  (maxamillion, 16:46:42)
  * LINK: https://pagure.io/fesco/issue/1737   (maxamillion, 16:46:47)

* #1748 - F27 System Wide Change: No More i686 Kernels  (maxamillion,
  16:46:52)
  * LINK: https://pagure.io/fesco/issue/1748   (maxamillion, 16:46:53)

* #1737 - Proposal: i686 SIG needs to be functional by F27 release date
  or we drop i686 kernel from F28  (maxamillion, 16:49:18)
  * LINK: https://pagure.io/fesco/issue/1737   (maxamillion, 16:49:23)
  * AGREED: Proposal: Request criteria for what a "functional SIG" means
in a measurable way (+1:5, +0:0, -1:0)  (maxamillion, 17:02:57)

* #1748 - F27 System Wide Change: No More i686 Kernels  (maxamillion,
  17:03:11)
  * LINK: https://pagure.io/fesco/issue/1748   (maxamillion, 17:03:12)
  * AGREED: Proposal: postpone #1748 to F28 pending the outcome of #1737
(+1:5, +0:0, -1:0)  (maxamillion, 17:08:01)

* #1743 - F27 System Wide Change: NSS Default File Format SQL
  (maxamillion, 17:08:12)
  * LINK: https://pagur

Schedule for Today's FESCo Meeting (2017-07-21)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-07-21 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1741 - F27 System Wide Change: Graphical Applications as Flatpaks
.fesco 1741
https://pagure.io/fesco/issue/1741

= New business =

#topic #1736 - Don't automatically close security bugs on Fedora EOL
.fesco 1736
https://pagure.io/fesco/issue/1736

#topic #1737 - Proposal: i686 SIG needs to be functional by F27
release date or we drop i686 kernel from F28
.fesco 1737
https://pagure.io/fesco/issue/1737

#topic #1748 - F27 System Wide Change: No More i686 Kernels
.fesco 1748
https://pagure.io/fesco/issue/1748

#topic #1743 - F27 System Wide Change: NSS Default File Format SQL
.fesco 1743
https://pagure.io/fesco/issue/1743

#topic #1744 - F27 System Wide Change: NSS signtool deprecation
.fesco 1744
https://pagure.io/fesco/issue/1744

#topic #1745 - F27 System Wide Change: Switch OpenLDAP from NSS to OpenSSL
.fesco 1745
https://pagure.io/fesco/issue/1745

#topic #1746 - F27 System Wide Change: Reduce Initial Setup Redundancy
.fesco 1746
https://pagure.io/fesco/issue/1746

#topic #1747 - F27 System Wide Change: RPM 4.14
.fesco 1747
https://pagure.io/fesco/issue/1747

#topic #1749 - F27 Self Contained Change: VirtualBox Guest Integration
.fesco 1749
https://pagure.io/fesco/issue/1749

#topic #1750 - Decide if EOL is one month after release, four weeks,
or something else
.fesco 1750
https://pagure.io/fesco/issue/1750

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [Fedora-packaging] Bundled Provides Libraries and Versioning

[Adam Miller]

On Sat, Jul 8, 2017 at 10:24 AM, Ville Skyttä  wrote:
>
>
> 7.7.2017 20.45 "Jason L Tibbitts III"  kirjoitti:
>
>
> I would argue that it doesn't remove the ability, but that it does make
> it more difficult to do in an automated fashion.  Basically you can see
> that something has a bundled library but then you need to do manual
> inspection to go further.
>
>
> I think the versioning isn't worth much at all.
>
> If the bundled version corresponds to an upstream release to an extent that
> it can be called that version, and checks like the discussed one could be
> skipped just by looking at the version label, then it must be practically
> the same. So why is it bundled in the first place?
>
> On the other hand if there is a "good" reason it is bundled, that reason
> quite probably is that it is a modified version. So it's different than the
> upstream one, and thus knowledge whether an upstream release is vulnerable
> or not cannot be just assumed based on the version label a packager has
> attached to it. It needs to be checked anyway.
>

The main motivation for bundling as of late is golang[0], it's
extremely common out in the community for software to pull in
"Vendored" libraries even if they are exact copies of remote upstreams
(this is common with tools like godep[1]) because golang is statically
compiled by default (you can dynamically link with gcc-go and I
*think* recent releases of cgo but I've yet to find a golang project
that officially uses or endorses it's use). It's also extremely
painful to unbundle these as some more popular software written in
golang such as docker[2], kubernetes[3], and openshift[4] have upwards
of 100 bundled libs (over 1000 for OpenShift).

-AdamM

[0] - https://golang.org/
[1] - https://github.com/tools/godep
[2] - http://pkgs.fedoraproject.org/cgit/rpms/docker.git/tree/docker.spec
[3] - 
http://pkgs.fedoraproject.org/cgit/rpms/kubernetes.git/tree/kubernetes.spec
[4] - http://pkgs.fedoraproject.org/cgit/rpms/origin.git/tree/origin.spec

>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Bundled Provides Libraries and Versioning

[Adam Miller]

On Sun, Jul 9, 2017 at 5:36 PM, Kevin Kofler <kevin.kof...@chello.at> wrote:
> Adam Miller wrote:
>> In today's FESCo meeting we discussed the fact that there are many
>> RPMs currently in Fedora (a reported 244 in Rawhide currently) that
>> are defining a `Provides: bundled() = ` but excluding
>> the version completely[0][1]. This removes that ability to properly
>> perform source code auditing and security vulnerability tracking.
>>
>> My question to the Fedora Contributor Community is, how should we
>> handle this? Is this something that should just simply be fixed by the
>> packages currently violating the Guidelines, should the Guidelines be
>> altered in a way that makes this easier to deal with for Packagers but
>> also provides what is needed for auditing and vulnerability tracking,
>> or is there simply clarification needed by what is required in the
>>  field?
>
> A version number may not even exist at all. Not all code that people copy is
> a library with a version number. Copylibs often don't bother doing releases
> because everyone just embeds it as a git submodule or checks out some random
> revision to copy into their own SCM. Hence, it is not realistic to require a
> version number.

So should we just stop requiring any RPMs be versioned since it's not
realistic to require a version number?

-AdamM

>
> Kevin Kofler
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Bundled Provides Libraries and Versioning

[Adam Miller]

On Fri, Jul 7, 2017 at 12:10 PM, Jerry James <loganje...@gmail.com> wrote:
> On Fri, Jul 7, 2017 at 10:55 AM, Adam Miller
> <maxamill...@fedoraproject.org> wrote:
>> Hello all,
>
> After which my response was met with:
>
> --
> Your message to the packaging mailing-list was rejected for the following
> reasons:
>
> The message is not from a list member
>
> The original message as received by Mailman is attached.
> --
>
> You cross-posted to closed lists.  Please don't do that unless you
> know for certain that the lists have identical membership, which
> pretty much obviates the need for posting to multiple lists.  If you
> want to send the same message to multiple closed mailing lists, then
> send copies of it, one at a time, to each list.  Thank you,

Apologies, it was requested in the FESCo meeting that I CC the FPC so
I did. I wasn't aware of the restrictions on the mailing list. I'll be
sure to verify in the future.

-AdamM

> --
> Jerry James
> http://www.jamezone.org/
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Bundled Provides Libraries and Versioning

[Adam Miller]

Hello all,
In today's FESCo meeting we discussed the fact that there are many
RPMs currently in Fedora (a reported 244 in Rawhide currently) that
are defining a `Provides: bundled() = ` but excluding
the version completely[0][1]. This removes that ability to properly
perform source code auditing and security vulnerability tracking.

My question to the Fedora Contributor Community is, how should we
handle this? Is this something that should just simply be fixed by the
packages currently violating the Guidelines, should the Guidelines be
altered in a way that makes this easier to deal with for Packagers but
also provides what is needed for auditing and vulnerability tracking,
or is there simply clarification needed by what is required in the
 field?

I look forward to the discussion.

Thank you,
-AdamM


[0] - https://pagure.io/fesco/issue/1734
[1] - https://pagure.io/packaging-committee/issue/696
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Schedule for today's FESCo Meeting (2017-07-07)

[Adam Miller]

On Fri, Jul 7, 2017 at 9:45 AM, Justin Forbes  wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-06-30 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> #topic #1725 F27 System Wide Change: Enable TRIM pass down to encrypted disks
> .fesco 1725
> https://pagure.io/fesco/issue/1725
>
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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.

I would like to request this be added to today's meeting.

https://pagure.io/fesco/issue/1734

Thank you,
-AdamM

> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out today[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25


Updated Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are only releasing for the f25 namespace.)

registry.fedoraproject.org/f25/ruby:0-9.f25docker
registry.fedoraproject.org/f25/ruby:0
registry.fedoraproject.org/f25/ruby
registry.fedoraproject.org/f25/kubernetes-master:0.1-16.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/kubernetes-kubelet:0-15.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/redis:0-6.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-16.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/cockpit:135-11.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/mongodb:0-6.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/php:0-5.f25container
registry.fedoraproject.org/f25/php:0
registry.fedoraproject.org/f25/php
registry.fedoraproject.org/f25/s2i-base:1-14.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/nodejs:0-6.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-14.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-node:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-proxy:0-15.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/httpd:0-8.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/toolchain:1-12.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-8.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/flannel:0.1-14.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel

The source of this content is provided in DistGit which can easily be
searched via the container pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/CCYVMZIO4YLJC4QMW2PGY7TILTCHC7G5/
[3] - https://admin.fedoraproject.org/pkgdb/packages/container/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2017-06-30)

[Adam Miller]

===
#fedora-meeting: FESCO (2017-06-30)
===


Meeting started by maxamillion at 16:01:41 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-06-30/fesco.2017-06-30-16.01.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:01:44)
  * LINK: https://fedoraproject.org/wiki/Legal:PrivacyPolicy   (nirik,
16:07:21)

* Followups  (maxamillion, 16:13:12)

* #1690 F27 Self Contained Changes (Java system/command setting)
  (maxamillion, 16:13:14)
  * LINK: https://pagure.io/fesco/issue/1690   (maxamillion, 16:13:15)
  * AGREED: APRROVE: F27 Self Contained Change: Java system/command
setting (+1:5, +0:0, -1:0)  (maxamillion, 16:17:36)

* #1715  F27 System Wide Change: Rsyslog log format change proposal
  (maxamillion, 16:17:44)
  * LINK: https://pagure.io/fesco/issue/1715   (maxamillion, 16:17:44)
  * AGREED: FESCo Rejects F27 System Wide Change: Rsyslog log format
change (+1:5, +0:0, -1:0)  (maxamillion, 16:30:58)

* New Business  (maxamillion, 16:31:16)

* #1690 F27 Self Contained Changes (PHP 7.2 and Remove krb5-appl)
  (maxamillion, 16:31:17)
  * LINK: https://pagure.io/fesco/issue/1690   (maxamillion, 16:31:18)
  * AGREED: APPROVED: F27 Self Contained Changes (PHP 7.2 and Remove
krb5-appl) (+1:5, +0:0, -1:0)  (maxamillion, 16:34:19)

* #1722 F27 System Wide Change: Separate Subpackage and Source Debuginfo
  (maxamillion, 16:34:31)
  * LINK: https://pagure.io/fesco/issue/1722   (maxamillion, 16:34:37)
  * AGREED: APPROVED F27 System Wide Change: Separate Subpackage and
Source Debuginfo (+1:5, +0:0, -1:0)  (maxamillion, 16:37:43)

* #1723 F27 System Wide Change: Parallel Installable Debuginfo
  (maxamillion, 16:37:56)
  * LINK: https://pagure.io/fesco/issue/1723   (maxamillion, 16:37:56)
  * AGREED: APPROVE F27 System Wide Change: Parallel Installable
Debuginfo (+1:5, +0:0, -1:0)  (maxamillion, 16:46:09)

* #1724 F27 System Wide Change: Kerberos KCM credential cache by default
  (maxamillion, 16:46:18)
  * LINK: https://pagure.io/fesco/issue/1724   (maxamillion, 16:46:24)
  * LINK: https://bugzilla.gnome.org/show_bug.cgi?id=779140
(maxamillion, 16:48:46)
  * LINK: https://bugzilla.gnome.org/show_bug.cgi?id=779140
(maxamillion, 16:49:02)
  * AGREED: APPROVE F27 System Wide Change: Kerberos KCM credential
cache by default (+1:5, +0:0, -1:0)  (maxamillion, 16:51:02)

* #1725 F27 System Wide Change: Enable TRIM pass down to encrypted disks
  (maxamillion, 16:51:08)
  * LINK: https://pagure.io/fesco/issue/1725   (maxamillion, 16:51:13)
  * AGREED: Proposal: Request more infromation about the security impact
of this change, more technical details (including real numbers on
performance impact), and raw evidence of "vast majority of users"
wishes (questionaires, user studies, etc) (+1:5, +0:0, -1:0)
(maxamillion, 17:02:40)

* #1726 F27 System Wide Change: Fedora 27 Boost 1.64 upgrade
  (maxamillion, 17:02:49)
  * LINK: https://pagure.io/fesco/issue/1726   (maxamillion, 17:02:49)
  * AGREED: APPROVE F27 System Wide Change: Fedora 27 Boost 1.64 upgrade
(+1:5, +0:0, -1:0)  (maxamillion, 17:04:00)

* #1727 F27 System Wide Change: Golang 1.9  (maxamillion, 17:04:08)
  * LINK: https://pagure.io/fesco/issue/1727   (maxamillion, 17:04:09)
  * AGREED: F27 System Wide Change: Golang 1.9 (+1:5, +0:0, -1:0)
(maxamillion, 17:06:06)

* Next week's chair  (maxamillion, 17:06:21)
  * jforbes previously agreed to Chair next week  (maxamillion,
17:06:53)

* Open Floor  (maxamillion, 17:07:02)
  * all system wide changes must be submitted by July 4th for fesco to
review next week  (dgilmore, 17:08:27)

Meeting ended at 17:15:06 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (110)
* Rathann (35)
* dgilmore (34)
* nirik (25)
* mjw (24)
* jwb (22)
* zodbot (20)
* ignatenkobrain (4)
* jcajka (2)
* Son_Goku (2)
* sgallagh (0)
* kalev (0)
* jforbes (0)
* jsmith (0)



On Thu, Jun 29, 2017 at 1:38 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-06-30 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> #topic #1690 F27 Self Contained Changes (Java system/command setting)
> .fesco 1690
> https://pagure.io/fesco/issue/1690
>
> #topic #1715  F27 System Wide Change: Rsyslog log format change proposal
> .fesco 1715
> https://pagure.io/fesco/issue/1715
>
> = New business =
>
>

Schedule for tomorrow's FESCo Meeting (2017-06-30)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-06-30 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1690 F27 Self Contained Changes (Java system/command setting)
.fesco 1690
https://pagure.io/fesco/issue/1690

#topic #1715  F27 System Wide Change: Rsyslog log format change proposal
.fesco 1715
https://pagure.io/fesco/issue/1715

= New business =

#topic #1690 F27 Self Contained Changes (PHP 7.2)
.fesco 1690
https://pagure.io/fesco/issue/1690

#topic #1722 F27 System Wide Change: Separate Subpackage and Source Debuginfo
.fesco 1722
https://pagure.io/fesco/issue/1722

#topic #1723 F27 System Wide Change: Parallel Installable Debuginfo
.fesco 1723
https://pagure.io/fesco/issue/1723

#topic #1724 F27 System Wide Change: Kerberos KCM credential cache by default
.fesco 1724
https://pagure.io/fesco/issue/1724

#topic #1725 F27 System Wide Change: Enable TRIM pass down to encrypted disks
.fesco 1725
https://pagure.io/fesco/issue/1725

#topic #1726 F27 System Wide Change: Fedora 27 Boost 1.64 upgrade
.fesco 1726
https://pagure.io/fesco/issue/1726

#topic #1727 F27 System Wide Change: Golang 1.9
.fesco 1727
https://pagure.io/fesco/issue/1727

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out yesterday[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25


Updated Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are only releasing for the f25 namespace.)

registry.fedoraproject.org/f25/ruby:0-8.f25docker
registry.fedoraproject.org/f25/ruby:0
registry.fedoraproject.org/f25/ruby
registry.fedoraproject.org/f25/kubernetes-master:0.1-16.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/kubernetes-kubelet:0-14.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/redis:0-5.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-15.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/cockpit:135-10.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/mongodb:0-5.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/php:0-4.f25container
registry.fedoraproject.org/f25/php:0
registry.fedoraproject.org/f25/php
registry.fedoraproject.org/f25/s2i-base:1-13.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/nodejs:0-5.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-13.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-node:0.1-14.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-proxy:0-15.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/httpd:0-7.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/toolchain:1-11.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-7.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/flannel:0.1-13.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel


The source of this content is provided in DistGit which can easily be
searched via the container pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/LU57S5TNFZRHVOM4ZK2HAUMGEOR5GFDB/
[3] - https://admin.fedoraproject.org/pkgdb/packages/container/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2017-06-16)

[Adam Miller]

On Thu, Jun 15, 2017 at 5:23 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-06-16 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> #topic #1690 Self Contained Changes (Sudo pip safety)
> .fesco 1690
> https://pagure.io/fesco/issue/1690#comment-444058
>
> #topic #1715 System Wide Change: Rsyslog log format change
> .fesco 1715
> https://pagure.io/fesco/issue/1715
>
> = New business =
>
> #topic #1690 Self Contained Changes (Java system/command setting)
> .fesco 1690
> https://pagure.io/fesco/issue/1690#comment-444058
>
> #topic #1716 Request to take over NetHack package
> .fesco 1716
> https://pagure.io/fesco/issue/1716
>
> #topic #1717 provenpackager request for tdawson
> .fesco 1717
> https://pagure.io/fesco/issue/1717
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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.

===
#fedora-meeting: FESCO (2017-06-16)
===


Meeting started by maxamillion at 16:00:05 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-06-16/fesco.2017-06-16-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:08)

* #1690 Self Contained Changes (Sudo pip safety)  (maxamillion,
  16:02:35)
  * LINK: https://pagure.io/fesco/issue/1690#comment-444058
(maxamillion, 16:02:35)
  * LINK:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/OFPNLIYEVQWH7KHESJFMPDCZGXQVQAJX/
(dgilmore, 16:19:10)
  * AGREED: FESCo Approves Self Contained Change: Sudo pip safety
(maxamillion, 16:22:09)

* #1715 System Wide Change: Rsyslog log format change  (maxamillion,
  16:22:17)
  * LINK: https://pagure.io/fesco/issue/1715   (maxamillion, 16:22:17)
  * AGREED: FESCo asks that in the next week we get some of the benefits
to fedora and our users laid out in the change, an outline of docs
on how to manage things, and a commitment to help resolve conflicts
and problems as they come up in  the transistion (+1:5, -1:0, +0:0)
(maxamillion, 16:39:09)

* #1690 Self Contained Changes (Java system/command setting)
  (maxamillion, 16:39:20)
  * LINK: https://pagure.io/fesco/issue/1690#comment-444058
(maxamillion, 16:39:20)
  * AGREED: Defer Self Contained Changes (Java system/command setting)
until next week, requesting feedback from Change owners about
implementation details and actual impact to Fedora (+1:5, -1:0,
+0:0)  (maxamillion, 16:45:55)

* #1716 Request to take over NetHack package  (maxamillion, 16:46:00)
  * LINK: https://pagure.io/fesco/issue/1716   (maxamillion, 16:46:01)
  * AGREED: FESCo grants request to take over NetHack package by
tachoknight  (maxamillion, 16:50:55)

* #1717 provenpackager request for tdawson  (maxamillion, 16:51:02)
  * LINK: https://pagure.io/fesco/issue/1717   (maxamillion, 16:51:03)
  * AGREED: Approved: provenpackager request for tdawson (+1:5, -1:0,
+0:0)  (maxamillion, 16:57:33)

* Next week's chair  (maxamillion, 16:57:52)
  * jsmith to chair next weeks meeting  (maxamillion, 17:02:58)

* Open Floor  (maxamillion, 17:03:08)

Meeting ended at 17:07:16 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (71)
* dgilmore (46)
* nirik (37)
* sgallagh (15)
* jforbes (14)
* jsmith (14)
* zodbot (13)
* kalev (0)
* Rathann (0)
* jwb (0)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2017-06-16)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-06-16 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1690 Self Contained Changes (Sudo pip safety)
.fesco 1690
https://pagure.io/fesco/issue/1690#comment-444058

#topic #1715 System Wide Change: Rsyslog log format change
.fesco 1715
https://pagure.io/fesco/issue/1715

= New business =

#topic #1690 Self Contained Changes (Java system/command setting)
.fesco 1690
https://pagure.io/fesco/issue/1690#comment-444058

#topic #1716 Request to take over NetHack package
.fesco 1716
https://pagure.io/fesco/issue/1716

#topic #1717 provenpackager request for tdawson
.fesco 1717
https://pagure.io/fesco/issue/1717

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release[2].

At this time the following Container Images are available in the
Fedora Registry.


Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25
registry.fedoraproject.org/fedora:24


Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are only releasing for the f25 namespace.)

registry.fedoraproject.org/f25/ruby:0-6.f25docker
registry.fedoraproject.org/f25/ruby:0
registry.fedoraproject.org/f25/ruby
registry.fedoraproject.org/f25/kubernetes-master:0.1-15.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/kubernetes-kubelet:0-12.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/redis:0-4.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-14.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/cockpit:135-9.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/mongodb:0-4.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/php:0-2.f25container
registry.fedoraproject.org/f25/php:0
registry.fedoraproject.org/f25/php
registry.fedoraproject.org/f25/s2i-base:1-12.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/nodejs:0-3.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-7.f25docker
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-12.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-13.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-node:0.1-13.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-proxy:0-13.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/httpd:0-5.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/toolchain:1-10.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-13.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-6.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/flannel:0.1-12.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel


The source of this content is provided in DistGit which can easily be
searched via the container pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].


Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/ZVBWUSUKH5LZGKLOVBPFOICZUEZ7IAF6/
[3] - https://admin.fedoraproject.org/pkgdb/packages/container/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2017-06-09)

[Adam Miller]

On Fri, Jun 9, 2017 at 10:59 AM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Apologies for the late schedule email.
>
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-06-09 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = New business =
>
> #topic #1690 F27 Self Contained Changes - Making sudo pip Safe (Again)
> .fesco 1690
> https://pagure.io/fesco/issue/1690
>
> #topic #1715 F27 System Wide Change: Rsyslog log format change proposal
> .fesco 1715
> https://pagure.io/fesco/issue/1715
>
> #topic #1718 F27 System Wide Change: Node.js 8.x
> .fesco 1718
> https://pagure.io/fesco/issue/1718
>
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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.


===
#fedora-meeting: FESCO (2017-06-09)
===


Meeting started by maxamillion at 16:00:03 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-06-09/fesco.2017-06-09-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:06)

* #1690 F27 Self Contained Changes - Making sudo pip Safe (Again)
  (maxamillion, 16:03:45)
  * LINK: https://pagure.io/fesco/issue/1690   (maxamillion, 16:03:45)
  * LINK:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3HFI7YKTQQCSNK2VWYWW3H2NGKLPT2PH/
(Rathann, 16:07:33)
  * AGREED: Defer decision on F27 Self Contained Changes - Making sudo
pip Safe (Again) until next week to allow more discussion on devel
thread (+1:6, -1:0, +0:0)  (maxamillion, 16:10:43)

* #1715 F27 System Wide Change: Rsyslog log format change proposal
  (maxamillion, 16:10:50)
  * LINK: https://pagure.io/fesco/issue/1715   (maxamillion, 16:10:51)
  * AGREED: FESCo requests that the Change owners update the proposal
with a much more detailed "Benefit to Fedora" section as well as
clearly identifying affected packages and processes that would need
to be updated if the change occurs. (+1:5, -1:0, +0:0)
(maxamillion, 16:24:41)

* #1718 F27 System Wide Change: Node.js 8.x  (maxamillion, 16:24:52)
  * LINK: https://pagure.io/fesco/issue/1718   (maxamillion, 16:24:53)
  * AGREED: FESCo Approves F27 System Wide Change: Node.js 8.x (+1:5,
-1:0, +0:0)  (maxamillion, 16:29:57)

* Next week's chair  (maxamillion, 16:30:17)
  * maxamillion to Chair Next Week's Meeting (2017-06-16)  (maxamillion,
16:34:19)

* Open Floor  (maxamillion, 16:34:29)

Meeting ended at 16:38:11 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (66)
* Rathann (30)
* sgallagh (27)
* kalev (14)
* zodbot (13)
* jsmith (12)
* dgilmore (7)
* nirik (0)
* jforbes (0)
* jwb (0)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Today's FESCo Meeting (2017-06-09)

[Adam Miller]

Apologies for the late schedule email.

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-06-09 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= New business =

#topic #1690 F27 Self Contained Changes - Making sudo pip Safe (Again)
.fesco 1690
https://pagure.io/fesco/issue/1690

#topic #1715 F27 System Wide Change: Rsyslog log format change proposal
.fesco 1715
https://pagure.io/fesco/issue/1715

#topic #1718 F27 System Wide Change: Node.js 8.x
.fesco 1718
https://pagure.io/fesco/issue/1718


= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: The future of the packager group for dist-git

[Adam Miller]

On Fri, Jun 2, 2017 at 3:07 PM, Matthew Miller  wrote:
> On Fri, Jun 02, 2017 at 09:42:48PM +0200, Pierre-Yves Chibon wrote:
>> (Note: pagure can and will enforce the FPCA for dist-git)
>
> I know Richard Fontana has expressed some interest in reducing the need
> for FPCA. Maybe this is an opportunity to move in that direction? I
> know Spot has said that "License In = License Out" is adequate for
> projects on Github; I think Spot's concern with spec files is that we
> don't give them an explicit license (right)?
>

I was under the impression that everything in Fedora was MIT licensed
unless otherwise specified as per:
https://fedoraproject.org/wiki/Legal:Licenses/LicenseAgreement

Is that incorrect?

-AdamM

> As we're moving things, can we do something in Pagure to cover this, so
> the FPCA isn't needed here?
>
>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out earlier today[2].

At this time the following Container Images are available in the
Fedora Registry.

Updated Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25


Updated Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are only releasing for the f25 namespace.)

registry.fedoraproject.org/f25/kubernetes-master:0.1-12.f25container
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/kubernetes-kubelet:0-11.f25container
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/redis:0-2.f25container
registry.fedoraproject.org/f25/redis:0
registry.fedoraproject.org/f25/redis
registry.fedoraproject.org/f25/etcd:0.1-11.f25container
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/cockpit:135-7.f25container
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/mongodb:0-2.f25container
registry.fedoraproject.org/f25/mongodb:0
registry.fedoraproject.org/f25/mongodb
registry.fedoraproject.org/f25/s2i-base:1-10.f25container
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/nodejs:0-2.f25container
registry.fedoraproject.org/f25/nodejs:0
registry.fedoraproject.org/f25/nodejs
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-13.f25container
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-10.f25container
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-12.f25container
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-node:0.1-11.f25container
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-proxy:0-12.f25container
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/httpd:0-4.f25container
registry.fedoraproject.org/f25/httpd:0
registry.fedoraproject.org/f25/httpd
registry.fedoraproject.org/f25/toolchain:1-8.f25container
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-12.f25container
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3-4.f25container
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist:0.7.3
registry.fedoraproject.org/f25/mirrormanager2-mirrorlist
registry.fedoraproject.org/f25/flannel:0.1-9.f25container
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel


The source of this content is provided in DistGit which can easily be
searched via the container pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/WLSPN4LPUXEYRRPFLFXDTNMONGZDU6JK/
[3] - https://admin.fedoraproject.org/pkgdb/packages/container/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announce: Fedora Layered Image Release

[Adam Miller]

On Tue, May 23, 2017 at 9:38 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote:
> On Mon, May 15, 2017 at 03:45:32PM -0500, Adam Miller wrote:
>> >
>> > Is the infrastructure now ready for the respin?
>>
>> It appears the builds are still failing because of
>> https://bugzilla.redhat.com/show_bug.cgi?id=144
>
> The bugzilla was addressed -- can we give
>
> registry.fedoraproject.org/fedora:26
>
> another try?
>

Yes, it's on the agenda for today to go out with the layered image
release that will follow today's Atomic Host release.

-AdamM

> --
> Jan Pazdziora
> Senior Principal Software Engineer, Identity Management Engineering, Red Hat
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2017-05-19)

[Adam Miller]

===
#fedora-meeting: FESCO (2017-05-19)
===


Meeting started by maxamillion at 16:00:31 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-05-19/fesco.2017-05-19-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:34)

* #1707 Firefox on non-x86 architectures  (maxamillion, 16:06:35)
  * LINK: https://pagure.io/fesco/issue/1707   (maxamillion, 16:06:36)
  * LINK: https://bugzilla.mozilla.org/show_bug.cgi?id=1323303 has some
interesting comments  (nirik, 16:45:51)
  * FESCo to table this issue for future discussion  (maxamillion,
17:07:26)

* #1708 F27 System Wide Change: Arbitrary Branching  (maxamillion,
  17:07:35)
  * LINK: https://pagure.io/fesco/issue/1708   (maxamillion, 17:07:36)
  * LINK:

https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching
(threebean, 17:11:33)
  * LINK: http://pkgs.fedoraproject.org/cgit/rpms/koji.git/log/?h=1.12.0
(dgilmore, 17:38:34)
  * AGREED: Proposal: Current F27 System Wide Change: Arbitrary
Branching will make changes based on FESCo feedback and be back on
the FESCo meeting agenda next week (+1: 6, -1: 0, +0: 0)
(maxamillion, 17:48:54)

* #1709 Review of release blocking deliverables for F26  (maxamillion,
  17:49:03)
  * LINK: https://pagure.io/fesco/issue/1709   (maxamillion, 17:49:04)
  * AGREED: Proposal: Table Review of release blocking deliverables for
F26 until next week to allow updates to the issue to be made (+1: 6,
-1: 0, +0: 0)  (maxamillion, 17:52:24)

* #1710 F26 Changes not in ON_QA status (<100% completed)  (maxamillion,
  17:52:32)
  * LINK: https://pagure.io/fesco/issue/1710   (maxamillion, 17:52:32)
  * AGREED: we give everyone a week to update the change staus. If the
change is not updated or complete we will enact contigency plans.
(+1: 6, -1: 0  )  (dgilmore, 18:04:38)

* #1712 F27 System Wide Change: Perl 5.26  (maxamillion, 18:04:59)
  * LINK: https://pagure.io/fesco/issue/1712   (maxamillion, 18:04:59)
  * AGREED: F27 System Wide Change: Perl 5.26 (+1: 6, -1: 0, +0: 0)
(maxamillion, 18:07:21)

* Next week's chair  (maxamillion, 18:07:47)
  * nirik to chair next week's meeting  (maxamillion, 18:09:58)

* Open Floor  (maxamillion, 18:10:11)

Meeting ended at 18:12:03 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (153)
* dgilmore (114)
* nirik (74)
* sgallagh (58)
* threebean (42)
* jwb (37)
* jforbes (19)
* zodbot (16)
* langdon (12)
* mprahl (10)
* jkaluza (9)
* cstratak (1)
* kalev (0)
* Rathann (0)
* jsmith (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2017-05-19)

[Adam Miller]

# UPDATE: New agenda with missing item and fixed typo

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-05-19 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= New business =

#topic #1707 Firefox on non-x86 architectures
.fesco 1707
https://pagure.io/fesco/issue/1707

#topic #1708 F27 System Wide Change: Arbitrary Branching
.fesco 1708
https://pagure.io/fesco/issue/1708

#topic #1709 Review of release blocking deliverables for F26
.fesco 1709
https://pagure.io/fesco/issue/1709

#topic #1710 F26 Changes not in ON_QA status (<100% completed)
.fesco 1710
https://pagure.io/fesco/issue/1710

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2017-05-19)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-05-19 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= New business =

#topic #1708 F27 System Wide Change: Arbitrary Branching
.fesco 1708
https://pagure.io/fesco/issue/1708

#topic #1709 Review of release blocking deliverables for F26
.fesco 1709
https://pagure.io/fesco/issue/1709

#topic #1910 F26 Changes not in ON_QA status (<100% completed)
.fesco 1910
https://pagure.io/fesco/issue/1910

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announce: Fedora Layered Image Release

[Adam Miller]

On Mon, May 15, 2017 at 8:16 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote:
> On Thu, May 11, 2017 at 10:04:19AM -0500, Dennis Gilmore wrote:
>> El mié, 10-05-2017 a las 22:47 -0500, Adam Miller escribió:
>> > On Tue, May 9, 2017 at 7:22 AM, Jan Pazdziora <jpazdzi...@redhat.com>
>> > wrote:
>> > >
>> > > One problem with the current Fedora 26 image is that it enables
>> > > rawhide repo and not the 26 development repo. So anybody using that
>> > > image to build something which installs additional packages will
>> > > get
>> > > Fedora 27, not Fedora 26 packages installed.
>> > >
>> > > Could the registry.fedoraproject.org/fedora:26 be respun to point
>> > > to
>> > > the correct Fedora 26 package source?
>> >
>> > Absolutely. I went to look into that today but the koji builder tasks
>> > were having an issue for the last few weeks. It turns out that there
>> > was a bug in oz (which is used in image builds in koji). This has
>> > been
>> > fixed and we should be able to get updates out tomorrow.
>>
>> the bug was not in oz. I suspect it was a regression in nss, all the
>> gory details are in
>> https://pagure.io/releng/issue/6776https://pagure.io/releng/issue/6776
>
> Is the infrastructure now ready for the respin?
>

It appears the builds are still failing because of
https://bugzilla.redhat.com/show_bug.cgi?id=144

-AdamM

> --
> Jan Pazdziora
> Senior Principal Software Engineer, Identity Management Engineering, Red Hat
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announce: Fedora Layered Image Release

[Adam Miller]

On Tue, May 9, 2017 at 7:22 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote:
> On Mon, May 08, 2017 at 01:59:36PM -0500, Adam Miller wrote:
>> On Thu, May 4, 2017 at 6:55 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote:
>> > On Thu, Apr 20, 2017 at 10:39:22PM -0500, Adam Miller wrote:
>> >> Hello all,
>> >> On behalf of the Fedora Atomic WG[0] and Fedora Release
>> >> Engineering[1], I am pleased to announce the latest Fedora Layered
>> >> Image Release. This follows the latest Atomic Host Release that came
>> >> out yesterday[2].
>> >>
>> >> At this time the following Container Images are available in the
>> >> Fedora Registry.
>> >>
>> >>
>> >> Base Images:
>> >>
>> >> (Note that the "latest" tag currently points to "25" and the "rawhide"
>> >> tag currently points to "27", if no tag is provided in your pull
>> >> command then it will always default to "latest")
>> >>
>> >> registry.fedoraproject.org/fedora:latest
>> >> registry.fedoraproject.org/fedora:rawhide
>> >> registry.fedoraproject.org/fedora:27
>> >
>> > The current registry.fedoraproject.org/fedora:rawhide and
>> > registry.fedoraproject.org/fedora:27 image 202b880ac136 says it's
>> > 7 weeks old,
>> >
>> >> registry.fedoraproject.org/fedora:26
>> >
>> > Fedora 26 image is 4 months old.
>> >
>> > What are the plans for respining these images on regular basis?
>> > Especially the development "releases" tend to change quite heaving and
>> > if we do not want to encourage the use of
>> >
>> > RUN dnf upgrade -y
>> >
>> > in every Dockerfile, we might want to make it easy for people to
>> > consume fresh content.
>> >
>> > Incidently, registry.fedoraproject.org/fedora:25 is rather new, just
>> > 13 days old.
>>
>> Yes, the current stable is planned to be respun on a two-week average.
>> The others as well but they aren't priority right now. There's an
>> automation process in the works and once that is done then all of
>> these will happen automatically.
>
> One problem with the current Fedora 26 image is that it enables
> rawhide repo and not the 26 development repo. So anybody using that
> image to build something which installs additional packages will get
> Fedora 27, not Fedora 26 packages installed.
>
> Could the registry.fedoraproject.org/fedora:26 be respun to point to
> the correct Fedora 26 package source?
>

Absolutely. I went to look into that today but the koji builder tasks
were having an issue for the last few weeks. It turns out that there
was a bug in oz (which is used in image builds in koji). This has been
fixed and we should be able to get updates out tomorrow.

-AdamM

> Thank you,
>
> --
> Jan Pazdziora
> Senior Principal Software Engineer, Identity Management Engineering, Red Hat
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announce: Fedora Layered Image Release

[Adam Miller]

On Thu, May 4, 2017 at 6:55 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote:
> On Thu, Apr 20, 2017 at 10:39:22PM -0500, Adam Miller wrote:
>> Hello all,
>> On behalf of the Fedora Atomic WG[0] and Fedora Release
>> Engineering[1], I am pleased to announce the latest Fedora Layered
>> Image Release. This follows the latest Atomic Host Release that came
>> out yesterday[2].
>>
>> At this time the following Container Images are available in the
>> Fedora Registry.
>>
>>
>> Base Images:
>>
>> (Note that the "latest" tag currently points to "25" and the "rawhide"
>> tag currently points to "27", if no tag is provided in your pull
>> command then it will always default to "latest")
>>
>> registry.fedoraproject.org/fedora:latest
>> registry.fedoraproject.org/fedora:rawhide
>> registry.fedoraproject.org/fedora:27
>
> The current registry.fedoraproject.org/fedora:rawhide and
> registry.fedoraproject.org/fedora:27 image 202b880ac136 says it's
> 7 weeks old,
>
>> registry.fedoraproject.org/fedora:26
>
> Fedora 26 image is 4 months old.
>
> What are the plans for respining these images on regular basis?
> Especially the development "releases" tend to change quite heaving and
> if we do not want to encourage the use of
>
> RUN dnf upgrade -y
>
> in every Dockerfile, we might want to make it easy for people to
> consume fresh content.
>
> Incidently, registry.fedoraproject.org/fedora:25 is rather new, just
> 13 days old.

Yes, the current stable is planned to be respun on a two-week average.
The others as well but they aren't priority right now. There's an
automation process in the works and once that is done then all of
these will happen automatically.

-AdamM

>
> --
> Jan Pazdziora
> Senior Principal Software Engineer, Identity Management Engineering, Red Hat
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes for today's FESCo meeting (2017-04-28)

[Adam Miller]

On Thu, Apr 27, 2017 at 10:22 AM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2017-04-28 16:00 UTC'
>
>
> Links to all issues below can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Followups =
>
> #topic #1699 xml-security-c new maintainer
> .fesco 1699
> https://pagure.io/fesco/issue/1699
>
> = New business =
>
> #topic #1653 Better communicating roles and responsibilities of FESCo
> for elections
> .fesco 1653
> https://pagure.io/fesco/issue/1653
>
> #topic #1690 F27 Self Contained Changes - Java 9
> .fesco 1690
> https://pagure.io/fesco/issue/1690#comment-438338
>
> #topic #1702 Fedora support_url
> .fesco 1702
> https://pagure.io/fesco/issue/1702
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, 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.

===
#fedora-meeting: FESCO (2017-04-28)
===


Meeting started by maxamillion at 16:02:56 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-04-28/fesco.2017-04-28-16.02.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:02:59)

* #1699 xml-security-c new maintainer  (maxamillion, 16:07:41)
  * LINK: https://pagure.io/fesco/issue/1699   (maxamillion, 16:07:42)
  * LINK: https://admin.fedoraproject.org/pkgdb/packager/anttix/ shows
they are point of contact for 3 packages  (nirik, 16:10:53)
  * LINK:
https://admin.fedoraproject.org/pkgdb/package/rpms/xml-security-c/
shows kloczek as an administrator  (jforbes, 16:12:30)
  * AGREED: - xml-security-c new maintainer request - leave as is,
administrator already updated (+1:6, -1:0, +0:0)  (maxamillion,
16:16:47)

* #1653 Better communicating roles and responsibilities of FESCo for
  elections  (maxamillion, 16:16:55)
  * LINK: https://pagure.io/fesco/issue/1653   (maxamillion, 16:17:00)
  * nirik to update the wiki  (maxamillion, 16:18:34)

* #1690 F27 Self Contained Changes - Java 9  (maxamillion, 16:18:42)
  * LINK: https://pagure.io/fesco/issue/1690#comment-438338
(maxamillion, 16:18:43)
  * AGREED: - APPROVED: F27 Self Contained Changes - Java 9 (+1:6, -1:0,
+0:0)  (maxamillion, 16:23:32)

* #1702 Fedora support_url  (maxamillion, 16:23:40)
  * LINK: https://pagure.io/fesco/issue/1702   (maxamillion, 16:23:40)
  * LINK: https://fedoraproject.org/wiki/Communicating_and_getting_help
(dgilmore, 16:27:10)
  * AGREED: FESCo has agreed that
https://fedoraproject.org/wiki/Communicating_and_getting_help is the
official support url (+1:6, -1:0, +0:0)  (maxamillion, 16:31:42)
  * maxamillion to check
https://fedoraproject.org/wiki/Communicating_and_getting_help is up
to date  (maxamillion, 16:32:46)

* Next week's chair  (maxamillion, 16:32:55)
  * kalev to chair next week's meeting  (maxamillion, 16:35:34)

* Open Floor  (maxamillion, 16:35:43)
  * AGREED: Enable s390x support in Rawhide only - (+1:6, -1:0, +0:0)
(maxamillion, 16:49:52)

Meeting ended at 16:52:36 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (59)
* dgilmore (35)
* nirik (20)
* kalev (16)
* jforbes (15)
* zodbot (13)
* sgallagh (12)
* Pharaoh_Atem (7)
* sharkcz (2)
* Rathann (0)
* jwb (0)
* jsmith (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announce: Fedora Layered Image Release

[Adam Miller]

On Fri, Apr 28, 2017 at 2:39 AM, Jan Pazdziora <jpazdzi...@redhat.com> wrote:
> On Thu, Apr 20, 2017 at 10:39:22PM -0500, Adam Miller wrote:
>> Hello all,
>> On behalf of the Fedora Atomic WG[0] and Fedora Release
>> Engineering[1], I am pleased to announce the latest Fedora Layered
>> Image Release. This follows the latest Atomic Host Release that came
>> out yesterday[2].
>>
>> At this time the following Container Images are available in the
>> Fedora Registry.
>>
>> Base Images:
>>
>> (Note that the "latest" tag currently points to "25" and the "rawhide"
>> tag currently points to "27", if no tag is provided in your pull
>> command then it will always default to "latest")
>>
>> registry.fedoraproject.org/fedora:latest
>> registry.fedoraproject.org/fedora:rawhide
>> registry.fedoraproject.org/fedora:27
>> registry.fedoraproject.org/fedora:26
>> registry.fedoraproject.org/fedora:25
>> registry.fedoraproject.org/fedora:24
>
> What is the relationship to docker.io/fedora?
>
> Running docker pull for various images and then docker images, I can see
>
> REPOSITORY  TAG IMAGE ID
> CREATED SIZE
> docker.io/fedora24  f623aaef07f05 
> months ago204.4 MB
> registry.fedoraproject.org/fedora   24  f623aaef07f05 
> months ago204.4 MB
>
> so for Fedora 24 the images are the same, but
>
> REPOSITORY  TAG IMAGE ID
> CREATED SIZE
> docker.io/fedora25  15895ef0b3b26 
> days ago  230.9 MB
> registry.fedoraproject.org/fedora   25  b414411f6e007 
> days ago  230.9 MB
>
> So it looks like docker.io/fedora has newer Fedora 25 image than
> registry.fedoraproject.org/fedora. Is that expected?
>
> If we are building building images
>
> FROM fedora:25
>
> should we start using
>
> FROM registry.fedoraproject.org/fedora:25
>
> instead in Dockerfiles? If merely fedora does not point to whatever
> is the authoritative location for Fedora images, shouldn't it be purged
> in docker.io to avoid confusion?

We do have 'FROM registry.fedoraproject.org/fedora:25' in our
Container Guidelines[0] today.

As a note though, we do maintain the docker base images on the Docker
Hub also, they are made from the same rootfs of the Fedora Official
ones that comes from Koji but we have to extract the rootfs from the
archive file and add a Dockerfile to comply with Docker Library's
upload workflow[1]. However, we do not upload pre-GA Releases
(branched) or rawhide to Docker Hub currently because of this added
manual work that is required.

We are also aiming to sync out all layered image content to Docker Hub
(and potentially other publicly available registries such as Quay.io)
but that is not currently high in priority. Hopefully in the next
couple months. As a point of note, layered image content can easily be
sync'd via the fedora Docker Hub account once the automatic release
process is in place (currently being worked on[2]) but base images are
considered special.

-AdamM

[0] - https://fedoraproject.org/wiki/Container:Guidelines
[1] - https://github.com/fedora-cloud/docker-brew-fedora
[2] - 
https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkflowEngine

>
> --
> Jan Pazdziora
> Senior Principal Software Engineer, Identity Management Engineering, Red Hat
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2017-04-28)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-04-28 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1699 xml-security-c new maintainer
.fesco 1699
https://pagure.io/fesco/issue/1699

= New business =

#topic #1653 Better communicating roles and responsibilities of FESCo
for elections
.fesco 1653
https://pagure.io/fesco/issue/1653

#topic #1690 F27 Self Contained Changes - Java 9
.fesco 1690
https://pagure.io/fesco/issue/1690#comment-438338

#topic #1702 Fedora support_url
.fesco 1702
https://pagure.io/fesco/issue/1702

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out yesterday[2].

At this time the following Container Images are available in the
Fedora Registry.


Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25
registry.fedoraproject.org/fedora:24


Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are only releasing for the f25 namespace.)

registry.fedoraproject.org/f25/cockpit:135-5.f25docker
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/kubernetes-node:0.1-9.f25docker
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-9.f25docker
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-8.f25docker
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-9.f25docker
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-9.f25docker
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-master:0.1-10.f25docker
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/s2i-base:1-8.f25docker
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/kubernetes-kubelet:0-9.f25docker
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/flannel:0.1-8.f25docker
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel
registry.fedoraproject.org/f25/kubernetes-proxy:0-9.f25docker
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/etcd:0.1-10.f25docker
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/toolchain:1-7.f25docker
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain

The source of this content is provided in DistGit which can easily be
searched via the container pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Special side note with this release, all layered images have been
rebuilt to ensure the base image they rely upon includes the fix for
CVE-2017-5461[7][8].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/B6CXLASBHNDM3KL6A5SXKSMNM3OCPNYX/
[3] - https://admin.fedoraproject.org/pkgdb/packages/container/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
[7] - https://bugzilla.redhat.com/show_bug.cgi?id=1440080
[8] - https://bodhi.fedoraproject.org/updates/FEDORA-2017-521b5e42a4
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: DistGit namespace migration: docker -> container

[Adam Miller]

Hello all,
The migration of the docker namespace in DistGit, cgit, PackageDB
and Container Guidelines is now complete. This migration is at the
request of the Fedora Atomic WG[0] to highlight that Fedora is
targeting all OCI[1] compliant container runtimes instead of any
specific one.

For those who maintain container layered images in Fedora space you
will need to re-clone your DistGit repositories under the new
namespace. (Backwards compatibility was not left in place on purpose
because of an inheritance attribute of namespaces mapping to koji
build targets):

$ fedpkg clone container/foo

Instead of:

$ fedpkg clone docker/foo

This marks "Phase 1" of the migration and was the big ticket items. We
did not want to wait on Phase 2 to announce because they are mostly
cosmetic/book-keeping and with Phase 1 complete we can keep from
increasing the layered images needing migration later. We also wanted
to let container maintainers know as soon as possible after the
changes to DistGit and PackageDB went live.

Builds will continue to work as they had previously with once you re-clone:

$ fedpkg container-build

Phase 2
There are three final items which are: the migration of the koji
targets, the migration of the $DISTTAG and the Buzilla entry[2].

The koji tags and targets exist but builds won't use them until a
required rpkg patch is merged upstream[3] to properly inherit the new
DistGit namespace.

The Bugzilla entry is currently awaiting update from the Fedora Infra
and Bugzilla Admin groups[4].

Once these changes are in place, we will release a new Fedora base
image set that will include the updated $DISTTAG which will be
inherited by layered image builds upon new builds (which are all
rebuilt before a container release so this will happen automatically).

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://www.opencontainers.org/
[2] - https://bugzilla.redhat.com/enter_bug.cgi?classification=Fedora
[3] - https://pagure.io/rpkg/pull-request/214
[4] - https://pagure.io/fedora-infrastructure/issue/5920
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out yesterday[2].

At this time the following Container Images are available in the
Fedora Registry.


Base Images:

(Note that the "latest" tag currently points to "25" and the "rawhide"
tag currently points to "27", if no tag is provided in your pull
command then it will always default to "latest")

registry.fedoraproject.org/fedora:latest
registry.fedoraproject.org/fedora:rawhide
registry.fedoraproject.org/fedora:27
registry.fedoraproject.org/fedora:26
registry.fedoraproject.org/fedora:25
registry.fedoraproject.org/fedora:24


Layered Images:

(Note: Layered Images are namespaced in the registry and at this time
we are only releasing for the f25 namespace.)

registry.fedoraproject.org/f25/cockpit:135-4.f25docker
registry.fedoraproject.org/f25/cockpit:135
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/kubernetes-node:0.1-8.f25docker
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-8.f25docker
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-7.f25docker
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-8.f25docker
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-8.f25docker
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-master:0.1-9.f25docker
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/s2i-base:1-5.f25docker
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/kubernetes-kubelet:0-8.f25docker
registry.fedoraproject.org/f25/kubernetes-kubelet:0
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/flannel:0.1-7.f25docker
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel
registry.fedoraproject.org/f25/kubernetes-proxy:0-8.f25docker
registry.fedoraproject.org/f25/kubernetes-proxy:0
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/etcd:0.1-9.f25docker
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/toolchain:1-6.f25docker
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain


As a reminder, the source of this content is provided in DistGit which
can easily be searched via the container-specific pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/7MTNJIPL4EJOS7WXX6W65JU6S4SI4QEM/
[3] - https://admin.fedoraproject.org/pkgdb/packages/docker/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
[7] - https://github.com/jessfraz/reg/tree/master/server
[8] - https://bugzilla.redhat.com/show_bug.cgi?id=1432214
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out yesterday[2].

At this time the following Container Images are available in the
Fedora Registry.

registry.fedoraproject.org/f25/cockpit:130-1.8.f25docker
registry.fedoraproject.org/f25/cockpit:130
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/kubernetes-node:0.1-6.f25docker
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1-6.f25docker
registry.fedoraproject.org/f25/kubernetes-controller-manager:0.1
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/mariadb:10.1-5.f25docker
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-6.f25docker
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1-6.f25docker
registry.fedoraproject.org/f25/kubernetes-scheduler:0.1
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-master:0.1-7.f25docker
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/s2i-base:1-4.f25docker
registry.fedoraproject.org/f25/s2i-base:1
registry.fedoraproject.org/f25/s2i-base
registry.fedoraproject.org/f25/kubernetes-kubelet:0.1-5.f25docker
registry.fedoraproject.org/f25/kubernetes-kubelet:0.1
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/flannel:0.1-5.f25docker
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel
registry.fedoraproject.org/f25/kubernetes-proxy:0.1-5.f25docker
registry.fedoraproject.org/f25/kubernetes-proxy:0.1
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/etcd:0.1-7.f25docker
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/toolchain:1-4.f25docker
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain

As a reminder, the source of this content is provided in DistGit which
can easily be searched via the container-specific pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Also, it was previously mentioned that we're aiming to provide a webUI
in front of our registry. We're currently planning to use MIT Licensed
reg-server[7] which we will deploy once we have a completed package
review[8] and a Fedora CSS theme from the websites group. Updates on
that will come as we are able to accomplish these tasks.

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/thread/CS6NKTLLYWEC3AXJPYQ2LPBTFSD43HRC/
[3] - https://admin.fedoraproject.org/pkgdb/packages/docker/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
[7] - https://github.com/jessfraz/reg/tree/master/server
[8] - https://bugzilla.redhat.com/show_bug.cgi?id=1432214
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the latest Fedora Layered
Image Release. This follows the latest Atomic Host Release that came
out yesterday[2].

At this time the following Container Images are available in the
Fedora Registry.

registry.fedoraproject.org/f25/cockpit:130-1.3.f25docker
registry.fedoraproject.org/f25/cockpit:130
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/kubernetes-node:0.1-3.f25docker
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/mariadb:10.1-2.f25docker
registry.fedoraproject.org/f25/mariadb:10.1
registry.fedoraproject.org/f25/mariadb
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1-3.f25docker
registry.fedoraproject.org/f25/kubernetes-apiserver:0.1
registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/kubernetes-master:0.1-5.f25docker
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/flannel:0.1-3.f25docker
registry.fedoraproject.org/f25/flannel:0.1
registry.fedoraproject.org/f25/flannel
registry.fedoraproject.org/f25/kubernetes-proxy:0.1-3.f25docker
registry.fedoraproject.org/f25/kubernetes-proxy:0.1
registry.fedoraproject.org/f25/kubernetes-proxy
registry.fedoraproject.org/f25/etcd:0.1-5.f25docker
registry.fedoraproject.org/f25/etcd:0.1
registry.fedoraproject.org/f25/etcd
registry.fedoraproject.org/f25/toolchain:1-2.f25docker
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain

As a reminder, the source of this content is provided in DistGit which
can easily be searched via the container-specific pkgdb namespace[3].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[4] family of technologies into Fedora.
Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[5][6].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - 
https://lists.fedoraproject.org/archives/list/cl...@lists.fedoraproject.org/message/63LXWH33QYZKTNOFNJ5T6TRNNJ376RC7/
[3] - https://admin.fedoraproject.org/pkgdb/packages/docker/%2A/
[4] - https://www.projectatomic.io/
[5] - https://fedoraproject.org/wiki/Container:Review_Process
[6] - https://fedoraproject.org/wiki/Container:Guidelines
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2017-02-17)

[Adam Miller]

===
#fedora-meeting: FESCO (2017-02-17)
===


Meeting started by maxamillion at 16:00:02 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2017-02-17/fesco.2017-02-17-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:05)

* #1635 Self Contained Changes: Anaconda LVM RAID  (maxamillion,
  16:03:34)
  * LINK: https://pagure.io/fesco/issue/1635   (maxamillion, 16:03:35)
  * AGREED: Table Anaconda LVM another week awaiting change owner
reponse to pending questions (+1:6, +0:0, -1:0)  (maxamillion,
16:14:09)
  * ACTION: maxamillion to email Anaconda LVM RAID Change owner to
request questions on devel list be addressed  (maxamillion,
16:15:37)

* #1635 Self Contained Changes: The GNU C Library version 2.25
  (maxamillion, 16:16:00)
  * LINK: https://pagure.io/fesco/issue/1635   (maxamillion, 16:16:01)
  * AGREED: FESCo Approves F26 Self Contained Change: The GNU C Library
Version 2.25 (+1:6, +0:0, -1:0)  (maxamillion, 16:17:18)

* Next week's chair  (maxamillion, 16:17:24)
  * AGREED: jsmith will chair FESCo meeting on 2017-02-24  (maxamillion,
16:18:14)

* Open Floor  (maxamillion, 16:18:22)

Meeting ended at 16:22:28 UTC.




Action Items

* maxamillion to email Anaconda LVM RAID Change owner to request
  questions on devel list be addressed




Action Items, by person
---
* maxamillion
  * maxamillion to email Anaconda LVM RAID Change owner to request
questions on devel list be addressed
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (46)
* zodbot (12)
* Rathann (11)
* jforbes (8)
* jwb (8)
* jsmith (8)
* nirik (6)
* sgallagh (2)
* kalev (0)
* dgilmore (0)

Minutes:

https://meetbot.fedoraproject.org/fedora-meeting/2017-02-17/fesco.2017-02-17-16.00.html
Minutes (text):

https://meetbot.fedoraproject.org/fedora-meeting/2017-02-17/fesco.2017-02-17-16.00.txt
Log:

https://meetbot.fedoraproject.org/fedora-meeting/2017-02-17/fesco.2017-02-17-16.00.log.html
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announce: Fedora Layered Image Release

[Adam Miller]

Hello all,
On behalf of the Fedora Atomic WG[0] and Fedora Release
Engineering[1], I am pleased to announce the first ever Fedora Layered
Image Release. Each Container Image is released with the following
streams which aim to provide lifecycle management choices to our
users:

Name
Name-Version
Name-Version-Release

Each of the Name and Name-Version tags will be updated in place with
their respective updates for as long as the maintainer supports them
and the Name-Version-Release will always be a frozen in time reference
to that particular release of the Container Image.

At this time the following Container Images are available in the
Fedora Registry.

registry.fedoraproject.org/f25/cockpit:130-1.f25docker
registry.fedoraproject.org/f25/cockpit:130
registry.fedoraproject.org/f25/cockpit
registry.fedoraproject.org/f25/kubernetes-node:0.1-2.f25docker
registry.fedoraproject.org/f25/kubernetes-node:0.1
registry.fedoraproject.org/f25/kubernetes-node
registry.fedoraproject.org/f25/toolchain:1-1.f25docker
registry.fedoraproject.org/f25/toolchain:1
registry.fedoraproject.org/f25/toolchain
registry.fedoraproject.org/f25/kubernetes-master:0.1-3.f25docker
registry.fedoraproject.org/f25/kubernetes-master:0.1
registry.fedoraproject.org/f25/kubernetes-master

From now on we will be doing regularly scheduled releases of Fedora
Layered Image content that will match the Fedora Atomic Two Week
Release schedule.

We are currently working on a way to provide browse and search
functionality for Fedora Container Images so please stay tuned for
that.

For those interested, the source of this content is provided in
DistGit which can easily be searched via the container-specific pkgdb
namespace[2].

As always, we welcome feedback and would encourage anyone interested
to come join the Fedora Atomic WG[0] as we continue to iterate on
integrating the Project Atomic[3] family of technologies into Fedora.

Anyone interested in contributing Container Images, please feel free
to join in and submit one for Review[4][5].

Thank you,
-AdamM

[0] - https://pagure.io/atomic-wg
[1] - https://docs.pagure.org/releng/
[2] - https://admin.fedoraproject.org/pkgdb/packages/docker/%2A/
[3] - http://www.projectatomic.io/
[4] - https://fedoraproject.org/wiki/Container:Review_Process
[5] - https://fedoraproject.org/wiki/Container:Guidelines
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2017-02-17)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2017-02-17 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1635 Self Contained Changes: Anaconda LVM RAID
.fesco 1635
https://pagure.io/fesco/issue/1635

= New business =

#topic #1635 Self Contained Changes: The GNU C Library version 2.25
.fesco 1635
https://pagure.io/fesco/issue/1635

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

[Adam Miller]

On Tue, Dec 13, 2016 at 4:18 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> On Tue, Dec 13, 2016 at 2:52 PM, Igor Gnatenko <ignate...@redhat.com> wrote:
>> On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller
>> <maxamill...@fedoraproject.org> wrote:
>>> It is with great pleasure that the Fedora Project Announces the availability
>>> of the Fedora Docker Layered Image Build Service[0] to the Fedora 
>>> Contributor
>>> Community!
>>>
>>> With this announcement we are opening availability of the Docker Layered
>>> Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
>>> SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
>>> official components of Fedora. From there we will be extending an invitation
>>> to all Fedora Contributors to maintain Docker Layered Image Containers for
>>> official release by the Fedora Project. Currently this effort is to enable
>>> the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
>>> primary deliverable to power the future of Cloud. This is also to enable the
>>> Fedora Modularity[5] work be delivered as Containers in the future as Fedora
>>> becomes fundamentally more modular in nature.
>>>
>>> How do I get started?
>>>
>>> Contributors will go through a simliar process as what they currently do
>>> with RPM Review Requests. There will be Container Reviews as well as
>>> Container Guidelines:
>>>
>>> https://fedoraproject.org/wiki/Container:Review_Process
>>> https://fedoraproject.org/wiki/Container:Guidelines
>> Nice job!
>>
>> I have couple of questions:
>> * why "FROM fedora:25", how do I choose version on which I want to
>> base container?
>
> The 'FROM fedora:25' line should coordinate with the branch of DistGit
> you're working in. Since Docker doesn't have a mechanism like RPMs do
> with macros where we can parameterize things like that, we just have
> to define it for now (we may later change it to where the 'FROM
> fedora:$version' is inferred and something makes a modification to the
> Dockerfile before building.
>
>> * is there containers in registry for rawhide?
>
> There are not at this moment, only for Fedora 24 and Fedora 25. I hope
> to have rawhide enabled very soon though. The layout of DistGit
> branches correlated to Fedora release information fed into the Build
> System is something that needs be sorted since "branched" Fedora
> Releases have a version number tied to DistGit but Rawhide is
> technically f26 right now. I'll update as soon as this is live.

Rawhide is now live, you can 'fedpkg container-build' from DistGit
master branch just like you can 'fedpkg build' for rawhide RPMs.

Apologies for the delay,
-AdamM

>
> -AdamM
>
>>>
>>> At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
>>> the Review Process along with input from all Fedora Contributors. This may
>>> change later with the formation of a Fedora Container Committee (similar to
>>> the Fedora Packaging Committee[6]).
>>>
>>> Please note that both the Guidelines and the Review Process are likely to
>>> evolve along with the Container technologies as we move into the future so
>>> we encourage community members to check the documentation for updates.
>>>
>>> For more information, please see the following Fedora Community Blog:
>>>
>>> 
>>> https://communityblog.fedoraproject.org/fedora-docker-layered-image-build-service-now-available/
>>>
>>> [0] - 
>>> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>>> [1] - https://fedoraproject.org/wiki/Cloud
>>> [2] - 
>>> https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
>>> [3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
>>> [4] - https://getfedora.org/en/atomic/download/
>>> [5] - https://fedoraproject.org/wiki/Modularity
>>> [6] - https://fedoraproject.org/wiki/Packaging_Committee
>>> ___
>>> devel mailing list -- devel@lists.fedoraproject.org
>>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>
>>
>>
>> --
>> -Igor Gnatenko
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

[Adam Miller]

On Thu, Dec 15, 2016 at 5:49 AM, Trishna Guha <trishnaguh...@gmail.com> wrote:
> On Wed, Dec 14, 2016 at 1:06 AM, Adam Miller
> <maxamill...@fedoraproject.org> wrote:
>> Contributors will go through a simliar process as what they currently do
>> with RPM Review Requests. There will be Container Reviews as well as
>> Container Guidelines:
>
> Absolutely great news.
>
> I have couple of questions regarding Container review process.
> After container build are we going to request updates for fedora
> release braches using Bodhi?
> As discussed in 15-12-2016 Atomic-wg meeting we are going to have
> taskotron automated testcases as well.
> Are these all going to use Bodhi interface like it happens for RPM packages?
>

At this time there will not be Bodhi updates, but there will be a
RelEng process that will perform releases every other week
(alternating with the weeks that we do Two Week Atomic Releases). Once
the Taskotron work is in place (being released soon), we'll have
automated testing happening on every container build in koji and then
there will be fedmsg data stored in datagrepper that we can query to
find out the latest version of a container that is successfully
passing all it's tests.

I'll update the wiki page with information about this.

-AdamM

>
> --
> Regards,
> Trishna Guha
>
> trishnaguh...@gmail.com
> trishnag.wordpress.com
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announcement: Fedora Docker Layered Image Build Service is GO!

[Adam Miller]

It is with great pleasure that the Fedora Project Announces the availability
of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
Community!

With this announcement we are opening availability of the Docker Layered
Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
official components of Fedora. From there we will be extending an invitation
to all Fedora Contributors to maintain Docker Layered Image Containers for
official release by the Fedora Project. Currently this effort is to enable
the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
primary deliverable to power the future of Cloud. This is also to enable the
Fedora Modularity[5] work be delivered as Containers in the future as Fedora
becomes fundamentally more modular in nature.

How do I get started?

Contributors will go through a simliar process as what they currently do
with RPM Review Requests. There will be Container Reviews as well as
Container Guidelines:

https://fedoraproject.org/wiki/Container:Review_Process
https://fedoraproject.org/wiki/Container:Guidelines

At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
the Review Process along with input from all Fedora Contributors. This may
change later with the formation of a Fedora Container Committee (similar to
the Fedora Packaging Committee[6]).

Please note that both the Guidelines and the Review Process are likely to
evolve along with the Container technologies as we move into the future so
we encourage community members to check the documentation for updates.

For more information, please see the following Fedora Community Blog:


https://communityblog.fedoraproject.org/fedora-docker-layered-image-build-service-now-available/

[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - https://fedoraproject.org/wiki/Cloud
[2] - 
https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
[3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
[4] - https://getfedora.org/en/atomic/download/
[5] - https://fedoraproject.org/wiki/Modularity
[6] - https://fedoraproject.org/wiki/Packaging_Committee
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org

Re: Announcement: Fedora Docker Layered Image Build Service is GO!

[Adam Miller]

On Tue, Dec 13, 2016 at 2:52 PM, Igor Gnatenko <ignate...@redhat.com> wrote:
> On Tue, Dec 13, 2016 at 8:36 PM, Adam Miller
> <maxamill...@fedoraproject.org> wrote:
>> It is with great pleasure that the Fedora Project Announces the availability
>> of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
>> Community!
>>
>> With this announcement we are opening availability of the Docker Layered
>> Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
>> SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
>> official components of Fedora. From there we will be extending an invitation
>> to all Fedora Contributors to maintain Docker Layered Image Containers for
>> official release by the Fedora Project. Currently this effort is to enable
>> the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
>> primary deliverable to power the future of Cloud. This is also to enable the
>> Fedora Modularity[5] work be delivered as Containers in the future as Fedora
>> becomes fundamentally more modular in nature.
>>
>> How do I get started?
>>
>> Contributors will go through a simliar process as what they currently do
>> with RPM Review Requests. There will be Container Reviews as well as
>> Container Guidelines:
>>
>> https://fedoraproject.org/wiki/Container:Review_Process
>> https://fedoraproject.org/wiki/Container:Guidelines
> Nice job!
>
> I have couple of questions:
> * why "FROM fedora:25", how do I choose version on which I want to
> base container?

The 'FROM fedora:25' line should coordinate with the branch of DistGit
you're working in. Since Docker doesn't have a mechanism like RPMs do
with macros where we can parameterize things like that, we just have
to define it for now (we may later change it to where the 'FROM
fedora:$version' is inferred and something makes a modification to the
Dockerfile before building.

> * is there containers in registry for rawhide?

There are not at this moment, only for Fedora 24 and Fedora 25. I hope
to have rawhide enabled very soon though. The layout of DistGit
branches correlated to Fedora release information fed into the Build
System is something that needs be sorted since "branched" Fedora
Releases have a version number tied to DistGit but Rawhide is
technically f26 right now. I'll update as soon as this is live.

-AdamM

>>
>> At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
>> the Review Process along with input from all Fedora Contributors. This may
>> change later with the formation of a Fedora Container Committee (similar to
>> the Fedora Packaging Committee[6]).
>>
>> Please note that both the Guidelines and the Review Process are likely to
>> evolve along with the Container technologies as we move into the future so
>> we encourage community members to check the documentation for updates.
>>
>> For more information, please see the following Fedora Community Blog:
>>
>> 
>> https://communityblog.fedoraproject.org/fedora-docker-layered-image-build-service-now-available/
>>
>> [0] - 
>> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>> [1] - https://fedoraproject.org/wiki/Cloud
>> [2] - 
>> https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
>> [3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
>> [4] - https://getfedora.org/en/atomic/download/
>> [5] - https://fedoraproject.org/wiki/Modularity
>> [6] - https://fedoraproject.org/wiki/Packaging_Committee
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
>
> --
> -Igor Gnatenko
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Announcement: Fedora Docker Layered Image Build Service is GO!

[Adam Miller]

It is with great pleasure that the Fedora Project Announces the availability
of the Fedora Docker Layered Image Build Service[0] to the Fedora Contributor
Community!

With this announcement we are opening availability of the Docker Layered
Image Build Service for the Docker Layered Images[1] that the Fedora Cloud
SIG[2] has been the primary maintainers[3] of on GitHub into DistGit as
official components of Fedora. From there we will be extending an invitation
to all Fedora Contributors to maintain Docker Layered Image Containers for
official release by the Fedora Project. Currently this effort is to enable
the Fedora Cloud/Atomic WG[2] goals which target Fedora Atomic Host[4] as a
primary deliverable to power the future of Cloud. This is also to enable the
Fedora Modularity[5] work be delivered as Containers in the future as Fedora
becomes fundamentally more modular in nature.

How do I get started?

Contributors will go through a simliar process as what they currently do
with RPM Review Requests. There will be Container Reviews as well as
Container Guidelines:

https://fedoraproject.org/wiki/Container:Review_Process
https://fedoraproject.org/wiki/Container:Guidelines

At this time the Cloud/Atomic WG[2] will maintain the Guidelines as well as
the Review Process along with input from all Fedora Contributors. This may
change later with the formation of a Fedora Container Committee (similar to
the Fedora Packaging Committee[6]).

Please note that both the Guidelines and the Review Process are likely to
evolve along with the Container technologies as we move into the future so
we encourage community members to check the documentation for updates.

For more information, please see the following Fedora Community Blog:


https://communityblog.fedoraproject.org/fedora-docker-layered-image-build-service-now-available/

[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - https://fedoraproject.org/wiki/Cloud
[2] - 
https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers/
[3] - https://github.com/fedora-cloud/Fedora-Dockerfiles
[4] - https://getfedora.org/en/atomic/download/
[5] - https://fedoraproject.org/wiki/Modularity
[6] - https://fedoraproject.org/wiki/Packaging_Committee
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2016-12-09)

[Adam Miller]

===
#fedora-meeting: FESCO (2016-12-09)
===


Meeting started by maxamillion at 16:00:37 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-12-09/fesco.2016-12-09-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:40)

* #1635 F26 Self Contained Changes (Java Security Policy)  (maxamillion,
  16:10:07)
  * LINK: https://pagure.io/fesco/issue/1635#comment-43494
(maxamillion, 16:10:07)
  * AGREED: Approve F26 Self Contained Change Java Security Policy (+1:
5, -1: 0, +0: 0)  (maxamillion, 16:18:40)

* #1646 No appropriate sudo directory for user scripts  (maxamillion,
  16:18:50)
  * LINK: https://pagure.io/fesco/issue/1646   (maxamillion, 16:18:50)
  * AGREED: Defer decision of Issue #1646 until 2016-12-16
(maxamillion, 16:21:28)

* #1635 F26 Self contained Changes - Zend Framework 3  (maxamillion,
  16:21:35)
  * LINK: https://pagure.io/fesco/issue/1635#comment-45817
(maxamillion, 16:21:35)
  * AGREED: F26 Self Contained Change - Zend Framework 3 (+1: 6, -1: 0,
+0: 0)  (maxamillion, 16:24:53)

* #1652 i686 is not on primary mirror location  (maxamillion, 16:25:21)
  * LINK: https://pagure.io/fesco/issue/1652   (maxamillion, 16:25:21)
  * AGREED: Proposal: FESCo will draft an announcement for the demotion
of i686 to an atlernative architecture and seek Council input before
publishing. Secondly, FESCo will draft an architecture demotion
process. (+1: 5, -1: 0, +0: 0)  (maxamillion, 16:46:39)

* Next week's chair  (maxamillion, 16:48:21)
  * jsmith to chair FESCo Meeting 2016-12-16  (maxamillion, 16:49:26)

* Open Floor  (maxamillion, 16:49:37)
  * Reminder that 5 FESCo seats are open for elections now
https://fedoraproject.org/wiki/Elections  (maxamillion, 16:50:27)
  * AGREED: Cancel FESCo Meetings on 2016-12-23 and 2016-12-30
(maxamillion, 17:00:51)

Meeting ended at 17:02:03 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (88)
* jwb (43)
* Rathann (27)
* jsmith (21)
* zodbot (15)
* sgallagh (13)
* dgilmore (3)
* nirik (0)
* paragan (0)
* kalev (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-12-09)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-12-09 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1635 F26 Self Contained Changes (Java Security Policy)
.fesco 1635
https://pagure.io/fesco/issue/1635#comment-43494

#topic #1646 No appropriate sudo directory for user scripts
.fesco 1646
https://pagure.io/fesco/issue/1646

= New business =

#topic #1651 F26 System Wide Change: Fedora 26 Boost 1.63 upgrade
.fesco 1651
https://pagure.io/fesco/issue/1651

#topic #1650 F26 System Wide Change: Debugging Information For Static Libraries
.fesco 1650
https://pagure.io/fesco/issue/1650

#topic #1635 F26 Self contained Changes - Zend Framework 3
.fesco 1635
https://pagure.io/fesco/issue/1635#comment-45817

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-11-18)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-11-18 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= New business =

#topic #1635 F26 Self Contained Changes
.fesco 1635
https://pagure.io/fesco/issue/1635

Two on the list for this week:
- Module Build Service
- Modular Compose

https://pagure.io/fesco/issue/1635#comment-42681


#topic #1647 F26 System Wide Change: Fedora 26 C/C++ Compilation Flags Updates
.fesco 1647
https://pagure.io/fesco/issue/1647

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Today's FESCo Meeting (2016-10-21)

[Adam Miller]

Apologies for getting the agenda out late.

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-10-21 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

#topic #1634 EOL and vulnerable software
.fesco 1634
https://pagure.io/fesco/issue/1634

= New business =

#topic #1635 F26 Self Contained Changes
.fesco 1635
https://pagure.io/fesco/issue/1635

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, 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.

-AdamM
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Cloud and Server Q

[Adam Miller]

On Tue, Oct 4, 2016 at 6:21 AM, Kushal Das  wrote:
> On 30/09/16, Josh Berkus wrote:
>> On 09/30/2016 02:01 PM, Josh Boyer wrote:
>>
>> > 16:44:56  Cloud base image is the only blocking deliverable.
>> > 16:44:59  Atomic is not.
>> >
>> > I realize this WG is in the middle of rebooting itself, but to have
>> > clearly conflicting information from the WG members is a bit
>> > concerning.
>>
> Atomic host image is the deliverable for the Atomic WG, which is under 2
> week release cycle. We sync up with the official release version at the
> time of GA, but we continue to be in our 2 week atomic release cycle
> then on the 6month old GA. This is my understanding about all the work
> done for 2 Week Atomic.
>
> Now I may be completely wrong to understand our 2 week release cycle
> process, but this is what I followed for the release-infra work till
> now.
>

This is correct, Fedora Atomic Two-Week Release was meant to allow
Fedora Atomic more flexibility in it's release cycle. Part of the
initial proposal was to remove it from being directly bound to the
standard six month release cycle. If this is something we want to
change, that's fine. However, if we do that we need to get buy in from
all groups involved in that process instead of just change things out
from everyone. Also, people will need to show up to do the work in
Fedora QA because there's a lot of it and we can't realistically ask
them to take on what is effectively 5 new deliverable artifacts
without assistance (ISO, qcow2, raw, vagrant-vbox, vagrant-libvirt).

-AdamM

> Kushal
> --
> Fedora Cloud Engineer
> CPython Core Developer
> https://kushaldas.in
> https://dgplug.org
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Cloud and Server Q

[Adam Miller]

On Fri, Sep 30, 2016 at 8:35 AM, Matthew Miller
 wrote:
> On Thu, Sep 29, 2016 at 04:16:15PM -0700, Adam Williamson wrote:
>> > think QA clearly understands what cloud image(s) are release blocking,
>> > as previously they were just the non-atomic images.
>> Which images are prominent on the download pages and how much of a
>> relationship there is between that and 'release blocking' status is
>> *also* not my problem, but I'd agree with you (Chris) that it'd be
>> rather strange for the most prominently advertised deliverable for a
>> given product not to be a release-blocking one.
>
> I don't think that Atomic *needs* to be release blocking, because if it
> misses the grand unified release, we have the ability to update it at
> the next cycle, so it's less of a big deal. But if we collectively
> prefer to make sure everything is lined up on the release day... I can
> see arguments for that, too.
>

Note that the cycle that Matt is mentioning here is Two-Week
iterations for Atomic Host so the window to release is relatively
rapid compared to the standard ~6 months.

-AdamM


>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Cloud and Server Q

[Adam Miller]

On Fri, Sep 30, 2016 at 8:35 AM, Matthew Miller
 wrote:
> On Thu, Sep 29, 2016 at 04:16:15PM -0700, Adam Williamson wrote:
>> > think QA clearly understands what cloud image(s) are release blocking,
>> > as previously they were just the non-atomic images.
>> Which images are prominent on the download pages and how much of a
>> relationship there is between that and 'release blocking' status is
>> *also* not my problem, but I'd agree with you (Chris) that it'd be
>> rather strange for the most prominently advertised deliverable for a
>> given product not to be a release-blocking one.
>
> I don't think that Atomic *needs* to be release blocking, because if it
> misses the grand unified release, we have the ability to update it at
> the next cycle, so it's less of a big deal. But if we collectively
> prefer to make sure everything is lined up on the release day... I can
> see arguments for that, too.
>
>
> --
> Matthew Miller
> 
> Fedora Project Leader
> ___
> cloud mailing list -- cl...@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Meeting Minutes for Friday's FESCo Meeting (2016-08-19)

[Adam Miller]

On Thu, Aug 18, 2016 at 4:43 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the
> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
> irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2016-08-12 16:00 UTC'
>
>
> Links to all tickets below can be found at:
> https://fedorahosted.org/fesco/report/9
>
> = Followups =
>
> #topic #1605 finish retirement of sysvinit-only packages
> .fesco 1605
> https://fedorahosted.org/fesco/ticket/1605
>
> #topic #1606 F25 approved Changes not in MODIFIED status
> .fesco 1606
> https://fedorahosted.org/fesco/ticket/1606
>
> #topic #1609 Fedora 26 schedule proposal
> .fesco 1609
> https://fedorahosted.org/fesco/ticket/1609
>
> #topic #1611 Continued lack of support for RPM weak deps in distro tooling
> .fesco 1611
> https://fedorahosted.org/fesco/ticket/1611
>
> = New business =
>
> #topic #1613 Deletion of EOL AMIs
> .fesco 1613
> https://fedorahosted.org/fesco/ticket/1613
>
> #topic #1614 FHS exception for /snap
> .fesco 1614
> https://fedorahosted.org/fesco/ticket/1614
>
>
> = Open Floor =
>
> For more complete details, please visit each individual
> ticket.  The report of the agenda items can be found at
> https://fedorahosted.org/fesco/report/9
>
> 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/fesco, 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.

===
#fedora-meeting: FESCO (2016-08-19)
===


Meeting started by maxamillion at 16:00:29 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-08-19/fesco.2016-08-19-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:40)

* Follow Ups  (maxamillion, 16:03:01)

* #1605 finish retirement of sysvinit-only packages  (maxamillion,
  16:03:14)
  * LINK: https://fedorahosted.org/fesco/ticket/1605   (maxamillion,
16:03:35)

* #1606 F25 approved Changes not in MODIFIED status  (maxamillion,
  16:07:23)
  * LINK: https://fedorahosted.org/fesco/ticket/1606   (maxamillion,
16:07:23)
  * AGREED: defer KillUserProcess to Fedora 26 (+1: 8, -1: 0, +0: 0)
(maxamillion, 16:20:50)
  * AGREED: maxamillion to take the review of cargo to move the rust
change through (+1: 8, -1: 0, +0: 0)  (maxamillion, 16:23:51)
  * AGREED: defer Koji Generates Installation Media change until Fedora
26 (+1: 8, -1: 0, +0: 0)  (maxamillion, 16:28:41)
  * AGREED: Approve Release Engineering Automation Workflow Engine
Change (+1: 8, -1: 0, +0: 0)  (maxamillion, 16:32:11)

* #1609 Fedora 26 schedule proposal  (maxamillion, 16:32:22)
  * LINK: https://fedorahosted.org/fesco/ticket/1609   (maxamillion,
16:32:22)
  * AGREED: more in ticket discussion needed for schedule, will revisit
later  (maxamillion, 16:45:36)

* #1611 Continued lack of support for RPM weak deps in distro tooling
  (maxamillion, 16:45:44)
  * LINK: https://fedorahosted.org/fesco/ticket/1611   (maxamillion,
16:45:49)
  * AGREED: releng will try and move all compose tools to support weak
deps, but in the mean time issues with composes and weak deps will
need to be handled on a case by case basis. (+1: 9, -1: 0, +0: 0)
(maxamillion, 16:56:28)

* New Business  (maxamillion, 16:57:28)

* #1613 Deletion of EOL AMIs  (maxamillion, 16:57:34)
  * LINK: https://fedorahosted.org/fesco/ticket/1613   (maxamillion,
16:57:34)
  * AGREED: defer decision on Deletion of EOL AMIs until the AWS billing
issue is sorted (+1: 7, -1: 0, +0: 1)  (maxamillion, 17:15:17)

* #1614 FHS exception for /snap  (maxamillion, 17:15:25)
  * LINK: https://fedorahosted.org/fesco/ticket/1614   (maxamillion,
17:15:26)
  * LINK:

https://build.opensuse.org/package/show/system:snappy/golang-github-snapcore-snapd
(Pharaoh_Atem, 17:23:24)
  * ACTION: maxamillion to reach out to openSUSE, arch, and debian
contacts on /snap topic to aid in cross-distro agreement on approach
(maxamillion, 17:31:15)
  * AGREED: defer FHS exception for /snap until next week's meeting (+1:
8, -1: 0, +0: 0)  (maxamillion, 17:36:08)

* #1615 Consider Wayland by default for F25  (maxamillion, 17:38:11)
  * LINK: https://fedorahosted.org/fesco/ticket/1615   (maxamillion,
17:38:19)
  * AGREED: FESCo agrees to go ahead with Wayland by default provided
that release notes and common bugs are clear about how to switch
back to X11 if needed. (+1: 7, -1: 0, +0: 0)  (maxamillion,
17:46:26)

* #1612 Provenpackager request jforbes  (

Schedule for Friday's FESCo Meeting (2016-08-19)

[Adam Miller]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-08-12 16:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1605 finish retirement of sysvinit-only packages
.fesco 1605
https://fedorahosted.org/fesco/ticket/1605

#topic #1606 F25 approved Changes not in MODIFIED status
.fesco 1606
https://fedorahosted.org/fesco/ticket/1606

#topic #1609 Fedora 26 schedule proposal
.fesco 1609
https://fedorahosted.org/fesco/ticket/1609

#topic #1611 Continued lack of support for RPM weak deps in distro tooling
.fesco 1611
https://fedorahosted.org/fesco/ticket/1611

= New business =

#topic #1613 Deletion of EOL AMIs
.fesco 1613
https://fedorahosted.org/fesco/ticket/1613

#topic #1614 FHS exception for /snap
.fesco 1614
https://fedorahosted.org/fesco/ticket/1614


= Open Floor =

For more complete details, please visit each individual
ticket.  The report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

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/fesco, 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://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2016-07-22) - Meeting Minutes

[Adam Miller]

On Thu, Jul 21, 2016 at 5:56 PM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> Following is the list of topics that will be discussed in the FESCo
> meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2016-07-22 16:00 UTC'
>
>
> Links to all tickets below can be found at:
> https://fedorahosted.org/fesco/report/9
>
> = Followups =
>
> #topic #1594 F25 System Wide Change: IBus Emoji Typing
> .fesco 1594
> https://fedorahosted.org/fesco/ticket/1594
>
> = New business =
>
> #topic #1568 F25 Self Contained Changes
> (Change/Remove slogin and sshd-keygen, GNS3, Rust Compiler)
> .fesco 1568
> https://fedorahosted.org/fesco/ticket/1568#comment:29
>
>
> = Open Floor =
>
> For more complete details, please visit each individual ticket.  The
> report of the agenda items can be found at
> https://fedorahosted.org/fesco/report/9
>
> 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/fesco,
> 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.
>
> Thank you
> -AdamM


===
#fedora-meeting: FESCO (2016-07-22)
===


Meeting started by maxamillion at 16:00:13 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-07-22/fesco.2016-07-22-16.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 16:00:16)

* Follow Up Items  (maxamillion, 16:03:24)

* #1594 F25 System Wide Change: IBus Emoji Typing  (maxamillion,
  16:03:28)
  * LINK: https://fedorahosted.org/fesco/ticket/1594   (maxamillion,
16:03:44)
  * AGREED: FESCo Approves #1594 F25 System Wide Change: IBus Emoji
Typing (+1:5, +0:1, -1:0)  (maxamillion, 16:11:18)

* New Business  (maxamillion, 16:11:55)

* #1568 F25 Self Contained Changes (Change/Remove slogin and
  sshd-keygen, GNS3, Rust Compiler)  (maxamillion, 16:12:08)
  * LINK: https://fedorahosted.org/fesco/ticket/1568#comment:29
(maxamillion, 16:12:19)
  * AGREED: FESCo Approves #1568 F25 Self Contained Changes
(Change/Remove slogin and sshd-keygen, GNS3, Rust Compiler) (+1:6,
+0:0, -1:0)  (maxamillion, 16:25:33)

* Next week's chair  (maxamillion, 16:25:51)
  * nirik to chair next week's FESCo meeting  (maxamillion, 16:27:17)

* Open Floor  (maxamillion, 16:27:28)

Meeting ended at 16:35:38 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (71)
* dgilmore (36)
* number80 (23)
* jsmith (21)
* zodbot (12)
* nirik (11)
* paragan (11)
* sgallagh (0)
* kalev (0)
* jwb (0)




Generated by `MeetBot`_ 0.1.4
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-07-22)

[Adam Miller]

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-07-22 16:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1594 F25 System Wide Change: IBus Emoji Typing
.fesco 1594
https://fedorahosted.org/fesco/ticket/1594

= New business =

#topic #1568 F25 Self Contained Changes
(Change/Remove slogin and sshd-keygen, GNS3, Rust Compiler)
.fesco 1568
https://fedorahosted.org/fesco/ticket/1568#comment:29


= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

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/fesco,
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.

Thank you
-AdamM
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

RFC: Round 2 review of Fedora Docker Layered Image Guidelines

[Adam Miller]

Hello all,
I had previously sent out a RFC email about a month ago asking for
feedback on the Fedora Docker Layered Image Guidelines[0].

I was asked by FESCo to start a new thread so that this can be
discussed further on the devel mailing list before we discuss it in
FESCo. Therefore if there are any requested items from the original
email thread that would like to be revisited, please bring them up
here.

Beyond that, my main question to everyone beyond the discussions we
had previously is: Is there any interest in forming a Fedora Container
Packaging Committee (I'm not married to the name, apply whatever color
of paint to that bikeshed) just as we have the Fedora Packaging
Committee?

Links of interest also in the first thread[1][2][3][4]

[0] - 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VHXGAR2YMVSJXYZPWH5A27JFFFLRR3IG/
[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - https://fedoraproject.org/wiki/PackagingDrafts/Containers
[2] - 
https://fedoraproject.org/wiki/PackagingDrafts/Package_Review_Process_with_Containers
[3] - 
https://fedoraproject.org/wiki/Draft/Packaging:DockerLayeredImageNamingGuidelines
[4] - https://fedorahosted.org/fesco/ticket/1573
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: RFC: Fedora Docker Layered Image Guidelines

[Adam Miller]

On Tue, May 3, 2016 at 12:32 PM, Kevin Fenzi <ke...@scrye.com> wrote:
> On Tue, 3 May 2016 11:22:30 -0500
> Adam Miller <maxamill...@fedoraproject.org> wrote:
>
>> Collection of RPMs is fine, the goal is just not to ship non-rpm code
>> or content yet outside of Docker-ized application control scripts
>> where needed/applicable.
>
> ok.
>>
>> It shouldn't but it can in the future, I was more or less replicating
>> this information in the beginning to hopefully leave some space for
>> this to change in the future of the Fedora Modularization efforts
>> because a module could potentially have it's own versioning scheme
>> outside of the content inside of it.
>
> Has it been decided that modules are docker containers?

Not to the best of my knowledge, but afaik modules could be containers
and/or optionally be distributed as such.
>
>> > And any guidelines on naming? Just use common sense? They will have
>> > to be unique.
>>
>> Yes, need to be unique. This is going to follow the RPM naming
>> guidelines for now.
>
> Well, sure, but say I make a container that is some web app + web
> server + database. Do I call it by the app name? The web server name? A
> combo?

So a question around this topic has come up recently on IRC, I was
hoping to see it make it to the mailing list but it has not.

Something we've not yet addressed yet and that we really need to, is
how to handle multi-service containers *OR* multi-container services
(I was secretly hoping to have a Container Guidelines SIG exist that
could hash this out).

Providing an all-in-one docker image is certainly something we can do
such that the container image provides web server + database + web
app, but it seems more popular to have each element (server, database,
app) be placed into it's own container and have them be "wired"
together via some tooling. There's many examples of open source
multi-container orchestration solutions[0][1][2][3][4][5][6] (and
likely others I'm not familiar with). Also, the Project Atomic
upstream group has an open specification for how to define these
multi-container services called Nulecule[7] that is meant to be
independent of the backend implementation of container orchestration
engine but simply a definition template/spec which is something I'd
also like to see considered.

As a side note, there's a reference implementation of the Nulecule
spec called Atomic App[8] that might also be worth while for
consideration from the group on the topic.

>
>> > I guess the build system has network access and people can put
>> > anything in CMD lines? How can we make reproducible builds? Or
>> > should CMD be restricted to only some network resources.
>>
>> The build system does currently but ultimately doesn't need it since
>> we can inject internal Fedora mirrors into the build environment that
>> the container is built in. Which is something we may or may not want
>> to do. The CMD lines likely need some guidelines around them and
>> should be added to the doc.
>
> Yeah, if we aren't restricting the network for builds, anyone can do
> anything in a CMD line right? and since it depends on something
> outside in the net it may be changed or gone later when we rebuild.

This is true and is probably something we should address in the near
term. I'll work on this in the staging environment and report back.

>
>> > So it's assumed here that someone is a packager to submit new
>> > container reviews? Or would we want some kind of 'containerger'
>> > role for people who maintainer containers?
>>
>> That's up for discussion. I think they should be separate because
>> being well versed in creating Docker images doesn't inherently mean
>> someone is well versed in creating RPMs, just as the inverse is not
>> inherently true. I've in the past gotten some flack for that opinion
>> so I'd definitely like that to be opened up to more discussion.
>
> Sure. I think seperate would be ok.

+1

>
>> > I agree with the folks downthread we can make a bugzilla "Container
>> > Review" to compliment Package Review. Unless we think we can spin
>> > up a review application for these (like we are still hopefully
>> > planning on doing for packages someday).
>>
>> +1
>>
>> >
>> > Also, we will need to make pkgdb create components for each
>> > container as well for people to report bugs against.
>>
>> +1 - I'm honestly not sure how to go about that, I assume I need to
>> send a request to BZ folks somehow but how BZ is admin'd/hosted is a
>> bit of a black box to me. I would appreciate advisement on that.
>
> Fedora Infrastructure has a ad

Re: RFC: Fedora Docker Layered Image Guidelines

[Adam Miller]

On Mon, May 2, 2016 at 12:07 PM, Kevin Fenzi <ke...@scrye.com> wrote:
> On Thu, 28 Apr 2016 17:52:44 -0500
> Adam Miller <maxamill...@fedoraproject.org> wrote:
>
>> Hello all,
>> We're wrapping up the first phase of the Fedora Docker Layered
>> Image Build Service[0] and the time has come to start thinking about
>> what we as a Project need to do to formalize what it means to be
>> shipping Docker Layered Images once we are capable of building and
>> distributing them.
>>
>> These are effectively going to compliment their RPM counterpart
>> at least in the beginning since we as a Project have never shipped
>> any build artifact other than RPMs as a part of the distribution
>> before. We can grow organically from there if we want to extend
>> beyond the initial offering for Docker Layered Images but I thought
>> following RPM as a guide in the beginning was a reasonable goal to
>> achieve. Some areas that seemed pertinant right off the bat are
>> below, for each of them I have alread created a Draft document that I
>> would appreciate feedback on.
>
> So, at least at first it's assumed there will just be one rpm in each
> container? Or can we have a collection of rpms that make sense to be
> together?

Collection of RPMs is fine, the goal is just not to ship non-rpm code
or content yet outside of Docker-ized application control scripts
where needed/applicable.

>
>> Docker Layered Image "packaging" Guidelines [1]
>
> Whats the difference here between version and release? Does version
> change any based on the version of the primary rpm in the container?

It shouldn't but it can in the future, I was more or less replicating
this information in the beginning to hopefully leave some space for
this to change in the future of the Fedora Modularization efforts
because a module could potentially have it's own versioning scheme
outside of the content inside of it.

>
> And any guidelines on naming? Just use common sense? They will have to
> be unique.

Yes, need to be unique. This is going to follow the RPM naming
guidelines for now.

>
> I guess the build system has network access and people can put anything
> in CMD lines? How can we make reproducible builds? Or should CMD be
> restricted to only some network resources.

The build system does currently but ultimately doesn't need it since
we can inject internal Fedora mirrors into the build environment that
the container is built in. Which is something we may or may not want
to do. The CMD lines likely need some guidelines around them and
should be added to the doc.

>
>> Package Review Process with a Docker Containers section [2]
>
> This might be better as a Container review process seperate from the
> Package review process, ie a different page?

Yes, it very well could be. I just put them together as a first pass
effort to get feedback from others. I'm open to them being separate
and don't have a real preference here.

>
> So it's assumed here that someone is a packager to submit new container
> reviews? Or would we want some kind of 'containerger' role for people
> who maintainer containers?

That's up for discussion. I think they should be separate because
being well versed in creating Docker images doesn't inherently mean
someone is well versed in creating RPMs, just as the inverse is not
inherently true. I've in the past gotten some flack for that opinion
so I'd definitely like that to be opened up to more discussion.

>
>> Docker Layered Images Naming Guildelines [3]
>
> I am not sure what to add to make this more concrete, but I think it
> needs to be. ;)

Agreed, I was hoping others could help fill in the blanks. :)

>>
>> The Fedora Cloud SIG has done a first-pass review of these (thanks
>> Cloud SIG!) so hopefully there's a certainly level of sanity to them
>> but I'm absolutely open to new ideas and extending the content with
>> more coverage.
>>
>> Another point to note is that we need to determine how this should be
>> handled in BZ components for bug reporting as well as for filing
>> review requests.
>
> I agree with the folks downthread we can make a bugzilla "Container
> Review" to compliment Package Review. Unless we think we can spin up a
> review application for these (like we are still hopefully planning on
> doing for packages someday).

+1

>
> Also, we will need to make pkgdb create components for each container
> as well for people to report bugs against.

+1 - I'm honestly not sure how to go about that, I assume I need to
send a request to BZ folks somehow but how BZ is admin'd/hosted is a
bit of a black box to me. I would appreciate advisement on that.

-AdamM

>
> kevin
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: RFC: Fedora Docker Layered Image Guidelines

[Adam Miller]

On Sun, May 1, 2016 at 10:26 AM, Subhendu Ghosh  wrote:
> If we assume that image is immutable, how does one expect the applications
> configuration and data to be managed? Are there additional ENV handlers
> inside the container that might not be present otherwise in the RPM world?
> Is there are requirement for volume mounts for certain locations inside the
> container?  Should that be expressed via labels?

+1

Yes, that's something we should likely handle in the guidelines.


-AdamM

>
> -subhendu
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: RFC: Fedora Docker Layered Image Guidelines

[Adam Miller]

On Fri, Apr 29, 2016 at 7:55 AM, Colin Walters <walt...@verbum.org> wrote:
> On Thu, Apr 28, 2016, at 06:52 PM, Adam Miller wrote:
>
>> Docker Layered Image "packaging" Guidelines [1]
>
> This current design means Dockerfiles are always secondary shims.
> I think the most interesting case is for new services which are
> Docker/container only at least upstream.
>

Yes, for now that is the case. In the future we want to enable
Docker-only content, but the current thought is to start small before
opening the floodgates and then work  to make sure we have some level
of validation along the pipeline. We have validation in place for RPMs
and we will eventually for Docker Images, just not there yet.

> Do we e.g. require systemd unit files for the RPM that contains the code?
> I don't think we should, but the current page says "packaged properly as RPMs"
> which implies all current RPM requirements.

Yes, the initial goal here is to just wrap pre-existing sets of RPMs
into Docker Images to provide out-of-the-box runnable services. From
there we can decide what all we want to do with these and what
capabilities will be required to enable a more flexible workflow in
the future.

> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

RFC: Fedora Docker Layered Image Guidelines

[Adam Miller]

Hello all,
We're wrapping up the first phase of the Fedora Docker Layered Image
Build Service[0] and the time has come to start thinking about what we as a
Project need to do to formalize what it means to be shipping Docker Layered
Images once we are capable of building and distributing them.

These are effectively going to compliment their RPM counterpart at least
in the beginning since we as a Project have never shipped any build artifact
other than RPMs as a part of the distribution before. We can grow organically
from there if we want to extend beyond the initial offering for Docker
Layered Images but I thought following RPM as a guide in the beginning was a
reasonable goal to achieve. Some areas that seemed pertinant right off the
bat are below, for each of them I have alread created a Draft document that
I would appreciate feedback on.

Docker Layered Image "packaging" Guidelines [1]

Package Review Process with a Docker Containers section [2]

Docker Layered Images Naming Guildelines [3]

The Fedora Cloud SIG has done a first-pass review of these (thanks Cloud
SIG!) so hopefully there's a certainly level of sanity to them but I'm
absolutely open to new ideas and extending the content with more coverage.

Another point to note is that we need to determine how this should be handled
in BZ components for bug reporting as well as for filing review requests.

Something else what was brought up when I originally submitted these ideas to
FESCo[4] (aside from the fact that this should go to devel list first) was
that it is probably a good idea to establish a Container-centric Guidelines
Committee much in the way there is a Fedora Packaging Committee (which focuses
on RPMs). My question to everyone on that topic is, would there be enough
interest to establish such a committee?

As a side note and just a matter of opinion but I think the idea of forming
a Committee to help shepherd these new types of deliverables through Fedora
will help to enable aspects of Fedora Modularization[5] which ultimately will
be good for the whole of the Fedora Project.

I look forward to questions and feedback.

Thank you,
-AdamM


[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - https://fedoraproject.org/wiki/PackagingDrafts/Containers
[2] - 
https://fedoraproject.org/wiki/PackagingDrafts/Package_Review_Process_with_Containers
[3] - 
https://fedoraproject.org/wiki/Draft/Packaging:DockerLayeredImageNamingGuidelines
[4] - https://fedorahosted.org/fesco/ticket/1573
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Summary/Minutes for today's FESCo meeting (2016-03-11)

[Adam Miller]

===
#fedora-meeting: FESCO (2016-03-11)
===


Meeting started by maxamillion at 17:00:19 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2016-03-11/fesco.2016-03-11-17.00.log.html
.



Meeting summary
---
* init process  (maxamillion, 17:00:38)

* Follow Up Items  (maxamillion, 17:03:51)

* #1552 Review of delayed Changes for F24  (maxamillion, 17:03:59)

* #1555 Please clarify updates policy for security issues  (maxamillion,
  17:07:57)
  * AGREED: Defer #1555 to next week's meeting (2016-03-18) to allow
jsmith time to update (+1: 9, 0:0, -1:0)  (maxamillion, 17:10:15)

* New Business  (maxamillion, 17:11:00)

* #1559 jvanek would like to become provenpacakger  (maxamillion,
  17:11:08)
  * AGREED: Remove ProvenPackager tickets from the meeting agenda since
there are no -1's in the tickets  (maxamillion, 17:14:58)

*   (maxamillion, 17:15:14)

* #1560 provenpackager request: yselkowitz  (maxamillion, 17:15:32)
  * AGREED: Remove ProvenPackager tickets from the meeting agenda since
there are no -1's in the tickets  (maxamillion, 17:15:41)

* #1518 Software packaged in Fedora should not be allowed to implement
  DRM schemes that cannot be disabled  (maxamillion, 17:16:43)

* Next week's chair  (maxamillion, 17:20:01)
  * nirik to chair next week's meeting (2016-03-18)  (maxamillion,
17:20:52)
  * paragan will not be available next week, attending fossasia
conference.  (paragan, 17:22:01)
  * AGREED: Cancel meeting the week of 2016-03-25 (+1:8, 0:0, -1:0)
(maxamillion, 17:26:18)

* Open Floor  (maxamillion, 17:27:11)
  * LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/24/alpha/buglist
(nirik, 17:29:34)

Meeting ended at 17:42:11 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* maxamillion (89)
* sgallagh (27)
* nirik (25)
* zodbot (17)
* dgilmore (15)
* jsmith (13)
* jwb (11)
* number80 (8)
* paragan (5)
* kalev (3)
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-03-11)

[Adam Miller]

Apologies for the late email, this is my first time as chair. :)

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 17:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-03-11 17:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#1518 Software packaged in Fedora should not be allowed to implement
DRM schemes that cannot be disabled
.fesco 1518
https://fedorahosted.org/fesco/ticket/1518

#1552 Review of delayed Changes for F24
.fesco 1552
https://fedorahosted.org/fesco/ticket/1552

#1555 Please clarify updates policy for security issues
.fesco 1555
https://fedorahosted.org/fesco/ticket/1555

= New business =

#1559 jvanek would like to become provenpacakger
.fesco 1559
https://fedorahosted.org/fesco/ticket/1559

#1560 provenpackager request: yselkowitz
.fesco 1560
https://fedorahosted.org/fesco/ticket/1560


= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

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/fesco,
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
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Orphaning Package: oggvideotools

[Adam Miller]

I plan to orphan oggvideotools, I don't have the time to really give
it the proper attention it needs anymore. It is currently failing to
build in rawhide.

https://admin.fedoraproject.org/pkgdb/package/rpms/oggvideotools/

-AdamM
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Proposal: spins-kickstarts workflow changes

[Adam Miller]

On Fri, Feb 19, 2016 at 1:37 PM, Kevin Fenzi  wrote:
> Greetings.
>
> I am sending this to the devel and spins lists. Feel free to forward to
> other places people who might be affected by it should see it.
>
> Some history:
>
> We setup the spin-kickstart project on fedorahosted a long time ago.
> At the start it was just the various spins and it's trac instance was
> used in the new spins workflow. Then, it was a handy place to put the
> dvd iso kickstart that releng made also. Then over time we added cloud
> and docker and everything else that used a kickstart to it. In the
> start we added some bugzilla components for the various spins for end
> user bugs, and used the trac for workflow things. Over time due to
> all the images there lots of people have been given commit access to
> the repo. Then the spins sig went quiet and we have sort of been limping
> along since then with trac tickets not getting to anyone who cares,
> etc.
>
> I'd like to propose the following plan of action:
>
> * Setup a new project at pagure.io called just kickstarts or
>   releng-kickstarts or something. (Bikeshed alert).
>
> * Setup tags for all the various groups that have kickstarts. ie,
>   'xfce' 'docker' 'cloud' 'atomic' 'workstation' etc. And get someone
>   from each of those groups to actually watch the tags or someone to CC
>   on who will actually look at those tagged issues.
>
> * Reduce the number of commiters a bunch and ask people to submit PR's
>   when they want a change. This will allow releng/qa to control changes
>   when in freeze. ie, we can require a freeze break and point to the
>   PR/bug with the exact change and merge it when it's approved.
>
> * Copy the git repo over to it from fedorahosted. Close that repo.
>
> * Mass close all the fedorahosted trac tickets and close trac to new
>   ones with a note to file new issues in pagure. ( 21 tickets
>   currently): https://fedorahosted.org/spin-kickstarts/report/1
>
> * Close the "LiveCD*" components in bugzilla to new bugs and close any
>   existing ones with a note to refile at pagure. (18 bugs currently):
>   
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=LiveCD=LiveCD%20-%20FEL=LiveCD%20-%20Games=LiveCD%20-%20KDE=LiveCD%20-%20LXDE=LiveCD%20-%20Xfce_id=4654195=Fedora_format=advanced
>
> * Adjust koji config to pull from pagure.io instead of fedorahosted.
>
> Thoughts? Additional steps? Better plans?

Seems like a logical plan that would offer us a lot of improvements
over the current workflow. Sounds great! +1

-AdamM

>
> kevin
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[EPEL-devel] Re: Commit access for EPEL branches?

[Adam Miller]

On Mon, Feb 1, 2016 at 12:57 PM, Kevin Fenzi  wrote:
> On Mon, 1 Feb 2016 08:58:13 -0700
> Dave Johansen  wrote:
>
>> I would like to package rpmorphan for EL [1]. I created an EPEL 7
>> branch, but the current owner/maintainer of the EPEL 5 and 6 branches
>> hasn't responded to my requests for commit access. Is there some way
>> for me to get commit access or do I have to go through the whole
>> non-responsive maintainer process [2]?
>>
>> [1]: https://admin.fedoraproject.org/pkgdb/package/rpms/rpmorphan/
>> [2]:
>> https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
>
> I pinged them on IRC, hopefully they will see this soon...
>

Yup, that's 100% my fault. I completely missed this in my email.
Access granted. Apologies for the delay. Thanks Kevin for reaching
out.

-AdamM

> kevin
>
> ___
> epel-devel mailing list
> epel-devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
>
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

Re: F24 Self Contained Change: sen - terminal user interface for docker engine

[Adam Miller]

On Mon, Dec 7, 2015 at 9:28 AM, Jan Kurik  wrote:
> = Proposed Self Contained Change: sen - terminal user interface for
> docker engine =
> https://fedoraproject.org/wiki/Changes/sen--tui-for-docker
>
> Change owner(s):
> * Tomas Tomecek 
>
> sen enables you to manage your containers and images interactively
> directly from command line. Interface is similar to htop, alot or tig.

+1 - I've been following sen on github for a little while now. I think
this would be great to have in Fedora.

-AdamM

>
> == Detailed Description ==
> * it can interactively manage your containers and images:
> -- manage? start, stop, restart, kill, delete,...
> * you are able to inspect containers and images
> * sen can fetch logs of containers and even stream logs real-time
> * all buffers support searching and filtering
> * sen receives real-time updates from docker when anything changes
> -- e.g. if you create a container in another terminal, sen will pick it up
> * sen notifies you whenever something happens (and reports slow queries)
> * supports a lot of vim-like keybindings (j, k, gg, /, ...)
>
> == Scope ==
> Proposal owners:
> * package sen to Fedora
> * provide an information it's available and documentation how to use
> it (maybe via developer portal, or release notes)
>
> Other developers: N/A (not a System Wide Change)
> Release engineering: N/A (not a System Wide Change)
> List of deliverables: N/A (not a System Wide Change)
> Policies and guidelines: N/A (not a System Wide Change)
> Trademark approval: N/A (not needed for this Change)
> --
> Jan Kuřík
> Platform & Fedora Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
> ___
> devel-announce mailing list
> devel-annou...@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel-annou...@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: F24 System Wide Change: Layered Docker Image Build Service

[Adam Miller]

On Thu, Dec 3, 2015 at 8:12 AM, Tomas Hozza <tho...@redhat.com> wrote:
> On 03.12.2015 14:54, Jan Kurik wrote:
>> On Thu, Dec 3, 2015 at 2:38 PM, Tomas Hozza <tho...@redhat.com> wrote:
>>> On 03.12.2015 11:40, Jan Kurik wrote:
>>>> = Proposed System Wide Change: Layered Docker Image Build Service =
>>>> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
>>>>
>>>> Change owner(s):
>>>> * Colin Walters 
>>>> * Adam Miller 
>>>> * Tomas Tomecek 
>>>> * Tim Waugh 
>>>> * Amanda Carter 
>>>>
>>>> Fedora currently ships a Docker base image, but Docker supports a
>>>> layering concept. There are some applications like Cockpit which we
>>>> would like to ship as layered applications.
>>>> This change will deploy the build service to support building and
>>>> delivering a set of layered Docker images, and will enable Fedora
>>>> contributors to create and maintain Dockerfiles from which those
>>>> images will be generated.
>>>>
>>>> == Detailed Description ==
>>>> This change opens up an new type of official binary artifact produced
>>>> by Fedora. Currently, we produce two main types of artifacts: RPMs,
>>>> and images. The RPMs are created in Koji from specfiles in dist-git.
>>>> The images come in different formats, but have in common creation in
>>>> Koji from kickstart files — this includes the official Fedora Docker
>>>> Base Image. This change introduces a new type of image, a Docker
>>>> Layered Image, which is created from a Dockerfile and builds on top of
>>>> that base image.
>>>>
>>>> The system has five major parts:
>>>>
>>>> A command-line client — already integrated into rpkg; needs only minor
>>>> work to enable in fedpkg (there is discussion about either extending
>>>> fedpkg or adding a new fedcontainer utility)
>>>> * dist-git for Dockerfiles
>>>> * A koji plugin, containerbuild
>>>> * An OpenShift 3 backend
>>>> * A distribution mechanism; a Docker Registry
>>>> * Currently evaluating options for this
>>>> * * Pulp Crane
>>>> * * Docker Registry
>>>>
>>>> == Scope ==
>>>> For the Scope of this Change please check
>>>> https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service#Scope
>>>>
>>>
>>> Hi.
>>>
>>> The "Ongoing Work Tracking" link does not work.
>>
>> Fixed. Thanks for verifying.
>>
>>> How is this different from the proposal for Fedora 23 [1]?
>>> What changed?
>>
>> It is not different. The project has started at F23 time however has
>> not been finished on time. This is continuation of the project.
>
> I'm curious to hear from the change owners if anything changed and
> what pieces that blocked this from being done last time are still pending
> and what is already done.

It was a few things but the biggest issue was that upstream docker was
in-flight on retiring the old image format (V1) in favor of the new
one (V2) which has implications on how a "non-native" docker build
system (read: something other than the docker daemon) can
import/export docker images to and from a registry which required a
lot of re-engineering the backend of the OSBS build system. Basically
the "docker save" functionality disappeared in V2 upstream without any
replacement. This work is mostly done and the build system can work
with V2 registries now.

I'm also not entirely sure this is a "system wide change" as others
might classify it. For people who are just using Fedora, if we missed
the deadline or messed something up, they wouldn't notice so it's
possible this needs to change in classification.

-AdamM

>
> Thanks.
>
> Tomas
>
>> Regards,
>> Jan
>>
>>> [1] https://fedorahosted.org/fesco/ticket/1461
>>>
>>> Thanks!
>>>
>>> Regards,
>>> --
>>> Tomas Hozza
>>> Software Engineer - EMEA ENG Developer Experience
>>>
>>> PGP: 1D9F3C2D
>>> UTC+1 (CET)
>>> Red Hat Inc. http://cz.redhat.com
>>> --
>>> devel mailing list
>>> devel@lists.fedoraproject.org
>>> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>>
>>
>>
>
> --
> Tomas Hozza
> Software Engineer - EMEA ENG Developer Experience
>
> PGP: 1D9F3C2D
> UTC+1 (CET)
> Red Hat Inc. http://cz.redhat.com
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Review Swap Request

[Adam Miller]

Hello all,
I would like to request a review for the OpenShift Origin package
and would be happy to review someone else's package in return.

origin - OpenShift Open Source Container Management by Red Hat
https://bugzilla.redhat.com/show_bug.cgi?id=1287822

Thank you,
-AdamM
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: [RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

Hello all,
After consideration and discussion of feedback from this thread
with members of the Fedora Infrastructure and Fedora Apps team
(special thanks to pingou and threebean), the following is the
proposal we'd like to move forward with:

DistGit Restructure/Namespace
  - Move all current rpm packages that live under repositories/ to
live under repositories/rpms/
  - Create new namespaces for other things (i.e. - repositories/docker/)


Current DistGit layout:
/srv/git/repositories/.git
future:
-> /srv/git/repositories/rpms/.git
(symlinked to the old location for a migration time period)
=> At one point, will break `git pull` if the remote url isn't fixed
-> /srv/git/repositories/docker/.git
=> /srv/git/repositories//.git

This will require updates to different aspects of the Fedora
Apps/Infrastructure over time which will be addressed in phases.
Everything will continue to function with business as usual during the
transition periods with the symlinks in place for backwards
compatibility.

In the future, users of fedpkg can do the following:

fedpkg clone /

Examples:

fedpkg clone rpms/foo
fedpkg clone docker/bar

In the event the namespace is omitted, fedpkg will default to rpms/foo
in order to maintain function-alike backwards compatibility.

If this proposal is agreed upon by general consensus, the teams
involved will begin to scope out what systems need what modifications
and begin the migration, with updates along the way (in case folks are
interested).

I look forward to feedback, thank you.

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

Re: [RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

On Fri, Nov 13, 2015 at 3:47 PM, Ralph Bean <rb...@redhat.com> wrote:
> On Thu, Nov 12, 2015 at 03:01:49PM -0500, Ray Strode wrote:
>> Hi,
>>
>> On Tue, Nov 10, 2015 at 1:08 PM, Adam Miller
>> <maxamill...@fedoraproject.org> wrote:
>> > If we were to go with the former rather than the latter, we would need
>> > to find a way to "namespace" container images so they can be
>> > determined as different. I've thought about this a lot and I worry
>> > about defining a namespace by some alphanumberic sequence because I
>> > just know that at some point there will end up being a piece of
>> > software in the ecosystem that we want to package as a rpm that will
>> > share this pattern and result in problematic filtering. We could
>> > accept that risk and simply say "this sequence is a reserved word" or
>> > use a special character as the leading character in a DistGit
>> > repository name to signify that it is a container.
>>
>> git repositories normally use '/' to separate namespaces, so i'd propose
>>
>> $ fedpkg clone containers/cockpit
>>
>> and maybe add support for
>>
>> $ fedpkg clone srpms/cockpit
>>
>> at the same time.
>>
>> This has the added benefit that cgit will automatically filter docker
>> reposistories when you visit, e.g,
>>
>> http://pkgs.fedoraproject.org/cgit/containers/
>
> I like this too.  Here are three thoughts:
>
> Perhaps, we use 'dockerfiles' for the prefix instead of 'containers',
> because presumably there will be some whole new way to build
> containers in 2017, and we'll need to keep our dockerfiles/ repos
> separate from our awesomefiles/ repos.
>
> We could also use this opportunity to move the kickstarts (another
> input to koji builds) away from https://fedorahosted.org/spin-kickstarts
> and over to dist-git as well, with a namespace like 'kickstarts/kde'
> and 'kickstarts/lxde'.
>
> The existing rpm content could be moved to a 'specfiles/' namespace
> (or maybe 'srpms/'?) but we could further add some apache httpd rules that
> respond with a redirect to the 'srpms/' namespace if the requests to
> the base namespaceless-namespace level are met with a 404. -- "when in
> doubt, default to srpms/".  That might help keep some of our existing
> tools working as-is without too much catastrophe.

+1

I'm a big fan of where this is going.

Maybe we should draft a proposal around this (maybe some notes in
gobby?) and then start a new thread under a new name to generate more
general discussion around this in the context of being able to deliver
many different kinds of artifact for Fedora.Next. My only fear of
continuing this topic thread is that folks who aren't interested in
containers or docker might not be tuned in because of the subject
line.

Thoughts?

-AdamM

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

Re: [RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

On Fri, Nov 13, 2015 at 5:14 PM, Brian C. Lane <b...@redhat.com> wrote:
> On Tue, Nov 10, 2015 at 12:08:25PM -0600, Adam Miller wrote:
>> Hello all,
>> In the Fedora 24 timeframe the Fedora Release Engineering group is
>> aiming to deliver the Layered Image Build Service[0] to allow Fedora
>> contributors to build containers images. In the first iteration of
>> this we're targeting Docker layered image support. Part of this will
>> be to allow Fedora contributors to maintain Dockerfiles much like we
>> maintain rpm spec files via DistGit.
>
> So you're talking about one docker file per package, right? Or are these
> going to pull from multiple packages and have the docker container be a
> different level of object? Or both?

Both, it's mostly at the discretion of the person attempting to
deliver something in a container. Some may be simple "I added httpd on
top of the base Fedora Docker image" and others might be "I put all of
ownCloud into a container so you can just run the whole thing with
this one command"

That being said, I'm not married to the concept. It was just the idea
going into it. If the general consensus among the community is "one
Dockerfile to one package" we could go that route.

>
> If you're talking about a 1:1 package:docker mapping then the only thing
> that makes sense to me is to have them live in the current system next
> to the .spec files. Anything else will easily introduce divergence from
> the rpm packages.

Absolutely, so far there has been the expectation that there will be
divergence because of the more "dynamic" nature of what containers
bring to the table.

>
> I also see that 'container packager' and 'rpm packager' are used in the
> build service page. I don't think these should be separate roles,
> everyone should be a packager. If you have one role working on container
> building for a package and another who only does rpm packaging we're
> going to, again, end up with things diverging.

I believe they will diverge naturally as time goes on. Also, I don' t
think everyone who has rpm packaging expertise is well versed in the
ways of Docker and vice versa.

>
> Some things I'd suggest (given I don't know the answers to the above
> questions):
>
> 1. All bits have to come from koji built rpms. No rebuilding of bits
> for docker, it just installs existing bits.

That is the plan, but configuration can take place inside the context
of the container image build process to allow for single-command
execution.

>
> 2. docker files for packages live in dist-git next to the package spec
> file.

We can, pending the agreement that's all we as a community/project use
Dockerfiles for. The original idea going in to this though is that we
could extend this to provide a more full featured solution for
services that would need more than one package. Even simple things
like httpd modules (mod_wsgi, mod_php, etc) would technically ship
more rpms than they produce in the docker image.

Also in the distant future (out of scope for the original offering),
we'd like to look at delivering multi-container apps via Nulecule[0]
specifications.

>
> 3. Any meta-containers collecting using packages are also an rpm
> package, following whatever naming convention gets decided on.
> fedora-docker-foo would make sense to me.

I'm not sure I follow what you mean here, why would something that
only comes as a Dockerfile also be a rpm?

>
> 4. package level docker files are maintained by the same people who maintain
> the package.
>

This certainly makes sense if we end up going the package:container 1:1 route.

-AdamM

[0] - https://github.com/projectatomic/nulecule

> --
> Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA 
> (PST8PDT)
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [EPEL-devel] SPEC file for nginx package ?

[Adam Miller]

On Thu, Nov 12, 2015 at 3:52 PM, Wojciech Sciesinski
 wrote:
> Hi!
>
> I would like create my own package for nginx with builtin
> nginx-dav-ext-module https://github.com/arut/nginx-dav-ext-module .
>
> If someone of you can share with me SPEC file for nginx rpm package?

It's publicly available in Fedora's DistGit here:

http://pkgs.fedoraproject.org/cgit/nginx.git/tree/?h=epel7

-AdamM

>
> Thank you in advance.
>
> --
> Wojciech Ściesiński, wojci...@sciesinski.net
> ___
> epel-devel mailing list
> epel-devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/epel-devel
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel

Re: i3wm based minimal Spin?

[Adam Miller]

On Wed, Nov 11, 2015 at 10:29 PM, Dan Book  wrote:
> On Wed, Nov 11, 2015 at 11:20 PM, Dennis Chen  wrote:
>>
>> Hi,
>>
>> What are the chances that a minimal desktop spin can be created for the
>> 24 release? It would be nice to have a prepackaged "desktop
>> environment" with the terminal as it's main focus.

I've thought about doing this a few times in the past but decided not
to because I generally expect folks who want very minimal systems with
tiling window managers like i3wm are going to want things very
customized exactly the way they like them (myself included). My
approach right now is just to install a minimal system with the net
installer and then run an ansible playbook[0] I have to setup my
laptop the way I like it along with my configs[1] and I'd be surprised
if others who use tiling window managers have a much different
approach.

That being said, if there are enough people interested in agreeing on
some sort of a baseline such that we have a nice LiveCD/USB image that
can be installed from, I'd be open to discussing and helping maintain
an i3wm spin.

-AdamM

[0] - https://github.com/maxamillion/ansible-maxamillion-workstation
[1] - https://github.com/maxamillion/dotfiles

>>
>> Dennis Chen
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/devel
>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
>
> As with anything, it probably depends foremost on someone being willing to
> set it up. There is a "Basic Desktop" group that could be used.
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

On Thu, Nov 12, 2015 at 4:57 AM, Tomas Tomecek <ttome...@redhat.com> wrote:
> Quoting Adam Miller (2015-11-10 19:08:25)
>> Cockpit's Dockerfile repo in DistGit would be stored with a
>> leading special character:
>> fedpkg clone -cockpit
>>
>
> How about
>
> $ fedpkg clone cockpit-docker
>
>
> Pros
>
>  * no need to change infrastructure
>
>  * easy to use
>
>  * repo name suggests content

I do like this, but I almost think if we were going to go this route
we should have a policy around naming a container in DistGit with a
prefix. I'd then suggest something like "ctr" to mean "container":

$ fedpkg clone ctr-cockpit

We would however need to request some kind of gating mechanism in
pkgdb to make whatever the prefix is be a "reserved word" that
wouldn't become the name of package in the future or else it would
cause havok.

Another thing that was mentioned to me was if we have separate DistGit
instances containing packages and containers named the same thing that
koji would be unhappy so that's definitely something we need to keep
in mind.

>
> Cons
>
>  * not a different namespace (in fact same namespace as rpms)
>
>  * someone can do `fedpkg clone cockpit-docker && cd cockpit-docker && fedpkg
>build` and get scared that it doesn't work
>
>* `build` could be aware of Dockerfile and run `container-build` actually
>
>* error could suggest using different build method

I'd vote for a detection of Dockerfile without a spec file error out
and suggest an alternative build method.

>
>
> What's the way of building (qcow, docker base) images? Could that approach be
> resued? (meaning, what's the way of storing kickstart files atm?)

Currently the kickstarts are flattened and passed to the koji
image-build command as a parameter, they are all stored as part of the
spin-kickstarts[0] fedorahosted space and aren't really managed at all
like DistGit.

-AdamM

[0] - https://fedorahosted.org/spin-kickstarts/

>
>
> ~~
> Tomáš Tomeček
> Software Engineer
> Developer Experience
> UTC+2 (CEST)
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

Hello all,
In the Fedora 24 timeframe the Fedora Release Engineering group is
aiming to deliver the Layered Image Build Service[0] to allow Fedora
contributors to build containers images. In the first iteration of
this we're targeting Docker layered image support. Part of this will
be to allow Fedora contributors to maintain Dockerfiles much like we
maintain rpm spec files via DistGit.

However we need to make a couple of decisions about naming conventions
such that we can distinguish between rpms and container images as they
are stored in Fedora DistGit. Also, alternatively we could setup a
completely separate DistGit for container images that is disjoint from
the one used for rpms. I would love feedback on everyone's preferences
between those two options.

If we were to go with the former rather than the latter, we would need
to find a way to "namespace" container images so they can be
determined as different. I've thought about this a lot and I worry
about defining a namespace by some alphanumberic sequence because I
just know that at some point there will end up being a piece of
software in the ecosystem that we want to package as a rpm that will
share this pattern and result in problematic filtering. We could
accept that risk and simply say "this sequence is a reserved word" or
use a special character as the leading character in a DistGit
repository name to signify that it is a container. A special character
is the option I propose.

Proposal:
In the event that container images (Dockerfiles for now, others in
the future) and rpm spec files are to share the DistGit repositories,
the container images leading character would be a special character.
The decision upon which special character is open to the community at
large to decide but certain ones impose obvious limitations for shell
quoting and the like. For the sake of example I will use the special
character '-' as my marker for a container image DistGit repository.
Also in the example I'm going to use the cockpit-project[1] as it is
already something that is packaged as an rpm[2] in Fedora and
delivered as a container image[3] built from it's Fedora rpm set.

Example:
Cockpit's rpm spec repo in DistGit would be stored as it is today:
fedpkg clone cockpit

Cockpit's Dockerfile repo in DistGit would be stored with a
leading special character:
fedpkg clone -cockpit

Here, the leading '-' signifies that it is the container image
DistGit repository which would make it an illegal name for an rpm by
the N-V-R convention.

The technical details of this are all open to change so feel free to
tell me I'm crazy and present a new idea and I'm happy to pursue it.

Looking forward to feedback.

Thank you,
-AdamM

[0] - https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[1] - http://cockpit-project.org/
[2] - https://apps.fedoraproject.org/packages/cockpit
[3] - https://hub.docker.com/r/cockpit/ws/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

On Tue, Nov 10, 2015 at 12:35 PM, Josh Boyer <jwbo...@fedoraproject.org> wrote:
> On Tue, Nov 10, 2015 at 1:08 PM, Adam Miller
> <maxamill...@fedoraproject.org> wrote:
>> Hello all,
>> In the Fedora 24 timeframe the Fedora Release Engineering group is
>> aiming to deliver the Layered Image Build Service[0] to allow Fedora
>> contributors to build containers images. In the first iteration of
>> this we're targeting Docker layered image support. Part of this will
>> be to allow Fedora contributors to maintain Dockerfiles much like we
>> maintain rpm spec files via DistGit.
>>
>> However we need to make a couple of decisions about naming conventions
>> such that we can distinguish between rpms and container images as they
>> are stored in Fedora DistGit. Also, alternatively we could setup a
>> completely separate DistGit for container images that is disjoint from
>> the one used for rpms. I would love feedback on everyone's preferences
>> between those two options.
>>
>> If we were to go with the former rather than the latter, we would need
>> to find a way to "namespace" container images so they can be
>> determined as different. I've thought about this a lot and I worry
>> about defining a namespace by some alphanumberic sequence because I
>> just know that at some point there will end up being a piece of
>> software in the ecosystem that we want to package as a rpm that will
>> share this pattern and result in problematic filtering. We could
>> accept that risk and simply say "this sequence is a reserved word" or
>> use a special character as the leading character in a DistGit
>> repository name to signify that it is a container. A special character
>> is the option I propose.
>>
>> Proposal:
>> In the event that container images (Dockerfiles for now, others in
>> the future) and rpm spec files are to share the DistGit repositories,
>> the container images leading character would be a special character.
>> The decision upon which special character is open to the community at
>> large to decide but certain ones impose obvious limitations for shell
>> quoting and the like. For the sake of example I will use the special
>> character '-' as my marker for a container image DistGit repository.
>> Also in the example I'm going to use the cockpit-project[1] as it is
>> already something that is packaged as an rpm[2] in Fedora and
>> delivered as a container image[3] built from it's Fedora rpm set.
>>
>> Example:
>> Cockpit's rpm spec repo in DistGit would be stored as it is today:
>> fedpkg clone cockpit
>>
>> Cockpit's Dockerfile repo in DistGit would be stored with a
>> leading special character:
>> fedpkg clone -cockpit
>>
>> Here, the leading '-' signifies that it is the container image
>> DistGit repository which would make it an illegal name for an rpm by
>> the N-V-R convention.
>>
>> The technical details of this are all open to change so feel free to
>> tell me I'm crazy and present a new idea and I'm happy to pursue it.
>
> How much collaboration do we expect around the dockerfiles?  I would
> think significantly more than an RPM spec file.  With an RPM, there
> are only a handful of ways to build the software and adding patches
> isn't a high-frequency/multi-maintainer event (usually).
>

I'm honestly not entirely sure. I think that will just kind of
organically happen. I would like to try and get a sense of what people
would like to come out of it though so that we can cater to the
preferred workload.

> If we expect dockerfiles to be more dynamic, then I would prefer a
> separate git instance.  Then we don't have to worry about collisions
> and hacks.  We can also set up a separate set of ACLs around who is
> allow to commit to them, etc.

That's definitely an option. I'm open to either but we can do that now
with what's surrounding DistGit.

-AdamM

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

Re: [RFC] DistGit Container Image namespacing for Layered Image Build Service

[Adam Miller]

On Tue, Nov 10, 2015 at 12:57 PM, Mathieu Bridon <boche...@daitauha.fr> wrote:
> On Tue, 2015-11-10 at 12:08 -0600, Adam Miller wrote:
>> Hello all,
>> In the Fedora 24 timeframe the Fedora Release Engineering group
>> is
>> aiming to deliver the Layered Image Build Service[0] to allow Fedora
>> contributors to build containers images. In the first iteration of
>> this we're targeting Docker layered image support. Part of this will
>> be to allow Fedora contributors to maintain Dockerfiles much like we
>> maintain rpm spec files via DistGit.
>>
>> However we need to make a couple of decisions about naming
>> conventions
>> such that we can distinguish between rpms and container images as
>> they
>> are stored in Fedora DistGit. Also, alternatively we could setup a
>> completely separate DistGit for container images that is disjoint
>> from the one used for rpms. I would love feedback on everyone's
>> preferences between those two options.
>
> You could set it up in /srv/git/containers, in parallel to the current
> /srv/git/rpms ?
>
> That nicely avoids naming collisions.
>
> It also should be quite asy now that dist-git is in ansible, you could
> probably just factor out the path in the roles as a variable?
>
>> Cockpit's Dockerfile repo in DistGit would be stored with a
>> leading special character:
>> fedpkg clone -cockpit
>
> With the "-" as a leading character, you open yourself to nice errors
> with the fact that it could be recognized as options. So you'd want to
> type: fedpkg clone -- -cockpit

Yeah, all special characters have special oddities. Some of them we
have to consider from many targets and not just the shell so it's
probably not ideal.

>
> Alternatively, if you separate the two distgits, you could have a
> fedcontainer tool, which would just be fedpkg but with its
> configuration pointing to the container distgit, the container build
> service, etc...
>
> Or maybe just a: fedpkg --container clone cockpit ?

Definitely something along these lines is what we'd want to do. I like
the idea. +1

>
> Most of the code (at least the one handling dist-git) could probably be
> reused without any difference.

Yes, it's likely something we'd want to maintain in the same code base
and have one just be a light wrapper of the other with the different
code paths as necessary.

>
> All in all, separating them seems much simpler to me.
>
> You'd have a bit of work up front (to adapt the Ansible playbooks and
> fedpkg slightly), but you pretty much avoid a whole class of issues
> with naming collisions, cli options, and future surprises.
>

Agreed.

+1

-AdamM

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

Re: Fedora Developer Portal - released !!!!

[Adam Miller]

On Mon, Nov 2, 2015 at 7:37 AM, Petr Hracek  wrote:
> Hello folks,
>
> I am happy to announce that Fedora Developer Portal is released.
> Official web address is http://developer.fedoraproject.org.
> Official ticket on Fedora infrastructure is here [1]. Thanks to kevin from
> Fedora Infrastructure team.
> And Mairin Duffy for design the portal from scratch
> Developing instance is located here [2].
>
> *Fedora developer portal:*
> The aim of the portal is to give an overview about important development
> tools and projects in Fedora (like Docker, Vagrant, DevAssistant).
> Focus is targeted on beginners, advanced users and developers.
>
> *Who will use the portal?*
> Fedora developer portal shows users how to develop on Fedora easily, and of
> course introduces them to new projects and tools that are available in
> Fedora.
> Fedora users will have and overview about:
> - new technologies
> - available developer languages
> - projects released in each Fedora release cycle
> - import tools in Fedora (like Docker, Vagrant, DevAssistant, etc.)
> - other tools which can be used for development
>
> All portal is located on GitHub here [3].
> Git repo with website, CSS and rest of stuff, is here [4].
> Git repo for contents is here [5].
>
> There were already several blog posts like [7][8].
> I am glad to thank you also Adam Samalik, Josef Stribny for cooperation.

This is wonderful, thanks to all involved!

-AdamM

>
> [1] https://fedorahosted.org/fedora-infrastructure/ticket/4876
> [2] http://developer.fedorainfracloud.org/
> [3] https://github.com/developer-portal/
> [4] https://github.com/developer-portal/website
> [5] https://github.com/developer-portal/content
> [6] https://fedoraproject.org/wiki/Websites/Developer
> [7] http://blog.samalik.com/fedora-developer-portal-prototype/
> [8] http://phracek.livejournal.com/1403.html
>
> --
> Petr Hracek
> Software Engineer
> Developer Experience
> Red Hat, Inc
> Mob: +420777056169
> email: phra...@redhat.com
>
> --
> Petr Hracek
> Software Engineer
> Developer Experience
> Red Hat, Inc
> Mob: +420777056169
> email: phra...@redhat.com
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Oprhaned EPEL7 branch of Quassel

[Adam Miller]

Hello all,
I have orphaned the EPEL7 branch of Quassel as I have stopped
using it long ago and no longer have the spare time to give it the
amount of attention it deserves. It's a package with many
co-maintainers so I doubt it will be orphaned for long.

https://admin.fedoraproject.org/pkgdb/package/quassel/

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

Re: Koji: no space left on device

[Adam Miller]

On Fri, Oct 23, 2015 at 1:42 PM, Susi Lehtola
 wrote:
> On 10/23/2015 11:12 AM, Jerry James wrote:
>>
>> Just had a build fail:
>> http://koji.fedoraproject.org/koji/taskinfo?taskID=11560206
>
>
> Me too, on multiple build nodes.

It's going to be a koji-wide problem since they all share a nfs mount.
The issue is known about, the filesystem on the filer ran out of
inodes and it is currently being looked into. (As per a conversation I
observed in #fedora-releng on freenode).

-AdamM

> --
> Susi Lehtola
> Fedora Project Contributor
> jussileht...@fedoraproject.org
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: ansible in Fedora 23+ (python3)

[Adam Miller]

On Mon, Oct 19, 2015 at 4:37 AM, Fabio Alessandro Locati
 wrote:
> 2015-10-19 2:33 GMT+02:00 Kevin Kofler :
>> Dusty Mabe wrote:
>>> Does anyone have a good solution for this? Obviously it would be nice
>>> if ansible went to python3 but I think they have stated clearly that
>>> they are sticking with python2 for backwards compat with systems that
>>> still need 2.4.
>>
>> I don't understand why still nobody has forked Ansible to get it out of the
>> stone age.
>
> It's not so easy. Ansible is based on Twisted which is not yet 100%
> Python3 compatible, as far as I understood.
> Also, the problem is that RedHat still supports RHEL5 systems which
> for today standards are totally legacy and therefore it has to run on
> Python 2.4.

What makes you think it's based on twisted? I just did a 'git grep
twisted' on the ansible code base and got zero hits.

-AdamM

>
> --
> Fabio Alessandro Locati
>
> PGP Fingerprint: B960 BE9D E7A8 FA12 273A  98BB 6D6A 29D6 709A 7851
> https://keybase.io/fale
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Proposal to reduce anti-bundling requirements

[Adam Miller]

On Fri, Sep 11, 2015 at 9:21 AM, Carlos O'Donell <car...@redhat.com> wrote:
> On 09/10/2015 03:42 PM, Adam Miller wrote:
>>> It doesn't matter how rare they are, it'll only take a single bundled
>>> library handled incorrectly to completely screw a running OS. I don't
>>> think this is something that can just be swept under the carpet, it
>>> needs to be addressed as a core part of the proposal and currently is
>>> not.
>>>
>>
>> I was talking to someone at Red Hat Summit from the GCC/glibc team and
>> I was under the impression they (upstream) are working on something
>> that handles the symbol tables to allow parallel installed versions of
>> libs. No idea how far this is along but it's something that people are
>> working towards.
>
> You spoke to me, and I am responding here to clarify exactly what the
> Fedora glibc team trying to do.

+1 - Thanks!

I remember that we spoke but I didn't want to throw you into the
flamewar without warning, but thanks for chiming in! :)

(Also, I got one of those ceramic burr grinders and it's awesome. :) )

>
> The work being done is to enable an alternate linkage model for Ring-0,
> where the implementation and interface of ELF-based shared libraries is
> split in two. Linking is carried out against a curated Ring-0 SDK
> and ensures if we upgrade say, glibc, and have accidentally added a
> new symbol, that no new package can use said symbol until the Ring-0 SDK
> package is updated to also have that symbol. Updating the Ring-0 SDK
> requires careful review and would likely be frozen after GA. The Ring-0
> SDK contains headers, stub libraries, and more.
>
> While this idea of an SDK could be extended to all ELF-based shared
> libraries in the distribution, it gets much harder outside of Ring-0
> and is more work with less benefit. Keep in mind the goal here is to
> provide automation and tooling to measure and control the most important
> core part of the OS, that layer upon which the other layers rely.
>
> The idea itself could allow you to install a brand new glibc on your
> system without impacting any builds you do with rpmbuild, mockbuild,
> etc. You are isolated from the implementation by the new linkage
> model (using curated sysroots). Thus with the brand new glibc, and
> because glibs offers backwards compatibility, you could run newer ISV
> applications that require newer glibc, without needing a VM. This
> ignores several problems like bug-for-bug compatibility, subtle changes
> that alter undefined behaviour or unspecified behaviour, and eventually
> result in the failure of an application to run against a new glibc.
>
> However, with the new linkage model it is possible to use it to upgrade,
> not not run multiple versions, of shared libraries.
>
> If you need different versions of shared libraries then you need to use
> software collections for those libraries (load isolation via the dynamic
> loader), containers (load isolation via namespaces), VMs (load isolation
> at the kernel level).
>
> If you need different versions of the same shared libraries in the same
> process then you must use dlmopen for symbol namespace isolation. Note
> that at present dlmopen is not functional for this purpose in upstream
> glibc master.

Ah ok, I either misunderstood or mis-remembered. Thank you for the
clarification.

-AdamM

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