Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copyright on source in Gitea #126

Closed
joubertredrat opened this issue Nov 9, 2016 · 6 comments
Closed

Copyright on source in Gitea #126

joubertredrat opened this issue Nov 9, 2016 · 6 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@joubertredrat
Copy link
Contributor

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

@bkcsoft
Copy link
Member

bkcsoft commented Nov 9, 2016

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

@lunny
Copy link
Member

lunny commented Nov 10, 2016

^, please see CONTRIBUTING

@joubertredrat
Copy link
Contributor Author

@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.

@strk
Copy link
Member

strk commented 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

@lunny
Copy link
Member

lunny commented Nov 10, 2016

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

@tboerger tboerger added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Nov 11, 2016
@tboerger
Copy link
Member

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

lunny pushed a commit to lunny/gitea that referenced this issue Feb 7, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
6543 pushed a commit to 6543-forks/gitea that referenced this issue Feb 26, 2024
Adds a new `/{username}/{repo}/badges` family of routes, which redirect
to various shields.io badges. The goal is to not reimplement badge
generation, and delegate it to shields.io (or a similar service), which
are already used by many. This way, we get all the goodies that come
with it: different styles, colors, logos, you name it.

So these routes are just thin wrappers around shields.io that make it
easier to display the information we want. The URL is configurable via
`app.ini`, and is templatable, allowing to use alternative badge
generator services with slightly different URL patterns.

Additionally, for compatibility with GitHub, there's an
`/{username}/{repo}/actions/workflows/{workflow_file}/badge.svg` route
that works much the same way as on GitHub. Change the hostname in the
URL, and done.

Fixes gitea#5633, gitea#23688, and also fixes go-gitea#126.

Work sponsored by Codeberg e.V.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit fcd0f61212d8febd4bdfc27e61a4e13cbdd16d49)
(cherry picked from commit 20d14f784490a880c51ca0f0a6a5988a01887635)
(cherry picked from commit 4359741431bb39de4cf24de8b0cfb513f5233f55)
(cherry picked from commit 35cff45eb86177e750cd22e82a201880a5efe045)
(cherry picked from commit 2fc0d0b8a302d24177a00ab48b42ce083b52e506)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

5 participants