[Pharo-dev] [ann] moldable editor - documenter and examples without pragma magic

[Tudor Girba]

Hi,

When we announced the GT Documenter as an application for the moldable editor, 
one of the remarks was that GT Examples implementation relies too much on 
pragma magic.

We are now happy to announce that this is no longer the case because Andrei did 
a great job and rebuilt examples without the need for static pragmas for 
specifying dependencies.

So, now we can example dependencies simply through normal calls:

emptyView

^ GtMondrian new

twoNodes

view := self emptyView
view nodes with: {1 . 2}

... and the engine can figure out the static dependencies. This means that 
examples can be used both as plain unary methods, and as replacement for tests. 
We think this should address the worry of examples being too heavy (the current 
implementation is ~350 lines).

With a bit of extra effort, we also adapted GT Documenter to expand the example 
dependencies as seen below. This means that examples can now be used directly 
as units of documentation as well.

We think this is significant.



Cheers,
The feenk team


--
www.tudorgirba.com
www.feenk.com

"We are all great at making mistakes."

Re: [Pharo-dev] BOF at ESUG - How about a BOF on Gemstone development environments?

[Stephane Ducasse]

Tim guille will do a presentation about the new process and esteban
one on Iceberg
and we should really release videos.

stef

On Fri, Sep 1, 2017 at 1:43 PM, Tim Mackinnon  wrote:
> I'm envious as I couldn't make it to Esug - but I'd love to hear any 
> conclusions/insights from that  bof. Iceberg/git is such a transformative 
> step that we need all the knowledge spread we can get.
>
> Tim
>
> Sent from my iPhone
>
>> On 1 Sep 2017, at 12:40, Reg Krock via Pharo-dev  
>> wrote:
>>
>> 
>
>

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

[Stephane Ducasse]

I know your feelings. I got a bad time back in July on my mac.
Iceberg blew up on me on anything I tried.
So I did something else and waited for a better version.

On Fri, Sep 1, 2017 at 5:54 PM, Nicolai Hess  wrote:

>
>
> 2017-08-31 20:05 GMT+02:00 Stephane Ducasse :
>
>> Hi nicolai
>>
>> here is what I do.
>> I always download the latest image via a bash script because updating can
>> fail since loading package without a baseline may break.
>>
>> After I use the set up described by guille blog post and I reuse my
>> downloaded clone (to avoid to trash my SSD).
>>
>> Esteban told me that he will do a video:
>> - for producing a PR
>> - for reviewing
>>
>> Stef
>>
>
> Thanks, that would be great. looking forward to it, but for now I think I
> will quit trying this. It is too frustrating. I can not even try to explore
> icebergs functionality because it is crashing all the time.
>
>
>
>
>>
>> On Thu, Aug 31, 2017 at 12:06 AM, Nicolai Hess 
>> wrote:
>>
>>> Hi,
>>>
>>> I am now able to use iceberg on windows, thanks for the help.
>>>
>>> But I am still a bit unsure about how the review and contribution
>>> workflow should work.
>>>
>>> up to pharo 6 I just load a latest image,
>>> - load the slice from a fogbugz number and was able to review the change
>>> - or create a slice and upload it to the inbox
>>>
>>> in pharo 7
>>> - what is the equivalent to "getting the latest image" (and being able
>>> to load and review a fix),
>>>up to pharo 6 I just
>>> - load the latest image in pharolauncher (or from the command line).
>>> - opened the inbox repository.
>>> - load and review change/fix
>>> - throw away this change (close image without save)
>>> - reopen that image to move on with the next item to review.
>>>
>>> But now, do I have to update my local branch for every new pull
>>> request ? And how do I do this ? In other git project I would, I would
>>> fetch upstream, checkout master, merge with upstream/master, push
>>> the master to my fork origin
>>>How should this be done with my pharo 7 fork ? (And do we only work
>>> on the development brach instead of the master)?
>>>
>>>And do I this only in the command line or do I manage my fork (and
>>> keep it up to date) from within pharo with iceberg ?
>>>How do I actually access the pull requests from within pharo ? Maybe
>>> I am stupid, but I just can not find it.
>>>I would like do this steps, (as I was used to it from the prior
>>> contribution process, by loading code from the inbox)
>>>- Just look at the changes
>>>- apply the changes
>>>- throw away this changes, and move one with the next fix review
>>>
>>> And the same for creating a fix / pull request. Do I need to be up to
>>> date with my own fork, or only the local copy of the pharo repository ?
>>> Again, for pharo 6 I would just load a latest image, make my changes /
>>> code fixes and create a slice. Save to the inbox -> done.
>>> And looking at iceberg, I have really no clue how to upload a fix.
>>>
>>> I see that other people are using the new process, and I feel a bit lost
>>> and closed out of the pharo 7 development process, as I am at the moment
>>> unable to understand how this work.
>>> Are there any other resources I missed ?
>>>
>>>
>>>
>>>
>>> 2017-08-11 19:30 GMT+02:00 Stephane Ducasse :
>>>
 Nicolai

 I started super simple. I clone and point my fresh dled image to the
 use the clone.
 Then I can do simple PR and review the issues.
 I will do the installation several times to learn (but not clone).

 I'm not sure that it is needed but I have
 cd   /Users/ducasse/Library/Preferences/pharo/7.0

 StartupPreferencesLoader default executeAtomicItems: {
 StartupAction
 name: 'Git Settings'
 code: [
 FileStream stdout
 cr; nextPutAll: 'Setting the ssh
 credentials'; cr.
 Iceberg enableMetacelloIntegration: true.
 IceCredentialsProvider useCustomSsh: true.
 IceCredentialsProvider sshCredentials
 username: 'git';
 publicKey:
 '/Users/ducasse/.ssh/id_rsa.pub';
 privateKey:
 '/Users/ducasse/.ssh/id_rsa'.
 IceCredentialsProvider
 plaintextCredentials:
 (IcePlaintextCredentials new username: 'Ducasse'; password: '' ;
 yourself ).
 FileStream stdout
 cr; nextPutAll: 'Finished'; cr ].
 }.



 On Fri, Aug 11, 2017 at 9:46 AM, Guillermo Polito <
 guillermopol...@gmail.com> wrote:

> I extended 

Re: [Pharo-dev] review pull request changes view

