Re: [Pharo-dev] Contribute to pharo8.0 ?

[Pavel Krivanek]

It is working now again as expected.

The only difference is that you need to use "Github-Create new branch for
issue..." instead of "Pharo-Create new branch for issue..." for the new
issues reported on GitHub.

-- Pavel

st 30. 1. 2019 v 9:42 odesílatel Guillermo Polito 
napsal:

> Hi,
>
> there is an issue for this problem,
>
> https://github.com/pharo-project/pharo/issues/2379
>
> We have identified the cause, I'll propose a fix now
>
> On Wed, Jan 30, 2019 at 8:44 AM ducasse  wrote:
>
>> >
>> > There is currently a bug eating one character of the commit hash. So
>> > Iceberg does not find the hash and thinks we need a fetch. So currently
>> > we need to checkout Pharo8.0 in order to be in a good state :(
>>
>> OOPs is there a bug entry?
>> >
>> >> I also don't understand how to make an issue branch for
>> >>
>> >> https://github.com/pharo-project/pharo/issues/2395
>> >>
>> >> Is it Iceberg > Pharo > Create new branch for issue or Iceberg >
>> Github > Create new branch for issue ?
>> >
>> > Just create a branch and choose the option to create a branch from a
>> > Github option.
>> >
>> > The other one was for Manuscript and is now useless for Pharo 8. I
>> > opened an issue in Iceberg to remove it but I did not got the time to
>> > contribute the change.
>> >
>> >> What is the difference ?
>> >> What about the Remote ?
>> >> Can I work with only an issue on GitHub ?
>> >>
>> >
>> > Yes!
>> >
>> > What I am doing currently:
>> >
>> > - Open an issue XX
>> > - Sync my fork Pharo8.0 branch via command line (This is optional and
>> > can also be done in Pharo. I just do it via command line because I like
>> > it better that way)
>>
>> how do you do it? Pull?
>>
>> > - Download a Pharo 8 image
>> > - Checkout the Pharo8.0 branch to get in a clean state because of the
>> > hash eating bug I mentioned earlier
>> > - Create a new branch from a github issue of the pharo remote
>> > - Do the changes and commit. I add `Fixes #XX` in the commit message to
>> > close automatically the issue when the PR is merged.
>> > - Push to my remote
>> > - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull
>> > request
>>
>> and checkout the pharo 8 branch to fix the next one.
>> >
>> >> Is the documentation
>> >>
>> >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo
>> >>
>> >> really up to date ?
>> >>
>> >
>> > No
>> >
>> > We should correct the hash eating bug before updating it I think.
>> >
>> >> Sven
>> >>
>> >>
>> >
>> >
>> > --
>> > Cyril Ferlicot
>> > https://ferlicot.fr
>> >
>>
>>
>>
>>
>
> --
>
>
>
> 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] [ANN] Pharo open documentation

[Cyril Ferlicot D.]

Le 30/01/2019 à 21:25, Hernán Morales Durand a écrit :
> Hi Cyril,
> 
> Nice project!
> I think you forgot to add the URL :
> https://github.com/pharo-open-documentation/awesome-pharo
> 
> Note: the Zinc entry has a reference to Cytoscape.js?
> 

Good catch! Just an error of copy past when I reorganized the entries :)
It should go at the end of TelescopeCytoscape line.

Thank you.

> Cheers,
> 
> Hernán
> 


-- 
Cyril Ferlicot
https://ferlicot.fr



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-dev] [ANN] Pharo open documentation

[ducasse]

I fix it in the pharoweekly blog post :)

