Handing over responsibility

[Dave Griswold]

Hi all,

As I'm sure many of you have noticed, I have not been able to spend
any time in quite a while on the system. That was certainly not my
intention, but anyway that's the way things have worked out, for which
I am sorry. I keep intending to spend more time on it, but I have
decided to accept reality and get out of the way so that those of you
who have contributed can self-organize without having to wait for me
to review and integrate your contributions.

I don't want to get too personal, but I feel like I should at least
give some explanation. Part of the problem is, as for most of you, I
have other higher priorities that I need to focus on. But besides
that, a big issue for me is that I've never gotten over the
disappointment I felt back when we had to put Strongtalk on the shelf
and work on the Java VM. I had hoped that when the system went open
source I would be able to jump back in and get motivated to work on
the system again, but for me there has just been too much "water under
the bridge" for that to happen. But those are my personal issues. As
for Strongtalk, it is still extremely cool technology, which after all
these years is still better than anything else available, and it
deserves to survive regardless of the involvement of me or others from
the original team.

The bottom line at this point is that I probably won't be able to
spend any significant time on Strongtalk for the foreseeable future.
I do hope to contribute more at some point, but I just can't give any
commitment as to when or how much.

So what I am doing is handing over responsibility to the other project
members with committer status. Being open source, it is up to you all
to self-organize and figure out how you want to organize things. I
would recommend that initially committers keep their changes in
repository branches until a consensus for reviewing and integrating
those changes is figured out.

Despite this bump in the road, some excellent progress has been made.
Versions of the system have been constructed that now compile and run
using gcc, and a lot of the work to get the VM running on Linux has
been done. Those of you who want to pick up the ball and continue,
now is the time to step up, and work out between yourselves how you
want to coordinate things.

Dave

[J J]

It's a real shame to see you have to step back, but I understand the time concern.

So, does anyone know where the Squeak port is?  I think getting an existing popular system running on Strongtalk will be the fastest way to gain momentum.

Just my 2 cents.