If SqueakSource would be made read-only even for existing projects, it
could help "encourage" the transition to the new resources (ss3 and hub). But the King still needs to remain available for some time yet -- to preserve some of the diamonds in there which may not have a caretaker at this time. On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <[hidden email]> wrote: > Hi, > > I strongly recommend all of you to move your projects into one of the alternatives: > > http://smalltalkhub.com > http://ss3.gemstone.com > > the king is dead, long live the king! > > Esteban |
On 6 November 2012 15:56, Chris Muller <[hidden email]> wrote:
> If SqueakSource would be made read-only even for existing projects, it > could help "encourage" the transition to the new resources (ss3 and > hub). I can't speak for others, but I'd personally find that quite irritating (and I make sure I keep my ss3 repos in sync with the ss ones). > But the King still needs to remain available for some time yet -- to > preserve some of the diamonds in there which may not have a caretaker > at this time. More than that: Metacello has - as I understand it at least - coupled the notion of a project together with the source of that project. In other words, a ConfigurationOfFoo says "get these packages from this server". That means that unless you take care in how you write your ConfigurationOfs your source location is a single point of failure. Dale, how complicated would it be to separate out the notion of findability? In other words, to have the person _executing_ the ConfigurationOf to say "look for packages in these locations" with defaults set to {ss. latAm. ss3}? frank > On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <[hidden email]> wrote: >> Hi, >> >> I strongly recommend all of you to move your projects into one of the alternatives: >> >> http://smalltalkhub.com >> http://ss3.gemstone.com >> >> the king is dead, long live the king! >> >> Esteban > |
In reply to this post by Chris Muller-3
On Tue, Nov 06, 2012 at 10:45:57AM +0100, Esteban Lorenzano wrote:
> Hi, > > I strongly recommend all of you to move your projects into one of the alternatives: > > http://smalltalkhub.com > http://ss3.gemstone.com I would appreciate some guidance as to which of these is intended to serve as the long term replacement for SqueakSource, and how specifically I should go about migrating an existing project from SqueakSource to the replacement system. Thanks, Dave |
On 6 November 2012 17:29, David T. Lewis <[hidden email]> wrote:
> On Tue, Nov 06, 2012 at 10:45:57AM +0100, Esteban Lorenzano wrote: >> Hi, >> >> I strongly recommend all of you to move your projects into one of the alternatives: >> >> http://smalltalkhub.com >> http://ss3.gemstone.com > > I would appreciate some guidance as to which of these is intended to > serve as the long term replacement for SqueakSource, and how specifically > I should go about migrating an existing project from SqueakSource to the > replacement system. Dave, Mariano's written up something which ought to help: http://marianopeck.wordpress.com/2011/11/08/migrating-projects-to-squeaksource3/ (I use ss3 for my new projects (but I'd rather be using GitHub).) frank > Thanks, > Dave > > |
In reply to this post by David T. Lewis
Please use ss3 for projects closely-related to Squeak.
ss3.gemstone.com is the like-replacement of the original SqueakSource which the Squeak board recognizes as the official replacement for SqueakSource. SmalltalkHub is a competing alternative which may be suitable for some Squeak application projects. It's implemented on Pharo. On Tue, Nov 6, 2012 at 11:29 AM, David T. Lewis <[hidden email]> wrote: > On Tue, Nov 06, 2012 at 10:45:57AM +0100, Esteban Lorenzano wrote: >> Hi, >> >> I strongly recommend all of you to move your projects into one of the alternatives: >> >> http://smalltalkhub.com >> http://ss3.gemstone.com > > I would appreciate some guidance as to which of these is intended to > serve as the long term replacement for SqueakSource, and how specifically > I should go about migrating an existing project from SqueakSource to the > replacement system. > > Thanks, > Dave > > |
Dne 07. 11. 2012 00:13, piše Chris Muller: > SmalltalkHub is a competing alternative which may be suitable for some > Squeak application projects. It's implemented on Pharo. It is actually implemented on Amber on web client and Seaside on (probably) Pharo on the server. Database is MongoDB. But main language is Amber, that's my point here. Another point is that broader SmalltalkHub goal is to cover all Smalltalks, VW, VA etc. included. Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si |
On 11/07/2012 10:08 AM, Janko Mivšek wrote:
> > Dne 07. 11. 2012 00:13, piše Chris Muller: > >> SmalltalkHub is a competing alternative which may be suitable for some >> Squeak application projects. It's implemented on Pharo. > > It is actually implemented on Amber on web client and Seaside on > (probably) Pharo on the server. Database is MongoDB. But main language > is Amber, that's my point here. Another point is that broader > SmalltalkHub goal is to cover all Smalltalks, VW, VA etc. included. Yes, SmalltalkHub has a HTML5 frontend written in Amber that uses REST calls with a backend written in Pharo with Seaside-REST handling the REST calls from the client side. Now... I wouldn't want to pitch one better than the other for *Squeak*, I mean - sure, SmalltalkHub is written in Pharo (backend) but S3 is written in GLASS, or? So neither is fully Squeak centric :) In the end we need to cope with multiple sources and make sure our front end tools can deal with that as gracefully as possible. At the moment they really don't IMHO. regards, Göran |
These tools are great and I look forward to using them.
Is there any chance one of them could be adopted by ESUG or the Software Freedom Conservancy? I don't wish anyone ill. Nevertheless, it could be a problem if an important domain name or server one day came under the control of creditors/courts/executors, through no fault of those who have kindly donated the resources and expertise. I am told this has happened to projects like ours in the past. Best, David |
On 2012-11-07, at 17:18, David Corking <[hidden email]> wrote: > These tools are great and I look forward to using them. > > Is there any chance one of them could be adopted by ESUG or the > Software Freedom Conservancy? > > I don't wish anyone ill. Nevertheless, it could be a problem if an > important domain name or server one day came under the control of > creditors/courts/executors, through no fault of those who have kindly > donated the resources and expertise. I am told this has happened to > projects like ours in the past. Well, the main Squeak server is now owned by the SFC, and we are in the process of setting up a few more (just got a new one for the build server). While we are working on getting active projects migrated to squeaksource3, we are also planning to set up another read-only backup mirror for squeaksource.com, like the one in Chile, though hopefully with the meta data intact. Help welcome - hop over to the box admins list. - Bert - |
In reply to this post by Frank Shearar-3
Frank,
With the Metacello Scripting API, I have introduced just the capability you are looking for. You can specify that a particular project be associated with a particular repository location for your image and whenever that project is referenced your "local override" will be used ... I haven't released this feature yet, because I'm looking for more feedback on the API. I was hoping that I would get experience reports from Pharo2.0 users, but the Metacello Scripting API doesn't work on Pharo2.0 (lack of OSProcess support) so I have backed off on the pedal for trying to push both the Scripting API and git support into production ... If you want to take the Preview release for a spin (and aren't using Pharo2.0) let me know. Dale ----- Original Message ----- | From: "Frank Shearar" <[hidden email]> | To: "ma chris m" <[hidden email]>, "The general-purpose Squeak developers list" | <[hidden email]> | Cc: [hidden email] | Sent: Tuesday, November 6, 2012 8:01:07 AM | Subject: Re: [squeak-dev] Re: [Pharo-project] now that squeaksource is back... | | On 6 November 2012 15:56, Chris Muller <[hidden email]> wrote: | > If SqueakSource would be made read-only even for existing projects, | > it | > could help "encourage" the transition to the new resources (ss3 and | > hub). | | I can't speak for others, but I'd personally find that quite | irritating (and I make sure I keep my ss3 repos in sync with the ss | ones). | | > But the King still needs to remain available for some time yet -- | > to | > preserve some of the diamonds in there which may not have a | > caretaker | > at this time. | | More than that: Metacello has - as I understand it at least - coupled | the notion of a project together with the source of that project. In | other words, a ConfigurationOfFoo says "get these packages from this | server". That means that unless you take care in how you write your | ConfigurationOfs your source location is a single point of failure. | | Dale, how complicated would it be to separate out the notion of | findability? In other words, to have the person _executing_ the | ConfigurationOf to say "look for packages in these locations" with | defaults set to {ss. latAm. ss3}? | | frank | | > On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano | > <[hidden email]> wrote: | >> Hi, | >> | >> I strongly recommend all of you to move your projects into one of | >> the alternatives: | >> | >> http://smalltalkhub.com | >> http://ss3.gemstone.com | >> | >> the king is dead, long live the king! | >> | >> Esteban | > | | |
In reply to this post by Frank Shearar-3
>> But the King still needs to remain available for some time yet -- to
>> preserve some of the diamonds in there which may not have a caretaker >> at this time. > > More than that: Metacello has - as I understand it at least - coupled > the notion of a project together with the source of that project. In > other words, a ConfigurationOfFoo says "get these packages from this > server". That means that unless you take care in how you write your > ConfigurationOfs your source location is a single point of failure. Making the original SqueakSource read-only has no bearing on this use-case. |
On Tue, Nov 20, 2012 at 10:49 AM, Chris Muller <[hidden email]> wrote:
>>> But the King still needs to remain available for some time yet -- to >>> preserve some of the diamonds in there which may not have a caretaker >>> at this time. >> >> More than that: Metacello has - as I understand it at least - coupled >> the notion of a project together with the source of that project. In >> other words, a ConfigurationOfFoo says "get these packages from this >> server". That means that unless you take care in how you write your >> ConfigurationOfs your source location is a single point of failure. > > Making the original SqueakSource read-only has no bearing on this use-case. Oops, I'm wrong about that. Please disregard. |
Free forum by Nabble | Edit this page |