> On 30 Jan 2019, at 21:27, Julien  wrote:
> 
> Looks like an error.
> 
> Will fix it.
> 
> Julien
> 
> ---
> Julien Delplanque
> Doctorant à l’Université de Lille
> http://juliendelplanque.be/phd.html 
> Equipe Rmod, Inria
> Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq
> Numéro de téléphone: +333 59 35 86 40
> 
>> Le 30 janv. 2019 à 21:25, Hernán Morales Durand > > a écrit :
>> 
>> Hi Cyril,
>> 
>> Nice project!
>> I think you forgot to add the URL : 
>> https://github.com/pharo-open-documentation/awesome-pharo 
>> 
>> 
>> Note: the Zinc entry has a reference to Cytoscape.js?
>> 
>> Cheers,
>> 
>> Hernán
>> 
>> 
>> 
>> El mié., 30 ene. 2019 a las 11:01, Cyril Ferlicot (> >) escribió:
>> Hi everyone!
>> 
>> With some other members of the community we are proud to announce a
>> new effort on Pharo documentation.
>> 
>> We launched an organization pharo-open-documentation which is a
>> user-maintained documentation related to Pharo environment, language,
>> and libraries.
>> 
>> Currently it has three main projects:
>> - pharo-wiki : Wiki related to the Pharo programming language and 
>> environment.
>> - awesome-pharo : A collection of awesome Pharo libraries, tools,
>> frameworks and software. We want to make this project a reference in
>> https://github.com/sindresorhus/awesome 
>> 
>> - awesome-pharo-ml : List of projects, books, booklets, papers, and
>> applications related to machine learning, AI, data science in Pharo.
>> 
>> Contributions are welcomed!
>> 
>> If you own a cool project in Pharo others could use in their own
>> projects, send us a PR to awesome-pharo!
>> If you have knowledge on Pharo or projects of Pharo, we would be glad
>> if you could contribute to the pharo-wiki! Don't forget to read the
>> contribution guidelines. ;)
>> 
>> We opened a Twitter to announce new entries on the pharo-wiki.
>> 
>> https://twitter.com/PharoOpen 
>> 
>> Have a nice day!
>> 
>> -- 
>> Cyril Ferlicot
>> https://ferlicot.fr 
>> 
> 

Re: [Pharo-dev] [ANN] Pharo open documentation

[Julien]

Looks like an error.

Will fix it.

Julien

---
Julien Delplanque
Doctorant à l’Université de Lille
http://juliendelplanque.be/phd.html
Equipe Rmod, Inria
Bâtiment B 40, Avenue Halley 59650 Villeneuve d'Ascq
Numéro de téléphone: +333 59 35 86 40

> Le 30 janv. 2019 à 21:25, Hernán Morales Durand  a 
> écrit :
> 
> Hi Cyril,
> 
> Nice project!
> I think you forgot to add the URL : 
> https://github.com/pharo-open-documentation/awesome-pharo 
> 
> 
> Note: the Zinc entry has a reference to Cytoscape.js?
> 
> Cheers,
> 
> Hernán
> 
> 
> 
> El mié., 30 ene. 2019 a las 11:01, Cyril Ferlicot ( >) escribió:
> Hi everyone!
> 
> With some other members of the community we are proud to announce a
> new effort on Pharo documentation.
> 
> We launched an organization pharo-open-documentation which is a
> user-maintained documentation related to Pharo environment, language,
> and libraries.
> 
> Currently it has three main projects:
> - pharo-wiki : Wiki related to the Pharo programming language and environment.
> - awesome-pharo : A collection of awesome Pharo libraries, tools,
> frameworks and software. We want to make this project a reference in
> https://github.com/sindresorhus/awesome 
> 
> - awesome-pharo-ml : List of projects, books, booklets, papers, and
> applications related to machine learning, AI, data science in Pharo.
> 
> Contributions are welcomed!
> 
> If you own a cool project in Pharo others could use in their own
> projects, send us a PR to awesome-pharo!
> If you have knowledge on Pharo or projects of Pharo, we would be glad
> if you could contribute to the pharo-wiki! Don't forget to read the
> contribution guidelines. ;)
> 
> We opened a Twitter to announce new entries on the pharo-wiki.
> 
> https://twitter.com/PharoOpen 
> 
> Have a nice day!
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr 
> 

Re: [Pharo-dev] [ANN] Pharo open documentation

[Hernán Morales Durand]

Hi Cyril,

Nice project!
I think you forgot to add the URL :
https://github.com/pharo-open-documentation/awesome-pharo

Note: the Zinc entry has a reference to Cytoscape.js?

Cheers,

Hernán



El mié., 30 ene. 2019 a las 11:01, Cyril Ferlicot ()
escribió:

> Hi everyone!
>
> With some other members of the community we are proud to announce a
> new effort on Pharo documentation.
>
> We launched an organization pharo-open-documentation which is a
> user-maintained documentation related to Pharo environment, language,
> and libraries.
>
> Currently it has three main projects:
> - pharo-wiki : Wiki related to the Pharo programming language and
> environment.
> - awesome-pharo : A collection of awesome Pharo libraries, tools,
> frameworks and software. We want to make this project a reference in
> https://github.com/sindresorhus/awesome
> - awesome-pharo-ml : List of projects, books, booklets, papers, and
> applications related to machine learning, AI, data science in Pharo.
>
> Contributions are welcomed!
>
> If you own a cool project in Pharo others could use in their own
> projects, send us a PR to awesome-pharo!
> If you have knowledge on Pharo or projects of Pharo, we would be glad
> if you could contribute to the pharo-wiki! Don't forget to read the
> contribution guidelines. ;)
>
> We opened a Twitter to announce new entries on the pharo-wiki.
>
> https://twitter.com/PharoOpen
>
> Have a nice day!
>
> --
> Cyril Ferlicot
> https://ferlicot.fr
>
>

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

