This documents purpose is to define some direction for the furthering of the KDE community as it pertains to the kde.org websites.

+

1.1 Purpose

+

This document outlines a plan for moving the KDE.org family of websites to a content management system (CMS) and explores future improvements to KDE websites.

−

1.1 Points for consideration:

+

1.2 Points for consideration:

* We need a meeting! A physical meeting.

* We need a meeting! A physical meeting.

Line 45:

Line 47:

2.1 Current sites

2.1 Current sites

−

2.1.1 Introduction

+

2.1.1 Current State

+

+

The current state of the kde family of websites is quite poor. There are numerous pages and subdomain websites which are out of date, inaccurate or both. Compounding this problem is the lack of any specific maintainers for pages and for subdomain sites.

+

+

2.1.2 The KDE.org Family

As well as having a rather large website at kde.org, there are also over 20 sub-domains (each with an independent website), hosted beneath kde.org

As well as having a rather large website at kde.org, there are also over 20 sub-domains (each with an independent website), hosted beneath kde.org

−

2.1.2 List of KDE.org main sections

+

2.1.3 List of KDE.org main sections

* About KDE

* About KDE

Line 60:

Line 66:

−

2.1.3 List of KDE.org sub domains

+

2.1.4 List of KDE.org sub domains

I've taken this list from http://www.kde.org/family/. Also, the current status of the kde.org sub domains can be viewed here: http://techbase.kde.org/Projects/kde.org/Site_Status. Please note that these lists may be out of date and incomplete.

I've taken this list from http://www.kde.org/family/. Also, the current status of the kde.org sub domains can be viewed here: http://techbase.kde.org/Projects/kde.org/Site_Status. Please note that these lists may be out of date and incomplete.

This document outlines a plan for moving the KDE.org family of websites to a content management system (CMS) and explores future improvements to KDE websites.

1.2 Points for consideration:

* We need a meeting! A physical meeting.
* Where are we currently?
* Where are we headed?
* What obstacles are in our path?
* Porting of kde.org websites to a CMS system such as Drupal
* Designing of systems to accommodate open collaboration services
* Centralizing the management of users, information and services for all parts of the KDE community

2. The current state and purpose of the KDE.org websites

2.1 Current sites

2.1.1 Current State

The current state of the kde family of websites is quite poor. There are numerous pages and subdomain websites which are out of date, inaccurate or both. Compounding this problem is the lack of any specific maintainers for pages and for subdomain sites.

2.1.2 The KDE.org Family

As well as having a rather large website at kde.org, there are also over 20 sub-domains (each with an independent website), hosted beneath kde.org

One of the main things that came out of Akademy 2008 was 'brining the KDE community to the desktop'. What does this mean? Ideas like 'seeing KDE users nearby' is a good example.

We all know that KDE has a large community that is going through a new phase of growth. Because of this, coordinating, designing and maintaining open collaboration services given the existing scattered state of different sections of the community would be almost impossible. And even if it was possible, maintaining the resulting mess would be an effective step backwards.

If we were able to centrally manage communities and services such as kde-look.org, kde.org and its sub-websites, svn, mailing lists, Amarok, Konversation, etc. then Open Collaboration services would be doable and far more powerful than previously possible.

If you think about the idea behind Akonadi (http://pim.kde.org/akonadi/), why don't we apply this to the KDE web community? Also, once we've done that, why don't we build our own web based 'Nepomuk'? Why not build the KDE community on these same 'pillars' as the desktop? This would make Open Collaboration services one of the most advanced out there for any community and allow the users of KDE unprecedented ease of use and integration with each other. Of course, due appreciation of privacy and security need to be taken into account. And once again, having centralized management would make maintaining privacy and security a lot easier.