JIRA Component Labels

[Glenn Adams <gl...@skynav.com>]

I have long been unsatisfied with the set of component labels previously
used with Bugzilla, which we inherited in JIRA. I've finally gotten around
to relabeling many of the existing components and adding more specific
components.

I have relabeled as follows:

awt renderer : renderer/awt
fo tree : fo/unqualified
fonts : fonts/unqualified
general : unqualified
images : images/unqualified
page-master/layout : layout/unqualified
pcl : renderer/pcl
pdf : renderer/pdf
ps : renderer/ps
rtf : renderer/rtf
svg : renderer/svg

I have added the following:

fo/block
fo/inline
fo/page
fonts/opentype
fonts/postscript
images/jpeg
images/png
images/tiff
images/svg
layout/block
layout/inline
layout/line
layout/page
renderer/afp
renderer/txt

When you edit an existing issue, if its component contains "unqualified",
then please take the opportunity to review and preferably select a more
qualified component name. If you don't find a suitably named alternative,
then please suggest one to this list so I can add it.

Note also, regarding the former "svg" component, I have relabeled that as
renderer/svg, which may not be appropriate depending on the issue. If the
issue is related to input from SVG (as opposed to output to SVG), then I
have created the images/svg component for the issues related to SVG input.

Re: JIRA Component Labels

[Pascal Sancho <ps...@gmail.com>]

I missed it.
I was remembering about Bugzilla, but didn't get the idea to look into
Jira, my bad.

