Assigning Assets

Title: Assigning Assets
DRACC: 0014
Category: Regulatory
Scope: Global
Authors: Leenaars, M.A.G.J.; Šuklje, M.
Date: January 2017
Copyright: The Commons Conservancy

This doc­u­ment is part of the DRACC se­ries, see DRACC “In­tro­duc­tion to ­DRACC Se­ries” for an ex­pla­na­tion. You can re­use it un­der a “Cre­ative ­Com­mons At­tri­bu­tion 4.0 In­ter­na­tion­al” li­cense.

Assigning Assets

There are two rea­sons why a con­trib­u­tor would like to leave the full rights in­ their con­tri­bu­tion to [The Com­mons Con­ser­van­cy] — a) be­cause a Pro­gram­me re­quires the trans­fer of as­set­s; or b) due to the con­trib­u­tor’s own de­sire to as­sign their rights to [The Com­mons Con­ser­van­cy]. In both cas­es this doc­u­men­t pre­scribes the pro­ce­dure which is to be fol­lowed.

If a Pro­gramme re­quires in­tan­gi­ble as­sets — such as copy­right, trade mark­s, ­patents, databas­es, in­te­grat­ed cir­cuit lay­out de­sign and the like — to be as­signed to [The Com­mons Con­ser­van­cy], be­fore a con­trib­u­tor con­trib­utes to the Pro­gram­me, the con­trib­u­tors MUST sign a le­gal doc­u­ment for such trans­fer of ­such as­sets (see DRACC “Le­gal Doc­u­ment Whitelist”) with [The Com­mon­s ­Con­ser­van­cy].

Even if a Pro­gramme does not re­quire such trans­fer, a con­trib­u­tor MAY stil­l as­sign the in­tan­gi­ble as­sets — such as copy­right, trade mark­s, patents, ­databas­es, in­te­grat­ed cir­cuit lay­out de­sign and the like — in their ­con­tri­bu­tion(s) to [The Com­mons Con­ser­van­cy].

In both cas­es the fol­low­ing pro­ce­dure MUST be fol­lowed:

Manual Procedure

  1. The con­trib­u­tor SHALL send elec­tron­i­cal­ly (for in­stance by email) to the Board of [The Com­mons Con­ser­van­cy] a prop­er­ly filled out and signed legal ­doc­u­ment (see DRACC “Le­gal Doc­u­ment Whitelist”) need­ed for the as­set ­trans­fer. Said le­gal doc­u­ment SHALL al­so state ei­ther a) which Pro­gram­me(s) the as­sets SHOULD go to, or al­ter­na­tive­ly b) whether they SHALL go di­rect­ly ­to [The Com­mons Con­ser­van­cy] to be used by any Pro­gramme that might find­ them use­ful (see DRACC “Map­ping Rights to Pro­grammes”).
  2. The Board of [The Com­mons Con­ser­van­cy] SHALL ask all rel­e­vant Pro­grammes that were list­ed in the pre­vi­ous step as Pro­grammes the as­sets SHOULD go to, ­to de­cide whether they ac­cept the con­tri­bu­tion (see DRACC “De­ci­sion Han­dling Pro­ce­dure”).
  3. Un­less there is a time­ly op­po­si­tion from any of the rel­e­vant Pro­grammes, the Board of [The Com­mons Con­ser­van­cy] SHALL no­ti­fy the con­trib­u­tor and ­Gov­ern­ing Bod­ies of the rel­e­vant Pro­grammes that it ac­cepts the do­na­tion of in­tan­gi­ble as­sets and which Pro­grammes MAY ac­cess these as­set­s. If any of the Gov­ern­ing Bod­ies ob­ject­s, the as­sets SHALL not be shared on­ly with that spe­cif­ic Pro­gramme.

Third-Party Materials

If a con­tri­bu­tion con­tains any third-­par­ty ma­te­ri­al(s) (e.g. li­braries or snip­pet­s ­tak­en else­where), the con­trib­u­tor SHALL for each ma­te­ri­al:

  1. en­sure that they have the nec­es­sary rights to con­trib­ute said ma­te­ri­al to the Pro­gram­me(s) and that its li­cences are com­pat­i­ble with the out­bound­ li­cence of the Pro­gram­me(s); and
  2. en­ter it in­to the Bill of Third-­Par­ty Ma­te­ri­al­s, which MUST be de­posit­ed with [The Com­mons Con­ser­van­cy].

[The Com­mons Con­ser­van­cy] SHALL keep an ar­chive of all here­in men­tioned ­doc­u­ments.