This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=ISO-8859-1
On 08/24/2012 09:16 AM, Dave Neary wrote:
OK - suggestions, then:
According to your suggestions :) you should be posting this to just
I think we need to move this discussion there as it fits the scope of an
overall change that affects lots of things, not just an infrastructure
issue. Does that make sense?
users@ - User issues - help, troubleshooting, configuration issues,
sharing experiences, etc. Users@will have mostly technical users of
oVirt or people in the process of installing it, plus some of the oVirt=
developers (but we'd like to encourage our more technical users
answer questions). The list could also serve as a gateway drug to
contribution, and we should ask here for help for initiatives which do
not require intimate knowledge of the code base - VDSM hooks, wiki
editing, documentation drives, etc.
arch@ - rename to developers@ - This will be the key developer mailing
list for oVirt, the place where we discuss project-wide changes, the
roadmap for future versions, release planning, where people can perhaps=
propose patches for discussion, and where any issue affecting the
developer governance of the project will be discussed.
board@ - Issues related to the non-technical governance of the project
(ie things which require board approval). In the case of the website
redesign, for example, a final design, discussed beforehand on
developers@, would be submitted to board@ for approval.
infra@ - issues related to the management of oVirt infrastructure - web=
services, developer infrastructure, etc.
vdsm-devel, node-devel, engine-devel, *-devel: Low-traffic lists relate=
to the specific implementation issues of the individual components.
In this schema, if you want to talk to the developers, you email
developers@ - if you have a suggestion specific to vdsm, you might
contact developers@ or vdsm-devel@ - but not both. Any mailing list
thread to vdsm-devel@ which requires feedback from the maintainers of
other projects should move to developers@ once that's ascertained.
How does that sound?
On 08/22/2012 05:26 PM, Karsten 'quaid' Wade wrote:
> On 08/20/2012 12:19 PM, Dave Neary wrote:
>> The ironic solution to
>> that problem is to tighten the scope of all the lists, and cross-post=
>> the new proposed scope to them all :-)
> I'm happy with that. Once that proposed scope is agreed upon, then I
> guess people can suggest topics be moved to appropriate locations, whi=
> could help with some of the topics on engine-devel that
> on arch.
> - Karsten, not necessarily taking on the task of writing the list
> scopes ...
> Infra mailing list
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----