On 24 dec 2007, at 11:24, Martin Aspeli wrote:
Danny Bloemendaal wrote:
On 24 dec 2007, at 04:27, Hanno Schlichting wrote:
Danny Bloemendaal wrote:
After having waded through a big pile of plips I often (as a less
technical oriented member) had problems determining what the actual
usecase was that it was trying to solve. I would like to suggest
(when
thechcnically possible) to add such a section in a plip. I'd
like to see
a real-world usecase example (for the less technical ppl) what
the plip
has to solve/support/whatever.
Something like:
Suppose someone wants to write a product that supports this or
that.
Right now he has to do this or that to do this but with this plip
in
place he only has to do such or so.
Right now, the Motivation section isn't exactly that. In most
cases, the
author immediately dives into technical details.
I think it would help to have this addition? Or am I talking
nonsense here?
+1, I think we have been bad both on the side of use-case centric
and
integrator targeted information.
So what is needed? I think that only an extra header in the
boilerplate text for a plip would be enough (and stress that
writes fill it in of course).
I think this fits well inside the "Motivation" box we already have.
What's needed is a framework team that proactively asks people to
fill in that information when submitting PLIPs, should it be
insufficient.
I don't agree entirely. Motivation doesn't have to b a description for
the usecase. Motivation is very general and can be a technical story
only. A usecase is a 'normal'-people's description of what it tries to
solve. It's almost like a scenario or a scriptive way to describe
things. Motivation ís being used right now but hardly ever in the
scenario/use-case kinda way. I don't think it is good idea to
'correct' people if they didn't use Motivation is this way. It's
better to have them write it from the start.
Danny
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
