Mechanisms for the Transfer of Assets to SoylentNews PBC

From SoylentNews
Revision as of 16:13, 14 August 2014 by BlackHole (talk | contribs) (Created page with "==Introduction== SoylentNews PBC is off and running! We have incorporated, established the initial board of directors, held board meetings, elected officers, opened a bank acc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

SoylentNews PBC is off and running! We have incorporated, established the initial board of directors, held board meetings, elected officers, opened a bank account, and developed a plan for generating revenue. One task still remaining to place SoylentNews PBC on sound legal/financial footing is for the corporation to acquire certain important assets that are currently owned by private individuals. These assets include:

  • NCommander's property: Linode accounts, database, [please fill in], ...
  • matt_'s property: "SoylentNews.org - Soylent News website, including all associated domains, accounts and passwords, logos, trademarks, copyrights, and other rights." (This is the exact language in the purchase agreement with Barrabas).

This page is for discussion of the legal mechanisms that SoylentNews PBC could use to acquire these assets (or rights to these assets). Each option has advantages and drawbacks, but because everyone may not agree on whether certain features are advantages or drawbacks, they are listed simply as "Features" below. The options are listed roughly in order of the number of pages of legalese involved :-)

Transfer Mechanisms

Not doing anything (included for completeness)

  • Feature:

Assignment in connection with the issuance of common stock

  • Feature:

Assignment in connection with the issuance of an unsecured debt instrument (e.g., a corporate bond)

  • Feature:

Assignment in connection with the issuance of an unsecured convertible debt instrument (e.g., a convertible note)

  • Feature:

License, subject to the terms of a licensing agreement

  • Feature: