> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/journal/20210910-freebsd-kai-fa/events-calendar.md).

# 活动日历

* 原文链接：[Events Calendar](https://freebsdfoundation.org/wp-content/uploads/2021/11/SeptOct_events_calendar.pdf)
* 作者：**ANNE DICKISON**

截至 2021 年 12 月的 BSD 活动。请将未在此处列出的任何 FreeBSD 相关活动或对 FreeBSD 用户有意义的活动详情发送至 <freebsd-doc@FreeBSD.org>。

## OpenZFS 开发者峰会 2021

11 月 8-9 日

线上

第九届年度 OpenZFS 开发者峰会将于 11 月 8-9 日（周一至周二）线上举行。本次活动旨在促进 OpenZFS 工作的跨社区讨论，并推进一些已提议的项目。这场为期两天的活动包括一天的演讲和一天的 hackathon。

## 2021 年 11 月 FreeBSD 供应商峰会

11 月 18-19 日

线上

欢迎参加 2021 年 11 月线上 FreeBSD 供应商峰会。本次活动将包含半天的线上会议环节，于 2021 年 11 月 18-19 日举行。活动免费参加，但我们要求通过 eventbrite 系统注册，以获得会议室和独立的走廊讨论区访问权限。除厂商演讲外，我们还会安排讨论环节。

## FreeBSD Fridays

<https://freebsdfoundation.org/freebsd-fridays/>

下一期 FreeBSD Fridays 将于 12 月举行。敬请期待！往期 FreeBSD Fridays 内容可在以下地址查看：<https://freebsdfoundation.org/freebsd-fridays/>

## FreeBSD Office Hours

<https://wiki.freebsd.org/OfficeHours>

加入 FreeBSD 社区成员参加 FreeBSD Office Hours。从综合问答到基于主题的演示和教程，Office Hours 是解答你 FreeBSD 相关问题的好去处。

往期内容可在 FreeBSD YouTube 频道查看：<https://www.youtube.com/c/FreeBSDProject>。


---

# 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://book.bsdcn.org/journal/20210910-freebsd-kai-fa/events-calendar.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.