[Norbert Hartl]

> Am 30.01.2019 um 20:23 schrieb ducasse :
> 
> it means this is a call for fork :)
> 
No! A fork from something not github to github is contraproductive. 

Norbert
>>> On 30 Jan 2019, at 16:58, Norbert Hartl  wrote:
>>> 
>>> 
>>> 
>>> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe :
>>> 
>>> 
>>> 
 On 3 Oct 2018, at 07:43, monty  wrote:
 
 I am the principal maintainer of those projects, but any PharoExtras dev 
 can contribute. And the blog below (which I plan on updating) provides 
 additional information on them.
>>> 
>>> Has there been any progress in this area ?
>>> 
>>> It would be really great if this important project moved to GitHub.
>>> 
>> +100
>> 
>> Norbert
> 

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

[ducasse]

it means this is a call for fork :)

> On 30 Jan 2019, at 16:58, Norbert Hartl  > wrote:
> 
> 
> 
>> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe > >:
>> 
>> 
>> 
>>> On 3 Oct 2018, at 07:43, monty >> > wrote:
>>> 
>>> I am the principal maintainer of those projects, but any PharoExtras dev 
>>> can contribute. And the blog below (which I plan on updating) provides 
>>> additional information on them.
>> 
>> Has there been any progress in this area ?
>> 
>> It would be really great if this important project moved to GitHub.
>> 
> +100
> 
> Norbert

Re: [Pharo-dev] [ANN] Pharo open documentation

[ducasse]

super nice effort!!!

> On 30 Jan 2019, at 15:00, Cyril Ferlicot  wrote:
> 
> Hi everyone!
> 
> With some other members of the community we are proud to announce a
> new effort on Pharo documentation.
> 
> We launched an organization pharo-open-documentation which is a
> user-maintained documentation related to Pharo environment, language,
> and libraries.
> 
> Currently it has three main projects:
> - pharo-wiki : Wiki related to the Pharo programming language and environment.
> - awesome-pharo : A collection of awesome Pharo libraries, tools,
> frameworks and software. We want to make this project a reference in
> https://github.com/sindresorhus/awesome
> - awesome-pharo-ml : List of projects, books, booklets, papers, and
> applications related to machine learning, AI, data science in Pharo.
> 
> Contributions are welcomed!
> 
> If you own a cool project in Pharo others could use in their own
> projects, send us a PR to awesome-pharo!
> If you have knowledge on Pharo or projects of Pharo, we would be glad
> if you could contribute to the pharo-wiki! Don't forget to read the
> contribution guidelines. ;)
> 
> We opened a Twitter to announce new entries on the pharo-wiki.
> 
> https://twitter.com/PharoOpen
> 
> Have a nice day!
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr
> 

[Pharo-dev] Debugger opening on user halt and not Object>>halt

[Thomas Dupriez]

Hello,

Does someone know which is the code responsible for the debugger opening 
on the halt of the user instead of Object>>halt (see picture)? It's neat 
but it's not the regular behaviour so I'm guessing it is handled 
somewhere specifically for halt messages?



Thomas

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

[Norbert Hartl]

> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe :
> 
> 
> 
>> On 3 Oct 2018, at 07:43, monty  wrote:
>> 
>> I am the principal maintainer of those projects, but any PharoExtras dev can 
>> contribute. And the blog below (which I plan on updating) provides 
>> additional information on them.
> 
> Has there been any progress in this area ?
> 
> It would be really great if this important project moved to GitHub.
> 
+100

Norbert

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

[Sven Van Caekenberghe]

> On 3 Oct 2018, at 07:43, monty  wrote:
> 
> I am the principal maintainer of those projects, but any PharoExtras dev can 
> contribute. And the blog below (which I plan on updating) provides additional 
> information on them.

Has there been any progress in this area ?

It would be really great if this important project moved to GitHub.

Sven

[Pharo-dev] [Pharo 8.0] Build #45: add g prefix to keep code compatible with git describes

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #45 was: SUCCESS.

The Pull Request #2417 was integrated: "add g prefix to keep code compatible 
with git describes"
Pull request url: https://github.com/pharo-project/pharo/pull/2417

