Brian Rice wrote:
> Mostly through a couple of web pages that guide the newbie VM hacker in 
> the right direction. The initial steps are easy, just throwing up a web 
> page that explains the state of things (culled from these or similar 
> messages) and how to ask to do stuff that is not supported yet, and the 
> second part, how to learn from the build structure to make a new port, 
> would involve one person actually going through the process and being 
> able to channel that feedback into those online pages.

The uber-minimalistic front page at SqueakVM.org has a lot of room for 
improvement ;-)

> Oh, not at all. Actually the idea is to get one person to try this 
> approach with their pet port project, particularly where the person 
> isn't part of the core team and doesn't have implicit knowledge about 
> all this. The BeOS port authors still have websites and can be contacted 
> for their stuff and maybe even asked about their experiences with it.

I see. Yes, this would be a sound approach, in particular for gathering 
information about the issues that lurk along the way.

>> Like I was saying before, I don't own the PR on VM stuff. Knock 
>> yourself out if you like, in fact we could probably use someone who 
>> owns these aspects of vm-dev ;-) If you are willing to write a bit of 
>> documentation about it, I think that would be quite welcome.
> 
> Thanks. I'll contact Ian (he owns squeakvm.org) and see about a 
> short-term project to make/coordinate the described progress. (Not that 
> I'm going to give up, but limited-scope is what makes these ideas work.)

Yes, I agree.

Cheers,
   - Andreas