Introducing a GDB Code Of Conduct

Introducing a GDB Code Of Conduct

[Andrew Burgess]

Greetings GDB Community!

Many GNU toolchain projects have adopted a Code of Conduct (CoC)
recently, and I believe that GDB should do likewise.

A CoC is not about imposing new rules onto the GDB community, but is an
opportunity for us to document how we already treat each other within
our community, so that new people looking to engage with us can easily
understand what is expected of them, and what they can expect from
others.  Additionally, the CoC gives a clear mechanism by which any
issues a community member may have can be raised.

I have discussed this proposal briefly with the other global
maintainers, and their feedback was either supportive, or neutral on
this topic, so I'm now opening this conversation to the wider GDB
community.

The text of the proposed CoC can be found at the end of this email, and
I look forward to hearing people's thoughts.

Like anything, the CoC should grow and evolve as the GDB community
continues to grow and evolve, this is not a once and done deal.  But, we
need something in place to evolve from.

With that in mind, unless someone identifies a show stopping issue with
the text below, then I am proposing that I will make this live some time
around mid-December 2023.  After that changes to the CoC can be handled
in the normal way, via discussion on the list.

For a CoC to work, we will need a CoC committee that can respond to any
issues that are raised.  I believe that a CoC should be administered by
the community, for the community.  And so, I'm looking for active
community members, ideally, with at least a year of contributions (big
or small) to GDB who would be willing to volunteer to join the CoC
committee.  Let me know on-list or privately if you are interested, I
hope the work involved would pretty minimal.

If there are any other questions, then please feel free to ask.

Thanks,
Andrew

---

The GDB Code of Conduct

GDB is a Free Software project, part of the GNU Project.  Like other
Free Software projects, GDB and its community are made up of
professionals, volunteers, and users from all over the world.  This
diversity is a definite strength of GDB and its community, but it also
presents some unique challenges, and can sometimes lead to
mis-communications, misunderstandings, and (hopefully, rarely) to
frustration and unhappiness.  This code presents some ground rules of
conduct that we ask everyone -- leaders of the project, its developers
and maintainers, its users, and those who seek help and guidance in its
use -- to adhere to while they participate in activities and
discussions related to GDB.  The code applies to all the types of
media where we discuss GDB, its development, maintenance, and use,
including the GDB mailing lists and IRC channels, the GDB issue
tracker, and any other GDB-related forums.

Here are the rules that we ask everyone to observe:

    Be kind to others.  Do not insult or put down other participants
    of discussions.  Avoid any language or behavior that could be
    interpreted as harassment.  In general, if someone asks you to
    stop doing or saying something as part of a discussion, then stop
    and find alternative words or means of making your point.

    Be welcoming.  We strive to be a community that welcomes and
    supports people of all backgrounds and identities.  This includes,
    but is not limited to, members of any race, ethnicity, culture,
    national origin, color, immigration status, social and economic
    class, educational level, sex, sexual orientation, gender identity
    and expression, age, size, family status, political beliefs,
    religion, and mental or physical ability.

    Be considerate.  Think carefully about your words before you
    publish them.  Think about possible consequences of
    misunderstanding ambiguous words, and replace them in advance with
    better, clearer ones.

    Be friendly and patient when communicating with others.  Always
    assume the other participants in a discussion are likely to speak
    up in good-faith, even if they disagree with you.  Remember that
    most people here write in a language that is not their first one,
    so in many cases misunderstandings or unfortunate choice of words
    can easily be explained by that and not by ill will or hostility.

    Be respectful to participants in discussions and other members of
    the community, even if you are arguing with them.  Not all of us
    will agree all the time, but disagreement is no excuse for poor
    behavior and poor manners.  Try to understand the causes for the
    disagreement, and convince rather than suppress dissenting
    opinions.  It is important that we resolve disagreements and
    differing views constructively; doing so will more often than not
    result in superior decisions and courses of action, as it draws on
    the varied backgrounds and different perspectives each one of us
    has on the issues at hand.

The above isn't an exhaustive list; rather, take it in its spirit, as
guidelines intended to make the GDB project as welcoming as possible
to everyone who wants to participate and contribute, and to allow
everyone to speak up freely in the interests of developing GDB and
making our community broader and better.

See the GNU Kind Communications Guidelines for more guidance on
constructive interactions.

People who violate this code of conduct should be made aware of their
misconduct.  In many cases, but not always, this will happen in the
same forum where the problematic behavior happened: usually, one or
more members of the GDB community will react to any such violation.
If that doesn't happen, don't hesitate to speak up and explain why
some behavior hurts you or might hurt someone else.

Alternatively, you can write to the code of conduct committee at
gdb-conduct@sourceware.org, and report the behavior you think is in
violation of this code.

However the violation is brought to the attention of the code of
conduct committee, one or more of them will then decide how best to
handle each such situation.  Some ways in which they may to respond
include:

 . Explaining to the individual(s) who violated the CoC, either in
   public or in private email, which part of their conduct is
   unacceptable and why;
 . Requesting, repeatedly if needed, that the problematic behavior be
   stopped, and asking to post an apology if deemed appropriate;
 . In extreme cases, moderating or blocking the messages of person(s)
   who violated the CoC, when repeated requests to refrain from
   unacceptable behavior don't help.

Alternatively, the code of conduct committee might decide that the
behavior is not in violation of the CoC, in which case they will work
with the person who reported it to explain why they believe so.

The decision how to handle each potential violation, which of these
and other measures to take and in what order, is up to the code of
conduct committee, based on any input provided by members of the
community (which is always welcome), and also based on the committee's
best judgement of what are the most appropriate actions in each case.
We call upon the community to accept the decisions of the code of
conduct committee in each such case and not try to force them to
respond to such incidents in other ways.

Re: Introducing a GDB Code Of Conduct

[Kevin Buettner]

On Thu, 30 Nov 2023 15:59:44 +0000
Andrew Burgess <aburgess@redhat.com> wrote:

> The text of the proposed CoC can be found at the end of this email, and
> I look forward to hearing people's thoughts.

I'm in favor of adopting this code of conduct.

Kevin

Re: Introducing a GDB Code Of Conduct

[Mike Frysinger]

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

On 30 Nov 2023 15:59, Andrew Burgess wrote:
> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
> recently, and I believe that GDB should do likewise.

adopting a CoC sounds fine, but really seems like we should be using the
same one across them.  there isn't anything in the content that screams
"this only makes sense for XXX project".  can't we do this akin to how
we merge changes from "upstream" gcc tree ?

yes, i know there are a few things inline like "here's the gdb e-mail",
but that should be fairly trivial to summarize at the beginning/end, or
ideally in a sep file altogether to make merging trivial.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Introducing a GDB Code Of Conduct

[Eli Zaretskii]

> Date: Sat, 2 Dec 2023 22:26:48 -0500
> From: Mike Frysinger <vapier@gentoo.org>
> Cc: gdb-patches@sourceware.org
> 
> On 30 Nov 2023 15:59, Andrew Burgess wrote:
> > Many GNU toolchain projects have adopted a Code of Conduct (CoC)
> > recently, and I believe that GDB should do likewise.
> 
> adopting a CoC sounds fine, but really seems like we should be using the
> same one across them.  there isn't anything in the content that screams
> "this only makes sense for XXX project".  can't we do this akin to how
> we merge changes from "upstream" gcc tree ?
> 
> yes, i know there are a few things inline like "here's the gdb e-mail",
> but that should be fairly trivial to summarize at the beginning/end, or
> ideally in a sep file altogether to make merging trivial.

I would object to adopting the GCC CoC because it has some parts that
I cannot live with, as a member of the GDB project and a global
maintainer.  That's why I wrote the GDB CoC in the first place, and
the differences are not trivial, at least to me, and are not limited
to the email addresses.

Re: Introducing a GDB Code Of Conduct

[Andrew Burgess]

Mike Frysinger <vapier@gentoo.org> writes:

