Update Security topic coordinators section in MAINTAINERS.txt

Makes sense to me, though I was never comfortable being listed there (and especially not as an individual).

I suggest it could make more sense to get a list of people who are interested in being listed there and add a link to https://drupal.org/security-team/report-issue

Ah, the use of - as a bullet point in this file threw me off on what was proposed.

I'm fine adding Michael as a first step. I'd like to see a broader call for interested people as a second step (this issue seems like a good spot to do that).

Sounds good to me as well. Maybe add the security@drupal.org address to report an issue to the security team (https://www.drupal.org/security-team)

I think we're trying to phase out that address for public use, right?

Looks good to me. Thanks @xjm

+The Drupal security team provives Security Advisories for vulnerabilities,

"provives" => "provides" (could be fixed on commit)

This should be backported in some form or other. Though I'd suggest keeping Greg listed there also for D6 and D7 (perhaps with some kind of "emeritus" modifier or a list of years served), unless he really doesn't want to be?

(I think there's a precedent for treating it as a "credits" list too, so keeping people who were security leads for a long time during these releases could be good. By that logic, Heine should still be listed there too of course.)

Cool, this seems good to me. For some reason I thought I remembered a discussion at NYCCamp where greggles wanted to remain on but #1 seems to imply perhaps that was a hallucination. :)

Committed and pushed to 8.x. Moving down to 7.x for discussion, since David's point in #8 is worth discussing for 6.x and 7.x. (Not as much for 8.x, IMO, because Greg's retirement pre-dates 8.x's release. Hopefully we'll get 8.x done before Michael retires, too. ;))

I have back-ported the D8 changes to D7.

@greggles, any thoughts on #8 and #9? Are you OK having your name totally removed (even for Drupal 7)?

Yep, I'm fine with this.

11: secteam-2249025-11.patch queued for re-testing.

Likely testbot glitch - moving back to RTBC.

Went ahead and committed this to get it into the upcoming Drupal 7.30 release - thanks!