Now that I should be able to actually keep up with my summary duties, I need to figure out how to tackle the changing landscape of the development lists. The old summaries were no problem, before my time. When the python-3000 list was created, nearly everything was just conceptual, floaty talk that didn't have place in the concrete world of real development conversation in python-dev. The day recently came when python-3000 got to the point of being "real" enough to warrant a third list, python-ideas, for real floaty ideas and now conversations routinely cross all three. Something might be brought up in ideas, move to 3000 to be solidified, and then to dev to discuss backporting to 2.6 or so. Obviously, we're missing out on a lot for the summaries.
So, the question I pose is how would everyone like to see this resolved? As I see it, there are two things I can do. I can either summaries each list separately, and try to sort out the cross overs. Or, I can start pulling in all three development lists into all the summaries. I prefer the second option, but I want to clear with everyone else. I hope no one has a problem with getting more with the summaries from now on? If not, I'll begin with the second half of April.
Along with that, I need to know if my svn rights for submitting the summaries extends to the actual summary scripts? I'll need to change them to pull in extra lists. I'm actually thinking lots of projects could use such a script, so while I'm at it I want to just generalize it a bit and put it somewhere for anyone else to use, if no one has issues with that.
On Tue, Apr 24, 2007 at 04:37:14PM -0400, Calvin Spealman wrote:
So, the question I pose is how would everyone like to see this resolved? As I see it, there are two things I can do. I can either summaries each list separately, and try to sort out the cross overs. Or, I can start pulling in all three development lists into all the summaries. I prefer the second option
I prefer the second, too.
Oleg.
On 4/24/07, Calvin Spealman ironfroggy@gmail.com wrote:
So, the question I pose is how would everyone like to see this resolved? As I see it, there are two things I can do. I can either summaries each list separately, and try to sort out the cross overs. Or, I can start pulling in all three development lists into all the summaries.
I think putting all three into the same summaries is fine.
Along with that, I need to know if my svn rights for submitting the summaries extends to the actual summary scripts?
Feel free to modify those as you see fit -- they were really just my scripts, so I'd be amazed if changing them bothered anyone else. If you think you can make them more generally useful, that'd be great.
STeVe
On 4/24/07, Calvin Spealman ironfroggy@gmail.com wrote:
Now that I should be able to actually keep up with my summary duties, I need to figure out how to tackle the changing landscape of the development lists. The old summaries were no problem, before my time. When the python-3000 list was created, nearly everything was just conceptual, floaty talk that didn't have place in the concrete world of real development conversation in python-dev. The day recently came when python-3000 got to the point of being "real" enough to warrant a third list, python-ideas, for real floaty ideas and now conversations routinely cross all three. Something might be brought up in ideas, move to 3000 to be solidified, and then to dev to discuss backporting to 2.6 or so. Obviously, we're missing out on a lot for the summaries.
So, the question I pose is how would everyone like to see this resolved? As I see it, there are two things I can do. I can either summaries each list separately, and try to sort out the cross overs. Or, I can start pulling in all three development lists into all the summaries. I prefer the second option, but I want to clear with everyone else. I hope no one has a problem with getting more with the summaries from now on? If not, I'll begin with the second half of April.
All in one is fine. Just be *very* wary of getting burned out. I especially would watch out for python-ideas as any random idea can end up there and just go on and on with no resolution. I think only worrying about python-dev is fine, and if you want to pull in python-3000 that's great. But I personally consider python-ideas too wild to worry about summarizing.
-Brett
Brett Cannon writes:
All in one is fine. Just be *very* wary of getting burned out. I especially would watch out for python-ideas as any random idea can end up there and just go on and on with no resolution.
As basically a lurker, I second that -- these summaries (and the weekly tracker summary) are great, and anything that keeps the volunteers happy and healthy is really important.
Similarly, as an irregular reader, I would prefer all-in-one to the extent that you do summarize more than one list.
However, it would be nice if the thread summaries included a list of thread subjects occurring on any lists that don't get a verbose summary. For example, something automatic based on Subject header would be fine, any extra checking for topic changes that don't get a subject change or subject changes that don't correspond to a thread break is above and beyond the call of the volunteer spirit. Oh, and as part of the boilerplate call for comments on the summaries, suggest that people who care about a particular thread that isn't represented due to topic-Subject skew to suggest an entry for it (one line maximum).
-
Brett Cannon -
Calvin Spealman -
Oleg Broytmann -
Stephen J. Turnbull -
Steven Bethard