KDE TechBase:Migrate content: Difference between revisions

From KDE TechBase
No edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 4: Line 4:


# Step: Identify all developer-related content
# 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
# Step: put the material on this wiki
# If content is missing, use the template <nowiki>{{movepage|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.


== Rules ==
== Rules ==
Line 21: Line 21:
See also: [[Projects/Partners]]
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)
# finish half-started pages (fill todo's in the e.g. KDE Architecture pages)
# <insert todo's here>
# <insert todo's here>

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

  1. Step: Identify all developer-related content
  2. 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
  3. Step: put the material on this wiki
  4. If content is missing, use the template {{movepage|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

See also: Projects/Partners

Things to be done:

  1. dynamic content like feature plan
    • TODO: enable our mediawiki extension for our xml based feature plans
  2. validate our tutorials (i.e. proof-read everything and really try it)
  3. finish half-started pages (fill todo's in the e.g. KDE Architecture pages)
  4. <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.

Retrieved from "https://techbase.kde.org/index.php?title=KDE_TechBase:Migrate_content&oldid=72782"