> On 30 Nov 2023 15:59, Andrew Burgess wrote:
>> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
>> recently, and I believe that GDB should do likewise.
>
> adopting a CoC sounds fine, but really seems like we should be using the
> same one across them.  there isn't anything in the content that screams
> "this only makes sense for XXX project".  can't we do this akin to how
> we merge changes from "upstream" gcc tree ?
>
> yes, i know there are a few things inline like "here's the gdb e-mail",
> but that should be fairly trivial to summarize at the beginning/end, or
> ideally in a sep file altogether to make merging trivial.

Mike,

I agree that having a common policy would be great.  But as Eli has
already said, he strongly objects to both the GCC and binutils CoC.  And
if it comes to loosing Eli from the project or adopting a different CoC,
then I choose the latter.

I don't feel there is anything significantly different between what is
proposed here and either of the other CoC.  But I don't see any
significant cost in having a different policy.  Even if we did adopt the
same policy as some other project, I'd still be proposing that we (GDB)
should have our own CoC committee -- it's pretty important to me that
this should be the community policing itself, not some outside group
policing us.  As such, we (GDB) might choose to handle/interpret some
situation slightly differently to another project -- so simply having
the same written words wouldn't necessarily mean things are handled
exactly the same.

Thanks,
Andrew

Re: Introducing a GDB Code Of Conduct

[Guinevere Larsen]

Just dropping by to explicitly say: I am in favor of this code of conduct.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

