On Wed, Mar 31, 2010 at 05:41:47PM +0900, Stephen J. Turnbull wrote: > anatoly techtonik writes: > > > I would vote for allowing student work on community infrastructure > > tasks. Tracker, Wiki, Web site management tools are all outdated and > > everybody who cares agrees that they've seen a better tools.
[ munch ] > I would recommend changing the tools only if *current* maintainers are > either planning to step down (and so we face the problem of how to > support maintenance in the future in any case), or are willing to > supervise (ie, the people who will come back and fix problems in the > future find the proposed "improvements" to be real improvements). Eg, > MvL should be intimately involved in any move to use different > software for the tracker. If the GSoC student(s) is (are) willing to > work within the constraints of the existing software (ie, incremental > improvements), then the constraints on mentors could be substantially > relaxed to any of the senior folks who have recently contributed in > those areas. Agreed. It'd be great to have students work on prototyping improvements, with an eye to making changes that can then be evaluated in terms of maintainability, extensibility, etc. Having them actually change the infrastructure itself seems to me like a bad idea :) --titus -- C. Titus Brown, c...@msu.edu _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
