thanks ron.
For us keeping the things simple and working is the best.
We just mentioned to janko that using the money that GOSC send 500Euros to pay
other Smalltalk projects at the same
time than GSOC projects is not automatically efficient.
This is not that we want to keep the money for ESUG.
Why?
- students get the money but not the GSOC fame for their CV
- usually it is rare that we got so many good guys. Now if the guys are
good I would really do it.
but from what I understood some mentors were not happy last year (igor,
guillermo and me were not happy with the work done).
Of course it can happen but it is difficult to choose so I would prefer
that as a community we trust each other (and do not get polluted
by this project is in Pharo. Usually I try to attract the best students
of the lectures. Alex is doing the same and Noury too.
So this year Ronie, Leo, Max, Vincent (if he applies) are all excellent
students we saw in action and that ranked 1st or second in their
lectures.
- finally we should pay attention because there is an overhead (now we
fill up all the information required by the google accounting system
Now each time ESUG sponsors something we always ask ourselves
- impact impact impact
- it can be because we keep a smart guy in the communitee and there is
a better chance that he will stay having fun with us
- it can be topics
- it can be lecture creation….
For example for the new lecture in Cameron, we invited Hayatou with my team
money. Then he learned Moose
then I gave him all my lectures and CD. Then he came as a student volunteer at
ESUG. Then ESUG sent him books.
When I went to give lectures at Prague, ESUG payed the flight and hotel.
Sometimes when my team has some money left
we pay to keep money for ESUG. And at Prague, I put them in contact with
Gemstone people for a lecture on databases.
And I presented Smalltalk success stories: GS, VW and Pharo ones.
Recently I gave all my lectures to a guy arriving to Delft and we will help him
trying to push a lecture there first using my team money.
So we (me and rmod team) pay real attention to pay ESUG attendance and paying
trips when we can.
Stef
> HI All,
>
> ESUG is not unknown. Community members know exactly what ESUG is. We don't
> seem to have trouble attracting participants and completing projects using
> the ESUG name for GSoC. There is so much cool stuff to do and it seems cool
> people to do the work. ESUG has been doing a terrific job supporting
> Smalltalk. Success matters.
>
> I would vote to not mess with success. The ESUG name should stay. Now if
> we had even more groups mentoring Smalltalk for GSoC that would be fine with
> me too. There is no reason to lose any.
>
> All the best,
>
> Ron Teitelbaum
>
>> -----Original Message-----
>> From: Pharo-dev [mailto:[email protected]] On Behalf Of
>> Pharo4Stef
>> Sent: Saturday, February 08, 2014 9:54 AM
>> To: Pharo Development List
>> Subject: Re: [Pharo-dev] for those not in the smalltalk-gsoc-mentors
> mailing-list
>> nor in esug
>>
>>
>>> 1. Creating separate powerful organisation that will move in one
> direction will
>> give good results in a longer time, but the beginning will be tuff.
>>
>> I do not think that we should do it. We were frustated in the past that we
> could
>> not participate then we participate and ESUG was nice to handle the
> billing part.
>> So I would let run it now that marcus and luc spent the time to iron
> everything.
>> Now it would be good that people stop to piss on us.
>>
>>
>>> 2. I wouldn't call it a "Pharo" organisation. e.g. Amber is cool too,
> no? In fact
>> it should be some group that want's to do rings for real and not just
> state that
>> they are writing a code in Smalltalk.
>>
>> indeed.
>> I propose that just to see how far Janko was going. I think that it would
> be a
>> stupid move.
>>
>> This is why we stopped organizing a Pharo specific conference this year.
> But on
>> the other hand this is too easy to say that ESUG is biaised. And this is
> not good
>> from an energy stand point.
>> But some people are better at ranting than doing.
>>
>>
>> Stef
>
>
>
