+1 to both

AGREED: OpenCL self-contained change accepted. Deferring another week on Allwinner ARM for status update. (+5,-2,0)

(See meeting minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-03-12/fesco.2014-03-12-18.00.log.html#l-561 )

Self Contained Changes for 2014-03-19 meeting (I'm going to reuse this ticket as it's still open and let's not pollute FESCo Trac).

Follow up on Allwinner sunxi (A10 / A13 / A20) ARM SoC support - Change owners contacted to provide more details requested by FESCo.

• Add amd map parser to autofs - https://fedoraproject.org/wiki/Changes/Add_amd_map_parser_to_autofs discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196372.html
  The am-utils package provides automount services for automount maps that use an amd format. However, the am-utils project has not been actively maintained for quite a while now.

The am-utils package in Fedora has significant problems that are not easily resolved so an amd format parser is to be added to the autofs package.

• CUPS Journal Logging - https://fedoraproject.org/wiki/Changes/CupsJournalLogging discussed at https://fedoraproject.org/wiki/Changes/CupsJournalLogging

By default, CUPS will send log output to the system journal rather than /var/log/cups/error_log.

Replying to [comment:3 jreznik]:

Follow up on Allwinner sunxi (A10 / A13 / A20) ARM SoC support - Change owners contacted to provide more details requested by FESCo.

I've mostly been working on upstream sunxi support. I've managed to get a lot of patches queued up in -next for 3.15, so once we move to 3.15 we will only need to carry the sunxi-mmc driver and the rest should be there ready to use. I plan to add the (for now much larger) patchset to add usable sunxi support to the rawhide kernel packages soon, say sometime in the next 2 weeks.

Recently I've moved my main attention from upstreaming kernel code to upstreaming u-boot code. This effort is also looking very promising. We will need to carry some (almost entirely self contained) patches in u-boot for the short run, but it looks like we should have everything upstream in a couple of months.

Once I start actually adding the necessary patches to the Fedora packages i should be able to get things up and running fairly quickly. I've chosen to do things this way / in this order, so that the patches which we will be carrying in Fedora will resemble what is going upstream as much as possible.

Replying to [comment:4 jwrdegoede]:

Replying to [comment:3 jreznik]:

Follow up on Allwinner sunxi (A10 / A13 / A20) ARM SoC support - Change owners contacted to provide more details requested by FESCo.

I've mostly been working on upstream sunxi support. I've managed to get a lot of patches queued up in -next for 3.15, so once we move to 3.15 we will only need to carry the sunxi-mmc driver and the rest should be there ready to use. I plan to add the (for now much larger) patchset to add usable sunxi support to the rawhide kernel packages soon, say sometime in the next 2 weeks.

There's no reason to do this. When I spoke with Peter Robinson we agreed that adding anything to any 3.14 based rawhide kernel was pointless given the current F21 draft schedule. Rawhide will move to 3.15 merge window kernels within the next 2 weeks, so adding a large patchset is just going to be a bunch of churn. At this point, we'll just wait until 3.15-rc1/rc2 is out and revisit.

all 3 self contained changes approved. (+7,0,0)

There's no reason to do this. When I spoke with Peter Robinson we agreed that adding anything to any 3.14 based rawhide kernel was pointless given the current F21 draft schedule. Rawhide will move to 3.15 merge window kernels within the next 2 weeks, so adding a large patchset is just going to be a bunch of churn. At this point, we'll just wait until 3.15-rc1/rc2 is out and revisit.

I agree here. The MMC patch is very self contained in 3.14 and allows us to boot the CubieTruck (the one a lot of people are interested in) through to login but there's issues with network/usb/sata/smp so while it boots I don't believe it adds massive value for 3.14. If the MMC patch doesn't land in 3.15 (and Hans comment makes it look like it won't) I'll work with Hans send it through for addition once we have 3.15rc1

Reopening for another Self Contained Changes for 2014-03-26 meeting.

• Security Policy In The Installer - https://fedoraproject.org/wiki/Changes/SecurityPolicyInTheInstaller discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196666.html

There are many known tips and tricks how to make a system more secure, often depending on the use case for the system. With the OSCAP Anaconda Addon and the SCAP Security Guide projects, we may allow users choosing a security policy for their newly installed system.

Agreed on today's FESCo meeting: Security Policy In The Installer was not accepted (-7)
Please consider re-proposing as a kickstart-only feature

Self Contained Changes for 2014-04-02 meeting.

• Amplab Tachyon - https://fedoraproject.org/wiki/Changes/AmplabTachyon discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197168.html

Amplab-Tachyon is a fault tolerant distributed file system enabling reliable file sharing at memory-speed across cluster frameworks.

• Apache Mesos - https://fedoraproject.org/wiki/Changes/ApacheMesos discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197180.html

Apache Mesos is a cluster manager for sharing distributed application frameworks. This change brings Mesos to Fedora, which many have called a micro-kernel for the data center.

• Apache Spark - https://fedoraproject.org/wiki/Changes/ApacheSpark discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196967.html

Apache Spark is a fast and general engine for large-scale data processing. This change brings Spark to Fedora, allowing easy deployment and development of Spark applications on Fedora.

• Improved Scala Ecosystem Support - https://fedoraproject.org/wiki/Changes/ImprovedScalaEcosystem discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196964.html

Fedora now supports several essential parts of the Scala language ecosystem as well as building packages with sbt, the de facto build tool for the Scala community.

• DNSSEC support for FreeIPA - https://fedoraproject.org/wiki/Changes/IPAv3DNSSEC discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197177.html

FreeIPA with integrated DNS server will support serving of DNSSEC secured zones and automatic DNSSEC key maintenance.

This first version will have only the very basic functionality with limited user interface and limited resiliency. Next versions (to be delivered in Fedora 22 time frame) will improve resiliency and user interface significantly.

• NFS Ganesha File Server - https://fedoraproject.org/wiki/Changes/NFSGanesha discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/196968.html

NFS Ganesha is a user mode file server that supports NFSv3, NFSv4, and NFSv4.1 including pNFS for distributed filesystems. It uses loadable filesystem driver modules to support its backend filesystems. It also integrates 9P.2000L file service

Hmmm for the scala one -- do we need packaging guidelines? I think traditionally, additional cosystem packages wouldn't have been approved until packaging guidelines were added.

All Changes for 2014-04-02 FESCo meeting were approved: self contained changes approved with addition to scala that they work to develop packaging guidelines (7+1 0-1)

Self Contained Changes for 2014-04-09 meeting.

• Apache HBase - https://fedoraproject.org/wiki/Changes/ApacheHBase discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197294.html

Apache HBase is a distributed database built on top of Apache Hadoop.

• Apache Hive - https://fedoraproject.org/wiki/Changes/ApacheHive discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197295.html

Apache Hive is a data warehouse built on top of Apache Hadoop.

• Apache Oozie - https://fedoraproject.org/wiki/Changes/ApacheOozie discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197293.html

Apache Oozie is a workflow scheduler system to manage Apache Hadoop jobs.

• Better Erlang Support - https://fedoraproject.org/wiki/Changes/BetterErlangSupport discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197311.html

Update Erlang/OTP to R17, and improve Erlang integration with the rest of Fedora.

• Improved Ivy Packaging - https://fedoraproject.org/wiki/Changes/ImprovedIvyPackaging discussed at https://lists.fedoraproject.org/pipermail/devel/2014-March/197314.html

This change aims at improving the way of packaging Java software, which uses Apache Ivy to manage build dependencies.

• KDE Frameworks 5 - https://fedoraproject.org/wiki/Changes/KDE_Frameworks_5 discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197336.html

KDE Frameworks 5 is a set of libraries and technologies developed in the KDE project over the past 18 years. Most of the frameworks come from the kdelibs module, which has been split, cleaned up, dependencies were strightened and packed into individual libraries. This allows developers and projects outside the KDE ecosystem to make use of these technologies and benefit from work of the KDE Community.

• MATE Desktop 1.8 - https://fedoraproject.org/wiki/Changes/MATE_1.8 discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197364.html

Update MATE Desktop to version 1.8

• AGREED: All F21 Self Contained Changes for 2014-04-09 meeting are approved (+7, -0, 0:0) (t8m, 18:40:13)

Self Contained Changes for 2014-04-16 meeting.

• Playground repository - https://fedoraproject.org/wiki/Changes/Playground_repository discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197617.html

The Playground repository gives contributors a place to host packages that are not up to the standards of the main Fedora repository but may still be useful to other users. For now the Playground repository contains both packages that are destined for eventual inclusion into the main Fedora repository and packages that are never going to make it there. Users of the repository should be willing to endure a certain amount of instability when using packages from there.

• Apache Accumulo - https://fedoraproject.org/wiki/Changes/ApacheAccumulo discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197756.html

The Apache Accumulo is a scalable sorted, distributed, key/value store.

• Apache Ambari - https://fedoraproject.org/wiki/Changes/ApacheAmbari discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197757.html

Apache Ambari is a cluster management framework and UI for Apache Hadoop.

• Apache Pig - https://fedoraproject.org/wiki/Changes/ApachePig discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197787.html

Apache Pig is a data analysis tool built on top of Apache Hadoop.

From 2014-04-16 FESCo meeting:

AGREED: Apache Accumulo, Ambari, and Pig changes approved (+:6, -:0)

Note: suggest coalescing of Hadoop and Hadoop-related changes for relnote/doc purposes

AGREED: Playground Repo should be promoted to a System-Wide Change.
Playground Repo change deferred for a week for more discussion (+:6, -:0)

Self Contained Changes for 2014-04-23 meeting.

• Adopt-Your-Cattle - https://fedoraproject.org/wiki/Changes/Adopt-Your-Cattle discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197752.html

We provide a smooth path so a Cloud Base Image can be turned into Fedora Server.

• Big Data Cloud Image - https://fedoraproject.org/wiki/Changes/Big_Data_Cloud_Image discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197789.html

Fedora Cloud agreed to make a base image plus several tailored to specific purposes. This is one of the tailored ones, produced in collaboration with the Big Data SIG.

• Docker Container Image - https://fedoraproject.org/wiki/Changes/Docker_Container_Image discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197791.html

This is Fedora running inside Docker. Currently, there are non-official images in the docker index, but we'd like them to really come out of release engineering.

• Jenkins - https://fedoraproject.org/wiki/Changes/Jenkins discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197799.html

Jenkins is an open source continuous integration tool written in Java.

• libzhuyin - https://fedoraproject.org/wiki/Changes/libzhuyin discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198056.html

An new intelligent input method for Traditional Chinese (Taiwan) provided by libzhuyin using n-gram to give better conversion than ibus-chewing with libchewing.

• Move to ImageFactory For Cloud Image Creation - https://fedoraproject.org/wiki/Changes/Move_to_ImageFactory_For_Cloud_Image_Creation discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197975.html

Create images using Anaconda in Koji rather than appliance-creator. Allows non-scratch builds with fedmsg integration for upload service, and also could produce official Docker images.

• Remote Journal Logging - https://fedoraproject.org/wiki/Changes/Remote_Journal_Logging discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197980.html

Systemd journal can be configured to forward events to a remote server. Entries are forwarded including full metadata, and are stored in normal journal files, identically to locally generated logs.

• SDDM as the default KDE display manager instead of KDM - https://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197986.html

Retire KDM as the default display manager of the KDE Fedora Spin in favor of
SDDM.

• 64bit ARM emulation on x86 - https://fedoraproject.org/wiki/Changes/Virt_64bit_ARM_on_x86 discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198040.html

Allow running 64bit ARM (AArch64) VMs on x86 hosts using standard the standard qemu and libvirt stack, as well as end user tools like virt-manager and virt-install.

Replying to [comment:18 jreznik]:

• Remote Journal Logging - https://fedoraproject.org/wiki/Changes/Remote_Journal_Logging discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/197980.html

Systemd journal can be configured to forward events to a remote server. Entries are forwarded including full metadata, and are stored in normal journal files, identically to locally generated logs.

I don't consider this to be a self-contained change. If it goes into effect, we (FESCo) are basically stating that this a recommended way for users to gather journald logs in a central location. I (like many others on the mailing list) have serious reservations about this approach, particularly since it appears to have been developed without the input of the journald creators. I think that advertising this Change in the release notes will have significant impact on the way Fedora systems are used and perceived and that this should be considered separately.

I am also casting a -1 vote for this Change, as I will probably be unable to attend the meeting tomorrow.

Consider me +1 to all of the other self-contained Changes in comment [comment:18 18].

agreed all self contained changes proposed this week approved, except remote journal, we will work more with change owners and revisit next week. (+6,0,0)

Remote journal Change owner replied to all the concerns I can recall:

https://lists.fedoraproject.org/pipermail/devel/2014-May/198859.html

Please bring up on the list any additional concerns or questions you may have about it.

Self Contained Changes for 2014-05-07 meeting.

• Cache Logical Volumes - https://fedoraproject.org/wiki/Changes/Cache_Logical_Volumes discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198692.html

LVM can now use fast block devices (e.g. SSDs and PCIe Flash) to improve the performance of larger but slower block devices. These hierarchical or layered logical volumes are called "Cache Logical Volumes" in LVM.

• Docker Cloud Image - https://fedoraproject.org/wiki/Changes/Docker_Cloud_Image discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198691.html

New Fedora product: Fedora Docker Cloud Image - Docker host ready to go.

• MariaDB 10.0 - https://fedoraproject.org/wiki/Changes/MariaDB10 discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198796.html

Update MariaDB to version 10.0

• Shogun - https://fedoraproject.org/wiki/Changes/shogun discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198795.html

SHOGUN is a large Scale Machine Learning Toolbox, being implemented in C++ and offering interfaces to C#, Java, Lua, Octave, Perl, Python, R and Ruby.

Replying to [comment:22 jreznik]:

• Docker Cloud Image - https://fedoraproject.org/wiki/Changes/Docker_Cloud_Image discussed at https://lists.fedoraproject.org/pipermail/devel/2014-April/198691.html
  New Fedora product: Fedora Docker Cloud Image - Docker host ready to go.

Note that we have decided that this will be Atomic based, and will probably be branded in that way ("Fedora Atomic", or "Atomic Fedora". We should update the change page -- can we pull this particular one off the agenda until next week for that update?

AGREED: Self-Contained Changes: Remote Journal Logging, Cache Logical Volumes, MariaDB 10.0, Shogun approved (+6)

Docker Cloud skipped per mattdm’s request.

Self Contained Changes for 2014-05-21 meeting.

• Review Board 2.0 - http://fedoraproject.org/wiki/Changes/ReviewBoard2 discussed at https://lists.fedoraproject.org/pipermail/devel/2014-May/199143.html

Review Board is a powerful tool for managing patch reviews.

• Serf 0.4.5 - http://fedoraproject.org/wiki/Changes/Serf_0.4.5 discussed at https://lists.fedoraproject.org/pipermail/devel/2014-May/199148.html

Serf is a decentralized solution for service discovery and orchestration that is lightweight, highly available, and fault tolerant. This change is to package serf for Fedora users.

• SSSD GPO-Based Access Control - fedoraproject.org/wiki/Changes/SssdGpoBasedAccessControl discussed at https://lists.fedoraproject.org/pipermail/devel/2014-May/199145.html

This change will enhance SSSD, by adding support for centrally managed host-based access control in an Active Directory (AD) environment, using Group Policy Objects (GPOs).

• Web Application Authentication - fedoraproject.org/wiki/Changes/Web_App_Authentication discussed at https://lists.fedoraproject.org/pipermail/devel/2014-May/199144.html

On operating system level, there are numerous authentication and identity lookup mechanisms, some of them using sssd. With new Apache modules and new sssd, some of those mechanisms become more easily consumable by web applications. Various web application environments and frameworks can then consume results of the authentication and information retrieval using environment variables similar to REMOTE_USER.

From FESCo meeting 2014-05-21:

• AGREED: All self contained Changes (Review Board 2.0, Serf 0.4.5, SSSD GPO-Based Access Control, Web Application Authentication) for 2014-05-21 FESCo meeting are approved (+9, -0, 0:0) (t8m, 17:12:06)

From FESCo meeting 2014-07-16:
* AGREED: Atomic_Cloud_Image Self contained change is accepted for Fedora 21 (+7, -0, 0:0)