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 <rchi...@apache.org> 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 > > -- -- Guozhang
