<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Phillip J. Eby wrote:
<blockquote
cite="mid:20080319152101.730BC3A40A5@sparrow.telecommunity.com"
type="cite">
<pre wrap="">At 03:57 AM 3/19/2008 -0500, Jeff Rush wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> I'd be willing to help out, and keep a carefully balanced hand in
what is accepted.
</pre>
</blockquote>
<pre wrap=""><!---->
I'm not sure exactly how to go about such a handoff though. My guess
is that we need a bug/patch tracker, and a few people to review,
test, and apply. Maybe a transitional period during which I just say
yea or nay and let others do the test and apply, before opening it up
entirely. That way, we can perhaps solidify a few principles that
I'd like to have stay in place. (Like no arbitrary post-install code hooks.)
</pre>
</blockquote>
<br>
+1 to blessing more people to commit.<br>
+1 to the transition period idea.<br>
<br>
These two ought to enable things to move a bit quicker than taking a
year to accept a patch. :-)<br>
<br>
In addition to a bug tracker and patch manager, seems like perhaps a
wiki to help document some of these solidified principles and other
notes would be a good thing. (Like a patch should almost always
include at least one test, possibly more.) Given that the source for
setuptools is in the python.org svn, couldn't we just use the
python.org roundup and wiki for these facilities? Though looking at
the list of components, it seems that things in the sandbox generally
aren't tracked in this infrastructure. In which case, I'm sure we
could use sf, launchpad, or some such external provider. Enthought
could even host this stuff.<br>
<br>
Like Jeff Rush, I'm also willing to help out as both a writer and
reviewer of patches. As you can see from my earlier posts there are a
number of things (besides running an arbitrary post-install script)
that we'd like to be able to get into the codebase.<br>
<br>
<br>
-- Dave<br>
</body>
</html>