November 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Not happy with the issues feed from Google

by StÃ©phane Ducasse

I asked for the creation of bugtracker list

Nov. 18, 2010

Re: [Pharo-project] Issue 3210 in pharo: SimpleMorphic Integration

by pharo＠googlecode.com

Comment #3 on issue 3210 by stephane.ducasse: SimpleMorphic Integration http://code.google.com/p/pharo/issues/detail?id=3210 part one two and three are integrated

Nov. 18, 2010

Re: [Pharo-project] [ANN] Smalltalk Screencast

by StÃ©phane Ducasse

I cross my fingers for you. > > I know Laurent's screencasts are very good. I'm actually trying that business > model, in the future who knows :-) > Davide

Nov. 18, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by StÃ©phane Ducasse

>>> > > I fully agree that bugs are our concern, and that it is important to make > activity visible. I also understand and share your frustration that bug > reports are badly read and written. I just think that this works contra-productive. > - the subject of a feed message is bad: it is just the issue number > and the issue title, instead of adding what happened with the issue. I guess that you do not really measure the amount of work it can represent. The only way to be able to do that is to force people to write better bug tracker description and guess not a lot of people open a bug entry so a core of people is again doing that. > - the content of a feed message is bad: the context is missing. > >> - It reduces the searchability/usability of the mailing list archives; >>> Why? >>> I want to look for bug discussions there too and not using a bad google search engine. > > I think the problem most potential contributors have is one of too much information, > not too little. Giving them more, in a badly prepared format, is unlikely to help. We will see but what if it helps the contributors and make them more productive? So may be the solution is to add another mailing-list. what is clear for me is that I would love to get the changes like in squeak in the mailing-list in addition to all the bugtracker activity. Stef

Nov. 18, 2010

[Pharo-project] Issue 3271 in pharo: r isLiteralSymbol: #<= is broken

by pharo＠googlecode.com

Status: Accepted Owner: stephane.ducasse Labels: Milestone-1.2 Importance-High New issue 3271 by stephane.ducasse: r isLiteralSymbol: #<= is broken http://code.google.com/p/pharo/issues/detail?id=3271 Scanner isLiteralSymbol: #<= ... It works ok in Cuis. You can see #isLiteralSymbol: there. BTW, this was changed when I integrated the Compiler package from you, in April this year. If you want to see what else changed then, see change sets 0482, 0483 and 0484 in the Cuis updates. You can get Cuis and the zip file with the updates from http://www.jvuletich.org/Cuis/Index.html .

Nov. 18, 2010

Re: [Pharo-project] [ANN] Smalltalk Screencast

by Davide Varvello

I know Laurent's screencasts are very good. I'm actually trying that business model, in the future who knows :-) Davide StÃ©phane Ducasse wrote: > > great! > May be you should join effort with laurent. Because laurent screencasts > are really excellent too. > > Stef > On Nov 15, 2010, at 11:18 PM, Davide Varvello wrote: > >> >> Hi! >> I've two news for this list: >> 1) It's actually available my screencast on Smalltalk, you can find it >> here: >> http://thinkcode.tv/catalog/introduction-to-smalltalk/ >> 2) But you can have it for free if you look carefully at my timeline on >> twitter at @Varvello or at @ThinkCodeTV >> >> Enjoy the show. >> Davide >> -- >> View this message in context: >> http://forum.world.st/ANN-Smalltalk-Screencast-tp3043919p3043919.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > > -- View this message in context: http://forum.world.st/ANN-Smalltalk-Screencast-tp3043919p3049624.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 18, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by Igor Stasenko

As an option, we could rely mails to a mail bot, which will format a message more nicely, by changing the topic and removing other stuff, and then resend it to mailing list. Or ask google staff to gives the way how we can customize it. -- Best regards, Igor Stasenko AKA sig.

Nov. 18, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by Igor Stasenko

On 18 November 2010 22:38, Stephan Eggermont <stephan(a)stack.nl> wrote: > Stef wrote in reply to: >>On Nov 18, 2010, at 5:53 PM, Stephan Eggermont wrote: >>>That doesn't help with the web interface; >>?? > As I said, I often browse > http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/ > >>>But you just get a bad summary from squeak-source I have to click on the link all the time. > But then you at least get to see the whole discussion instead of one line. > >> - Filtering doesn't work with digests; >>>I do not understand > > The mailing list has a digest function. Most email clients do not know how to > filter them. > >> - The subject is not good and the content is not good for a mailing list; >>>Why >>>Bugs are our concerns > > I fully agree that bugs are our concern, and that it is important to make > activity visible. I also understand and share your frustration that bug > reports are badly read and written. I just think that this works contra-productive. > - the subject of a feed message is bad: it is just the issue number > and the issue title, instead of adding what happened with the issue. > - the content of a feed message is bad: the context is missing. > i think its because you turned it on just recently. For new issues, all messages will probably be gathered into a single thread by mailing client, so by opening it, everyone could be able to read a whole issue from very starting, without a need to visit an issue tracker. (btw, to test that, create a new issue) >> - It reduces the searchability/usability of the mailing list archives; >>>Why? >>>I want to look for bug discussions there too and not using a bad google search engine. > > I think the problem most potential contributors have is one of too much information, > not too little. Giving them more, in a badly prepared format, is unlikely to help. > > Stephan > -- Best regards, Igor Stasenko AKA sig.

Nov. 18, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by Adrian Lienhard

Yes, please keep it! (And mails with code diffs would be great too...) Adrian On Nov 18, 2010, at 18:33 , StÃ©phane Ducasse wrote: > +1 > > Sorry guys this is not optimal but after been against when I see it in squeak, I'm in favor because it > helps understanding what is happening. > > Sorry to be blunt but > ****YOU**** yes you guys do not look at the bug or bug fixes in general. > > So often ME myself and I, have to send email about point from the archive to the mailing-list. > Often I do not even see that a bug has been posted and YES I have 5 rss feed and I read them all. > > What is the last time you read the bug archives to see what is happening there? > So if you do not read the archive then how can you help? how can we make sure that people are aware? > > What is the last time you look at the code of the fixes that got integrated? Because if you do not read > it how can we do quality control? So if I could I would send the diff of all the package in the mailing-lits as this is done in squeak. > > Now what we can do to please some of you so far 4, we could create a mailing-list where such mails would be sent. > But let us see so far who is really against. > > Stef > > >> Remember that most email client support filters. You can easily create one. >> >> Cheers >> >> Mariano >

Nov. 18, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by Stephan Eggermont

Stef wrote in reply to: >On Nov 18, 2010, at 5:53 PM, Stephan Eggermont wrote: >>That doesn't help with the web interface; >?? As I said, I often browse http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/ >>But you just get a bad summary from squeak-source I have to click on the link all the time. But then you at least get to see the whole discussion instead of one line. > - Filtering doesn't work with digests; >>I do not understand The mailing list has a digest function. Most email clients do not know how to filter them. > - The subject is not good and the content is not good for a mailing list; >>Why >>Bugs are our concerns I fully agree that bugs are our concern, and that it is important to make activity visible. I also understand and share your frustration that bug reports are badly read and written. I just think that this works contra-productive. - the subject of a feed message is bad: it is just the issue number and the issue title, instead of adding what happened with the issue. - the content of a feed message is bad: the context is missing. > - It reduces the searchability/usability of the mailing list archives; >>Why? >>I want to look for bug discussions there too and not using a bad google search engine. I think the problem most potential contributors have is one of too much information, not too little. Giving them more, in a badly prepared format, is unlikely to help. Stephan

Nov. 18, 2010