> 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/my-profile/profile/community-roles.md). # Community Roles To view the roles you hold or have been elected to as an active member of the open-source community, follow these steps: 1. Log in to 2. Scroll down to the **Community** **Roles** section. The **Community** **Roles** are populated automatically based on the individual's assigned roles in different project communities. You can view the following information for each role: * Project Name for which you have the role * Committee Name * Role names, such as Lead, Chair, LF Staff, and so on * Start and end date associated with the role If you are a point of contact on behalf of your company, which is a partner of the Linux Foundation and its projects, then your role in the context of your employer's participation in the project is also displayed. These roles are assigned by your company administrator during the membership enrollment process.

--- # 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/my-profile/profile/community-roles.md?ask=&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.