> 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/20180708-da-shu-ju/events-calendar.md).

# 活动日历

* 作者：**ANNE DICKISON** 与 **DRU LAVIGNE**

以下 BSD 相关会议将于 2018 年 8 月和 9 月举行。

## USENIX Security ‘18

8 月 15–17 日

美国马里兰州巴尔的摩

<https://www.usenix.org/conference/usenixsecurity18>

第 27 届 USENIX 安全研讨会汇聚研究人员、从业者、系统管理员、系统程序员，以及其他关注计算机系统与网络安全和隐私最新进展的人士。

## BSDCam 2018

8 月 15–17 日

英国剑桥

<https://bsdcam.cl.cam.ac.uk>

2018 年剑桥 FreeBSD 开发者峰会（BSDCam）将于 2018 年 8 月 15-17 日在英国剑桥举行。本次活动以“非会议风格”运行，我们在第一天上午集体讨论实际日程安排，重点关注反映与会者兴趣并发挥其知识的互动话题。

## Write the Docs+Open Help

8 月 18-22 日

美国俄亥俄州辛辛那提

<http://www.writethedocs.org/conf/cincinnati/2018/>

一场专注于软件文档各方面的会议。

## FOSSCON

8 月 25 日

美国宾夕法尼亚州费城

<https://fosscon.us>

一年一度的自由及开源软件会议，在宾夕法尼亚州费城举行，FOSSCON 汇聚了来自各个领域的自由及开源软件用户。

## OpenZFS 开发者峰会

9 月 10–11 日

美国加利福尼亚州旧金山

<http://open-zfs.org/wiki/OpenZFS_Developer_Summit>

第六届年度 OpenZFS 开发者峰会将于 2018 年 9 月 10-11 日在旧金山举行。与往届一样，本次活动旨在促进 OpenZFS 工作的跨社区讨论，并推动一些已提议的项目取得进展。本次为期 2 天的活动包括一天的演讲和一天的编程马拉松。

## EuroBSDCon 2018

9 月 20–23 日

罗马尼亚布加勒斯特

<https://2018.eurobsdcon.org>

EuroBSDcon 是欧洲年度技术会议，汇聚使用和开发 4.4BSD（Berkeley Software Distribution）家族操作系统及相关项目的用户和开发者。

## Grace Hopper 2018

9 月 26–28 日

美国得克萨斯州休斯敦

<https://ghc.anitab.org/2018-attend/>

Grace Hopper Celebration 是世界上规模最大的女性技术从业者聚会。由 AnitaB.org 主办，并与 ACM 合作举办。


---

# 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/20180708-da-shu-ju/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.
