Would it make sense to add a "low hanging fruilt" section to dev/TODO and put these in it
or else put each of these in https://gitlab.com/NTPsec/ntpsec/issues with an issue weight of "2", designating 2 as "low hanging fruit". ..m On Mon, Jan 25, 2016 at 7:27 PM Eric S. Raymond <[email protected]> wrote: > Mark Atwood <[email protected]>: > > I leave it to each of your judgement and coordination, Eric and Hal. I > am > > not technically qualified to assign them. :) > > OK, I'll take that as "both", then. Hal, would you look over the > Classic fixes for the stuff on the list (2845 2882 2772 2948 2939 2935 > 2937 2814 2829 2887 2958 2962) and pick five or six you think > you can do easily? Then I'll triage the rest and post a non-overlapping > list. Any hard ones we can defer to a second pass > > (Now I'm trying to think forward to expanding our developer pool.) > > Mark, if we've got any n00bs you want to start training, I think > almost all of these fix transplants are in the not-hard category. The > main difference is that a n00b would do this sort of thing more slowly > and with effort, as opposed to blowing through it as rapidly as Hal or > myself. But since none of these are super-urgent and they're > bite-sized tasks, that's an opportunity. > > Susan, do you have any New Guard people you think might be ready to write > C systems code in ... hm, not the deep end, but not the kiddie pool > either. :-) > -- > <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> >
_______________________________________________ devel mailing list [email protected] http://lists.ntpsec.org/mailman/listinfo/devel
