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

[Guillermo Polito]

On Thu, Oct 19, 2017 at 1:36 AM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:

> Thanks Guille, now it looks fine.
>
> Another issue for Windows users is that you cannot execute the workaround:
>
> $ git config core.longpaths true
>
> until you first cloned the repository. That's why I said one first should
> let fail the git clone command and then:
>
> $ cd pharo/
> $ git config core.longpaths true
> $ git checkout -f HEAD
>
> If anyone can check because submitting a fix should be easy and there
> shouldn't be guessing in the process.
>

If a windows user confirms, I update it. I don't have access to a windows
machine right now :).

>
> Cheers,
>
> Hernán
>
>
> 2017-10-18 4:37 GMT-03:00 Guillermo Polito :
>
>>
>>
>> On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand <
>> hernan.mora...@gmail.com> wrote:
>>
>>> Thank you Esteban, that was the problem! :)
>>>
>>> Maybe guille wants to clarify the correct remote repository in the page:
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>>> ribute-a-fix-to-Pharo after "You can click on the *Add remote* option
>>> and configure a remote with a name and repository url."
>>>
>>
>> Done that.
>>
>> Can you check if that's ok?
>>
>>
>>>
>>> Another thing. I created a PR with a fix for this bug :
>>> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioB
>>> uttonModel-ignore-disable following the guide to the Step 3. However I
>>> couldn't view any PR in my Github page (see attach).
>>>
>>> Do I miss something?
>>>
>>>
>>> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano :
>>>
 no is ok.
 with the pharo version I know the iceberg version :)

 anyway your problem is that the remote for pharo is bad.

 you added g...@github.com:pharo/pharo.git and I do not think that
 exists.
 Correct one is:

 g...@github.com:pharo-project/pharo.git

 Esteban


 On 17 Oct 2017, at 11:51, Hernán Morales Durand <
 hernan.mora...@gmail.com> wrote:

 I don't see any easy way to find the Iceberg version.

 Should I update Iceberg using this script also in Pharo 7?

 "Restore defaults"
 Iceberg enableMetacelloIntegration: false.
 MetacelloPharo30Platform select.

 "Update metacello"
 Metacello new
   baseline: 'Metacello';
   repository: 'github://metacello/metacello:Pharo6.1/repository';
   onConflict: [:e | e useIncoming ];
   get;
   load.

 "Update iceberg"
  #(
 'Iceberg-UI'
 'Iceberg-Plugin-GitHub'
 'Iceberg-Plugin'
 'Iceberg-Metacello-Integration'
 'Iceberg-Libgit-Tonel'
 'Iceberg-Libgit-Filetree'
 'Iceberg-Libgit'
 'Iceberg'
 'LibGit-Core')
 do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
 #removeFromSystem ].
 Metacello new
   baseline: 'Iceberg';
   repository: 'github://pharo-vcs/iceberg:v0.6';
   load.

 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand <
 hernan.mora...@gmail.com>:

> Hi Esteban,
>
> This one:
>
> wget -O- get.pharo.org/70+vm | bash -
>
> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :
>
>> which Pharo version (and Iceberg version) do you have?
>>
>> Esteban
>>
>> On 17 Oct 2017, at 04:36, Hernán Morales Durand <
>> hernan.mora...@gmail.com> wrote:
>>
>> Hi Guille,
>>
>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>> ribute-a-fix-to-Pharo
>>
>> This part is not working for me: "Go back to iceberg, right click on
>> the pharo repository and go to the *Pharo* entry. You'll see the
>> option *Create new branch from Fogbugz issue*."
>>
>> Because there is no such "Pharo" option in the menu. See the attached
>> screenshot.
>>
>> Did I miss something?
>> Any suggestion?
>>
>>
>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito <
>> guillermopol...@gmail.com>:
>>
>>> 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 everything is smooth. If you
>>> have comments, they are welcome.
>>>
>>> Guille
>>>
>>> --
>>>
>>> Guille Polito
>>>
>>> Research Engineer
>>> French National Center for Scientific Research -
>>> *http://www.cnrs.fr* 
>>>
>>>
>>> *Web:* *http://guillep.github.io* 
>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>>
>>
>> 
>>
>>
>>
>


>>>
>>
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>> Research Engineer
>>
>> Centre de Recherche en Informatique, Signal et Automatique de 

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

[Esteban Lorenzano]

Hi,

> On 19 Oct 2017, at 01:36, Hernán Morales Durand  
> wrote:
> 
> Thanks Guille, now it looks fine.
> 
> Another issue for Windows users is that you cannot execute the workaround:
> 
> $ git config core.longpaths true
> 
> until you first cloned the repository. That's why I said one first should let 
> fail the git clone command and then:
> 
> $ cd pharo/
> $ git config core.longpaths true
> $ git checkout -f HEAD
> 
> If anyone can check because submitting a fix should be easy and there 
> shouldn't be guessing in the process.

that’s why we created tonel (we will be moving to it soon). 
libgit2 does not recognise core.longpaths (in iceberg, process is split in two: 
bare clone and checkout so I tried adding that option when repository is 
created before checking out and it does not works either).
also, one other reason to move to tonel is time: clone itself is very fast, but 
the checkout (there is a ridiculous amount of files to recreate there) is very 
slow.

Esteban

> 
> Cheers,
> 
> Hernán
> 
> 
> 2017-10-18 4:37 GMT-03:00 Guillermo Polito  >:
> 
> 
> On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand 
> > wrote:
> Thank you Esteban, that was the problem! :)
> 
> Maybe guille wants to clarify the correct remote repository in the page: 
> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>  
> 
>  after "You can click on the Add remote option and configure a remote with a 
> name and repository url."
> 
> Done that.
> 
> Can you check if that's ok?
>  
> 
> Another thing. I created a PR with a fix for this bug : 
> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioButtonModel-ignore-disable
>  
> 
>  following the guide to the Step 3. However I couldn't view any PR in my 
> Github page (see attach).
> 
> Do I miss something?
> 
> 
> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano  >:
> no is ok.
> with the pharo version I know the iceberg version :)
> 
> anyway your problem is that the remote for pharo is bad.
> 
> you added g...@github.com :pharo/pharo.git and I do 
> not think that exists. 
> Correct one is: 
> 
> g...@github.com :pharo-project/pharo.git
> 
> Esteban
> 
> 
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand > > wrote:
>> 
>> I don't see any easy way to find the Iceberg version.
>> 
>> Should I update Iceberg using this script also in Pharo 7?
>> 
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>> 
>> "Update metacello" 
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository <>';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>> 
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI' 
>> 'Iceberg-Plugin-GitHub' 
>> 'Iceberg-Plugin' 
>> 'Iceberg-Metacello-Integration' 
>> 'Iceberg-Libgit-Tonel' 
>> 'Iceberg-Libgit-Filetree' 
>> 'Iceberg-Libgit' 
>> 'Iceberg' 
>> 'LibGit-Core') 
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem 
>> ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6 <>';
>>   load.
>> 
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>> Hi Esteban,
>> 
>> This one:
>> 
>> wget -O- get.pharo.org/70+vm  | bash -
>> 
>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano > >:
>> which Pharo version (and Iceberg version) do you have?
>> 
>> Esteban
>> 
>>> On 17 Oct 2017, at 04:36, Hernán Morales Durand >> > wrote:
>>> 
>>> Hi Guille,
>>> 
>>> In 
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>>  
>>> 
>>> 
>>> This part is not working for me: "Go back to iceberg, right click on the 
>>> pharo repository and go to the Pharo entry. You'll see the option Create 
>>> new branch from Fogbugz issue."
>>> 
>>> Because there is no such "Pharo" option in the menu. See the attached 
>>> screenshot.
>>> 
>>> Did I miss something?
>>> Any suggestion?
>>> 
>>> 
>>> 2017-08-10 12:17 GMT-03:00 Guillermo Polito >> >:
>>> 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

[Hernán Morales Durand]

Thanks Guille, now it looks fine.

Another issue for Windows users is that you cannot execute the workaround:

$ git config core.longpaths true

until you first cloned the repository. That's why I said one first should
let fail the git clone command and then:

$ cd pharo/
$ git config core.longpaths true
$ git checkout -f HEAD

If anyone can check because submitting a fix should be easy and there
shouldn't be guessing in the process.

Cheers,

Hernán


2017-10-18 4:37 GMT-03:00 Guillermo Polito :

>
>
> On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand <
> hernan.mora...@gmail.com> wrote:
>
>> Thank you Esteban, that was the problem! :)
>>
>> Maybe guille wants to clarify the correct remote repository in the page:
>> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>> ribute-a-fix-to-Pharo after "You can click on the *Add remote* option
>> and configure a remote with a name and repository url."
>>
>
> Done that.
>
> Can you check if that's ok?
>
>
>>
>> Another thing. I created a PR with a fix for this bug :
>> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-RadioB
>> uttonModel-ignore-disable following the guide to the Step 3. However I
>> couldn't view any PR in my Github page (see attach).
>>
>> Do I miss something?
>>
>>
>> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano :
>>
>>> no is ok.
>>> with the pharo version I know the iceberg version :)
>>>
>>> anyway your problem is that the remote for pharo is bad.
>>>
>>> you added g...@github.com:pharo/pharo.git and I do not think that
>>> exists.
>>> Correct one is:
>>>
>>> g...@github.com:pharo-project/pharo.git
>>>
>>> Esteban
>>>
>>>
>>> On 17 Oct 2017, at 11:51, Hernán Morales Durand <
>>> hernan.mora...@gmail.com> wrote:
>>>
>>> I don't see any easy way to find the Iceberg version.
>>>
>>> Should I update Iceberg using this script also in Pharo 7?
>>>
>>> "Restore defaults"
>>> Iceberg enableMetacelloIntegration: false.
>>> MetacelloPharo30Platform select.
>>>
>>> "Update metacello"
>>> Metacello new
>>>   baseline: 'Metacello';
>>>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>>>   onConflict: [:e | e useIncoming ];
>>>   get;
>>>   load.
>>>
>>> "Update iceberg"
>>>  #(
>>> 'Iceberg-UI'
>>> 'Iceberg-Plugin-GitHub'
>>> 'Iceberg-Plugin'
>>> 'Iceberg-Metacello-Integration'
>>> 'Iceberg-Libgit-Tonel'
>>> 'Iceberg-Libgit-Filetree'
>>> 'Iceberg-Libgit'
>>> 'Iceberg'
>>> 'LibGit-Core')
>>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
>>> #removeFromSystem ].
>>> Metacello new
>>>   baseline: 'Iceberg';
>>>   repository: 'github://pharo-vcs/iceberg:v0.6';
>>>   load.
>>>
>>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand <
>>> hernan.mora...@gmail.com>:
>>>
 Hi Esteban,

 This one:

 wget -O- get.pharo.org/70+vm | bash -

 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :

> which Pharo version (and Iceberg version) do you have?
>
> Esteban
>
> On 17 Oct 2017, at 04:36, Hernán Morales Durand <
> hernan.mora...@gmail.com> wrote:
>
> Hi Guille,
>
> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
> ribute-a-fix-to-Pharo
>
> This part is not working for me: "Go back to iceberg, right click on
> the pharo repository and go to the *Pharo* entry. You'll see the
> option *Create new branch from Fogbugz issue*."
>
> Because there is no such "Pharo" option in the menu. See the attached
> screenshot.
>
> Did I miss something?
> Any suggestion?
>
>
> 2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
>> comments, they are welcome.
>>
>> Guille
>>
>> --
>>
>> Guille Polito
>>
>> Research Engineer
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>> *Web:* *http://guillep.github.io* 
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
> 
>
>
>

>>>
>>>
>>
>
>
> --
>
>
>
> 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
>

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

[Esteban Lorenzano]

hi,

> On 18 Oct 2017, at 08:39, Stephane Ducasse  wrote:
> 
> Esteban it would be good to make the remote handling more robust because many 
> people face
> this problem.

if people enter a wrong url, we can't do anything. 
now, the RSD is another problem, not related with this one.

