Daniel Vainsencher danielv@tx.technion.ac.il wrote: [SNIP]
So let me beg here instead: who is actually interested in doing partitioning work? Anyone? Is this just something that we care about more in the abstract than in practice, and nobody really wants it enough to do it? Are there other ways we should be thinking about this that would get more traction? (like, "how many bits of code can we package up and unload from the image?")
Well, what are our goals? seems to me like the partitioning work is not good for itself - it supports (or should support) use cases.
Some obvious kinds of use cases are:
- "I want to be able to strip my images of this part" (MorphicSplitters)
- "I want to be able to swap in an alternative implementation"
(ToolBuilder) 3. "I want to develop/maintain this outside the image" (Celeste, when I started doing it)
And IMHO:
4. "I want to have the image staked out with maintainers assigned so that we have 'owners' of the code."
This #4 doesn't imply 1, 2 or 3. It is useful all on its own.
[SNIP]
What usecases (from either of the lists above or otherwise), do people on this list want to work on?
I will get back to you on that one. No time at this minute. :)
Daniel
regards, Göran