- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Issue Tracker: enabled Projects (Boards)

by Serge Stinckwich

but you need to be on the Pharo organization to be able to add/modify card on the board ? A+ On Tue, Mar 19, 2019 at 11:07 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > it seems that the account / access model of GitHub forces us to move the > boards to the organisation level > (where we can have a user group with write access for the boards). > > This means I will move them slowly to > > https://github.com/orgs/pharo-project/projects > > So lets treat all this as a testâ¦ as soon as it is really working I will > send another mail. > > On 18 Mar 2019, at 08:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We enabled the GitHub âProjectsâ feature for the pharo repo: > > https://github.com/pharo-project/pharo/projects > > > The idea is that one can add as many âKanbanâ style boards as one wants. > issues and pull requests can be added, as well as simple cards that are > not yet issues. > > This is quite nice as an issue tracker gets very confusing and > overwhelming as soon as there > are >500 issues. > > With these boards, we can create âviewsâ on this sea of issues. > > I created for now: > > -> some board related to specific parts of the system (e.g. Traits or > Reflectivity) > example: https://github.com/pharo-project/pharo/projects/11 > -> "Pharo7 Backportingâ > https://github.com/pharo-project/pharo/projects/12 > -> "Simple Issues for Beginnersâ > https://github.com/pharo-project/pharo/projects/14 > Here the feature to be able to put things that are not yet > issue tracker entries seems very useful > > > I think this can be quite niceâ¦ we should add more Projects as soon as we > find that they make sense > and should move issues there. > > Marcus > > > -- Serge Stinckwic âhâ Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) âSorbonne University (SU) French National Research Institute for Sustainable Development (IRD)â U âniversity of YaoundÃ© Iâ, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich â

March 19, 2019

Re: [Pharo-dev] [Issue Trackker][Help Needed]: Move issues from Fogbugz to GitHub

by Tim Mackinnon

Yes - Cyril is a tool meisterâ¦. ;) > On 19 Mar 2019, at 10:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > I think Cyril has some kind of tool? Yes, that might be interesting... > >> On 18 Mar 2019, at 19:26, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Marcus - do we just manually copy over the title and description (and any relevant comments) - or is there some tool to do this with? >> >> Tim >> >>> On 18 Mar 2019, at 07:38, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >>> Hi, >>> >>> We should all look at the old issues: >>> >>> https://pharo.fogbugz.com/f/filters/57/All-newest-first <https://pharo.fogbugz.com/f/filters/57/All-newest-first> >>> >>> and move them to the new one: >>> >>> https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> >>> >>> instead of moving them automatically, we should take the chance to >>> clean up. >>> >>> Please check, first for the issues that *you* added: >>> >>> -> is it still relevant? >>> ->if yes: add a new issue on GitHub >>> ->close this issue, there is now an explicit âmoved to GitHubâ state. >>> >>> >>> Marcus >> >

March 19, 2019

[Pharo 8.0] Build #155: UndefinedObject should not implement at:put: (or inherit it). This isâ¦

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

There is a new Pharo build available! The status of the build #155 was: SUCCESS. The Pull Request #2888 was integrated: "UndefinedObject should not implement at:put: (or inherit it). This isâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/2888 Issue Url: https://pharo.fogbugz.com/f/cases/2795 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2019

[Pharo 8.0] Build #154: 2776-Hitting-an-undefined-class-gives-a-debugger-with-misleading-message-new-was-sent-to-nil-2

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

There is a new Pharo build available! The status of the build #154 was: SUCCESS. The Pull Request #2893 was integrated: "2776-Hitting-an-undefined-class-gives-a-debugger-with-misleading-message-new-was-sent-to-nil-2" Pull request url: https://github.com/pharo-project/pharo/pull/2893 Issue Url: https://pharo.fogbugz.com/f/cases/2776 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2019

Re: [Pharo-dev] [Issue Trackker][Help Needed]: Move issues from Fogbugz to GitHub

by Marcus Denker

Hi, I think Cyril has some kind of tool? Yes, that might be interesting... > On 18 Mar 2019, at 19:26, Tim Mackinnon <tim(a)testit.works> wrote: > > Marcus - do we just manually copy over the title and description (and any relevant comments) - or is there some tool to do this with? > > Tim > >> On 18 Mar 2019, at 07:38, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> We should all look at the old issues: >> >> https://pharo.fogbugz.com/f/filters/57/All-newest-first <https://pharo.fogbugz.com/f/filters/57/All-newest-first> >> >> and move them to the new one: >> >> https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> >> >> instead of moving them automatically, we should take the chance to >> clean up. >> >> Please check, first for the issues that *you* added: >> >> -> is it still relevant? >> ->if yes: add a new issue on GitHub >> ->close this issue, there is now an explicit âmoved to GitHubâ state. >> >> >> Marcus >