Esteban

> 
> On Tue, Oct 17, 2017 at 11:53 AM, Esteban Lorenzano  > wrote:
> no is ok.
> with the pharo version I know the iceberg version :)
> 
> anyway your problem is that the remote for pharo is bad.
> 
> you added g...@github.com :pharo/pharo.git and I do 
> not think that exists. 
> Correct one is: 
> 
> g...@github.com :pharo-project/pharo.git
> 
> Esteban
> 
> 
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand > > wrote:
>> 
>> I don't see any easy way to find the Iceberg version.
>> 
>> Should I update Iceberg using this script also in Pharo 7?
>> 
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>> 
>> "Update metacello" 
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository <>';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>> 
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI' 
>> 'Iceberg-Plugin-GitHub' 
>> 'Iceberg-Plugin' 
>> 'Iceberg-Metacello-Integration' 
>> 'Iceberg-Libgit-Tonel' 
>> 'Iceberg-Libgit-Filetree' 
>> 'Iceberg-Libgit' 
>> 'Iceberg' 
>> 'LibGit-Core') 
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem 
>> ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6 <>';
>>   load.
>> 
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>> Hi Esteban,
>> 
>> This one:
>> 
>> wget -O- get.pharo.org/70+vm  | bash -
>> 
>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano > >:
>> which Pharo version (and Iceberg version) do you have?
>> 
>> Esteban
>> 
>>> On 17 Oct 2017, at 04:36, Hernán Morales Durand >> > wrote:
>>> 
>>> Hi Guille,
>>> 
>>> In 
>>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>>  
>>> 
>>> 
>>> This part is not working for me: "Go back to iceberg, right click on the 
>>> pharo repository and go to the Pharo entry. You'll see the option Create 
>>> new branch from Fogbugz issue."
>>> 
>>> Because there is no such "Pharo" option in the menu. See the attached 
>>> screenshot.
>>> 
>>> Did I miss something?
>>> Any suggestion?
>>> 
>>> 
>>> 2017-08-10 12:17 GMT-03: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/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
>>> 
>>> Research Engineer
>>> French National Center for Scientific Research - http://www.cnrs.fr 
>>> 
>>> 
>>> 
>>> Web: http://guillep.github.io 
>>> Phone: +33 06 52 70 66 13 
>>> 
>> 
>> 
>> 
> 
> 

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

[Guillermo Polito]

On Tue, Oct 17, 2017 at 12:42 PM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:

> Thank you Esteban, that was the problem! :)
>
> Maybe guille wants to clarify the correct remote repository in the page:
> https://github.com/guillep/PharoIntegrationProcess/wiki/
> Contribute-a-fix-to-Pharo after "You can click on the *Add remote* option
> and configure a remote with a name and repository url."
>

Done that.

Can you check if that's ok?


>
> Another thing. I created a PR with a fix for this bug :
> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-
> RadioButtonModel-ignore-disable following the guide to the Step 3.
> However I couldn't view any PR in my Github page (see attach).
>
> Do I miss something?
>
>
> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano :
>
>> no is ok.
>> with the pharo version I know the iceberg version :)
>>
>> anyway your problem is that the remote for pharo is bad.
>>
>> you added g...@github.com:pharo/pharo.git and I do not think that exists.
>> Correct one is:
>>
>> g...@github.com:pharo-project/pharo.git
>>
>> Esteban
>>
>>
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand 
>> wrote:
>>
>> I don't see any easy way to find the Iceberg version.
>>
>> Should I update Iceberg using this script also in Pharo 7?
>>
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>>
>> "Update metacello"
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>>
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI'
>> 'Iceberg-Plugin-GitHub'
>> 'Iceberg-Plugin'
>> 'Iceberg-Metacello-Integration'
>> 'Iceberg-Libgit-Tonel'
>> 'Iceberg-Libgit-Filetree'
>> 'Iceberg-Libgit'
>> 'Iceberg'
>> 'LibGit-Core')
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
>> #removeFromSystem ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6';
>>   load.
>>
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>>
>>> Hi Esteban,
>>>
>>> This one:
>>>
>>> wget -O- get.pharo.org/70+vm | bash -
>>>
>>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :
>>>
 which Pharo version (and Iceberg version) do you have?

 Esteban

 On 17 Oct 2017, at 04:36, Hernán Morales Durand <
 hernan.mora...@gmail.com> wrote:

 Hi Guille,

 In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
 ribute-a-fix-to-Pharo

 This part is not working for me: "Go back to iceberg, right click on
 the pharo repository and go to the *Pharo* entry. You'll see the
 option *Create new branch from Fogbugz issue*."

 Because there is no such "Pharo" option in the menu. See the attached
 screenshot.

 Did I miss something?
 Any suggestion?


 2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>
> --
>
> Guille Polito
>
> Research Engineer
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
> *Web:* *http://guillep.github.io* 
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>

 



>>>
>>
>>
>


-- 



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

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

[Stephane Ducasse]

Esteban it would be good to make the remote handling more robust because
many people face
this problem.

On Tue, Oct 17, 2017 at 11:53 AM, Esteban Lorenzano 
wrote:

