120
edits
(linkify) |
|||
Line 176: | Line 176: | ||
== Collaboration and teamwork == | == Collaboration and teamwork == | ||
=== Communication === | |||
Nearly all communication is handled through [bugzilla.mozilla.org Bugzilla]. All bugs, feature requests, issues, enhancements, etc, are all referred to as bugs. No code may enter the Mozilla repository without being a patch attached to a bugzilla bug first. To follow all SpiderMonkey related bugs (very high traffic, and very detailed): | |||
Go to [https://bugzilla.mozilla.org/userprefs.cgi?tab=email email preferences] | |||
Watch the user general@spidermonkey.bugs | |||
SpiderMonkey contributors generally hang out in the very active [irc://irc.mozilla.org/jsapi #jsapi IRC channel]. You might also find the [irc://irc.mozilla.org/static #static channel] (discussions about static analysis in Mozilla) interesting. | |||
The [https://developer.mozilla.org/en/SpiderMonkey#Community js-engine mailing list] is generally used for communicating with people who embed SpiderMonkey, such as asking questions and announcing API changes. No actual development happens on the list. | |||
The Mozilla platform team has a [https://wiki.mozilla.org/Platform#Meetings public weekly meeting] where SpiderMonkey progress is discussed. | |||
The [http://benjamin.smedbergs.us/weekly-updates.fcgi/ Mozilla Status Board] allows team members to give brief overviews of their recent work. At the moment, it is seldom used, but we are trying to encourage team members to post there. | |||
Some team members blog about SpiderMonkey, if somewhat infrequently: | |||
[http://www.bailopan.net/blog/ David Anderson] | |||
[http://blog.mozilla.com/rob-sayre/ Rob Sayre] | |||
[http://blog.mozilla.com/jorendorff Jason Orendorff] | |||
[http://blog.mozilla.com/dmandelin/ David Mandelin] | |||
[http://blog.mozilla.com/nnethercote/ Nicholas Nethercote] | |||
- Overview | - Overview | ||
Line 194: | Line 220: | ||
- fixed-in-tracemonkey | - fixed-in-tracemonkey | ||
- following what other team members are doing | - following what other team members are doing | ||
- patch policy | - patch policy | ||
- commit access | - commit access | ||
Line 201: | Line 226: | ||
- reviewers | - reviewers | ||
- mercurial queues | - mercurial queues | ||
- who are they, which faces in phonebook | - who are they, which faces in phonebook | ||
- who's in "charge" | - who's in "charge" | ||
- blogs and twitterers, etc | - blogs and twitterers, etc |
edits