March 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PR2789, Rubric integration revert

by Esteban Lorenzano

Hi, I am sorry you feel frustrated but this is an important change that is going on and we need to tackle it, not revert it. Yes, probably last two weeks there has not been much movement, but reason is we are working on make PharoDays possible. Now, as Stef saidâ¦ Pharo 8 is alpha. I will add VERY alpha. Each release has some moments where there is something severely broken. From my part Iâm happy that this happens now and now (as usual) in august when we are preparing for release :) Please, do a step back and and rephrase your mail. You are the advocate of non-violent communication. Iâm afraid do tell you that the tone of the mail was very violent. In the positive lecture of things: yes, we are having problems with rubric. But once we fix it, you will be happier with it, Iâm sure :) Esteban > On 26 Mar 2019, at 18:39, Stephan Eggermont <stephan(a)stack.nl> wrote: > > ducasse <stepharo(a)netcourrier.com> wrote: >> Hi stephan >> >>> Unless someone is working on fixing it today, I want this PR reverted. >>> Issues 2865, 2963, 2964, 2980, 3013 >>> >>> Stephan >> >> Nobody is working on Pharo this is well known. > > I am feeling angry and ignored. I am trying to contribute and am frustrated > in doing so. I am asked to go through fogbugz and make sure that important > issues are reopened on github. I do so and get comments that bugs donât > solve themselves, on the one where I notice that Rubric is not ready. I > find and fix important other bugs and try to integrate them and notice that > a lot of things donât work as they should. CI has been systematically red. > The first thing I notice is that an in-image test is red, with a trivial to > fix issue. Then I run into all kinds of other problems with Rubric not > implementing something. And Iâm not the only one, looking at the issue > tracker. So I look back trough github and see no signs of improvements in > the past 14 days. I collected the relevant issues and reached out on github > and discord first, without getting a useful reaction. This is not the > development process we are using, as I understand it. > > Please revert the PR. I have been working on FFI, Taskbar and CI bugs and I > want to be able to commit, integrate PRs and make Pharo better. Pharo is > mine. > >> >> Sorry but I did not like the ton of your email, especially because there are >> lot of information that you do not know. > > Iâm up to date with the github commits, issues and PRs, Discord and the > mailing lists. If you feel contributors need more information, please make > sure we get it > >> Now if you want to help, add the issue to the projects so that I can work >> on them with Alain >> and others. Else I will do it. > > Projects donât work yet. > > If you want time to focus on Rubric only and donât want other contributions > to Pharo 8 at the moment, then please announce so. Or use a branch. Donât > integrate a PR that breaks CI and then donât fix the issues for two weeks. > > Stephan > > > > >

March 26, 2019

Re: [Pharo-dev] PR2789, Rubric integration revert

by ducasse

I think that you are exaggerating. We are not working on Pharo 100% of our time and life is complex. Stef > ducasse <stepharo(a)netcourrier.com> wrote: >> Hi stephan >> >>> Unless someone is working on fixing it today, I want this PR reverted. >>> Issues 2865, 2963, 2964, 2980, 3013 >>> >>> Stephan >> >> Nobody is working on Pharo this is well known. > > I am feeling angry and ignored. I am trying to contribute and am frustrated > in doing so. I am asked to go through fogbugz and make sure that important > issues are reopened on github. I do so and get comments that bugs donât > solve themselves, on the one where I notice that Rubric is not ready. I > find and fix important other bugs and try to integrate them and notice that > a lot of things donât work as they should. CI has been systematically red. > The first thing I notice is that an in-image test is red, with a trivial to > fix issue. Then I run into all kinds of other problems with Rubric not > implementing something. And Iâm not the only one, looking at the issue > tracker. So I look back trough github and see no signs of improvements in > the past 14 days. I collected the relevant issues and reached out on github > and discord first, without getting a useful reaction. This is not the > development process we are using, as I understand it. > > Please revert the PR. I have been working on FFI, Taskbar and CI bugs and I > want to be able to commit, integrate PRs and make Pharo better. Pharo is > mine. > >> >> Sorry but I did not like the ton of your email, especially because there are >> lot of information that you do not know. > > Iâm up to date with the github commits, issues and PRs, Discord and the > mailing lists. If you feel contributors need more information, please make > sure we get it There are information about private people and this is private! >> Now if you want to help, add the issue to the projects so that I can work >> on them with Alain >> and others. Else I will do it. > > Projects donât work yet. I just added your issues to them. > If you want time to focus on Rubric only and donât want other contributions > to Pharo 8 at the moment, then please announce so. Or use a branch. Donât > integrate a PR that breaks CI and then donât fix the issues for two weeks. Come on. Stop that kind of bullshit. We have been integrating fixes since the beginning with tests not passing. But you convince me I decided that I will stop reviewing issues and take responsibility to integrate fixes. Esteban and marcus will do it. I will focus on my projects because Iâm total disagreement. My point of view is that life is complex but you have the right to have rigid views and I have the right to drop and use my time for something else. Stef

