First for staring a software project a good thing is a list of needs. We can see if any other software can fill these needs or why they're failing to respond to them.
Needs should be in simple form.
I need a chat window.
I need multiple board.
I need secret cards for a players.
I need to have it run on multiple platform (PC, Mac, Palm, Nokia phones) ok just kidding.
Starting with this in a clean format we can collect them and later put them in a nice list. We could review them and decide of the most important one and the nice to have. If we keep the needs short and clean it will be easy to collect the information and compile it.
Have a good day.
Many of the required functionality of our product would be fairly stereotypic for any collaborative tool. These include:
(1) Ability to create project
(2) Ability for users to sign up, request membership, be assigned to roles within a project (~= "access control list")
(3) Ability to post rules (~= "documentation")
(4) Ability to post new graphics, cards, tiles (~= documents)
(5) Ability to automatically package latest version for download as PDF or other format, so people can test
(6) Version control
This is an incomplete list and represents extensive software "plumbing" that has been re-invented a thousand times over. As such, existing software should be leveraged to fulfill these more stereotyped & mundane tasks where possible.
So I suggest the scope of the "Let's Not Reinvent the Wheel" topic within this forum should expand to find open source, extensible collaborative systems we could leverage.
-Splunge