Voting is now under way in this year’s elections for the Squeak Oversight Board.

After some prompting from their colleagues, the following people have thrown their hats into the ring:

If you are one of the 460 registered members of the Squeak community you should have received an email “Poll: Squeak Oversight Board Election 2011” sent by Göran Krampe, who is running the election. If you’ve not got an email and you should have, email and Göran will see what he can do.

Find out more at the election wiki page.

Voting closes on 10th April at 18.00 UTC.

An Election Entertainment - Hogarth

Göran Krampe has begun the process for this year’s elections for the Squeak Oversight Board.
The Squeak Oversight Board (SOB) consists of seven members from our community, all of whom are elected by popular vote. The members are responsible for

  • building a legal presence – currently by working with the Software Freedom Law Center as part of their Conservancy;
  • providing the network services that support the various mailing lists and repositories that in turn make a community possible;
  • helping coordinate the various interest groups and projects being pursued by Squeakers;
  • making decisions where there is no clear community consensus.

The current board members are:

  • Jecel Assumpcao Jr
  • Ken Causey
  • Bert Freudenberg
  • Craig Latta
  • Andreas Raab
  • Randal Schwartz
  • Igor Stasenko


The schedule and process of the Election is as follows:


Candidates should nominate themselves by 3rd March and start their campaign on the squeak-dev mailing list. Or if you nominate someone else, make sure that person really wants to run. Göran will not put anyone on the candidate list until that person makes it known on squeak-dev that he/she does run.

Final candidate list

The list will be closed on 3rd March. The candidates should ideally present themselves on squeak-dev, unless they have already done so, and the community can ask questions.

Online election starts

The voting period starts on 10th March 6PM (18.00 UTC) and is one week long. Ballots are sent out via email.

Online election ends

The voting process will end on 17th March 6PM (18.00 UTC). Results will be announced immediately when the election ends.


If you were invited to vote last year you are already on the voter list, no worries! If you are a new Squeaker and wish vote do ONE of the following:

  • Get a “known” Squeaker to vouch for you. If a known Squeaker sends an email to giving your name and email address then Göran will add you.
  • Send an email to yourself (and CC to squeak-dev if you like) with information/arguments showing that you are indeed serious about voting and that you are indeed a Squeaker.

When the voting period starts all voters will receive an email with instructions and a link to the voting website.

More information

Everything about the election, including schedule above and more, can be tracked here:

It has been two months since the Squeak Oversight Board first put forward their “New Community Development Model”. At the time the proposal caused a lot of heated debate on the squeak-dev mailing list, with concerns being expressed that similar efforts in the past had had little lasting impact, and had caused great frustration for those pushing those earlier efforts.

The motives of the Board were to “get rid of as many hurdles as possible in the contribution process [and]  to enable the community at large to improve Squeak, the core of the system and its supporting libraries”.

So, two months down the line, how’s it doing?

If sheer volume is any criterion, it looks like a great success with over 500 packages uploaded as patches to 3.10.2 and over 40,000 downloads from the trunk (see bottom of the linked page for up to date statistics).

The results of all this activity are available to use and test in the daily updated image published at (needs a recent VM). If you want to contribute, you can add new patches at, or ask one of the current developers for access to the developers repository at

If you just want to get an idea of what’s going on, check out the commit logs that are getting posted to the squeak-dev mailing list, and to the #squeak irc channel on freenode.


Those of you who read the squeak-dev mailing list will know that the list is currently going through the annual frenzy of discussion about the nature and direction of Squeak, including much to-and-fro over such topics as: the original vision of the founders of Squeak; the tangled relationship between Etoys and the rest of the Squeak environment and community; the reasons behind the Pharo project and how much its goals really differ from those of Squeak; whether children should be locked in the nursery or allowed to roam freely into every room of the house; and much more. If you have time (and some light body armour), it’s well worth reading through the hundreds of emails that have been written which explore and interpret much of the history and philosophy of Squeak.

This discussion has motivated the Squeak Oversight Board to look at one topic that caused much debate: how to manage the development of Squeak. Driven by a concern that there are many hurdles that discourage wide-spread participation in the contribution process, the Board have put forward a new community development model that they hope will “enable the community at large to improve Squeak, the core of the system and its supporting libraries”.

Based on processes that have been shown to work in commercial settings, the Board’s model includes the use of Monticello as the primary source code management system, free access for the developers to the main repositories (trunk, tests, and inbox) and an incremental update process for both developers and users of Squeak.

Obviously, such a change has sparked off its own debate, and important questions are being hammered out on the squeak dev mailing list. If you care about the health of the Squeak environment, its future direction, and the future support for your own favourite applications, this is a key moment for you to understand and contribute to the discussion which is continuing on the squeak-dev mailing list (see archives), on irc, and on the Board’s blog.

As a result of ongoing discussions with the Software Freedom Conservancy, the Squeak Leadership team have now adopted the formal name of the “Squeak Oversight Board”. The members of the new team have made clear and open communications one of their priorities, and to that end, have started up a new blog at, where they will be publishing agendas and minutes of their monthly meetings.

In keeping with their mission statement of “Communicating with the Squeak and greater Dynamic Languages Community”, the board will also be using the blog to encourage discussion about the direction and priorities of the Squeak community.

And yes, the board members are fully aware of the double meaning of “oversight”.