Re: Proposed F19 Feature: Replace MySQL with MariaDB
by Norvald H. Ryeng
----- misc(a)zarb.org wrote:
> So let's take a very narrow and specific example, and see what could you
> do after the fact to make packagers life easier.
>
> While working with Remi on a package review[1], I was quite surprised to
> see that one Oracle engineer created a internal bug for the inclusion of
> a patch from a external community member, to be added to a free software
> project.
Here's the bug: http://bugs.mysql.com/bug.php?id=68182
We'll try to do better in the future.
Have a nice weekend!
Regards,
Norvald H. Ryeng
11 years, 2 months
Proposed F19 Feature: More Mobile Broadband
by Jaroslav Reznik
= Features/MoreMobileBroadband =
https://fedoraproject.org/wiki/Features/MoreMobileBroadband
Feature owner(s): Dan Williams <dcbw at redhat dot com>
New mobile broadband devices supporting multiple technologies (eg,
CDMA/EVDO/LTE and/or GSM/UMTS/LTE) and using new proprietary protocols are
becoming common in the marketplace, and are not well supported by ModemManager
0.6 and earlier. We developed ModemManager 0.7/0.8 with a new API specifically
to address this issue and to be more compatible with future mobile broadband
devices.
== Detailed description ==
Multi-mode Qualcomm-based devices have on the market since 2009 and support
multiple WWAN technologies, often at the same time or with a runtime firmware
change. CDMA-based carriers migrating to LTE (like Verizon, Sprint, China
Telecom, KDDI, etc) require these multi-mode devices to ensure that coverage
is not interrupted when handoff between CDMA/EVDO and LTE occurs.
ModemManager 0.6's D-Bus API simply could not be extended to handle these
cases, and due to this, the opportunity was taken to rewrite the API to ensure
future functionality could be more easily supported in the D-Bus API.
Additionally, most newer Qualcomm chipsets (which the majority of phones and
data cards contain) use the proprietary QMI protocol for most operations
instead of their limited AT command port. We have developed the libqmi library
to support these devices, and ModemManager 0.7 and later use libqmi to provide
fully-featured support for these Qualcomm devices.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: Fedora Upgrade - using yum
by Jaroslav Reznik
= Features/FedoraUpgrade =
https://fedoraproject.org/wiki/Features/FedoraUpgrade
Feature owner(s): Miroslav Suchý <msuchy(a)redhat.com>
Upgrade Fedora to next version using yum upgrade.
== Detailed description ==
In past (until Fedora 17) we could upgrade Fedora using Anaconda Upgrade and
PreUpgrade.
Now (in Fedora 18) we have only FedUp and previous methods are obsoleted.
I propose to have FedUp and FedoraUpgrade in Fedora 19.
FedUp is in fact yum-upgrade as well, but in dracut environment (aka off-line
upgrade). Some devels say that offline upgrade is only way. But on-line upgrade
is possible. E.g in Debian world it is even prefered method. In Fedora exist
upgrade using yum as unofficial method for long time.
A lot of people are using upgrade using yum for long time and the "problem
ratio" was at least on pair with Anaconda upgrade. In fact most problems comes
from improper packaging. E.g. maintainer forgot to obsolete, so during upgrade
user get file conflict. Once these problems are reported and fixed the upgrade is
without problem.
And since FedUp is just different approach to yum-upgrade, FedUp will benefit
from fixes on FedoraUpgrade (and vice versa).
I propose to support both FedUp and FedoraUpgrade and give user option.
If this method will be tested by FedoraQA, then I believe this upgrade method
can be safely recommended to user.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: Apache OpenOffice
by Jaroslav Reznik
= 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.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: Virtio RNG
by Jaroslav Reznik
= Features/Virtio RNG =
https://fedoraproject.org/wiki/Features/Virtio_RNG
Feature owner(s): Cole Robinson <crobinso(a)redhat.com>, Amit Shah
<amit.shah(a)redhat.com>
Provide a paravirtual random number generator to virtual machines, to prevent
entropy starvation in guests.
== Detailed description ==
The linux kernel collects entropy from various non-deterministic hardware
events, like mouse and keyboard input, and network traffic. This entropy is then
exposed through /dev/random, commonly used by cryptographic applications that
need true randomness to maintain security. However if more entropy is being
consumed than is being produced, we have entropy starvation: reading from
/dev/random will block, which can cause a denial of service. A common example
here is use of /dev/random by SSL in various services.
VirtIO RNG (random number generator) is a paravirtualized device that is
exposed as a hardware RNG device to the guest. Virtio RNG just appears as a
regular hardware RNG to the guest, which the kernel reads from to fill its
entropy pool. This effectively allows a host to inject entropy into a guest via
several means: The default mode uses the host's /dev/random, but a physical HW
RNG device or EGD (Entropy Gathering Daemon) source can also be used.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: Trusted Network Connect (TNC)
by Jaroslav Reznik
= 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.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: QXL/Spice KMS Driver
by Jaroslav Reznik
= Features/QXLKMSSupport =
https://fedoraproject.org/wiki/Features/QXLKMSSupport
Feature owner(s): Alon Levy <alevy(a)redhat.com>
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.
== Detailed description ==
The current spice GPU driver for Linux guests is an X.org only driver. A
kernel modesetting driver needs to be developed along with a new X.org driver
that runs on top of it. Additionally the kernel driver will allow it to work
with the modesetting DDX driver. The new ioctl interface the driver will
expose will allow updating the qxl DDX driver to work on it. The new driver
needs to support all revisions of the qxl device.
Btw. Feature has been already proposed as Fedora 18 feature but was postponed
for Fedora 19.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: DualstackNetworking - proper dual stack IPv4 and IPv6 networking
by Jaroslav Reznik
As decided by FESCo on 2012-12-05 meeting, all proposed Features are required
to pass through the community review by announcing them on devel-announce list.
FESCo votes on new features no sooner than a week from the announcement.
= Features/DualstackNetworking =
https://fedoraproject.org/wiki/Features/DualstackNetworking
* Detailed description
Fedora supports dualstack global networking. That means the computer with
Fedora is connected to internet using both IPv4 and IPv6 protocols. But many
important system services and applications either don't do IPv6, do it
incorrectly, or don't cope with various network conditions.
Unfortunately, while trying to improve IPv6 support, some IPv4 use cases became
broken as well. That's why the goal of this feature is not only to support IPv4,
but to support all possible real-world cases.
Dualstack-ready software must cope with all possible scenarios including
IPv4-only connectivity, IPv6-only connectivity and dual connectivity.
The software must also cope with node-local (aka localhost) networking, which
as been used by software for decades.
Though it would be nice to have all applications in Fedora fixed to work in
any of the scenarios, it is not feasible to test that. Therefore this feature
is about major software used in servers, desktops and laptops. The list of such
applications will be completed over the time.
Bugs related to dualstack networking should be added to the following tracker
bug:
http://bugzilla.redhat.com/show_bug.cgi?id=883152
Also see: https://bugzilla.redhat.com/show_bug.cgi?id=ipv6blocker
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: firewalld Lockdown
by Jaroslav Reznik
= Features/FirewalldLockdown =
https://fedoraproject.org/wiki/Features/FirewalldLockdown
Feature owner(s): Thomas Woerner <twoerner(a)redhat.com>
This feature adds a simple configuration setting for firewalld to be able to
lock down configuration changes from local applications.
== Detailed description ==
Local applications are able to change the firewall configuration. With this
feature the administator can lock the firewall configuration and these
applications are not able to modify the firewall anymore.
The lockdown feature is the first part of user and application policies for
firewalld and will be disabled by default.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
Proposed F19 Feature: libkkc - a new Japanese Kana Kanji input library
by Jaroslav Reznik
= Features/libkkc =
https://fedoraproject.org/wiki/Features/libkkc
Feature owner(s): Daiki Ueno <ueno at gnu.org>
libkkc, a new Japanese Kana Kanji input library, will be available in Fedora
19, along with an IBus input method engine which uses libkkc as backend (ibus-
kkc).
== Detailed description ==
There are currently two options for typical users to input Japanese sentences:
ibus-anthy or ibus-mozc. However, both have issues:
* ibus-anthy
- Anthy, the backend library, has been dead upstream for years.
- The accuracy is not good because of bugs in the core algorithm of Anthy.
* ibus-mozc
- Contributions to the input method are limited to Google employees.
- There are no library interface. That means it cannot easily be used by other
input method frameworks than IBus, such as Fcitx and uim.
libkkc and ibus-kkc will be a better replacement of those.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
11 years, 2 months
