The proposed set of changes are a breath of fresh air in the race to keep up with changing technology.  But it would be even better if some of the changes that are proposed originate from the end-users, the desktop users. 

Fedora is mainly a desktop / workstation distribution. If one wanted it to use it to host a database, or a website, a support duration of more than 1 release is required.  If you want Fedora to  be a more inclusive distribution Fedora development has to include a wish-list from end-users.  Disappointingly there is at this time, no easy facility to collect end-user requests or pains. Bugzilla postings are ignored..

Many many years ago, IBM with their large mainframe systems was in a similar predicament. IBM was having a disconnect with it's users and were not getting the great press they expected.
IBM did one thing significant that extended their mainframe business by 4 decades.  IBM developed SHARE, an exchange meet-up with user groups. At share, there was a two way exchange between developers and end-users. End users presented ideas, and from subsequent polling of end-users for the importance of these ideas, many new features were incorporated into later MVS and OS390 releases..

We need this with Fedora. Times and budgets are very restricted. The majority of Fedora users are either college or retirees. Travel costs are a barrier. But there are many other ways to obtain end-user feedback. One of the best ways is via Linux forums, a Fedora wiki that is easy to use, Facebook, twitter, to name two.

Fedora needs to be inclusive, to poll users for their ideas or change requests. Polling would provide a list of features or enhancements "end-users" would like to have. 

Documentation, that is not due to a "global change of two digits such as converting Fedora 19 documents" where 19 is changed to a 20, then a 20 to 21 and 21 to 22.
Restore nautilus to Fedora21 level of functionality.. 
Put Fedora documentation onto the wiki so that all users may contribute to corrections and additions..
Let at least 10% of Fedora improvements originate with end-users.

I noted that eleven changes were tentatively accepted.  It would be nice for the Fedora 24 release that one or two additional should be added that originates from end-users.  Is that asking a lot?.
    .  . 
 
Regards

 Leslie
Mr. Leslie Satenstein
Montréal Québec, Canada



From: Pete Travis <me@petetravis.com>
To: For participants of the Documentation Project <docs@lists.fedoraproject.org>
Cc: fedora-join@lists.fedoraproject.org
Sent: Monday, June 29, 2015 11:18 AM
Subject: F23 Accepted Changes

Fedora developers are busy preparing for the Fedora 23 Release.  At this point in the release cycle, major changes are planned using a scheme called a "Change".  Changes are either "Self-Contained", where the impact is limited to the proposed packages and coordination with other developers or Fedora teams is minimal, or "System Wide", which affects a number of interrelated packages and requires coordination from other teams such as QA or release engineering.

For both types, the Fedora Docs team will follow the development and implementation of each Change and summarize it for the Release Notes.  Volunteer writers 'own' each change by taking the Docs Contact designation in the Change tracking bug, and coordinating documentation with the Change owners.

Writing these up is a relatively straightforward, well defined task that's ideally suited for new Docs contributors.  The proposals are discussed at length on the devel@lists.fedoraproject.org mailing list and in FESCo meetings.  Some topics might be unfamiliar to you, but don't let that be a roadblock - the writing is targeting uninitiated readers, so your perspective is in a good place.

Without further editorializing, I present the list of approved Changes so far.  Please take the opportunity to get started early!

Fedora 23 Accepted System Wide Changes Proposals

These changes have been accepted by the Fedora Engineering Steering Committee for the Fedora 23 Release as System Wide Changes.

Harden All Packages

Hardening is the process of securing a system/application by reducing its unnecessary functions, or restricting access. In Fedora 22 and before, it was up to the package maintainer to add %global _hardened_build 1 to their spec file to ensure their program was hardened. Beginning with Fedora 23 this will now become the defaults for all packages. You can compare the security by running the following as root:

Owners

  • Owner: Till Maas | Moez Roy | Florian Weimer
  • Release notes owner:

Tracking

  • Last updated: 2015-02-12
  • Tracking bug: #1215939
  • Original tracking bug: #1199775
  • Status: Change accepted

Mono 4

Update the Mono stack in Fedora from 2.10 to 4.*

Owners

  • Owner: Claudio Rodrigo Pereyra Diaz
  • Release notes owner:

Tracking

  • Last updated: April 29, 2015
  • Tracking bug: #1221559
  • Status: Change accepted

Disable SSL3 and RC4 by default

This change will disable by default the SSL 3.0 protocol and the RC4 cipher in components which use the system wide crypto policy. That is, gnutls and openssl libraries, and all the applications based on them.

Owners

  • Owner: Nikos Mavrogiannopoulos
  • Release notes owner:

Tracking

  • Last updated: 2015-04-28
  • Tracking bug: #1220679
  • Status: Change accepted

Perl 5.22

A new perl 5.22 version brings a lot of changes done over a year of development. Perl 5.22 should be released 5/20/2015. See 5.21.11 perldelta for more details about preparing release.

Owners

  • Owner: Petr Písař
  • Release notes owner:

Tracking

  • Last updated: 2015-04-28
  • Tracking bug: #1220680
  • Status: Change accepted

Default Local DNS Resolver

To install a local DNS resolver trusted for the DNSSEC validation running on 127.0.0.1:53. This must be the only name server entry in /etc/resolv.conf.

Owners

  • Owner: P J P | Pavel Šimerda | Tomas Hozza | Petr Špaček
  • Release notes owner:

Tracking

  • Last updated: 2015-05-28
  • Tracking bug: #1182488
  • Status: Change accepted

Fedora 23 Boost 1.59 Uplift

This change brings Boost 1.58.0 or later to Fedora 23. We generally aim to ship 1.59.0, as that seems likely to make it (hence the Change name), but 1.58.0 is out and available now.

Owners

  • Owner: Jon Wakely
  • Release notes owner:

Tracking

  • Last updated: 2015-06-07
  • Tracking bug: #1229030
  • Status: Change accepted

Fedora 23 Accepted Self Contained Changes Proposals

These changes have been accepted by the Fedora Engineering Steering Committee for the Fedora 23 Release as Self Contained Changes.

Cinnamon Spin

A Fedora Spin using the Cinnamon desktop environment.
  • Owner: Dan Book
  • Last updated: 2015-05-06
  • Completed: no

System Firmware Updates

This change is to add the ability to perform firmware updates on UEFI machines.
  • Owner: Richard Hughes
  • Last updated: 2015-06-03
  • Completed: no

Cockpit GUI for Domain Controller Role

Provide a graphical mechanism for deploying a FreeIPA Domain Controller on Fedora Server through the Cockpit administrative console.
  • Owner: Stephen Gallagher, Stef Walter
  • Last updated: 2015-06-18
  • Completed: no

Containerized Server Roles

Enhance rolekit to be able to deploy Server Roles using the Nulecule Container Specification.
  • Owner: Stephen Gallagher
  • Last updated: 2015-06-18
  • Completed: no

Frappe Framework

A full-stack web framework based on Python and Javascript to help you build powerful business apps and nifty extensions.
  • Owner: Eduardo Mayorga , William Moreno
  • Last updated: 2015-06-18
  • Completed: no

-- Pete




--
docs mailing list
docs@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs