Difference between revisions of "Project Issues"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| − | <td width="23%">[[ | + | <td width="23%">[[Tester's Agreement]]</td> |
<td width="12%">high</td> | <td width="12%">high</td> | ||
<td width="12%">medium</td> | <td width="12%">medium</td> | ||
| − | <td width="69%"> | + | <td width="69%">Legal: Is the agreement sufficient?<br>Can the agreement be simplified?</td> |
| − | + | </tr> | |
| + | </table> | ||
| + | |||
| + | |||
| + | == Pre Marketing Issues == | ||
| + | |||
| + | <p>The following issues need resolution prior to releasing a build for sale.</p> | ||
| + | <table border="1" width="100%" style="font-size: 10pt; font-family: Arial"> | ||
| + | <tr> | ||
| + | <td width="23%">Title</td> | ||
| + | <td width="12%">Priority</td> | ||
| + | <td width="12%">Difficulty</td> | ||
| + | <td width="69%">Description</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| Line 29: | Line 41: | ||
</tr> | </tr> | ||
</table> | </table> | ||
| + | |||
== Other Development Issues == | == Other Development Issues == | ||
| Line 35: | Line 48: | ||
* How can outside developers get involved and compensated? | * 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)? | * How can the interfaces to open source projects be improved (not to mention that the one existing interface needs to be fixed)? | ||
| + | |||
| + | |||
| + | == Resolved Issues == | ||
| + | |||
| + | <table border="1" width="100%" style="font-size: 10pt; font-family: Arial"> | ||
| + | <tr> | ||
| + | <td width="23%">Title</td> | ||
| + | <td width="12%">Priority</td> | ||
| + | <td width="12%">Difficulty</td> | ||
| + | <td width="69%">Description</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td width="23%">[[Debug Build Release Requirements]]</td> | ||
| + | <td width="12%">high</td> | ||
| + | <td width="12%">medium</td> | ||
| + | <td width="69%">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?</td> | ||
| + | </tr> | ||
| + | </table> | ||
Latest revision as of 20:00, 14 January 2013
Contents
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? |
