[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-project-leadership] Mailing lists {WAS: Automated Error Reporting - Sign up for Weekly Problem Digests for your Project]



On 2015-06-04 01:41 PM, Denis Roy wrote:
On 04/06/15 07:32 AM, Alexandre Montplaisir wrote:

2) Impossibility to post on the list without being registered. Adding this extra step may turn some users away from posting to the list.


Of course the reason for this is probably due to reducing spam. But this could be solved with the following point:

3) Impossibility to moderate our own lists.


We will gladly make you (and another member of your team, so that you have backup) moderators of your list and turn off the subscription requirement if you want. As long as webmasters don't have to do the moderation work.


A bug to Eclipse Foundation > Community > Mailing Lists is all it takes.

As for 1. yes, we prefer that the default reply-to be the list, not the sender.

Denis

Hi Denis,

Great! I'm happy to learn that projects can indeed moderate their own list! Me and my entourage were under the impression that this option was not available.

I will look into this shortly then.


I still don't agree about the Reply-To header (I had to add your address manually to this email for instance), but one step at a time :)


Thanks,
Alexandre










On 2015-06-03 03:28 PM, Mike Milinkovich wrote:
On 03/06/2015 9:22 AM, Jay Jay Billings wrote:
We have three public mailing lists for ICE, but what if someone wants to just send something to an inbox and not join a list? We have found over the past few years that many users prefer a single project email instead of a public list. (Government types, you know. Most of the time we end up forwarding their letter to the list!)

Alternatively, what if we want to CC an email address on all of our bug reports that is not a list but we all have access to? What if someone wants to email us a question that they don't feel like putting on a public list like "What can I do to use ICE in my proprietary project at company X?"

Certainly we could just use my email address for these things, but that is not appealing for a variety of reasons. Ideally we could have a single project inbox that we could all monitor for these communication edge cases. So we created eclipse.ice.project@xxxxxxxxx <mailto:eclipse.ice.project@xxxxxxxxx> because we thought that we could only get mailing lists through the Foundation.

Ah, now I understand. I personally dislike all those forms of private communications, largely because they are almost always completely unnecessary.


I am sure that this is not a unique requirement to ICE. How do other projects handle this?

P.S. I do not understand the "...what if we want to CC an email address on all of our bug reports that is not a list but we all have access to..." use case. Why wouldn't you just use the mailing list so the discussion is archived?



_______________________________________________ eclipse.org-project-leadership mailing list eclipse.org-project-leadership@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

_______________________________________________ eclipse.org-project-leadership mailing list eclipse.org-project-leadership@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-project-leadership

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.