> no is ok.
> with the pharo version I know the iceberg version :)
>
> anyway your problem is that the remote for pharo is bad.
>
> you added g...@github.com:pharo/pharo.git and I do not think that exists.
> Correct one is:
>
> g...@github.com:pharo-project/pharo.git
>
> Esteban
>
>
> On 17 Oct 2017, at 11:51, Hernán Morales Durand 
> wrote:
>
> I don't see any easy way to find the Iceberg version.
>
> Should I update Iceberg using this script also in Pharo 7?
>
> "Restore defaults"
> Iceberg enableMetacelloIntegration: false.
> MetacelloPharo30Platform select.
>
> "Update metacello"
> Metacello new
>   baseline: 'Metacello';
>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>   onConflict: [:e | e useIncoming ];
>   get;
>   load.
>
> "Update iceberg"
>  #(
> 'Iceberg-UI'
> 'Iceberg-Plugin-GitHub'
> 'Iceberg-Plugin'
> 'Iceberg-Metacello-Integration'
> 'Iceberg-Libgit-Tonel'
> 'Iceberg-Libgit-Filetree'
> 'Iceberg-Libgit'
> 'Iceberg'
> 'LibGit-Core')
> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
> #removeFromSystem ].
> Metacello new
>   baseline: 'Iceberg';
>   repository: 'github://pharo-vcs/iceberg:v0.6';
>   load.
>
> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand 
> :
>
>> Hi Esteban,
>>
>> This one:
>>
>> wget -O- get.pharo.org/70+vm | bash -
>>
>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :
>>
>>> which Pharo version (and Iceberg version) do you have?
>>>
>>> Esteban
>>>
>>> On 17 Oct 2017, at 04:36, Hernán Morales Durand <
>>> hernan.mora...@gmail.com> wrote:
>>>
>>> Hi Guille,
>>>
>>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>>> ribute-a-fix-to-Pharo
>>>
>>> This part is not working for me: "Go back to iceberg, right click on the
>>> pharo repository and go to the *Pharo* entry. You'll see the option *Create
>>> new branch from Fogbugz issue*."
>>>
>>> Because there is no such "Pharo" option in the menu. See the attached
>>> screenshot.
>>>
>>> Did I miss something?
>>> Any suggestion?
>>>
>>>
>>> 2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
 comments, they are welcome.

 Guille

 --

 Guille Polito

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


 *Web:* *http://guillep.github.io* 
 *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>

>>>
>>> 
>>>
>>>
>>>
>>
>
>

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

[Hernán Morales Durand]

2017-10-17 7:42 GMT-03:00 Hernán Morales Durand :

> Thank you Esteban, that was the problem! :)
>
> Maybe guille wants to clarify the correct remote repository in the page:
> https://github.com/guillep/PharoIntegrationProcess/wiki/
> Contribute-a-fix-to-Pharo after "You can click on the *Add remote* option
> and configure a remote with a name and repository url."
>
> Another thing. I created a PR with a fix for this bug :
> https://pharo.fogbugz.com/f/cases/17754/CheckBoxModel-
> RadioButtonModel-ignore-disable following the guide to the Step 3.
> However I couldn't view any PR in my Github page (see attach).
>
>
Ah, it is in the pharo repository:
https://github.com/pharo-project/pharo/pulls
Cool




> Do I miss something?
>
>
> 2017-10-17 6:53 GMT-03:00 Esteban Lorenzano :
>
>> no is ok.
>> with the pharo version I know the iceberg version :)
>>
>> anyway your problem is that the remote for pharo is bad.
>>
>> you added g...@github.com:pharo/pharo.git and I do not think that exists.
>> Correct one is:
>>
>> g...@github.com:pharo-project/pharo.git
>>
>> Esteban
>>
>>
>> On 17 Oct 2017, at 11:51, Hernán Morales Durand 
>> wrote:
>>
>> I don't see any easy way to find the Iceberg version.
>>
>> Should I update Iceberg using this script also in Pharo 7?
>>
>> "Restore defaults"
>> Iceberg enableMetacelloIntegration: false.
>> MetacelloPharo30Platform select.
>>
>> "Update metacello"
>> Metacello new
>>   baseline: 'Metacello';
>>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>>   onConflict: [:e | e useIncoming ];
>>   get;
>>   load.
>>
>> "Update iceberg"
>>  #(
>> 'Iceberg-UI'
>> 'Iceberg-Plugin-GitHub'
>> 'Iceberg-Plugin'
>> 'Iceberg-Metacello-Integration'
>> 'Iceberg-Libgit-Tonel'
>> 'Iceberg-Libgit-Filetree'
>> 'Iceberg-Libgit'
>> 'Iceberg'
>> 'LibGit-Core')
>> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil:
>> #removeFromSystem ].
>> Metacello new
>>   baseline: 'Iceberg';
>>   repository: 'github://pharo-vcs/iceberg:v0.6';
>>   load.
>>
>> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand > >:
>>
>>> Hi Esteban,
>>>
>>> This one:
>>>
>>> wget -O- get.pharo.org/70+vm | bash -
>>>
>>> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :
>>>
 which Pharo version (and Iceberg version) do you have?

 Esteban

 On 17 Oct 2017, at 04:36, Hernán Morales Durand <
 hernan.mora...@gmail.com> wrote:

 Hi Guille,

 In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
 ribute-a-fix-to-Pharo

 This part is not working for me: "Go back to iceberg, right click on
 the pharo repository and go to the *Pharo* entry. You'll see the
 option *Create new branch from Fogbugz issue*."

 Because there is no such "Pharo" option in the menu. See the attached
 screenshot.

 Did I miss something?
 Any suggestion?


 2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>
> --
>
> Guille Polito
>
> Research Engineer
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
> *Web:* *http://guillep.github.io* 
> *Phone: *+33 06 52 70 66 13
>

 



>>>
>>
>>
>

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

[Esteban Lorenzano]

no is ok.
with the pharo version I know the iceberg version :)

anyway your problem is that the remote for pharo is bad.

you added g...@github.com :pharo/pharo.git and I do not 
think that exists. 
Correct one is: 

g...@github.com :pharo-project/pharo.git

Esteban


