> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/zh/general-guides/community/community-call.md).

# #Community Call

如何參與每月社群治理會議 Community Call

每月的[社群治理會議](https://blog.like.co/en/tag/community-call/)於 #Community Call 頻道公開舉行，任何人都歡迎參與。

會議日期及內容請參看：

{% content-ref url="/pages/-MHG5LvRyu16yOMuf99\_" %}
[社群治理會議](https://docs.v2.like.co/zh/general-guides/governance/community-call.md)
{% endcontent-ref %}

參與會議的方法很簡單：

1\. 到 LikeCoin Discord 點 #Communty Call 頻道參與會議。

![#Communty Call 頻道](https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FdKRkP6mEgIxSlSikym9l%2FCommunity%20Call%201.png?alt=media\&token=2e2adc60-67c4-4c38-8c7f-cbf5e1b43489)

2\. 並非發言時請保持靜音。

![靜音按鍵](https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FxKdWXl7YHrCJPIsPC2x7%2FCommunity%20Call%202.png?alt=media\&token=9234b6c9-fc12-4f1b-99d7-8c2091eab446)

3\. 點右上角顯示聊天。

![點擊進行聊天](https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2Fhfru6Tw6gYqzvaC3x2ba%2FCommunity%20Call%203.png?alt=media\&token=da34701f-a335-4585-acfc-22f001063b36)

4\. 在會議時可輸入文字內容聊天。

![輸入文字內容聊天](https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FL9Twq0lLT699ydhf1AlU%2FCommunity%20Call%204.png?alt=media\&token=d6f52af8-409c-444f-86d7-0a44905f84c7)

5\. 會議完結後亦可在 #📞｜community-call-discussion 頻道跟進各項事宜。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v2.like.co/zh/general-guides/community/community-call.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
