| 95% || [[Features/256_Color_Terminals | 256 Color Terminals]] || Enable terminal programs to use the enhanced color capabilities of modern terminals by default. I.E. increase their color options from the 8 colors at the top of this picture, to the other 256 displayed. || 2012-08-09

+

| 100% || [[Features/256_Color_Terminals | 256 Color Terminals]] || Enable terminal programs to use the enhanced color capabilities of modern terminals by default. I.E. increase their color options from the 8 colors at the top of this picture, to the other 256 displayed. || 2012-10-08

|-

|-

−

| 80% || [[Features/ActiveDirectory | Active Directory]] || Fedora should be able to be used on an Active Directory domain (or other kerberos realms, such as IPA) out of the box. It should be easy to configure domain logins on a Fedora machine, and then it should be intuitive and uneventful to login with those credentials. || 2012-08-13

+

| 100% || [[Features/ActiveDirectory | Active Directory]] || Fedora should be able to be used on an Active Directory domain (or other kerberos realms, such as IPA) out of the box. It should be easy to configure domain logins on a Fedora machine, and then it should be intuitive and uneventful to login with those credentials. || 2012-10-09

|-

|-

−

| 50% || [[Features/AgentFreeManagement | Agent Free Management]] || The goal of this feature is the substitute some of the important functionality of the systems management software that is usually installed on the operating system by a native implementation. This will also put existing standards already in use by Service Processors like IPMI and WSMAN to better use. || 2012-08-02

+

| 100% || [[Features/AgentFreeManagement | Agent Free Management]] || The goal of this feature is the substitute some of the important functionality of the systems management software that is usually installed on the operating system by a native implementation. This will also put existing standards already in use by Service Processors like IPMI and WSMAN to better use. || 2012-09-17

|-

|-

−

| 80% || [[Features/AvahiDefaultOnDesktop | Avahi by Default on the Desktop]] || Fedora should work out of the box discovering MDNS shared printers and other MDNS devices. The system should not publish any private information via MDNS by default, but MDNS should be available for device discovery by default for the Desktop install of Fedora. || 2012-08-06

+

| 100% || [[Features/AvahiDefaultOnDesktop | Avahi by Default on the Desktop]] || Fedora should work out of the box discovering MDNS shared printers and other MDNS devices. The system should not publish any private information via MDNS by default, but MDNS should be available for device discovery by default for the Desktop install of Fedora. || 2012-10-22

|-

|-

−

| 90% || [[Features/CIMManagement | CIM Management]] || WBEM and CIM are two of the DMTF standards for enterprise system management. Fedora already contains implementation of the standard but the existing capabilities are focused more on system monitoring. The standards allow to add methods for system management as well. The goal is to implement new CIM providers and extend the existing ones to enable the basic system management capabilities. The implementation should adhere to the standards to allow for easier interoperability with other CIM/WBEM based applications. The feature is targeting system administrators and experienced users and should lay base ground for future development of enterprise-level management infrastructure for Fedora. || 2012-08-02

| 90% || [[Features/Clojure | Clojure]] || Addition of Clojure tooling packages to Fedora, including the Leinengen build tool and its configuration to use the system Maven repository, as well as Clojure libraries and frameworks, including Korma and Noir. || 2012-08-20

+

| 100% || [[Features/CIMManagement | CIM Management]] || WBEM and CIM are two of the DMTF standards for enterprise system management. Fedora already contains implementation of the standard but the existing capabilities are focused more on system monitoring. The standards allow to add methods for system management as well. The goal is to implement new CIM providers and extend the existing ones to enable the basic system management capabilities. The implementation should adhere to the standards to allow for easier interoperability with other CIM/WBEM based applications. The feature is targeting system administrators and experienced users and should lay base ground for future development of enterprise-level management infrastructure for Fedora. || 2012-10-15

| 100% || [[Features/Clojure | Clojure]] || Addition of Clojure tooling packages to Fedora, including the Leinengen build tool and its configuration to use the system Maven repository, as well as Clojure libraries and frameworks, including Korma and Noir. || 2012-10-16

| 90% || [[Features/gss-proxy | GSS Proxy ]] || The main purpose of this project is to replace rpc.svcgssd(8), the server-side rpcsec_gss daemon. The gss-proxy consists of a standardized RPC protocol, a client and server implementation with other future components. The gss-proxy protocol allows proxying of GSSAPI initiation and authentication. || 2012-06-30

| 100% || [[Features/Typing-Booster | Ibus-Typing-Booster ]] || Ibus-Typing Booster is a predictive input method for the ibus platform. It predicts complete words based on partial input. One can then simply select the desired word from a list of suggestions and improve one's typing speed and spelling. || 2012-08-15

| 100% || [[Features/Typing-Booster | Ibus-Typing-Booster ]] || Ibus-Typing Booster is a predictive input method for the ibus platform. It predicts complete words based on partial input. One can then simply select the desired word from a list of suggestions and improve one's typing speed and spelling. || 2012-08-15

−

|-

−

| 33% || [[Features/InitialExperience | Initial Experience]] || After installing a new Fedora desktop system there are a few essential things to set up before use, preferably in a simple, easy, and safe way; these enhancements will walk the user through many of these first-time setup steps. Initial-setup will replace the user login screen only for the first boot; we also want to offer a 'tour' of the GNOME 3 desktop at the end of the setup tasks, to help new users find their way in GNOME 3. || 2012-07-17

| 80% || [[Features/NewInstallerUI | New Installer UI]] || Enhancing the anaconda installer with a new user interface, improving both the end-user experience as well as ease of implementation of new features, particularly new storage technologies, for developers. || 2012-08-07

| 80% || [[Features/NewInstallerUI | New Installer UI]] || Enhancing the anaconda installer with a new user interface, improving both the end-user experience as well as ease of implementation of new features, particularly new storage technologies, for developers. || 2012-08-07

Line 90:

Line 82:

| 100% || [[Features/OfflineSystemUpdates | Offline Updates using systemd and PackageKit]] || Make updating of system components more reliable by doing it in an minimal, controlled environment. || 2012-07-23

| 100% || [[Features/OfflineSystemUpdates | Offline Updates using systemd and PackageKit]] || Make updating of system components more reliable by doing it in an minimal, controlled environment. || 2012-07-23

|-

|-

−

| 90% || [[Features/OpenShift_Origin | OpenShift Origin]] || OpenShift Origin is a cloud application platform as a service (PaaS). It is the open-sourced, community-supported version of the OpenShift service. || 2012-08-17

+

| 100% || [[Features/OpenStack_Folsom | OpenStack Folsom]] || OpenStack will be upgraded to the next major stable release, called "Folsom". || 2012-10-12

|-

|-

−

| 80% || [[Features/OpenStack_Folsom | OpenStack Folsom]] || OpenStack will be upgraded to the next major stable release, called "Folsom". || 2012-06-15

+

| 100% || [[Features/oVirtEngine_3.1 | oVirt engine 3.1 ]] || The oVirt engine is the management application of the oVirt virtualization platform. Version 3.1 is the latest version, including the GUI and many important new features. || 2012-10-03

−

|-

+

−

| 85% || [[Features/oVirtEngine_3.1 | oVirt engine 3.1 ]] || The oVirt engine is the management application of the oVirt virtualization platform. Version 3.1 is the latest version, including the GUI and many important new features. || 2012-08-09

+

−

|-

+

−

| 60% || [[Features/OwnCloud | ownCloud ]] || A flexible, open source file sync and share solution that can be accessed from a mobile device, a workstation, or a web client. || 2012-08-20

+

|-

|-

| 100% || [[Features/PackagePresets | Package Service Presets ]] || So far, whether a service is enabled or disabled after package installation is encoded in the %post scripts of the RPM, and decided globally for the entire distribution, ignoring the particular needs of spins. With the introduction of "presets" we'd like to remove this policy from the packaging scripts and place them in explicit "preset" files instead which can be different for the various spins, and even for individual systems. || 2012-08-07

| 100% || [[Features/PackagePresets | Package Service Presets ]] || So far, whether a service is enabled or disabled after package installation is encoded in the %post scripts of the RPM, and decided globally for the entire distribution, ignoring the particular needs of spins. With the introduction of "presets" we'd like to remove this policy from the packaging scripts and place them in explicit "preset" files instead which can be different for the various spins, and even for individual systems. || 2012-08-07

| 70% || [[Features/QXLKMSSupport | QXL/Spice KMS Driver ]] || Currently the QXL driver is X.org only, a KMS driver is required to move forward with projects like spice 3D, and also to allow more features to be show in virt environments like plymouth. || 2012-08-13

| 99% || [[Features/Samba4 | Samba 4]] || The Samba Team is working on a final release of Samba 4.0. On Monday, 16th of July 2012, Beta4 of Samba 4.0 has been released. This is important milestone in a more than 8 years of Samba 4 development. This page attempts to explain what will be and will not be available in Fedora. || 2012-07-20

+

| 100% || [[Features/Samba4 | Samba 4]] || The Samba Team is working on a final release of Samba 4.0. On Monday, 16th of July 2012, Beta4 of Samba 4.0 has been released. This is important milestone in a more than 8 years of Samba 4 development. This page attempts to explain what will be and will not be available in Fedora. || 2012-10-10

