0 Fork 0

mirror of https://github.com/lucannez64/darling-lol.git synced 2026-10-26 19:47:42 +00:00

Files

T

3AvisD c48272aa8f docs: clarify interoperability and compliance wording

Add docs/INTEROPERABILITY.md, an English scope document that describes
the project's interoperability and responsible-use practices: what it
distributes, how it handles local platform metadata and the MAC/AMFI
probe, how it keeps copyright and licence notices, how it avoids
access/authentication/integrity shortcuts, how it presents trademarks
and handles notices, and the user's responsibility for Riot's terms.

Update README, NOTICE, COMPLIANCE and PLATFORM_IDENTITY to link the
document and to state the opt-in window-helper and synthetic-identity
behaviour accurately. Add CONTRIBUTING with DCO sign-off and a scope
checklist.

Documentation-only change: no launcher, patch, build or test behaviour
changes.

Signed-off-by: 3AvisD <[email protected]>

2026-10-23 14:03:59 -06:00

2.5 KiB

Raw Blame History

Contributing

Thank you for improving darling-lol. The project is an unofficial interoperability effort; contributions must keep it in that scope.

Before you start

Read docs/COMPLIANCE.md and docs/INTEROPERABILITY.md.
Do not add Riot client files, game binaries, game assets, logos, screenshots, gameplay audio/video, account data, tokens or credentials.
Do not add DRM/anti-cheat/authentication circumvention, telemetry spoofing, credential handling, or gameplay automation. Changes that present the project as an evasion tool are out of scope.
Keep existing copyright, licence and attribution notices. New third-party code or assets need a licence and provenance note in the pull request.

Licence of contributions

Original integration tooling (scripts, tools, tests, docs and project artwork) is licensed under GPL-3.0-only.
Patches to upstream components are licensed under the licence of the upstream file(s) they modify. If a patch touches files under different licences, each hunk keeps the licence of its target file.
By submitting a contribution, you confirm that you have the right to submit it and agree to license it under the applicable terms above.

Developer Certificate of Origin

Sign off every commit:

git commit -s -m "area: short description"

The sign-off certifies the Developer Certificate of Origin 1.1 (https://developercertificate.org/): you created the contribution or have the right to submit it under the project's licence, and you understand that the contribution and its sign-off are public and may be redistributed.

Checks

Run the source audit and the relevant tests before opening a pull request:

python3 scripts/validate.py
python3 -m unittest discover -s tests -p 'test_*.py'

The audit checks tracked source, rendered Python/shell and the pinned patch entries. Do not bypass it; fix the source or document the exception in the pull request.

Pull requests

Keep changes focused and describe the compatibility problem and the fix.
Mention any change that touches platform identity, sandbox/AMFI probes, anti-cheat or account risk. Do not describe it as stealth, evasion, spoofing or an anti-cheat bypass.
If you change a patch, verify that it still applies to the pinned revision.
If you change a user-facing variable, keep the old name as a deprecated alias for at least one release.

This is not legal advice. See docs/INTEROPERABILITY.md.

2.5 KiB Raw Blame History