- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] make github issues clearer?

by Marcus Denker

I can tell you that it is even hard for me to understand some issue tracker entries. We really need to find a way that people add better information. For me one thing I will try to do: to not use the issue tracker anymore as my private TODO list. This means that the âI should maybe look into this but i have no time to even add a descriptionâ entries are now in my private list and if I make an issue on the issue tracker I will try to write it in a way that it explains how someone else could fix it. Marcus > On 4 Nov 2019, at 07:16, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > This is it. > > Finally this problem is spotted. It's been years since I read a Pharo issue because of their targeted "narrative" to a bunch of 5 - 10 people who share a daily operational knowledge. This is more severe with the VM front. > > Other communities, like R, use a lot minimum reproducible example (MRE). So nothing new should be invented here, if Pharo just could adopt one of the standard practices... > > Cheers, > > HernÃ¡n > > > > El mar., 29 oct. 2019 a las 8:56, Torsten Bergmann (<astares(a)gmx.de <mailto:astares@gmx.de>>) escribiÃ³: > +1000 > > I've seen this several times that issues where just a short title only "wizards" were able to understand > > The "Full description requires time" is not an argument here. We all should get more professional > and disciplined here - so anyone is able to reproduce and understand what an issue is about. This will > also increase the trust into Pharo and its dev process... > > Bye > T.

Nov. 4, 2019

Re: [Pharo-dev] make github issues clearer?

by HernÃ¡n Morales Durand

This is it. Finally this problem is spotted. It's been years since I read a Pharo issue because of their targeted "narrative" to a bunch of 5 - 10 people who share a daily operational knowledge. This is more severe with the VM front. Other communities, like R, use a lot minimum reproducible example (MRE). So nothing new should be invented here, if Pharo just could adopt one of the standard practices... Cheers, HernÃ¡n El mar., 29 oct. 2019 a las 8:56, Torsten Bergmann (<astares(a)gmx.de>) escribiÃ³: > +1000 > > I've seen this several times that issues where just a short title only > "wizards" were able to understand > > The "Full description requires time" is not an argument here. We all > should get more professional > and disciplined here - so anyone is able to reproduce and understand what > an issue is about. This will > also increase the trust into Pharo and its dev process... > > Bye > T. >

Nov. 4, 2019

Re: [Pharo-dev] I love this idea: learning by doing...

by ducasse

> On 3 Nov 2019, at 11:10, Hilaire <hilaire(a)drgeo.eu> wrote: > > There were some game frameworks project goings on with Pharo. > > What are their status? I never finished to have a look and produce something that could be used by others. Coding is just a part of the story. Explaining and presenting is the part that is often missing. > > Hilaire > > Le 03/11/2019 Ã 09:53, ducasse a Ã©crit : >> https://github.com/danistefanovic/build-your-own-x >> >> I would love to get some pharo there. >> >> Thanks sebastian for the pointer. >> >> Stef >> >> > -- > Dr. Geo > http://drgeo.eu > > >

Nov. 3, 2019

Re: [Pharo-dev] I love this idea: learning by doing...

by Hilaire

There were some game frameworks project goings on with Pharo. What are their status? Hilaire Le 03/11/2019 Ã 09:53, ducasse a Ã©critÂ : > https://github.com/danistefanovic/build-your-own-x > > I would love to get some pharo there. > > Thanks sebastian for the pointer. > > Stef > > -- Dr. Geo http://drgeo.eu

Nov. 3, 2019

I love this idea: learning by doing...

by ducasse

https://github.com/danistefanovic/build-your-own-x I would love to get some pharo there. Thanks sebastian for the pointer. Stef

Nov. 3, 2019