F22 Self Contained Change: Domain Controller Set Up Through Cockpit

2015-01-20 Thread Jaroslav Reznik
= Proposed Self Contained Change: Domain Controller Set Up Through Cockpit =
https://fedoraproject.org/wiki/Changes/CockpitDomainController

Change owner(s): Stephen Gallagher sgall...@redhat.com 

With Fedora 21, the rolekit project now provides a public D-BUS interface for 
creating a Domain Controller based on the FreeIPA project. This Change will 
track adding this capability to the Cockpit management console of Fedora 
Server. 

== Detailed Description ==
Providing users with a simple graphical user interface to set up a FreeIPA 
Domain Controller will provide a fast way to bootstrap an enterprise-grade 
Linux environment. Once the Domain Controller is made available, it becomes 
easy to manage single-sign-on between systems (and Cockpit instances), control 
user authentication and authorization centrally and manage DNS entries (among 
other things). 

== Scope ==
* Proposal owners: The Cockpit user experience needs to be written and added 
to that upstream project. It needs to be connected to the local rolekit 
daemon.

* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

F22 System Wide Change: Glibc Unicode 7.0

2015-01-20 Thread Jaroslav Reznik
= Proposed System Wide Change: Glibc Unicode 7.0 =
https://fedoraproject.org/wiki/Changes/Glibc_Unicode_7

Change owner(s):  Mike Fabian mfabian At redhat DOT com, Pravin Satpute 
pravins At fedoraproject DOT org, Siddhesh Poyarekarspoyarek AT redhat DOT 
com

We are updating Glibc Unicode data from Unicode 5.1 to Unicode 7.0 version. It 
took long time since there was not much documentation on how to update Unicode 
data and also there was chance of loosing backward compatibility. Most of the 
issues are resolved now and patches are ready for inclusion. This update adds 
around 8000 number of character support in Glibc and also correcting the 
Unicode data of many characters as per latest Unicode standard. 

== Detailed Description ==
In this update we are planning to update Glibc's the Unicode locale data - 
character map and LC_CTYPE information to Unicode 7.0 version. This data is 
used almost in all locales and going to affect all applications using these 
locales. It is system wide change since it impacting glibc and application 
dependent on it. Glibc provides two files for Unicode data, UTF-8 and i18n. 
UTF-8 file provides information about CHARMAP and WIDTH for Unicode characters. 
i18n file provides CTYPE (uppercase, lowercase, punct etc.) information for all 
Unicode characters. It has been long time this is not updated due to 
incomplete documentation and also possible chances of loosing backward 
compatibility. Work has been started on this 5-6 months back and now most of 
the issues are resolved.

Respective bugs in upstream for more information.

* Update locale data to Unicode 7.0.0 [1]
* Update UTF-8 charmap and width to Unicode 7.0.0 [2]

Github repo for scripts. [3]

== Scope ==
* Proposal owners:
1. Writing scripts for generating UTF-8 and i18n files from Unicode character 
database.
2. Preparing patch for UTF-8 and i18n files.
3. Preparing backward compatibility report.
4. Applying patches to Fedora.
5. Testing whether does it breaks anything around.

* Other developers: This change impacting glibc and all applications that 
using locales. Other Developers do not need to do any changes from there end 
but they need to watch how there application behave with improved localedata. 
We need proper testing to see it does not break any application.

* Release engineering: No work required from Release engineering.

* Policies and guidelines: No, this change does not required any updates to 
Policies or packaging guideline updates.

== Contingency Plan ==
* Contingency mechanism: Will drop patches from Glibc build.
* Contingency deadline: Before F22 Beta release eg. Beta freeze.
* Blocks release? No
* Blocks product? product No 

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=14094
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=17588
[3] https://github.com/pravins/lohit
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

F22 Self Contained Change: Gradle 2.x

2015-01-20 Thread Jaroslav Reznik
= Proposed Self Contained Change: Gradle 2.x =
https://fedoraproject.org/wiki/Changes/Gradle

