How to become a MediaWiki hacker/ko

이 문서는 초보 개발자들이 미디어위키 개발에 기여할 수 있도록 도움을 주기 위해 작성한 글 입니다.

만약 당신이 이미 숙련된 개발자라면 개발자 허브 을 방문해주세요!

개요
미디어위키는 위키피디아를 지탱하는 자매 프로젝트로써, 전세계 수천개의 위키사이트에서 사용되는 소프트웨어입니다. PHP로 작성되었고, MySQL 데이터베이스를 사용하며, 클라이언트 자바스크립트 라이브러리로 jQuery를 사용하는 이 소프트웨어는 대부분의 운영체제에서 동작합니다. 보통 미디어위키는 자원봉사자들이 큰 역할을 하지만, 주로 위키미디어 재단에 의해서 후원됩니다.

이 문서는 미디어위키에 어떻게 기여할 수 있는지 알려드립니다. 단, 이 문서는 튜토리얼은 아니며, 필요한 것들이 어디에 있는지 알려드립니다.

PHP
미디어위키는 PHP로 작성되어 있습니다, 미디어위키를 낱낱히 파헤치기 위해선 PHP 에 익숙해질 필요가 있겠지요?


 * PHP를 배울 수 있는곳


 * PHP tutorial — 여러 언어로 가능. PHP에 대한 지식이 전무하지만 다른 객체지향 프로그래밍 언어를 배워보신 경험이 있다면 PHP도 어렵진 않을 껍니다.
 * PHP Programming - 영어판 위키책.


 * PHP 자료:
 * The PHP manual — Available in many different languages.
 * PHP coding conventions within the MediaWiki community.


 * Stuff to know:
 * The script maintenance/eval.php in MediaWiki provides a basic PHP interpreter with MediaWiki objects and classes loaded.

데이터베이스
Many features require some amount of database manipulation, so you'll often need to be familiar with MySQL.


 * MySQL 배우기
 * MySQL 튜토리얼 — MySQL 5.0 레퍼런스 메뉴얼 참조.
 * MySQL - 영어판 위키책.


 * MySQL 자료
 * MySQL Reference Manuals — Available in many different languages.
 * Database coding conventions within the MediaWiki community.


 * Stuff to know:
 * Test your code with MySQL.
 * MediaWiki currently uses MySQL as the primary database back-end. It also supports other DBMSes, such as PostgreSQL and SQLite. However, almost all developers use MySQL and don't test other DBs, which consequently break on a regular basis. You're therefore advised to use MySQL 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 (or write queries that are horribly inefficient in it), since that's what everybody else uses.

자바스크립트 및 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.


 * Learn JavaScript and CSS
 * JavaScript and CSS at Wikibooks.
 * Getting Started with jQuery — A jQuery tutorial.


 * JavaScript and CSS resources
 * JavaScript coding conventions within the MediaWiki community.
 * CSS coding conventions within the MediaWiki community.

미디어위키
The MediaWiki code base is large and ugly; don't be overwhelmed by it. When you're first starting off, aim to write features or fix bugs which are constrained to a small region of code.


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


 * MediaWiki resources:
 * Manual:Code — A list of important files and links to more detailed information.
 * Coding conventions — An overview of general coding conventions within the MediaWiki community.
 * Intro-to-MediaWiki workshop syllabus — Ways to hack MediaWiki, from user preferences to extensions and core.
 * Complete documentation (warning: huge page) — Automatically generated documentation from the code and code comments.
 * How to debug — A guide to debugging MediaWiki.
 * eval.php — A tool to interact with MediaWiki objects live.

Set up your environment

 * Installation requirements — Check hardware requirements, and install a LAMP, MAMP or WAMP server (Linux, Mac or Windows, plus Apache, MySQL and PHP).
 * Download from Git — Download the latest source code from Git.
 * Installation guide — Continue with the installation and initial configuration
 * Set up the various debug modes in your environment to display warning and errors early.

It's not necessary to download Wikipedia database dumps in order to develop MediaWiki features. In fact, in many cases it's easier to use a near-empty database with a few specially-crafted test pages. However, if for some reason you want to have a copy of Wikipedia, you can get a dump.

Get started
The two main paths to get started with MediaWiki development are to fix an annoying little bug in the existing code, or to add a new feature, usually through a MediaWiki extension.


 * MediaWiki extensions primers:
 * Developing extensions — How to write an extension for MediaWiki.
 * Writing an extension for deployment — If you intend to have your extension deployed on Wikimedia sites (including possibly Wikipedia), additional scrutiny is warranted in terms of performance and security.
 * Extension writing tutorial


 * MediaWiki extensions resources:
 * List of simple extensions — A simple way to become more familiar with how extensions work.
 * 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. From February 2011.
 * Special page template — Add a special page to display some handy information.
 * Extending wiki markup — Add a parser hook to modify the content of wikitext.

Submit your changes
There are two main avenues for submitting changes to MediaWiki. You can either submit patches through our bug tracking system, or you can get Developer access so you can submit changes to Gerrit, our code review tool. Getting developer access is easy.

Pushing for review through Gerrit

 * Get developer access if you do not already have it (we usually respond to requests within 24 hours).
 * Make your changes in a branch in Git (see Git/Workflow).
 * Check your code against the pre-commit checklist. Don't skip this step ; you'll be happy you didn't.
 * Submit your change to Gerrit (see Git/Workflow).
 * Post a link to your Gerrit changeset in the appropriate bug report in Bugzilla with, and mark it with the   and   keywords.
 * Feel free to ping the Bugmeister if you see that your patch hasn't been pushed for review. This can be a slower process than just pushing it yourself, but by doing it once or twice you demonstrate your good faith, and your ability to write reasonably stable code.
 * Ask for your code to be reviewed, watch for email updates, and make requested changes.

Submit a patch to bugzilla

 * Check your code changes against the pre-commit checklist. Don't skip this step ; you'll be happy you didn't.
 * Create a patch of your changes (you can use 'git diff' or 'svn diff' if you're making changes against the code repository; for help, take a look at OpenHatch's diff and patch training mission)
 * Attach your patch to a corresponding bug in Bugzilla - if one does not exist, go ahead and create it
 * Add the  and   keywords to the bug

Discuss and get help
MediaWiki has a very friendly, large and diverse community. There are multiple places to get help. If you already have an idea for a feature you want to implement, it's also a good idea to talk to a senior developer before you start, especially if you're not sure how your feature will affect other parts of the code.


 * IRC — Specifically, the channel. The MediaWiki developer community is distributed around the world, and there most likely is someone awake, no matter what your timezone is. Hop in and start talking.
 * Mailing Lists — Since you are looking to be a developer, wikitech-l is where you should be at. You can also browse through the archives to get a feel of how the community operates.