Ok, now you have:
The next step is to get a grip on how the community is organised.
The Squeak community has undergone some changes over the years. First it was centrally controlled, then it was loosely managed with a group called the Guides trying to "guide" the way, and now for the last year a stronger leadership has formed but we are constantly refining our organisation in the long term. The current group leading the community is called the Squeak Oversight Board.
The SqF board is leading the Squeak community mainly through coordinating targeted teams. We have an established Team model and every team has a team leader and a mailinglist to coordinate the team. Anyone can join a team, but the leader is undisputed king. Each team also has a member of the board assigned as coordinator who basically tracks the team and bugs the leader for progress reports etc. Anyone in the Squeak community can step forward and propose a team and take on the role of being team leader but the board will in the end decide if the team gets a green light to be an official team.
The SqF board regularly posts reports on what is happening in the community and if you read those you should be able to keep up with the more important things that are going on. Another important mechanism that the board handles is the list of contact persons for the so called "stakeholder communities".
A stakeholder community is another project/community that heavily depends on Squeak, typically by using it as the basis for other work. The SqF board communicates with those contact persons in order to make sure the evolution of Squeak does not unnecessarily conflict with the needs and expectations of the stakeholders.
This was a brief description of how the community works and is organised. Feel free to ask questions on squeak-dev and help us evolve these pages to better describe the fundamentals.
Again, welcome to the Squeak community!