Skip to main content

​
Code of Conduct

​
Our Pledge

We as members, contributors, maintainers and leaders pledge to make participation in the TomorrowOS community a respectful, harassment-free experience for everyone. TomorrowOS exists to help the digital signage industry build more reliable, interoperable and developer-friendly experiences across different operating systems, hardware platforms, CMS environments and deployment conditions. We pledge to act and interact in ways that contribute to an open, welcoming, inclusive, constructive and technically honest community.

​
Our Standards

Examples of behaviour that contributes to a positive environment include:
  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility, apologising when mistakes are made and learning from the experience
  • Focusing on what is best for the overall project and the wider signage industry
  • Being clear when something is proven, untested, unknown or platform-dependent
  • Helping make TomorrowOS safer, clearer and more useful for real-world deployments
Examples of unacceptable behaviour include:
  • Harassment, threats, abuse or personal attacks
  • Trolling, insulting or derogatory comments
  • Sexualised language, imagery, attention or advances of any kind
  • Public or private harassment
  • Publishing another person’s private information without explicit permission
  • Sharing customer data, credentials, private keys, access tokens or confidential information
  • Misrepresenting platform support, device capability or test results
  • Submitting bad-faith contributions or intentional misinformation
  • Other conduct that could reasonably be considered inappropriate in a professional setting

​
Technical Honesty

TomorrowOS is built around real-world capability mapping. Contributors must not mark a feature as supported unless it has been tested, evidenced or clearly documented. Where support depends on an operating system, firmware version, device model, browser engine, native bridge, hardware capability or customer environment, that limitation should be documented clearly. Examples include:
  • Playback support
  • Image and video transitions
  • ZIP or widget package support
  • Device control APIs
  • Proof-of-play
  • Synchronisation
  • Screenshots
  • Storage limits
  • Network behaviour
  • Fallback and recovery logic
If something is uncertain, it should be marked as unknown, partial, model-dependent, firmware-dependent or requires-bridge rather than presented as fully supported.

​
Security and Responsible Device Control

TomorrowOS may touch local APIs, device control, playback surfaces, screen state, content packages and telemetry. Contributors must take extra care when working with:
  • Remote commands
  • Local device APIs
  • ZIP or widget package handling
  • Authentication
  • Access tokens
  • Device credentials
  • Logs
  • Screenshots
  • Customer environments
  • Proof-of-play or proof-of-display data
Security issues must not be raised publicly. Please follow the process in SECURITY.md.

​
Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing standards of acceptable behaviour. Maintainers have the right and responsibility to remove, edit or reject comments, commits, code, documentation, issues, pull requests and other contributions that are not aligned with this Code of Conduct. Maintainers may also take action where contributions create safety risks, misrepresent platform support, expose sensitive information or weaken trust in the project. Where appropriate, maintainers will communicate the reason for moderation decisions.

​
Scope

This Code of Conduct applies within all TomorrowOS community spaces. This includes:
  • GitHub issues
  • Pull requests
  • Discussions
  • Documentation
  • Community forums
  • Project chats
  • Official social media
  • Events
  • Any situation where someone is officially representing TomorrowOS

​
Enforcement

Instances of abusive, harassing or otherwise unacceptable behaviour may be reported to the project maintainers. For now, reports can be sent to: