[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-commits
Subject: www/areas/pim/development
From: Ingo Klöcker <kloecker () kde ! org>
Date: 2011-01-31 21:51:03
Message-ID: 20110131215103.AF6653E1F1 () svn ! kde ! org
[Download RAW message or body]
SVN commit 1218171 by kloecker:
Point more pages to the corresponding KDE Community Wiki pages.
M +4 -46 coding.php
M +2 -171 start.php
--- trunk/www/areas/pim/development/coding.php #1218170:1218171
@@ -4,55 +4,13 @@
include "$site_root/inc/new_pim.inc";
include "header.inc";
?>
+<!-- BEGIN CONTENT -->
-KDE PIM has a large and diverse code base.
-It also has a lot of different contributors,
-and (gladly!) accepts patches from outside
-the <a href="/people.php">core community</a>
-as well.
-However, to keep the code base sane and readable,
-there are <em>coding standards</em> which apply
-to various parts of the KDE PIM code.
-When you write a patch or contribute code,
-remember to follow these guidelines or you run
-the risk of your contribution being rejected.
-We don't like to reject things based on form,
-but it's got to be done to keep things readable in the long run.
+<p>The content of pim.kde.org is being moved to the <a \
href="http://community.kde.org/KDE_PIM">KDE PIM section</a> of the <a \
href="http://community.kde.org/">KDE Community Wiki</a>.</p>
-<h2>Coding standards</h2>
+<p><a href="http://community.kde.org/KDE_PIM/Development/CodingStyle">This page has \
already been moved.</a></p>
-<p>First off, there are the general guidelines that apply
-to all of KDE. I can't find them now, but they boild down to:
-</p>
-<ul>
- <li>Follow the coding standard you see in the code you are modifying.</li>
- <li>Follow the coding standard that applies to the code you are modifying.</li>
- <li>Before you commit, check out the <a \
href="http://techbase.kde.org/Policies/SVN_Commit_Policy">SVN \
Commit</a> policy.</li>
-</ul>
-
-<table class="iconlist">
-
-<tr>
-<td>
-<img src="<?php echo $site_root ?>/img/pixmaps/kmail.png" alt="KMail icon" \
title="The KMail Icon" width="48" height="48" border="0" />
-<br/>
-<img src="<?php echo $site_root ?>/img/pixmaps/korganizer.png" alt="KOrganizer" \
width="48" height="48" border="0" />
-<br/>
-<img src="<?php echo $site_root ?>/img/pixmaps/knode.png" alt="KNode" width="48" \
height="48" border="0" />
-<br/>
-<img src="<?php echo $site_root ?>/img/pixmaps/knotes.png" alt="KNotes" width="48" \
height="48" border="0" />
-</td>
-<td>
-KMail, KOrganizer, KNode, libkcal and libkabc have one single
-<a href="coding-korganizer.php">coding style</a>.
-It's a no-tabs, K&R brace style coding style.
-</td>
-</tr>
-
-</table>
-
-
-
+<!-- END CONTENT -->
<?php
include "footer.inc";
?>
--- trunk/www/areas/pim/development/start.php #1218170:1218171
@@ -6,179 +6,10 @@
?>
<!-- BEGIN CONTENT -->
+<p>The content of pim.kde.org is being moved to the <a \
href="http://community.kde.org/KDE_PIM">KDE PIM section</a> of the <a \
href="http://community.kde.org/">KDE Community Wiki</a>.</p>
-To get started, all you really need
-is a <a href="#git">GIT checkout</a>.
-After that, you can compile and run the latest-and-greatest
-(and maybe buggy) versions of the KDE PIM applications.<br>
-When you find a bug, you can fix it, create a patch,
-and send it to us! That's the way KDE PIM applications
-are continually improving. There is much more information
-available to begin with, though.
+<p><a href="http://community.kde.org/KDE_PIM/Development/Start">This page has \
already been moved.</a></p>
-<p>Here is a checklist of things to launch yourself into the
-world of KDE PIM development.<br>
-For lots of them, it is most important that you know they exist:
-</p>
-
-<ul>
-<li><a href="#mail">Subscribe</a> to the right
-<a href="#mail">mailing lists</a>. Read them regularly.</li>
-<li><a href="#tools">Browse</a> the information about the
-<a href="#tools">development tools</a>, to choose one. Most KDE PIM hackers
-use kate, vi, or emacs as editor and just compile in a konsole window,
-though.</li>
-<li>Take a brief look at the
-<a href="http://doc.trolltech.com/4.7">Qt documentation</a>.
-It is excellent, and you should know about QWidgets and QObjects a little
-before continuing.</li>
-<li>Take a brief look at the
-<a href="http://api.kde.org/">KDE documentation</a>.
-It is a bit overwhelming.</li>
-<li>Spend some time over at the
- <a href="http://www.kde.org/community/getinvolved/">KDE Community</a> website.
-</li>
-<li>Get the <a href="#prereq">prerequisites</a> for building KDE PIM master.
-Note that you really want to follow master to make a positive contribution to KDE \
PIM.<br>
-If you work on or with the last released version, you're usually a
-month or four behind the times, and that makes a <i>huge</i> difference
-in KDE PIM.
-You can work with a stable system -- the latest released KDE libs and base --
-and put (relatively) unstable PIM HEAD on it.</li>
-<li>Clone the relevant <a href="#git">GIT repositories</a>.</li>
-<li>Compile it and install.</li>
-<li>Report bugs, wishes, fix bugs, get involved!</li>
-</ul>
-
-<h2><a name="mail"></a>Mailing Lists</h2>
-
-<p>
-Mailing lists are probably the ultimate source of development information. Follow \
discussions of KDE
-core and application developers and ask your questions. Unless you don't think about \
what you are
-saying, you will surely get an answer.
-Subscribe to the <a href="http://mail.kde.org/mailman/listinfo/kdepim" \
target="_new">kde-pim mailing list</a>.
-It is for <b>discussion about development</b>.
-Please don't wildly post all your compilation problems there. Ask on <a \
href="#irc">IRC</a> for such issues.
-</p>
-
-<h2><a name="irc"></a>IRC (Chat)</h2>
-
-<p>
-Most of the developers hang around in one development
-IRC channel or another. On <a href="http://www.freenode.net/">freenode</a> \
(irc.kde.org), you can find:
-</p>
-<ul>
-<li>#KDE for the user questions.</li>
-<li>#akonadi for development discussion on Akonadi.</li>
-<li>#kontact for development discussion on Kontact and its components.
- Please don't post user-questions there.</li>
-</ul>
-<p>
-There are a variety of IRC (Chat) programs available.
-KDE ships with <a href="http://konversation.kde.org" target="_new">Konversation</a>.
-XChat is available in many installations as well.
-</p>
-
-<h2><a name="tools"></a>Common KDE Developer information</h2>
-
-<p>
-Visit the <a href="http://techbase.kde.org" target="_new">KDE techbase site</a> at
-<a href="http://techbase.kde.org" target="_new">http://techbase.kde.org</a> for very \
detailed
-information about KDE development.<br>
-You'll find lots of stuff, e.g. documentation, tutorials, reference guides, etc.
-</p>
-<p>
-<a href="http://techbase.kde.org/Projects/PIM" \
target="_new">http://techbase.kde.org/Projects/PIM</a>
-has lots of informations you may read before starting contributing to KDEPIM.
-</p>
-<p>
-<a href="http://userbase.kde.org/Kontact" \
target="_new">http://userbase.kde.org/Kontact</a> is
-the central place for user tips and tricks.
-</p>
-<p>
-<a href="http://www.kdevelop.org" target="_new">KDevelop</a> is an Integrated \
Development Environment
-for KDE. Learn more about KDevelop at
-<a href="http://www.kdevelop.org" target="_new">www.kdevelop.org</a>.
-</p>
-
-<p>
-For recent news about KDE development you may not miss the KDE news
-site at <a href="http://dot.kde.org" target="_new">dot.kde.org</a>
-</p>
-
-<h2><a name="prereq"></a>Prerequisites</h2>
-
-<p>
-the whole KDEPIM suite is composed of four modules. You're highly encouraged to
-checkout and build all of them:
-
-- <a href="http://www.akonadi-project.org" target="_new">Akonadi</a>, The PIM \
Storage Service
-- KDEPIMLIBS, the base libraries for all the PIM applications
-- KDEPIM-RUNTIME, the Akonadi resources which are required at runtime to let the \
kdepim applications
-communicate with the Akonadi server
-- KDEPIM, All the PIM applications
-</p>
-
-<p>
-In order to build and use the KDEPIM modules, you may use the last released KDE \
version.
-</p>
-
-<p>
-You might want to make a backup of your valuable data, though.
-Most of it lives in <tt>.kde</tt>, in your home directory;
-
-You may also backup your Akonadi server config files in \
<tt>$HOME/.config/akonadi</tt> and
-your kdepim applications data in <tt>$HOME/.local/share</tt>.
-<br>
-It may be easier to just create an additional user and
-give it a copy of your data, and run PIM HEAD there.
-</p>
-
-<h2><a name="git"></a>GIT - a Source Code Control System</h2>
-
-<p>
-The KDEPIM repositories can be visited via WWW at
-<a href="http://projects.kde.org" target="_new">http://projects.kde.org</a> or
-<a href="http://gitweb.kde.org" target="_new">http://gitweb.kde.org</a>.
-
-<br />
-the webpage is hosted in the <a href="http://websvn.kde.org/trunk/www/areas/pim" \
target="_new">KDE SVN repository</a>.
-</p>
-
-<h3>The really short guide</h3>
-
-This short guide will explain how to build Akonadi, kdepim and kdepim-runtime
-checked out from GIT.
-
-<p>You may use the following commands to check out the different repositories:
-<ul>
-<li> Akonadi:</li>
-<pre>
-git clone http://anongit.kde.org/akonadi
-</pre>
-<li> kdepimlibs:</li>
-<pre>
-git clone http://anongit.kde.org/kdepimlibs
-</pre>
-<li> kdepim-runtime:</li>
-<pre>
-git clone http://anongit.kde.org/kdepim-runtime
-</pre>
-<li> kdepim:</li>
-<pre>
-git clone http://anongit.kde.org/kdepim
-</pre>
-</ul>
-</p>
-
-<p>
-You can now build the modules in the following order:<br>
-Akonadi > kdepimlibs > kdepim > kdepim-runtime
-
-Complete guides to build KDE modules can be found on
-<a href="http://techbase.kde.org" target="_new">http://techbase.kde.org</a>.
-
-
<!-- END CONTENT -->
<?php
include "footer.inc";
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic