Hi Tobias,
I was referring only to the existing squeaksource.com service, not to future directions. The SCG group has kindly provided a full copy of the current system, and this is being moved to squeak.org for operational support. Discussion is at:
http://lists.squeakfoundation.org/pipermail/box-admins/2013-August/date.html
I apologize if I mixed up some unrelated issues here. I am not involved in future development directions and I did not intend to cause confusion.
Thanks for the tip regarding VM issues, I will make sure that we use an up-to-date VM.
Dave
On Mon, Aug 26, 2013 at 12:10:36PM +0000, Pape, Tobias wrote:
Am 24.08.2013 um 02:26 schrieb David T. Lewis lewis@mail.msen.com:
On Fri, Aug 23, 2013 at 03:18:19PM -0500, Chris Muller wrote:
Hi! Ok so there are a couple of questions and potential answers brewing. How to host? Where to host?
David Lewis expressed that we should recover the actual SS instance and stabilize it.
My immediate concern is to move the existing squeaksource.com to a new home that is stable, supportable, and sustainable for the long term. My hope is to accomplish that migration within days, not weeks. Once that has been completed, all options should be open as far as I'm concerned. But for now my only objective is to achieve operational stability and a sustainable support process for squeaksource.com.
Just to check my understanding, the reference to hosting by Robert Hirschfeld's group is for future consideration, and not something that I need to worry about to the migration plan for the next few days, is that right?
Well Oscar Nierstrasz is commit to us (Robert?s group) in a couple of weeks and would be able to bring a harddrive with all files? (image+mcz's)
This may include bringing it up to a more modern, Cog-supported Squeak image. I am working on doing this for source.squeak.org and so I hope that effort can overlap this one.
Yes for sure, it is important to get source.squeak.org and squeaksource.com onto a common code base and support structure in order to minimize the total support requirement. One way or another, I am quite confident that this will resolve the reliability and performance problems that have plagued squeaksource in the past.
But first things first, I'm still trying to copy files, including well over 15 GB of compressed project files. Firefox says it might be done after another 23 hours and 10 minutes or so ... then I'll need a box on squeak.org to unpack them on.
what files are you copying from where? Are you talking about source.squeak.org org squeaksource.com?
All that said, I maintained an image-based Squeaksource-installation a couple of years ago here at HPI and we ran into lockup-troubles (I figure they are quite similar to those squeaksource.com experienced over the past year) at least once if not twice a day. I tracked the problem down to Socket-related problems (one end closed, the other not, image not responding henceforth), but they were not deterministically reproducible. That was why I started participating in migrating SqS to Gemstone, Initially creating SqueakSource2, but soon changed to Squeaksource3.
From my experiences, I would _strongly_ advice not to setup a new SqueakSource based on a SqueakVM that still has this socket problem (no, it is not the wiggle-the-mouse-and-it-works-again bug).
I am currently devoting my free time to bring GemStone's Monticello-support up to par with Squeaks (read: add missing support for ScriptDefinitions), which would make SS3 on GemStone feature-wise a superset of current squeaksource.com and source.squeak.org while at the same time providing a higher reliability (esp, compared to squeaksource.com).
Best -Tobias
-- Tobias Pape Doktorand im Fachgebiet Software-Architekturen http://www.hpi.uni-potsdam.de/swa/
Hasso-Plattner-Institut f?r Softwaresystemtechnik GmbH Universit?t Potsdam Prof.-Dr.-Helmert-Str. 2-3 D-14482 Potsdam, Germany Amtsgericht Potsdam, HRB 12184 Gesch?ftsf?hrung: Prof. Dr. Christoph Meinel
box-admins@lists.squeakfoundation.org