[Stephane Ducasse]

How?


On Fri, Sep 1, 2017 at 5:56 PM, Esteban Lorenzano  wrote:
>
> On 1 Sep 2017, at 17:47, Nicolai Hess  wrote:
>
>
>
> 2017-09-01 17:44 GMT+02:00 Esteban Lorenzano :
>>
>>
>> On 1 Sep 2017, at 17:18, Nicolai Hess  wrote:
>>
>>
>>
>> 2017-09-01 17:11 GMT+02:00 Esteban Lorenzano :
>>>
>>>
>>> On 1 Sep 2017, at 17:06, Cyril Ferlicot  wrote:
>>>
>>>
>>>
>>> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess 
>>> wrote:


 Oh no!

 Now iceberg shows an empty list. Where is the pharo repository gone ?
 It took me a week to be at this point :(

 I reenabled the setting "Include system repositories by default", but
 still, the window is empty:

 


 How can I get back the system repository ?
>>>
>>>
>>> I'm not 100% sure but I think you just need to click on "add local
>>> repository", point the pharo clone and add src as subdirectory.
>>>
>>>
>>> mmm no.
>>> Better:
>>>
>>> IceCommitInfo allInstances anyOne repository register.
>>>
>>> (assuming anyOne will answer a pharo package)
>>
>>
>> hm, no.
>>
>> "IceCommitInfo allInstances" is empty.
>>
>>
>> weird… using 6.1?
>>
>
> no, should I ?
> I loaded the latest pharo 7 (or is it the same as 6.1?)
> (get.pharo.org/70+vm)
>
>
> no, is ok… in fact what happened is that unloading iceberg removed the
> instances of IceCommitInfo
> so, I do not think this is a valid way to update on 7.0… easier is just to
> clone iceberg (with iceberg) and update it as any other project.
>
> Esteban
>
>
>>
>>
>>
>>>
>>>
>>> Esteban
>>>
>>>
>>>
>>>
>>> --
>>> Cyril Ferlicot
>>> https://ferlicot.fr
>>>
>>> http://www.synectique.eu
>>> 2 rue Jacques Prévert 01,
>>> 59650 Villeneuve d'ascq France
>
>

Re: [Pharo-dev] The mooc is looking for forum moderators

[Stephane Ducasse]

Thank you
Rajula we should reply to the question of the mooc followers and help them


On Fri, Sep 1, 2017 at 6:12 PM, Rajula Vineet  wrote:
> Hey,
>
> I know I am new here. And I am not sure what exactly forum moderation is.
> But I would be happy to involve. Do let me know if I can do it.
>
> Rajula
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
>

Re: [Pharo-dev] State of 64bits? Errors during configuration loading

[Cyril Ferlicot]

On ven. 1 sept. 2017 at 20:24, Tim Mackinnon  wrote:

> I've probably done 100 builds on 64bits - I've had one crash (reported
> here).
>
> So it's not common, but does happen.
>
> Tim
>
> Sent from my iPhone
>


We must be unlucky :) 2 builds, 2 vm crashes.

>
> --
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

Re: [Pharo-dev] State of 64bits? Errors during configuration loading

[Tim Mackinnon]

I've probably done 100 builds on 64bits - I've had one crash (reported here).

So it's not common, but does happen.

Tim

Sent from my iPhone

> On 1 Sep 2017, at 17:08, Esteban Lorenzano  wrote:
> 
> I am using it everyday without problems… but this is a limited test ;)
> if you get crashes, I would like to have those reports to see what can we do.
> 
> Esteban
> 
>> On 1 Sep 2017, at 17:01, Cyril Ferlicot  wrote:
>> 
>> Hi,
>> 
>> I would like to know the state of the 64bits builds. At Synectique we
>> tried to build on of our tools in 64bits on ubuntu slaves but we get a
>> lot a VM crashes.
>> 
>> We get the image/vm with this command:
>> 
>> wget --quiet -O - get.pharo.org/64/$PHARO+$VM | bash
>> 
>> $PHARO = 61
>> $VM = vm
>> 
>> Here is the command we launch:
>> 
>> ./pharo Pharo.image --no-default-preferences eval --save 'Metacello new
>> repository:'\''http://smalltalkhub.com/mc/***/*/main'\'';
>> configuration: '\'''\'';
>> version: #development;
>>   load'
>> 
>> And I join an example of log we get when the vm crash.
>> 
>> Is that a known issue?
>> 
>> -- 
>> Cyril Ferlicot
>> https://ferlicot.fr
>> 
>> http://www.synectique.eu
>> 2 rue Jacques Prévert 01,
>> 59650 Villeneuve d'ascq France
>> 
> 
> 

Re: [Pharo-dev] The mooc is looking for forum moderators

[Rajula Vineet]

Hey,

I know I am new here. And I am not sure what exactly forum moderation is.
But I would be happy to involve. Do let me know if I can do it.

