devel-announce January 2013

devel-announce@lists.fedoraproject.org

9 participants
100 discussions

Proposed F19 Feature: Federated VoIP
by Jaroslav Reznik 30 Jan '13

30 Jan '13

= Features/FederatedVoIP = https://fedoraproject.org/wiki/Features/FederatedVoIP Feature owner(s): Daniel Pocock <daniel(a)pocock.com.au> Make it easier for the deployment of federated SIP and XMPP (Jabber) networks, functioning much like federated SMTP email. == Detailed description == Many VoIP installations still operate on a standalone basis, often with a single SIP proxy or soft PBX trunking all calls to an external provider. Ideally, VoIP should be fully federated, with no central provider other than perhaps the DNS. This feature aims to bring that vision closer to reality, by making it easier to start a SIP proxy in federated mode, using TLS by default for security/identity of external peers and benefiting from ENUM for legacy phone numbers.

1 0

Proposed F19 Feature: Apache OpenOffice
by Jaroslav Reznik 30 Jan '13

30 Jan '13

= Features/ApacheOpenOffice = https://fedoraproject.org/wiki/Features/ApacheOpenOffice Feature owner(s): Andrea Pescetti <pescetti(a)apache.org> Add Apache OpenOffice, the free productivity suite, to Fedora. == Detailed description == Apache OpenOffice (formerly OpenOffice.org) is the the leading free and open- source office software suite. Donated by Oracle to the Apache Software Foundation in 2011, it is now developed and supported by a thriving community; it graduated from the Apache Incubator in October 2012 and it is now an Apache Top-Level Project. Two new versions, 3.4.0 and 3.4.1, were released in the last 8 months and a major update, 4.0, is in the works and scheduled for April 2012. Versions 3.4.0 and 3.4.1 totalled 35 million downloads so far (not counting mirrors). To be clear, this proposal is about merely adding Apache OpenOffice: it doesn't affect existing office suites included in Fedora and it doesn't require that Apache OpenOffice is made the default office suite in Fedora.

1 0

Proposed F19 Feature: Add LVM Thin provisioning support to the yum-fs-snapshot plugin
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= Features/YumFsSnapshotThinpSupport = https://fedoraproject.org/wiki/Features/YumFsSnapshotThinpSupport Feature owner(s): Ondrej Kozina <okozina AT redhat DOT com>, Mike Snitzer <snitzer AT redhat DOT com > For the purposes of system rollback: Provide the ability to create a snapshot of all thinly provisioned LVM2 volumes associated with FS mount points that are relevant to a yum transaction. == Detailed description == Yum's fs-snapshot plugin already has support for LVM2's old snapshots. LVM2's new thinp snapshots offer much more performance and ease administration. It is desirable to have the life-cycle of snapshots that are created by yum's fs- snapshot plugin be managed by the snapper utility. As such it could be that the yum fs-snapshot plugin is extend to provide a wrapper around snapper for the creation of thinp based snapshots.

1 0

Fedora 19 Feature Submission Deadline is TODAY
by Jaroslav Reznik 29 Jan '13

29 Jan '13

Just a follow up to yesterday's reminder - Fedora 19 Feature Submission Deadline is TODAY (2013-01-29 23:59 UTC). Please make sure your Features are in the correct - FeatureReadyForWrangler - category. All Features submitted by this deadline will be processed and announced on devel-announce list but it could take a day/two to process it (+ I may ask you for fix) - also and not to overflood the list with announcements. Thanks for you patience ;-) Features announced for more than one week were already scheduled for tomorrow's FESCo meeting, see FESCo Trac (and you should be on CC). Jaroslav

1 0

Proposed F19 Feature: Erlang/OTP R16
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= Features/Erlang R16 = https://fedoraproject.org/wiki/Features/Erlang_R16 Feature owner(s): Peter Lemenkov <lemenkov(a)gmail.com> Update Erlang to the upstream R16 release. == Detailed description == Erlang is a general-purpose concurrent programming language and runtime system. The sequential subset of Erlang is a functional language, with strict evaluation, single assignment, and dynamic typing. For concurrency it follows the Actor model. It was designed by Ericsson to support distributed, fault- tolerant, soft-real-time, non-stop applications. The first version was developed by Joe Armstrong in 1986. It supports hot swapping, thus code can be changed without stopping a system. Erlang was originally a proprietary language within Ericsson, but was released as open source in 1998. While threads are considered a complicated and error-prone topic in most languages, Erlang provides language-level features for creating and managing processes with the aim of simplifying concurrent programming. Though all concurrency is explicit in Erlang, processes communicate using message passing instead of shared variables, which removes the need for locks. The above text was taken from http://en.wikipedia.org/wiki/Erlang_%28programming_language%29 The status of Erlang and related packages in Fedora/EPEL is shown at Erlang SIG page - https://fedoraproject.org/wiki/SIGs/Erlang#Current_packages

1 0