Change owner(s): Mikolaj Izdebski mizde...@redhat.com

This change aims at making latest version of Gradle available in Fedora and 
making it possible to easily build Fedora packages using Gradle. 

== Detailed Description ==
Gradle [1] is a popular Java build automation tool, which can automate 
building, testing, publishing, deployment and more of software packages or 
other types of projects such as generated static websites, generated 
documentation or indeed anything else.

This change brings latest upstream version of Gradle to Fedora, which enables 
Fedora users to use Gradle to work with software projects.

This change also implements integration with software used for Java packaging 
in Fedora (XMvn and Javapackages), which makes it possible to use standard 
Fedora pagkaging techniques to build RPM packages with Gradle with all 
features, such as automatic artifact installation or auto-requires/provides. 

== Scope ==
* Proposal owners:
** Package latest Gradle 2.x
** Implement local Gradle resolver so that RPM packages can be built with 
Gradle
** Update Java Packaging HOWTO to include information about Gradle packaging

* Other developers:
** Maintainers of packages not built with Gradle and which upstreams are using 
Gradle as build system can optionally update their packages to be built with 
Gradle, but that's not absolutely required as existing ways of building Java 
packages will continue to work.

* Release engineering: N/A

* Policies and guidelines: N/A

[1] http://gradle.org/
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

F22 System Wide Change: Enable Polyinstantiated /tmp and /var/tmp directories by default

2015-01-20 Thread Jaroslav Reznik
= Proposed System Wide Change: Enable Polyinstantiated /tmp and /var/tmp 
directories by default =
https://fedoraproject.org/wiki/Changes/Polyinstantiated_tmp_by_Default

Change owner(s): Huzaifa Sidhpurwala huzai...@redhat.com

Polyinstantiation of temperary directories is a pro-active security measure, 
which reduced chances of attacks caused due to the /tmp and /var/tmp 
directories being world-writable. These include flaws caused by predictive 
temp. file names, race conditions due to symbolic links etc. 

== Detailed Description ==
The basic idea is to provide better security to Fedora installs. Though 
Polyinstantiated /tmp has worked since Fedora 19, its not a single step 
process to configure it. Secondly people don't really understand its benefits. 
Because of this having it on by default makes more sense. It is completely 
transparent to the user, they wont even realize that it has been enabled.

The Red Hat Product Security Team assigns CWE ids to severe flaws (CVSSv2  7). 
Here is a list of severe flaws caused by insecure tmp files [1].

== Scope ==
* Proposal owners: No work required to be done by proposal owner.

* Other developers:
** Add /tmp-inst and /var/tmp/tmp-inst to filesystem. (packagename: filesystem)
** Enable namespaces in /etc/security/namespace.conf (packagename: PAM)
** Enable proper selinux context and polyinstantiation_enabled boolean to be 
set (packagename: selinux-policy-targeted or selinux-policy)

* Release engineering: N/A
* Policies and guidelines: N/A

== Contingency Plan ==
* Contingency mechanism: Poly tmp can be rolled back quite easily, by using 
the previous versions of packages which provides the old directory structures 
and old versions of the configuration files (poly tmp is just configuration and 
a 
few new directories). In releases earlier gnome-shell had issues with poly 
tmp, which now seems to be resolved. In any case, by Beta deadline if any 
blockers exists, we can easily remove this feature, by tagging previous 
versions of the affected packages, before the final spin.

* Contingency deadline: Beta freeze
* Blocks release? No 

[1] http://red.ht/1EkZ1gT
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

F22 Self Contained Change: Minglish - New input method for Marathi Language

2015-01-20 Thread Jaroslav Reznik
= Proposed Self Contained Change: Minglish - New input method for Marathi 
Language =
https://fedoraproject.org/wiki/Changes/minglish

Change owner(s): anish apa...@redhat.com

New input method for Marathi language users. 

