Difference between revisions of "KDE TechBase:Migrate content"

Jump to: navigation, search
m (fix link)
(draft of migration roadmap, just some thoughts...)
Line 16: Line 16:
 
# In case of doubt, read the [http://meta.wikimedia.org/wiki/Help:Contents#For_editors Media Wiki Users Guide]
 
# In case of doubt, read the [http://meta.wikimedia.org/wiki/Help:Contents#For_editors Media Wiki Users Guide]
 
# If you do have a KDE Subversion account, please use the ''same username'' in the wiki, because we might introduce unified login
 
# If you do have a KDE Subversion account, please use the ''same username'' in the wiki, because we might introduce unified login
 +
 +
== Roadmap ==
 +
 +
In order to finish the migration to the wiki we need to define a time span in which we manage to
 +
# identify and port all relevant content from the old developer pages
 +
#* tutorials and similar static content
 +
#* dynamic content like feature plan (right now based on .xml file, [http://meta.wikimedia.org/wiki/Extending_wiki_markup mediawiki extension] sane?)
 +
# redirect/map the old URLs to the new locations (httpd layer)
 +
# <insert todo's here>
 +
 +
After the migration we should
 +
# validate our tutorials (i.e. prove read everything and really try it)
 +
# finish half-started pages (fill todo's in the e.g. KDE Architecture pages)
 +
# <insert todo's here>
  
 
== Keep in mind ==
 
== Keep in mind ==
  
 
It's a wiki, you can change things easily later on. Note that this is not an invitation to just dump stuff here, but it may be relieving to know that not everything has to be perfect at first approach.
 
It's a wiki, you can change things easily later on. Note that this is not an invitation to just dump stuff here, but it may be relieving to know that not everything has to be perfect at first approach.

Revision as of 21:10, 27 December 2006

Information about syntax and templates can be found here.

Contents

How to fill this wiki with life

  1. Step: Identify all developer-related content
  2. Step: check developer.kde.org pages for similar content
  3. Step: put the material on this wiki
  4. If content is missing, use the template {{migrate|from-url}} to add a todo-box.

Rules

  1. Page names aren't in CamelCase (CamelCase proper nouns - like DocBook - are okay)
  2. Make use of subpages, for example Policies/SVN Commit Policy
  3. Make use of templates to mark Pages as relevant for KDE 3 or 4
  4. Use categories inside those templates.
  5. In case of doubt, read the Media Wiki Users Guide
  6. If you do have a KDE Subversion account, please use the same username in the wiki, because we might introduce unified login

Roadmap

In order to finish the migration to the wiki we need to define a time span in which we manage to

  1. identify and port all relevant content from the old developer pages
    • tutorials and similar static content
    • dynamic content like feature plan (right now based on .xml file, mediawiki extension sane?)
  2. redirect/map the old URLs to the new locations (httpd layer)
  3. <insert todo's here>

After the migration we should

  1. validate our tutorials (i.e. prove read everything and really try it)
  2. finish half-started pages (fill todo's in the e.g. KDE Architecture pages)
  3. <insert todo's here>

Keep in mind

It's a wiki, you can change things easily later on. Note that this is not an invitation to just dump stuff here, but it may be relieving to know that not everything has to be perfect at first approach.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal