[gentoo-dev] Two herds (and four extra?)

[gentoo-dev] Two herds (and four extra?)

[Jeroen Roovers]

This is madness, people. Two herds and four separately mentioned
developers? Why don't you join a herd? Go on, it's fun and you don't
have to be alone!


     jer


gentoo-x86/sys-kernel/hardened-sources $ cat metadata.xml
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE pkgmetadata SYSTEM
"http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata>
        <herd>kernel</herd>
        <herd>hardened</herd>
        <maintainer>
                <email>quantumsummers@gentoo.org</email>
                <name>Matthew Summers</name>
        </maintainer>
        <maintainer>
                <email>robbat2@gentoo.org</email>
                <name>Robin H. Johnson</name>
        </maintainer>
        <maintainer>
                <email>chainsaw@gentoo.org</email>
                <name>Tony Vroon</name>
        </maintainer>
        <maintainer>
                <email>blueness@gentoo.org</email>
                <name>Anthony G. Basile</name>
        </maintainer>
[...]

Re: [gentoo-dev] Two herds (and four extra?)

[Tony "Chainsaw" Vroon]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

On Wed, 2010-07-21 at 13:34 +0200, Jeroen Roovers wrote:
> This is madness, people. Two herds and four separately mentioned
> developers?

This is madness.
THIS IS HARDENED.

> Why don't you join a herd? Go on, it's fun and you don't
> have to be alone!

This was originally done because we were bypassing a herd (lead) in
getting our updates in. Toning it down is not a problem, would just
blueness in the list address your concerns?

>      jer

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-dev] Two herds (and four extra?)

[Jeroen Roovers]

On Wed, 21 Jul 2010 13:36:26 +0100
"Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org> wrote:

> This was originally done because we were bypassing a herd (lead) in
> getting our updates in. Toning it down is not a problem, would just
> blueness in the list address your concerns?

Current b-w policy is to assign to the first mentioned <maintainer>,
then CC all other <maintainer>s and <herd>s[1], so if blueness has no
problem with that, then sure.


     jer


[1] Or why would you mention them separately? I think we should still
    encourage developers to join herds.

Re: [gentoo-dev] Two herds (and four extra?)

[Anthony G. Basile]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/21/2010 08:58 AM, Jeroen Roovers wrote:
> On Wed, 21 Jul 2010 13:36:26 +0100
> "Tony \"Chainsaw\" Vroon" <chainsaw@gentoo.org> wrote:
> 
>> This was originally done because we were bypassing a herd (lead) in
>> getting our updates in. Toning it down is not a problem, would just
>> blueness in the list address your concerns?
> 
> Current b-w policy is to assign to the first mentioned <maintainer>,
> then CC all other <maintainer>s and <herd>s[1], so if blueness has no
> problem with that, then sure.
> 
> 
>      jer
> 
> 
> [1] Or why would you mention them separately? I think we should still
>     encourage developers to join herds.

I would prefer the bugs be assigned to hardened-kernel@gentoo.org and
cc'ed to hardened@gentoo.org.  All relevant devs should be on one or the
other list.  However, I am currently the principle maintainer of h-s.

The reason for my preference is 1) that's how we have been doing it
since before my time and that's how we keep track of bugs.  See [1] for
links to the open hardened-kernel bugs.  2) There is a close
relationship between hardened-kernel and hardened.  They are not two
separate projects.  The only reason for the two lists is to help keep
the issues straight: kernel issues to hardened-kernel and
userland/toolchain issues to hardened.


[1] http://dev.gentoo.org/~blueness/hardened-sources/


- -- 
Anthony G. Basile, Ph.D.
Gentoo Developer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxHB+AACgkQl5yvQNBFVTVK+wCgoA/CQPUwAwiOihjvkL2JfeZq
Rh0AoIgEPP8MfrRUNyRSRLcwg2W/quyF
=Qhls
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Two herds (and four extra?)

[Jeroen Roovers]

On Wed, 21 Jul 2010 10:44:48 -0400
"Anthony G. Basile" <blueness@gentoo.org> wrote:

