Project Issues

From PalOMoney
Revision as of 20:00, 14 January 2013 by Admin (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Issues to Be Resolved Pre Testing

The following issues need resolution prior to releasing a build for testing.

Title Priority Difficulty Description
Tester's Agreement high medium Legal: Is the agreement sufficient?
Can the agreement be simplified?


Pre Marketing Issues

The following issues need resolution prior to releasing a build for sale.

Title Priority Difficulty Description
Microsoft Licensing Restrictions medium medium We don't expect Microsoft or a successor to the Money product line be content or continue to supply a product that has restored functionality without compensation. What could that arrangement be? What about replacing key Microsoft Money components, is there some problem with that? We will need some expert opinions on this topic -- see the forum.
Other Licensing Requirements medium medium What, if any, licenses have to be obtained and documented in order to comply with license requirements.


Other Development Issues

  • How can further internal development be funded?
  • How can outside developers get involved and compensated?
  • How can the interfaces to open source projects be improved (not to mention that the one existing interface needs to be fixed)?


Resolved Issues

Title Priority Difficulty Description
Debug Build Release Requirements high medium What is required to release a debug build for testing? How is the tester made part of the development process? Is a non-disclosure agreement required? How to verify the license agreement, especially the part that holds the developers harmless in the event of a disaster? Does this require "employment" in any sense? What is the criteria for verifying a tester's identity? Possibilities range from email verification to a nominal credit card charge? Would such a charge trigger any product liability or other obligation?