Thinking again about this idea of voting system for features we would like to see in Pharo. ��

I won't pay 10 euros / month for someone to develop full time on Pharo on what I do not control (may not be the best words to explain my feelings :)

But I'm ready to give 30 to 50 euros to raise money to develop the most wanted feature from a voting system. This give more visibility.

It's easier to make a one shot donation than give XXeuros/month.

So one way to achieve this is to set up a voting system AND associated raising money system to develop the most wanted feature for one month.

Another way is to pick the most wanted feature for Google Summer of code.��

With enough money one can stop his work for one month and develop exclusively for Pharo. If it's too hard to raise money for one month, we can try 15 days. I've seen that some great developers can do fantastic stuff in 15 days when he loves it :)

Laurent Laffont

On Fri, Dec 10, 2010 at 3:29 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 10 December 2010 13:32, Davorin Rusevljan
<davorin.rusevljan@gmail.com> wrote:
> On Fri, Dec 10, 2010 at 1:06 PM, Alan Rodas <alanrodas@gmail.com> wrote:
>> I'm relatively new to Pharo, maybe this has been tried before, but what
>> about a forum where the ideas are published.
>> Each idea could be a thread in the forum, and the people that would like to
>> contribute may comment there. What it may be��interesting��is that the whole
>> discussion about an idea could live in the thread, and you can keep track of
>> old discussions and the state of a feature.
>> If you keep your ideas for yourself, and you cannot implement something by
>> your own, that idea will die there. If you allow people to comment on ideas,
>> maybe two or more people have the same, and they can start working on
>> it��together. A forum allows for��contacting��people, and sharing, and, in that
>> way, maybe the community will grow (Some��developers feel they can do
>> something��because��they don't have the time to do it by their own, or they
>> don't have the skills, but they can help to a dev team that share the same
>> goals.)
>>
>>
>> Is just a thought.
>> If you did it before and didn't work, my apologies.
>
> Well, those are all nice thoughts. I am also relatively new to Pharo
> though, I am with Smalltalk for quite a long time. In my humble
> opinion, while both are always nice to have, at this stage Pharo, much
> needs more hands willing to do the work, than hands filling the wish
> lists and voting about them.

Abso-freakin-lutely! :)

>
> The Pharo team did marvelous job, I assume with a lot of investment of
> their personal time and energy. They also did quite good job at
> setting their targets since they already managed at transforming huge
> but sometimes hectic Squeak core into consistent development product.
>
> The way things currently work nicely reflect this, you can freely
> float your ideas on the mailing list, but do not expect that someone
> else should do it just because of that. But the better the idea is,
> and the larger your contribution to Pharo is, chances of it being
> implemented will rise. Otherwise, roll up your sleeves, and do it for
> yourself. If that is too complicated, consider doing something else
> simpler but usefull.
>

I am always discussing ideas before going to implement them.
And for things i do, if i not sure if i doing the best way, or there
are multiple 'nice'
ways to solve the problem, i asking people, what they prefer.
In that way people staying in course of what i do, and sometimes could
give an advice or help by
other means.
But i don't expecting much, because we all busy with own agendas.

> rush
> http://www.cloud208.com/


--
Best regards,
Igor Stasenko AKA sig.