Projects/kde.org/Meetings/September08: Difference between revisions

From KDE TechBase
(New page: ===KDE Web Developers Meeting for September 2008=== The idea behind this meeting is to determine some future goals for the porting of kde.org and its sub domains over to a CMS system and ...)
 
No edit summary
(12 intermediate revisions by 2 users not shown)
Line 2: Line 2:


The idea behind this meeting is to determine some future goals for the porting of kde.org and its sub domains over to a CMS system and also on the future of open collaboration services within the KDE online community.
The idea behind this meeting is to determine some future goals for the porting of kde.org and its sub domains over to a CMS system and also on the future of open collaboration services within the KDE online community.
====When====
The meeting will be held in the #kde-www IRC channel on Freenode. It is scheduled to start on the 10th October 2008 at 1200 noon GMT. We'll see you there!
====Agenda====


Here is a basic list of what we're going to try and cover:
Here is a basic list of what we're going to try and cover:


* What is the current state of the KDE family of websites?
# What is the current state of the KDE family of websites?
  > Outdated/obsolete information - how pervasive?
## Outdated/obsolete information - how pervasive?
  > Well maintained sites
## Copyright issues - no policy on reuse of information and images
* What obstacles are there that would make improving KDE websites difficult?
## Well maintained sites
* Changing to a CMS system
# What obstacles are there that would make improving KDE websites difficult?
  > Which CMS do we use
## Too many scattered sites to maintain. Merge into Techbase and Userbase?
  > Porting content
# Changing to a CMS system
    * Method
## Which CMS do we use (Possibly [http://drupal.org Drupal])
    * Obstacles
## Porting content
  > CMS upgrades and versioning issues
### Method
* Centralizing the management of users, information and services for all parts of the KDE community
### Obstacles
  > Viability
### Re-word content to improve perception of KDE (see: [http://aseigo.blogspot.com/2008/09/what-does-kde-app-mean.html])
  > Method
## CMS upgrades and versioning issues
  > Open Collaboration Services
# Centralising the management of users, information and services for all parts of the KDE community
* Organise a physical KDE WWW developers meeting
## Viability
## Method
## [http://freedesktop.org/wiki/Specifications/open-collaboration-services Open Collaboration Services]
# What roles can be allocated out immediately
# Build a list of people wanting to help out
# Organise a physical KDE WWW developers meeting
# Organise another IRC meeting
 
 
==== Log ====
The log is available in a separate page, due to it's length ==> [[Projects/kde.org/Meetings/September08/Log|Log]]

Revision as of 14:54, 12 October 2008

KDE Web Developers Meeting for September 2008

The idea behind this meeting is to determine some future goals for the porting of kde.org and its sub domains over to a CMS system and also on the future of open collaboration services within the KDE online community.

When

The meeting will be held in the #kde-www IRC channel on Freenode. It is scheduled to start on the 10th October 2008 at 1200 noon GMT. We'll see you there!


Agenda

Here is a basic list of what we're going to try and cover:

  1. What is the current state of the KDE family of websites?
    1. Outdated/obsolete information - how pervasive?
    2. Copyright issues - no policy on reuse of information and images
    3. Well maintained sites
  2. What obstacles are there that would make improving KDE websites difficult?
    1. Too many scattered sites to maintain. Merge into Techbase and Userbase?
  3. Changing to a CMS system
    1. Which CMS do we use (Possibly Drupal)
    2. Porting content
      1. Method
      2. Obstacles
      3. Re-word content to improve perception of KDE (see: [1])
    3. CMS upgrades and versioning issues
  4. Centralising the management of users, information and services for all parts of the KDE community
    1. Viability
    2. Method
    3. Open Collaboration Services
  5. What roles can be allocated out immediately
  6. Build a list of people wanting to help out
  7. Organise a physical KDE WWW developers meeting
  8. Organise another IRC meeting


Log

The log is available in a separate page, due to it's length ==> Log