One of Mozilla's 2014 goals is to "Increase active contributors to
Mozilla’s target initiatives by 10x". [1] I'm not sure where the 10x
number comes from, but the intention is clear. SpiderMonkey is probably
not the ideal component for new contributors to start hacking on Gecko,
but there are exceptions and we can suggest good second bugs to keep
current contributors active.
Mentored bugs and "good first bugs" are the on-ramp for new
contributors. Many new contributors find bugs through Josh Matthew's
Bugs Ahoy [2] search engine. Unfortunately, Bugs Ahoy only searched one
of SpiderMonkey's five Bugzilla components. I submitted a pull request
[3] to fix this.
* The following bugs have [good first bug] have no [mentor=]. We should
always have a mentor contact for good first bugs. Any volunteers? :)
689368 - Investigate potential LifoAlloc performance improvements
513363 - Improve n-way string concat (when elements are not strings)
* The following bugs are have [mentor=] but not [good first bugs]. Are
any of them good first bugs? Are these bugs still relevant?
583083 Let the eval "//# sourceURL=..." trick work for stack traces
715181 Self-host Array.sort
852187 Optimize postMessage for large strings
894092 IonMonkey: clean-up: Remove VMFunction copy constructor.
905210 VMFunctions setup for JIT generates large static initializers
920484 Intl prototype initialisation requires empty object
950612 Warn about inefficient register-allocation for CallWithABI
952650 Kill jsval and all methods like JSVAL_IS_* and JSVAL_TO_*
956299 IonMonkey: Clean-up: Abstract trivial callVM codegen.
970865 Use GetTempRegForIntArg instead of CallTempReg* for passABIArg
974525 IonMonkey: ARM: Try optimizing ma_mod_mask by avoiding branches
976110 IonMonkey: Optimize integer divide by constant
977966 Optimize String#split('foo').join('bar') pattern
989348 BaselineCompiler: Optimize JSOP_ARRAYPUSH
995278 JS_NewArrayBufferContents frees user data on error
997274 Value.h should use NUNBOX32/PUNBOX64 instead of JS_BITS_PER_WORD
998485 Replace EdgeCaseAnalysis with RangeAnalysis
* Do you know of any other bugs (in Bugzilla or in your head) that could
be mentored? Are any of those good first or second bugs?
chris
[1]
https://intranet.mozilla.org/2014Goals#Enable_Communities_that_have_Impact_.7C_Accountable:_Debbie_Cohen_.2B_Mark_Surman
[2] http://www.joshmatthews.net/bugsahoy/?jseng=1
[3]
https://github.com/jdm/bugsahoy/commit/069ec54516988b749318a6fc3e4e9615ab64f48e
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
