How to become a MediaWiki hacker/es

Este artículo está escrito para ayudar a desarrolladores novatos para que aprendan las habilidades necesarias para contribuir al desarrollo de MediaWiki y sus extensiones. En la mayoría de los casos cuando trabajas con MediaWiki, tu no querras modificar MediaWiki a menos que sepas realmente bien lo que está haciendo.

The main path to get started with Wikimedia development is to contribute to Wikimedia projects that offer mentoring. An alternative without mentoring is to fix a good first bug.

Si eres un desarrollador experimentado que posee experiencia con MediaWiki, visita el  en cambio.

Para otras maneras de aportar en la comunidad Wikimedia, ve ''.

Resumen
MediaWiki es el software que permite el funcionamiento de Wikipedia, sus proyectos hermanos y miles de wikis en todo el mundo.

MediaWiki está escrito en el lenguaje de programación PHP. Usa jQuery como librería cliente de JavaScript.

MediaWiki está escrito principalmente para la plataforma LAMP y se ejecuta en la mayoría de los sistemas operativos. MediaWiki usa principalmente servidores de MySQL y MariaDB.

Development happens in an open source style, is largely coordinated online, and supported by the Wikimedia Foundation, though volunteer community developers play a huge part as well.

Esta página debería ayudarte a convertirte en un colaborador de MediaWiki. No es un tutorial; justo te señalas a varios sitios donde te puede ir aprender cualquier cosa es necesaria.
 * Development discussion happens on various mailing lists and IRC channels. La lista principal de desarrolladores es wikitech-l. Los canales del desarrollador son #mediawiki y #wikimedia-dev.
 * Source code is managed using the Git revision control system.
 * Revisión de códigos es desarrollada en . Sigue este tutorial para instalar Git y Gerrit para enviar cambios.
 * Reportes de error y tareas son manejadas en Phabricator.

Instalando tu ambiente de desarrollo
La mayoría de los proyectos usan Git y Gerrit. Sigue el tutorial de Gerrit para crear tu cuenta de desarrollador. Then you can move on to downloading our code, making changes, testing them, and submitting patches. Hay dos maneras para instalar vuestro entorno de desarrollo: utilizando un pre-máquina virtual configurada setup (vagrant), o manual.

Máquina virtual con Vagrant

 * Instalación de Vagrant - Esto da un paso que instalará el servidor de MediaWiki con todos los requisitos dentro de una máquina virtual con Linux (puede ser utilizado en Linux, Windows, o Hosts de Mac)

Docker development environment

 * MediaWiki Docker – Run MediaWiki using Docker (can be used on Linux, Windows or macOS hosts).

Instalación manual

 * Requisitos de instalación — Compruebe los requisitos de hardware, e instalar un LAMP, MAMP o WAMP servidor (Linux, Mac o Windows, plus Apache, MySQL/MariaDB y PHP).


 * — Descarga el código de fuente más reciente desde Git.
 * — Continuar con la instalación y configuración inicial
 * Instalar varios modos de debug en vuestro entorno para mostrar advertencias y errores pronto.

No es necesario descargar vertederos de base de datos de Wikipedia para desarrollar las características de MediaWiki. De hecho, en muchos casos es más fácil de utilizar una cercana-base de datos vacía con unos cuantas páginas de pruebas especiales. Aun así, si para alguna razón quieres tener una copia de Wikipedia, puedes conseguir un vertedero.

Lectura sugerida




Comentarios, preguntas y asistencia
 
 * You are expected to do some basic research yourself first: Look at the code, try to get some understanding what it is supposed to do, read related documentation, try to find the probable place(s) where you need to make changes in order to fix the bug.
 * If you have general questions which are not tied to the specific task that you want to work on, use generic channels like Wikimedia Developer Support, IRC chat or mailing lists but not the specific task.
 * If you have a specific question about the bug itself, comment in the corresponding bug report (normally a task in ). "Can you give me more info how to fix this bug?" is not a good question to start with: The more specific your questions are, the more likely somebody can answer them quickly. If you have no idea at all how to fix the bug, maybe that bug is not (yet) for you - please consider finding an easier one first.
 * When asking, explain what you have tried and found out already, so others can help at the right level. Sé específico - por ejemplo, copia y pega tus comandos y su salida (si no es muy larga) en lugar de expresarlo con tus propias palabras. Esto evita malentendidos.
 * Do not ask if you can work on a task.
 * Avoid private email or support requests in our social media channels.
 * Sé paciente cuando busques aportes y comentarios. On IRC, don't ask to ask, just ask: most questions can be answered by other community members too if you ask on an IRC channel. If nobody answers, please ask on the bug report or wiki page related to the problem; don't just give up.

