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

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

by Marcus Denker

> On 19 Mar 2019, at 12:22, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > The GitHub criteria is that issue reporters are not the ones that can distribute/label/recognise the areas of the reported issue, and that should be done by âadminsâ. > > I wonder if instead trying to fix the issue, we couldnât first check if thatâs an actual issue? I mean: maybe they have a point and we shouldnât ask people to know what area of effect is the problem they are reporting. > Does it make sense to have boards if only I use them? For sure notâ¦ e.g. Steven wants to use the Reflectivity board. I now added to to the organisation instead, created a Team for Kanban boards, added him there and now he can edit https://github.com/orgs/pharo-project/projects/7 > Esteban > >> On 19 Mar 2019, at 11:06, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@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 <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 <mailto:marcus.denker@inria.fr>> wrote: >>> >>> Hi, >>> >>> We enabled the GitHub âProjectsâ feature for the pharo repo: >>> >>> https://github.com/pharo-project/pharo/projects <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 <https://github.com/pharo-project/pharo/projects/11> >>> -> "Pharo7 Backportingâ >>> https://github.com/pharo-project/pharo/projects/12 <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] Issue Tracker: enabled Projects (Boards)

by Marcus Denker

Yes, it can not be completely public or it will be vandalised. > On 19 Mar 2019, at 12:17, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > 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 <mailto:marcus.denker@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 <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 <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> We enabled the GitHub âProjectsâ feature for the pharo repo: >> >> https://github.com/pharo-project/pharo/projects <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 <https://github.com/pharo-project/pharo/projects/11> >> -> "Pharo7 Backportingâ >> https://github.com/pharo-project/pharo/projects/12 <https://github.com/pharo-project/pharo/projects/12> >> -> "Simple Issues for Beginnersâ >> https://github.com/pharo-project/pharo/projects/14 <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 <https://twitter.com/SergeStinckwich> > â

March 19, 2019

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

by Tim Mackinnon

Yes point taken, should have mentioned - I will review all mine and close obsolete ones first. Sent from my iPhone > On 19 Mar 2019, at 11:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > I do not like that tool :) > > PLEASE do not blindly move issues from FogBugz to GitHub, if that would have been our purpose we would have done it! > > Migrate the issues that are relevant for you. And for relevant I mean: Just the ones that you actually find in P7-8. > > Thing isâ¦ many of those issues are no longer relevant (because of many things). > > Esteban > >> On 19 Mar 2019, at 12:12, Tim Mackinnon <tim(a)testit.works> wrote: >> >> 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> 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> wrote: >>>>> >>>>> Hi, >>>>> >>>>> We should all look at the old issues: >>>>> >>>>> https://pharo.fogbugz.com/f/filters/57/All-newest-first >>>>> >>>>> and move them to the new one: >>>>> >>>>> 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 Esteban Lorenzano

The GitHub criteria is that issue reporters are not the ones that can distribute/label/recognise the areas of the reported issue, and that should be done by âadminsâ. I wonder if instead trying to fix the issue, we couldnât first check if thatâs an actual issue? I mean: maybe they have a point and we shouldnât ask people to know what area of effect is the problem they are reporting. Esteban > On 19 Mar 2019, at 11:06, 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 <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 <mailto:marcus.denker@inria.fr>> wrote: >> >> Hi, >> >> We enabled the GitHub âProjectsâ feature for the pharo repo: >> >> https://github.com/pharo-project/pharo/projects <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] [Issue Trackker][Help Needed]: Move issues from Fogbugz to GitHub

by Esteban Lorenzano

I do not like that tool :) PLEASE do not blindly move issues from FogBugz to GitHub, if that would have been our purpose we would have done it! Migrate the issues that are relevant for you. And for relevant I mean: Just the ones that you actually find in P7-8. Thing isâ¦ many of those issues are no longer relevant (because of many things). Esteban > On 19 Mar 2019, at 12:12, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes - Cyril is a tool meisterâ¦. ;) > >> On 19 Mar 2019, at 10:08, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@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

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