Forum Post Migration Guidelines

Signaleers who take part in forum post migration programme must read and follow the migration guidelines below.

General Guidelines

All wiki editors must be familiar with Wiki Editing Guidelines.

Creating a page

Follow instructions in general guidelines to create a page which does not yet exist. If you don't have permission to create the page in the required namespace, omit the namespace prefix. Once it is reviewed, it will be moved to the target namespace by the administrator.

Images

Images in posts must be uploaded to the wiki and referenced using File: tag.

Style

Forum posts are often written from the first-person view and in a form of announcement. This represents typical single-author and point-in-time nature of forum communications. By contrast, wiki posts describe current or historical state of events and, over their lifetime, may be updated by many editors. For this reason, migrated forum posts should be rewritten from the third-person view. The following examples illustrate common post elements which must be edited during migration.

Minimal change

A good example of a post which requires minimum modification is Announcing the Search and Rescue Ship Replacement Program!. Although it is titled as an announcement, the body of the post is written in present tense which indicates a current and ongoing endeavour. Also it doesn't have any first-person pronouns and does not sound like an address. This post can be transferred to the wiki verbatim and the only required change is renaming it to "Search and Rescue Ship Replacement Program".

Common style elements which require rewording

PSA: Don't Use "Jita Scam" Format for Giveaways contains several elements which must be rewritten.

Post text	Proposed wiki text	Comment
It happened last year and has happened again this year that Signal Cartel members are being reported for scamming in Jita because they are using the typical "isk doubling scam message" format in trade hubs' Local chat to offer ISK to others in the spirit of the season. Please don't do this!	Signaleers who offer giveaways to out-of-corp members of Eve Online community must not use Jita scam format, like ISK doubling.	The starting sentences require the following modifications: Time references. "It happened last" year is anchored to the post publication date. Although a wiki page has its creation date, it is not readily visible on the screen, hence it is not immediately clear what period of time is referenced. Such relative reference should be removed or replaced with an absolute value, such as "in 2016". Context. The first sentence describes the sequence of events which led to publication of this PSA. This is appropriate in an announcement post but should not form part of the policy. If the context is required it can be provided through back references (described below). Addresses. "Please don't do this!" is an address which, again, is appropriate in a personal post, but should not be used in a policy. The restriction must be written as a statement.
Third parties will assume you are scamming and I will then get emails...	Third parties will assume you are scamming and the corp management will then get emails...	First-person view. The corp policy represents the position of corporation management in general and as such should be written from a third-person view.

Back References

To give credit to the original author of the post, each page must contain a section titled Reference with a link to the forum post.

Example

ESR:EvE-Scout Rescue Cache (ESRC) - Quick Reference Guide is an example of a migrated forum post which demonstrates common formatting techniques.

Reviews

Each migrated post must be reviewed by a relevant person.

Content	Reviewer
Policies, PSAs, any posts published by Mynxee, Thrice Hapus, Johnny Splunk or Katia Sae	Thrice Hapus or Katia Sae
Public information (in Public: namespace)	Katia Sae
Divisional information, as indicated by the namespace	Division Heads, or their delegates
All other information	Any member with C1 title

---

Historical Reference

The rest of this page relates to our process migrating information from the old forum posts to this wiki and has been kept for historical reference only.

Rewards

Corp management has pledged their support for migration of certain content to wiki. It mostly includes forum posts linked in DII and some pages on the corp blog. For each migrated page from the list supported by management, editors will receive a reward proportional to the size of the original content.

Migration tracking

The posts whose migration is officially supported by the management are listed in a table on a separate page. Here is the format of the table:

Post	Reward	Namespace	Page	Status	Editor	Reviewed by	Paid by

Post and Reward columns contain a pre-filled list of forum posts and rewards, in millions ISK. Other columns are initially empty. Status indicates the stage of the post's migration and can have values "In progress", "In review" and "Reviewed".

Migration workflow

Master List for Management-Supported Content Migration

1. An editor selects a post to migrate, puts their name into Editor column and changes Status to "In progress". The wiki markup shortcut for name and timestamp is ~~~~. Each editor can have only one in-progress post.
2. After the wiki page is created, edited and formatted, it must be reviewed. The editor
   1. adds the page name to Page column and links it to the new page using [[ ]] markup;
   2. changes the status to "In review", and
   3. requests a review from the appropriate reviewer. At this point the editor can start working on another post.
3. The reviewer provides feedback to the editor and they work together until the reviewer is satisfied with the result.
4. The reviewer changes the status to "Reviewed" and adds their name and the timestamp to Reviewed by column using ~~~~ markup. The timestamp is especially important for posts which will be moved to protected namespaces as it shows which revisions have been approved by the reviewer.
5. (Optional) If the new page must be in a protected namespace, the administrator will move it there. All revisions made after the reviewer's approval will be discarded.
6. A treasurer pays the agreed reward to the editor. This step does not depend on the page movement to a protected namespace; it can be performed as soon as the reviewer marked the page as reviewed.