Moving BFAV traffic off of squeak-dev short-term (was Re: BFAV
email prefix?)
Doug Way
dway at riskmetrics.com
Tue Aug 12 19:04:34 UTC 2003
I agree that we don't want to simply move all traffic to a separate
list... we need to keep the wider community informed of the more
important steps in the process, and also allow discussion of issues.
Andreas made many of the same points.
There are various ways this could be handled. I'm not even sure what
the best overall solution is... I guess we need to keep the discussion
going. :-)
To Daniel's wishlist I would add a point E.: It would also sometimes be
nice to (optionally) see the larger-issue mailing-list discussion on a
submission inside the BugFixArchiveViewer tool itself, to help get
context. This might be trickier, though.
Hmm, I suppose if Brent is truly on the verge of getting a Bug Fix
Archive server working, we may not need to use Bert's sqfixes archive on
a separate mailing list. But we still need to figure out which posts
will go to the squeak-harvest list versus squeak-dev...
- Doug
Daniel Vainsencher wrote:
>A few points:
>A. It is important to do more than keep the wider community informed. A
>large consideration is that we should make the process easy to join.
>Currently, the barriers are very low. You see everything happen in real
>time, just answer an email to participate. We should keep them as low as
>possible.
>B. While the news bot might do the trick (a good idea IMO), the ordering
>matters - move the traffic *after* the news bot is online.
>C. Sometimes an [ENH] or [FIX] actually stands for a larger issue, which
>should be discussed generally, not just as part of the harvest process.
>Being able to send it publically allows this to happen easily.
>D. The harvest list won't be as public as the squeak list unless we
>automatically enroll anyone that joins the squeak list into both.
>
>I agree completely that we're currently seeing too much of the traffic
>in squeak-dev, but there are reasons to do the scale-back gradually.
>
>Daniel
>
>
>
More information about the Squeak-dev
mailing list
|