Community Supported Packages

> On Dec 13, 2014, at 6:44 PM, David T. Lewis <[hidden email]> wrote:
>
> On Sat, Dec 13, 2014 at 11:58:15AM -0500, Chris Cunnington wrote:
>> Thinking about Seaside installation and pages on the homepage, I started to think about putting a Seaside installation script in SqueakMap. [1] (This script loads with no server, I don???t think, so I figure it???s incomplete. Does anybody have a more complete one?)
>> Maybe I???d create two new pages: Seaside; and, Installation. (That URI - Installation - is from the old site). And then add links to SqueakMap and SqueakSource on that page.
>> But then it made me think I???d have to find out who the Seaside maintainers are to ask them to put in a new script. But Seaside should be what we were calling a few years ago a Community Supported Package. Is it a CSM in SqueakMap? How does that work?
>> It seems to me that creating a Seaside page and slapping a Metacello installation script on it is a short sighted solution. Perhaps the notion of a CSM could be explored at this juncture.
>>
>> Chris
>> [1]
>> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfSeaside3'.
>> ((ConfigurationOfSeaside3 project) version: #stable) load.
>
>
> I think that Tobias Pape and Stephan Eggermont have given a good starting
> point. I tried the Metacello configuration, and that works fine. If I want
> to get started on Seaside (which in fact I do), I would want to start first
> with Tobias' latest prepared image, even if it's not updated to the latest
> trunk level.
>
> If we can get the squeak.org site to point to the information that Tobias
> and Stephan provide, that's probably the most important thing to do right
> now.
>
> I like your idea of getting the SqueakMap entry updated, although I'd be
> inclined to follow up on that issue later. How about January 1 as a new
> years resolution? Dang, we have a lot of outdated entries on SqueakMap,
> we really need to clean that up.
>
> New Seaside users are going to start at the Seaside home page, so we want
> to make sure that the download link for "Squeak Smalltalk" points to the
> information that Tobias and Stephan have provided. Right now it is pointing
> to "404 Not Found" which is not exactly the message that we want to be
> sending to the world.
>
> If I could start at the seaside.st home page and follow the download link
> for Squeak to find the Metacello configuration that Stephan provided, and
> the prepared image that Todias provides, I would be a happy camper :-)
>
> Thanks,
>
> Dave
>
>

> OK, let’s leave community supported packages for later. I’l make a
> page for Seaside today.
>
> Chris
>> On Dec 13, 2014, at 6:44 PM, David T. Lewis <[hidden email]> wrote:
>>
>> On Sat, Dec 13, 2014 at 11:58:15AM -0500, Chris Cunnington wrote:
>>> Thinking about Seaside installation and pages on the homepage, I
>>> started to think about putting a Seaside installation script in
>>> SqueakMap. [1] (This script loads with no server, I don???t think, so I
>>> figure it???s incomplete. Does anybody have a more complete one?)
>>> Maybe I???d create two new pages: Seaside; and, Installation. (That URI
>>> - Installation - is from the old site). And then add links to SqueakMap
>>> and SqueakSource on that page.
>>> But then it made me think I???d have to find out who the Seaside
>>> maintainers are to ask them to put in a new script. But Seaside should
>>> be what we were calling a few years ago a Community Supported Package.
>>> Is it a CSM in SqueakMap? How does that work?
>>> It seems to me that creating a Seaside page and slapping a Metacello
>>> installation script on it is a short sighted solution. Perhaps the
>>> notion of a CSM could be explored at this juncture.
>>>
>>> Chris
>>> [1]
>>> (Installer ss project: 'MetacelloRepository') install:
>>> 'ConfigurationOfSeaside3'.
>>> ((ConfigurationOfSeaside3 project) version: #stable) load.
>>
>>
>> I think that Tobias Pape and Stephan Eggermont have given a good
>> starting
>> point. I tried the Metacello configuration, and that works fine. If I
>> want
>> to get started on Seaside (which in fact I do), I would want to start
>> first
>> with Tobias' latest prepared image, even if it's not updated to the
>> latest
>> trunk level.
>>
>> If we can get the squeak.org site to point to the information that
>> Tobias
>> and Stephan provide, that's probably the most important thing to do
>> right
>> now.
>>
>> I like your idea of getting the SqueakMap entry updated, although I'd be
>> inclined to follow up on that issue later. How about January 1 as a new
>> years resolution? Dang, we have a lot of outdated entries on SqueakMap,
>> we really need to clean that up.
>>
>> New Seaside users are going to start at the Seaside home page, so we
>> want
>> to make sure that the download link for "Squeak Smalltalk" points to the
>> information that Tobias and Stephan have provided. Right now it is
>> pointing
>> to "404 Not Found" which is not exactly the message that we want to be
>> sending to the world.
>>
>> If I could start at the seaside.st home page and follow the download
>> link
>> for Squeak to find the Metacello configuration that Stephan provided,
>> and
>> the prepared image that Todias provides, I would be a happy camper :-)
>>
>> Thanks,
>>
>> Dave
>>
>>
>
>

> It seems to me that creating a Seaside page and slapping a Metacello
> installation script on it is a short sighted solution. Perhaps the notion of
> a CSM could be explored at this juncture.
>
> Chris
>
> [1]
>
> (Installer ss project: 'MetacelloRepository') install:
> 'ConfigurationOfSeaside3'.
> ((ConfigurationOfSeaside3 project) version: #stable) load.
>
>
>
>
>