Wiki Maintenance

From ReactOS Wiki
Revision as of 07:18, 9 September 2010 by DangerGround (talk | contribs)
Jump to: navigation, search

The purpose of this page is to direct users to articles that need attention and improvement. These articles may need more information, verification, or better organization. If you plan to create a new page, make sure it is relevant to the ReactOS project (pages dealing with testing, development, or documentation).

How to proceed

There is currently a need for volunteers to edit the wiki. This is a position where anyone wanting to contribute to the ReactOS community is welcome to join. All it takes to edit the wiki is to create an account. After creating an account, take the time to learn how to edit a page.

If you are not sure what to do, here are a few things to get you started:

  1. Mark articles needing changes with the appropriate Template flag (e.g., {{del}}, {{outdated}}, {{stub}}, etc.).
  2. Make sure pages have a similar style and layout -- similar use of headings, emphasis, code, and so on.
  3. Correct spelling, grammar, and language use; try to make it more professional sounding.
  4. Make the text concise and readable; remove irrelevant links and content.

General cleanup

If you do not have the time to do the cleanup yourself, simply marking articles as needing cleanup using one of the Templates can be helpful.

The Plan

The plan is to make the wiki to a place where you can find information about ReactOS development.

Phase 1

  • Mark all pages that don't belong to the wiki as {{del}}
  • Merge articles that cover the same area together
  • Move structures, APIs, stuff for clean room reverse engineering to Techwiki

Phase 2

  • Review existing articles.
  • Link existing articles in articles where is makes sense, to present a flow in information search.
  • Use List of articles sorted by relevance to add notes about work that has to be done. The article's discussion page may also be used.

Phase 3

  • Remove orphaned pages
  • Add supplementary pages that would provide a better understanding

List of articles sorted by relevance

Writing tests

article is based on CIS, which isn't used, we have buildbot, it would be more important to give a introduction on how to write tests, e.g. for Kernel APIs --DangerGround 09:17, 23 October 2008 (UTC)

Development Introduction

could be much more extended, needs a review --DangerGround 09:17, 23 October 2008 (UTC)

I tried cleaning it up a bit. --RideBMX 23:44, 26 October 2009 (UTC)

Testing Introduction

the text from the last few headlines is outdated and doesn't help very much --DangerGround 09:17, 23 October 2008 (UTC)

Version Status

could get a more uniform look --DangerGround 09:17, 23 October 2008 (UTC)

Needs review after new Version Status page implemented. --RideBMX 23:44, 26 October 2009 (UTC)


could be extended and merged to Techwiki --DangerGround 09:17, 23 October 2008 (UTC)

Moved information from several other pages into Kernel. Still needed to be fixed up. --RideBMX 23:44, 26 October 2009 (UTC)

ReactOS subsystems

most of them don't exist or not integrated into reactos, we should only document existing systems here --DangerGround 09:45, 23 October 2008 (UTC)

ReactOS ports

we need a page where we collect ports from ReactOS to other architectures than PC, some comments about current progress should be given there--DangerGround 09:45, 23 October 2008 (UTC)

Page created with minor information about each port. Information needs to be merged from port pages -- AMD64, PowerPC/PowerPC-Old, Xen port(?) -- and it needs information from the port developer(s) about the current status. --RideBMX 04:11, 18 November 2009 (UTC)

* translation pages

IMO they should go, not used for ages. Translators should be visible over svn commit messages. --DangerGround 17:01, 18 November 2009 (UTC)

Russian has been updated once since 2006, French hasn't been updated since 2007. They obviously do not reflect current status and do not include a lot of languages that are in ReactOS. Additionally, many translation updates are now included in bug reports and the changelogs. --RideBMX 18:37, 21 November 2009 (UTC)
Would it be possible to generate this information? e.g., Let a user select a language on some i18n page which generates a list of all the directories with a lang subfolder, along with the date of the last revision to the RC file. This wouldn't provide the actual translation status, but it would be automated and have all languages in ReactOS (as opposed to the list of 9 manually updated language lists here on the Wiki). --CycleGeek 21:08, 6 September 2010 (UTC)
Good idea, do you've time to write such a tool? --DangerGround 07:31, 7 September 2010 (UTC)
I have the time. Unfortunately, I don't have the experience to do it. --CycleGeek 03:11, 9 September 2010 (UTC)
Choose a language where you can use svn tools, do a scan over trunk, check for lang folders and which languages are in there (with), save that somewhere (this task should be done on a regulare basis, e.g. cronjob). Maintain a list with languages. As query there should be two languages, normally english as base and a language to compare, e.g. german; now you go through your list and compare dates (or if the translation exists) and use some colors to make it visible. A next step would be to exclude wine ressources from list (there is a file WINE.README which contains wine-synces parts) --DangerGround


  • Categorize Events, probably use a template for a event navigation