March 19, 2019

Re: [Pharo-dev] Issue Tracker: enabled Projects (Boards)

by Marcus Denker

Hi, it seems that the account / access model of GitHub forces us to move the boards to the organisation level (where we can have a user group with write access for the boards). This means I will move them slowly to https://github.com/orgs/pharo-project/projects <https://github.com/orgs/pharo-project/projects> So lets treat all this as a testâ¦ as soon as it is really working I will send another mail. > On 18 Mar 2019, at 08:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We enabled the GitHub âProjectsâ feature for the pharo repo: > > https://github.com/pharo-project/pharo/projects > > > The idea is that one can add as many âKanbanâ style boards as one wants. > issues and pull requests can be added, as well as simple cards that are not yet issues. > > This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there > are >500 issues. > > With these boards, we can create âviewsâ on this sea of issues. > > I created for now: > > -> some board related to specific parts of the system (e.g. Traits or Reflectivity) > example: https://github.com/pharo-project/pharo/projects/11 > -> "Pharo7 Backportingâ > https://github.com/pharo-project/pharo/projects/12 > -> "Simple Issues for Beginnersâ > https://github.com/pharo-project/pharo/projects/14 > Here the feature to be able to put things that are not yet issue tracker entries seems very useful > > > I think this can be quite niceâ¦ we should add more Projects as soon as we find that they make sense > and should move issues there. > > Marcus

March 19, 2019

Re: [Pharo-dev] About a better filedialog

by Guillermo Polito

YES! On Mon, Mar 18, 2019 at 11:13 PM ducasse <stepharo(a)netcourrier.com> wrote: > Yes I had to rename ComposableModel into ComposablePresenter so this is > probably that > > On 18 Mar 2019, at 23:09, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Thanks Stef! > > The build is failing for Pharo 6.1 for some reason (I can't reproduce it > locally), but I can look at that during the weekend... > > Peter > > On Mon, Mar 18, 2019 at 9:23 PM ducasse <stepharo(a)netcourrier.com> wrote: > >> Alex >> >> Have a look at the one I propose and play with it. >> Let me know what you think. >> >> Stef >> >> On 18 Mar 2019, at 21:20, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >> >> >> *From: *Alexandre Bergel <alexandre.bergel(a)me.com> >> *Subject: **Re: [Pharo-dev] About a better filedialog* >> *Date: *18 March 2019 at 21:20:35 CET >> *To: *Pharo Development List <pharo-dev(a)lists.pharo.org> >> >> >> I do not have time to personally work on this. But yes, having a better >> file dialog would be fantastic >> >> Alexandre >> >> On Mar 18, 2019, at 4:31 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi guys >> >> I did a pass (ported to P7, tonel, some little fixes) on the file-dialog >> developed by Peter Uhnak and I think that it would be good to propose it by >> default in the image. >> what do you think? >> >> https://github.com/Ducasse/file-dialog >> >> I would also like that the filedialog remembers the last list of visited >> directory. (I will see if I can add this). >> When Spec2 is out I would like to port it to Spec2. >> >> Does anybody want to help? Because it would be super nice and Iâm full >> with cleaning textEditor and pluggableTextMorph. >> >> Stef >> >> >> >> >> >> >> >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 19, 2019

[Pharo 8.0] Build #153: 2879-removeInstVarNamed-on-MetaClass-needs-to-use-removeSlot-like-the-implementation-on-Class

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

There is a new Pharo build available! The status of the build #153 was: FAILURE. The Pull Request #2890 was integrated: "2879-removeInstVarNamed-on-MetaClass-needs-to-use-removeSlot-like-the-implementation-on-Class" Pull request url: https://github.com/pharo-project/pharo/pull/2890 Issue Url: https://pharo.fogbugz.com/f/cases/2879 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2019

[Pharo 8.0] Build #152: 2891-fix-whichSelectorsRead-and-whichSelectorsStoreInto-for-Slots

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

There is a new Pharo build available! The status of the build #152 was: SUCCESS. The Pull Request #2894 was integrated: "2891-fix-whichSelectorsRead-and-whichSelectorsStoreInto-for-Slots" Pull request url: https://github.com/pharo-project/pharo/pull/2894 Issue Url: https://pharo.fogbugz.com/f/cases/2891 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2019

[Pharo 8.0] Build #151: 2852-CodeCompletion-should-not-be-managed-via-common-tools-but-via-a-TextArea-registration

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

There is a new Pharo build available! The status of the build #151 was: SUCCESS. The Pull Request #2857 was integrated: "2852-CodeCompletion-should-not-be-managed-via-common-tools-but-via-a-TextArea-registration" Pull request url: https://github.com/pharo-project/pharo/pull/2857 Issue Url: https://pharo.fogbugz.com/f/cases/2852 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 18, 2019