From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 9: Line 9:
<references/>
<references/>


=== Fedora 12 KDE Spin Not KDE3-less after all ===
=== New Soprano Backends coming to Fedora KDE ===
Last week Rex Dieter blogged<ref>http://rdieter.livejournal.com/15770.html</ref> about the versions of KOffice and K3b being included in the Fedora 12 KDE live spin. "The reality is that the kde4 ports of both k3b and koffice aren't quite ready, and not recommended for use by either upstream," says Dieter, so the versions shipping with Fedora 11 are going to be KOffice 1.6 and k3b 1.0.
[[MaryEllenFoster]] has been working on packaging the Java based Sesame2 backend for Nepomuk to replace the Redland backend. Unfortunately, Sesame2 is dependent on many other Java packages which must first be packaged for inclusion in Fedora. There are many packages that still need to be packaged for this backend to make it into Fedora<ref>https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame</ref>.


Unofficial builds of KDE4's Koffice and k3b will continue to be built in the unofficial kde-redhat/unstable repos<ref>http://kde-redhat.sourceforge.net/</ref>
After Sebastian Trueg announced<ref>http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/</ref> on his blog about getting Soprano and Virtuoso to work together, [[Rex Dieter|User:Rdieter]] began work on packaging the virtuoso backend as virtuoso-opensource. The Soprano plugins will not be stable until the release of KDE4.4 however, Dieter has packaged snapshots with working virtuoso support in the kde-redhat unstable repository<ref>http://kde-redhat.sf.net/</ref>


<references/>
<references />


=== KDE-SIG steering committee formed ===
=== gtk-qt-engine retired, replaced with kcm-gtk ===
At Tuesday's KDE-SIG IRC meeting<ref>https://www.fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-09-29</ref> an official steering committee was formed so that the SIG has somewhere "to take contentious decisions [and] so we know who exactly should be voting in such cases," says [[User:Kkofler|Kevin Kofler]]. The KDE-SIG steering group is formed of seven members,  [[RexDieter|Rex Dieter]], [[User:Than|Than Ngo]], [[User:Ltinkl|Lukáš Tinkl]], [[User:Kkofler|Kevin Kofler]], [[StevenParrish|Steven Parrish]], [[JaroslavReznik|Jaroslav Řezník]] and [[User:Svahl|Sebastian Vahl]]. Rex Dieter will summarize the exact rules for voting and management of the Steering Committee at next week's meeting.
[[Rex Dieter|User:Rdieter]] has decided to orphan the gtk-qt-engine package in favor of replacing it with the kcm-gtk package. The packages are for all intents and purposes identical except kcm-gtk doesn't ship the Qt style for gtk
 
<references/>
 
=== Amarok 2.2 released ===
This week marked the release of Amarok 2.2 "Sunjammer." [[RexDieter|Rex Dieter]] has been faithfully providing the Amarok builds from the first 2.2 beta to this release, and the final 2.2 release is currently in the updates-testing repository. This release marks the first official release that has many features that Amarok users have been missing since the 1.4 series, including the ability to sort the playlist and rearrange the application's layout to your preferences. Amarok 2.2 will be the first release series that will "focus on improving what is there rather than adding major new features," says Amarok developer Lydia Pintscher.<ref>http://amarok.kde.org/en/releases/2.2</ref>
 
<references/>

Revision as of 16:40, 2 November 2009

KDE

This section covers the news surrounding the Fedora KDE Special Interests Group[1].

Contributing Writer: Ryan Rix

New Soprano Backends coming to Fedora KDE

MaryEllenFoster has been working on packaging the Java based Sesame2 backend for Nepomuk to replace the Redland backend. Unfortunately, Sesame2 is dependent on many other Java packages which must first be packaged for inclusion in Fedora. There are many packages that still need to be packaged for this backend to make it into Fedora[1].

After Sebastian Trueg announced[2] on his blog about getting Soprano and Virtuoso to work together, User:Rdieter began work on packaging the virtuoso backend as virtuoso-opensource. The Soprano plugins will not be stable until the release of KDE4.4 however, Dieter has packaged snapshots with working virtuoso support in the kde-redhat unstable repository[3]

gtk-qt-engine retired, replaced with kcm-gtk

User:Rdieter has decided to orphan the gtk-qt-engine package in favor of replacing it with the kcm-gtk package. The packages are for all intents and purposes identical except kcm-gtk doesn't ship the Qt style for gtk