On 23/11/10 12:45, Jan-Simon Möller wrote:
Am Dienstag, 23. November 2010, 13:42:51 schrieb David Greaves:
On 22/11/10 07:42, Carsten Munk wrote:
Could distribution engineers/architects elaborate on this topic and
set forth a policy?
At the same time, when policy is proposed could we consider (and provide) an
automatable test. (Which in this case seems quite hard)
Shouldn't be that hard: osc validator ? src_service ?
Yes; the trigger is not hard to apply. Having a rules engine able to verify
policy compliance is a little more tricky. We're expecting BOSS to call this at
the appropriate times during the workflow but there's no reason the logic can't
be applied at other points. We'd also like this to be a useful tool elsewhere in
the vendor community so we should be able to extend / override it with local
policy checks too.
I've made tongue-in-cheek suggestions that we should have a set of policy
paragraphs and each policy statement should have a corresponding check so the
automated system can politely point back to policy in the event of a reject.
That may be OTT but it's worth considering in principle.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
