rev 9507 - people/mukidohime

Matthew Rosewarne mukidohime-guest at alioth.debian.org
Sun Mar 2 10:15:48 UTC 2008


Author: mukidohime-guest
Date: 2008-03-02 10:15:40 +0000 (Sun, 02 Mar 2008)
New Revision: 9507

Added:
   people/mukidohime/README.docbook
Modified:
   people/mukidohime/KDEinLenny.docbook
Log:
* Fleshing out
* instructions for the docbook-impaired


Modified: people/mukidohime/KDEinLenny.docbook
===================================================================
--- people/mukidohime/KDEinLenny.docbook	2008-03-02 06:18:09 UTC (rev 9506)
+++ people/mukidohime/KDEinLenny.docbook	2008-03-02 10:15:40 UTC (rev 9507)
@@ -8,16 +8,65 @@
 		</authorgroup>
 	</articleinfo>
 	<section label="notdone">
-		<title>Situation of KDE</title>
+		<title>Upstream Status</title>
 		<section label="notdone">
-			<title>KDE 3</title>
-			<para>KDE 3.5.9 is the final release of KDE 3</para>
+			<title>KDE 3.5</title>
+			<informaltable frame='none'>
+				<tgroup cols='2'>
+					<tbody>
+						<row>
+							<entry>3.5.5 <emphasis>(etch)</emphasis></entry>
+							<entry>Oct 2<superscript>nd</superscript>, 2006</entry>
+						</row>
+						<row>
+							<entry>3.5.8 <emphasis>(current)</emphasis></entry>
+							<entry>October 8<superscript>th</superscript>, 2007</entry>
+						</row>
+						<row>
+							<entry>3.5.9</entry>
+							<entry>February 14<superscript>th</superscript>, 2008</entry>
+						</row>
+					</tbody>
+				</tgroup>
+			</informaltable>
+			<para>There will be no further releases of KDE 3.</para>
 		</section>
 		<section label="notdone">
-			<title>KDE 4</title>
-			<para>4.0 does not provide a fully-usable desktop, and should not be shipped.</para>
-			<para>4.1 is intended to be a complete desktop for general use.</para>
+			<title>KDE 4.0</title>
+			<informaltable frame='none'>
+				<tgroup cols='2'>
+					<tbody>
+						<row>
+							<entry>4.0.0</entry>
+							<entry>January 8<superscript>th</superscript>, 2008</entry>
+						</row>
+						<row>
+							<entry>4.0.1 <emphasis>(current)</emphasis></entry>
+							<entry>February 4<superscript>th</superscript>, 2008</entry>
+						</row>
+						<row>
+							<entry>4.0.2</entry>
+							<entry>February 28<superscript>th</superscript>, 2008</entry>
+						</row>
+					</tbody>
+				</tgroup>
+			</informaltable>
+			<para>KDE 4.0.0 was tagged January 8<superscript>th</superscript>, 2008.  There have been two maintenance releases so far, 4.0.1 tagged February 4<superscript>th</superscript>, and 4.0.2 tagged February 28<superscript>th</superscript>.  KDE 4.0 does not provide a fully-usable desktop, and was never considered a suitable to replace KDE 3.5.  KDE 4.0.0 had stability issues which were mostly corrected in later maintenance releases.  The KDE PIM applications were not ready in time for 4.0, so they were not included in the release.</para>
 		</section>
+		<section label="notdone">
+			<title>KDE 4.1</title>
+			<informaltable frame='none'>
+				<tgroup cols='2'>
+					<tbody>
+						<row>
+							<entry>4.1.0</entry>
+							<entry>July 22<superscript>nd</superscript>, 2008 <emphasis>(planned)</emphasis></entry>
+						</row>
+					</tbody>
+				</tgroup>
+			</informaltable>
+			<para>KDE 4.1 is the first release of KDE 4 intended to be a complete desktop ready for widespread use.  With the release of KDE 4.0, application developers made final releases of their KDE 3 applications and switched focus to KDE 4, so most KDE applications should be available for 4.1.</para>
+		</section>
 	</section>
 	<section label="notdone">
 		<title>The previous plan</title>
@@ -121,25 +170,48 @@
 			<title>Problems with this plan</title>
 			<section label="notdone">
 				<title>Maintainability of KDE 3 packages</title>
-				<para>3.5.9 will be the final KDE 3 release</para>
-				<para>Debian effectively forks KDE 3, becoming the new upstream.</para>
-				<para>Flash debacle</para>
-				<para>Applications have been removed or rewritten upstream</para>
+				<para>Since KDE 3.5.9 will be the final release of KDE 3, any improvement or maintenance would have to be done by the Debian Qt/KDE Maintainers.  This work would place an unnecessary burden on the packagers and effectively create a Debian-only fork.</para>
+				<para>The surprise of a new version of flashplugin-nonfree that was incompatible with Konqueror caused many users a great deal of frustration.  Since the KDE developers consider KDE 3 to be effectively dead code, another such event during lenny's release life would be very difficult to resolve.</para>
+				<para>During the development of KDE 4.0, numerous applications have either been removed, replaced, or rewritten.  It is therefore impossible to resolve bugs filed against these KDE 3 packages, so they will have to be tagged "wontfix" and ignored.</para>
 			</section>
 			<section label="notdone">
 				<title>&quot;Make Debian sexy again&quot;</title>
