JavaScript:New to SpiderMonkey: Difference between revisions
Jump to navigation
Jump to search
(Add skeleton) |
m (How do you follow new bugs (thanks Luke)) |
||
| Line 24: | Line 24: | ||
- following what other team members are doing | - following what other team members are doing | ||
- status page | - status page | ||
- Get alerted to new bugs: From bugzilla, go to your preferences, then click "Email Preferences" then, near the bottom, follow the user "general@spidermonkey.bugs" | |||
- patch policy | - patch policy | ||
- commit access | - commit access | ||
| Line 31: | Line 32: | ||
- irc | - irc | ||
- mailing list | - mailing list | ||
== Community == | == Community == | ||
Revision as of 22:25, 24 July 2010
This is a page to help new member of the JS team or new contributors to SpiderMonkey to orient themselves to the codebase. It's maintained by Paul Biggar (pbiggar@mozilla.com), who is currently new to SpiderMonkey. Please help by telling me what you found useful when you were new.
Code
- Overview - repository - sharing - hgrc file - useful plugins - jaeger + trace + integration - Tests - benchmarks - build a shell - coding style - ignore old doc - link to recent doc - important compilers and platforms
Workflow
- bugzilla - fixed-in-tracemonkey - following what other team members are doing - status page - Get alerted to new bugs: From bugzilla, go to your preferences, then click "Email Preferences" then, near the bottom, follow the user "general@spidermonkey.bugs" - patch policy - commit access - checkin needed - reviewers - mercurial queues - irc - mailing list
Community
team
- who are they, which faces in phonebook - who's in "charge" - blogs and twitterers, etc
users
- firefox is most important - other users - exposed APIs