My experience is that the images on the site probably are not "stable" as-is, but that means the process needs to be fixed rather than killing off useful products - sending people off on their own will not help anything in itself. We also need to put some obstacles in the way of inclusion in Pharo; the latter will have pros and cons, but I suspect it will eventually be necessary for us to have a quality product. Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Tuesday, January 05, 2010 12:01 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] What about killing PharoWeb images? As an example...today I was in a Stef lesson at the Ecole de Mines. They have to do a TP with Pharo, and it was really sad to see Stef asking me in the middle of the class if the dev image from the website was usable or not. Image the students thoughts. I had to put the last image I had "stable" and put it in a USB key and give it to the students. On Tue, Jan 5, 2010 at 5:58 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote: On Tue, Jan 5, 2010 at 5:48 PM, Geert Claes <geert.wl.claes@gmail.com<mailto:geert.wl.claes@gmail.com>> wrote: Mariano Martinez Peck wrote:
Because of all the things I already have said: why to duplicate efforts? In that case, you the Seaside one click. What cab be easier than that ? And it would be FAR more stable than ours. Do we create PharoGlassClient image ? no. Do we create PharoMoos image? no. Because it is obvious that they know better than us what versions to include. Of course, if Seaside ready images doesn't exist we will probably do it. Give me only one reason why spending time and resources in PharoWeb? (taking into account you have other several alternatives better than this)
I don't see it as duplicating efforts, the Pharo-Web image is (should be) more than Pharo-Seaside and having this sandpit image will probably give a lot more feedback than just having a Pharo-Dev image ... in my view. Ok, fortunately, we live in a free world :) Everybody can think whatever. And that's cool. Mariano Martinez Peck wrote:
There is no such thing of "Pharo team". Pharo team are us. You. The community. Pharo has NO employee. There is the board but doesn't mean they are working full time in Pharo.
Settle down mate ... anyway, the Pharo Team is doing great stuff :) Yes, no problem :) But this is not something small to say. For me this is very important. For example, do you know who use to do the dev images since the last 2 or even more years ? Damien. Unfortunately Damien is very complicated with his studies (in Java) and has very little (or almost nothing) to prepare the images. So, it is easy to pretend. But who will do the images right now ? You will ? Anyway, I am glad to hear all the opinions. So...instead of building bad images, unstable and that gives a bad impression to the final user I proposed a simple solution for this. Maybe it is not the best. But this what we have. I even think I would do what I said having good images (but forget this). Damien also use to integrate stuff on OB and O2 for example before release. Who will do that now ? I don't know. That's why I am since 2 weeks writing Metacello configurations for all packages and that's why I asked Damien if he could send me his scrips and instructions of how to build those images. Kind regards, Mariano -- View this message in context: http://n2.nabble.com/What-about-killing-PharoWeb-images-tp4249050p4256091.ht... Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project