+1
No we also prefer to work on OUR tasks.
>> Someone needs to start fixing and improving. Why not, for example, you?
>
> I'm a Pharo user, not Pharo developer. Developer of Pharo itself, that
> is. I'm just using it as a tool to contribute on other fields like on
> the web.
>
> Therefore it is not to be expected to know Pharo internals enough to
> contribute directly, but I can report wishes, errors and help to someone
> more knowledgeable to fix them. And that's what I'm actually doing for
> improving Pharo reliability, ask Igor and Stef.
>
> About issue tracker: it is not a duty of us Pharo users to open and
> track issues there, IMHO. This is a tool for Pharo developers, so I
> propose that one of you "harvest" them from mailing lists and open
> issues. You know better how to open an issue than me. I can be then
> invited to describe the problem better and help with you solving it.
>
> And yes, this distinction between Pharo user and developer is necessary
> part of Pharo becoming more professional and business friendly.
>
> Best regards
> Janko
>
>>
>> Here is a link:
>>
>> http://code.google.com/p/pharo/issues/list
>>
>> It's much better than talking.
>>
>> Marcus
>>
>>
>> --
>> Marcus Denker -- http://marcusdenker.de
>>
>>
>>
>
> --
> Janko Mivšek
> Aida/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
>
