Hi karl

I think that the solution would be to use seaside + mewa to have a 
scriptable (from squeak)
web bug tracking systems.

We discussed a lot with marcus and parsing emails does not really scale 
in the long term.
We could image that this seaside server could handle something else 
than emails and still
have BFAV working on these other formats (ok this is a big change)

Look at Mantis to see what infomration we really need to track bugs.

Stef


On 3 oct. 04, at 14:38, karl.ramberg at chello.se wrote:

> danielv at tx.technion.ac.il wrote:
>
>> Yes, yes, Stef was far too ambivalent. We need to *decide* what system
>> is used for what.
>>
>> So if anyone thinks the policy should be different from the below, 
>> argue
>> for it.
>>
>> AFAIK, nobody has currently said that he is harvesting bug *fixes* 
>> from
>> mantis, which implies that bugfixes and enh are posted to and handled 
>> by
>> the BFAV, since that's what the harvesters currently use.
>>
>> We don't really do bug tracking on the BFAV, and Mantis might be
>> actually useful for that, so post *bugs* to Mantis.
>
> Could someone make up a list of what BFAV needs to be used
> as a bug tracker?
> Maybe it's not that hard to add those features.
> As a start I have added a bug tab, it's in the development version at
> SqueakSource.
> Karl
>