Hi all, Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads). What do you think about it ? Are there any good reasons to still keep SqueakSource alive? Cheers, The SCG Team
On 2013-05-07, at 19:03, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
I don't really think so. Read-only mode is perfect, you only waste time to relaunch squeaksource when it crashes :)
+1 On May 7, 2013, at 7:59 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-05-07, at 19:03, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
I don't really think so. Read-only mode is perfect, you only waste time to relaunch squeaksource when it crashes :)
I don't really think so. Read-only mode is perfect, you only waste time to relaunch squeaksource when it crashes :)
We were thinking at something more dramatic, like killing the image and putting all the public licensed projects on some ftp (or something similar). Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of the server at 100%
On 2013-05-07, at 21:21, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
I don't really think so. Read-only mode is perfect, you only waste time to relaunch squeaksource when it crashes :)
We were thinking at something more dramatic, like killing the image and putting all the public licensed projects on some ftp (or something similar). Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of the server at 100%
even better... I would definitely prefer such a low-tech solution that is maintainable and stable on the long run.
On May 7, 2013, at 9:15 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
I don't really think so. Read-only mode is perfect, you only waste time to relaunch squeaksource when it crashes :)
We were thinking at something more dramatic, like killing the image and putting all the public licensed projects on some ftp (or something similar).
Yes on a ftp would be really good. Stef
Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of the server at 100%
2013/5/7 Andrei Vasile Chis <chisvasileandrei@gmail.com>
I don't really think so. Read-only mode is perfect, you only waste time to
relaunch squeaksource when it crashes :)
We were thinking at something more dramatic, like killing the image and putting all the public licensed projects on some ftp (or something similar).
If you go such way it will be impossible to find old projects by description and wiki page contents. Squeaksource have search.
Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of the server at 100%
We can add a search based on project names. Also I'd like to create a virtual machine and move an instance of the SqueakSource image there. This way if in the future people will want to access any meta-information they could download the virtual machine and get a running SqueakSource. On Wed, May 8, 2013 at 11:25 AM, Denis Kudriashov <dionisiydk@gmail.com>wrote:
2013/5/7 Andrei Vasile Chis <chisvasileandrei@gmail.com>
I don't really think so. Read-only mode is perfect, you only waste time to
relaunch squeaksource when it crashes :)
We were thinking at something more dramatic, like killing the image and putting all the public licensed projects on some ftp (or something similar).
If you go such way it will be impossible to find old projects by description and wiki page contents. Squeaksource have search.
Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of the server at 100%
On May 8, 2013, at 6:11 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
We can add a search based on project names. Also I'd like to create a virtual machine and move an instance of the SqueakSource image there. This way if in the future people will want to access any meta-information they could download the virtual machine and get a running SqueakSource.
yes this is a really good idea!
On Wed, May 8, 2013 at 11:25 AM, Denis Kudriashov <dionisiydk@gmail.com> wrote: 2013/5/7 Andrei Vasile Chis <chisvasileandrei@gmail.com> I don't really think so. Read-only mode is perfect, you only waste time to relaunch squeaksource when it crashes :)
We were thinking at something more dramatic, like killing the image and putting all the public licensed projects on some ftp (or something similar).
If you go such way it will be impossible to find old projects by description and wiki page contents. Squeaksource have search.
Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of the server at 100%
On May 7, 2013, at 7:03 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ?
Yes, I think this is the way to go⦠there are better things to do than to keep it alive with the limited resources we have. And if the file system is available, all scripts loading things from there will continue to work. Marcus
I think it would be helpful to have those public open source licensed projects that are not yet loaded on ss3 or smalltalk hub copied there for posterity. Maybe make a squeaksource archive account on each platform that does the copying. On 05/07/2013 08:19 AM, Andrei Vasile Chis wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
Cheers, The SCG Team
On 2013-05-07, at 23:21, Paul DeBruicker <pdebruic@gmail.com> wrote:
I think it would be helpful to have those public open source licensed projects that are not yet loaded on ss3 or smalltalk hub copied there for posterity. Maybe make a squeaksource archive account on each platform that does the copying.
Just for the record: they won't be removed from squeaksource, the projects will just be read-only.
On 05/07/2013 08:19 AM, Andrei Vasile Chis wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
Cheers, The SCG Team
On May 7, 2013, at 11:21 PM, Paul DeBruicker <pdebruic@gmail.com> wrote:
I think it would be helpful to have those public open source licensed projects that are not yet loaded on ss3 or smalltalk hub copied there for posterity. Maybe make a squeaksource archive account on each platform that does the copying.
If the file system view stays available via squeaksource.com, people can do this lazily as needed. And having the files available via http should be easy to just keep forever⦠Disk space is cheap. Marcus
On May 7, 2013, at 5:40 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
If the file system view stays available via squeaksource.com, people can do this lazily as needed.
And having the files available via http should be easy to just keep forever⦠Disk space is cheap.
+1 on that. You only need a plain web server to serve static files, that's what the mirror is doing. (I'll probably close the mirror down though as there seems to be little used now) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
Keep it alive so that we can slowly migrate. Because migrating takes a lot of time.
Cheers, The SCG Team
We were thinking of keeping the current image alive for one or two more months. Then replace it with just a simple view of the file system. On Wed, May 8, 2013 at 9:50 AM, stephane ducasse <stephane.ducasse@free.fr>wrote:
On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com> wrote:
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
Keep it alive so that we can slowly migrate. Because migrating takes a lot of time.
Cheers, The SCG Team
Are the project descriptions and wiki entries stored in the file system or the image? On 05/08/2013 09:07 AM, Andrei Vasile Chis wrote:
We were thinking of keeping the current image alive for one or two more months. Then replace it with just a simple view of the file system.
On Wed, May 8, 2013 at 9:50 AM, stephane ducasse <stephane.ducasse@free.fr <mailto:stephane.ducasse@free.fr>> wrote:
On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
> Hi all, > > Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. > Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads). > > What do you think about it ? > Are there any good reasons to still keep SqueakSource alive?
Keep it alive so that we can slowly migrate. Because migrating takes a lot of time.
> > Cheers, > The SCG Team
The project descriptions and the wiki entries are stored in the image. On May 8, 2013 7:05 PM, "Paul DeBruicker" <pdebruic@gmail.com> wrote:
Are the project descriptions and wiki entries stored in the file system or the image?
On 05/08/2013 09:07 AM, Andrei Vasile Chis wrote:
We were thinking of keeping the current image alive for one or two more months. Then replace it with just a simple view of the file system.
On Wed, May 8, 2013 at 9:50 AM, stephane ducasse <stephane.ducasse@free.fr <mailto:stephane.ducasse@free.fr>> wrote:
On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <chisvasileandrei@gmail.com <mailto:chisvasileandrei@gmail.com>> wrote:
> Hi all, > > Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. > Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads). > > What do you think about it ? > Are there any good reasons to still keep SqueakSource alive?
Keep it alive so that we can slowly migrate. Because migrating takes a lot of time.
> > Cheers, > The SCG Team
A small note or link in Squeaksource how to migrate to smaltalkhub will be helpful. Thanks Hilaire Le 07/05/2013 17:19, Andrei Vasile Chis a écrit :
Hi all,
Given that SmalltalkHub is now stable we were considering to discontinue SqueakSource. Our idea is to provide a grace period of a couple of months to allow the current active users to migrate their projects to the new service and then simply put squeaksource in read-only mode (simply exposing the directory structure and allowing downloads).
What do you think about it ? Are there any good reasons to still keep SqueakSource alive?
Cheers, The SCG Team
-- Dr. Geo http://drgeo.eu
On Wed, May 8, 2013 at 4:05 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
A small note or link in Squeaksource how to migrate to smaltalkhub will be helpful.
I agree. Something like that would make sense for people who want to get an exact copy of their project: | source goSource destination goDestination files destinationFiles | source := MCHttpRepository location: 'http://www.squeaksource.com/YOURPROJECT'. destination := MCSmalltalkhubRepository owner: 'YOURNAME' project: 'YOURPROJECT' user: 'YOURNAME' password: 'YOURPASSWORD'. goSource := Gofer new repository: source. goDestination := Gofer new repository: destination. files := source allVersionNames. (goSource allResolved select: [ :resolved | files anySatisfy: [ :each | resolved name = each ] ]) do: [ :each | goSource package: each packageName ]. goSource fetch. "downloads all mcz on your computer" destinationFiles := destination allVersionNames. "checks what files are already at destination" files reject: [ :file | destinationFiles includes: file ] thenDo: [ :file | goDestination version: file ]. "selects only the mcz that are not yet at destination" goDestination push. "sends everything to SmalltalkHub" self assert: destination allVersionNames sorted = files sorted. "checks we have exactly the same files at source and destination" -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Thanks. I will add this script to the front page of SqueakSource. On Wed, May 8, 2013 at 5:55 PM, Damien Cassou <damien.cassou@gmail.com>wrote:
On Wed, May 8, 2013 at 4:05 PM, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
A small note or link in Squeaksource how to migrate to smaltalkhub will be helpful.
I agree. Something like that would make sense for people who want to get an exact copy of their project:
| source goSource destination goDestination files destinationFiles |
source := MCHttpRepository location: ' http://www.squeaksource.com/YOURPROJECT'. destination := MCSmalltalkhubRepository owner: 'YOURNAME' project: 'YOURPROJECT' user: 'YOURNAME' password: 'YOURPASSWORD'.
goSource := Gofer new repository: source. goDestination := Gofer new repository: destination.
files := source allVersionNames.
(goSource allResolved select: [ :resolved | files anySatisfy: [ :each | resolved name = each ] ]) do: [ :each | goSource package: each packageName ].
goSource fetch. "downloads all mcz on your computer"
destinationFiles := destination allVersionNames. "checks what files are already at destination" files reject: [ :file | destinationFiles includes: file ] thenDo: [ :file | goDestination version: file ]. "selects only the mcz that are not yet at destination"
goDestination push. "sends everything to SmalltalkHub"
self assert: destination allVersionNames sorted = files sorted. "checks we have exactly the same files at source and destination"
-- Damien Cassou http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Le 08/05/2013 18:08, Andrei Vasile Chis a écrit :
Thanks. I will add this script to the front page of SqueakSource.
Thanks. Hilaire -- Dr. Geo http://drgeo.eu
Hi, So SqueakSource will remain like it's now until 15 July 2013. Afterward we'll replace it with a simple view exposing just the file system. This view will only contain projects that are globally visible. I've updated the front page with this news and the migration script to smalltalk hub. Now a question. If we replace squeak source with a view of the file system all meta information won't be accessible any more. This also includes the license of the projects. Do you think it makes sense to extract this information and put it next to the projects? Also is there any other meta information that would be useful to have? Cheers, Andrei On Thu, May 9, 2013 at 10:22 AM, Hilaire Fernandes < hilaire.fernandes@gmail.com> wrote:
Le 08/05/2013 18:08, Andrei Vasile Chis a écrit :
Thanks. I will add this script to the front page of SqueakSource.
Thanks.
Hilaire
-- Dr. Geo http://drgeo.eu
participants (10)
-
Andrei Vasile Chis -
Camillo Bruni -
Damien Cassou -
Denis Kudriashov -
Esteban Lorenzano -
Hilaire Fernandes -
Johan Fabry -
Marcus Denker -
Paul DeBruicker -
stephane ducasse