== Detailed Description ==
Minglish input method is to type Marathi using Latin alpha-bates.However there 
are existing mim layouts are available though each layout has few problems. 
e.g to type word anish in Marathi using phonetic input method one has to 
type sequence as FniS while with itrans input method one has to type 
anisha. In given example user often expects अनिश to be appear with 
keystrokes anish. In India, people who have familiar with English language 
tend to type Marathi letters upon English letter pronunciation, that is why we 
have new term http://en.wikipedia.org/wiki/Hinglish. 

== Scope ==
* Proposal owner: Initial plan is to send this patch to upstream and otherwise 
patch it into Fedora 

* Other developers: N/A (not a System Wide Change) 
* Release engineering: N/A (not a System Wide Change) 
* Policies and guidelines: N/A (not a System Wide Change) 
___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

F22 System Wide Change: Plasma 5

2015-01-20 Thread Jaroslav Reznik
= Proposed System Wide Change: Plasma 5 =
https://fedoraproject.org/wiki/Changes/Plasma_5

Change owner(s): KDE SIG  Daniel Vrátil dvra...@redhat.com, Lukáš Tinkl 
lti...@redhat.com, Jan Grulich jgrul...@redhat.com, Rex Dieter 
rdie...@fedoraproject.org, Than Ngo t...@redhat.com, Kevin Kofler 
ke...@tigcc.ticalc.org

Plasma 5 is successor to KDE Plasma 4 created by the KDE Community. It is 
based on Qt 5 and KDE Frameworks 5 and brings many changes and improvements 
over previous versions, including new look  feel as well as important changes 
under the hood. 

== Detailed Description ==
Plasma 5 is a new major version of KDE's workspaces. It has a new theme called 
Breeze, which has cleaner visuals and better readability, improves certain 
work-flows and provides overall more consistent and polished interface.

Changes under the hood include switch to Qt 5 and KDE Frameworks 5 and 
migration to fully hardware-accelerated graphics stack based on OpenGL(ES).

Note that Plasma 5 only includes the actual shell, decorations, icons and a 
few applications coupled with workspace (e.g. KWin, System Settings, 
KSysGuard). It does not include regular applications like Dolphin, Okular, 
Konqueror, etc. which are part of KDE Applications product and released 
independently of Plasma 5.

Plasma 5 gets a new feature release every three months, and each feature 
release has monthly bugfix releases. Plasma 5.2 is scheduled to be released on 
January 27. KDE SIG intends to ship Plasma 5.2.2 or Plasma 5.3, depending on 
the final schedules. 

== Scope ==
* Proposal owners:
** Submit, review and import new packages for Plasma 5 to rawhide/F22
** Modify existing KDE 4 packages to ensure smooth upgrade path to Plasma 5
** Retire KDE 4 packages not compatible with Plasma 5, or available in Plasma 
5 under different names/components

* Other developers:
Optionally, maintainers of 3rd party KDE Workspace 4 packages such as Plasma 
applets or KCMs may want to consult upstream regarding Qt 5/Frameworks 
versions of their packages, and eventually update them to Frameworks version, 
so that they are available in Plasma 5.

* Release engineering: 
No, this change requires no coordination with rel-eng.

* Policies and guidelines:
No, this change requires no update to packaging guidelines or policies.

== Contingency Plan ==
* Contingency mechanism: Rolling back to KDE 4 and shipping KDE Workspace 
4.11.X. As rawhide would already have packages with version 5.x.y, we would 
have to increase the epoch number of all affected KDE 4 packages, and making 
them Obsolete their Plasma 5 equivalents (since some Plasma 5 packages have 
been renamed or split from larger KDE 4 packages)
* Contingency deadline: Before F22 beta freeze
* Blocks release? No
* Blocks product? No 

___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

openSUSE Beer

2015-01-20 Thread Douglas DeMaio
Hi all. openSUSE will have it's conference between May 1-4 in The  
Hague, Netherlands. If you want to participate, do some cross  
pollinating and hack with us, we would love to have you attend -  
http://bit.ly/1yeBGg0 Cya at FOSDEM and come enjoy one of our openSUSE  
beers while you're there.


See some of you at SCALE

Cheers
Doug

___
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce