Re: [Pharo-dev] pharo.prg is down

[Christophe Demarey]

There is a documentation I wrote when preparing server migration (none before) 
hosted at https://gitlab.inria.fr/RMOD/servers.
It is a private repository as it contains sensitive information.

> Le 5 févr. 2019 à 14:58, ducasse  a écrit :
> 
> Do we have a document somwhere to know what to do
> if knowing people are in vacation?
> 
> 
> 
>> On 5 Feb 2019, at 13:57, Christophe Demarey  
>> wrote:
>> 
>> Thanks for the report.
>> I restarted the service. It is now back on line.
>> 
>> Cheers,
>> Christophe
>> 
>>> Le 5 févr. 2019 à 13:41, Tudor Girba  a écrit :
>>> 
>>> Hi,
>>> 
>>> pharo.org looks down:
>>> https://downforeveryoneorjustme.com/pharo.org
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> --
>>> www.feenk.com
>>> 
>>> “How do you feenk today?"
>>> 
>>> 
>> 
>> 
> 
> 
> 

[Pharo-dev] shortcut to browser ref to a class

[ducasse]

Hi

Is it me or we lost cmd + shift B to browse refs to class in Calypso?

Stef

Re: [Pharo-dev] pharo.prg is down

[ducasse]

Do we have a document somwhere to know what to do
if knowing people are in vacation?



> On 5 Feb 2019, at 13:57, Christophe Demarey  
> wrote:
> 
> Thanks for the report.
> I restarted the service. It is now back on line.
> 
> Cheers,
> Christophe
> 
>> Le 5 févr. 2019 à 13:41, Tudor Girba  a écrit :
>> 
>> Hi,
>> 
>> pharo.org looks down:
>> https://downforeveryoneorjustme.com/pharo.org
>> 
>> Cheers,
>> Doru
>> 
>> --
>> www.feenk.com
>> 
>> “How do you feenk today?"
>> 
>> 
> 
> 

[Pharo-dev] [ANN] Pharo Sprints first half 2019

[Marcus Denker]

We organise one Pharo “Sprint” per month were we meet to work on boring issue 
tracker entries together.

Goals of the next sprints:

- Fix issues for Pharo8
- Backport important fixes to Pharo7

Remotely, you can join us on Discord. During the sprint, we will try to 
synchronize local and 
remote Pharo sprinters. In the past people organised local sprints at the same 
time (e.g. Santiago/Chile). 
See here for more infos: http://pharo.org/contribute-events

There will be an event on the association website for each sprint. The next 
dates are:

- 22 Feb https://association.pharo.org/event-3253818
- 29 Mar https://association.pharo.org/event-3253842
- 26 Apr https://association.pharo.org/event-3253846
- 31 May https://association.pharo.org/event-3253848
- 28 Jun https://association.pharo.org/event-3253850

For more Pharo Event, have a look at the Events Page: 
https://association.pharo.org/events

Re: [Pharo-dev] An article that talks about Pharo in a portal from México

[Ben Coman]

On Tue, 5 Feb 2019 at 17:58, Esteban Lorenzano  wrote:

> https://www.unocero.com/smartphones/pharo-7-internet-de-las-cosas/
>

Nice. Google translate works wonders.


> 2. IoT has a lot of attention at this moment.
>

IoT is new to a lot of people, which presents an opportunity since people
are
more receptive to new ideas when they are already in an exploring mode.

cheers -ben

Re: [Pharo-dev] pharo.prg is down

[Christophe Demarey]

Thanks for the report.
I restarted the service. It is now back on line.

Cheers,
Christophe

> Le 5 févr. 2019 à 13:41, Tudor Girba  a écrit :
> 
> Hi,
> 
> pharo.org looks down:
> https://downforeveryoneorjustme.com/pharo.org
> 
> Cheers,
> Doru
> 
> --
> www.feenk.com
> 
> “How do you feenk today?"
> 
> 

Re: [Pharo-dev] pharo.prg is down

[Esteban Maringolo]

Is up again.

Esteban A. Maringolo

El mar., 5 feb. 2019 a las 9:42, Tudor Girba () escribió:
>
> Hi,
>
> pharo.org looks down:
> https://downforeveryoneorjustme.com/pharo.org
>
> Cheers,
> Doru
>
> --
> www.feenk.com
>
> “How do you feenk today?"
>
>