Rajula



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 17:47, Nicolai Hess  wrote:
> 
> 
> 
> 2017-09-01 17:44 GMT+02:00 Esteban Lorenzano  >:
> 
>> On 1 Sep 2017, at 17:18, Nicolai Hess > > wrote:
>> 
>> 
>> 
>> 2017-09-01 17:11 GMT+02:00 Esteban Lorenzano > >:
>> 
>>> On 1 Sep 2017, at 17:06, Cyril Ferlicot >> > wrote:
>>> 
>>> 
>>> 
>>> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess >> > wrote:
>>> 
>>> Oh no!
>>> 
>>> Now iceberg shows an empty list. Where is the pharo repository gone ?
>>> It took me a week to be at this point :(
>>> 
>>> I reenabled the setting "Include system repositories by default", but 
>>> still, the window is empty:
>>> 
>>> 
>>> 
>>> 
>>> How can I get back the system repository ?
>>> 
>>> I'm not 100% sure but I think you just need to click on "add local 
>>> repository", point the pharo clone and add src as subdirectory.  
>> 
>> mmm no. 
>> Better: 
>> 
>> IceCommitInfo allInstances anyOne repository register.
>> 
>> (assuming anyOne will answer a pharo package)
>> 
>> hm, no.
>> 
>> "IceCommitInfo allInstances" is empty.
> 
> weird… using 6.1?
> 
> 
> no, should I ?
> I loaded the latest pharo 7 (or is it the same as 6.1?)
> (get.pharo.org/70+vm )

no, is ok… in fact what happened is that unloading iceberg removed the 
instances of IceCommitInfo
so, I do not think this is a valid way to update on 7.0… easier is just to 
clone iceberg (with iceberg) and update it as any other project.

Esteban

>  
>> 
>>  
>> 
>> Esteban
>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Cyril Ferlicot
>>> https://ferlicot.fr 
>>> 
>>> http://www.synectique.eu 
>>> 2 rue Jacques Prévert 01,
>>> 59650 Villeneuve d'ascq France

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

[Nicolai Hess]

2017-08-31 20:05 GMT+02:00 Stephane Ducasse :

> Hi nicolai
>
> here is what I do.
> I always download the latest image via a bash script because updating can
> fail since loading package without a baseline may break.
>
> After I use the set up described by guille blog post and I reuse my
> downloaded clone (to avoid to trash my SSD).
>
> Esteban told me that he will do a video:
> - for producing a PR
> - for reviewing
>
> Stef
>

Thanks, that would be great. looking forward to it, but for now I think I
will quit trying this. It is too frustrating. I can not even try to explore
icebergs functionality because it is crashing all the time.




>
> On Thu, Aug 31, 2017 at 12:06 AM, Nicolai Hess 
> wrote:
>
>> Hi,
>>
>> I am now able to use iceberg on windows, thanks for the help.
>>
>> But I am still a bit unsure about how the review and contribution
>> workflow should work.
>>
>> up to pharo 6 I just load a latest image,
>> - load the slice from a fogbugz number and was able to review the change
>> - or create a slice and upload it to the inbox
>>
>> in pharo 7
>> - what is the equivalent to "getting the latest image" (and being able to
>> load and review a fix),
>>up to pharo 6 I just
>> - load the latest image in pharolauncher (or from the command line).
>> - opened the inbox repository.
>> - load and review change/fix
>> - throw away this change (close image without save)
>> - reopen that image to move on with the next item to review.
>>
>> But now, do I have to update my local branch for every new pull
>> request ? And how do I do this ? In other git project I would, I would
>> fetch upstream, checkout master, merge with upstream/master, push the
>> master to my fork origin
>>How should this be done with my pharo 7 fork ? (And do we only work on
>> the development brach instead of the master)?
>>
>>And do I this only in the command line or do I manage my fork (and
>> keep it up to date) from within pharo with iceberg ?
>>How do I actually access the pull requests from within pharo ? Maybe I
>> am stupid, but I just can not find it.
>>I would like do this steps, (as I was used to it from the prior
>> contribution process, by loading code from the inbox)
>>- Just look at the changes
>>- apply the changes
>>- throw away this changes, and move one with the next fix review
>>
>> And the same for creating a fix / pull request. Do I need to be up to
>> date with my own fork, or only the local copy of the pharo repository ?
>> Again, for pharo 6 I would just load a latest image, make my changes /
>> code fixes and create a slice. Save to the inbox -> done.
>> And looking at iceberg, I have really no clue how to upload a fix.
>>
>> I see that other people are using the new process, and I feel a bit lost
>> and closed out of the pharo 7 development process, as I am at the moment
>> unable to understand how this work.
>> Are there any other resources I missed ?
>>
>>
>>
>>
>> 2017-08-11 19:30 GMT+02:00 Stephane Ducasse :
>>
>>> Nicolai
>>>
>>> I started super simple. I clone and point my fresh dled image to the use
>>> the clone.
>>> Then I can do simple PR and review the issues.
>>> I will do the installation several times to learn (but not clone).
>>>
>>> I'm not sure that it is needed but I have
>>> cd   /Users/ducasse/Library/Preferences/pharo/7.0
>>>
>>> StartupPreferencesLoader default executeAtomicItems: {
>>> StartupAction
>>> name: 'Git Settings'
>>> code: [
>>> FileStream stdout
>>> cr; nextPutAll: 'Setting the ssh
>>> credentials'; cr.
>>> Iceberg enableMetacelloIntegration: true.
>>> IceCredentialsProvider useCustomSsh: true.
>>> IceCredentialsProvider sshCredentials
>>> username: 'git';
>>> publicKey:
>>> '/Users/ducasse/.ssh/id_rsa.pub';
>>> privateKey:
>>> '/Users/ducasse/.ssh/id_rsa'.
>>> IceCredentialsProvider
>>> plaintextCredentials:
>>> (IcePlaintextCredentials new username: 'Ducasse'; password: '' ;
>>> yourself ).
>>> FileStream stdout
>>> cr; nextPutAll: 'Finished'; cr ].
>>> }.
>>>
>>>
>>>
>>> On Fri, Aug 11, 2017 at 9:46 AM, Guillermo Polito <
>>> guillermopol...@gmail.com> wrote:
>>>
 I extended the document with some windows specific instructions also.

 On Fri, Aug 11, 2017 at 9:31 AM, Guillermo Polito <
 guillermopol...@gmail.com> wrote:

>
>
> On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess 
> wrote:
>
>>
>>
>> 2017-08-10 17:17 GMT+02:00 Guillermo Polito <
>> 

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 17:44 GMT+02:00 Esteban Lorenzano :

>
> On 1 Sep 2017, at 17:18, Nicolai Hess  wrote:
>
>
>
> 2017-09-01 17:11 GMT+02:00 Esteban Lorenzano :
>
>>
>> On 1 Sep 2017, at 17:06, Cyril Ferlicot  wrote:
>>
>>
>>
>> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess  w
>> rote:
>>
>>>
>>> Oh no!
>>>
>>> Now iceberg shows an empty list. Where is the pharo repository gone ?
>>> It took me a week to be at this point :(
>>>
>>> I reenabled the setting "Include system repositories by default", but
>>> still, the window is empty:
>>>
>>> 
>>>
>>>
>>> How can I get back the system repository ?
>>>
>>
>> I'm not 100% sure but I think you just need to click on "add local
>> repository", point the pharo clone and add src as subdirectory.
>>
>>
>> mmm no.
>> Better:
>>
>> IceCommitInfo allInstances anyOne repository register.
>>
>> (assuming anyOne will answer a pharo package)
>>
>
> hm, no.
>
> "IceCommitInfo allInstances" is empty.
>
>
> weird… using 6.1?
>
>
no, should I ?
I loaded the latest pharo 7 (or is it the same as 6.1?)
(get.pharo.org/70+vm)


>
>
>
>>
>> Esteban
>>
>>
>>
>>
>> --
>> Cyril Ferlicot
>> https://ferlicot.fr
>>
>> http://www.synectique.eu
>> 2 rue Jacques Prévert 01,
>> 59650 Villeneuve d'ascq France
>>
>>
>

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 17:18, Nicolai Hess  wrote:
> 
> 
> 
> 2017-09-01 17:11 GMT+02:00 Esteban Lorenzano  >:
> 
>> On 1 Sep 2017, at 17:06, Cyril Ferlicot > > wrote:
>> 
>> 
>> 
>> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess > > wrote:
>> 
>> Oh no!
>> 
>> Now iceberg shows an empty list. Where is the pharo repository gone ?
>> It took me a week to be at this point :(
>> 
>> I reenabled the setting "Include system repositories by default", but still, 
>> the window is empty:
>> 
>> 
>> 
>> 
>> How can I get back the system repository ?
>> 
>> I'm not 100% sure but I think you just need to click on "add local 
>> repository", point the pharo clone and add src as subdirectory.  
> 
> mmm no. 
> Better: 
> 
> IceCommitInfo allInstances anyOne repository register.
> 
> (assuming anyOne will answer a pharo package)
> 
> hm, no.
> 
> "IceCommitInfo allInstances" is empty.

weird… using 6.1?

> 
>  
> 
> Esteban
> 
>> 
>> 
>> 
>> -- 
>> Cyril Ferlicot
>> https://ferlicot.fr 
>> 
>> http://www.synectique.eu 
>> 2 rue Jacques Prévert 01,
>> 59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 17:11 GMT+02:00 Esteban Lorenzano :

>
> On 1 Sep 2017, at 17:06, Cyril Ferlicot  wrote:
>
>
>
> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess 
> wrote:
>
>>
>> Oh no!
>>
>> Now iceberg shows an empty list. Where is the pharo repository gone ?
>> It took me a week to be at this point :(
>>
>> I reenabled the setting "Include system repositories by default", but
>> still, the window is empty:
>>
>> 
>>
>>
>> How can I get back the system repository ?
>>
>
> I'm not 100% sure but I think you just need to click on "add local
> repository", point the pharo clone and add src as subdirectory.
>
>
> mmm no.
> Better:
>
> IceCommitInfo allInstances anyOne repository register.
>
> (assuming anyOne will answer a pharo package)
>

hm, no.

"IceCommitInfo allInstances" is empty.



>
> Esteban
>
>
>
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>
>
>

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 17:19, Nicolai Hess  wrote:
> 
> 
> 
> 2017-09-01 17:09 GMT+02:00 Nicolai Hess  >:
> 
> 
> 2017-09-01 17:06 GMT+02:00 Cyril Ferlicot  >:
> 
> 
> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess  > wrote:
> 
> Oh no!
> 
> Now iceberg shows an empty list. Where is the pharo repository gone ?
> It took me a week to be at this point :(
> 
> I reenabled the setting "Include system repositories by default", but still, 
> the window is empty:
> 
> 
> 
> 
> How can I get back the system repository ?
> 
> I'm not 100% sure but I think you just need to click on "add local 
> repository", point the pharo clone and add src as subdirectory.  
> 
> yes, seems to work.
>  
> 
> But, is the 
> 
> GitHub -> Review pull requests 
> 
> menu entry gone? I can not find it anymore.

nope.
somehow something went really bad with your update.

anyway, it will not solve the crash problem, I just reproduced it (is just 
random… which makes it worst)

Esteban

>  
> 
> 
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr 
> 
> http://www.synectique.eu 
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 17:09 GMT+02:00 Nicolai Hess :

>
>
> 2017-09-01 17:06 GMT+02:00 Cyril Ferlicot :
>
>>
>>
>> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess 
>> wrote:
>>
>>>
>>> Oh no!
>>>
>>> Now iceberg shows an empty list. Where is the pharo repository gone ?
>>> It took me a week to be at this point :(
>>>
>>> I reenabled the setting "Include system repositories by default", but
>>> still, the window is empty:
>>>
>>> [image: Inline-Bild 1]
>>>
>>>
>>> How can I get back the system repository ?
>>>
>>
>> I'm not 100% sure but I think you just need to click on "add local
>> repository", point the pharo clone and add src as subdirectory.
>>
>
> yes, seems to work.
>
>

But, is the

GitHub -> Review pull requests 

menu entry gone? I can not find it anymore.


>
>>
>>
>> --
>> Cyril Ferlicot
>> https://ferlicot.fr
>>
>> http://www.synectique.eu
>> 2 rue Jacques Prévert 01,
>> 59650 Villeneuve d'ascq France
>>
>
>

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 17:06, Cyril Ferlicot  wrote:
> 
> 
> 
> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess  > wrote:
> 
> Oh no!
> 
> Now iceberg shows an empty list. Where is the pharo repository gone ?
> It took me a week to be at this point :(
> 
> I reenabled the setting "Include system repositories by default", but still, 
> the window is empty:
> 
> 
> 
> 
> How can I get back the system repository ?
> 
> I'm not 100% sure but I think you just need to click on "add local 
> repository", point the pharo clone and add src as subdirectory.  

mmm no. 
Better: 

IceCommitInfo allInstances anyOne repository register.

(assuming anyOne will answer a pharo package)

Esteban

> 
> 
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr 
> 
> http://www.synectique.eu 
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 17:06 GMT+02:00 Cyril Ferlicot :

>
>
> On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess 
> wrote:
>
>>
>> Oh no!
>>
>> Now iceberg shows an empty list. Where is the pharo repository gone ?
>> It took me a week to be at this point :(
>>
>> I reenabled the setting "Include system repositories by default", but
>> still, the window is empty:
>>
>> [image: Inline-Bild 1]
>>
>>
>> How can I get back the system repository ?
>>
>
> I'm not 100% sure but I think you just need to click on "add local
> repository", point the pharo clone and add src as subdirectory.
>

yes, seems to work.


>
>
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>

Re: [Pharo-dev] State of 64bits? Errors during configuration loading

[Esteban Lorenzano]

I am using it everyday without problems… but this is a limited test ;)
if you get crashes, I would like to have those reports to see what can we do.

Esteban

> On 1 Sep 2017, at 17:01, Cyril Ferlicot  wrote:
> 
> Hi,
> 
> I would like to know the state of the 64bits builds. At Synectique we
> tried to build on of our tools in 64bits on ubuntu slaves but we get a
> lot a VM crashes.
> 
> We get the image/vm with this command:
> 
> wget --quiet -O - get.pharo.org/64/$PHARO+$VM | bash
> 
> $PHARO = 61
> $VM = vm
> 
> Here is the command we launch:
> 
> ./pharo Pharo.image --no-default-preferences eval --save 'Metacello new
> repository:'\''http://smalltalkhub.com/mc/***/*/main'\'';
> configuration: '\'''\'';
> version: #development;
>load'
> 
> And I join an example of log we get when the vm crash.
> 
> Is that a known issue?
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr
> 
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
> 

Re: [Pharo-dev] review pull request changes view

[Cyril Ferlicot]

On Fri, Sep 1, 2017 at 5:04 PM, Nicolai Hess  wrote:

>
> Oh no!
>
> Now iceberg shows an empty list. Where is the pharo repository gone ?
> It took me a week to be at this point :(
>
> I reenabled the setting "Include system repositories by default", but
> still, the window is empty:
>
> [image: Inline-Bild 1]
>
>
> How can I get back the system repository ?
>

I'm not 100% sure but I think you just need to click on "add local
repository", point the pharo clone and add src as subdirectory.



-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 16:48 GMT+02:00 Nicolai Hess :

>
>
> 2017-09-01 16:29 GMT+02:00 Cyril Ferlicot :
>
>> On Fri, Sep 1, 2017 at 4:26 PM, Nicolai Hess 
>> wrote:
>> >
>> >
>> >
>> > update what? pharo ?
>> >
>> >
>>
>> You can update Iceberg by executing:
>>
>> #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration'
>> 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core'
>> 'BaselineOfLibGit')
>> do: [ :each | each asPackage removeFromSystem ].
>>
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:dev-0.5';
>>   load.
>>
>>
>>
> Ah, thanks. I will try it out and report back if the crashes still occur.
>
>

Oh no!

Now iceberg shows an empty list. Where is the pharo repository gone ?
It took me a week to be at this point :(

I reenabled the setting "Include system repositories by default", but
still, the window is empty:

[image: Inline-Bild 1]


How can I get back the system repository ?


>
>> --
>> Cyril Ferlicot
>> https://ferlicot.fr
>>
>> http://www.synectique.eu
>> 2 rue Jacques Prévert 01,
>> 59650 Villeneuve d'ascq France
>>
>>
>

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 16:50, Cyril Ferlicot  wrote:
> 
> 
> 
> On Fri, Sep 1, 2017 at 4:46 PM, Nicolai Hess  > wrote:
> 
> 
> And how do I know if a pull request / change is already included ?
> 
> I looked at a pull request 
> and it seems this change is already in my image (a fresh image from 30.08 
> (Pharo7.0alpha.build.78.sha.35c21c3fac9b557eb38ec569fbbb109f2015c71a)
> The pull request (https://api.github.com/repos/pharo-project/pharo/pulls/231 
> ) is  "open", but 
> I can see the new code already in my image.
> 
> The diff view tells me, that the method 
> UITheme>>warningTextColor changes from 
> 
> warningTextColor
> ^ Color yellow muchDarker
> 
> to
> 
> warningTextColor
> ^ Color yellow
> 
> But the method in the image already looks like this:
> 
> warningTextColor
> ^ Color yellow
>  
> 
> 
> The *old* implementation is
> 
> warningTextColor
>   ^ Color yellow
> 
> and the *new* implementation is
> 
> warningTextColor
>   ^ Color yellow muchDarker
> 
> (See https://github.com/pharo-project/pharo/pull/231/files 
> )
> 
> So, the diff may be inversed. (I did not checked)

yep. Damn it :)

Esteban

> 
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr 
> 
> http://www.synectique.eu 
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Cyril Ferlicot]

On Fri, Sep 1, 2017 at 4:46 PM, Nicolai Hess  wrote:

>
>>
> And how do I know if a pull request / change is already included ?
>
> I looked at a pull request
> and it seems this change is already in my image (a fresh image from 30.08
> (Pharo7.0alpha.build.78.sha.35c21c3fac9b557eb38ec569fbbb109f2015c71a)
> The pull request (https://api.github.com/repos/
> pharo-project/pharo/pulls/231) is  "open", but I can see the new code
> already in my image.
>
> The diff view tells me, that the method
> UITheme>>warningTextColor changes from
>
> warningTextColor
> ^ Color yellow muchDarker
>
> to
>
> warningTextColor
> ^ Color yellow
>
> But the method in the image already looks like this:
>
> warningTextColor
> ^ Color yellow
>
>
>
The *old* implementation is

warningTextColor
  ^ Color yellow

and the *new* implementation is

warningTextColor
  ^ Color yellow muchDarker

(See https://github.com/pharo-project/pharo/pull/231/files)

So, the diff may be inversed. (I did not checked)


-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 16:29 GMT+02:00 Cyril Ferlicot :

> On Fri, Sep 1, 2017 at 4:26 PM, Nicolai Hess 
> wrote:
> >
> >
> >
> > update what? pharo ?
> >
> >
>
> You can update Iceberg by executing:
>
> #('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration'
> 'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core'
> 'BaselineOfLibGit')
> do: [ :each | each asPackage removeFromSystem ].
>
> Metacello new
>   baseline: 'Iceberg';
>   repository: 'github://pharo-vcs/iceberg:dev-0.5';
>   load.
>
>
>
Ah, thanks. I will try it out and report back if the crashes still occur.


>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
>
>

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 14:48 GMT+02:00 Nicolai Hess :

> When reviewing a pull request, I see this in the changes view:
> The tab title says
> "left working copy / right incoming update"
> but the code on the right side is what is current in my image
>
> [image: Inline-Bild 1]
>
>
> And I don't think "working copy" is the correct naming, as this view lets
> me diff changes within
> that history, so it may be that none of this code is actually in my
> "working copy", no ?
>

And how do I know if a pull request / change is already included ?

I looked at a pull request
and it seems this change is already in my image (a fresh image from 30.08
(Pharo7.0alpha.build.78.sha.35c21c3fac9b557eb38ec569fbbb109f2015c71a)
The pull request (https://api.github.com/repos/pharo-project/pharo/pulls/231)
is  "open", but I can see the new code already in my image.

The diff view tells me, that the method
UITheme>>warningTextColor changes from

warningTextColor
^ Color yellow muchDarker

to

warningTextColor
^ Color yellow

But the method in the image already looks like this:

warningTextColor
^ Color yellow

Re: [Pharo-dev] review pull request changes view

[Cyril Ferlicot]

On Fri, Sep 1, 2017 at 4:26 PM, Nicolai Hess  wrote:
>
>
>
> update what? pharo ?
>
>

You can update Iceberg by executing:

#('Iceberg-UI' 'Iceberg-Plugin' 'Iceberg-Metacello-Integration'
'Iceberg-Libgit' 'Iceberg' 'BaselineOfIceberg' 'LibGit-Core'
'BaselineOfLibGit')
do: [ :each | each asPackage removeFromSystem ].

Metacello new
  baseline: 'Iceberg';
  repository: 'github://pharo-vcs/iceberg:dev-0.5';
  load.



-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 16:13 GMT+02:00 Esteban Lorenzano :

>
> On 1 Sep 2017, at 16:02, Esteban Lorenzano  wrote:
>
>
> On 1 Sep 2017, at 15:50, Nicolai Hess  wrote:
>
>
>
> 2017-09-01 15:03 GMT+02:00 Esteban Lorenzano :
>
>>
>> On 1 Sep 2017, at 14:51, Nicolai Hess  wrote:
>>
>>
>>
>> 2017-09-01 14:48 GMT+02:00 Nicolai Hess :
>>
>>> When reviewing a pull request, I see this in the changes view:
>>> The tab title says
>>> "left working copy / right incoming update"
>>> but the code on the right side is what is current in my image
>>>
>>> 
>>>
>>>
>>> And I don't think "working copy" is the correct naming, as this view
>>> lets me diff changes within
>>> that history, so it may be that none of this code is actually in my
>>> "working copy", no ?
>>>
>>
>>
>> BTW, this is extremly unstable, reviewing a pull request, crashes a lot
>> (the vm)
>>
>>
>> on windows?
>>
>>
>>
>>
> Yes,
>
> attached a another crash.dmp (maybe it helps)
>
> 
>
>
> can you tell me the PR you were analysing ?
>
>
> ah, and btw… can you update with latest dev-0.5? I made some changes that
> may help there that I still do not merge into master.
>

update what? pharo ?


>
> Esteban
>
>
> Esteban
>
>
>

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 16:02 GMT+02:00 Esteban Lorenzano :

>
> On 1 Sep 2017, at 15:50, Nicolai Hess  wrote:
>
>
>
> 2017-09-01 15:03 GMT+02:00 Esteban Lorenzano :
>
>>
>> On 1 Sep 2017, at 14:51, Nicolai Hess  wrote:
>>
>>
>>
>> 2017-09-01 14:48 GMT+02:00 Nicolai Hess :
>>
>>> When reviewing a pull request, I see this in the changes view:
>>> The tab title says
>>> "left working copy / right incoming update"
>>> but the code on the right side is what is current in my image
>>>
>>> 
>>>
>>>
>>> And I don't think "working copy" is the correct naming, as this view
>>> lets me diff changes within
>>> that history, so it may be that none of this code is actually in my
>>> "working copy", no ?
>>>
>>
>>
>> BTW, this is extremly unstable, reviewing a pull request, crashes a lot
>> (the vm)
>>
>>
>> on windows?
>>
>>
>>
>>
> Yes,
>
> attached a another crash.dmp (maybe it helps)
>
> 
>
>
> can you tell me the PR you were analysing ?
>

https://api.github.com/repos/pharo-project/pharo/pulls/237


>
> Esteban
>

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 16:02, Esteban Lorenzano  wrote:
> 
> 
>> On 1 Sep 2017, at 15:50, Nicolai Hess > > wrote:
>> 
>> 
>> 
>> 2017-09-01 15:03 GMT+02:00 Esteban Lorenzano > >:
>> 
>>> On 1 Sep 2017, at 14:51, Nicolai Hess >> > wrote:
>>> 
>>> 
>>> 
>>> 2017-09-01 14:48 GMT+02:00 Nicolai Hess >> >:
>>> When reviewing a pull request, I see this in the changes view:
>>> The tab title says
>>> "left working copy / right incoming update"
>>> but the code on the right side is what is current in my image
>>> 
>>> 
>>> 
>>> 
>>> And I don't think "working copy" is the correct naming, as this view lets 
>>> me diff changes within
>>> that history, so it may be that none of this code is actually in my 
>>> "working copy", no ?
>>> 
>>> 
>>> BTW, this is extremly unstable, reviewing a pull request, crashes a lot 
>>> (the vm)
>> 
>> on windows?
>> 
>>> 
>> 
>> 
>> Yes,
>> 
>> attached a another crash.dmp (maybe it helps)
>> 
>> 
> 
> can you tell me the PR you were analysing ?

ah, and btw… can you update with latest dev-0.5? I made some changes that may 
help there that I still do not merge into master.

Esteban

> 
> Esteban

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 15:50, Nicolai Hess  wrote:
> 
> 
> 
> 2017-09-01 15:03 GMT+02:00 Esteban Lorenzano  >:
> 
>> On 1 Sep 2017, at 14:51, Nicolai Hess > > wrote:
>> 
>> 
>> 
>> 2017-09-01 14:48 GMT+02:00 Nicolai Hess > >:
>> When reviewing a pull request, I see this in the changes view:
>> The tab title says
>> "left working copy / right incoming update"
>> but the code on the right side is what is current in my image
>> 
>> 
>> 
>> 
>> And I don't think "working copy" is the correct naming, as this view lets me 
>> diff changes within
>> that history, so it may be that none of this code is actually in my "working 
>> copy", no ?
>> 
>> 
>> BTW, this is extremly unstable, reviewing a pull request, crashes a lot (the 
>> vm)
> 
> on windows?
> 
>> 
> 
> 
> Yes,
> 
> attached a another crash.dmp (maybe it helps)
> 
> 

can you tell me the PR you were analysing ?

Esteban

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 15:03 GMT+02:00 Esteban Lorenzano :

>
> On 1 Sep 2017, at 14:51, Nicolai Hess  wrote:
>
>
>
> 2017-09-01 14:48 GMT+02:00 Nicolai Hess :
>
>> When reviewing a pull request, I see this in the changes view:
>> The tab title says
>> "left working copy / right incoming update"
>> but the code on the right side is what is current in my image
>>
>> 
>>
>>
>> And I don't think "working copy" is the correct naming, as this view lets
>> me diff changes within
>> that history, so it may be that none of this code is actually in my
>> "working copy", no ?
>>
>
>
> BTW, this is extremly unstable, reviewing a pull request, crashes a lot
> (the vm)
>
>
> on windows?
>
>
>
>
Yes,

attached a another crash.dmp (maybe it helps)


crash.dmp
Description: Binary data

[Pharo-dev] 1st CfP: OOPS @ SAC 2018 - April 9 - 13, Pau, France

[Nick Papoylias]

**
  OOPS 2018 Call for Papers
Object-Oriented Programming Languages and Systems
   http://oops.disi.unige.it/OOPS18
**

Technical Track at the 33rd ACM Symposium on Applied Computing, SAC 2018
https://www.sigapp.org/sac/sac2018/index.html

April 9 - 13, 2018
Pau, France

- Important Dates

Submission of regular papers and SRC abstracts
September 15, 2017
Paper and SRC notifications
November 10, 2017
Paper and SRC camera-ready copies
November 25, 2017
Author registration
December 10, 2017
SAC 2018
April 9 - 13, 2018

- Track Chair

Davide Ancona (davide.anc...@unige.it)
DIBRIS, University of Genova, Italy

- SAC 2018

For the past thirty two years, the ACM Symposium on Applied Computing (SAC)
has been a
primary gathering forum for applied computer scientists, computer
engineers, software
engineers, and application developers from around the world.

SAC 2018 is sponsored by the ACM Special Interest Group on Applied
Computing (SIGAPP) and
is hosted by hosted by Université de Pau et des Pays de l'Adour (UPPA),
Pau, France.

- Call For Student Research Abstracts

Graduate students seeking feedback from the scientific community on their
research ideas
are invited to submit original abstracts of their research work in areas of
experimental
computing and application development related to SAC 2018 Tracks. The
Student Research
Competition (SRC) Program is designed to provide graduate students the
opportunity to meet
and exchange ideas with researchers and practitioners in their areas of
interest.

- OOPS Track: Aims and Topics

Object-oriented programming (OOP) has become the mainstream programming
paradigm for
developing complex software systems in most application domains.

However, existing OO languages and platforms need to evolve to meet the
continuous demand
for new abstractions, features, and tools able to reduce the time, effort,
and cost of
creating object-oriented software systems, and improving their performance,
quality and
usability.

To this aim, OOPS is seeking for research advances bringing benefits in all
those typical
aspects of software development, such as modeling, prototyping, design,
implementation,
concurrency and distribution, code generation, analysis, verification,
testing, debugging,
evaluation, deployment, maintenance, reuse, and software evolution and
adaptation.

The specific topics of interest for the OOPS track include, but are not
limited to, the
following:

*Aspects and components
*Code generation, and optimization, just-in-time compilation
*Context-oriented programming
*Databases and persistence
*Distribution and concurrency
*Dynamic and scripting languages
*Evaluation
*Feature Oriented Software Development and Programming
*Formal verification
*Internet of Things technology and programming
*Integration with other paradigms
*Interoperability, versioning and software evolution and adaptation
*Language design and implementation
*Modular and generic programming
*Reflection, meta-programming
*Runtime verification and monitoring
*Safe, secure and dependable software
*Static analysis
*Testing and debugging
*Type systems and type inference
*Virtual machines

OOPS offers a great opportunity to the OOP community to gain visibility,
and to
exploit the inter-disciplinary nature of SAC.

- Submission Instructions

Prospective papers should be submitted to the track in pdf format using the
START
submission system for regular and SRC papers available through the SAC 2018
home page.

Submission of the same paper to multiple tracks is not allowed; all papers
should
represent original and previously unpublished works that are currently not
under review in
any conference or journal. Both basic and applied research papers are
welcome.

SAC 2018 will use double-blind reviewing; to facilitate this, author
name(s) and
institution(s) must be omitted, and references to authors' own related work
should be in
the third person.

The format of the paper must adhere to the sig-alternate style
(http://www.acm.org/sigs/publications/proceedings-templates).

Full papers are limited to 8 pages, in camera-ready format, included in the
registration
fee. Authors have the option to include up to two (2) extra pages at
additional fee of
US$80 per page.

Papers accepted as posters are limited to 3 pages, in camera-ready format,
included in the
registration fee. Authors have the option to include only one (1) extra
page at additional
fee of US$80.

SRC abstracts are limited to 2 pages, in camera-ready format, included in
the registration
fee. No extra pages are allowed.

Papers that fall short the above requirements are subjected to rejection.
All papers must
be submitted by September 15, 2017. For more information please visit the
SAC 2018 home
page.

- Proceedings

Accepted papers will be published by ACM in 

Re: [Pharo-dev] review pull request changes view

[Esteban Lorenzano]

> On 1 Sep 2017, at 14:51, Nicolai Hess  wrote:
> 
> 
> 
> 2017-09-01 14:48 GMT+02:00 Nicolai Hess  >:
> When reviewing a pull request, I see this in the changes view:
> The tab title says
> "left working copy / right incoming update"
> but the code on the right side is what is current in my image
> 
> 
> 
> 
> And I don't think "working copy" is the correct naming, as this view lets me 
> diff changes within
> that history, so it may be that none of this code is actually in my "working 
> copy", no ?
> 
> 
> BTW, this is extremly unstable, reviewing a pull request, crashes a lot (the 
> vm)

on windows?

> 

Re: [Pharo-dev] review pull request changes view

[Nicolai Hess]

2017-09-01 14:48 GMT+02:00 Nicolai Hess :

> When reviewing a pull request, I see this in the changes view:
> The tab title says
> "left working copy / right incoming update"
> but the code on the right side is what is current in my image
>
> [image: Inline-Bild 1]
>
>
> And I don't think "working copy" is the correct naming, as this view lets
> me diff changes within
> that history, so it may be that none of this code is actually in my
> "working copy", no ?
>


BTW, this is extremly unstable, reviewing a pull request, crashes a lot
(the vm)

[Pharo-dev] review pull request changes view

[Nicolai Hess]

When reviewing a pull request, I see this in the changes view:
The tab title says
"left working copy / right incoming update"
but the code on the right side is what is current in my image

[image: Inline-Bild 1]


And I don't think "working copy" is the correct naming, as this view lets
me diff changes within
that history, so it may be that none of this code is actually in my
"working copy", no ?

Re: [Pharo-dev] BOF at ESUG - How about a BOF on Gemstone development environments?

[Tim Mackinnon]

I'm envious as I couldn't make it to Esug - but I'd love to hear any 
conclusions/insights from that  bof. Iceberg/git is such a transformative step 
that we need all the knowledge spread we can get.

Tim

Sent from my iPhone

> On 1 Sep 2017, at 12:40, Reg Krock via Pharo-dev  
> wrote:
> 
> 

[Pharo-dev] BOF at ESUG - How about a BOF on Gemstone development environments?

[Reg Krock via Pharo-dev]

--- Begin Message ---

> On 1 Sep2017, at 6:35 AM, Tudor Girba  wrote:
> 
> Hi,
> 
> I would also be interested in a Pillar BOF.
> 
> Doru
> 
> 
>> On Sep 1, 2017, at 11:43 AM, Stephane Ducasse  
>> wrote:
>> 
>> May be wednesday afternoon the talks
>> 
>> On Fri, Sep 1, 2017 at 9:17 AM, Tudor Girba  wrote:
>>> +1
>>> 
>>> Doru
>>> 
>>> 
 On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano  wrote:
 
 +1 :)
 
> On 31 Aug 2017, at 20:11, Stephane Ducasse  
> wrote:
> 
> Hi
> 
> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG.
> 
> Stef
> 
 
 
>>> 
>>> --
>>> www.tudorgirba.com
>>> www.feenk.com
>>> 
>>> “Live like you mean it."
>>> 
>>> 
>> 
> 
> --
> www.tudorgirba.com
> www.feenk.com
> 
> "We are all great at making mistakes."
> 
> 
> 
> 
> 
> 
> 
> 
> 


--- End Message ---

Re: [Pharo-dev] Pharo / Iceberg BOF at ESUG

[Tudor Girba]

Hi,

I would also be interested in a Pillar BOF.

Doru


> On Sep 1, 2017, at 11:43 AM, Stephane Ducasse  wrote:
> 
> May be wednesday afternoon the talks
> 
> On Fri, Sep 1, 2017 at 9:17 AM, Tudor Girba  wrote:
>> +1
>> 
>> Doru
>> 
>> 
>>> On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano  wrote:
>>> 
>>> +1 :)
>>> 
 On 31 Aug 2017, at 20:11, Stephane Ducasse  wrote:
 
 Hi
 
 I'm wondering if we should not do a BOF around Pharo iceberg at ESUG.
 
 Stef
 
>>> 
>>> 
>> 
>> --
>> www.tudorgirba.com
>> www.feenk.com
>> 
>> “Live like you mean it."
>> 
>> 
> 

--
www.tudorgirba.com
www.feenk.com

"We are all great at making mistakes."

Re: [Pharo-dev] The mooc is looking for forum moderators

[Cyril Ferlicot]

On Fri, Sep 1, 2017 at 11:37 AM, Stephane Ducasse
 wrote:
> Hi guys
>
> we are looking for some brave souls to help us helping newbies during
> the next run of the mooc
> planned for October 16th 2017...
>

I can help like last year.

> https://www.fun-mooc.fr/courses/course-v1:inria+41010+session02/about
>
> Please let me know if you are interested helping.
>
> Stef
>



-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

Re: [Pharo-dev] Pharo / Iceberg BOF at ESUG

[Stephane Ducasse]

May be wednesday afternoon the talks

On Fri, Sep 1, 2017 at 9:17 AM, Tudor Girba  wrote:
> +1
>
> Doru
>
>
>> On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano  wrote:
>>
>> +1 :)
>>
>>> On 31 Aug 2017, at 20:11, Stephane Ducasse  wrote:
>>>
>>> Hi
>>>
>>> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG.
>>>
>>> Stef
>>>
>>
>>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> “Live like you mean it."
>
>

Re: [Pharo-dev] The mooc is looking for forum moderators

[Serge Stinckwich]

I should be able to help like last year.

On Fri, Sep 1, 2017 at 11:37 AM, Stephane Ducasse 
wrote:

> Hi guys
>
> we are looking for some brave souls to help us helping newbies during
> the next run of the mooc
> planned for October 16th 2017...
>
> https://www.fun-mooc.fr/courses/course-v1:inria+41010+session02/about
>
> Please let me know if you are interested helping.
>
> Stef
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

[Pharo-dev] The mooc is looking for forum moderators

[Stephane Ducasse]

Hi guys

we are looking for some brave souls to help us helping newbies during
the next run of the mooc
planned for October 16th 2017...

https://www.fun-mooc.fr/courses/course-v1:inria+41010+session02/about

Please let me know if you are interested helping.

Stef

Re: [Pharo-dev] Pharo / Iceberg BOF at ESUG

[Tudor Girba]

+1

Doru


> On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano  wrote:
> 
> +1 :)
> 
>> On 31 Aug 2017, at 20:11, Stephane Ducasse  wrote:
>> 
>> Hi
>> 
>> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG.
>> 
>> Stef
>> 
> 
> 

--
www.tudorgirba.com
www.feenk.com 

“Live like you mean it."

Re: [Pharo-dev] Pharo / Iceberg BOF at ESUG

[Esteban Lorenzano]

+1 :)

> On 31 Aug 2017, at 20:11, Stephane Ducasse  wrote:
> 
> Hi
> 
> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG.
> 
> Stef
>