Thanks for the feedback. And here's some context:
We do update the website regularly. We also update twitter.
Experience (and polls) have shown that none of our attendees
are big on any of these methods of communication. They
rely on old school mailing lists.
We are also not a traditional organized conference that gets
to know the schedule a few months before the event. We will
likely never ever be one (3 months to organize and run this
conference).
People depend on knowing the content at times to decide
if they want to show up. This is our way of notifying them.
The content announcements will continue until the very last
minute.
In the past these announcements went to a much larger list
(netdev@) - but now we just send summaries.
So there are several options:
1)
Are you a twitter person? Because that is one option - we post
there all the announcements. If you are then it would make sense
to unsubscribe from people@ and watch twitter - all events
will go there.
2)
The summaries idea may be useful - but lets hear more voices
say that..
people@netdevconf is also intended to be a discussion list;
but maybe we need two lists.
cheers,
jamal
On 17-03-18 06:22 PM, Mathieu Desnoyers wrote:
----- On Mar 18, 2017, at 8:34 AM, Jamal Hadi Salim jhs@xxxxxxxxxxxx wrote:
On 17-03-18 08:27 AM, Amine Aouled Hamed wrote:
Can you stop with the spam?
Which mailing list do you represent that considers this spam?
My personal 2 cents: I got subscribed automatically to
people@xxxxxxxxxxxxxx when I registered to netconf.
The level of noise on this list is way too much for me.
May I respectfully recommend that you guys use this kind of
mailing list for organizational messages only, and keep the
schedule and sponsor details to a website, or a summary sent at
most once or twice before the event.
I will personally unsubscribe from this netdev "people"
mailing list, which will fix the problem on my side, but
I won't receive any of the communication related to
organization of the event from now on, which I think is
something the event organizers should consider in their
use of this communication channel with their attendees.
Best regards,
Mathieu
