Contact

Get in touch with the ProteanOS project for questions, feedback, or collaboration.

Communication and collaboration illustration

Getting in Touch

The ProteanOS project welcomes questions, feedback, and contributions from the community. Several communication channels are available depending on the nature of your inquiry.

Before reaching out, consider checking the FAQ and searching the mailing list archives—your question may already have been answered.

Communication Channels

Mailing Lists

Mailing lists are the primary communication channel for the ProteanOS project. They provide a public record of discussions and allow participation from community members worldwide.

See the Mailing Lists section for subscription information and posting guidelines.

Email Contact

For matters that don't fit the public mailing lists (such as security issues or private inquiries), you can reach the project maintainers directly:

General Inquiries:

contact@proteanos.com

Security Issues:

security@proteanos.com

For security vulnerabilities, please review our security policy first.

What to Include in Your Message

To help us respond effectively, please include relevant details when contacting the project:

For Technical Questions

  • A clear description of what you're trying to accomplish
  • The specific problem or error you're encountering
  • Your development environment details (host OS, target platform)
  • Version information for relevant tools and packages
  • Steps to reproduce the issue, if applicable
  • Any error messages or relevant log output

For Bug Reports

  • A concise summary of the bug
  • Steps to reproduce the issue consistently
  • Expected behavior vs. actual behavior
  • Environment details where the bug occurs
  • Any workarounds you've discovered

For Feature Requests

  • A description of the feature and its purpose
  • Use cases that would benefit from the feature
  • How the feature might fit with existing functionality
  • Whether you're interested in implementing it yourself

Response Times

The ProteanOS project is maintained by volunteers, so response times may vary. Generally:

  • Mailing list posts typically receive responses within a few days
  • Complex technical questions may take longer to investigate
  • Security issues receive priority attention
  • Patches and contributions are reviewed as maintainer availability permits

If you don't receive a response after a reasonable time, a polite follow-up is appropriate.

Contributing

If you're interested in contributing to ProteanOS—whether through code, documentation, testing, or other means—see the Development section for information on how to get involved.

Code of Conduct

All project communication channels are governed by the expectation of professional, respectful interaction. When participating:

  • Be respectful and constructive in discussions
  • Focus on technical merit rather than personal criticisms
  • Be patient with those who are learning
  • Accept constructive feedback gracefully
  • Help create a welcoming environment for all participants

Contact FAQ

Which mailing list should I use?

Use proteanos-dev for technical questions, development discussions, and patch submissions. The announce list is primarily for receiving project news rather than posting.

Do I need to subscribe to the mailing list to post?

Yes, posting to the lists requires subscription to reduce spam. Subscription is free and archives are publicly readable.

How do I report a security vulnerability?

Email security@proteanos.com directly rather than posting to public lists. See the security policy for details on responsible disclosure.

Can I contact maintainers privately?

For matters that don't fit public discussion, use the contact@proteanos.com address. However, public mailing lists are preferred for most technical topics.

I sent a message but haven't received a response. What should I do?

Wait a few days, then send a polite follow-up. Maintainers are volunteers with limited time. For mailing lists, ensure your message was delivered by checking the archives.