> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/collaborations/committees.md).

# Committees

### Overview

The committee set up for a project is designed to streamline communication and task delegation. This guide covers various aspects of committee management, including:

* **Manage Mailing List**: Essential for effective communication among committee members.
* **Manage Meetings**: Organize and track committee meetings for optimal collaboration.
* **Adding Members**: Process for incorporating new members into the committee.
* **Deleting a Member from a Committee**: Guidelines for removing members when necessary.
* **Deleting a Committee**: Steps to disband a committee when its objectives have been met or in case of restructuring.
* **Committee Overview**: General information and the committee's purpose within the project.

## Committee Overview <a href="#committee-overview" id="committee-overview"></a>

The Committee overview section provides overview information on:

* Total number of committee meetings
* Total number of meeting attendees
* Committee List table


---

# 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.linuxfoundation.org/lfx/project-control-center/v2-latest-version/collaborations/committees.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.