BetaWiki:Guidelines

We would like to ask you to follow these common practices for creating and extending BetaWiki content to prevent any possible conflicts.

Breaking or abusing the rules, depending on the severity, can result in either a verbal warning on your talk page or a temporary/permanent ban on administators' discretion. Your article might end up in the Hall of Shame if you don't follow the guidelines.

By editing on BetaWiki you acknowledge that you have read these rules and guidelines.

Common rules

The rules are not exhaustive. Do not assume that not forbidden automatically means allowed. We are not going to tolerate spam, vandalism, or not-so-okay usernames.

General

Any unoriginal content should be properly accredited to the original source.

Don't copy content from other sites without providing at least a source URL.

Add a build article only if you have a source of the particular build.

A source can be a leak, a screenshot, a file version, a mention in a warez CD list, mention in an antitrust document, etc. We document fakes aswell, so don't hesitate to make an article on a fake screenshot!

Make sure that you link to the articles you create!

If you don't, the article will get lost and probably will lead to another one being made, for no reason. Unlinked pages can be found here: Orphaned pages

The only exception to this rule is a staff member removing a controversial thread.

Talk pages are not a private messaging service

Use a different service to request your builds.

Naming scheme

Windows

Windows <version> build <buildnumber> (lab)

The specification above is the most verbose one and isn't going to be used a lot. In most cases BetaWiki covers only one build with a particular build number, in that case the lab (if any) should be omitted from the page name. Use the name that's reported by the RTM build in the version field, i.e. NT 4.0, XP, 10. If the full build tag contains a lab name, make sure to create a redirect from the most verbose form above to the reduced form of the page name (without lab), i.e. Windows XP build 2428 (idx01)⇒Windows XP build 2428.

In case there are several known builds with the same build number but from different labs, names of the pages should contain the lab name. To maintain a degree of consistency, the reduced name without a lab should be used for a disambiguation between the individual builds. If there are several known builds with the same build number that come from the same lab (i.e. are distinguished by the build date and time only), add the full timestamp to the lab component, i.e. Windows Longhorn build 4050 (private/lab06_demo.031019-1809).

For Windows versions that just used a major and a minor version number, use them in the version field and omit the buildnumber completely, i.e. Windows 1.04. For versions of Windows 2.x that had different 286 and 386 compiles, add the particular architecture to brackets, i.e. Windows 2.11 (386).

Don't mention the full update name for builds of Windows 10 updates, just use a plain numeral 10, i.e.: Windows 10 build 16179. On the other side, it's encouraged to make separate build listings for the individual updates, whose names should contain the official name of the update, i.e.: Windows 10 Creators Update. The YYMM update version should redirect to the full name, for example Windows 10 v1703 would redirect to the Creators Update mentioned before.

Redirects

To make searching for build pages easier, BetaWiki maintains a couple more redirects aside from the ones mentioned above:

If the build has got an official name, we should redirect it to the main page, i.e. Windows 8.1 Preview⇒Windows 8.1 build 9431.

If there are more official builds with the same official name, redirect it to the main version page, i.e. Windows 10 Insider Preview⇒Windows 10

The full buildtag, both including and not including the major and minor version must redirect to the main article, i.e. 6.3.9431.0.winmain_bluemp.130615-1214⇒Windows 8.1 build 9431, 9431.0.winmain_bluemp.130615-1214⇒Windows 8.1 build 9431. If there is a build number conflict between two versions of Windows, make a disambiguation at the conflicting redirect name.

For already existing articles, the old-fashioned page name should redirect to the new page name for the purpose of not breaking old links.

If the build calls itself by a codename, the combination of the codename and the build number should also be a redirect, i.e. Chicago 40e⇒Windows 95 build 40e

macOS

Classic

Mac OS <version> build <build>

Mac OS X

Mac OS X <version> build <build>

OS/2

<vendor> OS/2 <version> build <build>, where vendor can be either Microsoft or IBM.

Omit the vendor part for OS/2 2.0 and later, make sure to redirect the name with a vendor to the actual page.

Templates

Infobox Windows build

Every page about a Windows build must contain the "Infobox Windows build" template. It has only two required values: buildtag (the whole known buildstring, for example 6.3.9431.0.winmain_bluemp.130615-1214 or 5.1.2428.idx01.010129-1827) and version (i.e. 8.1 or Server 2003). If you don't supply any image, Placeholder.png will be automatically used.

Reference for other values:

