Communication

💬 Communication Channels

Welcome to the eOzka community! Communication is the lifeblood of any open-source project. Whether you are seeking help with a stubborn bug. proposing a massive new feature, or just want to chat with fellow developers, here is how you can connect with us.

---

📢 GitHub Discussions (Asynchronous)

For general questions, feature requests, and community discussions, we heavily lean on GitHub Discussions within our main repositories. This is the preferred method for any technical conversation that requires a permanent, searchable record.

We use Discussions for:

• Asking architectural questions and getting help with the codebase.
• Showcasing what you've built using eOzka tools.
• Discussing API design debates before opening a formal Pull Request or Issue constraint.

💬 Community Chat (Synchronous)

For real-time communication, casual hanging out, or rapid-fire debugging sessions, we invite all contributors, maintainers, and users to join our official communication server:

• 👉 Join the eOzka Discord Server

When joining the Discord, please ensure your nickname matches (or closely resembles) your GitHub handle so we know who you are!

🐛 Bug Reports & Issue Trackers

If you have found a verifiable bug that you can reproduce, do not use Discussions or Chat. Instead, please navigate directly to the specific repository where the bug occurs and open a formal GitHub Issue.

• Always use the provided Issue Templates.
• Provide as much detail as possible (logs, screenshots, steps to reproduce).

For more details on getting help with bugs, please refer to the Support page.

---

📧 Contacting the Maintainers Privately

If you need to discuss a highly sensitive matter, please refrain from opening a public issue or talking about it in Discord. We take these matters very seriously and handle them privately.

For Code of Conduct violations, Legal inquiries, or Administrative matters, please reach out to the organization administrators directly at info_eozka@googlegroups.com.

For Security Vulnerabilities (Zero-days, exploits, sensitive data leaks), please refer immediately to our Security page to understand our responsible disclosure protocols.