March 26, 2019

Re: [Pharo-dev] PR2789, Rubric integration revert

by Stephan Eggermont

ducasse <stepharo(a)netcourrier.com> wrote: > Hi stephan > >> Unless someone is working on fixing it today, I want this PR reverted. >> Issues 2865, 2963, 2964, 2980, 3013 >> >> Stephan > > Nobody is working on Pharo this is well known. I am feeling angry and ignored. I am trying to contribute and am frustrated in doing so. I am asked to go through fogbugz and make sure that important issues are reopened on github. I do so and get comments that bugs donât solve themselves, on the one where I notice that Rubric is not ready. I find and fix important other bugs and try to integrate them and notice that a lot of things donât work as they should. CI has been systematically red. The first thing I notice is that an in-image test is red, with a trivial to fix issue. Then I run into all kinds of other problems with Rubric not implementing something. And Iâm not the only one, looking at the issue tracker. So I look back trough github and see no signs of improvements in the past 14 days. I collected the relevant issues and reached out on github and discord first, without getting a useful reaction. This is not the development process we are using, as I understand it. Please revert the PR. I have been working on FFI, Taskbar and CI bugs and I want to be able to commit, integrate PRs and make Pharo better. Pharo is mine. > > Sorry but I did not like the ton of your email, especially because there are > lot of information that you do not know. Iâm up to date with the github commits, issues and PRs, Discord and the mailing lists. If you feel contributors need more information, please make sure we get it > Now if you want to help, add the issue to the projects so that I can work > on them with Alain > and others. Else I will do it. Projects donât work yet. If you want time to focus on Rubric only and donât want other contributions to Pharo 8 at the moment, then please announce so. Or use a branch. Donât integrate a PR that breaks CI and then donât fix the issues for two weeks. Stephan

March 26, 2019

Re: [Pharo-dev] PR2789, Rubric integration revert

by ducasse

Hi stephan > Unless someone is working on fixing it today, I want this PR reverted. > Issues 2865, 2963, 2964, 2980, 3013 > > Stephan Nobody is working on Pharo this is well known. Second my mom always told me that we should not say want but would like. Third, Pharo 80 is ALPHA. Fourth it will be released in November or December 2019. Sorry but I did not like the ton of your email, especially because there are lot of information that you do not know. Now if you want to help, add the issue to the projects so that I can work on them with Alain and others. Else I will do it. S.

March 26, 2019

Re: [Pharo-dev] Request-info bot on github

by ducasse

This is call botWars. So may be we will have to calm them down. > On 26 Mar 2019, at 17:14, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: > > Ok. I wrote a new comment and another bot removed the label. :) > > Thomas > > On 26/03/2019 17:11, Marcus Denker wrote: >> I think you should not edit but put a new comment. The bot seems to only get to see new comments, not edit actions of existing comments. >> >>> On 26 Mar 2019, at 17:06, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: >>> >>> Hello, just asking if this behaviour is normal: >>> >>> - I created an issue with an empty body. >>> - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. >>> - I updated the body of the issue >>> - Now the issue no longer has an empty body, but it still has the message from the bot and the label. >>> >>> The issue in question: https://github.com/pharo-project/pharo/issues/3025 >>> >>> Thomas >>> >>> >> >

March 26, 2019

Re: [Pharo-dev] Request-info bot on github

by Thomas Dupriez

