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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to