Re: [Pharo-dev] Writeup: how to contribute to Pharo

Le ven. 11 août 2017 à 00:53, Nicolai Hess a écrit : > 2017-08-10 17:17 GMT+02:00 Guillermo Polito : > >> Hi, >> >> I've made some write up for the pharo part (not metacello or external >> projects) >> >> >>

[Pharo-dev] Launcher Error w Pharo 7

I just downloaded Launcher for Mac via the CI. I created a Pharo 7 image and launched it. The following error came up: "Error: External module not found" from libgit2_init. I assume it's because libgit2 is not installed on my system. If that's right, how do I set it up e.g. What's the best way to

Re: [Pharo-dev] Writeup: how to contribute to Pharo

2017-08-10 17:17 GMT+02:00 Guillermo Polito : > Hi, > > I've made some write up for the pharo part (not metacello or external > projects) > > https://github.com/guillep/PharoIntegrationProcess/wiki/Cont > ribute-a-fix-to-Pharo > > Of course, expect bugs on it :) Not

Re: [Pharo-dev] Writeup: how to contribute to Pharo

2017-08-10 17:17 GMT+02:00 Guillermo Polito : > Hi, > > I've made some write up for the pharo part (not metacello or external > projects) > > https://github.com/guillep/PharoIntegrationProcess/wiki/Cont > ribute-a-fix-to-Pharo > > Of course, expect bugs on it :) Not

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Am 11.08.2017 12:02 vorm. schrieb "Cyril Ferlicot D." < cyril.ferli...@gmail.com>: Le 10/08/2017 à 23:58, Nicolai Hess a écrit : > > What does "clone using sourcetree" mean? > > IIRC SourceTree is a Git GUI available on Windows, as GitKraken, SmartGit, GitExtensions, TortoiseGit… Ok, so I can

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Le 10/08/2017 à 23:58, Nicolai Hess a écrit : > > What does "clone using sourcetree" mean? > > IIRC SourceTree is a Git GUI available on Windows, as GitKraken, SmartGit, GitExtensions, TortoiseGit… -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01,

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Am 10.08.2017 11:21 nachm. schrieb "Guillermo Polito" < guillermopol...@gmail.com>: On Thu, Aug 10, 2017 at 9:39 PM, Torsten Bergmann wrote: > Hi Guille, > > nice writeup and definitely needed. Thanks a lot! > > If possible you should complete it with: > - how Windows users

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Tx this is really good and I will use it to produce new clean images to work on Pharo 70 On Thu, Aug 10, 2017 at 5:17 PM, Guillermo Polito wrote: > Hi, > > I've made some write up for the pharo part (not metacello or external > projects) > >

Re: [Pharo-dev] Writeup: how to contribute to Pharo

On Thu, Aug 10, 2017 at 9:39 PM, Torsten Bergmann wrote: > Hi Guille, > > nice writeup and definitely needed. Thanks a lot! > > If possible you should complete it with: > - how Windows users could contribute > Hard topic. I'm taking benefit of my gf's windows computer right now

Re: [Pharo-dev] [Pharo-users] [ann] moldable brick editor - alpha

Thanks Stef! Doru > On Aug 10, 2017, at 11:52 AM, Stephane Ducasse > wrote: > > Hi alex > > I added > https://pharo.fogbugz.com/f/cases/20298/Check-and-remove-Athens-dependency-from-OSWindow > But it would be better that you enter bug entry and not me because IT

Re: [Pharo-dev] FileSystem fix integration

Hi Stef, On Wed, Aug 09, 2017 at 10:12:17PM +0200, Stephane Ducasse wrote: > Hi alistair > > I went on fogbugz to find the fix to be included and I'm not sure not > that find them. > I looked for FileSystem. > > I found > -

Re: [Pharo-dev] FileSystem fix integration

Hi Stef, On Wed, Aug 09, 2017 at 08:23:50PM +0200, Stephane Ducasse wrote: > Tx! > So that I do not make mistake: > The fix is the second solution. Now do we have somewhere the first one? See below... > On Wed, Aug 9, 2017 at 10:08 AM, Denis Kudriashov > wrote: > > Hi >

Re: [Pharo-dev] Writeup: how to contribute to Pharo

Hi Guille, nice writeup and definitely needed. Thanks a lot!   If possible you should complete it with:  - how Windows users could contribute    -  that #development branch is used instead of master   - how one can keep his own fork up to date Also it would be good to have the AboutBox in

Re: [Pharo-dev] Spec menu extensibility (epicea)

Tx eliot for sharing your experience with us. I will keep that in mind (I decided that I should not start something new before finishing something) So frustrating to have many not finished items. Stef On Thu, Aug 10, 2017 at 7:39 PM, Eliot Miranda wrote: > Hi Peter, > >

Re: [Pharo-dev] Spec menu extensibility (epicea)

Hi Peter, On Thu, Aug 10, 2017 at 12:48 AM, Peter Uhnak wrote: > Hi Stef, > > I use both a variant with an argument and without, however I have slightly > modified PragmaMenuBuilder to support this. > > e.g. I have > > which always adds entries to a particular menu. > which

