Anatoly, While I agree many of the things in your list would be nice to get done. I'm not sure most of them are a good thing for a GSOC student to attempt. Few students would have the time to ramp up on all the info needed and make some concrete contributions in the time allowed.
my 2cents. -Bill On Tue, Feb 11, 2014 at 12:35 PM, anatoly techtonik <[email protected]>wrote: > On Tue, Feb 11, 2014 at 11:30 PM, anatoly techtonik <[email protected]> > wrote: > > On Mon, Feb 3, 2014 at 10:05 PM, Gary Oberbrunner <[email protected]> > wrote: > >> Hi folks; if we want to get a GSoC project this year, now's the time to > >> think about it. > >> > >> Top of my priority list for a GSoC student would be someone to convert > >> everything to python3, finishing what we've started already. > > > > Can of worms. IMHO. > > > >> Other ideas? > > > > Concentrate on visualizing and documenting how SCons works. Cleaning > > up and opening internals to the public. Enhance test running, bring > > back slaves. List current workflows and tools discovery, research best > > practices and see how the tool discovery should be improved. > > > > Research and document the problem of compiling C programs. > > Research and document the problem of compiling C++ programs. > > Enhance documentation. > > Add more design touches. > > Integrate best practices from other projects. > > > > Fix async subprocess execution with proper handling of std* streams. > > Also integrate with https://github.com/facebook/watchman to speed up > rebuilds (instead of scanning the whole tree again and again). > > -- > anatoly t. > _______________________________________________ > Scons-dev mailing list > [email protected] > http://two.pairlist.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