2014-05-27 15:02 GMT+02:00 Glenn Adams <gl...@skynav.com>:
> A similar set of descriptions are available at [1] for the JIRA FOP project.
>
> [1]
> https://issues.apache.org/jira/browse/FOP/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel
>
>
> On Tue, May 27, 2014 at 8:43 PM, Pascal Sancho <ps...@gmail.com>
> wrote:
>>
>> The only doc I've found was in Bugzilla (see [1]).
>>
>> Your refactor is certainly more appropriate, regarding FOP "new"
>> design (I mean post v0.2x, hehe).
>>
>> [1]
>> https://issues.apache.org/bugzilla/describecomponents.cgi?product=Fop%20-%20Now%20in%20Jira
>>
>> 2014-05-27 10:09 GMT+02:00 Glenn Adams <gl...@skynav.com>:
>> > Perhaps. However, I'm not aware of any documentation for the prior
>> > component
>> > labeling system. Please point me at it if you know otherwise.
>> >
>> > I will endeavor to follow up with documentation of the more elaborate
>> > componentization when an opportunity arises. In the mean time, if you
>> > feel
>> > the urge, please feel free to write something.
>> >
>> >
>> > On Tue, May 27, 2014 at 4:00 PM, Pascal Sancho <ps...@gmail.com>
>> > wrote:
>> >>
>> >> Hi Glenn,
>> >>
>> >> Such info should be available either on website or on wiki, shouldn't
>> >> it?
>> >>
>> >> 2014-05-27 6:31 GMT+02:00 Glenn Adams <gl...@skynav.com>:
>> >> > Additional minor changes:
>> >> >
>> >> > fonts/* changed to font/*
>> >> > images/* changed to image/*
>> >> >
>> >> > Added:
>> >> >
>> >> > foreign/barcode
>> >> > foreign/svg
>> >> >
>> >> > There are now 3 SVG components:
>> >> >
>> >> > foreign/svg -  for SVG input via instream-foreign-object
>> >> > image/svg - for SVG input via external-graphic
>> >> > renderer/svg - for SVG output
>> >> >
>> >> >
>> >> >
>> >> > On Tue, May 27, 2014 at 9:56 AM, Glenn Adams <gl...@skynav.com>
>> >> > wrote:
>> >> >>
>> >> >> I have long been unsatisfied with the set of component labels
>> >> >> previously
>> >> >> used with Bugzilla, which we inherited in JIRA. I've finally gotten
>> >> >> around
>> >> >> to relabeling many of the existing components and adding more
>> >> >> specific
>> >> >> components.
>> >> >>
>> >> >> I have relabeled as follows:
>> >> >>
>> >> >> awt renderer : renderer/awt
>> >> >> fo tree : fo/unqualified
>> >> >> fonts : fonts/unqualified
>> >> >> general : unqualified
>> >> >> images : images/unqualified
>> >> >> page-master/layout : layout/unqualified
>> >> >> pcl : renderer/pcl
>> >> >> pdf : renderer/pdf
>> >> >> ps : renderer/ps
>> >> >> rtf : renderer/rtf
>> >> >> svg : renderer/svg
>> >> >>
>> >> >> I have added the following:
>> >> >>
>> >> >> fo/block
>> >> >> fo/inline
>> >> >> fo/page
>> >> >> fonts/opentype
>> >> >> fonts/postscript
>> >> >> images/jpeg
>> >> >> images/png
>> >> >> images/tiff
>> >> >> images/svg
>> >> >> layout/block
>> >> >> layout/inline
>> >> >> layout/line
>> >> >> layout/page
>> >> >> renderer/afp
>> >> >> renderer/txt
>> >> >>
>> >> >> When you edit an existing issue, if its component contains
>> >> >> "unqualified",
>> >> >> then please take the opportunity to review and preferably select a
>> >> >> more
>> >> >> qualified component name. If you don't find a suitably named
>> >> >> alternative,
>> >> >> then please suggest one to this list so I can add it.
>> >> >>
>> >> >> Note also, regarding the former "svg" component, I have relabeled
>> >> >> that
>> >> >> as
>> >> >> renderer/svg, which may not be appropriate depending on the issue.
>> >> >> If
>> >> >> the
>> >> >> issue is related to input from SVG (as opposed to output to SVG),
>> >> >> then
>> >> >> I
>> >> >> have created the images/svg component for the issues related to SVG
>> >> >> input.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> pascal
>> >
>> >
>>
>>
>>
>> --
>> pascal
>
>



-- 
pascal

Re: JIRA Component Labels

[Glenn Adams <gl...@skynav.com>]

A similar set of descriptions are available at [1] for the JIRA FOP project.

[1]
https://issues.apache.org/jira/browse/FOP/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel


On Tue, May 27, 2014 at 8:43 PM, Pascal Sancho <ps...@gmail.com>wrote:

> The only doc I've found was in Bugzilla (see [1]).
>
> Your refactor is certainly more appropriate, regarding FOP "new"
> design (I mean post v0.2x, hehe).
>
> [1]
> https://issues.apache.org/bugzilla/describecomponents.cgi?product=Fop%20-%20Now%20in%20Jira
>
> 2014-05-27 10:09 GMT+02:00 Glenn Adams <gl...@skynav.com>:
> > Perhaps. However, I'm not aware of any documentation for the prior
> component
> > labeling system. Please point me at it if you know otherwise.
> >
> > I will endeavor to follow up with documentation of the more elaborate
> > componentization when an opportunity arises. In the mean time, if you
> feel
> > the urge, please feel free to write something.
> >
> >
> > On Tue, May 27, 2014 at 4:00 PM, Pascal Sancho <ps...@gmail.com>
> > wrote:
> >>
> >> Hi Glenn,
> >>
> >> Such info should be available either on website or on wiki, shouldn't
> it?
> >>
> >> 2014-05-27 6:31 GMT+02:00 Glenn Adams <gl...@skynav.com>:
> >> > Additional minor changes:
> >> >
> >> > fonts/* changed to font/*
> >> > images/* changed to image/*
> >> >
> >> > Added:
> >> >
> >> > foreign/barcode
> >> > foreign/svg
> >> >
> >> > There are now 3 SVG components:
> >> >
> >> > foreign/svg -  for SVG input via instream-foreign-object
> >> > image/svg - for SVG input via external-graphic
> >> > renderer/svg - for SVG output
> >> >
> >> >
> >> >
> >> > On Tue, May 27, 2014 at 9:56 AM, Glenn Adams <gl...@skynav.com>
> wrote:
> >> >>
> >> >> I have long been unsatisfied with the set of component labels
> >> >> previously
> >> >> used with Bugzilla, which we inherited in JIRA. I've finally gotten
> >> >> around
> >> >> to relabeling many of the existing components and adding more
> specific
> >> >> components.
> >> >>
> >> >> I have relabeled as follows:
> >> >>
> >> >> awt renderer : renderer/awt
> >> >> fo tree : fo/unqualified
> >> >> fonts : fonts/unqualified
> >> >> general : unqualified
> >> >> images : images/unqualified
> >> >> page-master/layout : layout/unqualified
> >> >> pcl : renderer/pcl
> >> >> pdf : renderer/pdf
> >> >> ps : renderer/ps
> >> >> rtf : renderer/rtf
> >> >> svg : renderer/svg
> >> >>
> >> >> I have added the following:
> >> >>
> >> >> fo/block
> >> >> fo/inline
> >> >> fo/page
> >> >> fonts/opentype
> >> >> fonts/postscript
> >> >> images/jpeg
> >> >> images/png
> >> >> images/tiff
> >> >> images/svg
> >> >> layout/block
> >> >> layout/inline
> >> >> layout/line
> >> >> layout/page
> >> >> renderer/afp
> >> >> renderer/txt
> >> >>
> >> >> When you edit an existing issue, if its component contains
> >> >> "unqualified",
> >> >> then please take the opportunity to review and preferably select a
> more
> >> >> qualified component name. If you don't find a suitably named
> >> >> alternative,
> >> >> then please suggest one to this list so I can add it.
> >> >>
> >> >> Note also, regarding the former "svg" component, I have relabeled
> that
> >> >> as
> >> >> renderer/svg, which may not be appropriate depending on the issue. If
> >> >> the
> >> >> issue is related to input from SVG (as opposed to output to SVG),
> then
> >> >> I
> >> >> have created the images/svg component for the issues related to SVG
> >> >> input.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> pascal
> >
> >
>
>
>
> --
> pascal
>

Re: JIRA Component Labels

[Pascal Sancho <ps...@gmail.com>]

The only doc I've found was in Bugzilla (see [1]).

Your refactor is certainly more appropriate, regarding FOP "new"
design (I mean post v0.2x, hehe).

[1] https://issues.apache.org/bugzilla/describecomponents.cgi?product=Fop%20-%20Now%20in%20Jira

2014-05-27 10:09 GMT+02:00 Glenn Adams <gl...@skynav.com>:
> Perhaps. However, I'm not aware of any documentation for the prior component
> labeling system. Please point me at it if you know otherwise.
>
> I will endeavor to follow up with documentation of the more elaborate
> componentization when an opportunity arises. In the mean time, if you feel
> the urge, please feel free to write something.
>
>
> On Tue, May 27, 2014 at 4:00 PM, Pascal Sancho <ps...@gmail.com>
> wrote:
>>
>> Hi Glenn,
>>
>> Such info should be available either on website or on wiki, shouldn't it?
>>
>> 2014-05-27 6:31 GMT+02:00 Glenn Adams <gl...@skynav.com>:
>> > Additional minor changes:
>> >
>> > fonts/* changed to font/*
>> > images/* changed to image/*
>> >
>> > Added:
>> >
>> > foreign/barcode
>> > foreign/svg
>> >
>> > There are now 3 SVG components:
>> >
>> > foreign/svg -  for SVG input via instream-foreign-object
>> > image/svg - for SVG input via external-graphic
>> > renderer/svg - for SVG output
>> >
>> >
>> >
>> > On Tue, May 27, 2014 at 9:56 AM, Glenn Adams <gl...@skynav.com> wrote:
>> >>
>> >> I have long been unsatisfied with the set of component labels
>> >> previously
>> >> used with Bugzilla, which we inherited in JIRA. I've finally gotten
>> >> around
>> >> to relabeling many of the existing components and adding more specific
>> >> components.
>> >>
>> >> I have relabeled as follows:
>> >>
>> >> awt renderer : renderer/awt
>> >> fo tree : fo/unqualified
>> >> fonts : fonts/unqualified
>> >> general : unqualified
>> >> images : images/unqualified
>> >> page-master/layout : layout/unqualified
>> >> pcl : renderer/pcl
>> >> pdf : renderer/pdf
>> >> ps : renderer/ps
>> >> rtf : renderer/rtf
>> >> svg : renderer/svg
>> >>
>> >> I have added the following:
>> >>
>> >> fo/block
>> >> fo/inline
>> >> fo/page
>> >> fonts/opentype
>> >> fonts/postscript
>> >> images/jpeg
>> >> images/png
>> >> images/tiff
>> >> images/svg
>> >> layout/block
>> >> layout/inline
>> >> layout/line
>> >> layout/page
>> >> renderer/afp
>> >> renderer/txt
>> >>
>> >> When you edit an existing issue, if its component contains
>> >> "unqualified",
>> >> then please take the opportunity to review and preferably select a more
>> >> qualified component name. If you don't find a suitably named
>> >> alternative,
>> >> then please suggest one to this list so I can add it.
>> >>
>> >> Note also, regarding the former "svg" component, I have relabeled that
>> >> as
>> >> renderer/svg, which may not be appropriate depending on the issue. If
>> >> the
>> >> issue is related to input from SVG (as opposed to output to SVG), then
>> >> I
>> >> have created the images/svg component for the issues related to SVG
>> >> input.
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> pascal
>
>



-- 
pascal

Re: JIRA Component Labels

[Glenn Adams <gl...@skynav.com>]

Perhaps. However, I'm not aware of any documentation for the prior
component labeling system. Please point me at it if you know otherwise.

I will endeavor to follow up with documentation of the more elaborate
componentization when an opportunity arises. In the mean time, if you feel
the urge, please feel free to write something.


On Tue, May 27, 2014 at 4:00 PM, Pascal Sancho <ps...@gmail.com>wrote:

> Hi Glenn,
>
> Such info should be available either on website or on wiki, shouldn't it?
>
> 2014-05-27 6:31 GMT+02:00 Glenn Adams <gl...@skynav.com>:
> > Additional minor changes:
> >
> > fonts/* changed to font/*
> > images/* changed to image/*
> >
> > Added:
> >
> > foreign/barcode
> > foreign/svg
> >
> > There are now 3 SVG components:
> >
> > foreign/svg -  for SVG input via instream-foreign-object
> > image/svg - for SVG input via external-graphic
> > renderer/svg - for SVG output
> >
> >
> >
> > On Tue, May 27, 2014 at 9:56 AM, Glenn Adams <gl...@skynav.com> wrote:
> >>
> >> I have long been unsatisfied with the set of component labels previously
> >> used with Bugzilla, which we inherited in JIRA. I've finally gotten
> around
> >> to relabeling many of the existing components and adding more specific
> >> components.
> >>
> >> I have relabeled as follows:
> >>
> >> awt renderer : renderer/awt
> >> fo tree : fo/unqualified
> >> fonts : fonts/unqualified
> >> general : unqualified
> >> images : images/unqualified
> >> page-master/layout : layout/unqualified
> >> pcl : renderer/pcl
> >> pdf : renderer/pdf
> >> ps : renderer/ps
> >> rtf : renderer/rtf
> >> svg : renderer/svg
> >>
> >> I have added the following:
> >>
> >> fo/block
> >> fo/inline
> >> fo/page
> >> fonts/opentype
> >> fonts/postscript
> >> images/jpeg
> >> images/png
> >> images/tiff
> >> images/svg
> >> layout/block
> >> layout/inline
> >> layout/line
> >> layout/page
> >> renderer/afp
> >> renderer/txt
> >>
> >> When you edit an existing issue, if its component contains
> "unqualified",
> >> then please take the opportunity to review and preferably select a more
> >> qualified component name. If you don't find a suitably named
> alternative,
> >> then please suggest one to this list so I can add it.
> >>
> >> Note also, regarding the former "svg" component, I have relabeled that
> as
> >> renderer/svg, which may not be appropriate depending on the issue. If
> the
> >> issue is related to input from SVG (as opposed to output to SVG), then I
> >> have created the images/svg component for the issues related to SVG
> input.
> >>
> >>
> >>
> >>
> >
>
>
>
> --
> pascal
>

Re: JIRA Component Labels

[Pascal Sancho <ps...@gmail.com>]

Hi Glenn,

Such info should be available either on website or on wiki, shouldn't it?

2014-05-27 6:31 GMT+02:00 Glenn Adams <gl...@skynav.com>:
> Additional minor changes:
>
> fonts/* changed to font/*
> images/* changed to image/*
>
> Added:
>
> foreign/barcode
> foreign/svg
>
> There are now 3 SVG components:
>
> foreign/svg -  for SVG input via instream-foreign-object
> image/svg - for SVG input via external-graphic
> renderer/svg - for SVG output
>
>
>
> On Tue, May 27, 2014 at 9:56 AM, Glenn Adams <gl...@skynav.com> wrote:
>>
>> I have long been unsatisfied with the set of component labels previously
>> used with Bugzilla, which we inherited in JIRA. I've finally gotten around
>> to relabeling many of the existing components and adding more specific
>> components.
>>
>> I have relabeled as follows:
>>
>> awt renderer : renderer/awt
>> fo tree : fo/unqualified
>> fonts : fonts/unqualified
>> general : unqualified
>> images : images/unqualified
>> page-master/layout : layout/unqualified
>> pcl : renderer/pcl
>> pdf : renderer/pdf
>> ps : renderer/ps
>> rtf : renderer/rtf
>> svg : renderer/svg
>>
>> I have added the following:
>>
>> fo/block
>> fo/inline
>> fo/page
>> fonts/opentype
>> fonts/postscript
>> images/jpeg
>> images/png
>> images/tiff
>> images/svg
>> layout/block
>> layout/inline
>> layout/line
>> layout/page
>> renderer/afp
>> renderer/txt
>>
>> When you edit an existing issue, if its component contains "unqualified",
>> then please take the opportunity to review and preferably select a more
>> qualified component name. If you don't find a suitably named alternative,
>> then please suggest one to this list so I can add it.
>>
>> Note also, regarding the former "svg" component, I have relabeled that as
>> renderer/svg, which may not be appropriate depending on the issue. If the
>> issue is related to input from SVG (as opposed to output to SVG), then I
>> have created the images/svg component for the issues related to SVG input.
>>
>>
>>
>>
>



-- 
pascal

Re: JIRA Component Labels

[Glenn Adams <gl...@skynav.com>]

Additional minor changes:

fonts/* changed to font/*
images/* changed to image/*

Added:

foreign/barcode
foreign/svg

There are now 3 SVG components:

foreign/svg -  for SVG input via instream-foreign-object
image/svg - for SVG input via external-graphic
renderer/svg - for SVG output



On Tue, May 27, 2014 at 9:56 AM, Glenn Adams <gl...@skynav.com> wrote:

> I have long been unsatisfied with the set of component labels previously
> used with Bugzilla, which we inherited in JIRA. I've finally gotten around
> to relabeling many of the existing components and adding more specific
> components.
>
> I have relabeled as follows:
>
> awt renderer : renderer/awt
> fo tree : fo/unqualified
> fonts : fonts/unqualified
> general : unqualified
> images : images/unqualified
> page-master/layout : layout/unqualified
> pcl : renderer/pcl
> pdf : renderer/pdf
> ps : renderer/ps
> rtf : renderer/rtf
> svg : renderer/svg
>
> I have added the following:
>
> fo/block
> fo/inline
> fo/page
> fonts/opentype
> fonts/postscript
> images/jpeg
> images/png
> images/tiff
> images/svg
> layout/block
> layout/inline
> layout/line
> layout/page
> renderer/afp
> renderer/txt
>
> When you edit an existing issue, if its component contains "unqualified",
> then please take the opportunity to review and preferably select a more
> qualified component name. If you don't find a suitably named alternative,
> then please suggest one to this list so I can add it.
>
> Note also, regarding the former "svg" component, I have relabeled that as
> renderer/svg, which may not be appropriate depending on the issue. If the
> issue is related to input from SVG (as opposed to output to SVG), then I
> have created the images/svg component for the issues related to SVG input.
>
>
>
>
>