> On 17 Oct 2017, at 11:51, Hernán Morales Durand  
> wrote:
> 
> I don't see any easy way to find the Iceberg version.
> 
> Should I update Iceberg using this script also in Pharo 7?
> 
> "Restore defaults"
> Iceberg enableMetacelloIntegration: false.
> MetacelloPharo30Platform select.
> 
> "Update metacello" 
> Metacello new
>   baseline: 'Metacello';
>   repository: 'github://metacello/metacello:Pharo6.1/repository';
>   onConflict: [:e | e useIncoming ];
>   get;
>   load.
> 
> "Update iceberg"
>  #(
> 'Iceberg-UI' 
> 'Iceberg-Plugin-GitHub' 
> 'Iceberg-Plugin' 
> 'Iceberg-Metacello-Integration' 
> 'Iceberg-Libgit-Tonel' 
> 'Iceberg-Libgit-Filetree' 
> 'Iceberg-Libgit' 
> 'Iceberg' 
> 'LibGit-Core') 
> do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem ].
> Metacello new
>   baseline: 'Iceberg';
>   repository: 'github://pharo-vcs/iceberg:v0.6';
>   load.
> 
> 2017-10-17 6:46 GMT-03:00 Hernán Morales Durand  >:
> Hi Esteban,
> 
> This one:
> 
> wget -O- get.pharo.org/70+vm  | bash -
> 
> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano  >:
> which Pharo version (and Iceberg version) do you have?
> 
> Esteban
> 
>> On 17 Oct 2017, at 04:36, Hernán Morales Durand > > wrote:
>> 
>> Hi Guille,
>> 
>> In 
>> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>>  
>> 
>> 
>> This part is not working for me: "Go back to iceberg, right click on the 
>> pharo repository and go to the Pharo entry. You'll see the option Create new 
>> branch from Fogbugz issue."
>> 
>> Because there is no such "Pharo" option in the menu. See the attached 
>> screenshot.
>> 
>> Did I miss something?
>> Any suggestion?
>> 
>> 
>> 2017-08-10 12:17 GMT-03: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/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
>> 
>> Research Engineer
>> French National Center for Scientific Research - http://www.cnrs.fr 
>> 
>> 
>> 
>> Web: http://guillep.github.io 
>> Phone: +33 06 52 70 66 13
>> 
>> 
> 
> 
> 

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

[Hernán Morales Durand]

I don't see any easy way to find the Iceberg version.

Should I update Iceberg using this script also in Pharo 7?

"Restore defaults"
Iceberg enableMetacelloIntegration: false.
MetacelloPharo30Platform select.

"Update metacello"
Metacello new
  baseline: 'Metacello';
  repository: 'github://metacello/metacello:Pharo6.1/repository';
  onConflict: [:e | e useIncoming ];
  get;
  load.

"Update iceberg"
 #(
'Iceberg-UI'
'Iceberg-Plugin-GitHub'
'Iceberg-Plugin'
'Iceberg-Metacello-Integration'
'Iceberg-Libgit-Tonel'
'Iceberg-Libgit-Filetree'
'Iceberg-Libgit'
'Iceberg'
'LibGit-Core')
do: [ :each | (each asPackageIfAbsent: [ nil ]) ifNotNil: #removeFromSystem
].
Metacello new
  baseline: 'Iceberg';
  repository: 'github://pharo-vcs/iceberg:v0.6';
  load.

2017-10-17 6:46 GMT-03:00 Hernán Morales Durand :

> Hi Esteban,
>
> This one:
>
> wget -O- get.pharo.org/70+vm | bash -
>
> 2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :
>
>> which Pharo version (and Iceberg version) do you have?
>>
>> Esteban
>>
>> On 17 Oct 2017, at 04:36, Hernán Morales Durand 
>> wrote:
>>
>> Hi Guille,
>>
>> In https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
>> ribute-a-fix-to-Pharo
>>
>> This part is not working for me: "Go back to iceberg, right click on the
>> pharo repository and go to the *Pharo* entry. You'll see the option *Create
>> new branch from Fogbugz issue*."
>>
>> Because there is no such "Pharo" option in the menu. See the attached
>> screenshot.
>>
>> Did I miss something?
>> Any suggestion?
>>
>>
>> 2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
>>> comments, they are welcome.
>>>
>>> Guille
>>>
>>> --
>>>
>>> Guille Polito
>>>
>>> Research Engineer
>>> French National Center for Scientific Research - *http://www.cnrs.fr*
>>> 
>>>
>>>
>>> *Web:* *http://guillep.github.io* 
>>> *Phone: *+33 06 52 70 66 13
>>>
>>
>> 
>>
>>
>>
>

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

[Hernán Morales Durand]

Hi Esteban,

This one:

wget -O- get.pharo.org/70+vm | bash -

2017-10-17 3:36 GMT-03:00 Esteban Lorenzano :

> which Pharo version (and Iceberg version) do you have?
>
> Esteban
>
> On 17 Oct 2017, at 04:36, Hernán Morales Durand 
> wrote:
>
> Hi Guille,
>
> In https://github.com/guillep/PharoIntegrationProcess/wiki/
> Contribute-a-fix-to-Pharo
>
> This part is not working for me: "Go back to iceberg, right click on the
> pharo repository and go to the *Pharo* entry. You'll see the option *Create
> new branch from Fogbugz issue*."
>
> Because there is no such "Pharo" option in the menu. See the attached
> screenshot.
>
> Did I miss something?
> Any suggestion?
>
>
> 2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
>> comments, they are welcome.
>>
>> Guille
>>
>> --
>>
>> Guille Polito
>>
>> Research Engineer
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>> *Web:* *http://guillep.github.io* 
>> *Phone: *+33 06 52 70 66 13
>>
>
> 
>
>
>

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

[Esteban Lorenzano]

which Pharo version (and Iceberg version) do you have?

Esteban

> On 17 Oct 2017, at 04:36, Hernán Morales Durand  
> wrote:
> 
> Hi Guille,
> 
> In 
> https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo
>  
> 
> 
> This part is not working for me: "Go back to iceberg, right click on the 
> pharo repository and go to the Pharo entry. You'll see the option Create new 
> branch from Fogbugz issue."
> 
> Because there is no such "Pharo" option in the menu. See the attached 
> screenshot.
> 
> Did I miss something?
> Any suggestion?
> 
> 
> 2017-08-10 12:17 GMT-03: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/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
> 
> Research Engineer
> French National Center for Scientific Research - http://www.cnrs.fr 
> 
> 
> 
> Web: http://guillep.github.io 
> Phone: +33 06 52 70 66 13
> 
> 

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

[Hernán Morales Durand]

Hi Guille,

In
https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to-Pharo

This part is not working for me: "Go back to iceberg, right click on the
pharo repository and go to the *Pharo* entry. You'll see the option *Create
new branch from Fogbugz issue*."

Because there is no such "Pharo" option in the menu. See the attached
screenshot.

Did I miss something?
Any suggestion?


