mandrew wrote:

What do you mean by an organization's Jazz policy? Do you mean the
process it is using? What type of information do you expect to be
exported and imported?

I have to admit my thoughts are not fully formed on this but I'll try to
clarify.

Broadly speaking what I mean by Jazz policy is the complete set of
customizations applied after the server came "out of the box". In other
words, imagine that I download and set up a Jazz server, create some
users, project areas, etc, and eventually the pilot project is deemed a
success. Is it then possible to export the experience acquired, in the
form of XML presumably, and hand it out to other groups within the same
organization as a good starting place, or would they have to point and
click their way to something similar?

It's not at all clear to me whether this would be better in bits and
pieces, e.g. a document containing user definitions, another with
project area, etc., or as one large XML schema. As noted, I'm kind of
thinking out loud here.

What originally brought this to mind was wondering about how Jazz uses
Jazz. You are (presumably) the largest successful deployment to date,
and your project is committed to doing its work in an open fashion. A
number of the tutorials, blog entries, webinars, etc are based on your
own internal configuration, and it's possible to see little bits of it
in detail in screenshots, but not enough to build on. I was thinking
about whether some of your setup might be available as importable XML
files, not necessarily to use as-is but to compare against, and that
lead to the baseline question above.

Thanks,
DSB