-				<para>KDE 3 makes lenny seem slale</para>
-				<para>Contemporary distribution releases will likely include KDE 4</para>
+				<para>The platform of the current DPL puts a strong emphasis on making Debian more appealing and persuing fresher software.  From a user's perspective, releasing with KDE 3 would give the lenny the immediate impression of being stale and obsolete on arrival.   Contemporary releases from other distributions will undoubtedly use KDE 4.1, so that impression would be deserved.  While it's unlikely that the lack of a modern KDE release would drive away existing users, it would certainly cause many potential new users to overlook Debian when choosing a distribution for the desktop.</para>
 			</section>
 			<section label="notdone">
-				<title>Development platform is not useful</title>
-				<para>The primary reason to have a development platform is to develop applications for some target.  If Lenny is not actually running a KDE 4 desktop, the utility of the development platform is very limited.  KDE developers use SVN, and people building KDE 4 will likely be using a platform that does ship the KDE 4 desktop.</para>
-				<para>The 4.0 development platform should not be shipped, since some of its APIs are incomplete or expected to change for 4.1.</para>
+				<title>A KDE 4.0 development platform is not useful</title>
+				<para>Besides KDE developers (who use the KDE VCS), anyone building KDE 4 software will likely be targeting a platform that uses a KDE 4 desktop.  If Lenny is not actually running a KDE 4 desktop, the utility of the development platform is very limited.</para>
+				<para>The Plasma ABI will not be stabilized until KDE 4.1, so it makes very little sense to include Plasma-related parts of the KDE 4.0 development platform.  Significant API additions, such as WebKit, Akonadi, and Decibel, will also be introduced in KDE 4.1.</para>
 			</section>
 		</section>
 	</section>
 	<section label="notdone">
 		<title>The new plan</title>
-		<para>There might still be a possibility to include KDE4 in lenny.  The efforts on KDE4.1 have been quite promising and seem to be leading to a desktop environment which can fully replace KDE3.  The KDE team will provide betas and release candidates of the 4.1 release in experimental and interested users are encouraged to test them. Should KDE4.1 be on time and now major problems be discovered, the release team welcomes an upload to unstable.</para>
+		<blockquote>
+			<attribution>Marc 'HE' Brockschmidt</attribution>
+			<para>There might still be a possibility to include KDE4 in lenny.  The efforts on KDE4.1 have been quite promising and seem to be leading to a desktop environment which can fully replace KDE3.  The KDE team will provide betas and release candidates of the 4.1 release in experimental and interested users are encouraged to test them. Should KDE4.1 be on time and now major problems be discovered, the release team welcomes an upload to unstable.</para>
+		</blockquote>
+		<section label="notdone">
+			<title>Benefits from this plan</title>
+			<section label="notdone">
+				<title>Happy packagers</title>
+				<para>Doing KDE4 packaging anyway, time not wasted backporting</para>
+				<para>Security and bug fixes easily backportable</para>
+				<para>Lots of bugs closed</para>
+			</section>
+			<section label="notdone">
+				<title>Happy hackers</title>
+				<para>kubuntu became choice of many KDE developers partly due to recent software</para>
+				<para>more interest in Debian from upstream</para>
+				<para>maybe more upstream devs running Debian</para>
+				<para>overall better cooperation between Debian and KDE</para>
+			</section>
+			<section label="notdone">
+				<title>Happy users</title>
+				<para>Fun new software, yay</para>
+				<para>existing users enjoy improved features and fixed bugs</para>
+				<para>potential users are more interested in trying Debian</para>
+			</section>
+		</section>
 	</section>
 </article>

Added: people/mukidohime/README.docbook
===================================================================
--- people/mukidohime/README.docbook	                        (rev 0)
+++ people/mukidohime/README.docbook	2008-03-02 10:15:40 UTC (rev 9507)
@@ -0,0 +1,11 @@
+So, you want to use docbook?
+----------------------------
+
+Edit KDEinLenny.docbook in your editor, it's XML.
+
+My preferred way to view the results:
+apt-get install docbook-simple docbook-xsl xsltproc
+xsltproc --output KDEinLenny.html /usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl KDEinLenny.docbook
+open KDEinLenny.html
+
+You can also use docbook-utils, docbook2odf, dblatex, or whatever else.




More information about the pkg-kde-commits mailing list