Re: [gentoo-dev] Re: About herds and their non-existant use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tiziano � wrote:
| Marius Mauch wrote:
| - only have one location where members of a given team are listed,
| currently it's possible and quite likely that herds.xml and the mail
| alias files get out of sync
| Well, we need one location where the name of the team is mapped to the
| actual mail-alias. But I don't get what you're trying to say...
While we're changing things around, perhaps we can then also standardize the
mail alias to
[EMAIL PROTECTED]
What Marius is saying though is that there are two files that handle people and
their
herds. One XML for saying who is in a herd and one for each herd mail alias on
woodpecker
with a list of developer email prefixes.
Marijn
- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
http://www.gentoo.org/proj/en/lisp/, #gentoo-{lisp,ml} on FreeNode
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkg2U5gACgkQp/VmCx0OL2wIVQCfVRE1/lP60+cspM6Zay5kyVwl
yUUAn1rBssAT2ndNpo55NLI3vzLrWdIN
=RMvL
-END PGP SIGNATURE-
--
gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: About herds and their non-existant use
Marijn Schouten (hkBst) wrote: While we're changing things around, perhaps we can then also standardize the mail alias to [EMAIL PROTECTED] What Marius is saying though is that there are two files that handle people and their herds. One XML for saying who is in a herd and one for each herd mail alias on woodpecker with a list of developer email prefixes. Which could be generated out of the XML file, right? -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: About herds and their non-existant use
On Fri, May 23, 2008 at 10:39 AM, Tiziano Müller [EMAIL PROTECTED] wrote: Marijn Schouten (hkBst) wrote: While we're changing things around, perhaps we can then also standardize the mail alias to [EMAIL PROTECTED] What Marius is saying though is that there are two files that handle people and their herds. One XML for saying who is in a herd and one for each herd mail alias on woodpecker with a list of developer email prefixes. Which could be generated out of the XML file, right? It could, but it would be nice to preserve a method for allowing lurkers on aliases. Regards, -- Santiago M. Mola Jabber ID: [EMAIL PROTECTED]
[gentoo-dev] lastrite: sys-cluster/{wulfstat,xmlsysd} (replaced by sys-cluster/wulfware)
# Samuli Suominen [EMAIL PROTECTED] (23 May 2008) # Replaced by sys-cluster/wulfware wrt bug #193635. # Unversioned and old tarballs, and an ebuild # altering /etc/services which is wrong. # Removed in ~60 days by treecleaners. sys-cluster/wulfstat sys-cluster/xmlsysd -- gentoo-dev@lists.gentoo.org mailing list
[gentoo-dev] Re: Re: About herds and their non-existant use
Santiago M. Mola wrote: On Fri, May 23, 2008 at 10:39 AM, Tiziano Müller [EMAIL PROTECTED] wrote: Marijn Schouten (hkBst) wrote: While we're changing things around, perhaps we can then also standardize the mail alias to [EMAIL PROTECTED] What Marius is saying though is that there are two files that handle people and their herds. One XML for saying who is in a herd and one for each herd mail alias on woodpecker with a list of developer email prefixes. Which could be generated out of the XML file, right? It could, but it would be nice to preserve a method for allowing lurkers on aliases. I'm sure something like this should be possible: ### AUTOGENERATED PART, DO NOT EDIT ### ... ### AUTOGENERATED END ### ### Add additional aliases here: ... -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: About herds and their non-existant use
On Thu, 22 May 2008 08:05:07 +0200 Tiziano Müller [EMAIL PROTECTED] wrote: While I think the herds concecpt is somewhat useless, I'd rather like to see something like this instead: maintainer teamfoobar/team /maintainer This makes it clear that it is a team instead of a person (where name would have been used) And the herds.xml isn't completely useless, but I'd rather name it teams.xml and list the teams there. This way we can validated the team mentioned in team.../team against the list of available teams and make sure the complete thing is valid (can be done in the current metadata.dtd or in a future metadata.xsd). (If we're gonna re-use the email.../email element for the herd-alias, we can never validate it. And I'm personally for the: if something can be automatically validated, it should be) Hmm, in that case maybe it's be possible to use a similar system for devs, e.g. maintainer devgenone/dev /maintainer and only use the email element for non-dev maintainers and upstream contacts. Anyway, as long as we use the same tag to list both individual and group maintainers it would be an improvement IMO. This would have a number of benefits: - you no longer have to look at herds.xml to determine the actual maintainers of a given package (as herd-name and associated mail alias don't always match) I don't consider this much of a problem. You just have to know xsl/xpath to cope with this as generating the list of mail-aliases to assign this bug to is a simple xsl-transformation... When we use XML we can also use the right tools to handle them, can't we? My point is that it's an unneccessary extra step Sometimes you only have the raw XML file. Anyway, that's maybe more of a policy problem, we just need to enforce 'name == mail alias' (or would that be such a horrible requirement?) - it would simplify bug assignment rules, as the current case where a package has both a herd and a maintainer tag in metadata.xml no longer exists It doesn't. You can still have more than one maintainer in there. We'd have to introduce an attribute to mark the primary maintainer. Relying on the order of maintainer elements doesn't work because ...? (Assign to first listed maintainer, CC others) - only have one location where members of a given team are listed, currently it's possible and quite likely that herds.xml and the mail alias files get out of sync Well, we need one location where the name of the team is mapped to the actual mail-alias. But I don't get what you're trying to say... Why do you need to separate the name from the alias? Sure, sometimes there are technical reasons why you can't use your preferred name as mail alias (when it matches a system account), but then you can just adjust your name a bit (e.g. adding some suffix). Don't know if you're aware of this, but the separation of herd names and aliases of the herd maintainers has always been something that bug-wranglers complained about. But my main issue is that currently we have multiple unconnected locations where teams are defined, some more and some less important: - herds.xml - project pages - mail aliases - cvs access groups - role definitions in ldap/roll-call So when someone wants to change his roles there are a lot of places to care about, and it's likely that one or more are forgotten and things get out of sync, so you have different views of who actually belongs to a group depending on what source you use. Don't know if it has improved in the last years, but it used to happen quite often that herds.xml was completely out of sync with reality simply because it didn't really affect anything (now that jeeves is using it it's probably become a bit better). Ideally we could list that information in just one authorative location, but that's not feasable for technical reasons, but if we can eliminate one source (or auto-generate it from another source) the problem is already reduced quite a bit. And herds.xml is IMO the most likely candidates for that, but there are of course also other ways to improve the situation. Marius -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: Re: About herds and their non-existant use
On Fri, 23 May 2008 14:07:41 +0200 Tiziano Müller [EMAIL PROTECTED] wrote: Santiago M. Mola wrote: On Fri, May 23, 2008 at 10:39 AM, Tiziano Müller [EMAIL PROTECTED] wrote: Marijn Schouten (hkBst) wrote: While we're changing things around, perhaps we can then also standardize the mail alias to [EMAIL PROTECTED] What Marius is saying though is that there are two files that handle people and their herds. One XML for saying who is in a herd and one for each herd mail alias on woodpecker with a list of developer email prefixes. Which could be generated out of the XML file, right? It could, but it would be nice to preserve a method for allowing lurkers on aliases. I'm sure something like this should be possible: ### AUTOGENERATED PART, DO NOT EDIT ### ... ### AUTOGENERATED END ### ### Add additional aliases here: ... When you want to generate mail aliases from an XML file I'm quite sure you could list lurkers in the XML file by tagging them somehow (attribute or different element name). The main thing is to have one authorative location. Marius -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: About herds and their non-existant use
On Fri, May 23, 2008 at 07:18:16AM +0200, Marijn Schouten (hkBst) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tiziano ??? wrote: | Marius Mauch wrote: | - only have one location where members of a given team are listed, | currently it's possible and quite likely that herds.xml and the mail | alias files get out of sync | Well, we need one location where the name of the team is mapped to the | actual mail-alias. But I don't get what you're trying to say... While we're changing things around, perhaps we can then also standardize the mail alias to [EMAIL PROTECTED] The sole reason that isn't possible is that some teams would have names that conflict with system accounts. While it's possible to override those in the Gentoo mail server setup, the system account versions DO receive a _LOT_ of spam because they are so common (eg mysql@, ldap@). -- Robin Hugh Johnson Gentoo Linux Developer Infra Guy E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpNDEFFumd9j.pgp Description: PGP signature
[gentoo-dev] Re: About herds and their non-existant use
Robin H. Johnson [EMAIL PROTECTED] writes: The sole reason that isn't possible is that some teams would have names that conflict with system accounts. While it's possible to override those in the Gentoo mail server setup, the system account versions DO receive a _LOT_ of spam because they are so common (eg mysql@, ldap@). What about standardising on a suffix too? [EMAIL PROTECTED] or [EMAIL PROTECTED] or [EMAIL PROTECTED] and then all the aliases following that [EMAIL PROTECTED] [EMAIL PROTECTED] and so on -- Diego Flameeyes Pettenò http://blog.flameeyes.eu/ -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: About herds and their non-existant use
Diego 'Flameeyes' Pettenò a écrit : Robin H. Johnson [EMAIL PROTECTED] writes: The sole reason that isn't possible is that some teams would have names that conflict with system accounts. While it's possible to override those in the Gentoo mail server setup, the system account versions DO receive a _LOT_ of spam because they are so common (eg mysql@, ldap@). What about standardising on a suffix too? [EMAIL PROTECTED] or [EMAIL PROTECTED] or [EMAIL PROTECTED] and then all the aliases following that [EMAIL PROTECTED] [EMAIL PROTECTED] and so on or [EMAIL PROTECTED] ? Rémi -- gentoo-dev@lists.gentoo.org mailing list
[gentoo-dev] [RFC] Eclass for gnome-python* split
Greetings All, I've been working on an ancient bug [1] requesting a split of the gnome-python, gnome-python-extras, and gnome-python-desktop ebuilds. The motivation behind the split is that packages that depend on a single module or a small set of modules from one of these packages end up pulling in the numerous dependencies required when pulling all the modules in the package (example -- nautilus gets pulled in because of a dep on the gnomeprint module). I have split these 3 packages into packages for the component modules. Since there was a lot of common functionality between these packages, and the 28 modules' ebuilds were basically very similar, I've split out a large amount of the required functionality into an eclass. The work is heavily based on Jim Ramsay's ([EMAIL PROTECTED]) work on splitting gnome-python-desktop. The split ebuilds are available via a git repository [2]. The actual eclass can be viewed online at: http://tinyurl.com/6z2ltc (full URL [3]) Feedback and comments (and even brickbats ;)) on the eclass are invited. [1] https://bugs.gentoo.org/show_bug.cgi?id=108479 [2] http://gitorious.org/projects/g-py-split/repos/mainline (branch is g-py-split) [3] http://gitorious.org/projects/g-py-split/repos/mainline/blobs/g-py-split/eclass/gnome-python-common.eclass Cheers! -- Arun Raghavan (http://nemesis.accosted.net) v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056 e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com -- gentoo-dev@lists.gentoo.org mailing list
