Dan,

I think the type of discussion and interest around BrandX is likely to
be orthogonal to that of Zones. Without completely spoiling the
surprise, BrandX hopes to publish interfaces where Zones could take on
personalities for RedHat, FreeBSD, AIX, Mac OS X or whatever. I imagine
much of the discussion may focus on the specifics of using those
interfaces and differences between the Zone personality and the real
deal. Those discussions seem very much distinct from the Zones community.

BrandX is also unlikely to be a code name any more than Zones, DTrace,
or FMA are code names. All those names are reflected in the interfaces
and commands associated with those project and BrandX will be no different.

Further, having branded-zones-discuss really obscures what I think will
be a hot community and one in which we've already seen tremendous interest.

Adam

On Sun, Nov 06, 2005 at 11:54:03PM -0800, Dan Price wrote:
> Nils-- I'm wondering if we are too closely mirroring the details
> of Sun's internal organizational hierarchy with our selection of
> communities.  And I think that 'BrandX' is going to feel confusing
> to folks 24 months down the line, when the memory of that code name
> is hazy, don't you?
> 
> Might 'branded-zones' be a logical part of the zones community?
> I'm concerned that for folks casually browsing, things may otherwise
> become confusing.  We can obviously refactor the zones community site as
> needed in cooperation with you and your team.
> 
> As a side note, a single community can support multiple mailing lists,
> so there would be no problem with having branded-zones-discuss as an
> alias.  Thoughts?
> 
>         -dp
> 
> -- 
> Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - 
> blogs.sun.com/dp
> _______________________________________________
> opensolaris-discuss mailing list
> [email protected]

-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to