- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #923: 4481-Copying-class-does-not-copy-class-comment
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2019

Oct. 30, 2019

There is a new Pharo build available! The status of the build #923 was: SUCCESS. The Pull Request #5026 was integrated: "4481-Copying-class-does-not-copy-class-comment" Pull request url: https://github.com/pharo-project/pharo/pull/5026 Issue Url: https://github.com/pharo-project/pharo/issues/4481 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #922: Executable Comments in Number
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2019

Oct. 30, 2019

There is a new Pharo build available! The status of the build #922 was: FAILURE. The Pull Request #5035 was integrated: "Executable Comments in Number" Pull request url: https://github.com/pharo-project/pharo/pull/5035 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #921: Use NECEntry
by ci-pharo-ci-jenkins2＠inria.fr Oct. 30, 2019

Oct. 30, 2019

There is a new Pharo build available! The status of the build #921 was: FAILURE. The Pull Request #5033 was integrated: "Use NECEntry" Pull request url: https://github.com/pharo-project/pharo/pull/5033 Issue Url: https://github.com/pharo-project/pharo/issues/UseNECEntry Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

PLZ fix it for Pharo8...
by Casimiro de Almeida Barreto Oct. 29, 2019

Oct. 29, 2019

In the last builds of Pharo8, CatalogBrowser comes with an easily fixable glitch... Please could someone take a look? My humble suggestion is: =============================================================== createRepositoryURLtoNameMappings Â Â Â "Return a mapping between repositories URLs and their user names" Â Â Â <script: 'self createRepositoryURLtoNameMappings inspect'> Â Â Â |repos| Â Â Â repos := Dictionary new.Â Â Â Â Â Â 3 to: SystemVersion current major do: [:v | Â Â Â Â Â Â repos Â Â Â Â Â Â Â Â Â Â Â Â at: ('http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo{1}0/main' format: (Array with: v)) Â Â Â Â Â Â Â Â Â put: ('Pharo{1}.0' format: (Array with: v)]. Â Â Â repos at: 'http://www.squeaksource.com/MetacelloRepository' put: 'Unsorted'.Â Â Â Â Â Â Â Â Â ^repos ================================================================ Best wishes, Casimiro Barreto

3 2

Re: [Pharo-dev] make github issues clearer?
by Gabriel Cotelli Oct. 29, 2019

Oct. 29, 2019

Hi! I think one of the problems is that not everybody can set labels. I've created a lot of issues but the only thing I can do is to set the description and title, even if I already know if it's a bug or feature, or the Pharo version it affects. For ba-st projects we have a set of standardized labels (see for example https://github.com/ba-st/Stargate/labels) and using it in every project makes it easy to filter them. AFAIR the permissions on GitHub are pretty crappy, so I think it's not possible to give permissions to external collaborators to change labels on issues without giving it write permissions over the repository. In any case having templates for bugs and feature issues sounds like a good idea. And I love the option to not have to open an issue if I will immediately provide a PR with code, because this avoids duplicating the discussion in two places. Best, Gabriel On Mon, Oct 28, 2019 at 7:13 PM Myroslava Romaniuk via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hi everyone > > Maybe it makes sense to generate some github issue templates and encourage > people to fill in the related information from a prompt? I think with bug > reports the situation is better, but for feature requests the state of > things could be very much improved by adding a template that goes: > "describe problem", "describe solution you'd like", "other alternatives", > "additional context". > > Because right now github issues are a mess. I get it that some projects > have particular maintainers and they know what the issues are and the > phrasing doesn't matter, ok, but a lot of the issues that don't have a tie > to any particular project and are labeled "easy" or "beginner" take a while > to understand because you have no idea what the person who created the > issue actually means. > > Just a suggestion, but i think there's really a lot of room to improve > with labels and templates for issues, and make them more accessible to > outsiders. > > Best, > Myroslava >

1 0

Re: [Pharo-dev] make github issues clearer?
by Nicolas Cellier Oct. 29, 2019

Oct. 29, 2019

+1 for improving the issues. I call that the "checkbox attitude": Opening an issue is mandatory for a change to be merged? No problem, i open an issue (just a title), check the box, et voilÃ ... That's applying the letter of the law rather than the spirit of the law. Either the law is bad (too cumbersome for trivial changes?), or we are at degree zero of quality... I also call that quality-dry: It has the color of quality, the smell of quality, but it's not quality ;) Le lun. 28 oct. 2019 Ã 23:12, Myroslava Romaniuk via Pharo-dev < pharo-dev(a)lists.pharo.org> a Ã©crit : > Hi everyone > > Maybe it makes sense to generate some github issue templates and encourage > people to fill in the related information from a prompt? I think with bug > reports the situation is better, but for feature requests the state of > things could be very much improved by adding a template that goes: > "describe problem", "describe solution you'd like", "other alternatives", > "additional context". > > Because right now github issues are a mess. I get it that some projects > have particular maintainers and they know what the issues are and the > phrasing doesn't matter, ok, but a lot of the issues that don't have a tie > to any particular project and are labeled "easy" or "beginner" take a while > to understand because you have no idea what the person who created the > issue actually means. > > Just a suggestion, but i think there's really a lot of room to improve > with labels and templates for issues, and make them more accessible to > outsiders. > > Best, > Myroslava >

3 3

FOSDEM rooms are available
by ducasse Oct. 29, 2019

Oct. 29, 2019

https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ I do not know in which one we want to participate Debugging Tools Minimalistic, Experimental and Emerging Languages Open Research Tools and Technologies How do we coordinate? S.

4 6

make github issues clearer?
by Myroslava Romaniuk Oct. 28, 2019

Oct. 28, 2019

Hi everyone Maybe it makes sense to generate some github issue templates and encourage people to fill in the related information from a prompt? I think with bug reports the situation is better, but for feature requests the state of things could be very much improved by adding a template that goes: "describe problem", "describe solution you'd like", "other alternatives", "additional context". Because right now github issues are a mess. I get it that some projects have particular maintainers and they know what the issues are and the phrasing doesn't matter, ok, but a lot of the issues that don't have a tie to any particular project and are labeled "easy" or "beginner" take a while to understand because you have no idea what the person who created the issue actually means. Just a suggestion, but i think there's really a lot of room to improve with labels and templates for issues, and make them more accessible to outsiders. Best, Myroslava

1 0

[Pharo 8.0] Build #920: Allow-to-use-boolean-with-sort-functions
by ci-pharo-ci-jenkins2＠inria.fr Oct. 28, 2019

Oct. 28, 2019

There is a new Pharo build available! The status of the build #920 was: SUCCESS. The Pull Request #5023 was integrated: "Allow-to-use-boolean-with-sort-functions" Pull request url: https://github.com/pharo-project/pharo/pull/5023 Issue Url: https://github.com/pharo-project/pharo/issues/Allow Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #919: Update Tonel to v1.0.15
by ci-pharo-ci-jenkins2＠inria.fr Oct. 28, 2019

Oct. 28, 2019

There is a new Pharo build available! The status of the build #919 was: SUCCESS. The Pull Request #5022 was integrated: "Update Tonel to v1.0.15" Pull request url: https://github.com/pharo-project/pharo/pull/5022 Issue Url: https://github.com/pharo-project/pharo/issues/update Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0