Fedora Release Engineering
Find a file
Mohan Boddu d3385cabec Adding a script to generate odcs token
Also, moving the odcs related scripts to odcs/ dir

Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
2020-08-13 12:03:45 -04:00
configs configs and changes needed for openh264 2018-03-23 15:28:13 -05:00
docs Doc for updating rawhide koji repo after branching 2020-08-12 13:39:50 -04:00
scripts Adding a script to generate odcs token 2020-08-13 12:03:45 -04:00
tests/pylint Create basic python3 testing framework 2017-07-27 16:39:14 -04:00
.gitignore Add .idea folder to gitignore 2019-02-21 11:26:26 +01:00
koji-archive-policy Adding koji archive policy 2019-10-04 12:03:59 -04:00
Makefile Create basic python3 testing framework 2017-07-27 16:39:14 -04:00
README update CC-BY-SA-3.0 to use SPDX 2015-11-13 16:19:25 -06:00
TESTING Create basic python3 testing framework 2017-07-27 16:39:14 -04:00
Vagrantfile Use Fedora 29 for Vagrant 2019-02-13 14:46:56 +00:00

This is the Fedora Release Engineering GIT repo.  Random stuff is tossed
here.


#########################################################################
#                                                                       #
# For more information please see the docs/ dir or alternatively:       #
# https://docs.pagure.org/releng/                                       #
#                                                                       #
#########################################################################


Everything is copyrighted by the respective authors. You can use and
redistribute the code under the terms of version 2 or later of the
GNU Public License as published by the Free Software Foundation.

To make licensing easier, license headers in the source files will be
a single line reference to Unique License Identifiers as defined by
the Linux Foundation's SPDX project [1].  For example,
in a source file the full "GPL v2.0 or later" header text will be
replaced by a single line:

    SPDX-License-Identifier:    GPL-2.0+

the license terms of all files in the source tree should be defined
by such License Identifiers; in no case a file can contain more than
one such License Identifier list.

If a "SPDX-License-Identifier:" line references more than one Unique
License Identifier, then this means that the respective file can be
used under the terms of either of these licenses, i. e. with

    SPDX-License-Identifier:    GPL-2.0+    LGPL-2.1+

you can chose between GPL-2.0+ and LGPL-2.1+ licensing.

We use the SPDX Unique License Identifiers here; these are available
at [2].

[1] http://spdx.org/
[2] http://spdx.org/licenses/

Full name                                       SPDX Identifier     OSI Approved    File name           URI
============================================================================================================================================================
GNU General Public License v2.0 or later        GPL-2.0+            Y               gpl-2.0.txt         http://www.gnu.org/licenses/gpl-2.0.txt
GNU Lesser General Public License v2.1 or later LGPL-2.1+           Y               lgpl-2.1.txt        http://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt
Creative Commons Attribution Share Alike 3.0    CC-BY-SA-3.0                        CC-BY-SA-3.0.html   http://spdx.org/licenses/CC-BY-SA-3.0.html