I am trying to contribute Fedora about Baculum WebGUI (BugZilla
1203018). This WebGUI uses PHP framework (PRADO framework) that is not
available in Fedora packages.
My first question is: if first should I try to contribute Fedora about
PRADO Framework and then try to contribute Fedora about Baculum? I would
not provide bundled framework to Fedora.
Second my issue is that PHP framework itself contains bundled libraries
from which part is available in Fedora packages (for example:
prototype.js, script.aculo.us, tinymce editor...etc.) and a part that
is not available in Fedora packages.
I can try to contribute Fedora about PRADO Framework but I will need to
solve all dependencies and tune PRADO code to external libraries which
in this case will be using Fedora packages (prototype.js,
Additionally I will need to contribute this part of PRADO dependencies
(3rd party code) that is not in Fedora packages (SafeHtml, FirePHP...
I would avoid situation that at the start for provide Baculum I will
become a maintainer 30 other packages :-)
Last information is that Baculum uses raw framework without 3rd party
libraries. For preparing buildroot files in Spec I just not include 3rd
party code from upstream tar.gz archive. Maybe this information can make
Thank you in advance for advises and any help.
as you know the talk proposal was accepted(https://flock2015.sched.org/
There are some points I should develop:
1) the new structure of fedora-join;
2) the target of fed-join;
3) the new workflow of fed-join;
4) what we need to reach the goal;
1) why "Mary" is "marooned" (wiki for "dummies", how don't get lost
2) what we can do for Mary;
3) let's "rescue" Mary together.
1) a badge assigned for each rescued user;
Those are some of the points I guessed, of course others can get up
while writing the talk, but if you have any suggestion, feel free to
Looking for a new project? Want to work with the Docs team, but don't know
where to start? Interested in the shiny goodness from the upcoming Fedora
23 release? Read on...
---------- Forwarded message ----------
From: "Zachary Oglesby" <zach(a)oglesby.co>
Date: Jul 21, 2015 7:44 AM
Subject: Release Notes, and F23 Change list
To: "docs(a)lists.fedoraproject.org" <docs(a)lists.fedoraproject.org>
> Fedora 23 is just around the corner and it is time to buckle down and
start working on the release notes. If you are interested in working on
this, or you want an easy way to get more badges please take a look at the
[wiki page] and sign up to write a beat for the release notes. If you
have question on what a beat is or how to go about writing it please ask on
the list, or in irc, or read the documentation on [how to write this
> If you have worked on this in the past please visit the page and remove
the asterisk (*) from your name to show that you want to work on that beat
this time around.
> Now your [change log]: (Note: I did not add a synopsis for self
> 1 Fedora 23 Accepted System Wide Changes Proposals
> 1.1 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.
> 1.2 Mono 4
> Update the Mono stack in Fedora from 2.10 to 4.*
> 1.3 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.
> 1.4 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.
> 1.5 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
> 1.6 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.
> 1.7 Glibc locale subpackaging
> This change should make it possible to install or uninstall locales
> 1.8 SELinux policy store migration
> The newest SELinux userspace project release 2015-02-02 includes a
change of the location of the SELinux policy store, which defaults to
> 1.9 Two Week Atomic
> Fedora Atomic Host is an implementation of the Project Atomic pattern
for a specialized operating system for the deployment of containerized
applications. For the past two Fedora releases, we've included an Atomic
Host cloud image as a non-blocking deliverable. However, upstream Atomic is
moving very fast — by the end of the alpha, beta, final stabilization cycle
Fedora uses, the released artifact is basically obsolete. Additionally, the
Project Atomic team at Red Hat would like to do their ongoing development
work in the Fedora upstream, and the six-month release cycle does not lend
itself to that.
> 1.10 Unicode 8.0 support
> Unicode 8.0 got release on 17th June 2015. It includes 41 new emoji
characters (including five modifiers for diversity), 5,771 new ideographs
for Chinese, Japanese, and Korean, the new Georgian lari currency symbol,
and 86 lowercase Cherokee syllables. It also adds letters to existing
scripts to support Arwi (the Tamil language written in the Arabic script),
the Ik language in Uganda, Kulango in the Côte d’Ivoire, and other
languages of Africa. In total, this version adds 7,716 new characters and
six new scripts.
> 1.11 IBus 1.5.11
> IBus 1.5.11 will have the features of XKB prefix language icons on the
panel in KDE 5 and support $HOME/.XCompose file in all desktops.
> 1.12 Node.js 0.12
> Fedora 23 will be updated to Node.js 0.12, the latest release of the
scalable network applications.
> 1.13 jQuery
things like HTML document traversal and manipulation, event handling,
animation, and Ajax much simpler with an easy-to-use API that works across
a multitude of browsers. With a combination of versatility and
extensibility, jQuery has changed the way that millions of people write
> 1.14 Layered Docker Image Build Service
> Fedora currently ships a Docker base image, but Docker supports a
layering concept. There are some applications like Cockpit which we would
like to ship as layered applications.
> 2 Fedora 23 Accepted Self Contained Changes Proposals
> 2.1 Cinnamon Spin
> 2.2 System Firmware Updates
> 2.3 Cockpit GUI for Domain Controller Role
> 2.4 Containerized Server Roles
> 2.5 Frappe Framework
> 2.6 Cloud MOTD
> 2.7 Cloud Systemd Networkd
> 2.8 Local Test Cloud
> 2.9 RPM MPI Requires Provides
> 2.10 Sugar 0.106
> 2.11 ibus-libzhuyin
> 2.12 npm 2
> 2.13 Astronomy Spin
> 2.14 io.js Technology Preview
> : https://fedoraproject.org/wiki/Category:Documentation_beats
> : https://fedoraproject.org/wiki/Docs_Project_workflow_-_beat_writing
> : https://fedoraproject.org/wiki/Releases/23/ChangeSet
> docs mailing list
> To unsubscribe: