Join the community

Choose the public channel that best matches your content, and make sure the information is reproducible and sanitized.

• Ask installation, configuration, certificate discovery, or automatic-update questions in Q&A
• Report consistently reproducible defects in Issues
• Describe feature, upstream, or deployment-target requests in Ideas
• Share real deployment steps and solutions in Show and tell
• Point out documentation that is inaccurate, outdated, or easy to misunderstand

A clear scope makes your information easier for maintainers and other users to understand and reuse.

• Search the documentation, Discussions, and Issues first
• State the clmbot version, operating system, CPU architecture, and deployment target
• Separate the expected result, actual result, and methods already tried
• Remove AccessKey, AccessSecret, private keys, customer domains, internal addresses, and other sensitive information

Use Discussions for questions, open ideas, and experience sharing. Use Issues for reproducible defects or well-scoped work items. Because the source code is not public, the repository does not currently accept pull requests for product code.

You may request support for certificate services, devices, or deployment targets that are not listed. Include the product name and version, official documentation, certificate format, authentication method, deployment or reload mechanism, and a description of an environment that can be used for validation.

Maintainers classify submissions based on reproduction details, security impact, breadth of use, and the conditions required for adaptation. They may request more information. Community support is best effort and does not promise a fixed response time or processing order.

• Q&A: after a useful answer is posted, the author can mark the most helpful response
• Ideas: after the user scenario, scope, and acceptance result are clear, an idea may become an Issue
• Bug: after reproduction is confirmed, the defect enters issue tracking with its impact documented
• Security: vulnerability details move immediately to a private channel and are not discussed publicly

The clmbot and clmbot.org source code is not currently public. The project plans to publish source code in the future, but no timeline or license has been announced. Rely on formal announcements on the website and GitHub.