You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Roland Weber <RO...@de.ibm.com> on 2005/02/13 01:09:36 UTC
Wiki: Use Cases
Hello all,
as you have guessed from the Wiki messages,
I have set up a first take on pages for use cases:
a) RequestForUseCases
b) UseCaseTemplate
c) UseCases - list of use cases
d) UseCases/AccessURLs - example use case
We should have a discussion on these before hitting
the user list with an RfUC (Request for Use Cases).
I see the following topics for discussion, in order
of relevance:
1) procedure for new use cases (see a.2)
Should we encourage users to enter new use cases
directly in the wiki, or should we ask them to
always post them to the user mailing list first?
Posting first would help to avoid duplicates, but
it is a break of media. Users that browse from the
web page to the wiki could be discouraged by having
to subscribe to the mailing list.
2) template for use cases (see b,d)
3) wording of the RfUC (see a.1)
The first impression sticks...
4) categories for use cases (see c)
Easy to change, hence lowest importance.
What do you think?
cheers,
Roland
Re: Wiki: Use Cases
Posted by Roland Weber <RO...@de.ibm.com>.
Hi Oleg,
I do have a tendency for overdesigning :-) I'm probably looking
too much at where I want to get instead of where I start.
I fully agree that the template in it's current form will
discourage some people, just because of the size of it. On
the other hand, I like the idea of a fully structured collection
of use cases with all the stuff in the template.
It's somehow similar with the categories. Once we have over
200 use cases, we sure want some kind of structure in there.
I thought of the "Engineered Use Cases" as a place where I can
put some of the things I thought about when discussing the
HLCA :-)
And finally, I read that Wiki pages can not easily be deleted,
which makes me hesitant about redundant and nonsensical contributions.
So I see two possibilities:
1) forget about the fully structured collection
2) have a sandbox for easy submission of use cases, and a separate
fully structured collection maintained by volunteers that process
input from the sandbox and the mailing lists
Obviously, I would prefer the second choice. And I volunteer to
add some more fully structured use cases over time.
What do you (all) think?
cheers,
Roland
Oleg Kalnichevski <ol...@apache.org>
15.02.2005 21:57
Please respond to
"HttpClient Project"
To
HttpClient Project <ht...@jakarta.apache.org>
cc
Subject
Re: Wiki: Use Cases
Hi Roland,
Just a few thoughts about the new use case resources:
I think we should keep the entry barrier as low as possible. The users
should be able to type away in wiki without having to spend a good deal
of time studying the API redesign proposal or any other resources. I
would prefer to deal with 30% rate of completely nonsensical or
redundant postings rather end up with a few or none at all because
people gave up somewhere half way in the process. We ought to suggest a
structure but we should not insist on people strictly following it.
<http://wiki.apache.org/jakarta-httpclient/UseCases>
Do we really care if a use case falls into any of categories:
Application, Middleware, Engineered or anything else? Use cases can be
semi-structured or un-structured. Eventually the relevant data should
end up in Bugzilla/JIRA in a form of feature requests.
<http://wiki.apache.org/jakarta-httpclient/UseCases/AccessURLs>
This is terrific and very detailed stuff probably worth half a day of
work. I seriously doubt, though, we'll have many submissions of this
quality. We should be realistic and encourage simple postings along this
line: "Wouldn't it be cool if HttpClient 4.0 supported automatic
redirects on POST methods?"
> 1) procedure for new use cases (see a.2)
> Should we encourage users to enter new use cases
> directly in the wiki, or should we ask them to
> always post them to the user mailing list first?
>
The former in my opinion.
> Posting first would help to avoid duplicates, but
> it is a break of media. Users that browse from the
> web page to the wiki could be discouraged by having
> to subscribe to the mailing list.
>
> 2) template for use cases (see b,d)
Absolutely. Very simple and non-intrusive, though.
>
> 3) wording of the RfUC (see a.1)
> The first impression sticks...
>
Looks good to me
> 4) categories for use cases (see c)
> Easy to change, hence lowest importance.
>
See above
> What do you think?
>
You rock
> cheers,
> Roland
Cheers,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: Wiki: Use Cases Vol.2
Posted by Roland Weber <RO...@de.ibm.com>.
Hello all,
I have not gotten any feedback on the modified use case pages
in the Wiki. I hope that one or the other will find a few
minutes to have a look at them this weekend:
http://wiki.apache.org/jakarta-httpclient/RequestForUseCases
If I get feedback, I will incorporate it next week. If the pages
are ok as they are, could someone of the project team please open
the floodgates by posting a "Request for Use Cases" to the user
mailing list? I've been wiki-ing on private time, so I don't want
to post the RfUC from my corporate email account.
cheers,
Roland
Roland Weber/Germany/IBM@IBMDE
20.02.2005 10:21
Please respond to
"HttpClient Project"
To
"HttpClient Project" <ht...@jakarta.apache.org>
cc
Subject
Wiki: Use Cases Vol.2
Hello all,
since I didn't get any other feedback, I incorporated Oleg's
suggestions by creating a UseCases/SandBox where people can
easily add use cases without much ado. I put in two examples,
one directly in the sandbox and one as an extra page. Edwin,
thanks for your submission. The RequestForUseCases has become
simpler and there is a new SimpleUseCaseTemplate.
Please have a look at the pages and let me know what you think:
http://wiki.apache.org/jakarta-httpclient/RequestForUseCases
cheers,
Roland
Wiki: Use Cases Vol.2
Posted by Roland Weber <RO...@de.ibm.com>.
Hello all,
since I didn't get any other feedback, I incorporated Oleg's
suggestions by creating a UseCases/SandBox where people can
easily add use cases without much ado. I put in two examples,
one directly in the sandbox and one as an extra page. Edwin,
thanks for your submission. The RequestForUseCases has become
simpler and there is a new SimpleUseCaseTemplate.
Please have a look at the pages and let me know what you think:
http://wiki.apache.org/jakarta-httpclient/RequestForUseCases
cheers,
Roland
Re: Wiki: Use Cases
Posted by Oleg Kalnichevski <ol...@apache.org>.
Hi Roland,
Just a few thoughts about the new use case resources:
I think we should keep the entry barrier as low as possible. The users
should be able to type away in wiki without having to spend a good deal
of time studying the API redesign proposal or any other resources. I
would prefer to deal with 30% rate of completely nonsensical or
redundant postings rather end up with a few or none at all because
people gave up somewhere half way in the process. We ought to suggest a
structure but we should not insist on people strictly following it.
<http://wiki.apache.org/jakarta-httpclient/UseCases>
Do we really care if a use case falls into any of categories:
Application, Middleware, Engineered or anything else? Use cases can be
semi-structured or un-structured. Eventually the relevant data should
end up in Bugzilla/JIRA in a form of feature requests.
<http://wiki.apache.org/jakarta-httpclient/UseCases/AccessURLs>
This is terrific and very detailed stuff probably worth half a day of
work. I seriously doubt, though, we'll have many submissions of this
quality. We should be realistic and encourage simple postings along this
line: "Wouldn't it be cool if HttpClient 4.0 supported automatic
redirects on POST methods?"
> 1) procedure for new use cases (see a.2)
> Should we encourage users to enter new use cases
> directly in the wiki, or should we ask them to
> always post them to the user mailing list first?
>
The former in my opinion.
> Posting first would help to avoid duplicates, but
> it is a break of media. Users that browse from the
> web page to the wiki could be discouraged by having
> to subscribe to the mailing list.
>
> 2) template for use cases (see b,d)
Absolutely. Very simple and non-intrusive, though.
>
> 3) wording of the RfUC (see a.1)
> The first impression sticks...
>
Looks good to me
> 4) categories for use cases (see c)
> Easy to change, hence lowest importance.
>
See above
> What do you think?
>
You rock
> cheers,
> Roland
Cheers,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: Wiki: Use Cases
Posted by Oleg Kalnichevski <ol...@apache.org>.
Wow! This is massive. Roland, you rock! Let me chew on it for a couple
of days
Oleg
On Sun, 2005-02-13 at 01:09 +0100, Roland Weber wrote:
> Hello all,
>
> as you have guessed from the Wiki messages,
> I have set up a first take on pages for use cases:
>
> a) RequestForUseCases
> b) UseCaseTemplate
> c) UseCases - list of use cases
> d) UseCases/AccessURLs - example use case
>
> We should have a discussion on these before hitting
> the user list with an RfUC (Request for Use Cases).
> I see the following topics for discussion, in order
> of relevance:
>
> 1) procedure for new use cases (see a.2)
> Should we encourage users to enter new use cases
> directly in the wiki, or should we ask them to
> always post them to the user mailing list first?
>
> Posting first would help to avoid duplicates, but
> it is a break of media. Users that browse from the
> web page to the wiki could be discouraged by having
> to subscribe to the mailing list.
>
> 2) template for use cases (see b,d)
>
> 3) wording of the RfUC (see a.1)
> The first impression sticks...
>
> 4) categories for use cases (see c)
> Easy to change, hence lowest importance.
>
> What do you think?
>
> cheers,
> Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org