Use Cases & Feature Requests

[Arved Sandstrom <Ar...@chebucto.ns.ca>]

Hi, folks

In one form or another we get feature requests now - people ask why feature 
X is not implemented, or when it will be implemented, or whether it's 
implemented, and we can logically surmise that this is a desired feature. :-)

But this all arrives in a fairly haphazard and disjointed fashion. It's hard 
for us to piece together a picture of what are the most important features. 
All of you who are programmers know that just a list of rquirements is not 
enough - you also want to have priorities: is this a "1"? Is that a "3"? Is 
this "must-have" or is it "optional"?

So, what I'd like to request is this. If you can or want, please provide a 
prioritized list of features that you consider important. These can be 
features that are already in place, or unimplemented ones. Bear in mind that 
because of refactoring, implemented features could get bashed around a bit 
(which you have already seen), so if it is important to you that feature 
such-and-such doesn't get this kind of treatment, or is broken for as short 
a period of time as possible, include that feature in your list.

The ranking scale isn't overly important - use a scale of 1-5, with 1 being 
the most important, if you like, or rate your features as "must have", 
"important", "nice to have", or anything that makes sense to all of us.
Please label the post as being a FEATURE LIST or something similar.

If you can provide use-cases at the same time, "e.g. we are doing business 
forms, and use the following features, with these categories of 
importance...", that would be even better.

There is no urgency. Obviously the more of these we have the better it will 
be for all concerned, I believe. It's easier for us to look at a bug with a 
user-specified severity and urgency in the defect tracking, and assess it, 
if we have a bigger picture and more context for FOP usage and wish-lists.

Thanks for your help.

Regards,
Arved Sandstrom

Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org

Re: Use Cases & Feature Requests

[Alex McLintock <al...@yahoo.com>]

--- Arved Sandstrom <Ar...@chebucto.ns.ca> wrote: > Hi, folks
> 
> In one form or another we get feature requests now - people ask why feature 
> X is not implemented, or when it will be implemented, or whether it's 
> implemented, and we can logically surmise that this is a desired feature. :-)
> > 
> So, what I'd like to request is this. If you can or want, please provide a 
> prioritized list of features that you consider important. 

I'd offer the FAQ for collating and disseminating this information except I seem
to have broken the user system in it - in a totally different way to the 
official apache.org FAQ.

    http://www.OWAL.co.uk:8090/asf/fop.jsp

Alex


=====
Alex McLintock        alex@OWAL.co.uk

OpenWeb Analysts Ltd, http://www.OWAL.co.uk/
Software for Complex Websites.

Publisher of       http://www.DiverseBooks.com
                   http://www.galactic-guide.com/

__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/?.refer=text

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org