Copyright on source in Gitea #48

New Issue

GiteaMirror · 2025-11-02T03:05:57-06:00

GiteaMirror commented

2025-11-02 03:05:57 -06:00

Originally created by @joubertredrat on GitHub (Nov 9, 2016).

Hi guys,

Gitea is fork from Gogs and we need to respect this, but, the plan is make this as independent fork, then, we need to copyright us too. In PHP project we refer to the old contributors, but also the new ones on comments.

The question is, we will add new copyright on comments as example or not?

// Copyright 2014-2016 The Gogs Authors. All rights reserved.
// Copyright 2016-2016 The Gogs and Gitea Authors. All rights reserved.
// Use of this source code is governed by a MIT-style
// license that can be found in the LICENSE file.

Let's talk

Originally created by @joubertredrat on GitHub (Nov 9, 2016). Hi guys, Gitea is fork from Gogs and we need to respect this, but, the plan is make this as independent fork, then, we need to copyright us too. In PHP project we refer to the old contributors, but also the new ones on comments. The question is, we will add new copyright on comments as example or not? ``` // Copyright 2014-2016 The Gogs Authors. All rights reserved. // Copyright 2016-2016 The Gogs and Gitea Authors. All rights reserved. // Use of this source code is governed by a MIT-style // license that can be found in the LICENSE file. ``` Let's talk

GiteaMirror added the type/question label 2025-11-02 03:05:57 -06:00

GiteaMirror closed this issue

2025-11-02 03:05:57 -06:00

GiteaMirror commented

2025-11-02 03:05:58 -06:00

@bkcsoft commented on GitHub (Nov 9, 2016):

GiteaMirror commented

2025-11-02 03:05:58 -06:00

@lunny commented on GitHub (Nov 10, 2016):

^, please see CONTRIBUTING

@lunny commented on GitHub (Nov 10, 2016): ^, please see [CONTRIBUTING](CONTRIBUTING.md)

GiteaMirror commented

2025-11-02 03:05:58 -06:00

@joubertredrat commented on GitHub (Nov 10, 2016):

@lunny I saw here, but in my opinion, this section isn't clear enough. Only saw how comments need to be, don't talk if is to add our copyright or replace original copyright by our. Because this my question.

For me, we need to add our copyright on files changed and preserve original, like @bkcsoft saw.

// Copyright 2014-2016 The Gogs Authors. All rights reserved.
// Copyright (c) 2016 The Gitea Authors
// Use of this source code is governed by a MIT-style
// license that can be found in the LICENSE file.

@joubertredrat commented on GitHub (Nov 10, 2016): @lunny I saw here, but in my opinion, this section isn't clear enough. Only saw how comments need to be, don't talk if is to add our copyright or replace original copyright by our. Because this my question. For me, we need to add our copyright on files changed and preserve original, like @bkcsoft saw. ``` // Copyright 2014-2016 The Gogs Authors. All rights reserved. // Copyright (c) 2016 The Gitea Authors // Use of this source code is governed by a MIT-style // license that can be found in the LICENSE file. ```

GiteaMirror commented

2025-11-02 03:05:58 -06:00

@strk commented on GitHub (Nov 10, 2016):

On Wed, Nov 09, 2016 at 09:15:17AM -0800, bkcsoft wrote:

Files that are changed should add a line above saying // Copyright (c) 2016 The Gitea Authors :)

+1

@strk commented on GitHub (Nov 10, 2016): On Wed, Nov 09, 2016 at 09:15:17AM -0800, bkcsoft wrote: > Files that are _changed_ should **add** a line _above_ saying `// Copyright (c) 2016 The Gitea Authors` :) +1

GiteaMirror commented

2025-11-02 03:05:58 -06:00

@lunny commented on GitHub (Nov 10, 2016):

If you thinks it's not clear, send a PR to change the CONTRIBUTING. And the owners should review it .

@lunny commented on GitHub (Nov 10, 2016): If you thinks it's not clear, send a PR to change the CONTRIBUTING. And the owners should review it .

GiteaMirror commented

2025-11-02 03:05:59 -06:00

@tboerger commented on GitHub (Nov 11, 2016):

Question is answered, we add the Gitea copyright to files we are changing.

@tboerger commented on GitHub (Nov 11, 2016): Question is answered, we add the Gitea copyright to files we are changing.

GiteaMirror referenced this issue

2025-11-02 11:39:07 -06:00