Morphic: doing something (was Incorporating changes)

Jerome Peace peace_the_dreamer at yahoo.com
Mon Oct 9 02:15:37 UTC 2006


Morphic: doing something

Edgar wrote:


>You know me, I was on the first team and on the
second.
>And you know could work together.
>Maybe it's time to start to do something?

The time to start doing something is when there is a
clear something to do.

The morphic roadblock right now is maintaining it with
MC.

Or rather maintaining with changesets and getting them
into mc to be acceptable to the powers that harvest.

Morphic is a tangle. A big tangle. MC does not work
well or fast with big. It does not work well with
detangling. 

Changesets work well with anything inside the image.
They do not work well with MC packages.
(Largely because changesets reorganize catagories at
the drop of a hat and know that catagories are not
critical. ) MC knows that catagories names are
critical and demands that they be maintained
scrupulously.

My path to solving has these goals.

1) MC and changesets (actually all fileouts) must
interoperate in a friendly manner.

2) Morphic must be broken up in to right sized
packages along lines that make sense.

3) Once detangled Morphic must be simplified and
repaired.

The three goals will help each other.

They can also be worked on separate from each other.

My plan of action is to solve these problems with
elegance and patience.

For right now:

!) I await MC2.  Study changesets to satisfy my
curiosity and suggest repairs.

2) I wait for resources and help to come forward. I
try to identify leaf classes and see if they can be
peeled off of the bulk package.

3) I post mantis reports (clearly described
complaints) Add to them with analysis. And when
possible provide fixes in the form of changesets.

Part (3) is the one I have the most fun with so and
which gets most of my time. Also I come upon part (3)
tasks as I persue the loog range morphic enhancements
I seek. (Such as the thread of puzzle enhancements to
polygon sparked by your posts. :-)

For the morphic package to progress the team must find
a MC maven willing to take a batch of fixes and
wrestle them into a MC package acceptable to the
release-team/harvesters.

The other task of importance is communication but that
deserves its own post.

I look forward to the reply this post generates. 

And Edgar, thanks for keeping it fun.


Yours in service, -- Jerome Peace

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



More information about the Squeak-dev mailing list