[Pharo-project] Really Important message (tm)

Germán Arduino garduino at gmail.com
Fri Apr 16 23:32:56 CEST 2010


hehe, I understood that a real letter is needed, and sent it yesterday :)

2010/4/16 Mariano Martinez Peck <marianopeck at gmail.com>:
> Be aware (Carla) you don't need to be a letter...it can be the letter
> signed, scanned and sent by email. For those who live far away from France
> it is easier and cheaper ;)
>
> Mariano
>
> ps: don't tell my wife I am here hahahah
>
> On Fri, Apr 16, 2010 at 10:08 AM, Stéphane Ducasse
> <stephane.ducasse at inria.fr> wrote:
>>
>> On Apr 16, 2010, at 12:02 AM, Germán Arduino wrote:
>>
>> > The letter is on the way.
>> >
>> > A first question, to help with unstable I should use it as it comes
>> > (with no added packages) or I can install somethings to make the
>> > environment more comfortable (as shout for example) ?
>>
>> the way you want but if you load packages you should pay attention that
>> you changes do not impact them by accident.
>> Ideally we would like to have metacello to manage core and the process
>> would be
>>
>>        - take latest core
>>        - update
>>                -> get Pharo with maintained Pharo package: sound
>>        ------------------------------------------------------- this phase
>> should be done for us on a server with a hudson cron like job
>>
>>        - you change
>>        - you publish changes
>>        --------------------------------------------------------
>>        we take the current unstable core + packages
>>        - integrate your changes
>>        -> produce new version of packages + new metacello configuration
>>
>> Now since loading code is too slow we have to pay attention and avoid to
>> frantically remove packages from the image
>> because they can desync too easily when we do system wide changes.
>>
>> So for simple things just take the latest unstable and publish changes
>>
>>
>>
>>
>> > Germán.
>> >
>> > 2010/4/15 Stéphane Ducasse <stephane.ducasse at inria.fr>:
>> >> Thanks!
>> >> As I said, 30 min are enough
>> >> Stef
>> >>
>> >> On Apr 15, 2010, at 9:25 PM, Germán Arduino wrote:
>> >>
>> >>> ok, my signed agreement is leaving today for France.
>> >>>
>> >>> I will try to start understanding how is the contribution process in
>> >>> Pharo and playing a bit with unstable.
>> >>>
>> >>> Unfortunately I've very little free time, but still, will try to help.
>> >>>
>> >>> Cheers.
>> >>>
>> >>>
>> >>> 2010/4/15 Stéphane Ducasse <stephane.ducasse at inria.fr>:
>> >>>> Hi guys
>> >>>>
>> >>>> Let me reiterate it:
>> >>>>
>> >>>>        - We need you!
>> >>>>        - 75 % of the issues on the bug tracker are simple.
>> >>>>        - BTW how did we learn stuff, by reading code and learning.
>> >>>> I'm not smart I'm just a tedious learner
>> >>>>        I can any opportunity to learn something new.
>> >>>>        - if you spend 30 min a week, YOU CAN get an IMPACT!
>> >>>>        - if pharo is important for you then 30 min in a good
>> >>>> investment
>> >>>>        - every single LITTLE bugs fixed and improvement is IMPORTANT
>> >>>>        - we do not want the final latest coolest superhyper cool and
>> >>>> hyper clever fixes!
>> >>>>        - we accept little improvement
>> >>>>        - in UNSTABLE we have the right to push not 100% finish code
>> >>>>
>> >>>> Now think what YOU can do for pharo. Because Yes YOU can
>> >>>>        - screencast
>> >>>>        - checking tests (yesterday I moved
>> >>>> CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah
>> >>>> hyper difficult
>> >>>>        - Class comments: look at the URI class comment
>> >>>>        - blogging
>> >>>>        - tweeting
>> >>>>
>> >>>>
>> >>>> We should slowly change our process so that Pharo continue to evolve
>> >>>> even if we disappear on the moon.
>> >>>>
>> >>>> Now I asked marcus to focus on the newcompiler and stop fixing little
>> >>>> bugs because we want to make progress on other fronts.
>> >>>>
>> >>>> We want newcompiler -  we want the newcompiler -  we want the
>> >>>> newcompiler and fixing it and fixing its interface.
>> >>>> We want Helvetia hooks -We want Helvetia hooks.
>> >>>> We want a new package object (but I do not find time to code argh).
>> >>>>
>> >>>> Stef
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> Pharo-project mailing list
>> >>>> Pharo-project at lists.gforge.inria.fr
>> >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> =================================================
>> >>> Germán S. Arduino  <gsa @ arsol.net>   Twitter: garduino
>> >>> Arduino Software & Web Hosting   http://www.arduinosoftware.com
>> >>> PasswordsPro  http://www.passwordspro.com
>> >>> =================================================
>> >>>
>> >>> _______________________________________________
>> >>> Pharo-project mailing list
>> >>> Pharo-project at lists.gforge.inria.fr
>> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> >>
>> >>
>> >> _______________________________________________
>> >> Pharo-project mailing list
>> >> Pharo-project at lists.gforge.inria.fr
>> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> >>
>> >
>> > _______________________________________________
>> > Pharo-project mailing list
>> > Pharo-project at lists.gforge.inria.fr
>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



-- 
=================================================
Germán S. Arduino  <gsa @ arsol.net>   Twitter: garduino
Arduino Software & Web Hosting   http://www.arduinosoftware.com
PasswordsPro  http://www.passwordspro.com
=================================================




More information about the Pharo-project mailing list