You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by Jesse McConnell <je...@gmail.com> on 2006/11/10 19:12:40 UTC
jira components
The current components in jira are (with current # of categoried issues):
AOL Notifier 1
Core system 80
Database 16
Documentation 12
IRC Notifier 3
Jabber Notifier 3
Mail Notifier 14
MSN Notifier 2
Notification 5
Project Grouping 1
SCM 18
Web interface 107
XMLRPC Interface 12
No Component 61
I would like to propose reorganizing these a little bit, combining all
of the Notifiers into the Notification component. Also add a
component for the different integrations for issues related to
Ant/Shell/M1 and M2 integrations, I think they are currently mostly
getting split out between Web Interface and Core system.
We also might be well served by breaking out the web interface into
components: Web - Security, Web - Notification, Web - Groups, Web -
Projects, Web - Other.
thoughts?
jesse
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: jira components
Posted by Jesse McConnell <je...@gmail.com>.
well, when you look at it like that...
ok, I'll do that this weekend and try and get a home for those poor 61
lonely issues :)
jesse
On 11/10/06, Brett Porter <br...@apache.org> wrote:
> I think breaking out the tools and notifiers is a good idea. They are
> actually the *easiest* ones for people to hit because they know which
> specific one they are using.
>
> How about breaking up core system into scheduling, etc? Also, is
> there anything in those 61 no components that should be a new component?
>
> - Brett
>
> On 11/11/2006, at 6:41 AM, Jesse McConnell wrote:
>
> > well thats a little more verbose then I was looking for, I was
> > thinking we could shove all the tool integration stuff together, and
> > all the notifiers together. I was envisioning
> >
> >
> > Core system 80
> > Database 16
> > Documentation 12
> > Tool Integration
> > Notification 5
> > SCM 18
> > Web UI 89
> > Web Security 0
> > Web Groups 13
> > Web Projects 9
> > Web Configuration 2
> > XMLRPC Interface 12
> > No Component 61
> >
> > Web seems to be the noisiest so breaking it out a bit might help, but
> > the others could be consolidated to make it easier for people
> > assigning issues initially to hit the right side of the right barn.
> >
> > jesse
> >
> >
> >
> > On 11/10/06, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> >> Breaking apart the notifiers are a good idea.
> >> However, due to natural language sort, they are not grouped very
> >> efficiently.
> >>
> >> How about "Notifier ___" instead?
> >>
> >> So, expanding your ideas to a the eventual list, we wind up with ...
> >>
> >> Core system 80
> >> Database 16
> >> Documentation 12
> >> Integration M2 0
> >> Integration M1 0
> >> Integration Ant 0
> >> Integration Shell 0
> >> Notification Subsystem 5
> >> Notifier (AOL) 1
> >> Notifier (IRC) 3
> >> Notifier (Jabber) 3
> >> Notifier (Mail) 14
> >> Notifier (MSN) 2
> >> Notifier (Wagon) 0
> >> Project Grouping 1
> >> SCM 18
> >> Web UI 89
> >> Web Security 0
> >> Web Groups 13
> >> Web Projects 9
> >> Web Configuration 2
> >> XMLRPC Interface 12
> >> No Component 61
> >>
> >> Looks detailed. ;-)
> >>
> >> - Joakim
> >>
> >> Jesse McConnell wrote:
> >> > The current components in jira are (with current # of categoried
> >> issues):
> >> >
> >> > AOL Notifier 1
> >> > Core system 80
> >> > Database 16
> >> > Documentation 12
> >> > IRC Notifier 3
> >> > Jabber Notifier 3
> >> > Mail Notifier 14
> >> > MSN Notifier 2
> >> > Notification 5
> >> > Project Grouping 1
> >> > SCM 18
> >> > Web interface 107
> >> > XMLRPC Interface 12
> >> > No Component 61
> >> >
> >> >
> >> > I would like to propose reorganizing these a little bit,
> >> combining all
> >> > of the Notifiers into the Notification component. Also add a
> >> > component for the different integrations for issues related to
> >> > Ant/Shell/M1 and M2 integrations, I think they are currently mostly
> >> > getting split out between Web Interface and Core system.
> >> >
> >> > We also might be well served by breaking out the web interface into
> >> > components: Web - Security, Web - Notification, Web - Groups, Web -
> >> > Projects, Web - Other.
> >> >
> >> > thoughts?
> >> >
> >> > jesse
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
> > --
> > jesse mcconnell
> > jesse.mcconnell@gmail.com
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: jira components
Posted by Brett Porter <br...@apache.org>.
I think breaking out the tools and notifiers is a good idea. They are
actually the *easiest* ones for people to hit because they know which
specific one they are using.
How about breaking up core system into scheduling, etc? Also, is
there anything in those 61 no components that should be a new component?
- Brett
On 11/11/2006, at 6:41 AM, Jesse McConnell wrote:
> well thats a little more verbose then I was looking for, I was
> thinking we could shove all the tool integration stuff together, and
> all the notifiers together. I was envisioning
>
>
> Core system 80
> Database 16
> Documentation 12
> Tool Integration
> Notification 5
> SCM 18
> Web UI 89
> Web Security 0
> Web Groups 13
> Web Projects 9
> Web Configuration 2
> XMLRPC Interface 12
> No Component 61
>
> Web seems to be the noisiest so breaking it out a bit might help, but
> the others could be consolidated to make it easier for people
> assigning issues initially to hit the right side of the right barn.
>
> jesse
>
>
>
> On 11/10/06, Joakim Erdfelt <jo...@erdfelt.com> wrote:
>> Breaking apart the notifiers are a good idea.
>> However, due to natural language sort, they are not grouped very
>> efficiently.
>>
>> How about "Notifier ___" instead?
>>
>> So, expanding your ideas to a the eventual list, we wind up with ...
>>
>> Core system 80
>> Database 16
>> Documentation 12
>> Integration M2 0
>> Integration M1 0
>> Integration Ant 0
>> Integration Shell 0
>> Notification Subsystem 5
>> Notifier (AOL) 1
>> Notifier (IRC) 3
>> Notifier (Jabber) 3
>> Notifier (Mail) 14
>> Notifier (MSN) 2
>> Notifier (Wagon) 0
>> Project Grouping 1
>> SCM 18
>> Web UI 89
>> Web Security 0
>> Web Groups 13
>> Web Projects 9
>> Web Configuration 2
>> XMLRPC Interface 12
>> No Component 61
>>
>> Looks detailed. ;-)
>>
>> - Joakim
>>
>> Jesse McConnell wrote:
>> > The current components in jira are (with current # of categoried
>> issues):
>> >
>> > AOL Notifier 1
>> > Core system 80
>> > Database 16
>> > Documentation 12
>> > IRC Notifier 3
>> > Jabber Notifier 3
>> > Mail Notifier 14
>> > MSN Notifier 2
>> > Notification 5
>> > Project Grouping 1
>> > SCM 18
>> > Web interface 107
>> > XMLRPC Interface 12
>> > No Component 61
>> >
>> >
>> > I would like to propose reorganizing these a little bit,
>> combining all
>> > of the Notifiers into the Notification component. Also add a
>> > component for the different integrations for issues related to
>> > Ant/Shell/M1 and M2 integrations, I think they are currently mostly
>> > getting split out between Web Interface and Core system.
>> >
>> > We also might be well served by breaking out the web interface into
>> > components: Web - Security, Web - Notification, Web - Groups, Web -
>> > Projects, Web - Other.
>> >
>> > thoughts?
>> >
>> > jesse
>> >
>> >
>> >
>>
>>
>
>
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
Re: jira components
Posted by Jesse McConnell <je...@gmail.com>.
well thats a little more verbose then I was looking for, I was
thinking we could shove all the tool integration stuff together, and
all the notifiers together. I was envisioning
Core system 80
Database 16
Documentation 12
Tool Integration
Notification 5
SCM 18
Web UI 89
Web Security 0
Web Groups 13
Web Projects 9
Web Configuration 2
XMLRPC Interface 12
No Component 61
Web seems to be the noisiest so breaking it out a bit might help, but
the others could be consolidated to make it easier for people
assigning issues initially to hit the right side of the right barn.
jesse
On 11/10/06, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> Breaking apart the notifiers are a good idea.
> However, due to natural language sort, they are not grouped very
> efficiently.
>
> How about "Notifier ___" instead?
>
> So, expanding your ideas to a the eventual list, we wind up with ...
>
> Core system 80
> Database 16
> Documentation 12
> Integration M2 0
> Integration M1 0
> Integration Ant 0
> Integration Shell 0
> Notification Subsystem 5
> Notifier (AOL) 1
> Notifier (IRC) 3
> Notifier (Jabber) 3
> Notifier (Mail) 14
> Notifier (MSN) 2
> Notifier (Wagon) 0
> Project Grouping 1
> SCM 18
> Web UI 89
> Web Security 0
> Web Groups 13
> Web Projects 9
> Web Configuration 2
> XMLRPC Interface 12
> No Component 61
>
> Looks detailed. ;-)
>
> - Joakim
>
> Jesse McConnell wrote:
> > The current components in jira are (with current # of categoried issues):
> >
> > AOL Notifier 1
> > Core system 80
> > Database 16
> > Documentation 12
> > IRC Notifier 3
> > Jabber Notifier 3
> > Mail Notifier 14
> > MSN Notifier 2
> > Notification 5
> > Project Grouping 1
> > SCM 18
> > Web interface 107
> > XMLRPC Interface 12
> > No Component 61
> >
> >
> > I would like to propose reorganizing these a little bit, combining all
> > of the Notifiers into the Notification component. Also add a
> > component for the different integrations for issues related to
> > Ant/Shell/M1 and M2 integrations, I think they are currently mostly
> > getting split out between Web Interface and Core system.
> >
> > We also might be well served by breaking out the web interface into
> > components: Web - Security, Web - Notification, Web - Groups, Web -
> > Projects, Web - Other.
> >
> > thoughts?
> >
> > jesse
> >
> >
> >
>
>
--
jesse mcconnell
jesse.mcconnell@gmail.com
Re: jira components
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Breaking apart the notifiers are a good idea.
However, due to natural language sort, they are not grouped very
efficiently.
How about "Notifier ___" instead?
So, expanding your ideas to a the eventual list, we wind up with ...
Core system 80
Database 16
Documentation 12
Integration M2 0
Integration M1 0
Integration Ant 0
Integration Shell 0
Notification Subsystem 5
Notifier (AOL) 1
Notifier (IRC) 3
Notifier (Jabber) 3
Notifier (Mail) 14
Notifier (MSN) 2
Notifier (Wagon) 0
Project Grouping 1
SCM 18
Web UI 89
Web Security 0
Web Groups 13
Web Projects 9
Web Configuration 2
XMLRPC Interface 12
No Component 61
Looks detailed. ;-)
- Joakim
Jesse McConnell wrote:
> The current components in jira are (with current # of categoried issues):
>
> AOL Notifier 1
> Core system 80
> Database 16
> Documentation 12
> IRC Notifier 3
> Jabber Notifier 3
> Mail Notifier 14
> MSN Notifier 2
> Notification 5
> Project Grouping 1
> SCM 18
> Web interface 107
> XMLRPC Interface 12
> No Component 61
>
>
> I would like to propose reorganizing these a little bit, combining all
> of the Notifiers into the Notification component. Also add a
> component for the different integrations for issues related to
> Ant/Shell/M1 and M2 integrations, I think they are currently mostly
> getting split out between Web Interface and Core system.
>
> We also might be well served by breaking out the web interface into
> components: Web - Security, Web - Notification, Web - Groups, Web -
> Projects, Web - Other.
>
> thoughts?
>
> jesse
>
>
>