.chglog/CHANGELOG.tpl.md

+{{ range .Versions }}
+Gajim {{ .Tag.Name }} ({{ datetime "02 Jan 2006" .Tag.Date }})
+
+{{ range .CommitGroups -}}
+{{ if .Title }}  {{ .Title }}{{end}}
+
+{{ range .Commits -}}
+{{ if .Subject }}  * {{ .Subject }}{{end}}{{if .Refs}} ({{range .Refs}}#{{.Ref}}{{end}}){{end}}
+{{ end }}
+{{ end -}}
+
+{{- if .NoteGroups -}}
+{{ range .NoteGroups -}}
+{{ .Title }}
+{{ range .Notes }}
+{{ .Body }}
+{{ end }}
+{{ end -}}
+{{ end -}}
+
+{{break}}
+
+{{ end -}}

.chglog/config.yml

+style: gitlab
+template: CHANGELOG.tpl.md
+info:
+  title: CHANGELOG
+  repository_url: https://dev.gajim.org/gajim/gajim
+options:
+  commits:
+    filters:
+      Type:
+        - feat
+        - imprv
+        - change
+        - perf
+        - fix
+  commit_groups:
+    sort_by: Custom
+    title_order:
+      - feat
+      - imprv
+      - change
+      - perf
+      - fix
+    title_maps:
+      feat: New
+      imprv: Improvements
+      change: Change
+      perf: Performance
+      fix: Bug Fixes
+  header:
+    pattern: "^(\\w*)\\:\\s(.*)$"
+    pattern_maps:
+      - Type
+      - Subject
+  issues:
+    prefix:
+      - "#"
+  refs:
+    actions:
+      - Fixes
+  notes:
+    keywords:
+      - NOTES

.ci/appveyor.yml

+version: 1.1.{build}
+
+image: Visual Studio 2019
+
+environment:
+  MSYSTEM: MINGW64
+  ARCH: "64bit"
+
+clone_depth: 10
+
+# init:
+#   - ps: iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
+
+install:
+  - set PATH=C:\msys64\usr\bin;%PATH%
+  - bash -lc "pacman --needed --noconfirm -Syu"
+  # This is needed because without killing all processes -Su will fail
+  - ps: Get-Process | Where-Object {$_.path -like 'C:\msys64*'} | Stop-Process
+  - bash -lc "pacman -Sydd --noconfirm filesystem"
+  - bash -lc "pacman --needed --noconfirm -Su"
+
+build_script:
+  - ps: |
+        $filename = "Gajim-$($env:GAJIM_VERSION)-$($env:ARCH)"
+        $filename_portable = "Gajim-Portable-$($env:GAJIM_VERSION)-$($env:ARCH)"
+        $filename_msixbundle = "Gajim-$($env:GAJIM_VERSION)"
+
+        if ($env:GAJIM_VERSION -eq "Nightly") {
+            $time_string=(get-date -UFormat "%Y-%m-%d").ToString()
+            $filename = $filename + "-" + $time_string
+            $filename_portable = $filename_portable + "-" + $time_string
+        }
+
+        $buildroot="C:\msys64\home\appveyor\gajim\win\_build_root"
+
+        function bash($command) {
+          Write-Host $command -NoNewline
+          C:\msys64\usr\bin\sh.exe --login -c $command
+        }
+
+        git clone "$env:APPVEYOR_BUILD_FOLDER" "C:\msys64\home\appveyor\gajim"
+        bash "C:/msys64/home/appveyor/gajim/win/build.sh"
+        if ($LastExitCode -ne 0) { $host.SetShouldExit($LastExitCode)  }
+
+        Push-AppveyorArtifact "$($buildroot)/Gajim.exe" -FileName "$($filename).exe"
+        Push-AppveyorArtifact "$($buildroot)/Gajim-Portable.exe" -FileName "$($filename_portable).exe"
+        Push-AppveyorArtifact "$($buildroot)/Gajim.msixbundle" -FileName "$($filename_msixbundle).msixbundle"
+        if ($LastExitCode -ne 0) { $host.SetShouldExit($LastExitCode)  }
+
+# on_finish:
+#   - ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))

.ci/prepare_git.sh

+#!/bin/sh
+
+echo "$2" | tr -d '\r' | ssh-add - > /dev/null
+ssh-add -l
+mkdir -p ~/.ssh
+chmod 700 ~/.ssh
+ssh-keyscan "$1" >> ~/.ssh/known_hosts
+git config --global user.email "$CI_GIT_USER_EMAIL"
+git config --global user.name "$CI_GIT_USER_USERNAME"

.gitattributes

+*.css   diff=css
+*.html  diff=html
+*.xhtml diff=html
+*.py    diff=python
+*.md    diff=markdown
\ No newline at end of file

.githooks/update

+#!/usr/bin/env python3
+
+from __future__ import annotations
+
+from typing import List
+from typing import Tuple
+
+import subprocess
+import sys
+
+ALLOWED_TAGS = [
+    "ci",
+    "cfix",
+    "new",
+    "cq",
+    "feat",
+    "fix",
+    "perf",
+    "refactor",
+    "chore",
+    "change",
+    "release",
+    "other",
+    "imprv",
+    "revert",
+]
+
+
+def parse_args() -> Tuple[str, str, str]:
+    ref_name = sys.argv[1]
+    old_ref = sys.argv[2]
+    new_ref = sys.argv[3]
+    return ref_name, old_ref, new_ref
+
+
+def get_commit_subject(sha: str) -> str:
+    data = subprocess.check_output(["git", "log", "-1", "--pretty=format:%s", sha])
+    return data.decode()
+
+
+def get_commit_shas(start_ref: str, end_ref: str) -> List[str]:
+    arg = f"{start_ref}..{end_ref}"
+    data = subprocess.check_output(["git", "rev-list", arg])
+    text = data.decode()
+    text = text.strip()
+    if not text:
+        # Can happen if commits are deleted after force push
+        return []
+    return text.split("\n")
+
+
+def enforce_message_rules(subject: str) -> None:
+    try:
+        tag, subject = subject.split(": ", maxsplit=1)
+    except ValueError:
+        print("Unknown commit message tag:", subject)
+        sys.exit(1)
+
+    if tag not in ALLOWED_TAGS:
+        print("Unknown commit message tag:", tag)
+        sys.exit(1)
+
+    if tag == "release":
+        if not subject[0].isdigit():
+            print('Release commits should be of the form "release: X.X.X"')
+            sys.exit(1)
+        return
+
+    if not subject[0].isupper():
+        print("First letter after tag must be uppercase")
+        sys.exit(1)
+
+
+def main(args: Tuple[str, str, str]) -> None:
+    ref_name, old_ref, new_ref = args
+    print("UPDATE", ref_name, old_ref, new_ref)
+
+    if ref_name != "refs/heads/master":
+        # We enforce only for master branch
+        return
+
+    shas = get_commit_shas(old_ref, new_ref)
+    for sha in shas:
+        print("Check", sha)
+        subject = get_commit_subject(sha)
+        enforce_message_rules(subject)
+
+
+if __name__ == "__main__":
+    args = parse_args()
+    main(args)

.gitignore

+syntax: glob
+*.orig
+*.swp
+*.gmo
+*.m4
+*.pyc
+*.pyo
+*~
+*#
+
+gajim/data/locale
+
+# Cache
+
+__pycache__/
+.mypy_cache/
+.ruff_cache/
+
+# Build folders
+
+debian_build/
+build/
+dist/
+gajim.egg-info/
+win/_build_root
+venv/
+.venv/
+node_modules/
+.flatpak-builder
+
+# IDE files
+
+.vscode
+*.sublime-project
+*.sublime-workspace
+.idea

.gitlab-ci.yml

+workflow:
+  rules:
+    - if: $NIGHTLY_BUILD
+    - if: $DEBIAN_BUILD
+    - if: $WINDOWS_BUILD
+    - if: $DEPLOY_FLATPAK
+    - if: $CI_PIPELINE_SOURCE == "push"
+
+stages:
+  - test
+  - build
+  - deploy
+  - publish
+
+test-other:
+  image: gajim-test
+  stage: test
+  script:
+    - ./make.py build
+    - pyproject-build
+    - appstream-util validate dist/metadata/org.gajim.Gajim.metainfo.xml
+  interruptible: true
+
+test-black:
+  image: gajim-test
+  stage: test
+  rules:
+    - changes:
+      - "**/*.py"
+  script:
+    - black --version
+    - black --check .
+  interruptible: true
+
+test-codespell:
+  image: gajim-test
+  stage: test
+  script:
+    - codespell --version
+    - codespell gajim
+  interruptible: true
+
+test-pyright:
+  image: gajim-test
+  stage: test
+  rules:
+    - changes:
+      - "**/*.py"
+  script:
+    - pip install git+https://dev.gajim.org/gajim/python-nbxmpp.git
+    - pip install git+https://dev.gajim.org/gajim/omemo-dr.git
+    - pip install --config-settings=config=Gtk4,Gdk4,GtkSource5 git+https://github.com/pygobject/pygobject-stubs.git
+    - pyright --version
+    - pyright
+  interruptible: true
+
+test-ruff:
+  image: gajim-test
+  stage: test
+  rules:
+    - changes:
+      - "**/*.py"
+  script:
+    - ruff --version
+    - ruff check .
+  interruptible: true
+
+test-isort:
+  image: gajim-test
+  stage: test
+  rules:
+    - changes:
+      - "**/*.py"
+  script:
+    - isort --version
+    - isort --check .
+  interruptible: true
+
+test-unittest:
+  image: gajim-test
+  stage: test
+  script:
+    - pip install git+https://dev.gajim.org/gajim/python-nbxmpp.git
+    - coverage run --source=gajim -m unittest discover -s test -v
+    - coverage report -mi
+    - coverage xml -i
+  coverage: "/TOTAL.+ ([0-9]{1,3}%)/"
+  artifacts:
+    reports:
+      coverage_report: 
+        coverage_format: cobertura
+        path: coverage.xml
+  interruptible: true
+
+build-unix:
+  image: gajim-build
+  stage: build
+  dependencies: []
+  rules:
+    - if: '$DEBIAN_BUILD'
+    - if: '$NIGHTLY_BUILD'
+    - if: '$CI_COMMIT_TAG'
+  script:
+    - ./make.py build
+    - pyproject-build
+
+  artifacts:
+    name: "gajim-$CI_COMMIT_REF_NAME-$CI_COMMIT_SHA"
+    expire_in: 1 week
+    paths:
+      - dist/gajim-*.tar.gz
+      - dist/gajim-*.whl
+
+build-debian-nightly:
+  image: gajim-build
+  stage: build
+  variables:
+    REV: "1"
+  needs:
+    - job: build-unix
+      artifacts: true
+  rules:
+    - if: '$DEBIAN_BUILD'
+    - if: '$NIGHTLY_BUILD'
+  allow_failure: true
+  script:
+    - apt-get update
+    - apt-get install -y python3-nbxmpp-nightly
+    - apt-get install -y python3-omemo-dr
+    - release-helper build-debian-pkg "$(find dist/gajim-*.tar.gz)" $REV --pkgsuffix=nightly
+
+  artifacts:
+    name: "gajim-$CI_COMMIT_REF_NAME-$CI_COMMIT_SHA"
+    expire_in: 1 week
+    paths:
+      - debian_build/*
+
+# build-windows:
+#   image: gajim-build
+#   stage: build
+#   dependencies: []
+#   rules:
+#     - if: '$CI_COMMIT_TAG'
+#   script:
+#     - >
+#       release-helper build-windows-pkg \
+#         --account=lovetox \
+#         --repository=https://dev.gajim.org/gajim/gajim \
+#         --branch=master \
+#         --version=$CI_COMMIT_TAG \
+#         --commit-sha=$CI_COMMIT_SHA \
+#         --api-key=$APPVEYOR_API_KEY \
+#         .ci/appveyor.yml
+#   artifacts:
+#     expire_in: 1 day
+#     paths:
+#       - windows_build/*.json
+
+build-windows-nightly:
+  image: gajim-build
+  stage: build
+  dependencies: []
+  rules:
+    - if: '$NIGHTLY_BUILD'
+    - if: '$WINDOWS_BUILD'
+  script:
+    - >
+      release-helper build-windows-pkg \
+        --account=lovetox \
+        --repository=https://dev.gajim.org/gajim/gajim \
+        --branch=master \
+        --version=Nightly \
+        --commit-sha=$CI_COMMIT_SHA \
+        --api-key=$APPVEYOR_API_KEY \
+        .ci/appveyor.yml
+  artifacts:
+    expire_in: 1 day
+    paths:
+      - windows_build/*.json
+
+deploy-unix:
+  image: gajim-deploy
+  stage: deploy
+  dependencies:
+    - build-unix
+  rules:
+    - if: '$CI_COMMIT_TAG'
+  script:
+    - >
+      release-helper deploy-to-ftp \
+        --host=$FTP_HOST \
+        --user=$FTP_USER \
+        --password=$FTP_PASS \
+        --directory=downloads/"$(echo $CI_COMMIT_TAG | cut -c 1-3)" \
+        --rename=gajim-$CI_COMMIT_TAG.tar.gz \
+        "$(find dist/gajim-*.tar.gz)"
+
+deploy-unix-nightly:
+  image: gajim-deploy
+  stage: deploy
+  dependencies:
+    - build-unix
+  needs:
+    - build-unix
+  rules:
+    - if: '$NIGHTLY_BUILD'
+  allow_failure:
+    exit_codes:
+      - 100
+  script:
+    - release-helper nightly-check
+    - >
+      release-helper deploy-to-ftp \
+        --host=$FTP_HOST \
+        --user=$FTP_USER \
+        --password=$FTP_PASS \
+        --directory=downloads/snap \
+        --rename=gajim-"$(date +'%Y-%m-%d')".tar.gz \
+        "$(find dist/gajim-*.tar.gz)"
+
+deploy-debian-nightly:
+  image: gajim-deploy
+  stage: deploy
+  dependencies:
+    - build-debian-nightly
+  needs:
+    - build-debian-nightly
+  rules:
+    - if: '$DEBIAN_BUILD'
+    - if: '$NIGHTLY_BUILD'
+  allow_failure: true
+  script:
+    - |
+      if [ "$FORCE_DEB_DEPLOY" != "true" ]
+      then
+        release-helper nightly-check
+      fi
+    - >
+      release-helper deploy-to-ftp \
+        --host=$FTP_HOST \
+        --user=$FTP_USER \
+        --password=$FTP_PASS \
+        --directory=debian/gajim/"$(date +'%Y%m%d')" \
+        debian_build
+
+# deploy-windows:
+#   image: gajim-deploy
+#   stage: deploy
+#   dependencies:
+#     - build-windows
+#   rules:
+#     - if: '$CI_COMMIT_TAG'
+#   script:
+#     - release-helper download-appveyor-artifacts "$(find windows_build/*.json)" windows_build
+#     - rm windows_build/*.json
+#     - >
+#       release-helper deploy-to-ftp \
+#         --host=$FTP_HOST \
+#         --user=$FTP_USER \
+#         --password=$FTP_PASS \
+#         --directory=downloads/"$(echo $CI_COMMIT_TAG | cut -c 1-3)" \
+#         windows_build
+
+deploy-windows-nightly:
+  image: gajim-deploy
+  stage: deploy
+  dependencies:
+    - build-windows-nightly
+  needs:
+    - build-windows-nightly
+  rules:
+    - if: '$NIGHTLY_BUILD'
+    - if: '$WINDOWS_BUILD'
+  allow_failure:
+    exit_codes:
+      - 100
+  script:
+    - release-helper nightly-check
+    - release-helper download-appveyor-artifacts "$(find windows_build/*.json)" windows_build
+    - rm windows_build/*.json
+    - >
+      release-helper deploy-to-ftp \
+        --host=$FTP_HOST \
+        --user=$FTP_USER \
+        --password=$FTP_PASS \
+        --directory=downloads/snap/win \
+        windows_build
+
+deploy-flatpak:
+  image: gajim-deploy
+  stage: deploy
+  dependencies: []
+  rules:
+    - if: '$DEPLOY_FLATPAK'
+    - if: '$CI_COMMIT_TAG'
+  before_script:
+    - eval $(ssh-agent -s)
+    - .ci/prepare_git.sh github.com "${FLATHUB_DEPLOY_KEY}"
+  script:
+    # extract the current commit hash of the shared-modules submodule
+    - submodule_commit=$(git submodule status flatpak/shared-modules | cut -c 2-41)
+    - git clone git@github.com:flathub/org.gajim.Gajim.git
+    - cd org.gajim.Gajim
+    - mv ../flatpak/org.gajim.Gajim.yaml org.gajim.Gajim.yaml
+    - mv ../flatpak/app-overrides.json app-overrides.json
+    # point the shared-modules submodule to the new commit, without fetching the repository
+    - git update-index --cacheinfo 160000,${submodule_commit},shared-modules
+    - git diff
+    - git add --all
+    - git commit -m "$CI_COMMIT_TAG$DEPLOY_FLATPAK"
+    - git push
+
+publish-website:
+  image: gajim-publish
+  stage: publish
+  dependencies: []
+  rules:
+    - if: '$CI_COMMIT_TAG'
+  before_script:
+    - eval $(ssh-agent -s)
+    - .ci/prepare_git.sh dev.gajim.org "${WEBSITE_DEPLOY_KEY}"
+  script:
+    - git clone git@dev.gajim.org:gajim/website.git
+    - cd website
+    - git checkout master
+    - python ./scripts/bump_version.py $CI_COMMIT_TAG
+    - git diff
+    - git add -u
+    - git commit -m "Release Gajim $CI_COMMIT_TAG"
+    - git push
+
+publish-release:
+  image: gajim-publish
+  stage: publish
+  dependencies: []
+  rules:
+    - if: '$CI_COMMIT_TAG'
+  script:
+    - >
+      release-helper finish-milestone \
+        $CI_PROJECT_ID \
+        $PROJECT_TOKEN \
+        --version=$CI_COMMIT_TAG \
+        --title="Next Release"
+    - >
+      release-helper create-release \
+        $CI_PROJECT_ID \
+        $PROJECT_TOKEN \
+        --version=$CI_COMMIT_TAG \
+        --tag=$CI_COMMIT_TAG \
+        --milestone=$CI_COMMIT_TAG

.gitlab/issue_templates/Bug.md

+**Please first check if another issue has been opened for your problem**
+
+## Versions
+
+  - OS: 
+  - Gajim version: 
+  - GTK version: 
+  - Python-nbxmpp version: 
+
+## Steps to reproduce the problem
+
+  1.
+  1.
+  1.
+
+## Expected behavior
+
+
+## Actual behavior
+
+

.gitlab/issue_templates/Enhancement.md

+**Please note by far the quickest way to get a new feature is to file a Merge Request.**
+
+## Description of the new feature
+
+

.gitlab/issue_templates/Release.md

+*Release date: xx xxx xxxx*
+
+## Preparations
+
+* [ ] Raise nbxmpp version (if necessary)
+
+## Build
+
+* [ ] Merge translations from Weblate
+* [ ] Update IANA data with `./scripts/get_iana_data.py gajim/common/iana.py`
+* [ ] Run `./scripts/update_flatpak_manifest.py`
+* [ ] Run `./scripts/bump_version.py x.x.x`
+* [ ] Push release tag `x.x.x`
+* [ ] Upload .msixbundle to Windows store
+* [ ] Close release milestone after new milestone has been created automatically
+
+## Update
+
+* [ ] Website: Write announcement post with changelog
+* [ ] Website: Update screenshots
+* [ ] Website: Merge website translations from Weblate
+* [ ] MUC: Update MUC subject on gajim@conference.gajim.org
+* [ ] Publish release post on [Fosstodon](https://fosstodon.org/@gajim)

.gitmodules

+[submodule "flatpak/shared-modules"]
+	path = flatpak/shared-modules
+	url = https://github.com/flathub/shared-modules.git

.pre-commit-config.yaml

+repos:
+  - repo: https://github.com/charliermarsh/ruff-pre-commit
+    rev: v0.9.7
+    hooks:
+      - id: ruff
+        exclude: ".githooks/"
+
+  - repo: https://github.com/codespell-project/codespell
+    rev: v2.4.1
+    hooks:
+    - id: codespell
+      pass_filenames: false
+      additional_dependencies:
+        - tomli
+
+  - repo: https://github.com/RobertCraigie/pyright-python
+    rev: v1.1.394
+    hooks:
+    - id: pyright
+      pass_filenames: false
+      additional_dependencies:
+        - nbxmpp @ git+https://dev.gajim.org/gajim/python-nbxmpp.git
+        - PyGObject-stubs @ git+https://github.com/pygobject/pygobject-stubs.git
+        - python-gitlab
+        - ruamel.yaml
+        - sentry-sdk
+      stages: [manual]
+
+  - repo: https://github.com/pycqa/isort
+    rev: 5.13.2
+    hooks:
+      - id: isort
+
+  - repo: https://github.com/psf/black
+    # The `refs/tags/<tag>:refs/tags/<tag>` is needed for black's required-version to work:
+    # https://github.com/psf/black/issues/2493#issuecomment-1081987650
+    rev: 'refs/tags/24.10.0:refs/tags/24.10.0'
+    hooks:
+      - id: black
+
+  - repo: https://github.com/fsfe/reuse-tool
+    rev: v5.0.2
+    hooks:
+      - id: reuse
+        stages: [manual]

AUTHORS

-CURRENT DEVELOPERS:
-
-Stephan Erb (steve-e AT h3c.de)
-Nikos Kouremenos (kourem AT gmail.com)
-Yann Leboulanger (asterix AT lagaule.org)
-Julien Pivotto (roidelapluie AT gmail.com)
-Jonathan Schleifer (js-gajim AT webkeks.org)
-Travis Shirk (travis AT pobox.com)
-Brendan Taylor (whateley AT gmail.com)
-Jean-Marie Traissard (jim AT lapin.org)
-
-PAST DEVELOPERS:
-
-Stefan Bethge (stefan AT lanpartei.de)
-Vincent Hanquez (tab AT snarc.org)
-Dimitur Kirov (dkirov AT gmail.com)

CONTRIBUTING.md

+# Project
+
+If you want to create a fork and use an external account (Github, Google) drop us a message at the Gajim support [group chat](xmpp:gajim@conference.gajim.org?join) so we can give you the necessary rights
+
+## Versioning
+
+┌────── Major (Will not change unless we switch GTK version)  
+│ ┌───── Minor (Changes when new features are introduced  
+│ │ ┌──── Micro (Used for hotfixes and small changes)  
+│ │ │ ┌─── Only used while developing  
+│ │ │ │  
+│ │ │ │  
+│ │ │ │  
+│ │ │ │  
+1.3.3-dev1
+
+## Branches
+
+Currently there is only one stable/development branch - master.
+The master branch must always be in a releasable state.
+
+Development for bigger changes need to happen in feature branches or forks.
+
+Previously the project maintained multiple versions of Gajim in
+different stable branches, but from Gajim 1.4.0 on this approach was changed
+to lower the maintenance burden and release faster.
+
+
+# Commit Messages
+
+If you are not familiar with Git please read the [HowTo](https://dev.gajim.org/gajim/gajim/wikis/development/howtogit)
+
+A good article regarding [good commit messages](https://chris.beams.io/posts/git-commit/)
+
+Every commit message must be prefixed with one of the following tags:
+
+Changelog relevant
+
+- feat      (a new feature was added)
+- fix       (something was fixed)
+- perf      (performance related changes)
+- imprv     (improvements)
+- change    (existing functionality was changed)
+
+Prefixes for development
+
+- new       (new code, but the end user will not notice)
+- ci        (ci related changes)
+- cq        (code quality changes e.g. formatting, typing, codestyle)
+- cfix      (code fixes which should not show up in the changelog)
+- refactor  (code was changed, but the end user will not notice)
+- chore     (reoccuring tasks which need to be done)
+- release   (only used for release commits)
+- revert    (used when a commit needs to be reverted)
+- other
+
+Further the first letter after the tag must be upper case
+
+Example:
+
+`feat: New Button which does something`
+
+# Use pre-commit
+
+Execute the following inside the repository dir
+
+    $ pip install pre-commit
+    $ pre-commit install
+
+Now pre-commit will run various checks before code can be committed.
+
+To update to the newest versions
+
+    $ pre-commit autoupdate
+
+# Man Pages
+
+Man pages are written in markdown and converted with pandoc
+
+While developing this command is useful to preview the manpage
+
+    $ pandoc gajim.1.md -s -t man | /usr/bin/man -l -
+
+To convert the markdown
+
+    $ pandoc gajim.1.md -s -t man -o gajim.1

INSTALL

-Installation Instructions
-*************************
-
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
-Software Foundation, Inc.
-
-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
-
-Basic Installation
-==================
-
-These are generic installation instructions.
-
-   The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions.  Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
-   It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring.  (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
-
-   If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release.  If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
-   The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'.  You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
-
-The simplest way to compile this package is:
-
-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.  If you're
-     using `csh' on an old version of System V, you might need to type
-     `sh ./configure' instead to prevent `csh' from trying to execute
-     `configure' itself.
-
-     Running `configure' takes awhile.  While running, it prints some
-     messages telling which features it is checking for.
-
-  2. Type `make' to compile the package.
-
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
-
-  4. Type `make install' to install the programs and any data files and
-     documentation.
-
-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
-
-Compilers and Options
-=====================
-
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about.  Run `./configure --help' for
-details on some of the pertinent environment variables.
-
-   You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment.  Here
-is an example:
-
-     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
-   *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'.  `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
-
-   If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory.  After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-
-Installation Names
-==================
-
-By default, `make install' installs the package's commands under
-`/usr/local/bin', include files under `/usr/local/include', etc.  You
-can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX'.
-
-   You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files.  If you
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses
-PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files still use the regular prefix.
-
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
-
-   If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-Optional Features
-=================
-
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System).  The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
-   For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-Specifying the System Type
-==========================
-
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
-     CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
-     OS KERNEL-OS
-
-   See the file `config.sub' for the possible values of each field.  If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option `--target=TYPE' to select the type of system they will
-produce code for.
-
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `config.site' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists.  Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'.  However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./configure CC=/usr/local2/bin/gcc
-
-causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script).  Here is a another example:
-
-     /bin/bash ./configure CONFIG_SHELL=/bin/bash
-
-Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
-configuration-related scripts to be executed by `/bin/bash'.
-
-`configure' Invocation
-======================
-
-`configure' recognizes the following options to control how it operates.
-
-`--help'
-`-h'
-     Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to `/dev/null' (any error
-     messages will still be shown).
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
-

LICENSES/GPL-2.0-only.txt

+GNU GENERAL PUBLIC LICENSE
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
+
+Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
+
+Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
+
+     a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
+
+     b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
+
+     c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
+
+     a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+
+     b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+
+     c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
+
+If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
+
+5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
+
+7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     one line to give the program's name and an idea of what it does. Copyright (C) yyyy name of author
+
+     This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+     You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
+
+     Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
+
+     Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice

LICENSES/GPL-2.0-or-later.txt

+GNU GENERAL PUBLIC LICENSE
+Version 2, June 1991
+
+Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+Preamble
+
+The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
+
+For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
+
+We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
+
+Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
+
+Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
+
+1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
+
+2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
+
+     a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
+
+     b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
+
+     c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
+
+3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
+
+     a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+
+     b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
+
+     c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
+
+If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
+
+4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
+
+5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
+
+6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
+
+7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
+
+This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
+
+8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
+
+9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
+
+10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
+
+NO WARRANTY
+
+11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+END OF TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     one line to give the program's name and an idea of what it does. Copyright (C) yyyy name of author
+
+     This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+     You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this when it starts in an interactive mode:
+
+     Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
+
+     Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+signature of Ty Coon, 1 April 1989 Ty Coon, President of Vice