Issue Url: https://pharo.fogbugz.com/f/cases/2379
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/45/

[Pharo-dev] [ANN] Pharo open documentation

[Cyril Ferlicot]

Hi everyone!

With some other members of the community we are proud to announce a
new effort on Pharo documentation.

We launched an organization pharo-open-documentation which is a
user-maintained documentation related to Pharo environment, language,
and libraries.

Currently it has three main projects:
- pharo-wiki : Wiki related to the Pharo programming language and environment.
- awesome-pharo : A collection of awesome Pharo libraries, tools,
frameworks and software. We want to make this project a reference in
https://github.com/sindresorhus/awesome
- awesome-pharo-ml : List of projects, books, booklets, papers, and
applications related to machine learning, AI, data science in Pharo.

Contributions are welcomed!

If you own a cool project in Pharo others could use in their own
projects, send us a PR to awesome-pharo!
If you have knowledge on Pharo or projects of Pharo, we would be glad
if you could contribute to the pharo-wiki! Don't forget to read the
contribution guidelines. ;)

We opened a Twitter to announce new entries on the pharo-wiki.

https://twitter.com/PharoOpen

Have a nice day!

-- 
Cyril Ferlicot
https://ferlicot.fr

[Pharo-dev] [Pharo 8.0] Build #44: 2414-failing-testAndMakeSureSuperSetupIsCalledAsFirstMessageInSetupMethodsOfTestCases

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #44 was: SUCCESS.

The Pull Request #2415 was integrated: 
"2414-failing-testAndMakeSureSuperSetupIsCalledAsFirstMessageInSetupMethodsOfTestCases"
Pull request url: https://github.com/pharo-project/pharo/pull/2415

Issue Url: https://pharo.fogbugz.com/f/cases/2414
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/44/

Re: [Pharo-dev] Contribute to pharo8.0 ?

[Guillermo Polito]

Hi,

there is an issue for this problem,

https://github.com/pharo-project/pharo/issues/2379

We have identified the cause, I'll propose a fix now

On Wed, Jan 30, 2019 at 8:44 AM ducasse  wrote:

> >
> > There is currently a bug eating one character of the commit hash. So
> > Iceberg does not find the hash and thinks we need a fetch. So currently
> > we need to checkout Pharo8.0 in order to be in a good state :(
>
> OOPs is there a bug entry?
> >
> >> I also don't understand how to make an issue branch for
> >>
> >> https://github.com/pharo-project/pharo/issues/2395
> >>
> >> Is it Iceberg > Pharo > Create new branch for issue or Iceberg > Github
> > Create new branch for issue ?
> >
> > Just create a branch and choose the option to create a branch from a
> > Github option.
> >
> > The other one was for Manuscript and is now useless for Pharo 8. I
> > opened an issue in Iceberg to remove it but I did not got the time to
> > contribute the change.
> >
> >> What is the difference ?
> >> What about the Remote ?
> >> Can I work with only an issue on GitHub ?
> >>
> >
> > Yes!
> >
> > What I am doing currently:
> >
> > - Open an issue XX
> > - Sync my fork Pharo8.0 branch via command line (This is optional and
> > can also be done in Pharo. I just do it via command line because I like
> > it better that way)
>
> how do you do it? Pull?
>
> > - Download a Pharo 8 image
> > - Checkout the Pharo8.0 branch to get in a clean state because of the
> > hash eating bug I mentioned earlier
> > - Create a new branch from a github issue of the pharo remote
> > - Do the changes and commit. I add `Fixes #XX` in the commit message to
> > close automatically the issue when the PR is merged.
> > - Push to my remote
> > - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull
> > request
>
> and checkout the pharo 8 branch to fix the next one.
> >
> >> Is the documentation
> >>
> >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo
> >>
> >> really up to date ?
> >>
> >
> > No
> >
> > We should correct the hash eating bug before updating it I think.
> >
> >> Sven
> >>
> >>
> >
> >
> > --
> > Cyril Ferlicot
> > https://ferlicot.fr
> >
>
>
>
>

-- 



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] [Pharo 7.0] Build #146: Revert "18764-Remove-external-dependencies-from-Kernel-Tests-"

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #146 was: SUCCESS.

The Pull Request #2411 was integrated: "Revert 
"18764-Remove-external-dependencies-from-Kernel-Tests-""
Pull request url: https://github.com/pharo-project/pharo/pull/2411

Issue Url: https://pharo.fogbugz.com/f/cases/revert
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo7.0/146/