Public SourceMage Discussion List

[Jaka Kranjc <lynx AT mages.ath.cx>]

On Saturday 21 October 2006 17:58, Eric Sandall wrote:
> Jaka Kranjc wrote:
> <snip>
>
> > I have a suggestion. Let 5 of those (say) 20 be feature bugs. Not as in
> > wishlist feature requests, but bugs on the same topic, technology. It
> > would force us to learn new things and know what is available better.
> >
> > Examples:
> > * convert a spell to build_api2
> > * remove one $SPELL_CONFIG usage in favour of config_query and persistent
> > variables
> > * use a repair file
> > * use upstream signature/hash
> > * patching
> > * use a trigger
> > * implement a subdep call
> > * new spell (something from the 100 submissions in the bt)
> > ...
> >
> > So some bitderot duties and technology applications. Most of the examples
> > I thought of, have such bugs or needs already available.
>
> Those are 'normal' bugs to me and so would be valid (and need bugs
> failed if not already). A 'feature' bug would, to me, be "allow xorg to
> build XGL support" or "add my cool spell XyZ".
>
> -sandalle
let me repeat:
> > I have a suggestion. Let 5 of those (say) 20 be feature bugs. Not as in
> > wishlist feature requests, but bugs on the same topic, technology. It
> > would force us to learn new things and know what is available better.

I didn't say they would be invalid otherwise, you're missing the educational 
point here.

-- 
We cannot command nature except by obeying her.  --Sir Francis Bacon
Have a sourcerous day! www.sourcemage.org

Attachment: pgpuKE_24nY4A.pgp
Description: PGP signature