KDE TechBase:Migrate content: Difference between revisions

Revision as of 19:29, 10 June 2007

Information about syntax and templates can be found here.

How to fill this wiki with life

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

Rules

Page names aren't in CamelCase (CamelCase proper nouns - like DocBook - are okay)
Make use of subpages, for example Policies/SVN Commit Policy
Make use of templates to mark Pages as relevant for KDE 3 or 4
Use categories inside those templates.
In case of doubt, read the 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

Roadmap

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.

@@ Line 21: / Line 21: @@
 See also: [[Projects/Partners]]
-In order to finish the migration to the wiki we need to define a time span in which we manage to
+Things to be done:
-# identify and port all relevant content from the old developer pages
+# dynamic content like feature plan
-#* tutorials and similar static content
+#* TODO: enable our mediawiki extension for our xml based feature plans
-#* dynamic content like feature plan (right now based on .xml file, [http://meta.wikimedia.org/wiki/Extending_wiki_markup mediawiki extension] sane?)
+# validate our tutorials (i.e. proof-read everything and really try it)
-# 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. proofread everything and really try it)
 # finish half-started pages (fill todo's in the e.g. KDE Architecture pages)
 # <insert todo's here>