+1. I've requested the community@ mailing list from infra.

On Tue, Dec 13, 2016 at 10:40 AM, Kostas Tzoumas <ktzou...@apache.org>
wrote:

> It seems that several folks are excited about the idea - but there is still
> a concern on whether this would be spam for the dev@ and user@ lists
> (which
> I share)
>
> As a compromise, I propose to request a new mailing list (
> commun...@flink.apache.org) which we can use for this purpose, and also to
> post upcoming meetups, conferences, etc. In order to inform the community
> about this mailing list, we can cc the dev@ and user@ lists in the first
> months until the new mailing list has ramped up.
>
> On Fri, Dec 9, 2016 at 4:55 PM, Greg Hogan <c...@greghogan.com> wrote:
>
> > Google indexes the mailing list. Anyone can filter the messages to trash
> > in a few clicks.
> >
> > This will also be a means for the community to better understand which
> and
> > how companies are using Flink.
> >
> > On Fri, Dec 9, 2016 at 8:27 AM, Felix Neutatz <neut...@googlemail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I wonder whether a mailing list is a good choice for that in general. If
> >> I am looking for a job I won't register for a mailing list or browse
> >> through the archive of one but rather search it via Google. So what
> about
> >> putting it on a dedicated site on the Web Page. This feels more
> intuitive
> >> to me and gives a better overview.
> >>
> >> Best regards,
> >> Felix
> >>
> >> On Dec 9, 2016 14:20, "Ufuk Celebi" <u...@apache.org> wrote:
> >>
> >>
> >>
> >>
> >> On 9 December 2016 at 14:13:14, Robert Metzger (rmetz...@apache.org)
> >> wrote:
> >> > I'm against using the news@ list for that.
> >> > The promise of the news@ list is that its low-traffic and only for
> >> news. If
> >> > we now start having job offers (and potentially some questions on them
> >> > etc.) it'll be a list with more than some announcements.
> >> > That's also the reason why the news@ list is completely moderated.
> >>
> >> I agree with Robert. I would consider that to be spam if posted to news@
> .
> >>
> >>
> >>
> >>
> >
>

Reply via email to