The truth on GSOC, ESUG and bad attitude

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
42 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: [Vm-dev] NB and assembly methods (WAS: a lot of non-constructive things I refuse to talk about :)

EstebanLM

On 11 Feb 2014, at 20:08, Eliot Miranda <[hidden email]> wrote:

Hi Igor,


On Tue, Feb 11, 2014 at 7:16 AM, Igor Stasenko <[hidden email]> wrote:

On 11 February 2014 10:56, Esteban Lorenzano <[hidden email]> wrote:
>
> PS. I am hacking on protobuf in Pharo 3.0 and noticed cool NB assembler in some places - are such methods creeping into base libraries now? What does that mean for other CPUs? Sorry, for changing subject - feel free to reply under different subject.

Hi Goran,

Yes… since NB and Athens, there are some methods in assembler spread around. Is my opinion that all assembler-containing methods should be refactored into a more comprensible unit (and that can be changed by another set of assembly instrucction when we achieve multiplatform-NB). Today they are all along Athens, and if we continue this path they will be all along Pharo soon. I would better modularise that.
But Igor maybe has something different to say :)

Esteban

not much to add to what i already been said:
 - have any other CPU which can run pharo JIT? No? Will talk when it will be available.

There's an unfortunate chicken-and-egg problem here.  The way we develop a new platform with Cog is to build a simulator for the CPU and run the VM simulator above the CPU simulator.  But, by making Pharo non-portable because NB only works on x86 you've made it extremely difficult to use a Pharo image to develop the new platform.  That will be really important when x86-64 comes into the picture, which it shoudl sometime later this year.  In fact its worse.  Because there is no simulator support for NB I can't even start up a Pharo image on the current simulator and that's directly affecting my ability to sup[port Clément in the Sista work.   Note that we already have an ARM simulator and unfortunately Pharo can't run on that simulator either.  Some way of making NB get out of the way except on x86 until it is portable would be much appreciated.

Eliot, I made NB optional in Pharo3… you should not have problems (from that side) to simulate the image. But I’m also willing to help in anything else that is needed. Just point me your problem and I will try to solve it :)

Esteban



Doing anything before that is just waste of time.

--
Best regards,
Igor Stasenko.



--
best,
Eliot

Reply | Threaded
Open this post in threaded view
|

Re: Unethical behaviour on GSoC 2010 (was The truth on GSOC, ESUG and bad attitude)

Ben Coman
In reply to this post by Janko Mivšek

Janko,

Thank you for sharing the details of your concern.  It is better to deal
with facts rather than hints and allusions, since the former is
something the defendant and community can respond to and the latter can
conjure the worst imagination and polarise both defendant and community.
I can understand your need for hinting since it can be difficult to call
out a leader in the community, and perhaps is why you've shouldered this
burden since 2010.  Unfortunately such burdens can sour our perspective
on matters. As a reasonably independent observer (in Australia doing
Smalltalk just 2 years by myself) looking at the facts you've presented,
this seems to me more to a difference of opinion and perspective than a
violation of ethics.  Certainly your perspective as a GSoC Admin will be
different from me observing from the outside, but I think that Stéphane
as a representative of ESUG has some right to specify parameters for a
project like GSoC running under their name.  It just would have been
better this was done more transparently/publicly, and also that the
project parameters are publicly defined up front before the project
begins, but then life doesn't always happen like the ideal - there
always ends up gray areas that were not previously considered.

I hope that having shared these details, even if community sentiment did
not go the way you assumed, there is some sense of a burden has lifted.  
I particularly appreciate that you've stepped back from the GSoC Admin
role you obviously care a lot about, to allow the project to proceed
with someone outside the conflict.  Personally I would be glad to see
you involved again at a later time, though some bridge building may be
needed.


Stef,

I hope that after some time, even though this was damaging to you, you
might consider there were some honorable intentions that drove Janko's
motivations over the last three years, even if these were poorly
communicated.


My kind regards to you both,
-ben


Janko Mivšek wrote:

> Time therefore to expose that sad story from GSoC 2010. So that the
> community can judge by themselves if my claims are insults or real.
>
> For the start, this was not a money matter but meddling into project
> selection process.
>
> Here is the story:
>
> On GSoC 2010 Gilad Bracha proposed a Newspeak/Smalltalk Import/Export
> Tool project idea [1]. After the idea was put on ideas list [2],
> Stéphane Ducasse ordered my co-admin to remove Gilad's idea from the
> list. Co-admin told that to me. I was shocked that someone can come to
> such an idea to remove something even in the idea phase from the GSoC.
> Of course I rejected such an order immediately.
>
> Even more, co-admin was at that time just starting the postgraduade
> study under the Mr.Ducasse mentorship. You can imagine how he felt, like
> between two fires. It is reasonable therefore to suspect that Mr.Duccase
> uses his power as a mentor over postgraduate student to try to achieve
> his goal.
>
> What was the motivation of Mr.Ducasse to made such a blatant act was not
> quite clear to me. And is also not important. Important is that such
> removal attempts are totally unacceptable. Only GSoC mentors have that
> right by reviewing and voting on the projects to be finally selected for
> stipendiums.
>
> In any case, this incident was a start of my thinking and working on
> GSoC to be as transparent, neutral and independent as possible.
>
> Best regards
> Janko
>
> [1] http://gsoc2010.esug.org/projects/newspeak-tool
> [2] http://gsoc2010.esug.org/ideas
>  


123