WhatsUp from: 2013-03-11 until: 2013-03-24

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts.  Just answer informally, and feel free to spawn discussions thereafter!

### Here's what I've been up to since the last WhatsUp:

- $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS

### What's next, until 2013-03-24 (*):

- $NEXT_STEPS_TOWARDS_WORLD_DOMINATION

(*) we'll be expecting results by then ;)

On Mar 12, 2013, at 4:08 PM, [hidden email] wrote:

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts.  Just answer informally, and feel free to spawn discussions thereafter!
>
> ### Here's what I've been up to since the last WhatsUp:

- Working on Pharo 2.0 release (a lot)
- VM stuff (merges, catch bugs, jenkins)
- A couple of passes on consortium site.

>
> ### What's next, until 2013-03-24 (*):

- Release Pharo 2.0
- Build 1.4 winter (we need to incorporate one critical bugfix to 1.4 and new VMs)
- Review 2.0 (Retrospective meeting, etc.)
- Plan and start Pharo 3.0
- More VM stuff
- Update of association site (no, it will not look good now, it will still suck until we get a real designer, but it will incorporate some adjustments I made for consortium site)
        (and this could be postponed, too)

Esteban

On Mar 12, 2013, at 4:08 PM, [hidden email] wrote:

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts.  Just answer informally, and feel free to spawn discussions thereafter!
>
> ### Here's what I've been up to since the last WhatsUp:
>
> - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS

        - working with Damien Cassou on the pier extensions:
                missing figures but else the html is
        - migrating XMLParser
        - migrating XMLWriter
        - migrating Soup
        - migrating other moosish collections
        - first release of the ZeroConf chapter
        - migrating sound
        - Pharo 2.0 list of actions
        - producing issues for 3.0 :)
        - learn with igor on resources management and weakregistry bugs :)
       

> ### What's next, until 2013-03-24 (*):
>
> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION
>
> (*) we'll be expecting results by then ;)
       
        - Retrospective planning
        - Continue to migrate projects to Smalltalkhub
                game
                moose projects
                look for orphan squeaksource important project
        - Finish block chapter for the book
        - Add discussion about tests in default group the metacello chapter!
        - Prepare and plan 3.0 features introduction

Stef

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts.  Just answer informally, and feel free to spawn discussions thereafter!

Cool idea!

> ### Here's what I've been up to since the last WhatsUp:
>
> - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS

- Fixing many bugs in Roassal
- Writing the chapter on Roassal
- Working on the Loom thread profiler

> ### What's next, until 2013-03-24 (*):
>
> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION

- Reviewing the ZeroConf chapter
- Working on the Rizel profiler

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

This is fun :) I'm getting an even stronger sense of how much we've accomplished!!

seaside wrote

### Here's what I've been up to since the last WhatsUp:

- Participated in 109 2.0 issues, 85 of which got integrated
- Small infrastructure improvements e.g. updating website links, Jenkins descriptions/configs
- Testing Spec, Nautilus, and FileSystem; providing feedback (or harassing Ben and Cami, if you prefer ;-P)
- Updated some community Metacello configurations
- Some work on Metacello; learning the git workflow, updated the bootstrap
- Integrated all remaining COTDC class comments
- Proof-of-concept at ESUG to enhance FileTree/Cypress for VW <-> Pharo porting, automatically converting between prefixes and namespaces; Cami and I were able to load the newest version of Xstreams from VW, and then commit it again in a cross platform format that could (I think, not tested) be loaded in VW
- Smalltalk PR in NYC programming circles; attended quite a few meetups and talked up Pharo
- Test 2.0 by working in it day to day on my personal projects

seaside wrote

### What's next, until 2013-03-24 (*):

- Resume work on Vim key bindings; hopefully after new text model is integrated...
- Package and release some useful IDE improvements
- Reinvented BDD: I've been working on this for about a year, like rspec but with a live model of real objects, not class based like rspec and SUnit

On 12 March 2013 16:08,  <[hidden email]> wrote:
> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts.  Just answer informally, and feel free to spawn discussions thereafter!
>
> ### Here's what I've been up to since the last WhatsUp:
>
It is hard to remember.. but i will try:

- working on VM builds, making things run.. crashing and run again
- working on NB & FFI
- working on Athens , M4te, NBOpenGL and other cool stuff

> ### What's next, until 2013-03-24 (*):
>

- to dominate world, i want to update configuration of NBOpenGL, so it
can work fine with updated version of NativeBoost, found in Pharo 2.0

- same applies to Athens, because its configuration also needs to be
updated and some testing

- a small yet important project NBFpu, to test and learn NB and Jit
coexistance and see how we can squeeze even more performance from our
code. The outcome is more documentation how internally jit works as
well as an open road for new FFI code generator which will use inline
JIT code for FFI calls instead of C primitive (primitiveNativeCall)

- i want to move all VMMaker sources to git repository, to no longer
deal with tons of configurations and making single commit containing
all necessary bits to build VM. But this can take a while


--
Best regards,
Igor Stasenko.

Alex

did you get a real look on the profiler of Andreas?
Did it help?
I would like to understand when it is really better?

Stef

On Mar 13, 2013, at 3:26 AM, Alexandre Bergel <[hidden email]> wrote: