Wiki Wednesday (Developing Mozilla) - September 14, 2011

[Sheppy]

Here are today's Wiki Wednesday articles! If you know about these
topics, please try to find a few minutes to look over these articles
that are marked as needing technical intervention and see if you can
fix them up. You can do so either by logging into the wiki and editing
the articles directly, or by emailing your notes, sample code, or
feedback to mdn...@mozilla.org.

Contributors to Wiki Wednesday will get recognition in next week's
Wiki Wednesday announcement. Thanks in advance for your help!

1) Creating a patch ( http://mzl.la/keGAaB )
2) Syntax ( http://mzl.la/mJI2ss )
3) Makefile - variables ( http://mzl.la/pOQWVF )

[Benoit Jacob]

2011/9/14 Sheppy <the.s...@gmail.com>:

> Here are today's Wiki Wednesday articles! If you know about these
> topics, please try to find a few minutes to look over these articles
> that are marked as needing technical intervention and see if you can
> fix them up. You can do so either by logging into the wiki and editing
> the articles directly, or by emailing your notes, sample code, or
> feedback to mdn...@mozilla.org.
>
> Contributors to Wiki Wednesday will get recognition in next week's
> Wiki Wednesday announcement. Thanks in advance for your help!
>
> 1) Creating a patch ( http://mzl.la/keGAaB )

Wow, thanks a lot for doing that. I had been wondering how to improve
community involvement in coding and this is exactly what I thought was
needed.

Can I hijack this thread to ask a few related questions:
- what is the current good way of marking a bug as a "good first
bug"? I heard that good-first-bug was deprecated. I also heard about
"mentor=$NAME" in the Status Whiteboard, is there any wiki page about
that?
- more generally is there a wiki page for general resources for
helping new / prospective contributors in coding? Ideally it would
link to your wiki pages like "Creating a patch" and answer my
questions.
- I'm about to start a set of wiki pages for getting involved in
Graphics/WebGL platform development. My basic idea is that Mozilla can
be hard to join as it's very big, but by isolating a small subset
like "Graphics" one can give it a more approachable "small project"
feel. Is there already any ongoing documentation/engagement project
that this would be redundant with or that I should know about before
proceeding? Has that been done already elsewhere in Mozilla?

Thanks,
Benoit

> 2) Syntax ( http://mzl.la/mJI2ss )
> 3) Makefile - variables ( http://mzl.la/pOQWVF )

> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>

[Joshua Matthews]

On 11-09-14 7:36 PM, Benoit Jacob wrote:
> 2011/9/14 Sheppy<the.s...@gmail.com>:
>> Here are today's Wiki Wednesday articles! If you know about these
>> topics, please try to find a few minutes to look over these articles
>> that are marked as needing technical intervention and see if you can
>> fix them up. You can do so either by logging into the wiki and editing
>> the articles directly, or by emailing your notes, sample code, or
>> feedback to mdn...@mozilla.org.
>>
>> Contributors to Wiki Wednesday will get recognition in next week's
>> Wiki Wednesday announcement. Thanks in advance for your help!
>>
>> 1) Creating a patch ( http://mzl.la/keGAaB )
>
> Wow, thanks a lot for doing that. I had been wondering how to improve
> community involvement in coding and this is exactly what I thought was
> needed.
>
> Can I hijack this thread to ask a few related questions:
> - what is the current good way of marking a bug as a "good first
> bug"? I heard that good-first-bug was deprecated. I also heard about
> "mentor=$NAME" in the Status Whiteboard, is there any wiki page about
> that?

As the coding contributor engagement lead, I tell people to use
[mentor=bugzilla_id] which is the friendliest and most informative
annotation. I still add [good first bug] markings, but I'm probably
going to stop doing that soon.

> - more generally is there a wiki page for general resources for
> helping new / prospective contributors in coding? Ideally it would
> link to your wiki pages like "Creating a patch" and answer my
> questions.

https://developer.mozilla.org/en/Introduction

> - I'm about to start a set of wiki pages for getting involved in
> Graphics/WebGL platform development. My basic idea is that Mozilla can
> be hard to join as it's very big, but by isolating a small subset
> like "Graphics" one can give it a more approachable "small project"
> feel. Is there already any ongoing documentation/engagement project
> that this would be redundant with or that I should know about before
> proceeding? Has that been done already elsewhere in Mozilla?

Paul Biggar put together a New to Spidermonkey guide
(https://wiki.mozilla.org/JavaScript:New_to_SpiderMonkey) which looks
pretty fabulous, but apart from the general Introduction that I linked
above, the onus is on enterprising people like yourselves. I very much
appreciate this work; it makes it easier for me to give new contributors
better direction if they express interest in a component with a good
introductory guide.

[passfree]

On Sep 15, 12:36 am, Benoit Jacob <jacob.benoi...@gmail.com> wrote:
> 2011/9/14 Sheppy <the.she...@gmail.com>:

>
> > Here are today's Wiki Wednesday articles! If you know about these
> > topics, please try to find a few minutes to look over these articles
> > that are marked as needing technical intervention and see if you can
> > fix them up. You can do so either by logging into the wiki and editing
> > the articles directly, or by emailing your notes, sample code, or

> > feedback to mdnw...@mozilla.org.

> > dev-platf...@lists.mozilla.org
> >https://lists.mozilla.org/listinfo/dev-platform

More importantly, it will be very beneficial to have a Wiki page
explaining in simple terms how to work with the source tree, tips and
tricks how to speed compilation, how to test your patches, etc, etc.
The biggest hurdle is the massive source tree which could be very
intimidating for beginners.