Smalltalk › Pharo › Pharo Smalltalk Users

the future of squeaksource

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

23 messages Options

Andrei Chis

the future of squeaksource

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

Camillo Bruni-3

Re: the future of squeaksource

On 2013-05-07, at 19:03, Andrei Vasile Chis <[hidden email]> 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 :)

EstebanLM

Re: the future of squeaksource

+1

On May 7, 2013, at 7:59 PM, Camillo Bruni <[hidden email]> wrote:

>
> On 2013-05-07, at 19:03, Andrei Vasile Chis <[hidden email]> 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 :)
>
>

Marcus Denker-4

Re: the future of squeaksource

In reply to this post by Andrei Chis

On May 7, 2013, at 7:03 PM, Andrei Vasile Chis <[hidden email]> 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

Paul DeBruicker

Re: the future of squeaksource

In reply to this post by Andrei Chis

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

Andrei Chis

Re: the future of squeaksource

In reply to this post by Camillo Bruni-3

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%

Camillo Bruni-3

Re: the future of squeaksource

On 2013-05-07, at 21:21, Andrei Vasile Chis <[hidden email]> 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.

Camillo Bruni-3

Re: the future of squeaksource

In reply to this post by Paul DeBruicker

On 2013-05-07, at 23:21, Paul DeBruicker <[hidden email]> 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
>
>

Marcus Denker-4

Re: the future of squeaksource

In reply to this post by Paul DeBruicker

On May 7, 2013, at 11:21 PM, Paul DeBruicker <[hidden email]> 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

jfabry

Re: the future of squeaksource

On May 7, 2013, at 5:40 PM, Marcus Denker <[hidden email]> 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

stephane ducasse

Re: the future of squeaksource

In reply to this post by Andrei Chis

On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <[hidden email]> 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

stephane ducasse

Re: the future of squeaksource

In reply to this post by Andrei Chis

On May 7, 2013, at 9:15 PM, Andrei Vasile Chis <[hidden email]> 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%

Denis Kudriashov

Re: the future of squeaksource

In reply to this post by Andrei Chis

2013/5/7 Andrei Vasile Chis <[hidden email]>

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%

hilaire

Re: the future of squeaksource

In reply to this post by Andrei Chis

CONTENTS DELETED

The author has deleted this message.

Damien Cassou

Re: the future of squeaksource

On Wed, May 8, 2013 at 4:05 PM, Hilaire Fernandes
<[hidden email]> 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

Andrei Chis

Re: the future of squeaksource

In reply to this post by stephane ducasse

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 <[hidden email]> wrote:

On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <[hidden email]> 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

Andrei Chis

Re: the future of squeaksource

In reply to this post by Damien Cassou

Thanks. I will add this script to the front page of SqueakSource.

On Wed, May 8, 2013 at 5:55 PM, Damien Cassou <[hidden email]> wrote:

On Wed, May 8, 2013 at 4:05 PM, Hilaire Fernandes
<[hidden email]> 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

Andrei Chis

Re: the future of squeaksource

In reply to this post by Denis Kudriashov

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 <[hidden email]> wrote:

2013/5/7 Andrei Vasile Chis <[hidden email]>

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%

Paul DeBruicker

Re: the future of squeaksource

In reply to this post by Andrei Chis

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
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>
> On May 7, 2013, at 5:19 PM, Andrei Vasile Chis
> <[hidden email] <mailto:[hidden email]>> 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
>
>
>

stephane ducasse

Re: the future of squeaksource

In reply to this post by Andrei Chis

On May 8, 2013, at 6:11 PM, Andrei Vasile Chis <[hidden email]> 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 <[hidden email]> wrote:

2013/5/7 Andrei Vasile Chis <[hidden email]>

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%