nocode
92bae9e4a6
Add Anaconda installer integration to FWS live environment: - Implement Anaconda launcher in .xinitrc with comprehensive error logging and debugging support - Add anaconda and anaconda-widgets packages to baseline and releng ISO configs - Fix anaconda-widgets PKGBUILD: replace gladeui with glib2-devel, disable Glade module - Update anaconda PKGBUILD with improved dependencies and build configuration - Add python-blivet PKGBUILD with detailed dependency documentation Enhance documentation and branding: - Expand AUTHORS.rst to clarify FWS vs archiso authorship and licensing - Update CONTRIBUTING.rst with inbound=outbound licensing policy and DCO requirements - Extend README.md with comprehensive legal basis table and licensing checklist - Remove Arch Linux references from MOTD and update to FWS GitHub project page - Fix fastfetch.sh to avoid read-only variable conflict in zsh - Add xterm to packages for installer debugging All changes maintain GPL-3.0-or-later compliance and improve GPL offer transparency.
70 lines
2.5 KiB
ReStructuredText
70 lines
2.5 KiB
ReStructuredText
============
|
|
Contributing
|
|
============
|
|
|
|
These are the contribution guidelines for **FWS**. FWS is a fork of `archiso
|
|
<https://gitlab.archlinux.org/archlinux/archiso>`_; the build-system parts
|
|
derived from archiso retain their original history and authorship (see
|
|
`AUTHORS.rst <AUTHORS.rst>`_).
|
|
|
|
Licensing of contributions (inbound = outbound)
|
|
===============================================
|
|
|
|
All contributions are accepted under the **same license as the project**,
|
|
``GPL-3.0-or-later`` (see `LICENSE <LICENSE>`_). By submitting a contribution you
|
|
agree that it is licensed under ``GPL-3.0-or-later`` and that you have the right
|
|
to submit it under that license.
|
|
|
|
Sign off every commit to certify the `Developer Certificate of Origin 1.1
|
|
<https://developercertificate.org/>`_:
|
|
|
|
.. code:: bash
|
|
|
|
git commit --signoff # adds a "Signed-off-by: Name <email>" trailer
|
|
|
|
For the full licensing, third-party and trademark picture, see `LICENSING.md
|
|
<LICENSING.md>`_, `THIRD-PARTY-LICENSES.md <THIRD-PARTY-LICENSES.md>`_ and
|
|
`TRADEMARKS.md <TRADEMARKS.md>`_.
|
|
|
|
Editorconfig
|
|
============
|
|
|
|
A top-level editorconfig file is provided. Please configure your text editor to use it.
|
|
|
|
Linting
|
|
=======
|
|
|
|
All ash and bash scripts are linted using shellcheck:
|
|
|
|
.. code:: bash
|
|
|
|
make lint
|
|
|
|
Changelog
|
|
=========
|
|
|
|
When adding, changing or removing something in a merge request, add a sentence to the `CHANGELOG.rst <CHANGELOG.rst>`_
|
|
explaining it.
|
|
The changelog entry needs to be added to the unreleased section at the top, as that section is used for the next
|
|
release.
|
|
|
|
Merge requests and signed commits
|
|
=================================
|
|
|
|
Merge requests are not required to contain signed commits (using ``git commit -S`` - see `man 1 git-commit
|
|
<https://man.archlinux.org/man/git-commit.1>`_).
|
|
The project maintainers may rebase a given merge request branch at their discretion (if possible), which may remove
|
|
signed commits.
|
|
|
|
The tip of the project's default branch is required to be a signed commit by the project maintainers.
|
|
For external contributors this means, that their merge request will be merged using ``--no-ff`` (see `man 1 git-merge
|
|
<https://man.archlinux.org/man/git-merge.1>`_) in a signed merge commit, while contributions by the project maintainers
|
|
may be merged using ``--ff`` when the top-most commit of the source branch is signed by a valid PGP key of the given
|
|
maintainer.
|
|
|
|
Testing
|
|
=======
|
|
|
|
Contributors are expected to test their contributions by building the releng profile and running the resulting image
|
|
using `run_archiso <scripts/run_archiso.sh>`_.
|