{{ Infobox Windows build|buildtag = 9.9.9999.0.winmain.991231-2359|version = 9|arch = x86, x64, ARM, ia64 //CPU architectures on which the build is avaliable (leaked/released)|sku = Personal<br/>Professional<br/>Ultimate<br/>Home Preview //SKUs in which the build is avaliable (leaked/released), preferably from low-end to high-end|bios = 2099-12-31 //Expected BIOS date|key = 12345-67890-ABCDE-FGHIJ-KLMNO //Product key required when installing|timebomb = 2100-12-31 (+365 days) //If the build has timebomb, when it ends (+ number of days after compilation)|emulator = [[BWware]]<br/>[[BetaBox]] //Emulators or hypervisors that the build is confirmed to work in|winver = Winver.png //Screenshot of winver or about dialog in older windows|ba = //BetaArchive database search query - this parameter should be the release GUID, if this is a specific BA release, or a string query that is as specific as possible|rivals = //Use the rivals template to link pages on TCB & BA}}

Infobox macOS build

Every page about a macOS build must contain the "Infobox macOS build" template. It has only three required values: brand (the OS brand, that is "System Software", "Mac OS", "Mac OS X", "OS X" or "macOS"), buildtag, and version. If you don't supply any image, Placeholder.png will be automatically used.

Rivals

Use when the build you're posting also has an article on BA wiki, has a build page on TCB or has a gallery on TCB.

BLItem

When creating buildlists, use the provided BLItem templates:{{BLItem Confirmed|<article-title>|<buildtag>}} - use when the build was leaked, released, or we have another confirmation from Microsoft. Private leaks don't count.{{BLItem Unconfirmed|<article-title>|<buildtag>}} - use when there is information avaliable, however no provided proof for it {{BLItem Fake|<article-title>|<buildtag>}} - use when this build is fake, don't use if it's real and fake screenshots are also avaliable

When sorting buildlists, the first thing that matters is the build number. If there are several different builds with the same number, always sort them like this:

winmain (& derivates like winmain_rtm or winmain_bluemp)

partner recompiles (fbl_partner_out)

other builds sorted alphabetically

Screenshots

Thanks to Foxlet for writing this!
Screenshots should be "clean" (no extraneous borders outside the video area) and scaled to their true size. If possible, use the Windows screenshot feature (Print Screen key, Snipping Tool) to take pictures of the desktop, or use the screenshot feature if using a hypervisor/emulator. For "Full Screen" shots, if a cursor is present, it should be isolated in a corner of the background if possible (to show unique features of the cursor). All screenshots should be lossless (JPEG is not acceptable).

Good Shot: Clean area at true scale

Good Shoot: 1024x768 in True Color

Good Shot: Pixels are 1:1, even at lower resolution

Good Shot: True scale and with transparency/shadow effects

Good Shot: Additional graphics are seen as the intended subject is the hypervisor, and the window is properly cropped

Bad Shot: Image has additional graphics and is not properly cropped, although it meets all other criteria

Article Screenshots

The desktop shouldn't be visible in application screenshots.

Each main article usually requires three components: the Desktop, the About window, and (sometimes) the Logo. In most cases, a Windows article only needs the first two. "Full Screen" shots (such as for the Desktop and Start Menu) should be 1024x768 in 16-bit color at minimum, unless the subject in question does not support such a video mode (for example, 1024x768 in 256 colors is fine for Windows 3.1 and Microsoft Chicago). Screenshots must not use themes, wallpapers, or other graphics that are not included with the particular operating system or application build. The default look and feel should be used for most screenshots; any personalization options can be reasonably demonstrated in a "Demo" screenshot in the Gallery.

Desktop shots should be void of any extra windows, it should represent the state of the system when it is completely idle without any running programs. In the case that the OS shows a tool or special graphic (such as a welcome screen), that is known as a "First Boot" shot, and is separate from the Desktop shot.

Each article also contains a Gallery, where other associated shots are contained. Additional full screen shots belong here, such as the "Demo" (which shows off particularly unique features of a build). The remaining shots are usually those of programs unique to a build. Those shots should be cropped to the size of the program's window (including transparency and window shadows if such effects are present). Child windows (if any) should be visible in their full area. The screenshots should be free of any watermarks, unless the respective build is unleaked and the only available screenshots are watermarked. Article screenshots should not be annotated in Paint or any other image editor, again the only exception is if there's no other screenshot available and the build is unleaked.