The reason why I dont contribute to Pharo and decided to create my own
project because frankly I cannot risk my code get rejected or debated upon.
I know I am new to Pharo and I am not experienced coder in any way but
still my free time is super valuable to me. I had made one contribution to
Pharo and it met some fierce resistance and I had zero problem with that.
My fix was accepted. I know people have their own preferences and
ideologies when it comes to coding like all things in life and I think its
100% to reject my code or request an improvement.  Frankly I am also afraid
of braking things and making other people life miserably.

But rejections and debates cost me valuable time. Sure if i was paid I
would have zero problem.

I mention this because I hear again and again, why people do not
contribute. This is my reason.

On Mon, Nov 10, 2014 at 5:36 PM, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote:

> I didn’t tell anything about Alain investing into Rubric. It’s just that
> Rubric is in GTInspector which I use, and I miss cmd+click feature. I think
> I could help to work on txText, but I’ve already broken quite a lot of
> things in Smalllint, so I’ll continue improving that part :)
>
> Uko
>
>
> > On 10 Nov 2014, at 11:17, stepharo <steph...@free.fr> wrote:
> >
> > Guys
> >
> > I just discussed with Alain who is at my place working with Igor.
> > Alain will not invest in Rubric. Rubric is the past. I told him to send
> a mail but he told me that he already said it.
> > We should push txText. I will spend some time with igor to push it again
> but we need more people to have a look
> > and help.
> >
> > Stef
> >
> > On 9/11/14 18:12, Yuriy Tymchuk wrote:
> >> Dear all.
> >>
> >> I’ve already reported this issue but didn’t make it clear.
> >>
> >> When I cmd+click some text in nautilus, I can “browse” it. This means
> browse class implementation, browse method implementors. When I cmd+click
> something in rubric it opens a context menu.
> >>
> >> I anybody using cmd+click besides of me?
> >> Can this be solved?
> >>
> >> Uko
> >>
> >
> >
>
>
>

Reply via email to