|-

|-

−

| 80% || [[Features/SecureBoot | Secure Boot]] || "Secure Boot" describes a UEFI feature by which malware is prevented from inserting itself into the boot process before the operating system loads. The UEFI feature is required to be enabled on all machines bearing the Windows 8 Client logo, which will be the overwhelming majority of all desktop and notebook systems. || 2012-08-13

+

| 99% || [[Features/SecureBoot | Secure Boot]] || "Secure Boot" describes a UEFI feature by which malware is prevented from inserting itself into the boot process before the operating system loads. The UEFI feature is required to be enabled on all machines bearing the Windows 8 Client logo, which will be the overwhelming majority of all desktop and notebook systems. || 2012-10-15

|-

|-

−

| 90% || [[Features/Securecontainers | Secure Containers ]] || Create a tool virt-sandbox-server that will allow an administrator to easily create a LXC Container to run the an application server, with libvirt and SELinux locking it down. This tool is part of the virt-sandbox package introduced in Fedora 17. || 2012-08-09

+

| 100% || [[Features/Securecontainers | Secure Containers ]] || Create a tool virt-sandbox-server that will allow an administrator to easily create a LXC Container to run the an application server, with libvirt and SELinux locking it down. This tool is part of the virt-sandbox package introduced in Fedora 17. || 2012-10-15

|-

|-

−

| 80% || [[Features/SELinuxBooleansRename | SELinux Rename Booleans]] || Rename all booleans that currently begin with allow_ to something that is more domain specific. || 2012-08-13

+

| 100% || [[Features/SELinuxBooleansRename | SELinux Rename Booleans]] || Rename all booleans that currently begin with allow_ to something that is more domain specific. || 2012-09-27

|-

|-

−

| 70% || [[Features/SELinuxSystemdAccessControl | SELinux Systemd Access Control ]] || We need systemd to do SELinux access checking whether or not a process is allowed to manage a unit file. || 2012-08-09

+

| 100% || [[Features/SELinuxSystemdAccessControl | SELinux Systemd Access Control ]] || We need systemd to do SELinux access checking whether or not a process is allowed to manage a unit file. || 2012-09-21

|-

|-

| 100% || [[Features/ServerKMSDrivers | Server KMS Drivers]] || Servers generally ship with fairly simple GPU hardware that can provide scanout and a small amount of VRAM. Currently we use X.org drivers to drive these chipsets. However a set of simple KMS drivers could be written along with a single X.org driver to drive this hardware. Bringing the featureset of KMS to these chipsets. || 2012-07-25

| 100% || [[Features/ServerKMSDrivers | Server KMS Drivers]] || Servers generally ship with fairly simple GPU hardware that can provide scanout and a small amount of VRAM. Currently we use X.org drivers to drive these chipsets. However a set of simple KMS drivers could be written along with a single X.org driver to drive this hardware. Bringing the featureset of KMS to these chipsets. || 2012-07-25

| 0% || [[Features/Sugar_0.98 | Sugar 0.98]]|| Provide the latest Sugar Learning Environment (0.98), including an enhanced activity set to provide an stable demo environment for Sugar as well as an environment for developers. || 2012-07-23

+

| 100% || [[Features/Sugar_0.98 | Sugar 0.98]]|| Provide the latest Sugar Learning Environment (0.98), including an enhanced activity set to provide an stable demo environment for Sugar as well as an environment for developers. || 2012-10-25

|-

|-

| 100% || [[Features/Syscall_Filters | Syscall Filters]]|| Syscall filtering is a security mechanism that allows applications to define which syscalls they should be allowed to execute. || 2012-08-15

| 100% || [[Features/Syscall_Filters | Syscall Filters]]|| Syscall filtering is a security mechanism that allows applications to define which syscalls they should be allowed to execute. || 2012-08-15

| 100% || [[Features/Virt_Live_Snapshots | Virt Live Snapshots ]] || Live snapshots allow a user to take a snapshot of a virtual machine while the guest is running, thus preserving the state and data of a VM at a specific point in time. || 2012-08-07

| 100% || [[Features/Virt_Live_Snapshots | Virt Live Snapshots ]] || Live snapshots allow a user to take a snapshot of a virtual machine while the guest is running, thus preserving the state and data of a VM at a specific point in time. || 2012-08-07

−

|-

−

| 20% || [[Features/UsermodeMigration | Usermode Migration]] || Access control of privileged operations for ordinary users should be handled exclusively by a centrally managed authority. Usermode/consolehelper should be phased out and be replaced entirely by PolicyKit. || 2012-04-03

−

|-

−

