Open Source Applications Foundation

[Design] Wiki organization for parcels

Greg Noel Fri, 28 Feb 2003 16:01:12 -0800


On Friday, Feb 28, 2003, at 11:41 US/Pacific, Kaitlin Duck Sherwood 
wrote:

> My second-highest priority is getting competitive analysis information 
> ready for our marketing guy.  I believe that he doesn't need a whole 
> lot of detail and I'm not sure he cares about the more obscure clients 
> (e.g. TheBat!).

Hmmm...  I got to thinking about this after I cautioned you that the 
basis and the context should be separate is that the marketing guy is 
only really interested in negative comparisons (places where Chandler 
does better) while designers are more interested in positive features 
(good ideas or capabilities).  I, for one, would not like to lose any 
good ideas embodied in TheBat!, so it could make sense to put the 
positive aspects even for obscure competitors in with the features list 
and the negative aspects in with the competitive analysis.

> Except that EmailRequirements is the parent or grandparent to lots of 
> pages... so there's still the name-change problem.  It's still a PITA 
> today, maybe it won't be next week.

What I meant was that you could start working on it today under its 
current name, so that that anyone who happened to have a handle on the 
page (because they'd found it via a search, for example {;-}) could 
still look at it and even offer suggestions...

Once the bug was fixed, it could still be moved to the correct name, 
but the content would already be in place, so you'd save some time.

> *Laugh*    Do me a favor and promise to nag me fiercely starting next 
> Friday if I don't release the EmailRequirements page.  That'll help to 
> motivate me.

OK, it's Friday; nag, Nag, NAG!

Oh, you meant Friday the 7th of March.  Well, in that case, I may start 
nagging a couple of days early and insist that you give me a birthday 
present...

BTW, "Requirements" is not a good word choice, since it tends to imply 
a commitment, even if minor, to implementing it.  A more neutral word 
like "Features" or "Scope" (or even "Basis") would be better.

Hope this helps,
-- Greg Noel, retired UNIX guru