Ok. I wrote a new comment and another bot removed the label. :) Thomas On 26/03/2019 17:11, Marcus Denker wrote: > I think you should not edit but put a new comment. The bot seems to only get to see new comments, not edit actions of existing comments. > >> On 26 Mar 2019, at 17:06, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: >> >> Hello, just asking if this behaviour is normal: >> >> - I created an issue with an empty body. >> - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. >> - I updated the body of the issue >> - Now the issue no longer has an empty body, but it still has the message from the bot and the label. >> >> The issue in question: https://github.com/pharo-project/pharo/issues/3025 >> >> Thomas >> >> >

March 26, 2019

Re: [Pharo-dev] Request-info bot on github

by Marcus Denker

I think you should not edit but put a new comment. The bot seems to only get to see new comments, not edit actions of existing comments. > On 26 Mar 2019, at 17:06, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: > > Hello, just asking if this behaviour is normal: > > - I created an issue with an empty body. > - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. > - I updated the body of the issue > - Now the issue no longer has an empty body, but it still has the message from the bot and the label. > > The issue in question: https://github.com/pharo-project/pharo/issues/3025 > > Thomas > >

March 26, 2019

Request-info bot on github

by Thomas Dupriez

Hello, just asking if this behaviour is normal: - I created an issue with an empty body. - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. - I updated the body of the issue - Now the issue no longer has an empty body, but it still has the message from the bot and the label. The issue in question: https://github.com/pharo-project/pharo/issues/3025 Thomas

March 26, 2019

[Pharo 8.0] Build #185: 3011-cleanup-delete-unsent-private-method-from-Slots-classes

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

There is a new Pharo build available! The status of the build #185 was: SUCCESS. The Pull Request #3012 was integrated: "3011-cleanup-delete-unsent-private-method-from-Slots-classes" Pull request url: https://github.com/pharo-project/pharo/pull/3012 Issue Url: https://github.com/pharo-project/pharo/issues/3011 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 26, 2019

Re: [Pharo-dev] Special Issue on Smalltalk Technologies

by CÃ©drick BÃ©ler

Tu penses que je peux tenter de publier un papier un peu sur les principes du SIS ? Je pense je pourrais tenter aussi un truc avec mon Ã©tudiants et Jannik sur lâaspect CPS. @++ Cedrick Ps je revois pour simplifier lâapproche et commencer Ã faire Ã©merger des scnenario EnvoyÃ© de mon iPhone > Le 26 mars 2019 Ã 11:37, ducasse <stepharo(a)netcourrier.com> a Ã©crit : > > Special Issue on Smalltalk Technologies > https://www.journals.elsevier.com/science-of-computer-programming > Guest Editors: > LoÃ¯c Lagadec (Coordinator) > Ensta Bretagne, Lab-STICC > Anne Etien > UniversitÃ© de Lille, CRIStAL, UMR9189 > Jannik Laval > UniversitÃ© LumiÃ¨re Lyon 2, DISP, EA 4570 > > Theme > Smalltalk is an exciting objectâoriented language in which even primitive values are uniformly handled as normal objects, described by classes that one can browse, inspect and extend. Smalltalk was born during the seventies, still the ideas behind the currently available implementations are often at the edge of innovation. > Smalltalk benefits from being a highly expressive language in which complex and powerful systems can emerge from the composition of simple building blocks. Thanks to its dynamic nature, fast prototyping and agile software development are made possible. Smalltalk is not only a simple and pure dynamic object-oriented language, but is also a programmable system with processes, its own user interface and a complete Interactive Development Environment (IDE). > Smalltalk is a reflexive system, with all its elements being implemented in Smalltalk, which benefits from powerful metaâprogramming facilities. This means that elements can be extended, customized or adapted according to particular contexts, that the Smalltalk IDE itself can be used to implement, validate and debug the Smalltalk system extensions, and that a program is able to query and to change its own structure and behaviour. > In this context, the research topics that relate to Smalltalk technologies are large, and need to receive more attention and research effort, considering that Smalltalk has established itself as a test bed for software engineering theories and tools. > > > > TOPICS include: > ï§ Aspect-oriented programming, > ï§ Design patterns, > ï§ Experience reports, > ï§ Frameworks, > ï§ Implementation, new dialects or languages implemented in Smalltalk, > ï§ Interaction with other languages, > ï§ Meta-programming and Meta-modelling, > ï§ Tools > > > Important Dates: > â¢ Apr. 30, 2019 Full paper submission due > â¢ Aug.31, 2019 Paper acceptance decision > â¢ Sep.15, 2019 Camera-ready paper due >

March 26, 2019