JavaScript:New to SpiderMonkey: Difference between revisions

Jump to navigation Jump to search
Reorder according to information content.
(linkify)
(Reorder according to information content.)
Line 178: Line 178:




=== Communication ===
=== Communication (in descending order of information content) ===


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):
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:


  Go to [https://bugzilla.mozilla.org/userprefs.cgi?tab=email email preferences]
  Go to [https://bugzilla.mozilla.org/userprefs.cgi?tab=email email preferences]
Line 187: Line 187:
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.
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.
Some team members blog about SpiderMonkey, though infrequently:
 
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://www.bailopan.net/blog/ David Anderson]
Line 201: Line 195:
  [http://blog.mozilla.com/nnethercote/ Nicholas Nethercote]
  [http://blog.mozilla.com/nnethercote/ Nicholas Nethercote]


The Mozilla platform team has a [https://wiki.mozilla.org/Platform#Meetings public weekly meeting] where SpiderMonkey progress is discussed.
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 [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.




120

edits

Navigation menu