a11y: Accessibility, or the act of ensuring a high quality experience for all users regardless of blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. #

admin: (and super admin) #

alpha (beta): Pre-release version of software intended to signal desire for compatibility, functional, and unit tests and feedback. Also see release candidate. #

back compat: Backwards compatibility – a desire to ensure that plugins and themes do not break under new releases – is a driving philosophy of WordPress. While it is a commonly accepted software development practice to break compatibility in major releases, WordPress strives to avoid this at all costs. Any backwards incompatible change is carefully considered by the entire core development team and announced, with affected plugins often contacted. It should be noted that external libraries, such as jQuery, do have backwards incompatible changes between major releases, which is often going to be a greater concern for developers. #

backport: A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. #

bleeding edge: The latest revision of the software, generally in development and often unstable. Also known as trunk. #

blocker: A bug which is so severe that it blocks a release. #

blog: (versus network, site) #

branch: A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.5, 3.6, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a “branch”, such as “the 3.6 branch”. #

bug: A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. #

command line interface (CLI): A type of human-computer interface (i.e., a way for humans to interact with computers) that relies solely on textual input and output. The entire display screen, or the currently active portion of it, shows only characters (and no images), and input is usually performed entirely with a keyboard. #

commit (noun): An individual change to WordPress, identified by an incremental revision number. Also called a changeset. #

commit (verb): To make a change to WordPress. Only committers can commit code, but often the code is contributed by developers without commit access. #

committer: A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers – a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. #

conflict: A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. #

copyright license: Copyright holders may grant a license with various allowances including the ability to modify or distribute the copyrighted material. Also see GPL. #

CRUD:

Create, read, update and delete, the four basic functions of storing data. (More on Wikipedia.) #

CSS: Cascading Style Sheets. #

docblock: (phpdoc, xref, inline docs) #

dogfood: The practice of using one’s own software, typically bleeding edge (trunk), thus “eating one’s own dogfood”. This also applies to using one’s own APIs internally. #

enhancement: Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. #

feature request: A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. #

GPL: GNU General Public License. Also see copyright license. #

hacked: #

HTML: HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. #

i18n: Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. #

IDE: Integrated Development Environment. A software package that provides a full suite of functionality to software developers/programmers. Normally an IDE includes a source code editor, code-build tools and debugging functionality. #

inline docs: (phpdoc, docblock, xref) #

invalid: A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. #

IRC: Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. #

JS: JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. #

L10n: Localization, or the act of translating code into one’s own language. Also see internationalization. Often written with an uppercase L so it is not confused with the capital letter i or the numeral 1. WordPress has a capable and dynamic group of polyglots who take WordPress to more than 70 different locales. #

Locale: A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. #

major release: A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. #

make: A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly “wpdevel”), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). #

mu-plugins, must-use plugins: (include old history as “multi-user”; x-ref with drop-ins) #

multisite: Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site #

network: (versus site, blog) #

P2: A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. #

patch: A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. #

PHP: The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.2.4. #

PHPDoc: (docblock, inline docs) #

point release: A minor release of WordPress, identified by the third number (the 2 in 3.5.2). These releases are for maintenance and security fixes only. Feature development is limited to major releases. Changes to point releases are carefully considered, and only critical or blocker-level bugs, and security enhancements, hardening, and fixes are accepted. #

priority (bug tracker): The seriousness of a bug report or ticket in the eyes of the project. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. #

priority (hooks): (higher priority means lower number) #

punt: Contributors sometimes use the verb “punt” when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don’t “make the cut.” In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) #

regression: A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A “3.6 regression” would be a bug in 3.6 that worked as intended in 3.5. #

release candidate: One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). #

scope creep: The tendency for requirements to increase during a release’s development cycle beyond those originally approved for the upcoming release. Something to be avoided. Also known as feature creep. #

security issue: A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have. #

severity: The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. #

site: (versus network, blog) #

SSL: Secure Sockets Layer. Provides a secure means of sending data over the internet. Used for authenticated and private actions. #

SVN: Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. #

tag: A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) #

task (blessed): Feature development for an upcoming major release centers around task tickets, which are major features or important enhancements that have been blessed by the core team. A ticket should otherwise never receive this designation. #

ticket: Created for both bug reports and feature development on the bug tracker. #

Trac: An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. #

translation: The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. #

triage: The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. #

trunk: A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running “trunk”, then you are on the latest revision. #

UI: User interface #

unit test: Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. #

UX: User experience #

version control: A version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. #

wontfix: A resolution on the bug tracker (and generally common in software development) that indicates the ticket will not be addressed further. This may be used for acceptable edge cases (for bugs), or enhancements that have been rejected for core inclusion. #

worksforme: A resolution on the bug tracker (and generally common in software development) that indicates the bug reported cannot be reproduced. #

wpdevel: Formerly the development updates P2 blog at wpdevel.wordpress.com. It is now make/core and resides at make.wordpress.org/core. #

xref: (php-xref, phpdoc, inline docs) #