On 30/11/2023 16:59, Andrew Burgess wrote:
> Greetings GDB Community!
>
> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
> recently, and I believe that GDB should do likewise.
>
> A CoC is not about imposing new rules onto the GDB community, but is an
> opportunity for us to document how we already treat each other within
> our community, so that new people looking to engage with us can easily
> understand what is expected of them, and what they can expect from
> others.  Additionally, the CoC gives a clear mechanism by which any
> issues a community member may have can be raised.
>
> I have discussed this proposal briefly with the other global
> maintainers, and their feedback was either supportive, or neutral on
> this topic, so I'm now opening this conversation to the wider GDB
> community.
>
> The text of the proposed CoC can be found at the end of this email, and
> I look forward to hearing people's thoughts.
>
> Like anything, the CoC should grow and evolve as the GDB community
> continues to grow and evolve, this is not a once and done deal.  But, we
> need something in place to evolve from.
>
> With that in mind, unless someone identifies a show stopping issue with
> the text below, then I am proposing that I will make this live some time
> around mid-December 2023.  After that changes to the CoC can be handled
> in the normal way, via discussion on the list.
>
> For a CoC to work, we will need a CoC committee that can respond to any
> issues that are raised.  I believe that a CoC should be administered by
> the community, for the community.  And so, I'm looking for active
> community members, ideally, with at least a year of contributions (big
> or small) to GDB who would be willing to volunteer to join the CoC
> committee.  Let me know on-list or privately if you are interested, I
> hope the work involved would pretty minimal.
>
> If there are any other questions, then please feel free to ask.
>
> Thanks,
> Andrew
>
> ---
>
> The GDB Code of Conduct
>
> GDB is a Free Software project, part of the GNU Project.  Like other
> Free Software projects, GDB and its community are made up of
> professionals, volunteers, and users from all over the world.  This
> diversity is a definite strength of GDB and its community, but it also
> presents some unique challenges, and can sometimes lead to
> mis-communications, misunderstandings, and (hopefully, rarely) to
> frustration and unhappiness.  This code presents some ground rules of
> conduct that we ask everyone -- leaders of the project, its developers
> and maintainers, its users, and those who seek help and guidance in its
> use -- to adhere to while they participate in activities and
> discussions related to GDB.  The code applies to all the types of
> media where we discuss GDB, its development, maintenance, and use,
> including the GDB mailing lists and IRC channels, the GDB issue
> tracker, and any other GDB-related forums.
>
> Here are the rules that we ask everyone to observe:
>
>      Be kind to others.  Do not insult or put down other participants
>      of discussions.  Avoid any language or behavior that could be
>      interpreted as harassment.  In general, if someone asks you to
>      stop doing or saying something as part of a discussion, then stop
>      and find alternative words or means of making your point.
>
>      Be welcoming.  We strive to be a community that welcomes and
>      supports people of all backgrounds and identities.  This includes,
>      but is not limited to, members of any race, ethnicity, culture,
>      national origin, color, immigration status, social and economic
>      class, educational level, sex, sexual orientation, gender identity
>      and expression, age, size, family status, political beliefs,
>      religion, and mental or physical ability.
>
>      Be considerate.  Think carefully about your words before you
>      publish them.  Think about possible consequences of
>      misunderstanding ambiguous words, and replace them in advance with
>      better, clearer ones.
>
>      Be friendly and patient when communicating with others.  Always
>      assume the other participants in a discussion are likely to speak
>      up in good-faith, even if they disagree with you.  Remember that
>      most people here write in a language that is not their first one,
>      so in many cases misunderstandings or unfortunate choice of words
>      can easily be explained by that and not by ill will or hostility.
>
>      Be respectful to participants in discussions and other members of
>      the community, even if you are arguing with them.  Not all of us
>      will agree all the time, but disagreement is no excuse for poor
>      behavior and poor manners.  Try to understand the causes for the
>      disagreement, and convince rather than suppress dissenting
>      opinions.  It is important that we resolve disagreements and
>      differing views constructively; doing so will more often than not
>      result in superior decisions and courses of action, as it draws on
>      the varied backgrounds and different perspectives each one of us
>      has on the issues at hand.
>
> The above isn't an exhaustive list; rather, take it in its spirit, as
> guidelines intended to make the GDB project as welcoming as possible
> to everyone who wants to participate and contribute, and to allow
> everyone to speak up freely in the interests of developing GDB and
> making our community broader and better.
>
> See the GNU Kind Communications Guidelines for more guidance on
> constructive interactions.
>
> People who violate this code of conduct should be made aware of their
> misconduct.  In many cases, but not always, this will happen in the
> same forum where the problematic behavior happened: usually, one or
> more members of the GDB community will react to any such violation.
> If that doesn't happen, don't hesitate to speak up and explain why
> some behavior hurts you or might hurt someone else.
>
> Alternatively, you can write to the code of conduct committee at
> gdb-conduct@sourceware.org, and report the behavior you think is in
> violation of this code.
>
> However the violation is brought to the attention of the code of
> conduct committee, one or more of them will then decide how best to
> handle each such situation.  Some ways in which they may to respond
> include:
>
>   . Explaining to the individual(s) who violated the CoC, either in
>     public or in private email, which part of their conduct is
>     unacceptable and why;
>   . Requesting, repeatedly if needed, that the problematic behavior be
>     stopped, and asking to post an apology if deemed appropriate;
>   . In extreme cases, moderating or blocking the messages of person(s)
>     who violated the CoC, when repeated requests to refrain from
>     unacceptable behavior don't help.
>
> Alternatively, the code of conduct committee might decide that the
> behavior is not in violation of the CoC, in which case they will work
> with the person who reported it to explain why they believe so.
>
> The decision how to handle each potential violation, which of these
> and other measures to take and in what order, is up to the code of
> conduct committee, based on any input provided by members of the
> community (which is always welcome), and also based on the committee's
> best judgement of what are the most appropriate actions in each case.
> We call upon the community to accept the decisions of the code of
> conduct committee in each such case and not try to force them to
> respond to such incidents in other ways.
>

Re: Introducing a GDB Code Of Conduct

[John Baldwin]

On 11/30/23 7:59 AM, Andrew Burgess wrote:
> 
> Greetings GDB Community!
> 
> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
> recently, and I believe that GDB should do likewise.
> 
> A CoC is not about imposing new rules onto the GDB community, but is an
> opportunity for us to document how we already treat each other within
> our community, so that new people looking to engage with us can easily
> understand what is expected of them, and what they can expect from
> others.  Additionally, the CoC gives a clear mechanism by which any
> issues a community member may have can be raised.
> 
> I have discussed this proposal briefly with the other global
> maintainers, and their feedback was either supportive, or neutral on
> this topic, so I'm now opening this conversation to the wider GDB
> community.
> 
> The text of the proposed CoC can be found at the end of this email, and
> I look forward to hearing people's thoughts.
> 
> Like anything, the CoC should grow and evolve as the GDB community
> continues to grow and evolve, this is not a once and done deal.  But, we
> need something in place to evolve from.
> 
> With that in mind, unless someone identifies a show stopping issue with
> the text below, then I am proposing that I will make this live some time
> around mid-December 2023.  After that changes to the CoC can be handled
> in the normal way, via discussion on the list.
> 
> For a CoC to work, we will need a CoC committee that can respond to any
> issues that are raised.  I believe that a CoC should be administered by
> the community, for the community.  And so, I'm looking for active
> community members, ideally, with at least a year of contributions (big
> or small) to GDB who would be willing to volunteer to join the CoC
> committee.  Let me know on-list or privately if you are interested, I
> hope the work involved would pretty minimal.
> 
> If there are any other questions, then please feel free to ask.

