Add JIRA components?

[Nick Dimiduk <nd...@gmail.com>]

Heya,

Does it make sense to introduce component labels into JIRA? For my own
needs, this would make it easier for me to find issues related to avatica.
Presumably others could find this useful as well.

Thoughts?
-n

Re: Add JIRA components?

[Nick Dimiduk <nd...@gmail.com>]

No issue. If that's how we want to handle it, then "core" should be the
default component selected when creating tickets.

On Fri, Jun 26, 2015 at 3:14 PM, Jacques Nadeau <ja...@apache.org> wrote:

> I think we should have an actual "core" component.  Otherwise it is hard to
> distinguish uncategorized and core issues.  Nick, any hesitancy with that?
>
> On Fri, Jun 26, 2015 at 3:03 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
> > In that case, I suggest the following as our project components: avatica,
> > mongo-connector, spark-connector, splunk-connector, build. Anything not
> > marked with a component would be "core" by default. This sound about
> right?
> >
> > Seems I lack sufficient JIRA privileges to administer components. Julian
> > would you mind terribly doing the honors?
> >
> > -n
> >
> > On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:
> >
> > > I'd much rather have too few components than too many. Otherwise there
> > > is a significant chance that bugs will be categorized in the wrong
> > > component.
> > >
> > > Avatica makes sense because it is very clear cut. The various adapters
> > > e.g. MongoDB make sense also. Other areas I'd need some convincing.
> > >
> > > On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com>
> > wrote:
> > > > Heya,
> > > >
> > > > Does it make sense to introduce component labels into JIRA? For my
> own
> > > > needs, this would make it easier for me to find issues related to
> > > avatica.
> > > > Presumably others could find this useful as well.
> > > >
> > > > Thoughts?
> > > > -n
> > >
> >
>

Re: Add JIRA components?

[Julian Hyde <jh...@apache.org>]

OK, you got it.

(Your sainthood may take a little longer.)

On Fri, Jun 26, 2015 at 3:38 PM, Nick Dimiduk <nd...@gmail.com> wrote:
> On Fri, Jun 26, 2015 at 3:17 PM, Julian Hyde <jh...@apache.org> wrote:
>
>> If anyone would like to volunteer to be the default assignee for a
>> particular component that would be MARVELOUS.
>>
>
> I can take avatica unless someone wants it more than I ;)
>
> On Fri, Jun 26, 2015 at 3:14 PM, Jacques Nadeau <ja...@apache.org> wrote:
>> > I think we should have an actual "core" component.  Otherwise it is hard
>> to
>> > distinguish uncategorized and core issues.  Nick, any hesitancy with
>> that?
>> >
>> > On Fri, Jun 26, 2015 at 3:03 PM, Nick Dimiduk <nd...@gmail.com>
>> wrote:
>> >
>> >> In that case, I suggest the following as our project components:
>> avatica,
>> >> mongo-connector, spark-connector, splunk-connector, build. Anything not
>> >> marked with a component would be "core" by default. This sound about
>> right?
>> >>
>> >> Seems I lack sufficient JIRA privileges to administer components. Julian
>> >> would you mind terribly doing the honors?
>> >>
>> >> -n
>> >>
>> >> On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:
>> >>
>> >> > I'd much rather have too few components than too many. Otherwise there
>> >> > is a significant chance that bugs will be categorized in the wrong
>> >> > component.
>> >> >
>> >> > Avatica makes sense because it is very clear cut. The various adapters
>> >> > e.g. MongoDB make sense also. Other areas I'd need some convincing.
>> >> >
>> >> > On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com>
>> >> wrote:
>> >> > > Heya,
>> >> > >
>> >> > > Does it make sense to introduce component labels into JIRA? For my
>> own
>> >> > > needs, this would make it easier for me to find issues related to
>> >> > avatica.
>> >> > > Presumably others could find this useful as well.
>> >> > >
>> >> > > Thoughts?
>> >> > > -n
>> >> >
>> >>
>>

Re: Add JIRA components?

[Nick Dimiduk <nd...@gmail.com>]

On Fri, Jun 26, 2015 at 3:17 PM, Julian Hyde <jh...@apache.org> wrote:

> If anyone would like to volunteer to be the default assignee for a
> particular component that would be MARVELOUS.
>

I can take avatica unless someone wants it more than I ;)

On Fri, Jun 26, 2015 at 3:14 PM, Jacques Nadeau <ja...@apache.org> wrote:
> > I think we should have an actual "core" component.  Otherwise it is hard
> to
> > distinguish uncategorized and core issues.  Nick, any hesitancy with
> that?
> >
> > On Fri, Jun 26, 2015 at 3:03 PM, Nick Dimiduk <nd...@gmail.com>
> wrote:
> >
> >> In that case, I suggest the following as our project components:
> avatica,
> >> mongo-connector, spark-connector, splunk-connector, build. Anything not
> >> marked with a component would be "core" by default. This sound about
> right?
> >>
> >> Seems I lack sufficient JIRA privileges to administer components. Julian
> >> would you mind terribly doing the honors?
> >>
> >> -n
> >>
> >> On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:
> >>
> >> > I'd much rather have too few components than too many. Otherwise there
> >> > is a significant chance that bugs will be categorized in the wrong
> >> > component.
> >> >
> >> > Avatica makes sense because it is very clear cut. The various adapters
> >> > e.g. MongoDB make sense also. Other areas I'd need some convincing.
> >> >
> >> > On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com>
> >> wrote:
> >> > > Heya,
> >> > >
> >> > > Does it make sense to introduce component labels into JIRA? For my
> own
> >> > > needs, this would make it easier for me to find issues related to
> >> > avatica.
> >> > > Presumably others could find this useful as well.
> >> > >
> >> > > Thoughts?
> >> > > -n
> >> >
> >>
>

Re: Add JIRA components?

[Julian Hyde <jh...@apache.org>]

Done. Components are now ["site", "spark", "splunk", "mongodb",
"avatica", "build", "core"].

On Fri, Jun 26, 2015 at 3:17 PM, Julian Hyde <jh...@apache.org> wrote:
> That sounds about right (except that we use the word "adapter" rather
> than "connector").
>
> If anyone would like to volunteer to be the default assignee for a
> particular component that would be MARVELOUS.
>
> Julian
>
>
> On Fri, Jun 26, 2015 at 3:14 PM, Jacques Nadeau <ja...@apache.org> wrote:
>> I think we should have an actual "core" component.  Otherwise it is hard to
>> distinguish uncategorized and core issues.  Nick, any hesitancy with that?
>>
>> On Fri, Jun 26, 2015 at 3:03 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>>
>>> In that case, I suggest the following as our project components: avatica,
>>> mongo-connector, spark-connector, splunk-connector, build. Anything not
>>> marked with a component would be "core" by default. This sound about right?
>>>
>>> Seems I lack sufficient JIRA privileges to administer components. Julian
>>> would you mind terribly doing the honors?
>>>
>>> -n
>>>
>>> On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:
>>>
>>> > I'd much rather have too few components than too many. Otherwise there
>>> > is a significant chance that bugs will be categorized in the wrong
>>> > component.
>>> >
>>> > Avatica makes sense because it is very clear cut. The various adapters
>>> > e.g. MongoDB make sense also. Other areas I'd need some convincing.
>>> >
>>> > On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com>
>>> wrote:
>>> > > Heya,
>>> > >
>>> > > Does it make sense to introduce component labels into JIRA? For my own
>>> > > needs, this would make it easier for me to find issues related to
>>> > avatica.
>>> > > Presumably others could find this useful as well.
>>> > >
>>> > > Thoughts?
>>> > > -n
>>> >
>>>

Re: Add JIRA components?

[Julian Hyde <jh...@apache.org>]

That sounds about right (except that we use the word "adapter" rather
than "connector").

If anyone would like to volunteer to be the default assignee for a
particular component that would be MARVELOUS.

Julian


On Fri, Jun 26, 2015 at 3:14 PM, Jacques Nadeau <ja...@apache.org> wrote:
> I think we should have an actual "core" component.  Otherwise it is hard to
> distinguish uncategorized and core issues.  Nick, any hesitancy with that?
>
> On Fri, Jun 26, 2015 at 3:03 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
>> In that case, I suggest the following as our project components: avatica,
>> mongo-connector, spark-connector, splunk-connector, build. Anything not
>> marked with a component would be "core" by default. This sound about right?
>>
>> Seems I lack sufficient JIRA privileges to administer components. Julian
>> would you mind terribly doing the honors?
>>
>> -n
>>
>> On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:
>>
>> > I'd much rather have too few components than too many. Otherwise there
>> > is a significant chance that bugs will be categorized in the wrong
>> > component.
>> >
>> > Avatica makes sense because it is very clear cut. The various adapters
>> > e.g. MongoDB make sense also. Other areas I'd need some convincing.
>> >
>> > On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com>
>> wrote:
>> > > Heya,
>> > >
>> > > Does it make sense to introduce component labels into JIRA? For my own
>> > > needs, this would make it easier for me to find issues related to
>> > avatica.
>> > > Presumably others could find this useful as well.
>> > >
>> > > Thoughts?
>> > > -n
>> >
>>

Re: Add JIRA components?

[Jacques Nadeau <ja...@apache.org>]

I think we should have an actual "core" component.  Otherwise it is hard to
distinguish uncategorized and core issues.  Nick, any hesitancy with that?

On Fri, Jun 26, 2015 at 3:03 PM, Nick Dimiduk <nd...@gmail.com> wrote:

> In that case, I suggest the following as our project components: avatica,
> mongo-connector, spark-connector, splunk-connector, build. Anything not
> marked with a component would be "core" by default. This sound about right?
>
> Seems I lack sufficient JIRA privileges to administer components. Julian
> would you mind terribly doing the honors?
>
> -n
>
> On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:
>
> > I'd much rather have too few components than too many. Otherwise there
> > is a significant chance that bugs will be categorized in the wrong
> > component.
> >
> > Avatica makes sense because it is very clear cut. The various adapters
> > e.g. MongoDB make sense also. Other areas I'd need some convincing.
> >
> > On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com>
> wrote:
> > > Heya,
> > >
> > > Does it make sense to introduce component labels into JIRA? For my own
> > > needs, this would make it easier for me to find issues related to
> > avatica.
> > > Presumably others could find this useful as well.
> > >
> > > Thoughts?
> > > -n
> >
>

Re: Add JIRA components?

[Nick Dimiduk <nd...@gmail.com>]

In that case, I suggest the following as our project components: avatica,
mongo-connector, spark-connector, splunk-connector, build. Anything not
marked with a component would be "core" by default. This sound about right?

Seems I lack sufficient JIRA privileges to administer components. Julian
would you mind terribly doing the honors?

-n

On Thu, Jun 25, 2015 at 3:53 PM, Julian Hyde <jh...@apache.org> wrote:

> I'd much rather have too few components than too many. Otherwise there
> is a significant chance that bugs will be categorized in the wrong
> component.
>
> Avatica makes sense because it is very clear cut. The various adapters
> e.g. MongoDB make sense also. Other areas I'd need some convincing.
>
> On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com> wrote:
> > Heya,
> >
> > Does it make sense to introduce component labels into JIRA? For my own
> > needs, this would make it easier for me to find issues related to
> avatica.
> > Presumably others could find this useful as well.
> >
> > Thoughts?
> > -n
>

Re: Add JIRA components?

[Julian Hyde <jh...@apache.org>]

I'd much rather have too few components than too many. Otherwise there
is a significant chance that bugs will be categorized in the wrong
component.

Avatica makes sense because it is very clear cut. The various adapters
e.g. MongoDB make sense also. Other areas I'd need some convincing.

On Thu, Jun 25, 2015 at 2:58 PM, Nick Dimiduk <nd...@gmail.com> wrote:
> Heya,
>
> Does it make sense to introduce component labels into JIRA? For my own
> needs, this would make it easier for me to find issues related to avatica.
> Presumably others could find this useful as well.
>
> Thoughts?
> -n