[Pharo-dev] Camp Smalltalk Charlotte 2019 Update!

[Mariano Martinez Peck]

Hello Smalltalkers,

Camp Smalltalk Charlotte 2019 is looking good! At this point we are over
half full.
Looks like some cool demos using different Smalltalk dialects are already
lining up.
A google groups forum has been created for attendees so everyone can
collaborate
beforehand.  Attendees will get an invitation for group access shortly
after registering.

This event is happening March 29th – March 31st 2019 in Charlotte, North
Carolina.
Please register for the event as spots will be limited.
Event details and registration info are available at the following link: Camp
Smalltalk Charlotte 2019


Hope to see you there!

-- 
Mariano
https://twitter.com/MartinezPeck
http://marianopeck.wordpress.com

[Pharo-dev] pharo.prg is down

[Tudor Girba]

Hi,

pharo.org looks down:
https://downforeveryoneorjustme.com/pharo.org

Cheers,
Doru

--
www.feenk.com

“How do you feenk today?"

Re: [Pharo-dev] iceberg: merging branches just at the git level without changing code in the image

[Guillermo Polito]

Hi,

On Mon, Feb 4, 2019 at 6:19 PM Andrei Chis 
wrote:

> Hi,
>
> Currently in Iceberg to merge a branch into another, we need to checkout
> the branch into which we want to merge and then do the merge.
>

For the moment it is done that way because
 - every commit is first written in disk before moved to the index and then
commited
 - a merge, unless fast forward, will need to create a new commit, and
potentially if there is a merge conflict it requires some manual
intervention

Also, we have decided for the moment to follow git's semantics to avoid
MORE terminology/technological mismatch than what we have.
We could implement the merge operation to work on any two arbitrary
branches, but still in case of merge conflict it's not so straight forward.
We have discussed in Esug with some guys, and there would be the
possibility to have automatic merge strategies like:
  - take all incoming
  - take all outgoing

But still there are cases where the user would like a mix of them, and even
do manual modifications.

Checking out a branch also updates the code in the image, which when
> needing to perform automatic releases on a branch can cause issues.
>

> Is there already a way in Iceberg to switch to a branch (for example
> `release`) and then merge another branch (for example `master`) into it
> without updating any code in the image?
> The use-case is that the user is on the `master` branch and needs to merge
> `master` into `release` without changing any code in the image.
>

Yes, when you checkout a branch, there is a combobox:

[image: image.png]

You can choose the last option for it.
These are called in iceberg CheckoutStrategies, and though they are so far
only used for checkouts, they could be used for merge toos.


>
> I found LGitRepository>>#merge:, but it seems not to be used anywhere in
> the image.
>
> Another way would be to implement something like the method below. This:
>   - calculates what changes need to be merged
>   - always takes what is on the left branch (in this case what is on
> master overrides what is on release)
>   - does not call loadChangesInWorkingCopy: to update the working copy as
> the code is already in the image
>   - refreshes the dirty packages in case there are changes between what is
> on the image and what is on disk
>
> ```
> IceMerge>>#executeWithAcceptingLeftOnConflictAndWithoutImageUpdate
> | commitToAdvance |
> mergeCommit validateCanMerge.
> self isAlreadyMerged ifTrue: [ ^ self ].
>
> self calculateChanges.
> self conflictsDo: [ :operation |
> operation selectLeft.
> ].
> commitToAdvance := self updateHead.
> "Do not update the working copy"
> "repository workingCopy loadChangesInWorkingCopy: self
> changesToWorkingCopyTree."
> repository workingCopy refreshDirtyPackages.
> ^ commitToAdvance
> ```
>
> Could something like the above solution work? Or are there other issues to
> take into account?
>

I think something like that would work...
But it would be nice to extract those things to be more reusable?
 - a conflict resolution strategy (with a default "do not solve conflict")
 - a checkout strategy (with a checkout in image strategy).

Anyway you go, I'd write some tests about that, since a broken merge can
lead to super fuzzy behaviour (like losing code...) :)


> Cheers,
> Andrei
>
>
>
>

-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

[Pharo-dev] An article that talks about Pharo in a portal from México

[Esteban Lorenzano]

https://www.unocero.com/smartphones/pharo-7-internet-de-las-cosas/ 


Just presenting version 7.

Couple of observations: 

1. We reach farther than we think.
2. IoT has a lot of attention at this moment.

Esteban