Contributions about Pharo and Moose
Hi all, This afternoon, my bike didn't start (the battery got weaker every day this week, no surprise), so I've put it in charge and decided to take a ride on the latest Pharo and Moose versions instead :) First I downloaded the latest Pharo 4 image, opened a Workspace and got an error clicking on the right arrow of the window to display the menu. I searched opened cases and saw issue 13865 (cleaning MenuMorph) and added a comment about the fix I am not a contributor to Pharo right now though I'm willing to, I believe I could do some minor cases like that one (I might have to check first with my employer about some intellectual property agreement I've signed in the past, but I guess no problem here). BTW I took a look at the video and slides 'how to contribute', opened and account on SmalltalkHub but didn't get the mail to confirm my registration right now. My first question is just a confirmation: I saw in the slides that to commit slices, one has to be given write access by asking in this mailing list ? (In this case, I will when everything is ok). Second question is about Moose : I tried to load the Moose development configuration in this Pharo4 image (I like to play Candid) and got small errors (big ones too, I guess Moose is on the way to move to Pharo4 and there is still some hard work) I'm wondering if fogbugz is the place to report Moose bugs ? And what about other packages like for example (two of the errors I had) ConfigurationOfPetitSQLParser or Hashtable-simon_denier.31 ? Most of the Moose related issues on fogbugz seems to be related to integration into Pharo, not to Moose development or to other packages ? Is there a fogbugz or other site for Moose or do we report Moose bugs in this list ? What about external packages ? What is the process in that case ? Thanks in advance for your answers Regards, Alain
On 31/8/14 19:20, Alain Rastoul wrote:
Hi all,
This afternoon, my bike didn't start (the battery got weaker every day this week, no surprise), so I've put it in charge and decided to take a ride on the latest Pharo and Moose versions instead :)
:)
First I downloaded the latest Pharo 4 image, opened a Workspace and got an error clicking on the right arrow of the window to display the menu.
Thanks I will enter a bug entry. https://pharo.fogbugz.com/default.asp?13944 I searched opened cases and saw issue 13865 (cleaning MenuMorph) and added a comment about the fix I am not a contributor to Pharo right now though I'm willing to, I believe I could do some minor cases like that one (I might have to check first with my employer about Yes I probably introduced this bug.
some intellectual property agreement I've signed in the past, but I guess no problem here).
BTW I took a look at the video and slides 'how to contribute', opened and account on SmalltalkHub but didn't get the mail to confirm my registration right now.
I do not think that you get one.
My first question is just a confirmation: I saw in the slides that to commit slices, one has to be given write access by asking in this mailing list ? (In this case, I will when everything is ok).
Normally in the inbox everybody can commit. Let us know if you do not get it working.
Second question is about Moose : I tried to load the Moose development configuration in this Pharo4 image (I like to play Candid) and got small errors (big ones too, I guess Moose is on the way to move to Pharo4 and there is still some hard work)
for moose we have a ci server that loads it. so we should look at the script.
I'm wondering if fogbugz is the place to report Moose bugs ?
No there is a moose bugtracker on code.google
And what about other packages like for example (two of the errors I had) ConfigurationOfPetitSQLParser or Hashtable-simon_denier.31 ? Most of the Moose related issues on fogbugz seems to be related to integration into Pharo, not to Moose development or to other packages ? Is there a fogbugz or other site for Moose or do we report Moose bugs in this list ? What about external packages ? What is the process in that case ?
Thanks in advance for your answers
Regards,
Alain
Thank you Stef for your answers. For Moose, I will search on code.google, and about loading it in Pharo4, i tried the development version (since Pharo4 is in development I assumed the latest Moose configuration was needed), if a ci job can load it , sure that the problem is me ... wouldn't be the first time btw :) And you are right, there is no confirmation email (I was stupidely waiting for it, as it was stated on the web page iirc) but I got connected without. Great! Regards, Alain
participants (2)
-
Alain Rastoul -
stepharo