How to Communicate with the Cobalt Team
Stay organized with collections
Save and categorize content based on your preferences.
We have several communication channels that we actively support, each for
different purposes.
Filing Bugs and Feature Requests
If you have identified a bug in Cobalt common code - meaning that you don't
expect that it is related to a platform or port implementation quirk, then you
should file a bug on our public issue tracker.
Additionally, if you have specific feature requests, you can also file them on
our public tracker, but they should be very concrete and well-specified. If
unsure, ask about your request on cobalt-dev first.
File a new Cobalt Bug
View all Open Cobalt Bugs
You will need a valid Google account to post. You can create a Google
account with a non-gmail
address (say, your work email address).
We also encourage contributions by sending pull requests on Github, especially
if the bugfix or feature addition is small, well tested, and follows
our contribution guidelines.
Asking about Schedules, Discussing Features, Announcements, and Miscellany
We also have a dedicated mailing list, cobalt-dev@googlegroups.com. If you are
spending time with Cobalt, you may want to subscribe. And if you have a concern
that doesn't fit into the above categories, asking about it on cobalt-dev is a
reasonable course of action.
Use this mailing list for asking related technical questions about Starboard or
Cobalt. We encourage searching through archives both in mailing list and bug
tracker for prior questions.
If your issue seems like a bug or is really a feature request, use the Issue
Tracker to file it.
cobalt-dev@googlegroups.com
cobalt-dev web interface
YouTube Topics
If you are using Cobalt for YouTube on your device, and have YouTube-specific
questions, you should contact your YouTube technical account manager
directly. The above forums are Cobalt-specific, but not YouTube-specific. The
Cobalt engineering team can't speak on behalf of Google or YouTube.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-09-03 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eCobalt supports various communication channels for different purposes, including bug reporting, feature requests, and general discussions.\u003c/p\u003e\n"],["\u003cp\u003eUtilize the public issue tracker for filing bugs and feature requests related to Cobalt common code.\u003c/p\u003e\n"],["\u003cp\u003eEngage in the cobalt-dev mailing list for discussions, schedules, announcements, and technical questions about Cobalt or Starboard.\u003c/p\u003e\n"],["\u003cp\u003eFor YouTube-specific inquiries, contact your YouTube technical account manager directly as Cobalt channels are not YouTube-specific.\u003c/p\u003e\n"]]],["Bugs and feature requests for Cobalt common code should be filed on the public issue tracker, ensuring they are concrete and well-specified. Small, tested bug fixes or features can be submitted as pull requests on GitHub, following contribution guidelines. For general questions, technical discussions, or announcements, use the cobalt-dev mailing list. YouTube-specific issues should be directed to your YouTube technical account manager, not the Cobalt forums. Always search archives for prior questions before posting.\n"],null,["We have several communication channels that we actively support, each for\ndifferent purposes.\n\nFiling Bugs and Feature Requests\n\nIf you have identified a bug in Cobalt common code - meaning that you don't\nexpect that it is related to a platform or port implementation quirk, then you\nshould file a bug on our public issue tracker.\n\nAdditionally, if you have specific feature requests, you can also file them on\nour public tracker, but they should be very concrete and well-specified. If\nunsure, ask about your request on cobalt-dev first.\n\n[File a new Cobalt Bug](https://issuetracker.google.com/issues/new?component=181120)\n\n[View all Open Cobalt Bugs](https://issuetracker.google.com/issues?q=componentid:181120%20status:open)\n\n*You will need a valid Google account to post. You can [create a Google\naccount](https://accounts.google.com/SignUpWithoutGmail) with a non-gmail\naddress (say, your work email address).*\n\nWe also encourage contributions by sending pull requests on Github, especially\nif the bugfix or feature addition is small, well tested, and [follows\nour contribution guidelines](https://github.com/youtube/cobalt/blob/main/CONTRIBUTING.md).\n\nAsking about Schedules, Discussing Features, Announcements, and Miscellany\n\nWe also have a dedicated mailing list, cobalt-dev@googlegroups.com. If you are\nspending time with Cobalt, you may want to subscribe. And if you have a concern\nthat doesn't fit into the above categories, asking about it on cobalt-dev is a\nreasonable course of action.\n\nUse this mailing list for asking related technical questions about Starboard or\nCobalt. We encourage searching through archives both in mailing list and bug\ntracker for prior questions.\n\nIf your issue seems like a bug or is really a feature request, use the Issue\nTracker to file it.\n\n[cobalt-dev@googlegroups.com](/youtube/cobalt/docs/cobalt-dev@googlegroups.com)\n\n[cobalt-dev web interface](https://groups.google.com/forum/#!forum/cobalt-dev)\n\nYouTube Topics\n\nIf you are using Cobalt for YouTube on your device, and have YouTube-specific\nquestions, you should contact your YouTube technical account manager\ndirectly. The above forums are Cobalt-specific, but not YouTube-specific. The\nCobalt engineering team can't speak on behalf of Google or YouTube."]]
