Browse Source

Initial commit

Thomas Boerger 3 years ago
No known key found for this signature in database GPG Key ID: 5A388F55283960B6
23 changed files with 508 additions and 0 deletions
  1. +17
  2. +1
  3. +28
  4. +0
  5. +0
  6. +2
  7. +127
  8. +9
  9. +36
  10. +202
  11. +10
  12. +23
  13. +7
  14. +3
  15. +7
  16. +2
  17. +23
  18. +0
  19. +1
  20. BIN
  21. +0
  22. +0
  23. +10

+ 17
- 0
.drone.yml View File

@@ -0,0 +1,17 @@
path: src

image: plugins/downstream
- go-gitea/website
- go-gitea/blog
- go-gitea/docs
- go-gitea/redirects
event: push
branch: master

image: plugins/gitter

+ 1
- 0
.drone.yml.sig View File

@@ -0,0 +1 @@

+ 28
- 0
.editorconfig View File

@@ -0,0 +1,28 @@

root = true

charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true

indent_style = tab
indent_size = 4

indent_style = tab
indent_size = 2

indent_style = tab

indent_style = space
indent_size = 2

indent_style = space
indent_size = 4

+ 0
- 0
.github/ View File

+ 0
- 0
.github/ View File

+ 2
- 0
.lgtm View File

@@ -0,0 +1,2 @@
self_approval_off = false
ignore_maintainers_file = true

+ 127
- 0 View File

@@ -0,0 +1,127 @@
# Contribution Guidelines

## Introduction