| 15% || [[Features/VNCServerWithLLVMpipe | VNCServer support for LLVMpipe/Mesa on 64-bit IBM Power Systems ]] || With Fedora 18 transitioning to 3D graphics support in the desktop, work is required to ensure that VNCServer will continue to support Power Systems. || 2012-08-13

|-

|-

| 100% || [[Features/Xfce-4.10 | Xfce 4.10]] || Updates the Fedora Xfce desktop to version 4.10. This release incorporates major changes to the core of the Xfce desktop environment, and includes numerous bugfixes and improvements. || 2012-05-04

| 100% || [[Features/Xfce-4.10 | Xfce 4.10]] || Updates the Fedora Xfce desktop to version 4.10. This release incorporates major changes to the core of the Xfce desktop environment, and includes numerous bugfixes and improvements. || 2012-05-04

Fedora 18 Accepted Features

Enable terminal programs to use the enhanced color capabilities of modern terminals by default. I.E. increase their color options from the 8 colors at the top of this picture, to the other 256 displayed.

Fedora should be able to be used on an Active Directory domain (or other kerberos realms, such as IPA) out of the box. It should be easy to configure domain logins on a Fedora machine, and then it should be intuitive and uneventful to login with those credentials.

The goal of this feature is the substitute some of the important functionality of the systems management software that is usually installed on the operating system by a native implementation. This will also put existing standards already in use by Service Processors like IPMI and WSMAN to better use.

Fedora should work out of the box discovering MDNS shared printers and other MDNS devices. The system should not publish any private information via MDNS by default, but MDNS should be available for device discovery by default for the Desktop install of Fedora.

WBEM and CIM are two of the DMTF standards for enterprise system management. Fedora already contains implementation of the standard but the existing capabilities are focused more on system monitoring. The standards allow to add methods for system management as well. The goal is to implement new CIM providers and extend the existing ones to enable the basic system management capabilities. The implementation should adhere to the standards to allow for easier interoperability with other CIM/WBEM based applications. The feature is targeting system administrators and experienced users and should lay base ground for future development of enterprise-level management infrastructure for Fedora.

Addition of Clojure tooling packages to Fedora, including the Leinengen build tool and its configuration to use the system Maven repository, as well as Clojure libraries and frameworks, including Korma and Noir.

Eucalyptus is a cloud computing software platform for on-premise (private) Infrastructure as a Service clouds. It uses existing infrastructure to create scalable and secure AWS-compatible cloud resources for compute, network and storage.

RFC 5716 introduces the Federated File System (FedFS, for short). FedFS is an extensible standardized mechanism by which system administrators construct a coherent namespace across multiple file servers using file system referrals.

Ibus-Typing Booster is a predictive input method for the ibus platform. It predicts complete words based on partial input. One can then simply select the desired word from a list of suggestions and improve one's typing speed and spelling.

Kerberos 1.10 added a new cache storage type, DIR: which allows Kerberos to maintain TGTs for multiple KDCs simultaneously and auto-select between them when negotiating with Kerberized resources. Fedora should switch to using the DIR: cache format over the older FILE: cache format to support accessing mulitple Kerberos realms.

Enhancing the anaconda installer with a new user interface, improving both the end-user experience as well as ease of implementation of new features, particularly new storage technologies, for developers.

So far, whether a service is enabled or disabled after package installation is encoded in the %post scripts of the RPM, and decided globally for the entire distribution, ignoring the particular needs of spins. With the introduction of "presets" we'd like to remove this policy from the packaging scripts and place them in explicit "preset" files instead which can be different for the various spins, and even for individual systems.

The Samba Team is working on a final release of Samba 4.0. On Monday, 16th of July 2012, Beta4 of Samba 4.0 has been released. This is important milestone in a more than 8 years of Samba 4 development. This page attempts to explain what will be and will not be available in Fedora.

"Secure Boot" describes a UEFI feature by which malware is prevented from inserting itself into the boot process before the operating system loads. The UEFI feature is required to be enabled on all machines bearing the Windows 8 Client logo, which will be the overwhelming majority of all desktop and notebook systems.

Create a tool virt-sandbox-server that will allow an administrator to easily create a LXC Container to run the an application server, with libvirt and SELinux locking it down. This tool is part of the virt-sandbox package introduced in Fedora 17.

Servers generally ship with fairly simple GPU hardware that can provide scanout and a small amount of VRAM. Currently we use X.org drivers to drive these chipsets. However a set of simple KMS drivers could be written along with a single X.org driver to drive this hardware. Bringing the featureset of KMS to these chipsets.

Linux guests don't do S3/S4 properly right now due to missing functionality in the virtio layer to save state before hibernation and restore it after resume. The plan is to extend virtio and individual virtio drivers to handle hibernation, as well as userspace components like libvirt + qemu to enable everything.