Re: [Pharo-dev] Updating the CI

This is done. Everything is working well. I closed the issue. https://pharo.fogbugz.com/f/cases/edit/20299/ On Thu, Aug 10, 2017 at 11:56 AM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi all, > > I'm updating some CI plugins right now. Will notify as soon as everything > is smooth

[Pharo-dev] Writeup: how to contribute to Pharo

Hi, I've made some write up for the pharo part (not metacello or external projects) https://github.com/guillep/PharoIntegrationProcess/wiki/ Contribute-a-fix-to-Pharo Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. Guille -- Guille Polito

Re: [Pharo-dev] Impediment to contributing

Hi, I've made some write up for the pharo part (not metacello or external projects) https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo Of course, expect bugs on it :) Not everything is smooth. If you have comments, they are welcome. Guille On Thu, Aug 10, 2017

[Pharo-dev] Impediment to contributing

I feel frustrated, and blocked in contributing. I miss up to date information on how to cleanly install Pharo so that I can use Iceberg with Metacello, and the process to use to contribute to both Pharo itself and to the different projects on github. Every time I try to do something that comes

[Pharo-dev] [Pharo 70] build 25 / PR 182

Hi, next Pharo 7 build is available: https://pharo.fogbugz.com/f/cases/20286/Bootstrap- packages-are-dirty-in-a-fresh-image https://github.com/pharo-project/pharo/pull/182 -- Pavel

Re: [Pharo-dev] post-download preparation of Pharo 7 image

On Thu, Aug 10, 2017 at 11:55 AM, Pavel Krivanek wrote: > Hi, > > currently we are fighting with several issues that make contributions to > Pharo 7 much more complicated than we would like. Even in case you have no > troubles with long paths (on Windows) nor SSH keys,

[Pharo-dev] post-download preparation of Pharo 7 image

Hi, currently we are fighting with several issues that make contributions to Pharo 7 much more complicated than we would like. Even in case you have no troubles with long paths (on Windows) nor SSH keys, it is now not easy now to start to contribute or review pull requests. Let's say you already

[Pharo-dev] Updating the CI

Hi all, I'm updating some CI plugins right now. Will notify as soon as everything is smooth again. The issue related to the update is here: https://pharo.fogbugz.com/f/cases/20299/Update-CI-plugins-to-latest-git-plugins (yes, we have an issue so we can keep track of the plugins we have) --

[Pharo-dev] [ Pharo 70 ] build 24 / PR 188

This PR is only jenkins related, it does not modify any pharo code. https://pharo.fogbugz.com/f/cases/20297/Avoid-deadlocks-in-jenkins https://github.com/pharo-project/pharo/pull/188 It produced build 24. Build artifacts in here: http://files.pharo.org/image/70/ -- Guille Polito Research

[Pharo-dev] [ Pharo 70 ] build 23 / PR 132

Hi https://pharo.fogbugz.com/f/cases/17848/SequenciableCollection-first-raise-an-Error-if-the-collection-if-too-small https://github.com/pharo-project/pharo/pull/132 Stef

Re: [Pharo-dev] FileSystem fix integration

Tx On Thu, Aug 10, 2017 at 7:21 AM, Alistair Grant wrote: > Hi Stef, > > On Wed, Aug 09, 2017 at 08:23:50PM +0200, Stephane Ducasse wrote: >> Tx! >> So that I do not make mistake: >> The fix is the second solution. Now do we have somewhere the first one? > > Not yet. My

Re: [Pharo-dev] Spec menu extensibility (epicea)

Since we can get the method and from the method the class I would not put the context:. On Thu, Aug 10, 2017 at 9:48 AM, Peter Uhnak wrote: > Hi Stef, > > I use both a variant with an argument and without, however I have slightly > modified PragmaMenuBuilder to support this.

Re: [Pharo-dev] [Pharo 70] build 19 / PR-168

:) Yes I launch a rebuild. On Wed, Aug 9, 2017 at 10:40 PM, Guillermo Polito wrote: > Probably you already saw it, but builds are green again. As I told you > this afternoon, there are some hiccups that cause failures from time to > time. We should chase them one by

[Pharo-dev] [Pharo 70] Build 22 / PR 169

Build 22 https://github.com/pharo-project/pharo/pull/169 https://pharo.fogbugz.com/f/cases/20249/Add-some-colors-to-the-themes

Re: [Pharo-dev] Pull requests ready to be reviewed

This is great to see the workflow start to emerge. I guess all PRs tagged with human-review-needed are the one to take care ? https://github.com/pharo-project/pharo/pulls?q=is%3Apr+is%3Aopen+label%3Ahuman-review-needed On Wed, Aug 9, 2017 at 10:09 AM, Pavel Krivanek

Re: [Pharo-dev] Spec menu extensibility (epicea)

Hi Stef, I use both a variant with an argument and without, however I have slightly modified PragmaMenuBuilder to support this. e.g. I have which always adds entries to a particular menu. which adds entries only when some particular context is active (here it would mean that the items are