Right now people googling "Squeak" or going to
squeak.org continue see the "Squeak 3.10 now released!" headline from The Weekly Squeak. A single simple blog post entitled "Squeak 3.10 release delayed" would prevent people from having the not-so-good experience - in effect stop the bleeding.
Since The Weekly Squeak is a Wordpress blog, establishing multiple authors with different roles/capabilities is a breeze. A board representative can make "official" announcements when necessary that will show up both on the blog and
squeak.org.
Perhaps Qwaq would consider providing a forum for the board and team leaders to facilitate more effective interaction. Voice/video sessions with a shared web browser should prove to be valuable tools for enhancing the communication process. It might also be a way to bring together leadership from the various Squeak-based communities.
Laurence
On Sat, Apr 5, 2008 at 3:28 AM, Randal L. Schwartz <
[hidden email]> wrote:
>>>>> "Dan" == Dan Ingalls <[hidden email]> writes:
Dan> I have to agree with Andreas here. Any board worth its salt should
Dan> consider itself to have a pretty wide scope, and it should feel pain
Dan> whenever something is not working right. It may not be able to fix the
Dan> problem directly, but it ought to be trying to understand it, and working
Dan> with doers to fix it, to work around it, or to chart another better path.
I too agree here. I think it's the job of the board to be accountable for the
overall vision of Squeak. I'd rather the board get out of the way when things
are already working, but if it's clear that things aren't working and some
decisions need to be made, I'll be personally motivated to make sure that
those shortcomings are on the board's agenda.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[hidden email]> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Locked