This document explains how to contribute changes to the Gitea project.
It assumes you have followed the
[installation instructions](

Sensitive security-related issues should be reported to [](

## Bug reports

Please search the issues on the issue tracker with a variety of keywords to
ensure your bug is not already reported.

If unique, [open an issue](
and answer the questions so we can understand and reproduce the problematic

The burden is on you to convince us that it is actually a bug in Gitea. This
is easiest to do when you write clear, concise instructions so we can reproduce
the behavior (even if it seems obvious). The more detailed and specific you are,
the faster we will be able to help you. Check out
[How to Report Bugs Effectively](

Please be kind, remember that Gitea comes at no cost to you, and you're
getting free help.

## Discuss your design

The project welcomes submissions but please let everyone know what
you're working on if you want to change or add something to the Gitea repositories.

Before starting to write something new for the Gitea project,
please [file an issue](
Significant changes must go through the
[change proposal process](
before they can be accepted.

This process gives everyone a chance to validate the design,
helps prevent duplication of effort,
and ensures that the idea fits inside the goals for the project and tools.
It also checks that the design is sound before code is written;
the code review tool is not the place for high-level discussions.

## Testing redux

Before sending code out for review, run all the tests for the whole
tree to make sure the changes don't break other usage and keep the compatibility on upgrade:

After running for a while, the command should print


## Code review

Changes to Gitea must be reviewed before they are accepted,
no matter who makes the change even if an owners or a maintainer.
We use github's pull request workflow to do that and use [lgtm]( to ensure every PR is reviewed by at least 2 maintainers.

## Sign your work

The sign-off is a simple line at the end of the explanation for the patch. Your
signature certifies that you wrote the patch or otherwise have the right to pass
it on as an open-source patch. The rules are pretty simple: If you can certify
[DCO](DCO), then you just add a line to every git commit message:

Signed-off-by: Joe Smith <>

Please use your real name, we really dislike pseudonyms or anonymous
contributions. We are in the opensource world without secrets. If you set your
`` and `` git configs, you can sign your commit automatically
with `git commit -s`.

## Contributors

Everyone who sent a PR to Gitea that gets accepted will be as a contributor. Please send a PR to add your name to

## Maintainers

To make sure every PR have been checked, we make a team maintainers. Any PR MUST be reviewed and by at least two maintainers before it can get merged.
Maintainers should be a contributor of gitea(or gogs) and contributed at least 4 accepted PRs. And a contributor should apply as a maintainer in [gitter Gitea develop](
And the owners or the team maintainer could invite the contributor. A maintainer should spend some time on code reviews. If some maintainer have no time
to do that, he should apply to leave maintainers team and we will give him an honor to be as a member of advisor team. Of course, if an advisor have time to code view, welcome it back to maintainers team.
If some one have no time to code view and forget to leave the maintainers, the owners have the power to move him from maintainers team to advisors team.

## Owners

Since Gitea is a pure community organization without any company support, to keep the development healthly We will elect the owners every year. Every time we will elect three owners.
All the contributers could vote for three owners, one is the main owner, the other two are assistant owners. When the new owners have been elected, the old owners MUST move the power to the new owners.
If some owner don't obey these rules, the other owners are allowed to revoke his owner status.

After the election, the new owners should say he agrees with these rules on the [CONTRIBUTING]( on the [Gitter Gitea Channel]( Below is the word to speak

I'm glad to be an owner of Gitea, I agree with [CONTRIBUTING]( I will spend part of my time on gitea and lead the development of gitea.

For a honor to the owners, this document will add the history owners below:

2016-11-04 ~ 2017-12-31 lunny <> tboerger <> bkcsoft <>

## Versions

Gitea has one master as a tip branch and have many version branch such as v0.9. v0.9 is a release branch and we will tag v0.9.0 both for binary download.
If v0.9.0 have some bugs, we will accept PR on v0.9 and publish v0.9.1 and merge bug PR to master.

Branch master is a tip version, so if you wish a production usage, please download the latest release tag version. All the branch will be protected via github,
All the PRs to all the branches should be review by two maintainers and pass the automatic tests.

## Copyright

Code that you contribute should use the standard copyright header:

// Copyright 2016 - 2017 The 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.

Files in the repository are copyright the year they are added and the year they are last changed. If the copyright author is changed, just copy the head
below the old one.

+ 9
- 0

@@ -0,0 +1,9 @@
Andrey Nering <nobody@nobody.tld> (@andreynering)
Kim Carlbäcker <> (@bkcsoft)
LefsFlare <nobody@nobody.tld> (@LefsFlarey)
Lunny Xiao <> (@lunny)
Rachid Zarouali <nobody@nobody.tld> (@xinity)
Rémy Boulanouar <> (@DblK)
Sandro Santilli <> (@strk)
Thibault Meyer <nobody@nobody.tld> (@0xbaadf00d)
Thomas Boerger <> (@tboerger)

+ 36
- 0
DCO View File

@@ -0,0 +1,36 @@
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
660 York Street, Suite 102,
San Francisco, CA 94110 USA

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

+ 202
- 0

@@ -0,0 +1,202 @@

Apache License
Version 2.0, January 2004


1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
implied, including, without limitation, any warranties or conditions
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.


APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

+ 10
- 0

@@ -0,0 +1,10 @@
Andrey Nering <nobody@nobody.tld> (@andreynering)
Kim Carlbäcker <> (@bkcsoft)
LefsFlare <nobody@nobody.tld> (@LefsFlarey)
Lunny Xiao <> (@lunny)
Matthias Loibl <> (@metalmatze)
Rachid Zarouali <nobody@nobody.tld> (@xinity)
Rémy Boulanouar <> (@DblK)
Sandro Santilli <> (@strk)
Thibault Meyer <nobody@nobody.tld> (@0xbaadf00d)
Thomas Boerger <> (@tboerger)

+ 23
- 0 View File

@@ -0,0 +1,23 @@
# Gitea: Theme

[![Build Status](](
[![Join the chat at](](

This is a Hugo theme that gets used within all of our websites like our blog,
documentation and also the redirects. If you commit any changes to the `master`
branch it will trigger rebuilds of all the related websites.

## Contributing

Fork -> Patch -> Push -> Pull Request

## License

This project is under the Apache-2.0 License. See the [LICENSE](LICENSE) file
for the full license text.

## Copyright

Copyright (c) 2016 The Gitea Authors <>

+ 7
- 0
layouts/404.html View File

@@ -0,0 +1,7 @@
{{ partial "header" . }}

Page not found

{{ partial "footer" . }}

+ 3
- 0
layouts/_default/single.html View File

@@ -0,0 +1,3 @@
{{ partial "header" . }}
{{ .Content }}
{{ partial "footer" . }}

+ 7
- 0
layouts/index.html View File

@@ -0,0 +1,7 @@
{{ partial "header" . }}

{{ range where .Site.Pages "Type" "index" }}
{{ .Content }}
{{ end }}

{{ partial "footer" . }}

+ 2
- 0
layouts/partials/footer.html View File

@@ -0,0 +1,2 @@

+ 23
- 0
layouts/partials/header.html View File

@@ -0,0 +1,23 @@
<!DOCTYPE html>

<html lang="en">
<title>{{ if .IsHome }}{{ .Site.Title }}{{ else }}{{ .Title }} - {{ .Site.Title }}{{ end }}</title>
{{ .Hugo.Generator }}

{{ with .Params.goimport }}
<meta name="go-import" content="{{ . }}">
{{ end }}

{{ with .Params.gosource }}
<meta name="go-source" content="{{ . }}">
{{ end }}

<link rel="shortcut icon" type="image/x-icon" href="images/favicon.png">
<link rel="icon" type="image/x-icon" href="images/favicon.png">

<link rel="stylesheet" href="styles/main.css">
<script type="text/javascript" src="scripts/main.js"></script>
{{ partial "navbar" . }}

+ 0
- 0
layouts/partials/menu.html View File

+ 1
- 0
layouts/partials/navbar.html View File

@@ -0,0 +1 @@
{{ partial "menu" . }}

static/images/favicon.png View File

Before After
Width: 143  |  Height: 152  |  Size: 10 KiB

+ 0
- 0
static/scripts/main.js View File

+ 0
- 0
static/styles/main.css View File

+ 10
- 0
theme.toml View File

@@ -0,0 +1,10 @@
name = "Gitea"
license = "Apache-2.0"
licenselink = ""
description = "General theme for Gitea pages"
homepage = ""
tags = []

name = "The Gitea Authors"
homepage = ""