Return-Path: X-Original-To: apmail-flink-dev-archive@www.apache.org Delivered-To: apmail-flink-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D0F317ADB for ; Sat, 18 Apr 2015 21:29:55 +0000 (UTC) Received: (qmail 53330 invoked by uid 500); 18 Apr 2015 21:29:55 -0000 Delivered-To: apmail-flink-dev-archive@flink.apache.org Received: (qmail 53271 invoked by uid 500); 18 Apr 2015 21:29:55 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 53259 invoked by uid 99); 18 Apr 2015 21:29:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Apr 2015 21:29:54 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for dev@flink.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Apr 2015 21:29:49 +0000 Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 327A6454A7 for ; Sat, 18 Apr 2015 21:29:29 +0000 (UTC) Received: by iejt8 with SMTP id t8so93893785iej.2 for ; Sat, 18 Apr 2015 14:28:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ML7HlCbLyeP+RY7B7Q1/OuAiW4llO3r16Hmvwcbd90Q=; b=nRI3bBLd44QmjStdia12JTZP9+3IWYLsVcrLsPJj2J/R5xWVG8viiapdLJdlGIoisH +JyUUSaAFYuLV4Fv8Ye2urdNal1UIAMXglswVUgwhrAo+Tl+a9TcL0JPEmQ/7I82d/KG 8iNeW6Qub7xQwp0UJ5HRzoSgxts0BZR2FkpjjuifCu2JUvfsqYBz/SWSn/vIRD4tI8IF wo3M+QXWAzRDd05MvMEe170MJzzi2N0rmQw46GKPt6KMA6ZUwGri6Sampe6XzZu3z0v3 OV5jJ7zomUo4G33LUtF7Tyy57X9qESTkYUZYwIsL+OfTnqAuyrCraT0htgxcOE/wKTfQ V1Vg== MIME-Version: 1.0 X-Received: by 10.107.128.149 with SMTP id k21mr12193345ioi.7.1429392523604; Sat, 18 Apr 2015 14:28:43 -0700 (PDT) Received: by 10.64.245.227 with HTTP; Sat, 18 Apr 2015 14:28:43 -0700 (PDT) In-Reply-To: References: Date: Sat, 18 Apr 2015 14:28:43 -0700 Message-ID: Subject: Re: [DISCUSS] Replace user@f.a.o with Stackoverflow From: Henry Saputra To: "dev@flink.apache.org" Cc: Flink dev list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Unfortunately as top level Apache project we can not have official discussions outside Apache domains. Which means that we still need user@ list as the main mechanism for users to ask to communicate and ask questions. Some Apache projects like Hadoop and Spark also have the community monitoring Stackoverflow for questions but still maintain user@ list as the official channel for communication for the project - Henry On Sat, Apr 18, 2015 at 2:16 AM, Ufuk Celebi wrote: > Hey all, > > I've been asking myself: how can we make it as easy as possible for futur= e > users who run into problems to find existing answers? > > As an example take this answer from Stephan [1]. This is super valuable > feedback and a very specific question. Ideally, a new user who runs into > the same problem should find this answer. > > I think the best way to achieve this is Stack Overflow. There are already= a > couple of questions regarding Flink, but they questions are fragmented ov= er > user@ and SO. > > Robert already added a suggested tag to the website recently, but I was > wondering whether we should take this a step further and want to discuss > the following: > > Should we *only* recommend SO for user questions and don't link the user > list at all? > > For example, the Netty project is doing it that way. This has the advanta= ge > that 1) there is one conveniently searchable place for user questions, an= d > 2) all the SO pros like voting on answers, it is well known etc. On the > other hand, you can already search the ML archives with Nabble and what > about existing questions/answers? > > Looking forward to get your feedback. It's also quite possible that there > is no real problem here and that I'm trying to over engineer this. Feel > free to tell me. ;-) > > =E2=80=93 Ufuk > > [1] > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Hash-= join-exceeded-exception-td1086.html