From dev-return-96340-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Mon Jul 23 20:28:41 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2D3F1180647 for ; Mon, 23 Jul 2018 20:28:40 +0200 (CEST) Received: (qmail 73296 invoked by uid 500); 23 Jul 2018 18:28:39 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 73279 invoked by uid 99); 23 Jul 2018 18:28:39 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2018 18:28:39 +0000 Received: from dhcp-10-16-3-136.pa.cloudera.com (unknown [64.125.238.131]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 0A8C72007 for ; Mon, 23 Jul 2018 18:28:38 +0000 (UTC) Subject: Re: Discussion: New components in JIRA? To: dev@kafka.apache.org References: From: Ray Chiang Message-ID: <74c05be3-b123-0f48-7735-e7649e05bdfb@apache.org> Date: Mon, 23 Jul 2018 11:28:44 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Good point.  I'll look into adding some JIRA guidelines to the documentation/wiki. -Ray On 7/22/18 10:23 AM, Guozhang Wang wrote: > Hello Ray, > > Thanks for brining this up. I'm generally +1 on the first two, while for > the last category, personally I felt leaving them as part of `tools` is > fine, but I'm also open for other opinions. > > A more general question though, is that today we do not have any guidelines > to ask JIRA reporters to set the right component, i.e. it is purely > best-effort, and we cannot disallow reporters to add any new component > names. And so far the project does not really have a tradition to manage > JIRA reports per-component, as the goal is to not "separate" the project > into silos but recommending everyone to get hands on every aspect of the > project. > > > Guozhang > > > On Fri, Jul 20, 2018 at 2:44 PM, Ray Chiang wrote: > >> I've been doing a little bit of component cleanup in JIRA. What do people >> think of adding >> one or more of the following components? >> >> - logging: For any consumer/producer/broker logging (i.e. log4j). This >> should help disambiguate from the "log" component (i.e. Kafka messages). >> >> - mirrormaker: There are enough requests specific to MirrorMaker that it >> could be put into its own component. >> >> - scripts: I'm a little more ambivalent about this one, but any of the >> bin/*.sh script fixes could belong in their own category. I'm not sure if >> other people feel strongly for how the "tools" component should be used >> w.r.t. the run scripts. >> >> Any thoughts? >> >> -Ray >> >> >