I will be on vacation next week.
You can expect more designs the week following. (There are a few
Please feel free to send replies to the design emails, including the
design for the new download page (and proposed all-in-one delivery
method). I'll read and respond when I return.
-----BEGIN PGP SIGNED MESSAGE-----
Anyone know what might happen if we subscribe the project mailing
lists to arch@?
I know the "try to avoid duplicates" is set in Mailman. Will that cover?
For example, when I send an email to two lists.ovirt.org mailing lists
I'm on, I get two copies. But I haven't tried having a mailing list
subscribed to another to see how it would work.
The deal is, we must have one generic all-project mailing list. When
we see there are more people subscribed to engine-devel@ than arch@,
what should we think & do? Leave them alone in their corner?
Part of the deal of being a project in oVirt is that your project must
integrate with the whole:
"Each project must agree to support the oVirt complete stack (CS)
"Each project must agree to provide or integrate with one of the
How can we be integrated if we don't have all project people on one
central mailing list?
On the other hand, everyone on engine-devel@ doesn't have to know
about the cross-project materials relevant to arch@ if they don't want
to - I respect that right. But that requires other people on
engine-devel@ to pass along *all* key information. Is that fair?
Until then, the only way to know we have hit all relevant people is to
send multiple-addressed emails, which creates duplicates. Maybe
subbing lists would fix that, but it means people would be in the
arch@ content flow without necessarily wanting it. The project
requirement to integrate to the whole isn't a personal requirement,
- - Karsten
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org .^\ http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
I am working on a project to make the existing vdsm hooks more accessible and available.
So in very short, for those who do not know, a vdsm hook is a script that can be placed on ovirt hosts, and which will do some custom actions, vdsm cannot do out of the box.
We have quite a few already in the repositories at http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=tree;f=vdsm_hooks;h=6f33db407... and the vdsm engineers are starting to turn these into proper RPMs and push them into fedora, and then EPEL repos, however, for these to be consumable, we also will need a description page for each hook, somewhere under ovirt.org/hooks or hooks.ovirt.org, where every hook can be downloaded, and have a description, version compatibility and a use case described.
If you use gnome-shell, it would be something like extensions.gnome.org, but of course, not quite the same, as we tend to a different kind of user.
I would like to find out what will be required to do this, as soon as possible
I'm trying to create a new user account for the oVirt wiki, and it fails, as I'm not an administrator in the oVirt wiki.
In the past I was able to create user accounts.
What should I do?