> 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/maintain-open-source-culture.md). # Maintain Open Source Culture It can be intimidating initially if you are mentoring an open source group for the first time. Be it teaching a large number of mentees from across the globe, or answering their questions, or scheduling meetings considering the different time zones of mentees– the method of training is different than classroom training. So, always maintain the culture when you are teaching in an environment, as Bill S. Preston Esq says—“Stick to the Open Source Culture : Be excellent to each other.” Open source development is truly global. All cultures, all languages, all time zones, and all continents--yes, even Antarctica. * It is asynchronous in nature. Most collaboration is done via email, forum posts, mailing lists, and pull requests. * Cooperation and consensus building is the greatest challenge. * Because other people can’t see your face or hear your voice, emotions are lost and intent muddled. --- # 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/maintain-open-source-culture.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.