Model statuses

[Pete Vander Giessen]

> - would you find it helpful to have common* statuses?
> - or, would you find it more helpful to have statuses unique to each
entity type?

I'm still very much a beginner when it comes to developing charms, but from
my perspective, it would be most useful to have common statuses, so that
knowledge gained while working with one entity could be applied to others.

Of course, there's a trap: "destroying" might end up meaning very different
things for different entities, depending on how they get torn down, what
remnants they leave, and what tools can be applied to them when they, say,
get stuck and hang while being destroyed.

I think that I'd still prefer simplicity, even if I occasionally bump my
shins on the sharp edges that the simplicity masks. Others with more
knowledge of the system internals might have different opinions, though :-)

~ PeteVG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160413/0af1a630/attachment.html>