> 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/mentorship/mentor-guide/participant-roles.md). # Participant Roles Following are various types of roles for the mentorship program: ### **Mentor** This is You— community members who guide mentees. Mentors help mentees learn open source development by providing thorough guidance. In addition to that, mentors also help contributors to integrate into project communities, and refer mentees to potential employers. ### **Program Administrator** Program administrators are the individuals who enroll the mentorship programs. They can be employees of Linux Foundation, and manage the entire program, and take a wide range of responsibilities, such as creating and analyzing the program evaluations, ensuring that mentees are paid on time, ensuring that mentors and mentees are in sync throughout the program, responding to inquiries, and so on. ### **Mentee** Mentee is a college or university student, or an active developer who wants to learn open source software development. Mentees must be at least 18 years of age to enroll into this mentorship program. Mentees come from diverse academic, geographical, and social backgrounds.So, keeping in mind that mentees come from diverse backgrounds, set a universal tone while communicating with mentees throughout the learning 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/mentorship/mentor-guide/participant-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.