Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Sun, 21 Feb 2016 12:23:18 +0000 (UTC)
From: =?utf-8?Q?Alexander_G=C3=B6dde_=28JIRA=29?= <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.12938511.1455198459000.103978.1456057398058@Atlassian.JIRA>
In-Reply-To: <JIRA.12938511.1455198459000@Atlassian.JIRA>
References: <JIRA.12938511.1455198459000@Atlassian.JIRA>
 <JIRA.12938511.1455198459584@arcas>
Subject: [jira] [Reopened] (LEGAL-233) US registration of copyright for
 projects hosted publicly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/LEGAL-233?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander G=C3=B6dde reopened LEGAL-233:
-----------------------------------

I think this is an important question - see my comment on the issue.

> US registration of copyright for projects hosted publicly
> ---------------------------------------------------------
>
>                 Key: LEGAL-233
>                 URL: https://issues.apache.org/jira/browse/LEGAL-233
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Alexander G=C3=B6dde
>
> I'm working for a company which maintains an open source project (AGPL v3=
, but the question I have applies independent of the specific license). Cop=
yright in the source code is assigned by all contributers to the company (v=
ia a Project Harmony-based CAA).
> The project is hosted on GitHub.
> In order to effectively assert the copyright against infringers in the US=
, registration may be required in principle (if this is seen as a US work, =
which is a possibility with it being hosted on GitHub) and is required for =
claiming statutory damages (which are a pretty good deterrent).
> But how does one register the copyright in a software hosted publicly?
> The initial registration is unproblematic (though the process the US copy=
right office is ridiculous).
> My problem is the constant stream of commits:
> If the fact that the software is accessible after each commit constitutes=
 publication, then I would need to register each commit since the US copyri=
ght office states that after initial registration only the difference betwe=
en two commits can be registered.
> How do the Apache foundation projects handle US copyright registration in=
 practice?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org