[schooltool-dev] Re: blueprints and bugs

[Tom Hoffman]

On 9/13/07, Tom Hoffman <tom.hoffman at gmail.com> wrote:
> I've gone through the bugs in Malone and the specs in Blueprint (both
> on Launchpad), trying to keep things relatively up to date.
>
> One confusing point is the difference between a "wishlist" bug and a
> specification.
>
> Right now, there are a few very simple Blueprints, like this one:
>
> Group field in new person screen should be set to "Students" by
> default. The large majority of "Persons" inside SchoolTool are
> students, so having the Group drop down dialog preset to Student will
> speed data entry.
>
> Something like this, which can easily be entered in a textbox and
> doesn't require much discussion other than "yes" or "no," probably
> fits better as a wishlist bug than a blueprint, so I'm moving it and a
> couple other things to Malone and marking them as 'superceded.'
>
> I'd say that we should only use blueprints for things that take a
> fairly detailed description and some active discussion to refine.
> Also we should try to divide up the blueprints into moderately sized
> chunks.  Each blueprint should represent in the neighborhood of 1
> developer week's work.

Actually, upon thinking about this a little more, a blueprint might be
something like "Speeding up student entry," and would include a
discussion of various ways to do that.  If you're suggesting a single
and straightforward implementation, that's a wishlist bug.

--Tom