[Swoop] Swoop Day Agenda: meeting 10:30 in MIND on Fri

[Bijan Parsia]

Clearly, I'm running late.

On Oct 1, 2004, at 2:18 AM, Aditya Kalyanpur wrote:

> ok, so we have a Swoop day planned: 10:30am Fri (Oct 1) in MIND..I
> guess we could work till about 1, take a break for lunch followed by
> the group meeting, and probably resume after the meeting depending on
> progress made and enthu left:)
>
> hmm, ppl planing to attend based on the e-mail responses:
> certain: Evren, Bijan, Bernardo

Turns out to be not so certain.

> maybe: DHewlett, Vladimir
> + whoever else is interested
>
> agenda (not sure abt time to spend on each)
> 1. do a quick code orientation again - most of you are familiar with
> the architecture, core components etc anyway, just need to bring you
> up to date with the latest changes in the code leading to the first
> beta release of 2.2 this week
>
> 2. roundup of current known bugs/issues - in some cases, we may need
> to refactor some code (esp. progress bar related threaded
> stuff)...there's plenty to do here (i'm maintaining a list) and im
> sure we'll discover new bugs tomorrow
>
> 3. it would be nice if as a follow up to 2, we could come up with some
> sort of regression tests to help us verify code in the future

This is a HUGE job, and ongoing!

> 4. finally, sort out the list of features to be implemented next: some
> of them are high priority and should be there in the next release,
> others can be put off till later, so basically we need to:
> - decide which features are high priority
> - come up with just a basic plan of how to implement the features (no
> coding yet)
> - divide and share the work depending on ppl's interests

Well, I sorta thought you'd already have this, but ok. I'll come bitch 
about these :)

> if anyone wants to add anything else , feel free..but IMHO the main
> point of the meeting is debugging..cos we need to get Swoop stable
> before we start putting in any more features, otherwise it'll be one
> big soupy mess:\

No, a *woopy* mess.

SOUP (Single Ontologies Understood Poorly) is another tool.

Cheers,
Bijan.