I think the proposed CoC is a good one.

-- 
John Baldwin

Re: Introducing a GDB Code Of Conduct

[Andrew Burgess]

Andrew Burgess <aburgess@redhat.com> writes:

> Greetings GDB Community!
>
> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
> recently, and I believe that GDB should do likewise.
>
> A CoC is not about imposing new rules onto the GDB community, but is an
> opportunity for us to document how we already treat each other within
> our community, so that new people looking to engage with us can easily
> understand what is expected of them, and what they can expect from
> others.  Additionally, the CoC gives a clear mechanism by which any
> issues a community member may have can be raised.
>
> I have discussed this proposal briefly with the other global
> maintainers, and their feedback was either supportive, or neutral on
> this topic, so I'm now opening this conversation to the wider GDB
> community.
>
> The text of the proposed CoC can be found at the end of this email, and
> I look forward to hearing people's thoughts.
>
> Like anything, the CoC should grow and evolve as the GDB community
> continues to grow and evolve, this is not a once and done deal.  But, we
> need something in place to evolve from.
>
> With that in mind, unless someone identifies a show stopping issue with
> the text below, then I am proposing that I will make this live some time
> around mid-December 2023.  After that changes to the CoC can be handled
> in the normal way, via discussion on the list.

I've now added the code of conduct to the GDB website.

However.  I still need some volunteers to join the code of conduct
committee.

The only requirement is that you have been active in the GDB community
for at lest the last year, that you be willing to sign up to the
gdb-conduct mailing list and be willing to engage with any issues that
are reported there.

I predict / hope that we'll not see anything much reported there, so my
hope is that this will be pretty much a non-task.

Remember, this is not about *changing* the way the GDB community works,
but about preserving the great environment we already have.

Membership of the conduct committee will be made public on the GDB
website.

If you are willing to help out with this, then let me know and I'll get
you added in the New Year.

Thanks,
Andrew

Re: Introducing a GDB Code Of Conduct

[Guinevere Larsen]

On 22/12/2023 12:24, Andrew Burgess wrote:
> Andrew Burgess <aburgess@redhat.com> writes:
>
>> Greetings GDB Community!
>>
>> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
>> recently, and I believe that GDB should do likewise.
>>
>> A CoC is not about imposing new rules onto the GDB community, but is an
>> opportunity for us to document how we already treat each other within
>> our community, so that new people looking to engage with us can easily
>> understand what is expected of them, and what they can expect from
>> others.  Additionally, the CoC gives a clear mechanism by which any
>> issues a community member may have can be raised.
>>
>> I have discussed this proposal briefly with the other global
>> maintainers, and their feedback was either supportive, or neutral on
>> this topic, so I'm now opening this conversation to the wider GDB
>> community.
>>
>> The text of the proposed CoC can be found at the end of this email, and
>> I look forward to hearing people's thoughts.
>>
>> Like anything, the CoC should grow and evolve as the GDB community
>> continues to grow and evolve, this is not a once and done deal.  But, we
>> need something in place to evolve from.
>>
>> With that in mind, unless someone identifies a show stopping issue with
>> the text below, then I am proposing that I will make this live some time
>> around mid-December 2023.  After that changes to the CoC can be handled
>> in the normal way, via discussion on the list.
> I've now added the code of conduct to the GDB website.
>
> However.  I still need some volunteers to join the code of conduct
> committee.
>
> The only requirement is that you have been active in the GDB community
> for at lest the last year, that you be willing to sign up to the
> gdb-conduct mailing list and be willing to engage with any issues that
> are reported there.
>
> I predict / hope that we'll not see anything much reported there, so my
> hope is that this will be pretty much a non-task.
>
> Remember, this is not about *changing* the way the GDB community works,
> but about preserving the great environment we already have.
>
> Membership of the conduct committee will be made public on the GDB
> website.
>
> If you are willing to help out with this, then let me know and I'll get
> you added in the New Year.
>
> Thanks,
> Andrew
>
I'm interested in joining the committee. I'm leaving for the holidays 
now, but I'll be happy to do whatever is needed in the new year

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

