KDE TechBase:Migrate content: Difference between revisions

Latest revision as of 18:49, 12 July 2012

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~~ Apart from some developers' home directories, all URLs on http://developer.org redirect to techbase.kde.org
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 1: / Line 1: @@
-== How to fill this page with life ==
+Information about syntax and templates can be found [[Help:Contents|here]].
+== How to fill this wiki with life ==
 # Step: Identify all developer-related content
-# Step: check [http://developer.kde.org developer.kde.org] pages for similar content
+# <del>Step: check [http://developer.kde.org developer.kde.org] pages for similar content</del> Apart from some developers' home directories, all URLs on http://developer.org redirect to techbase.kde.org
 # Step: put the material on this wiki
-# If content is missing, use the template <nowiki>{{migrate|from-url}}</nowiki> to add a todo-box.
+# If content is missing, use the template {{[[Template:movepage|movepage]]|''from-url''}} to add a todo-box.
-== Follow some simple rules ==
+== Rules ==
-# NotNotUseCamelCaseWikiSyntaxForPages (It has been dong wrong already)
+# Page names aren't in CamelCase (CamelCase proper nouns  - like ''DocBook'' - are okay)
-# Make use of subpages, e.g. [[Policies/Commits]]
+# Make use of subpages, for example [[Policies/SVN Commit Policy]]
 # Make use of [http://meta.wikimedia.org/wiki/Help:Template templates] to mark Pages as relevant for KDE 3 or 4
 # Use categories inside those templates.
-# 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]
-# '''Important:'''If you do have an svn account, ''please use the same login as in svn''. We might introduce unified login soon.
+# If you do have a KDE Subversion account, please use the ''same username'' in the wiki, because we might introduce unified login
+== Roadmap ==
+See also: [[Projects/Partners]]
+Things to be done:
+# dynamic content like feature plan
+#* TODO: enable our mediawiki extension for our xml based feature plans
+# validate our tutorials (i.e. proof-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 ==
-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 reliefing 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.