Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 220317

Summary: Refusal to remove from mailing lists
Product: Community Reporter: Jared Burns <jared_burns>
Component: MailingListsAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED WORKSFORME QA Contact:
Severity: critical    
Priority: P3 CC: anne.jacko, bjorn.freeman-benson, donald.smith, emo, karl.matthias
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: All   
Whiteboard:

Description Jared Burns CLA 2008-02-25 23:12:38 EST
I have repeatedly unsubscribed from the eclipse.org-committers and eclipse.org-membership-at-large mailing lists. Despite this fact, I continue to receive email from these lists.

I'm told that these lists are set up to refresh their membership from some database on a daily basis. This isn't kosher. When someone asks to be removed from a mailing list, Eclipse.org should honor that request.
Comment 1 Denis Roy CLA 2008-02-26 08:54:51 EST
Instead of rebuilding the mailing list membership every night, could we perhaps simply subscribe new members, allowing older members to unsubscribe from the lists?
Comment 2 Jared Burns CLA 2008-03-06 10:22:57 EST
Eclipse.org is literally the biggest source of spam mail that I receive. Can I please be removed from whatever database is the source of the spam?
Comment 3 Donald Smith CLA 2008-03-06 14:09:25 EST
There is no <jared_burns@us.ibm.com> committer.  I'm perplexed at how you could be getting SPAM at that email address.

Denis?

 - Don
Comment 4 Anne Jacko CLA 2008-03-06 14:15:45 EST
Jared resigned as a committer, but somehow he showed up again as a committer on some components. Sharon thinks this happened when a script was run. After we saw Jared's comment this morning, Sharon removed Jared as a committer on those components.

So now when you look in the db, he's not a committer, but he was earlier today.

So the immediate problem is solved for now -- Jared will be off the mailing list as of tonight when the list is updated.

Of course this doesn't address the bigger issue of whether we should be auto-generating the lists. I'm not aware that we get any significant number of complaints about it, and IMHO if you're a committer or member you should be expected to ready the committer or membership mailing lists.
Comment 5 Jared Burns CLA 2008-03-06 14:34:38 EST
(In reply to comment #3)
> There is no <jared_burns@us.ibm.com> committer.  I'm perplexed at how you could
> be getting SPAM at that email address.

Thanks Anne (and Sharon).

To answer your question, Don, my email address in Bugzilla was updated to my IBM address, but apparently this DB has (had?) the original address I used when I was a committer - jaredburns@acm.org. My ACM address is the one that all the mailing list messages go to.
Comment 6 Denis Roy CLA 2008-03-06 14:48:49 EST
I just ran our auto-generate script, and confirmed that Jared is no longer on the eclipse.org-* lists.

Jared, you're still subscribed to these lists below.  These lists are not manipulated in any way, so you can unsubscribe at will.

     eclipse-dev
     jdt-debug-dev
     platform-doc-dev
     platform-ant-dev (as @us.ibm.com)


> This isn't kosher. When someone asks to be removed
> from a mailing list, Eclipse.org should honor that request.

Bug 109231 requested that the Committers' mailing list be refreshed from the Foundation's internal database. Today nearly a dozen eclipse.org-* mailing lists are "impossible" to unsubscribe from, and there are even talks about extending this to *-dev lists (see bug 199282), so there's obviously a clash with Jared's insight.
Comment 7 Eclipse Webmaster CLA 2008-04-25 15:22:22 EDT
We've updated the message so that they indicate that to ask about being removed from this list(and others that are auto-generated) you need to talk to the EMO about it.  

Frankly this list is if not the only way we have to reach *all* of our committers, one a of a very small number of methods we have when we need to inform the entire committer base of things(system outages, policy changes etc.) so taking committers off the list isn't really an option.

-M.