Comunicar que trabajas en una tarea
Do not ask if you can work on a task. You do not need to announce your plans before you start working on a bug, but it would be welcome. You are welcome to set yourself as the assignee in a task: Use the dropdown Add Action… → Assign/Claim in Phabricator. At the latest when you are close to proposing a patch for the task, it is good to announce in a comment that you are working on it. Your announcement helps others to not work on the bug at the same time and to not duplicate work.

Also note that if a task already has a recent link to a patch in Gerrit and has the project "Patch-For-Review" associated in Phabricator, choose a different task to work on instead - avoid duplicating work. If an existing patch in Gerrit has not been merged and has not seen any changes for a long time, you could also pick up that existing patch and improve it, based on the feedback in Gerrit and in the task.

If you stop working on a task, remove yourself as the assignee of the task, so others know that they can work on the task and don't expect you to still work on it.

By communicating early you will get more attention, feedback and help from community members. 

PHP
MediaWiki is written in PHP, so you'll need to get familiar with PHP to hack MediaWiki's core.


 * Aprende PHP
 * Tutorial de PHP — Disponible en muchos idiomas diferentes. If you have no knowledge of PHP but know how to program in other object-oriented programming languages, PHP will be easy for you to learn.
 * PHP Programming at Wikibooks.
 * PHP topic at Wikiversity.


 * Recursos de PHP:
 * El manual de de PHP — Disponible en muchos idiomas diferentes.
 * PHP coding conventions within the MediaWiki community.


 * Stuff to know:
 * The script  in MediaWiki provides a basic PHP interpreter with MediaWiki objects and classes loaded.
 * Also, the script  in MediaWiki is a replacement of   based on PsySH, see Manual:Shell.php.

Base de datos
Many features require some amount of database manipulation, so you'll often need to be familiar with MySQL/MariaDB.


 * Aprende MySQL/MariaDB
 * Tutorial de MySQL — Desde el manual de referencia de MySQL 5.0
 * MySQL at Wikibooks.


 * Recursos de MySQL/MariaDB
 * Manuales de referencia de MySQL — Disponible en muchos idiomas diferentes.
 * MariaDB Knowledge Base
 * Database coding conventions within the MediaWiki community.


 * Stuff to know:
 * Prueba tu código con MySQL/MariaDB.
 * MediaWiki currently uses MySQL and MariaDB as the primary database back-end. It also supports other DBMSes, such as PostgreSQL and SQLite. However, almost all developers use MySQL/MariaDB and don't test other DBs, which consequently break on a regular basis. You're therefore advised to use MySQL/MariaDB when testing patches, unless you're specifically trying to improve support for another DB. In the latter case, make sure you're careful not to break MySQL/MariaDB (or write queries that are horribly inefficient in it), since MySQL/MariaDB is what everybody else uses.

JavaScript y CSS
JavaScript and CSS have become omnipresent in front-end code. You don't have to be familiar with JavaScript, jQuery and CSS to work on MediaWiki, but you might need to, depending on what you choose to work on.


 * Aprende JavaScript y CSS
 * JavaScript and CSS at Wikibooks.
 * Comenzando con jQuery — Un tutorial de jQuery.
 * Learning JavaScript — references and sources.


 * Recursos de Javascript y CSS
 * JavaScript coding conventions within the MediaWiki community.
 * CSS coding conventions within the MediaWiki community.

MediaWiki
The MediaWiki code base is large and some parts are ugly; don't be overwhelmed by it. When you're first starting off, aim to write features or fix bugs which only touch a small region of code.


 * MediaWiki basics and must-reads:
 *  — A high-level overview of the main components of MediaWiki and how they work with each other.
 *  — An overview of why and how to write secure code.


 * MediaWiki resources:
 * — A list of important files and links to more detailed information.
 * — A list of hooks. If you're trying to find what part of the codebase does something, often a good place to start is by searching for the related hooks.
 * — An overview of general coding conventions within the MediaWiki community.


 * Code documentation (class reference) — Automatically generated documentation from the code and code comments.
 * — A guide to debugging MediaWiki.
 * — A tool to interact with MediaWiki objects live.

Extensiones MediaWiki
If you choose to work on MediaWiki extensions code, the following links provide more information.


 * MediaWiki extensions basics:
 * Developing extensions — How to write an extension for MediaWiki.
 * Extension writing tutorial


 * MediaWiki extensions resources:
 * Best practices for extensions
 * A brief introduction to MediaWiki extension development — A video presentation about how to create a MediaWiki extension (slides).
 * Making a MediaWiki extension — Covers how to develop an extension for MediaWiki, best practices, and how to engage the MediaWiki community. Desde febrero de 2011.
 * Help for extension developers on the Developer Hub

Véase también

 * Search for code across repositories
 * – When you've thoroughly read the information in this article, it's time to move on to the information in the developer hub.
 * – a collection of related pages