Re: Introducing a GDB Code Of Conduct

[Mike Frysinger]

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

On 22 Dec 2023 11:24, Andrew Burgess wrote:
> I've now added the code of conduct to the GDB website.

pushing to the htdocs repo seems to not be working well.
remote: error: unable to unlink old 'code-of-conduct/Code-Of-Conduct.html': Permission denied
remote: error: unable to unlink old 'code-of-conduct/Committee.html': Permission denied
remote: error: unable to unlink old 'code-of-conduct/Reporting-Guide.html': Permission denied
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Introducing a GDB Code Of Conduct

[Guinevere Larsen]

On 12/22/23 08:24, Andrew Burgess wrote:
> Andrew Burgess <aburgess@redhat.com> writes:
>
>> Greetings GDB Community!
>>
>> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
>> recently, and I believe that GDB should do likewise.
>>
>> A CoC is not about imposing new rules onto the GDB community, but is an
>> opportunity for us to document how we already treat each other within
>> our community, so that new people looking to engage with us can easily
>> understand what is expected of them, and what they can expect from
>> others.  Additionally, the CoC gives a clear mechanism by which any
>> issues a community member may have can be raised.
>>
>> I have discussed this proposal briefly with the other global
>> maintainers, and their feedback was either supportive, or neutral on
>> this topic, so I'm now opening this conversation to the wider GDB
>> community.
>>
>> The text of the proposed CoC can be found at the end of this email, and
>> I look forward to hearing people's thoughts.
>>
>> Like anything, the CoC should grow and evolve as the GDB community
>> continues to grow and evolve, this is not a once and done deal.  But, we
>> need something in place to evolve from.
>>
>> With that in mind, unless someone identifies a show stopping issue with
>> the text below, then I am proposing that I will make this live some time
>> around mid-December 2023.  After that changes to the CoC can be handled
>> in the normal way, via discussion on the list.
> I've now added the code of conduct to the GDB website.
>
> However.  I still need some volunteers to join the code of conduct
> committee.
>
> The only requirement is that you have been active in the GDB community
> for at lest the last year, that you be willing to sign up to the
> gdb-conduct mailing list and be willing to engage with any issues that
> are reported there.
>
> I predict / hope that we'll not see anything much reported there, so my
> hope is that this will be pretty much a non-task.
>
> Remember, this is not about *changing* the way the GDB community works,
> but about preserving the great environment we already have.
>
> Membership of the conduct committee will be made public on the GDB
> website.
>
> If you are willing to help out with this, then let me know and I'll get
> you added in the New Year.
>
> Thanks,
> Andrew
>
Has there been any movement regarding the CoC committee? We've had the 
page up for quite a while and it would be nice to populate it.

Especially with the recent XZ backdoor being led by a 
harassment/bullying campaign, it would be nice to have people with the 
ability to shut down that type of behavior could be a good hardening 
step for the project (not that I have seen any interaction at all that 
would benefit from a step in, but that's what hardening is for).

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

Re: Introducing a GDB Code Of Conduct

[Andrew Burgess]

Guinevere Larsen <blarsen@redhat.com> writes:

>> Andrew Burgess <aburgess@redhat.com> writes:
>>
>> If you are willing to help out with this, then let me know and I'll get
>> you added in the New Year.
>>
>> Thanks,
>> Andrew
>>
> Has there been any movement regarding the CoC committee? We've had the 
> page up for quite a while and it would be nice to populate it.

I've started a new thread on gdb-patches asking for volunteers,
hopefully that might get more attention ... and responses.

Thanks,
Andrew