Hey! :)
Can we add both to the update map (somehow?) and see if it works out during the following days/weeks until the release? (Btw: How does "Adding some external project to trunk" work anyway?) Best, Marcel |
On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel
<[hidden email]> wrote: > Hey! :) > > Can we add both to the update map (somehow?) and see if it works out during > the following days/weeks until the release? +1 |
> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel
> <[hidden email]> wrote: >> Hey! :) >> >> Can we add both to the update map (somehow?) and see if it works out >> during >> the following days/weeks until the release? > > +1 > What is the point of moving these into the base image? Aren't these exactly the kinds of things that you would want to have maintained as independent packages that can be easily loaded from SqueakMap? Dave |
On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: >> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >> <[hidden email]> wrote: >>> Hey! :) >>> >>> Can we add both to the update map (somehow?) and see if it works out >>> during >>> the following days/weeks until the release? >> >> +1 >> > > What is the point of moving these into the base image? Aren't these > exactly the kinds of things that you would want to have maintained as > independent packages that can be easily loaded from SqueakMap? I think both these are Extremely Important (capital). WebClient as replacement for HTTPSocket (it already provides a compatibility layer; Andreas seemed to always considered WebClient to replace HTTPSocket), and SqueakSSL because you can't load anything meaningful on the web without SSL; github, twitter, most sites. And that's good. Plus we _finally_ could put the Plain Text Passwords for Monticello behind SSL… Best -Tobias |
In reply to this post by David T. Lewis
Squeak should be able to retrieve content from an HTTPS-Url out-of-the-box. :)
Best, Marcel |
In reply to this post by Tobias Pape
>
> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: > >>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >>> <[hidden email]> wrote: >>>> Hey! :) >>>> >>>> Can we add both to the update map (somehow?) and see if it works out >>>> during >>>> the following days/weeks until the release? >>> >>> +1 >>> >> >> What is the point of moving these into the base image? Aren't these >> exactly the kinds of things that you would want to have maintained as >> independent packages that can be easily loaded from SqueakMap? > > I think both these are Extremely Important (capital). > WebClient as replacement for HTTPSocket (it already provides a > compatibility > layer; Andreas seemed to always considered WebClient to replace > HTTPSocket), > and SqueakSSL because you can't load anything meaningful on the web > without > SSL; github, twitter, most sites. And that's good. > Plus we _finally_ could put the Plain Text Passwords for Monticello behind > SSL > OK that makes sense :-) Dave |
In reply to this post by Tobias Pape
It would be better for these packages too, because they would get more
attention. The SqueakSSL/WebClient changes I made in October[1] are still missing from the official repositories. Levente [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html On Mon, 6 Apr 2015, Tobias Pape wrote: > > On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: > >>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >>> <[hidden email]> wrote: >>>> Hey! :) >>>> >>>> Can we add both to the update map (somehow?) and see if it works out >>>> during >>>> the following days/weeks until the release? >>> >>> +1 >>> >> >> What is the point of moving these into the base image? Aren't these >> exactly the kinds of things that you would want to have maintained as >> independent packages that can be easily loaded from SqueakMap? > > I think both these are Extremely Important (capital). > WebClient as replacement for HTTPSocket (it already provides a compatibility > layer; Andreas seemed to always considered WebClient to replace HTTPSocket), > and SqueakSSL because you can't load anything meaningful on the web without > SSL; github, twitter, most sites. And that's good. > Plus we _finally_ could put the Plain Text Passwords for Monticello behind > SSL… > > Best > -Tobias > |
Hi Levente
On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: > It would be better for these packages too, because they would get more > attention. > The SqueakSSL/WebClient changes I made in October[1] are still missing from the official repositories. > > Levente > > [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html > I just now saw that there is more than just vm stuff. The problem with WebClient and SqueakSSL as of now is, that its maintenance-ship is, well, complicated. I went forth and pushed tiny changes to WebClient by just being somewhat on my own initiative[1]. =========== Dear Squeak Community as a whole and dear Ron as person possibly best fit to make a decision on this: Should we put the maintainer-ship of WebClient and SqueakSSL into the hands of the Squeak Core Team? =========== Best -Tobias [1]: There's a saying, initiative is discipline-lessness with positive outcome > On Mon, 6 Apr 2015, Tobias Pape wrote: > >> >> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: >> >>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >>>> <[hidden email]> wrote: >>>>> Hey! :) >>>>> >>>>> Can we add both to the update map (somehow?) and see if it works out >>>>> during >>>>> the following days/weeks until the release? >>>> >>>> +1 >>>> >>> >>> What is the point of moving these into the base image? Aren't these >>> exactly the kinds of things that you would want to have maintained as >>> independent packages that can be easily loaded from SqueakMap? >> >> I think both these are Extremely Important (capital). >> WebClient as replacement for HTTPSocket (it already provides a compatibility >> layer; Andreas seemed to always considered WebClient to replace HTTPSocket), >> and SqueakSSL because you can't load anything meaningful on the web without >> SSL; github, twitter, most sites. And that's good. >> Plus we _finally_ could put the Plain Text Passwords for Monticello behind >> SSL… >> >> Best >> -Tobias |
We should pull these in to trunk as soon as possible so we can get stuff tested before the release of a new image. Can you do that Levente, as you seem most familiar with the changes you made ? Karl On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: Hi Levente |
Hi,
On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: > We should pull these in to trunk as soon as possible so we can get stuff tested before the release of a new image. > > Can you do that Levente, as you seem most familiar with the changes you made ? > Although I am not levente I went ahead and pushed SqueakSSL and WebClient into the trunk. Lets see how it turns out. Best -Tobias > Karl > > On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: > Hi Levente > > On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: > > > It would be better for these packages too, because they would get more > > attention. > > The SqueakSSL/WebClient changes I made in October[1] are still missing from the official repositories. > > > > Levente > > > > [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html > > > > I just now saw that there is more than just vm stuff. > > The problem with WebClient and SqueakSSL as of now is, that > its maintenance-ship is, well, complicated. I went forth and > pushed tiny changes to WebClient by just being somewhat on > my own initiative[1]. > > =========== > > Dear Squeak Community as a whole and dear Ron as person possibly > best fit to make a decision on this: > > Should we put the maintainer-ship of WebClient and > SqueakSSL into the hands of the Squeak Core Team? > > > =========== > > Best > -Tobias > > > > > [1]: There's a saying, initiative is discipline-lessness with positive outcome > > > On Mon, 6 Apr 2015, Tobias Pape wrote: > > > >> > >> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: > >> > >>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel > >>>> <[hidden email]> wrote: > >>>>> Hey! :) > >>>>> > >>>>> Can we add both to the update map (somehow?) and see if it works out > >>>>> during > >>>>> the following days/weeks until the release? > >>>> > >>>> +1 > >>>> > >>> > >>> What is the point of moving these into the base image? Aren't these > >>> exactly the kinds of things that you would want to have maintained as > >>> independent packages that can be easily loaded from SqueakMap? > >> > >> I think both these are Extremely Important (capital). > >> WebClient as replacement for HTTPSocket (it already provides a compatibility > >> layer; Andreas seemed to always considered WebClient to replace HTTPSocket), > >> and SqueakSSL because you can't load anything meaningful on the web without > >> SSL; github, twitter, most sites. And that's good. > >> Plus we _finally_ could put the Plain Text Passwords for Monticello behind > >> SSL… > >> > >> Best > >> -Tobias |
I'm a bit too late here, but I wouldn't have pushed WebClient-HTTP,
because those are only overrides, and 2 methods do not work from those. Levente On Mon, 20 Apr 2015, Tobias Pape wrote: > Hi, > > On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: > >> We should pull these in to trunk as soon as possible so we can get stuff tested before the release of a new image. >> >> Can you do that Levente, as you seem most familiar with the changes you made ? >> > > Although I am not levente I went ahead and pushed SqueakSSL and WebClient into > the trunk. Lets see how it turns out. > > Best > -Tobias > >> Karl >> >> On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: >> Hi Levente >> >> On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: >> >>> It would be better for these packages too, because they would get more >>> attention. >>> The SqueakSSL/WebClient changes I made in October[1] are still missing from the official repositories. >>> >>> Levente >>> >>> [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html >>> >> >> I just now saw that there is more than just vm stuff. >> >> The problem with WebClient and SqueakSSL as of now is, that >> its maintenance-ship is, well, complicated. I went forth and >> pushed tiny changes to WebClient by just being somewhat on >> my own initiative[1]. >> >> =========== >> >> Dear Squeak Community as a whole and dear Ron as person possibly >> best fit to make a decision on this: >> >> Should we put the maintainer-ship of WebClient and >> SqueakSSL into the hands of the Squeak Core Team? >> >> >> =========== >> >> Best >> -Tobias >> >> >> >> >> [1]: There's a saying, initiative is discipline-lessness with positive outcome >> >>> On Mon, 6 Apr 2015, Tobias Pape wrote: >>> >>>> >>>> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: >>>> >>>>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >>>>>> <[hidden email]> wrote: >>>>>>> Hey! :) >>>>>>> >>>>>>> Can we add both to the update map (somehow?) and see if it works out >>>>>>> during >>>>>>> the following days/weeks until the release? >>>>>> >>>>>> +1 >>>>>> >>>>> >>>>> What is the point of moving these into the base image? Aren't these >>>>> exactly the kinds of things that you would want to have maintained as >>>>> independent packages that can be easily loaded from SqueakMap? >>>> >>>> I think both these are Extremely Important (capital). >>>> WebClient as replacement for HTTPSocket (it already provides a compatibility >>>> layer; Andreas seemed to always considered WebClient to replace HTTPSocket), >>>> and SqueakSSL because you can't load anything meaningful on the web without >>>> SSL; github, twitter, most sites. And that's good. >>>> Plus we _finally_ could put the Plain Text Passwords for Monticello behind >>>> SSL… >>>> >>>> Best >>>> -Tobias > > > > |
I see you've fixed those too. I'd still remove the WebClient-HTTP package,
and add these methods to the Network package. Levente On Tue, 21 Apr 2015, Levente Uzonyi wrote: > I'm a bit too late here, but I wouldn't have pushed WebClient-HTTP, because > those are only overrides, and 2 methods do not work from those. > > Levente > > On Mon, 20 Apr 2015, Tobias Pape wrote: > >> Hi, >> >> On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: >> >>> We should pull these in to trunk as soon as possible so we can get stuff >>> tested before the release of a new image. >>> >>> Can you do that Levente, as you seem most familiar with the changes you >>> made ? >>> >> >> Although I am not levente I went ahead and pushed SqueakSSL and WebClient >> into >> the trunk. Lets see how it turns out. >> >> Best >> -Tobias >> >>> Karl >>> >>> On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: >>> Hi Levente >>> >>> On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: >>> >>>> It would be better for these packages too, because they would get more >>>> attention. >>>> The SqueakSSL/WebClient changes I made in October[1] are still missing >>>> from the official repositories. >>>> >>>> Levente >>>> >>>> [1] >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html >>>> >>> >>> I just now saw that there is more than just vm stuff. >>> >>> The problem with WebClient and SqueakSSL as of now is, that >>> its maintenance-ship is, well, complicated. I went forth and >>> pushed tiny changes to WebClient by just being somewhat on >>> my own initiative[1]. >>> >>> =========== >>> >>> Dear Squeak Community as a whole and dear Ron as person possibly >>> best fit to make a decision on this: >>> >>> Should we put the maintainer-ship of WebClient and >>> SqueakSSL into the hands of the Squeak Core Team? >>> >>> >>> =========== >>> >>> Best >>> -Tobias >>> >>> >>> >>> >>> [1]: There's a saying, initiative is discipline-lessness with positive >>> outcome >>> >>>> On Mon, 6 Apr 2015, Tobias Pape wrote: >>>> >>>>> >>>>> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: >>>>> >>>>>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >>>>>>> <[hidden email]> wrote: >>>>>>>> Hey! :) >>>>>>>> >>>>>>>> Can we add both to the update map (somehow?) and see if it works out >>>>>>>> during >>>>>>>> the following days/weeks until the release? >>>>>>> >>>>>>> +1 >>>>>>> >>>>>> >>>>>> What is the point of moving these into the base image? Aren't these >>>>>> exactly the kinds of things that you would want to have maintained as >>>>>> independent packages that can be easily loaded from SqueakMap? >>>>> >>>>> I think both these are Extremely Important (capital). >>>>> WebClient as replacement for HTTPSocket (it already provides a >>>>> compatibility >>>>> layer; Andreas seemed to always considered WebClient to replace >>>>> HTTPSocket), >>>>> and SqueakSSL because you can't load anything meaningful on the web >>>>> without >>>>> SSL; github, twitter, most sites. And that's good. >>>>> Plus we _finally_ could put the Plain Text Passwords for Monticello >>>>> behind >>>>> SSL… >>>>> >>>>> Best >>>>> -Tobias >> >> >> > |
On 21.04.2015, at 06:25, Levente Uzonyi <[hidden email]> wrote: > I see you've fixed those too. I'd still remove the WebClient-HTTP package, and add these methods to the Network package. > Directly? Ok, seems fair. Could you do that? Best -Tobias > Levente > > On Tue, 21 Apr 2015, Levente Uzonyi wrote: > >> I'm a bit too late here, but I wouldn't have pushed WebClient-HTTP, because those are only overrides, and 2 methods do not work from those. >> >> Levente >> >> On Mon, 20 Apr 2015, Tobias Pape wrote: >> >>> Hi, >>> On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: >>>> We should pull these in to trunk as soon as possible so we can get stuff tested before the release of a new image. >>>> Can you do that Levente, as you seem most familiar with the changes you made ? >>> Although I am not levente I went ahead and pushed SqueakSSL and WebClient into >>> the trunk. Lets see how it turns out. >>> Best >>> -Tobias >>>> Karl >>>> On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: >>>> Hi Levente >>>> On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: >>>>> It would be better for these packages too, because they would get more >>>>> attention. >>>>> The SqueakSSL/WebClient changes I made in October[1] are still missing from the official repositories. >>>>> Levente >>>>> [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html >>>> I just now saw that there is more than just vm stuff. >>>> The problem with WebClient and SqueakSSL as of now is, that >>>> its maintenance-ship is, well, complicated. I went forth and >>>> pushed tiny changes to WebClient by just being somewhat on >>>> my own initiative[1]. >>>> =========== >>>> Dear Squeak Community as a whole and dear Ron as person possibly >>>> best fit to make a decision on this: >>>> >>>> Should we put the maintainer-ship of WebClient and >>>> SqueakSSL into the hands of the Squeak Core Team? >>>> =========== >>>> Best >>>> -Tobias >>>> [1]: There's a saying, initiative is discipline-lessness with positive outcome >>>>> On Mon, 6 Apr 2015, Tobias Pape wrote: |
In reply to this post by Tobias Pape
Great. Seems we need to issue a update map before these gets pulled in by updating. Can also remove Universes package ? That also needs to be done in a update map, I think Karl On Mon, Apr 20, 2015 at 10:54 PM, Tobias Pape <[hidden email]> wrote: Hi, |
There's update-topa.307, which contains these packages.
Levente On Tue, 21 Apr 2015, karl ramberg wrote: > Great.Seems we need to issue a update map before these gets pulled in by updating. > > Can also remove Universes package ? > That also needs to be done in a update map, I think > > Karl > > On Mon, Apr 20, 2015 at 10:54 PM, Tobias Pape <[hidden email]> wrote: > Hi, > > On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: > > > We should pull these in to trunk as soon as possible so we can get stuff tested before the release of a new image. > > > > Can you do that Levente, as you seem most familiar with the changes you made ? > > > > Although I am not levente I went ahead and pushed SqueakSSL and WebClient into > the trunk. Lets see how it turns out. > > Best > -Tobias > > > Karl > > > > On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: > > Hi Levente > > > > On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: > > > > > It would be better for these packages too, because they would get more > > > attention. > > > The SqueakSSL/WebClient changes I made in October[1] are still missing from the official repositories. > > > > > > Levente > > > > > > [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html > > > > > > > I just now saw that there is more than just vm stuff. > > > > The problem with WebClient and SqueakSSL as of now is, that > > its maintenance-ship is, well, complicated. I went forth and > > pushed tiny changes to WebClient by just being somewhat on > > my own initiative[1]. > > > > =========== > > > > Dear Squeak Community as a whole and dear Ron as person possibly > > best fit to make a decision on this: > > > > Should we put the maintainer-ship of WebClient and > > SqueakSSL into the hands of the Squeak Core Team? > > > > > > =========== > > > > Best > > -Tobias > > > > > > > > > > [1]: There's a saying, initiative is discipline-lessness with positive outcome > > > > > On Mon, 6 Apr 2015, Tobias Pape wrote: > > > > > >> > > >> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: > > >> > > >>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel > > >>>> <[hidden email]> wrote: > > >>>>> Hey! :) > > >>>>> > > >>>>> Can we add both to the update map (somehow?) and see if it works out > > >>>>> during > > >>>>> the following days/weeks until the release? > > >>>> > > >>>> +1 > > >>>> > > >>> > > >>> What is the point of moving these into the base image? Aren't these > > >>> exactly the kinds of things that you would want to have maintained as > > >>> independent packages that can be easily loaded from SqueakMap? > > >> > > >> I think both these are Extremely Important (capital). > > >> WebClient as replacement for HTTPSocket (it already provides a compatibility > > >> layer; Andreas seemed to always considered WebClient to replace HTTPSocket), > > >> and SqueakSSL because you can't load anything meaningful on the web without > > >> SSL; github, twitter, most sites. And that's good. > > >> Plus we _finally_ could put the Plain Text Passwords for Monticello behind > > >> SSL… > > >> > > >> Best > > >> -Tobias > > > > > > |
Ah, I was using a Spur image. Karl On Tue, Apr 21, 2015 at 11:47 AM, Levente Uzonyi <[hidden email]> wrote: There's update-topa.307, which contains these packages. |
He, Downloading latest build: Build #1337 (2015-apr-21 10:50:00)The coolest build so far... ;-) Karl On Tue, Apr 21, 2015 at 12:06 PM, karl ramberg <[hidden email]> wrote:
|
In reply to this post by Karl Ramberg
On 21 April 2015 at 10:39, karl ramberg <[hidden email]> wrote:
> Great. > Seems we need to issue a update map before these gets pulled in by updating. > > Can also remove Universes package ? > That also needs to be done in a update map, I think I _think_ that back during the 4.4 release cycle we reached consensus that Universes would last one more cycle. That would means its removal time is now. Don't forget that we need to bump the VersionNumber package version when this happens (or our "version number" will decrease). frank > Karl > > On Mon, Apr 20, 2015 at 10:54 PM, Tobias Pape <[hidden email]> wrote: >> >> Hi, >> >> On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: >> >> > We should pull these in to trunk as soon as possible so we can get stuff >> > tested before the release of a new image. >> > >> > Can you do that Levente, as you seem most familiar with the changes you >> > made ? >> > >> >> Although I am not levente I went ahead and pushed SqueakSSL and WebClient >> into >> the trunk. Lets see how it turns out. >> >> Best >> -Tobias >> >> > Karl >> > >> > On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> wrote: >> > Hi Levente >> > >> > On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: >> > >> > > It would be better for these packages too, because they would get more >> > > attention. >> > > The SqueakSSL/WebClient changes I made in October[1] are still missing >> > > from the official repositories. >> > > >> > > Levente >> > > >> > > [1] >> > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html >> > > >> > >> > I just now saw that there is more than just vm stuff. >> > >> > The problem with WebClient and SqueakSSL as of now is, that >> > its maintenance-ship is, well, complicated. I went forth and >> > pushed tiny changes to WebClient by just being somewhat on >> > my own initiative[1]. >> > >> > =========== >> > >> > Dear Squeak Community as a whole and dear Ron as person possibly >> > best fit to make a decision on this: >> > >> > Should we put the maintainer-ship of WebClient and >> > SqueakSSL into the hands of the Squeak Core Team? >> > >> > >> > =========== >> > >> > Best >> > -Tobias >> > >> > >> > >> > >> > [1]: There's a saying, initiative is discipline-lessness with positive >> > outcome >> > >> > > On Mon, 6 Apr 2015, Tobias Pape wrote: >> > > >> > >> >> > >> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> wrote: >> > >> >> > >>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >> > >>>> <[hidden email]> wrote: >> > >>>>> Hey! :) >> > >>>>> >> > >>>>> Can we add both to the update map (somehow?) and see if it works >> > >>>>> out >> > >>>>> during >> > >>>>> the following days/weeks until the release? >> > >>>> >> > >>>> +1 >> > >>>> >> > >>> >> > >>> What is the point of moving these into the base image? Aren't these >> > >>> exactly the kinds of things that you would want to have maintained >> > >>> as >> > >>> independent packages that can be easily loaded from SqueakMap? >> > >> >> > >> I think both these are Extremely Important (capital). >> > >> WebClient as replacement for HTTPSocket (it already provides a >> > >> compatibility >> > >> layer; Andreas seemed to always considered WebClient to replace >> > >> HTTPSocket), >> > >> and SqueakSSL because you can't load anything meaningful on the web >> > >> without >> > >> SSL; github, twitter, most sites. And that's good. >> > >> Plus we _finally_ could put the Plain Text Passwords for Monticello >> > >> behind >> > >> SSL… >> > >> >> > >> Best >> > >> -Tobias >> >> >> > > > > |
On Tue, Apr 21, 2015 at 1:46 PM, Frank Shearar <[hidden email]> wrote: On 21 April 2015 at 10:39, karl ramberg <[hidden email]> wrote: Yay
Ugh, I'm not sure how that is done... Karl
|
On 4/21/15, karl ramberg <[hidden email]> wrote:
> On Tue, Apr 21, 2015 at 1:46 PM, Frank Shearar <[hidden email]> > wrote: > >> On 21 April 2015 at 10:39, karl ramberg <[hidden email]> wrote: >> > Great. >> > Seems we need to issue a update map before these gets pulled in by >> updating. >> > >> > Can also remove Universes package ? >> > That also needs to be done in a update map, I think >> >> I _think_ that back during the 4.4 release cycle we reached consensus >> that Universes would last one more cycle. That would means its removal >> time is now. >> > > Yay +1 >> >> Don't forget that we need to bump the VersionNumber package version >> when this happens (or our "version number" will decrease). >> > > Ugh, I'm not sure how that is done... > > Karl > >> >> frank >> >> > Karl >> > >> > On Mon, Apr 20, 2015 at 10:54 PM, Tobias Pape <[hidden email]> wrote: >> >> >> >> Hi, >> >> >> >> On 14.04.2015, at 14:18, karl ramberg <[hidden email]> wrote: >> >> >> >> > We should pull these in to trunk as soon as possible so we can get >> stuff >> >> > tested before the release of a new image. >> >> > >> >> > Can you do that Levente, as you seem most familiar with the changes >> you >> >> > made ? >> >> > >> >> >> >> Although I am not levente I went ahead and pushed SqueakSSL and >> WebClient >> >> into >> >> the trunk. Lets see how it turns out. >> >> >> >> Best >> >> -Tobias >> >> >> >> > Karl >> >> > >> >> > On Mon, Apr 6, 2015 at 9:22 PM, Tobias Pape <[hidden email]> >> >> > wrote: >> >> > Hi Levente >> >> > >> >> > On 06.04.2015, at 20:43, Levente Uzonyi <[hidden email]> wrote: >> >> > >> >> > > It would be better for these packages too, because they would get >> more >> >> > > attention. >> >> > > The SqueakSSL/WebClient changes I made in October[1] are still >> missing >> >> > > from the official repositories. >> >> > > >> >> > > Levente >> >> > > >> >> > > [1] >> >> > > >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-October/180251.html >> >> > > >> >> > >> >> > I just now saw that there is more than just vm stuff. >> >> > >> >> > The problem with WebClient and SqueakSSL as of now is, that >> >> > its maintenance-ship is, well, complicated. I went forth and >> >> > pushed tiny changes to WebClient by just being somewhat on >> >> > my own initiative[1]. >> >> > >> >> > =========== >> >> > >> >> > Dear Squeak Community as a whole and dear Ron as person possibly >> >> > best fit to make a decision on this: >> >> > >> >> > Should we put the maintainer-ship of WebClient and >> >> > SqueakSSL into the hands of the Squeak Core Team? >> >> > >> >> > >> >> > =========== >> >> > >> >> > Best >> >> > -Tobias >> >> > >> >> > >> >> > >> >> > >> >> > [1]: There's a saying, initiative is discipline-lessness with >> >> > positive >> >> > outcome >> >> > >> >> > > On Mon, 6 Apr 2015, Tobias Pape wrote: >> >> > > >> >> > >> >> >> > >> On 06.04.2015, at 18:59, David T. Lewis <[hidden email]> >> wrote: >> >> > >> >> >> > >>>> On Sun, Apr 5, 2015 at 10:26 AM, Marcel Taeumel >> >> > >>>> <[hidden email]> wrote: >> >> > >>>>> Hey! :) >> >> > >>>>> >> >> > >>>>> Can we add both to the update map (somehow?) and see if it >> >> > >>>>> works >> >> > >>>>> out >> >> > >>>>> during >> >> > >>>>> the following days/weeks until the release? >> >> > >>>> >> >> > >>>> +1 >> >> > >>>> >> >> > >>> >> >> > >>> What is the point of moving these into the base image? Aren't >> these >> >> > >>> exactly the kinds of things that you would want to have >> >> > >>> maintained >> >> > >>> as >> >> > >>> independent packages that can be easily loaded from SqueakMap? >> >> > >> >> >> > >> I think both these are Extremely Important (capital). >> >> > >> WebClient as replacement for HTTPSocket (it already provides a >> >> > >> compatibility >> >> > >> layer; Andreas seemed to always considered WebClient to replace >> >> > >> HTTPSocket), >> >> > >> and SqueakSSL because you can't load anything meaningful on the >> >> > >> web >> >> > >> without >> >> > >> SSL; github, twitter, most sites. And that's good. >> >> > >> Plus we _finally_ could put the Plain Text Passwords for >> >> > >> Monticello >> >> > >> behind >> >> > >> SSL… >> >> > >> >> >> > >> Best >> >> > >> -Tobias >> >> >> >> >> >> >> > >> > >> > >> > >> >> > |
Free forum by Nabble | Edit this page |