My experience looking for similar things for Seneca would recommend: - relatively isolated subsystem: they should have to internalize less than 1KLOC - multiple meaningful milestones - good existing test coverage - few/no spec loose ends
On Wednesday, September 17, 2014, Till Schneidereit < [email protected]> wrote: > On Wed, Sep 17, 2014 at 3:36 PM, Bobby Holley <[email protected] > <javascript:;>> wrote: > > > > My spidey senses tell me that both of those projects are an order of > > magnitude too large for the demographic that jimb describes, especially > > given that they'll be SM/Gecko neophytes. > > > > I might have the wrong idea about the demographic, then. At least for the > first project. But yeah, the neophytes thing is a problem. > > So I guess the question is what would be the right size for a project. Do > they get credit for essentially fixing any Good First Bug, or does it have > to be a project of some substance? > _______________________________________________ > dev-tech-js-engine-internals mailing list > [email protected] <javascript:;> > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
