I'm a big fan of Plan B. Though Plan C comes in a close second. I have some webspace available and can host mailing lists. I would also be willing to help with coordination and other none coding aspects. Once we get going, maybe we could have a job listing section where people can sign up for open needed tasks.
This fits perfectly into my previous proposal. I am all for it.
I think this should be considered for the whole project. The smallest unit should not be a person, but a team. You know you're gonna curse yourself if the guy who has done 50% of the work on some huge component looses interest and moves on (or even worse, gets pissed at me for something I say and deletes all his sources/references/docs just to spite us ;-) )
All the key postions should have a deputy/second that can filling or replace them permanently or temporarily. Everything else should be broken down in to managable chunks that can be worked on my workgroups of 2 or 3 people. Were you thinking of something like that?
Yes. (or 4)
I'd like to take the first step to ask someone to arrange an IRC conference to discuss the basic organisation structure. We've to setup a executive board ASAP to contact OpenOffice.org officially and work out the details etc. (see also the discussion about the name here). I'd like to be part of that discussion, if possible. I'd reccomend a time around 8:00 am US Mountain time ( this is about -8 hours CET, don't know what thime this is in Austriala/Asia). Should be around max 1 hour. If someone can set something up, that would be fine. Maybe with an announcement thru aw or aw-dev site.