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

Pavel Krivanek pavel.krivanek at gmail.com
Fri Aug 11 02:13:04 EDT 2017


2017-08-11 0:53 GMT+02:00 Nicolai Hess <nicolaihess at gmail.com>:

>
>
> 2017-08-10 17:17 GMT+02:00 Guillermo Polito <guillermopolito at 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
>>
>
> 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*
>> <http://www.cnrs.fr>
>>
>>
>>
>> *Web:* *http://guillep.github.io* <http://guillep.github.io>
>>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20170811/f74f3442/attachment.html>


More information about the Pharo-dev mailing list