Hi!
On 04/23/2012 03:40 PM, Stéphane Ducasse wrote:
Just cloning it off into Pharo and forking seems... less optimal. Any ideas or
thoughts?
I do not get what you mean. I just want to work on our roadmap and make it
getting real.
It is hard enough to get some momentum and to deliver for real.
So can you help us to get focused?
People can do what they want. I wrote a vision document. We have a roadmap
and we will do it.
Ok, let me clarify. I was just wondering how the Pharo community wants
to handle a case where a substantial component (in this case, this new
editor) is not *primarily* developed in Pharo (in this case Cuis).
The simple route is to just copy and fork. But IMHO this doesn't
leverage the team already around this editor, right? We (Pharo) can't
just go around and forking everything and maintaining everything for
ourselves, right?
I just got interested in that problem - now, later replies indicated
that it would still need a substantial rewrite for Pharo, so perhaps the
situation I am describing is not really applicable in this case.
regards, Göran
