chore: replace generic emails with GitHub references

[CybotTM]

Summary

• Replace generic @netresearch.de email addresses with GitHub-native references
• Add support section to package metadata with Issues/Source URLs
• Use GitHub Security Advisories for vulnerability reporting
• Use GitHub Issues for general support/contact

Motivation

Generic email addresses in public repositories attract spam and create maintenance overhead. GitHub provides better mechanisms for each use case:

• Security: Private vulnerability reporting via Security Advisories
• Support: Issue tracker with templates and labels
• Contact: Discussions for general questions

Test plan

• Verify package metadata is valid (composer validate)
• Verify links in documentation point to correct URLs
• Verify no functional email addresses were removed (only metadata/docs)

[gemini-code-assist]

Summary of Changes

Hello @CybotTM, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes the project's contact and support mechanisms by migrating away from generic email addresses. It leverages GitHub's integrated features like Security Advisories and Issues to provide more efficient and less spam-prone channels for security reports, support, and general inquiries, thereby reducing maintenance overhead and improving communication clarity.

Highlights

• Email Replacement: Replaced generic @netresearch.de email addresses with GitHub-native references to reduce spam and maintenance.
• Package Metadata Update: Added a support section to the package metadata, including Issues and Source URLs.
• Vulnerability Reporting: Configured the project to use GitHub Security Advisories for private vulnerability reporting.
• General Support: Directed general support and contact inquiries to GitHub Issues.

Changelog

• config.dist.php
  • Removed the generic email address from the @author tag in the file header.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request replaces generic email addresses with GitHub-native references for support and contact, which is a good practice for reducing spam and centralizing communication. The change in config.dist.php correctly removes the email address from the author tag, aligning with the PR's stated goals. The change is straightforward and I see no issues.