> I would prefer the bugs be assigned to hardened-kernel@gentoo.org and
> cc'ed to hardened@gentoo.org.  All relevant devs should be on one or
> the other list.  However, I am currently the principle maintainer of
> h-s.

You really don't expect the currently 5-10 regular bug wranglers to
remember all that, do you? If you want things listed in a specific
order, then just remember the rules:

 = Alternative A =
* first maintainer from the top down gets to be assignee,
* otherwise the first herd gets to be assignee.

Put them in the right order an you should have no problem with bug
assignments. We could discuss this processing order (maybe change it
to having 

 = Alternative B =
* the top herd or maintainer as assignee

(but I really don't want to get tangled up in a discussion about your
preferences or anyone's preferences, and how bug wranglers should
reflect those).


     jer

Re: [gentoo-dev] Two herds (and four extra?)

[Peter Volkov]

В Срд, 21/07/2010 в 13:34 +0200, Jeroen Roovers пишет:
> This is madness, people. Two herds and four separately mentioned
> developers? Why don't you join a herd? Go on, it's fun and you don't
> have to be alone!

Jeroen, sometimes I add myself as maintainer at the same time being part
of herd for two reasons: 1. this makes clear that package has dedicated
maintainer, 2. mail client filters bug mail that are assigned on me and
on herd giving herd less priority. I really hope that semi-automatic bug
assignment will help to avoid problem b-w have now...

-- 
Peter.

Re: [gentoo-dev] Two herds (and four extra?)

[Chip Parker]

On Wed, Jul 21, 2010 at 10:11 AM, Jeroen Roovers <jer@gentoo.org> wrote:
> On Wed, 21 Jul 2010 10:44:48 -0400
> "Anthony G. Basile" <blueness@gentoo.org> wrote:
>
>> I would prefer the bugs be assigned to hardened-kernel@gentoo.org and
>> cc'ed to hardened@gentoo.org.  All relevant devs should be on one or
>> the other list.  However, I am currently the principle maintainer of
>> h-s.
>
> You really don't expect the currently 5-10 regular bug wranglers to
> remember all that, do you? If you want things listed in a specific
> order, then just remember the rules:

It seems that via this thread you've managed to inform all of them of
how things currently work. No further action necessary/problem solved.

Re: [gentoo-dev] Two herds (and four extra?)

[Anthony G. Basile]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/21/2010 12:11 PM, Jeroen Roovers wrote:
> = Alternative A = * first maintainer from the top down gets to be
> assignee, * otherwise the first herd gets to be assignee.

Thanks for the info.  Just one point of clarification.  How does the
"otherwise" work.  If we have herds listed before maintainers, do you
still assign to the first maintainer?  In other words, do you only
default to the first herd if there are no maintainers listed at all?

- -- 
Anthony G. Basile, Ph.D.
Gentoo Developer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxINfgACgkQl5yvQNBFVTVvmwCfc8JtVi9TlyzvO7MwRjcjdODH
eXMAnRjsqkjjpdrdgmNy2B+UvPGSbMyI
=Hikf
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Two herds (and four extra?)

[Jeroen Roovers]

On Thu, 22 Jul 2010 08:13:44 -0400
"Anthony G. Basile" <blueness@gentoo.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 07/21/2010 12:11 PM, Jeroen Roovers wrote:
> > = Alternative A = * first maintainer from the top down gets to be
> > assignee, * otherwise the first herd gets to be assignee.
> 
> Thanks for the info.  Just one point of clarification.  How does the
> "otherwise" work.  If we have herds listed before maintainers, do you
> still assign to the first maintainer?  In other words, do you only
> default to the first herd if there are no maintainers listed at all?

* "When metadata.xml lists a single maintainer or herd, then you assign
  the bug to that maintainer or herd. When the file lists multiple
  entries, then you assign the bug to the first maintainer, and CC the
  other maintainer(s) and herd(s). If you find that metadata.xml lists
  inappropriate and/or confusing contact information, then make a note
  of that in a comment on the bug report and assign/CC the bug report as
  optimal as possible."[1]


     jer


[1]
http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml#doc_chap4_sect3