- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1284: 21805-FFICompilerPlugin-is-not-anymore-activated

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

There is a new Pharo build available! The status of the build #1284 was: FAILURE. The Pull Request #1842 was integrated: "21805-FFICompilerPlugin-is-not-anymore-activated" Pull request url: https://github.com/pharo-project/pharo/pull/1842 Issue Url: https://pharo.fogbugz.com/f/cases/21805 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 1, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 24 September 2018

by Esteban Lorenzano

Ah yes, this seems a bit empty this week :) Reason is that Iâm working on some cleans on Calypso and additions to Iceberg, but I didnât finish any to announce it in the changelog ;) I hope to finish them this week :P Esteban > On 1 Oct 2018, at 08:00, estebanlm(a)gmail.com wrote: > > Hello! > > This is my weekly ChangeLog, from 24 September 2018 to 30 September 2018. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=24/9/2018&to=30/9/2018 > > ChangeLog > ========= > > 28 September 2018: > ------------------ > > * I submited a [PR for smalltalkCI](https://github.com/hpi-swa/smalltalkCI/pull/398) to handle onConflict/onUpgrade metacello options. > > This will allow us to test projects that are already loaded into the image (like Calypso, > for example) > > > cheers! > Esteban

Oct. 1, 2018

[Pharo 7.0-dev] Build #1283: 22399-packagesAffected-in-class-renames-does-not-honor-extension-methods

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

There is a new Pharo build available! The status of the build #1283 was: FAILURE. The Pull Request #1756 was integrated: "22399-packagesAffected-in-class-renames-does-not-honor-extension-methods" Pull request url: https://github.com/pharo-project/pharo/pull/1756 Issue Url: https://pharo.fogbugz.com/f/cases/22399 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 1, 2018

[Pharo 7.0-dev] Build #1282: 22496-ButtonPresenter-should-be-initialized-with-default-theme-color

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

There is a new Pharo build available! The status of the build #1282 was: SUCCESS. The Pull Request #1836 was integrated: "22496-ButtonPresenter-should-be-initialized-with-default-theme-color" Pull request url: https://github.com/pharo-project/pharo/pull/1836 Issue Url: https://pharo.fogbugz.com/f/cases/22496 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 1, 2018

Esteban's ChangeLog week of 24 September 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 24 September 2018 to 30 September 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=24/9/2018&to=30/9/2018 ChangeLog ========= 28 September 2018: ------------------ * I submited a [PR for smalltalkCI](https://github.com/hpi-swa/smalltalkCI/pull/398) to handle onConflict/onUpgrade metacello options. This will allow us to test projects that are already loaded into the image (like Calypso, for example) cheers! Esteban

Oct. 1, 2018

[Pharo 7.0-dev] Build #1281: 22433-Review-FloatTest-testCopySignTo-and-testSign

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

There is a new Pharo build available! The status of the build #1281 was: SUCCESS. The Pull Request #1835 was integrated: "22433-Review-FloatTest-testCopySignTo-and-testSign" Pull request url: https://github.com/pharo-project/pharo/pull/1835 Issue Url: https://pharo.fogbugz.com/f/cases/22433 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 30, 2018

[Pharo 7.0-dev] Build #1280: 22489-cleanup--CompilationContext-and-doSemanticAnalysis

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

There is a new Pharo build available! The status of the build #1280 was: SUCCESS. The Pull Request #1830 was integrated: "22489-cleanup--CompilationContext-and-doSemanticAnalysis" Pull request url: https://github.com/pharo-project/pharo/pull/1830 Issue Url: https://pharo.fogbugz.com/f/cases/22489 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 30, 2018

[Pharo 7.0-dev] Build #1279: 22498-TextEditorsaveContentsInFile-should-not-use-FileStream

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

There is a new Pharo build available! The status of the build #1279 was: FAILURE. The Pull Request #1839 was integrated: "22498-TextEditorsaveContentsInFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1839 Issue Url: https://pharo.fogbugz.com/f/cases/22498 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 30, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Success story Mobility Map

by Pierce Ng

On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote: >>> And a lot more. This is a coarse grained overview over the >>> architecture. Iâm happy to answer further questions about this. >>> [very nice writeup] Hi Norbert, Very nice write-up, thanks. What persistence mechanism are you using - Gemstone/S, Glorp, Voyage, ...? Pierce

Sept. 30, 2018

Re: [Pharo-dev] [ANN] Migrated Artefact to GitHub

by Stephane Ducasse

Thanks norbert. I accept your apologies. Stef On Sat, Sep 29, 2018 at 8:39 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi Peter > > Just a note to say that I appretiate your attitude and we know it each other. > I will try to use your tool when I will migrate my projects. > > Stef > > On Sat, Sep 29, 2018 at 2:32 PM Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >> > >> - you're stealing > > > > > > Sorry, I absolutely did not intend the evoke the notion of "stealing". > > My perspective is... I am spending time to migrate someone else's code, so the last thing I want is someone burning my energy and complaining that I voided their contribution. > > > > I don't give a fuck if someone migrates my contribution and strips the authorship (and when I do care I don't need to rely on others to prove it). > > But I want to cover my ass from backlash from other people, because I know it will happen and I know that people will complain (which is exactly what happened to you). > > > > So preventing the appropriation of code is not about you taking credit for other person's code, but you being covered from them accusing you of it. (It probably sounds like I am pathologically defensive, but dealing with people is exhausting for me.) > > > >> > >>> * it is sending bad signals to potential contributors that we can scrub them anytime we want > >>> > >>> as you yourself have said: > >>> > @People try to avoid to piss on good will of others. > >>> Yet this is what it feels like to some when traces of their contributions are voided. > >> > >> > >> And this is my third point. This "stealing" idea is mainly a matter of manners. > > > > > > Again, I didn't intend "stealing". It's about preventing people from thinking "They don't give a fuck about their contributors, so why I should give a fuck about contributing?". It can be dispiriting for them, even if they don't care about the code itself. And they will complain... and who needs that? > > > >> If instead of bashing on people, we wanted to discuss on how to actually FIX the thing, here are my 2 cents: > >> - From a copyright perspective it should have been enough to check the licence file and name the contributors there > > > > > > But nobody uses the license file for that, usually there's only the original author(s) / main maintainer(s). That's why the (git) history is relevant. > > > >> > >> - The history could have been retrieved in a separate branch and then merged (and look, we had the best of the two worlds!) > >> > >> - both of the things could have been then integrated through a pull request (luckily in less than one hour :)) > > > > > > Yep. > > > >> > >> And at the end, with the apport of everybody we could have got a repository with history, baseline and working on pharo 7. > >> > >> Now, from a human perspective, please let's try everybody to assume the best of the other by default. > >> That will just make all interactions much more healthy. > >> > >> And please, this is not particularly directed to anybody, I've seen such remarks many times. Let's just think positive. > >> Problems can be fixed if we talk about them, but more specifically if we are looking for solutions. > > > > > > I will see how I can streamline the tool even further... maybe a service that will migrate entire smalltalkhub :) > > > > Peter

Sept. 30, 2018