Help and Support

Getting Help & Community Support

Thank you for your interest in OpenPublisher! Currently, the application is maintained by a very small core team of two people. To keep the project focused and stable, please review our community guidelines before making changes or reporting issues.

Bugs & Feature Requests

Bugs & Feature Requests

The best way to contribute right now is by thoroughly documenting bugs or proposing well-thought-out features via our GitHub issue tracker:

  • Bugs: Include clear steps to reproduce the issue, your operating system, and your specific OpenPublisher version.

  • Features: Open an issue to discuss your idea first, explaining exactly why it is crucial and how it benefits the broader user base.

Code Contributions (Pull Requests)Code Contributions (Pull Requests)

Because our bandwidth for reviewing new code is strictly limited, we are highly selective about accepted Pull Requests (PRs). We generally only accept contributions that represent significant, high-impact improvements and are fully aligned with our immediate roadmap.

  • Open an Issue First: Do not write code or submit a PR without discussing it with maintainers first. Detail your proposed changes and implementation strategy.

  • Wait for Approval: Wait for an explicit “go-ahead” before working on the PR. Unapproved PRs will likely be closed to save everyone time.

  • Code Quality: If approved, your code must match the existing project style, be extensively commented, and avoid introducing unnecessary dependencies.

Security Policy & Vulnerability Reporting

Security Policy & Vulnerability ReportingOpenPublisher operates on a continuous, rolling release model. The application automatically pulls the latest updates and security patches silently upon launch (though major releases with large client-side changes may require manual updates).

  • Private Reporting: We ask that you report vulnerabilities directly and privately to security@openpublisher.app before opening public GitHub issues.

  • Include Details: Provide a clear description of the vulnerability, steps to reproduce it, and your operating system

Code of ConductCode of Conduct

We pledge to make participation in our community a harassment-free experience for everyone. We expect all contributors to demonstrate empathy, respect differing viewpoints, and gracefully accept constructive feedback. Instances of abusive, harassing, or otherwise unacceptable behavior can be reported confidentially to community leaders at info@openpublisher.app.