2017-08-10 12:17 GMT-03: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 everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13
>

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

[Hernán Morales Durand]

2017-08-10 18:20 GMT-03:00 Guillermo Polito :

>
>
> 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 to
> test. Basically, windows has problems with long paths but there are
> workarounds. Icerberg works by default without any changes (same bugs as in
> linux and osx at least :)). Here are my notes to make it work:
>
> * Download latest pharo:
>   - http://files.pharo.org/image/70/latest-32.zip
>   - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip
>
> * Clone using sourcetree
>This is very slow and failed to checkout (not clone) because of the
> "Filename too long errors"
>
> I found for this the following workaround: http://pingec.si/blog/
> articles/msysgit-longpath/
>
> Once I did that, sourcetree worked nicely, and I could commit and change
> branches using iceberg.
>
> Warning: I did not test making changes on the "long files" to see what
> happens...
>

I tested it on Windows with msysgit.

First you have to make the git clone

$ git clone https://github.com/hernanmd/pharo.git

You have to ***let it fail***

...
"fatal: unable to checkout working tree"
...

Then

$ cd pharo/
$ git config core.longpaths true
$ git checkout -f HEAD

Checking out files: 100% (107983/107983), done.
Your branch is up-to-date with 'origin/development'.

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] 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] Writeup: how to contribute to Pharo

[Stephane Ducasse]

Hi Niolai
thanks for raising this issue. The description should be migrated to
Pharo github.

Stef

On Thu, Aug 31, 2017 at 12:42 AM, Nicolai Hess  wrote:
>
>
> 2017-08-31 0:28 GMT+02:00 Cyril Ferlicot D. :
>>
>> Le 31/08/2017 à 00:06, Nicolai Hess a écrit :
>> > 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.
>> >
>>
>> Hi,
>>
>> I'll not be of a great help here since I only reviewed PR via the github
>> interface for now but I know that Guille wrote this guide:
>>
>> https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-Process
>>
>> There is a review process discription.
>
>
> Thank you Cyril.
>
> Do we have a list of links to this and other usefull articles or how did you
> know about this article?
>
>

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

[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

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  >:
>
>> 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 everything is smooth. If you have
>> comments, they are welcome.
>>
>
>
>
> [image: Inline-Bild 1]
>
>
> In 

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

[Marcus Denker]

> On 31 Aug 2017, at 00:06, 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 ?
> 

Hi,

Cyril send already the links to the description…

I have to admit that i am myself in the “this is very very slow and cumbersome” 
phase of things… we need to streamline the process
(I manage to do last week one pull request and this week one, this is not the 
speed that i want ;-)

Marcus

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

[Cyril Ferlicot]

On Thu, Aug 31, 2017 at 12:42 AM, Nicolai Hess  wrote:
>
> Thank you Cyril.
>
> Do we have a list of links to this and other usefull articles or how did you
> know about this article?
>
>

Most of those articles comes from the same wiki that Guille gave in
the first message of this thread. I just explored it :)
But for the review process one I had to ask to Guille because I did
not though I could have found it under "Pharo Development Process".

And for some other articles I search on google. (To get the stHub to
git migration script of Peter for example)

-- 
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 0:28 GMT+02:00 Cyril Ferlicot D. :

> Le 31/08/2017 à 00:06, Nicolai Hess a écrit :
> > 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.
> >
>
> Hi,
>
> I'll not be of a great help here since I only reviewed PR via the github
> interface for now but I know that Guille wrote this guide:
> https://github.com/guillep/PharoIntegrationProcess/wiki/
> Pharo-Development-Process
>
> There is a review process discription.
>

Thank you Cyril.

Do we have a list of links to this and other usefull articles or how did
you know about this article?

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

[Cyril Ferlicot D.]

Le 31/08/2017 à 00:06, Nicolai Hess a écrit :
> 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.
> 

Hi,

I'll not be of a great help here since I only reviewed PR via the github
interface for now but I know that Guille wrote this guide:
https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-Process

There is a review process discription.

>     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.
> 

To create a fix you don't really need a fork totally up to date with the
origin repository but it's recommended to sync once in a while to not
create conflics if changes happen in the same part of the system that
you'll change.

The process is described here:
https://github.com/guillep/PharoIntegrationProcess/wiki/Keep-your-repo-in-sync

In general this will do the trick:

$ git checkout development (if not already on development)
$ git pull [PHARO_ORIGIN] development
$ git push [FORK_ORIGIN] development

> 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 ?
> 
> 
I use the new process but I already had some knowledge of git. I used it
to manage team work at the university and I used it with smalltalk's
projects and file tree. Also I asked a looot of questions to
esteban/pavel/guille. The process need to be improved again and I still
often have troubles. (I got one vm crash and two iceberg crash today
while contributing for example).

I try to report the maximum of my reproducible problem here:
https://github.com/pharo-vcs/iceberg/issues

If you see trouble with Iceberg it could be cool to give info to help to
ease the contribution process.

For your last question, the resources I use are mostly the wiki of
Guille: https://github.com/guillep/PharoIntegrationProcess/wiki

My knowledge of git and the help of people like esteban/guille/pavel/marcus…

I hope some of those resources can help you.

-- 
Cyril Ferlicot
https://ferlicot.fr

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



signature.asc
Description: OpenPGP digital signature

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

[Nicolai Hess]

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 
 :

> 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 everything is smooth. If you have
> comments, they are welcome.
>



 [image: Inline-Bild 1]


 In option 2, I think this should be "Click on the Edit button",

>>>
>>> Thanks, fixed!
>>>




>
> Guille
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>


>>>
>>>
>>> --
>>>
>>>
>>>
>>> Guille Polito
>>>
>>>
>>> Research Engineer
>>>
>>> French National Center for 

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

