2013/10/15 Marcus Denker <marcus.denker@inria.fr>:

On Oct 15, 2013, at 12:56 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:

...

On Oct 15, 2013, at 9:43 AM, kilon <thekilon@yahoo.co.uk> wrote:

...

I really like the idea of roadmap. In an open source project people are free to work in anything they like , even bring new nice features of their design as long as they don't disturb the existing code.

But the same people, including me, or even mere users , wonder where the software is heading. Even an exploration ship , that sets to explore new areas has goals. I would like to see in the pharo website a roadmap not just for 3 but even for pharo 4. I know that Stephane has given a presentation about pharo 3 roadmap , maybe you could link those slides.

the problem with this is that we do not have a clear roadmap for Pharo4 (yet). How it works now is: at the beginning of a year iteration we make a list of what we want, taking into account what emerged latest year (both new possibilities opened and new/old problems that emerged).

That gives us what we can more or less call a "next release road map". And is "more or less" because situation can change. For example we wanted a complete revamp of Pharo3 L&F, and we wanted also a complete migration of Morph to be rendered with Athens, and reality showed that is not achievable this year... so it will wait until next one (and that does not means at all that we stopped work on that area, just that the completion of the task will take more time than expected). So... what's the roadmap for Pharo4? No Idea :) What we already know is that we made a huge move forward in infrastructure for Pharo3 (starting by Opal, but not restrained to that), and now we want to focus in the tools (but without doing *just* that, because there are lots of tasks to do in kernel, modularization, cleanups, etc.)

in general, for pharo there is a vision document that shows the long (really long) term goals. Now I do not remember where is it, but should be somewhere in the pharo site (probably not visible enough).

The problem is that I think we already did a lot of that vision. We need a new one.

I wish all our problems were like this one :-) -- Pavel

...

the problem with this is that we do not have a clear roadmap for Pharo4 (yet). How it works now is: at the beginning of a year iteration we make a list of what we want, taking into account what emerged latest year (both new possibilities opened and new/old problems that emerged).

That gives us what we can more or less call a "next release road map". And is "more or less" because situation can change. For example we wanted a complete revamp of Pharo3 L&F, and we wanted also a complete migration of Morph to be rendered with Athens, and reality showed that is not achievable this year... so it will wait until next one (and that does not means at all that we stopped work on that area, just that the completion of the task will take more time than expected). So... what's the roadmap for Pharo4? No Idea :) What we already know is that we made a huge move forward in infrastructure for Pharo3 (starting by Opal, but not restrained to that), and now we want to focus in the tools (but without doing *just* that, because there are lots of tasks to do in kernel, modularization, cleanups, etc.)

in general, for pharo there is a vision document that shows the long (really long) term goals. Now I do not remember where is it, but should be somewhere in the pharo site (probably not visible enough).

The problem is that I think we already did a lot of that vision. We need a new one.

I will update it :) And I want a bootstrap and mini core and ….

On Oct 16, 2013, at 4:32 AM, btc@openinworld.com wrote:

...

Stef,

A few weeks back I had occasion to review the Pharo Vision document again. In the process of adding an additional Use-Case, I ended up marking lots of small editorial improvements throughout the document. My focus was not on eliminating grammar mistakes by non-native-english authors (it was pretty good) - but more on trying to find the 'best' way to phrase something. Eliminating the sort of things that creep into my own writing until the third or fourth review, along the lines of that saying about the writing process... "The job is not done until there is nothing left to remove"

cheers -ben <pharovision-btc-markup-2013-09-11.pdf>

very nice! Thanks! I will make a pass to integrate your suggestions. Marcus

thanks I will have a look :) Stef On Oct 16, 2013, at 4:31 AM, btc@openInWorld.com wrote:

Stéphane Ducasse wrote:

...

...

...

the problem with this is that we do not have a clear roadmap for Pharo4 (yet). How it works now is: at the beginning of a year iteration we make a list of what we want, taking into account what emerged latest year (both new possibilities opened and new/old problems that emerged).

That gives us what we can more or less call a "next release road map". And is "more or less" because situation can change. For example we wanted a complete revamp of Pharo3 L&F, and we wanted also a complete migration of Morph to be rendered with Athens, and reality showed that is not achievable this year... so it will wait until next one (and that does not means at all that we stopped work on that area, just that the completion of the task will take more time than expected). So... what's the roadmap for Pharo4? No Idea :) What we already know is that we made a huge move forward in infrastructure for Pharo3 (starting by Opal, but not restrained to that), and now we want to focus in the tools (but without doing *just* that, because there are lots of tasks to do in kernel, modularization, cleanups, etc.)

in general, for pharo there is a vision document that shows the long (really long) term goals. Now I do not remember where is it, but should be somewhere in the pharo site (probably not visible enough).

The problem is that I think we already did a lot of that vision. We need a new one.

I will update it :) And I want a bootstrap and mini core and ….

...

Stef,

A few weeks back I had occasion to review the Pharo Vision document again. In the process of adding an additional Use-Case, I ended up marking lots of small editorial improvements throughout the document. My focus was not on eliminating grammar mistakes by non-native-english authors (it was pretty good) - but more on trying to find the 'best' way to phrase something. Eliminating the sort of things that creep into my own writing until the third or fourth review, along the lines of that saying about the writing process... "The job is not done until there is nothing left to remove"

cheers -ben <pharovision-btc-markup-2013-09-11.pdf>

Stéphane Ducasse wrote

On Oct 15, 2013, at 9:43 AM, kilon <

thekilon@.co

> wrote:

did you read the vision paper that I wrote one year ago? Because this is not like if I did not spent 3 weeks writing it. It is not perfect and a bit too much infrastructure-orieneted but it is there.

no I have not but I would like to. Is it linked in the pharo website cause I cant find it . -- View this message in context: http://forum.world.st/Is-there-a-Roadmap-for-Pharo-3-0-and-Pharo-4-0-tp47144... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.