Sorry that it took so long to answer, but I was quiet busy with real life.
Mike Auty wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Tiziano Müller wrote:
> | Hi everyone
> | What do you think of creating a new 'virtualization' project or
> | herd/team?
> Sounds like a good idea, there seem to be enough packages to warrant it.
> ~ Especially if you're finding shared packages and space for integration
> of components.
> | So, what do you think?
> As one of the primary vmware devs, I'm not sure that vmware easily fits
> into this group based on it's closed-source nature, and the complex (but
> just about workable) module system we've put in place. I also wouldn't
> want to muddy the virtualization email address with all the random
> vmware module bugs... 5
> I'm pretty happy for the vmware group to go under the virtualization
> herd, but I'd very much like to maintain the vmware email
> alias/assignment for bugs, and I'm not sure how much we'd be able to
> integrate with the larger group. Do you think it's worthwhile vmware
> joining the umbrella or should we just stay separate?
That's true. How about having a virtualization project which takes care of
the common part, the docs and the coordination (if any) and have separate
herds for larger "subprojects"?
email@example.com mailing list