[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  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 :
>>>
 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 everything is smooth. If you have
 comments, they are welcome.

>>>
>>>
>>>
>>> [image: Inline-Bild 1]
>>>
>>>
>>> In option 2, I think this should be "Click on the Edit button",
>>>
>>
>> Thanks, fixed!
>>
>>>
>>>
>>>
>>>

 Guille

 --



 Guille Polito


 Research Engineer

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



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

 *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>

>>>
>>>
>>
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>>
>> Research Engineer
>>
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>>
>> *Web:* *http://guillep.github.io* 
>>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
>
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>

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

[Guillermo Polito]

I extended the document with some windows specific instructions also.

On Fri, Aug 11, 2017 at 9:31 AM, Guillermo Polito  wrote:

>
>
> On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess 
> wrote:
>
>>
>>
>> 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 everything is smooth. If you have
>>> comments, they are welcome.
>>>
>>
>>
>>
>> [image: Inline-Bild 1]
>>
>>
>> In option 2, I think this should be "Click on the Edit button",
>>
>
> Thanks, fixed!
>
>>
>>
>>
>>
>>>
>>> Guille
>>>
>>> --
>>>
>>>
>>>
>>> Guille Polito
>>>
>>>
>>> Research Engineer
>>>
>>> French National Center for Scientific Research - *http://www.cnrs.fr*
>>> 
>>>
>>>
>>>
>>> *Web:* *http://guillep.github.io* 
>>>
>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>>
>>
>>
>
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>



-- 



Guille Polito


Research Engineer

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




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

*Phone: *+33 06 52 70 66 13

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

[Guillermo Polito]

On Fri, Aug 11, 2017 at 12:34 AM, Nicolai Hess 
wrote:

>
>
> 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 everything is smooth. If you have
>> comments, they are welcome.
>>
>
>
>
> [image: Inline-Bild 1]
>
>
> In option 2, I think this should be "Click on the Edit button",
>

Thanks, fixed!

>
>
>
>
>>
>> Guille
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>>
>> Research Engineer
>>
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>>
>> *Web:* *http://guillep.github.io* 
>>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
>


-- 



Guille Polito


Research Engineer

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




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

*Phone: *+33 06 52 70 66 13

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

[Guillermo Polito]

On Thu, Aug 10, 2017 at 11:58 PM, Nicolai Hess 
wrote:

>
>
> 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 could contribute
>>
>
> Hard topic. I'm taking benefit of my gf's windows computer right now to
> test. Basically, windows has problems with long paths but there are
> workarounds. Icerberg works by default without any changes (same bugs as in
> linux and osx at least :)). Here are my notes to make it work:
>
> * Download latest pharo:
>   - http://files.pharo.org/image/70/latest-32.zip
>   - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip
>
> * Clone using sourcetree
>This is very slow and failed to checkout (not clone) because of the
> "Filename too long errors"
>
>
> What does "clone using sourcetree" mean?
>

Yeap, sorry. I meant

https://www.sourcetreeapp.com/

It is a free graphical git client from atlassian.

In windows I default to graphical tools :). I assume not most of the people
will install a msys environment on their machines (but maybe I'm wrong...).


>
>
> I found for this the following workaround: http://pingec.si/blog/articles
> /msysgit-longpath/
>
> Once I did that, sourcetree worked nicely, and I could commit and change
> branches using iceberg.
>
> Warning: I did not test making changes on the "long files" to see what
> happens...
>
>
>>  -  that #development branch is used instead of master
>>
>
> I'll make another writeup about the entire process.
>
>
>>   - how one can keep his own fork up to date
>>
>
> And about this one too
>
>
>>
>> Also it would be good to have the AboutBox in Pharo with the build number
>>  again.
>>
>
>> Because the ZeroCnnf just gives you a Pharo.image and nobody knows what
>> the build number
>> or sha was to reproduce how old or new this is.
>>
>
> Well, actually right now
>
> SystemVersion current
>
> has the hash of the commit the image was generated from if you check the
> inspector. It's then a UI problem and easy to fix. Maybe somebody could use
> this to try making a pull request?
>
> Then, we could add a build number in SystemVersion of course.
>
> Guille
>
>>
>> Thanks
>> T.
>>
>>
>> *Gesendet:* Donnerstag, 10. August 2017 um 17:17 Uhr
>> *Von:* "Guillermo Polito" 
>> *An:* "Discusses Development of Pharo" 
>> *Betreff:* [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/Cont
>> ribute-a-fix-to-Pharo
>>
>> Of course, expect bugs on it :) Not everything is smooth. If you have
>> comments, they are welcome.
>>
>> Guille
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>>
>>
>> Research Engineer
>>
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>>
>>
>>
>> *Web:* *http://guillep.github.io* 
>>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
>
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>
>
>


-- 



Guille Polito


Research Engineer

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




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

*Phone: *+33 06 52 70 66 13

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

[Pavel Krivanek]

2017-08-11 0:53 GMT+02:00 Nicolai Hess :

>
>
> 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 everything is smooth. If you have
>> comments, they are welcome.
>>
>> Guille
>>
>
> Maybe I mixed something up, but following the other (pavel)howto  I
> thought that I would
> clone the origin repository, (and edit iceberg to use the local clone as
> the origin)
> and later define my (github)-fork as another remote.
>
> But in your screenshots, it looks like you cloned your pharo fork, and set
> the original pharo git project as another remote.
> Are both options equal and just differe in which remote is called "pharo"
> and which is called "origin" ?
>

To have pharo-project/pharo as the origin is a scheme that Esteban is using
and in past Iceberg had troubles to enable Pharo pluggin correctly for
repositories that were not set like that. Now it does not matter, however
if you will use your local repository clone more, you will have forks of
other people as remotes too and then it is quite natural to have your own
fork as only one of them.

-- Pavel



>
>
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>>
>> Research Engineer
>>
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>>
>> *Web:* *http://guillep.github.io* 
>>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
>

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

[Guillermo Polito]

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)
>>
>>
>> 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
>>
>
> Maybe I mixed something up, but following the other (pavel)howto  I
> thought that I would
> clone the origin repository, (and edit iceberg to use the local clone as
> the origin)
> and later define my (github)-fork as another remote.
>
> But in your screenshots, it looks like you cloned your pharo fork, and set
> the original pharo git project as another remote.
> Are both options equal and just differe in which remote is called "pharo"
> and which is called "origin" ?
>

