Whenever I'm thinking about a clever solution for a problem that I don't quite have yet, I go back to this page and meditate:<div><br></div><div><a href="http://c2.com/xp/YouArentGonnaNeedIt.html">http://c2.com/xp/YouArentGonnaNeedIt.html</a><br>
<br><div class="gmail_quote">On Mon, Aug 24, 2009 at 1:03 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2009/8/24 Ken Causey <<a href="mailto:ken@kencausey.com">ken@kencausey.com</a>>:<br>
<div><div></div><div class="h5">> +1<br>
><br>
> On Mon, 2009-08-24 at 00:07 +0200, Bert Freudenberg wrote:<br>
>> On 23.08.2009, at 23:51, Michael van der Gulik wrote:<br>
>><br>
>> > Hi all.<br>
>> ><br>
>> > Would it perhaps be better to have the automated trunk commit<br>
>> > messages going to some other dedicated mailing list?<br>
>> ><br>
>> > Gulik.<br>
>><br>
>><br>
>> I was curious how long it would take the first one to speak up :)<br>
>><br>
>> No, I would rather create a squeak-users list for those not interested<br>
>> in developing Squeak itself, but just "with" Squeak. IMHO the commits<br>
>> messages make the community development process visible, which is a<br>
>> Good Thing.<br>
>><br>
>> - Bert -<br>
><br>
> If we have to do anything about this then I think it is time we<br>
> seriously consider a separate "squeak users" mailing list. I would<br>
> rather that users have to consider going from 'developer' to 'user'<br>
> rather than from 'user' to 'developer'; by which I mean that I would<br>
> prefer that we change the definition of squeak-dev and make another list<br>
> the 'user' list, rather than create a new developer list. Perhaps we<br>
> should consider renaming the beginners list 'squeak-users' or the like.<br>
> This would have the added benefit of bringing more eyes to bear on<br>
> beginners requests.<br>
><br>
<br>
</div></div>+1<br>
a list name - "squeak-dev" speaks for itself.<br>
I can understand that some of list readers never contributed to<br>
squeak, or contributed occasionally, and mainly staying with it to be<br>
in touch with latest & hottest news and discussions around squeak. But<br>
let's not forget the main purpose of the list.<br>
<br>
Do trunk commits increasing mail traffic? Absolutely.<br>
Can they be easily filtered by users who reading the list? Absolutely.<br>
So, where is the problem?<br>
<br>
Do such commits increasing the process visibility and giving everyone<br>
a chance to evaluate and examine the changes as soon as they become<br>
available? Yes.<br>
So, given that this improves the development process (even by a bit) i<br>
think it overweights any inconveniences, such as increase in mail<br>
traffic, and everyone who understands that our main "employment" in<br>
squeak-dev list should be a development of Squeak, also should only<br>
wellcome such move :)<br>
<br>
<br>
> Ken<br>
><br>
<font color="#888888"><br>
<br>
<br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
<br>
</font></blockquote></div><br></div>