> 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/organization-dashboard/learn-about-lfx-data.md). # Learn About LFX Data Sources, Features, and Future Developments The **LFX Organization Dashboard** aggregates data for your company's employees, providing a summary and detailed view of their contributions, event attendance, training, and more. ### **Data Sources and Aggregation** The Organization Dashboard pulls data from various sources. Data sources vary depending on the data type. #### Events Event registration, attendance, speaker status, sponsorships, and audience reach. * **Cvent:** The Linux Foundation uses this tool to manage events. ### Training and Certifications Education started or completed by individuals is attributed to their employer. This affiliation is not dependent on whether the employer paid for the training. * **LF Education:** This data is sourced from the user activity on the LF Education Training Portal and Exam platform. ### Code Contributions **LFX Contributor Types** The LFX uses the following definitions to categorize contributors: * **Committer**: A person who has performed various activities, including commits, reviews, and pull request actions. * **Maintainer**: A person is considered a maintainer if they meet one of the following conditions: * They have merged or closed a pull request created by someone else. * They are listed as a maintainer in a project's documentation, as specified in the "Maintainer" file in GitHub, GitLab, Git, or Gerrit. * **Reviewer**: A person who has reviewed code, including activities such as commenting on pull requests or reviewing threads. * **Other Contributor**: A person who has made non-commit code contributions, such as creating issues, commenting on code, or merging pull requests. ### **Contributor Data Sources** The LFX collects contribution data for LF open source projects from various sources and affiliates contributors to their employers. This data is then combined into a single profile. **Public Data Sources** We gather publicly-available data from the following sources: * **GitHub, GitLab, Git, and Gerrit**: Publicly-visible contributor profiles and contribution history. * **LinkedIn**: Employer history and dates of employment, which helps us accurately affiliate contributors to their employers. ### **Commitment to Privacy** The LF takes data privacy seriously and is transparent about our practices. You can learn more about our commitment to privacy [here](https://www.linuxfoundation.org/legal/privacy-policy). ### **Future Developments** The LFX intends to expand the scope of the data sources in the future to include critical open source projects not hosted by the LF. --- # 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/organization-dashboard/learn-about-lfx-data.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.