Proposed F19 Feature: PreUpgrade Assistant
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= Features/PreUpgrade Assistant = https://fedoraproject.org/wiki/Features/PreUpgrade_Assistant Feature owner(s): Nils Philippsen <nils(a)redhat.com>, Phil Knirsch <pknirsch(a)redhat.com> The PreUgrade assistant is a tool to help people upgrade from one release to another and be sure to track important manual configuration changes they performed. == Detailed description == The idea behind the The PreUpgrade assistant came from the notion that even during the rather short release cycles in Fedora occasionally there are changes that are incompatible between releases and which are either hard or nearly impossible to cover during a standard package upgrade. Examples would be major version upgrades of applications or services that change configuration file syntax or on-disk date format changes. The assistant works by analyzing the source system and will generate a report which will offer information and configuration files for typically changed settings and services. It offers a plugin architecture where component or functional area owners can contribute and write their on plugins in python that can generate additional information for the report.

1 0

Proposed F19 Feature: KDE Plasma Workspaces 4.10
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= KDE Plasma Workspaces 4.10 = https://fedoraproject.org/wiki/Features/KDE410 Feature owner(s): rdieter(a)fedoraproject.org, ltinkl(a)redhat.com, than(a)redhat.com, jreznik(a)redhat.com Rebase to KDE Plasma Workspace 4.10. including Plasma Desktop and Netbook workspaces, the KDE Applications and the KDE Platform. == Detailed description == New features overview * KDE Plasma Workspaces, KDE Applications and KDE Platform 4.10 * based on top of Qt 4.8 * New Screen Locker, a new screen locking mechanism based on QtQuick brings more flexibility and security to Plasma Desktop. * Animated Wallpapers * Qt Quick in Plasma Workspaces * Improved Zooming in Okular * New Print Manager plasma applet and settings module * Faster indexing, improvements in the Nepomuk semantic engine allows faster indexing of files. * KWin supports global menu (appmenu-qt should be added to kickstart) * New Apper plasma applet for better updates notifications

1 0

Proposed F19 Feature: Trusted Network Connect (TNC)
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= Features/Trusted Network Connect (TNC) = https://fedoraproject.org/wiki/Features/Trusted_Network_Connect_%28TNC%29 Feature owner(s): Avesh Agarwal <avagarwa(a)redhat.com> This feature provides Trusted Network Connect(TNC) framework that can be used to assess and verify clients' posture (or integrity measurements or configuration) and its compliance to a predefined policy with existing network access control (NAC) solutions. == Detailed description == Traditionally network access control (NAC) has lacked the ability in its decision making to asses endpoint's security posture and its compliance to enterprise policies. This lack of assessment may leave an enterprise's network vulnerable to malicious attacks. Trusted Computing Group (TCG) (and IETF too) has defined an open architecture called Trusted network connect (TNC) (IETF's Network Endpoint Assessment (NEA)) to fill this gap. TNC, as part of its architectural components, includes integrity measurement collectors (IMCs) and TNC client at endpoint and integrity measurement verifiers (IMVs) and TNC server at enterprise network side communicating over NAC solutions such as EAP with 802.1X to evaluate and verify the security posture of the endpoint against the enterprise policies before allowing network access. For this, TCG has released transport (IF-T), session (IF-TNCCS) and messaging (IF-M) standards which are open and interoperable. TNC architecture by virtue of it's IF-M protocol can leverage NIST's SCAP's (OpenSCAP) automated security aspects for measurement collection, verification and remediation. In addition, TCG has defined IF-PTS and PTS protocol specifications to integrate platform trust services (PTS) with TNC for TPM based attestation of integrity measurements. PTS protocol defines messaging payloads to be used over IF-M protocol. This feature includes the aforementioned functionalities and aims to provide an end-to-end network based client assessment, verification and remediation.

1 0

Proposed F19 Feature: OpenShift Origin
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= Features/OpenShift_Origin = https://fedoraproject.org/wiki/Features/OpenShift_Origin Feature owner(s): Troy Dawson <tdawson(a)redhat.com> OpenShift Origin is a cloud application platform as a service (PaaS). It is the open sourced, community supported version of OpenShift. == Detailed description == OpenShift Origin is a cloud application platform as a service (PaaS). It is the open sourced, community supported version of OpenShift OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications. OpenShift Origin takes care of all the infrastructure, middleware, and management and allows the developer to focus on what they do best: designing and coding applications.

1 0

Proposed F19 Feature: Ease Of Use: System Management with OpenLMI
by Jaroslav Reznik 29 Jan '13

29 Jan '13

= Features/OpenLMIEaseOfUse = https://fedoraproject.org/wiki/Features/OpenLMIEaseOfUse Feature owner(s): Tomáš Smetana <tsmetana at redhat.com > Add providers and capabilites to the OpenLMI infrastructure that would ease the remote system management. == Detailed description == The OpenLMI project provides a common infrastructure for the management of Linux systems. The goal is to add the missing parts that would enable remote management of a Fedora system: * Complete the CIM storage API to allow for a better remote storage management * Add a new provider and extend the existing ones to allow for a remote hardware information retrieval (HW inventory) * Add a new provider that would allow for a remote AD/Kerberos realms enrollment * Add a new provider that would allow for a remote Firewall management (open/close a particular port) through firewalld * Improve the software management in OpenLMI to allow for a comprehensive remote package management * Add and improve the remote system monitoring using OpenLMI * Improve the OpenLMI Shell to allow for a quick and easy scriptable remote management * Allow to use OpenLMI under selinux enforcing policy * Possibly add providers to allow management also other system parts: Containers, SELinux, SCAP scans, performance monitoring

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce January 2013