Webdev/MDN/GetInvolved: Difference between revisions
Groovecoder (talk | contribs) |
Groovecoder (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= Welcome = | |||
Glad you're interested in helping with MDN. [https://developer.mozilla.org Mozilla Developer Network] empowers developers to build a better web that servers the greater good. To that end, the MDN community provides documentation, technology demos, and promotes developer resources and events. As Mozilla's primary developer engagement site, our work is critical - advocating for open web technologies to fellow developers who drive the direction of the Internet.<br> | |||
As you get involved, please reach out to us with any questions: | |||
=== | == IRC == | ||
We're in #mdn on irc.mozilla.org. Check with groovecoder and lorchard about how to get started. Just send a groovecoder: or lorchard: message and we should see get a notification even if we're not immediately available. Or you can email us ... | |||
== | == email == | ||
If you're more comfortable with email, you can email lcrouch at mozilla dot com or lorchard at mozilla dot com. We get lots of mail but we'll try to respond quickly. | |||
= | = Why MDN? = | ||
[[Category: | Mozilla has [https://wiki.mozilla.org/Websites hundreds of websites]. Here's why you want to work on MDN: | ||
* You'll develop the website for a high-profile web company promoting open web development. That's like web development^3 in here. | |||
* Cred - you'll show up on our [https://developer.mozilla.org/humans.txt humans.txt] file! | |||
* (Possibly) swag - we're hooked up with the development engagement team and they often give out shirts, stickers, bags, sometimes even an android phone! | |||
= How to contribute = | |||
There are a few ways to contribute to MDN: | |||
*Code | |||
*Localization | |||
*MDN Documentation | |||
*Demos | |||
== Code == | |||
We always like to see more coders around! MDN code is something of a hodge-podge - we run an instance of MindTouch to power the documentation wiki alongside a django site very close to, but not derived from, the standard Mozilla [https://github.com/mozilla/playdoh/ playdoh] project. So our technology stack is primarily python, django, html, javascript, and css. | |||
It's best to contribute to the django code. Our repository is [https://github.com/mozilla/kuma kuma on github]. (Kuma means "bear" in Japanese; we chose it because our codebase is cloned from the [https://support.mozilla.com SUMO] site, which is code-named Kitsune - "fox". The implication is that SUMO's users are like foxes, while our users are more like bears.) Please make a fork, and then either do a local installation, or use a ready-made virtual machine as described below. | |||
Then the best way to get involved is to check our MDN mentored bugs list for anything that appeals to you. These are bugs from the current [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=mdn_sprint&sharer_id=403306 mdn sprint] or from our general product backlog that make for good entry-level bugs. | |||
=== Local Installation === | |||
Follow the [https://github.com/mozilla/kuma/blob/master/docs/installation.rst installation instructions] in the docs folder. We try to keep them updated, but if you run into issues, ping us on irc or email so we can help fix them. Debugging installation issues is also a simple way to work thru our development process for the first time. (see below) | |||
=== Virtual Machine === | |||
=== Our Development Process === | |||
The MDN team uses a type of Agile/Scrum development process. We run 3-week "sprints" with overlapping dev/QA time so we can push code every 2 weeks. Each sprint is a milestone in [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Developer%20Network our bugzilla product] - e.g., [http://mzl.la/mdn_11 MDN 1.1], [http://mzl.la/nUhfpK MDN 1.2], [http://mzl.la/n3mrVe MDN 1.3], etc. | |||
== Localization == | |||
== MDN Documentation == | |||
== Demos == | |||
[[Category:New_Contributor_Landing_Page]] | |||
Revision as of 22:51, 15 October 2011
Welcome
Glad you're interested in helping with MDN. Mozilla Developer Network empowers developers to build a better web that servers the greater good. To that end, the MDN community provides documentation, technology demos, and promotes developer resources and events. As Mozilla's primary developer engagement site, our work is critical - advocating for open web technologies to fellow developers who drive the direction of the Internet.
As you get involved, please reach out to us with any questions:
IRC
We're in #mdn on irc.mozilla.org. Check with groovecoder and lorchard about how to get started. Just send a groovecoder: or lorchard: message and we should see get a notification even if we're not immediately available. Or you can email us ...
If you're more comfortable with email, you can email lcrouch at mozilla dot com or lorchard at mozilla dot com. We get lots of mail but we'll try to respond quickly.
Why MDN?
Mozilla has hundreds of websites. Here's why you want to work on MDN:
- You'll develop the website for a high-profile web company promoting open web development. That's like web development^3 in here.
- Cred - you'll show up on our humans.txt file!
- (Possibly) swag - we're hooked up with the development engagement team and they often give out shirts, stickers, bags, sometimes even an android phone!
How to contribute
There are a few ways to contribute to MDN:
- Code
- Localization
- MDN Documentation
- Demos
Code
We always like to see more coders around! MDN code is something of a hodge-podge - we run an instance of MindTouch to power the documentation wiki alongside a django site very close to, but not derived from, the standard Mozilla playdoh project. So our technology stack is primarily python, django, html, javascript, and css.
It's best to contribute to the django code. Our repository is kuma on github. (Kuma means "bear" in Japanese; we chose it because our codebase is cloned from the SUMO site, which is code-named Kitsune - "fox". The implication is that SUMO's users are like foxes, while our users are more like bears.) Please make a fork, and then either do a local installation, or use a ready-made virtual machine as described below.
Then the best way to get involved is to check our MDN mentored bugs list for anything that appeals to you. These are bugs from the current mdn sprint or from our general product backlog that make for good entry-level bugs.
Local Installation
Follow the installation instructions in the docs folder. We try to keep them updated, but if you run into issues, ping us on irc or email so we can help fix them. Debugging installation issues is also a simple way to work thru our development process for the first time. (see below)
Virtual Machine
Our Development Process
The MDN team uses a type of Agile/Scrum development process. We run 3-week "sprints" with overlapping dev/QA time so we can push code every 2 weeks. Each sprint is a milestone in our bugzilla product - e.g., MDN 1.1, MDN 1.2, MDN 1.3, etc.