Backport how-to-write-a-privacy.md to release_10#11204
Open
selyesa wants to merge 1 commit intoILIAS-eLearning:release_10from
Open
Backport how-to-write-a-privacy.md to release_10#11204selyesa wants to merge 1 commit intoILIAS-eLearning:release_10from
selyesa wants to merge 1 commit intoILIAS-eLearning:release_10from
Conversation
The privacy documentation template (Version 2.3) was added to trunk but never included in release_10. This backports it to provide component maintainers with the official guide for writing PRIVACY.md files, supporting GDPR transparency requirements. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/development/how-to-write-a-privacy.md(Version 2.3) from trunk to release_10Motivation
The GDPR requires transparency regarding personal data flows. ILIAS documents this per-component via PRIVACY.md files. The official guide for writing these files should be available on release_10 as well, so component maintainers can follow the established template.
Test plan
docs/development/how-to-write-a-privacy.md🤖 Generated with Claude Code