StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
683135
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-25T19:44:55.843
FavoriteCount
0
LastActivityDate
2009-03-25T19:44:55.843
LastEditDate
LastEditorUserId
0
OwnerUserId
1050
ParentId
676610
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
<ol> <li>What should I charge? Ultimately you have to arrive at a figure you both can live with. Start by asking what value the buyer will derive from using your product as a guide. It's probably more than you think.</li> <li>What does a commercial software license look like? It says whatever you want it to say, plus a bunch of standard legal boiler plate. As others have said, find a lawyer that specialises in software IP. Ask questions, If they keep saying they have to research it, it's probably a sign to look for another lawyer. Before you go to a lawyer have a clear idea about your goals. Here's a few things to think about: <ul> <li>what do you want to give the other party. What/how can they use your product.</li> <li>limitation of liability</li> <li>warranty. What warranty do you want to give</li> <li>support. What support will you provide. Costs.</li> <li>termination. How will the licence terminate and what will happen when it does</li> <li>intellectual property. Who owns what</li> <li>how will disputes be resolved</li> <li>assignment. Can they other part assign the agreement to someone else. If so under what conditions</li> </ul></li> <li>How do I protect my work? If you can't trust the other party you probably shouldn't do it. As Aaron said "If you can trust someone, you don't need a contract. If you can't trust them, a contract won't save you." You can write all the contracts and licences that you want, but if it goes wrong, litigating it is a painful business. Best not get in that position in the first place, or at least make sure the potential gains offset the risks.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat do I need to know before I sell a software license?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJohn Mac
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhat do I need to know before I sell a software license?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.