Bord are similar. If you clone pharo, you set your fork as push remote. If
you clone ur fork you set pharo as pull remote. I don't remember if iceberg
lets u rename a remote, but I think the remote name is not important but
the URL.

In any case you need both remotes. If you don't have pharo as remote you
wont see the pharo plugin.

>
>
>
>>
>> --
>>
>>
>>
>> Guille Polito
>>
>>
>> Research Engineer
>>
>> French National Center for Scientific Research - *http://www.cnrs.fr*
>> 
>>
>>
>>
>> *Web:* *http://guillep.github.io* 
>>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
> --



Guille Polito


Research Engineer

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




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

*Phone: *+33 06 52 70 66 13

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

[Nicolai Hess]

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 everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>

Maybe I mixed something up, but following the other (pavel)howto  I thought
that I would
clone the origin repository, (and edit iceberg to use the local clone as
the origin)
and later define my (github)-fork as another remote.

But in your screenshots, it looks like you cloned your pharo fork, and set
the original pharo git project as another remote.
Are both options equal and just differe in which remote is called "pharo"
and which is called "origin" ?


>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>

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

[Nicolai Hess]

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 everything is smooth. If you have
> comments, they are welcome.
>



[image: Inline-Bild 1]


In option 2, I think this should be "Click on the Edit button",




>
> Guille
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>

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

[Nicolai Hess]

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 just clone via command line
git clone 




--
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

[Cyril Ferlicot D.]

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,
59650 Villeneuve d'ascq France



signature.asc
Description: OpenPGP digital signature

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

[Nicolai Hess]

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 could contribute
>

Hard topic. I'm taking benefit of my gf's windows computer right now to
test. Basically, windows has problems with long paths but there are
workarounds. Icerberg works by default without any changes (same bugs as in
linux and osx at least :)). Here are my notes to make it work:

* Download latest pharo:
  - http://files.pharo.org/image/70/latest-32.zip
  - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip

* Clone using sourcetree
   This is very slow and failed to checkout (not clone) because of the
"Filename too long errors"


What does "clone using sourcetree" mean?



I found for this the following workaround: http://pingec.si/blog/
articles/msysgit-longpath/

Once I did that, sourcetree worked nicely, and I could commit and change
branches using iceberg.

Warning: I did not test making changes on the "long files" to see what
happens...


>  -  that #development branch is used instead of master
>

I'll make another writeup about the entire process.


>   - how one can keep his own fork up to date
>

And about this one too


>
> Also it would be good to have the AboutBox in Pharo with the build number
>  again.
>

> Because the ZeroCnnf just gives you a Pharo.image and nobody knows what
> the build number
> or sha was to reproduce how old or new this is.
>

Well, actually right now

SystemVersion current

has the hash of the commit the image was generated from if you check the
inspector. It's then a UI problem and easy to fix. Maybe somebody could use
this to try making a pull request?

Then, we could add a build number in SystemVersion of course.

Guille

>
> Thanks
> T.
>
>
> *Gesendet:* Donnerstag, 10. August 2017 um 17:17 Uhr
> *Von:* "Guillermo Polito" 
> *An:* "Discusses Development of Pharo" 
> *Betreff:* [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/Cont
> ribute-a-fix-to-Pharo
>
> Of course, expect bugs on it :) Not everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>
> --
>
>
>
> Guille Polito
>
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>



-- 



Guille Polito


Research Engineer

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




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

*Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>

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

[Stephane Ducasse]

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)
>
> https://github.com/guillep/PharoIntegrationProcess/wiki/Cont
> ribute-a-fix-to-Pharo
>
> Of course, expect bugs on it :) Not everything is smooth. If you have
> comments, they are welcome.
>
> Guille
>
> --
>
>
>
> Guille Polito
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>

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

[Guillermo Polito]

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 to
test. Basically, windows has problems with long paths but there are
workarounds. Icerberg works by default without any changes (same bugs as in
linux and osx at least :)). Here are my notes to make it work:

* Download latest pharo:
  - http://files.pharo.org/image/70/latest-32.zip
  - http://files.pharo.org/vm/pharo-spur32/win/stable-20170720.zip

* Clone using sourcetree
   This is very slow and failed to checkout (not clone) because of the
"Filename too long errors"

I found for this the following workaround:
http://pingec.si/blog/articles/msysgit-longpath/

Once I did that, sourcetree worked nicely, and I could commit and change
branches using iceberg.

Warning: I did not test making changes on the "long files" to see what
happens...


>  -  that #development branch is used instead of master
>

I'll make another writeup about the entire process.


>   - how one can keep his own fork up to date
>

And about this one too


>
> Also it would be good to have the AboutBox in Pharo with the build number
>  again.
>

> Because the ZeroCnnf just gives you a Pharo.image and nobody knows what
> the build number
> or sha was to reproduce how old or new this is.
>

Well, actually right now

SystemVersion current

has the hash of the commit the image was generated from if you check the
inspector. It's then a UI problem and easy to fix. Maybe somebody could use
this to try making a pull request?

Then, we could add a build number in SystemVersion of course.

Guille

>
> Thanks
> T.
>
>
> *Gesendet:* Donnerstag, 10. August 2017 um 17:17 Uhr
> *Von:* "Guillermo Polito" 
> *An:* "Discusses Development of Pharo" 
> *Betreff:* [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
>
>
>
> Research Engineer
>
> French National Center for Scientific Research - *http://www.cnrs.fr*
> 
>
>
>
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>



-- 



Guille Polito


Research Engineer

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




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

*Phone: *+33 06 52 70 66 13

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

[Torsten Bergmann]

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 Pharo with the build number  again.

 

Because the ZeroCnnf just gives you a Pharo.image and nobody knows what the build number
or sha was to reproduce how old or new this is.

 

Thanks

T.
 

 

Gesendet: Donnerstag, 10. August 2017 um 17:17 Uhr
Von: "Guillermo Polito" 
An: "Discusses Development of Pharo" 
Betreff: [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

			 

			Research Engineer

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

			 

			 

			Web: http://guillep.github.io

			Phone: +33 06 52 70 66 13