Well, since I seem to have left the window open, causing an apparent
chill here...
What I would suggest:
Try to focus the target a bit more - going from SOHO to Multi-National
Enterprise for a target audience is rather daunting.
Create a high level project plan and publish it. I'm not talking about
gantt charts and Work Break Down structures an such, more of a road map.
If it is to be a set of modules, can they be used separately? Which
module comes first?
Look at the types of issues you will need to deal with from a user
functionality perspective.
Look at what needs to be put in place, maybe there will be some set of
functions that will cross modules and these functions would best be put
into a library.
With that in place you can update the road map. Have items that people
can look at and say - I could help with that piece.
Don't hesitate to ask questions - people volunteer more readily when the
task is well defined.
I suppose what I am saying is this - If you ask on an open list such as
this, "Who would like to help write an Accounts payable module?", you
are not likely to get a lot of takers. However if you say, "For the
Accounts Payable module being worked on there is problem XXXX that I
need help solving, can anyone help?", you are likely to get responses.
It is much easier for folks to look at XXX and say, yes I have a couple
of hours I can spare to look at this, or even "This is how I did it for
a project in the past".
Anyway - those are just some personal thoughts on the subject.
--
OpenOffice.org User Community Forum: http://user.services.openoffice.org
United States PostgreSQL Association: http://www.postgresql.us/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
