June 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #325: 6412-RBComment-should-have-parent-pointer-to-node

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #325 was: SUCCESS. The Pull Request #6461 was integrated: "6412-RBComment-should-have-parent-pointer-to-node" Pull request url: https://github.com/pharo-project/pharo/pull/6461 Issue Url: https://github.com/pharo-project/pharo/issues/6412 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 2, 2020

[Pharo 9.0] Build #324: extract-return-from-conditionals-for-packages-o

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #324 was: SUCCESS. The Pull Request #6434 was integrated: "extract-return-from-conditionals-for-packages-o" Pull request url: https://github.com/pharo-project/pharo/pull/6434 Issue Url: https://github.com/pharo-project/pharo/issues/extract Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 1, 2020

IWST 2020 Edition

by Vincent Aranega

Hi everyone, In light of the continued uncertainty surrounding the Covid-19 situation, to guarantee the safety and well-being of all, the IWST Steering Committee has decided to move to a virtual event format for this year to be held Sept. 29th and 30th. The 2020 paper review, WiP submission and acceptance processes will proceed normally with a modification of the upcoming deadlines: - Submission deadline: July 15th, 2020 - Notification deadline: September 8th, 2020 - Workshop: September 29-30th, 2020. Like last year, we are very proud to announce a Best Paper Award. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers. We are also happy to announce that accepted papers will be published in the ACM Digital Library. We will follow up with further details on conference organization, presentation formats, and howto guides. The global idea is to collect all required material a week ahead of schedule to prevent any live technical issue: slides, but also video. Only the post presentation Q&A sessions will be interactive. IWST has now a significant history and has served for years as a smart playground for young researchers to practice writing articles & presenting results. In parallel, senior researchers take benefit from IWST to expose mature work and propose some retrospective or draw future directions. Mixing these two kinds of contributors makes IWST that attractive. Letâs do the 2020 edition conformed to this legacy https://esug.github.io/2020-Conference/cfpIWST2020.html Vincent Aranega LoÃ¯c Lagadec

June 1, 2020

IWST 2020 Edition

by Vincent Aranega

Hi everyone, In light of the continued uncertainty surrounding the Covid-19 situation, to guarantee the safety and well-being of all, the IWST Steering Committee has decided to move to a virtual event format for this year to be held Sept. 29th and 30th. The 2020 paper review, WiP submission and acceptance processes will proceed normally with a modification of the upcoming deadlines: - Submission deadline: July 15th, 2020 - Notification deadline: September 8th, 2020 - Workshop: September 29-30th, 2020. Like last year, we are very proud to announce a Best Paper Award. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers. We are also happy to announce that accepted papers will be published in the ACM Digital Library. We will follow up with further details on conference organization, presentation formats, and howto guides. The global idea is to collect all required material a week ahead of schedule to prevent any live technical issue: slides, but also video. Only the post presentation Q&A sessions will be interactive. IWST has now a significant history and has served for years as a smart playground for young researchers to practice writing articles & presenting results. In parallel, senior researchers take benefit from IWST to expose mature work and propose some retrospective or draw future directions. Mixing these two kinds of contributors makes IWST that attractive. Letâs do the 2020 edition conformed to this legacy https://esug.github.io/2020-Conference/cfpIWST2020.html Vincent Aranega LoÃ¯c Lagadec

June 1, 2020

Re: [Pharo-dev] [Pharo-users] About strange email related to smalltalkhub read-only on squeak-dev

by Esteban Lorenzano

Yes, also the project is MIT soâ¦ anyone has the right to take it and use it/modify it/etc. with the only constraint of mention all the contributors. But anyway, for me the most important question is: How far are we to provide good FFI bindings to a security library (like openssl or/and others) that will allow us to escape this situation? I really prefer not to have a hard to maintain solution that will also annoy the original authors who put its code in MIT but didnât realise the implications of it. Esteban > On 1 Jun 2020, at 08:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 1 Jun 2020, at 06:39, Jerry Kott <jkott(a)image-ware.com> wrote: >> >> If you read the text of the EAR and take into account all other facts, I think that the notion that anyone should get into trouble by copying open source Smalltalk crypto libraries to other repositories is just a pure FUD. This software is open source, it is publicly available including the source code, it is hosted on a domain that is controlled by a non-US entity, and itâs easily accessible in its current form from countries that are currently on the US âvorbotenâ list. > > Indeed. > >

June 1, 2020

Re: [Pharo-dev] [Pharo-users] About strange email related to smalltalkhub read-only on squeak-dev

by Sven Van Caekenberghe

> On 1 Jun 2020, at 06:39, Jerry Kott <jkott(a)image-ware.com> wrote: > > If you read the text of the EAR and take into account all other facts, I think that the notion that anyone should get into trouble by copying open source Smalltalk crypto libraries to other repositories is just a pure FUD. This software is open source, it is publicly available including the source code, it is hosted on a domain that is controlled by a non-US entity, and itâs easily accessible in its current form from countries that are currently on the US âvorbotenâ list. Indeed.

June 1, 2020