Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
To use the Community Management interface, follow these steps:
Open your browser and visit the Community Management URL. Sign in with your credentials.
You will be redirected to My Project Groups in CM.
On the My Project Groups, you can see your project groups. If you don't see your project, raise a support ticket on the support portal.
Privacy Matters To Us: Only Linux Foundation employees will have access to LFX Community Management.
Manage the settings of your project groups in CM
On the project group card, click Settings CTA.
On the Manage Projects page, you can either scroll down or use the search box to see the projects listed under your project group.
If you do not see certain projects or subprojects listed in CM, then contact the onboarding team to add that project.
You cannot add or delete the projects or sub-projects in your project groups.
Select the project for which you want to integrate the data sources.
Click Manage Integrations CTA.
On the INTEGRATIONS page, select the data source that you want to integrate and follow the integration steps.
On the project group card, click Project(s) CTA.
On the Project Groups page, you can see all the onboarded project groups and your project groups.
It is designed to give you a quick overview of your projects and help you navigate the tool easily.
On the Project Groups page, you will see the following tabs:
Explore Project Details
After selecting the project, you'll be directed to its dedicated page or details within the tool. Here, you can view information, manage integrations, access data, and perform various actions related to that project.
On the top left corner of the home page, you will find a search box labeled Select project group.
Start typing the name of the project you are looking for into the search box.
As you type, the tool will begin displaying a list of suggested projects that match your search query.
Once you see the desired project in the search suggestions, click on its name. The tool will either directly open that project or take you to its specific page or details within the tool's interface.
Community Management is a Customer Data Platform(CDP) tool which collects and stores customer data from across the communities in a single database for data unification, identity resolution, analysis, and activation.
By utilizing this tool, we can effectively identify key contributors and organizations, facilitating more efficient community support
Key points:
It consolidates developers' touchpoints with a company or brand.
It captures data from community platforms, product channels, and commercial channels.
The data is cleaned, and profiles are matched across platforms and enriched with third-party data.
The platform provides a unified 360-degree view of developers' engagement, their companies, and their customer journey.
Why Community Management?
Data-Driven Insights: CM provides comprehensive analytics for a clear understanding of community engagement and contributor behavior across multiple platforms
Efficient Management: Simplifies complex data, aiding in decision-making and efficient community management and support
Contributor and Organization Identification: Identifies not only key individual contributors, but also top-contributing organizations, recognizing where most active participants are affiliated
Cross-Platform Integration: Tracks interactions across various platforms like GitHub, X, etc., offering a holistic view of the community's activities
Better data helps us better support our community members!
To get started for free, sign up for Community Management.
Welcome to Community Management tool
Community Management (CM) is simplifying complex data for better decision-making. It tracks contributor interactions across platforms like GitHub, Git, Groups.io and Twitter, providing analytics-driven insights and identifying key contributors and organizations for effective community support.
To get started, refer to this quick start guide.
Visit the https://cm.lfx.dev/ login page.
Enter your credentials (username and password). If you don't have access, raise a support ticket on the support portal.
To see the data flowing on your CM portal, connect a few data sources.
It is preferable to use multiple data sources; however, if you start with only one, we recommend GitHub since it has a lot of developers' data, which we enhance by adding more data points for your use.
Once logged in, you will see the projects to which you have access under the My Project Groups tab. Raise support ticket on the support portal. if you do not see your project cards for your projects.
Click Settings button under the project group that you want to onboard
Click Manage Integrations for the project you want to onboard.
Connect your preferred data sources to start pulling information. For more information, see Integrations. If you need assistance, contact the onboarding team for further guidance.
Once the data sources are integrated, your workspace will soon be populated with your contacts and organization pages.
The Settings CTA on the project cards is available only if you have admin access to your project. You cannot edit project settings for other project groups. If you don't see Settings button for your projects raise support ticket on the support portal.
From the Project Groups page, click the View Project(s) CTA to explore details. For more information, see Home Page.
Click Overview link to find
Most active and most recent contributors
New organizations and the most active organizations.
New activities and top activities
From the left navigation, click Contributors to explore and edit contributors on the dedicated Contributors page. Explore contributors based on affiliation, engagement, and time of contribution, or create your contributor report. You can also click on individual contributors to see more details about contributors; such as location, work experience, list of contributor's activities, etc.
From the left navigation, click Organizations to gain insights into contributing organizations. Explore these Organizations in terms of contributions and number of contributors, or search organizations by name. You can also click on individual organizations to see more details about this org, like description, list of contributors, list of activities for this org, etc.
From the left navigation, click Activities to see a list of activities for the selected project, with the ability to filter them by various criteria.
From the left navigation, click Reports to see default reports about Contributors, Organizations, and Activities, or create your report.
Congratulations! You've successfully navigated through the initial steps of Community Management.
If you have any questions or need further assistance, refer to the help documentation or contact our support team.
Data integration helps the flow of data between systems, enabling you to access data from different sources within a Community Management, which will connect your project data sources to work together seamlessly within your community management tool.
Connect Gerrit to sync documentation activities from your repos.
On the INTEGRATIONS page, you will see all the connectors. Scroll down and check the Gerrit connector.
Click Connect.
On the pop-up window, enter the following details to connect the remote URL to the Gerrit repository that you want to connect to:
Enter your Organization's URL
Enter your project name
Enter your Username
Enter project key
Click Connect.
Verify Gerrit is connected
Activities Collected:
Change sets and change set comments
Patch sets and patch set comments
Follow these steps to integrate Github:
On the home page, search for the project group.
On the project card, click Settings.
On the MANAGE PROJECTS page, scroll down to see the listed projects.
Select the project, and click Manage Integrations CTA.
On the INTEGRATIONS page, you will see all the connectors. Check the GitHub connector.
Click Connect. On the pop-up window, click I'm the GitHub organization admin CTA.
Only GitHub users with admin permissions can connect to CM's GitHub integration. If you are an organization member, you will need approval from the GitHub workspace admin.
On the GitHub page, install LFX CM to connect project repositories for the data integration.
Once you complete the integration, the data will start syncing from the connected repositories.
After GitHub is connected, hover over (1) to see the list of repositories.
Add each of these repositories to their associated project under Git integration.
Activities Collected:
Stars/Un-stars
Forks
Issues
Pull requests
Discussions
Comments on issues/pull requests/discussions
Closing of issues/pull requests/discussions
After completing the GitHub integration, complete the Git integration.
Git repositories are not automatically connected when you do Git integration. You need to manually enter each Git repository URL.
On the INTEGRATIONS page, you will see all the connectors. Check for the Git connector.
Click Connect. On the pop-up window, enter remote URLs for each repository that you want to connect.
Click +Add remote URL to add multiple repositories. Click Connect.
Activities Collected:
Commits
On the INTEGRATIONS page, locate the Reddit integration.
Click Connect.
On the pop-up window, enter community subreddit name and CM will automatically check if subreddit name exists
Click Connect
You will be redirected to Reddit, asking you to accept LFX CM app. Click on Allow, and it is done!
Activities collected:
Posts published on a specified subreddit
(Nested) Comments on all posts
Limitations:
Limited historical import (maximum of 1000 posts in the past per subreddit)
Not tracking upvotes of posts and comments.
Connect Groups.io to sync groups and topics activity.
On the INTEGRATIONS page, you will see all the connectors. Scroll down and check the Groups.io connector.
Click Connect.
On the pop-up window, you need to authenticate your groups.io account that you want to connect. You must be a group owner to authenticate.
Enter the Email ID and the password, and click Verify Account.
After verification, add the groups name that you want to track under Connect groups.
Click Connect.
Verify if the groups.io integration is successfully completed on the Integration page.
Activities Collected:
Messages/emails
Member joining and leaving mailing groups
On the INTEGRATIONS page, you will see all the connectors. Scroll down and check the Confluence connector.
Click Connect.
On the pop-up window, enter the following details to connect the remote URL to the Confluence repository that you want to connect to:
Click +Add remote URL to add multiple repositories. Click Connect.
Verify if the confluence integration is completed on the Integration page.
Activities Collected:
Page created and updated
Comments
Attachments
Slack integration tracks the following activities:
Follow these steps to integrate Slack:
On the INTEGRATIONS page, locate the Slack integration.
Click Connect.
Click Allow.
Activities Collected:
Member joining a channel
Messages
Replies in threads
On the INTEGRATIONS page, locate the X/Twitter integration.
Click Connect.
On the pop-up window, click Authorize App CTA.
Activities Collected:
Tweets
Limitations:
Only one X/Twitter account/handle per integration
We can track only one hashtag per integration (planning to add more)
No ability to track tweets by keyword. Tweet will be tracked/collected only if it has either used X/Twitter account/handle mentioned or includes tracked hashtag
No stats about tweets, like number of views, comments, retweets or likes
No follower information or any other stats about X/Twitter account
Connect Discord to sync messages, threads, forum channels, and new joiners.
On the INTEGRATIONS page, locate the Discord integration.
Click Connect.
Select the Server from the dropdown.
Click Continue.
Activities Collected:
When someone joins a server
Messages
Replies (in threads)
Limitations:
Not tracking reactions
Not tracking when someone leaves a server
The Cvent integration already enabled and requiring no additional configuration, facilitates the automatic appearance of events from Cvent under the projects in CM.
This is achieved through a series of steps involving data transfer from Cvent to LFX and, subsequently, from LFX to CM via an API.
Steps
Data Transfer from Cvent to LFX: Cvent sends event data to LFX.
Integration between LFX and CM: An integration has been established between LFX and CM.
Data Push to CM: The integration pushes these events from LFX to CM through an API.
Data Appearance in CM: The event data, which includes details such as attendees’ or speakers’ names, the name of the event, and the date of the registration, automatically appears under the projects in CM.
Connect LinkedIn to sync comments and reactions from your organization's posts
Follow these steps to complete LinkedIn integration:
On the INTEGRATIONS page, locate the LinkedIn integration.
Click Connect.
Enter your LinkedIn credentials when prompted and click Sign In.
Authorize our LinkedIn app to ensure the integration works properly.
In the next step, a drawer opens, and you need to select which organizations' page you want to track. Once you've selected an organization from the select box, click Update.
Once authenticated, you'll be redirected back to the INTEGRATIONS page with the LinkedIn integration now listed as Connected.
Comments on posts
Reactions on posts
Not tracked
Followers
Mentions
The integration for Training and Certification (T&C) is already active, requiring no further setup.
This integration ensures that enrollments and certifications from Thought Industries, our Learning Management System (LMS), are automatically displayed under the projects section in CM.
Integration Setup: An integration has been established between Thought Industries and CM.
Data Transfer: T&C activities are sent from Thought Industries to CM using an API.
Data Display in CM: The T&C activities, which include details such as the learner’s names, the names of the T&C products learners have enrolled in or received certification for, the dates of enrollment or certification achievement, and links to the certificates, are automatically displayed under the projects section in CM.
CM is supporting 3 access levels to accommodate different roles and responsibilities within a community:
Admin Access: Full control over all projects, including the ability to manage settings, add/edit integrations, and edit contributors for all projects. Admins can also merge contributors and organizations in CM.
CM Manager Access: Ability to manage settings, add/edit integrations, and edit contributors for one or a limited number of projects. This role includes "read-only" permissions to view and explore contributors, organizations, and activity/contribution data for all projects. These users cannot merge contributors and organizations.
Viewer Access: Allows users to view contributor, organization, and activity/contribution data with "read-only" permissions for all projects.
CM uses the same SSO system as other LFX products. A valid LF Account grants access to CM and access to a project in PCC automatically gives access to the same project in CM. This integration ensures a seamless user experience across LFX platforms.
Contact the Support team and specify which project your peers need access to, along with their email and LF Account.
To onboard a data source into CM, you need CM Manager Access within CM for managing the onboarding process, along with admin-level permissions for the data source you're integrating. For example, GitHub Onboarding requires Admin access to your GitHub organization because the onboarding process involves installing the CM GitHub application, which is essential for CM to collect data from GitHub.
If you lack access to a required tool or platform for integration:
Find someone who has the necessary access and request that they either give you admin rights or share their login credentials with you.
Alternatively, you can reach out to the CM Support team and ask for temporary access for the person who has the needed access. This will enable them to log in to CM and set up the integration.
If you're experiencing issues with project permissions, such as not being able to see or edit integrations, contact the Support team for assistance.
In case some sub-projects do not appearing in CM, reach out to the Onboarding team for support. They can assist in adding these missing projects or sub-projects to CM.
In CM, if you have "edit" access to your project, you can modify integrations for that particular project. However, for all other projects, you will have "viewer" access, which is limited to read-only and does not permit any modifications.
If a project is present in PCC but does not automatically appear in CM, you should contact the onboarding team for assistance. They can facilitate adding the missing project to CM. This approach is applicable if a project is no longer relevant, needs to be hidden, or has been moved under a different project.
The time it takes for data to appear in CM varies depending on the size of the projects and the type of integration.
Small Projects: Data typically appears within a couple of hours.
Medium Projects: Data visibility ranges from a few hours to a day.
Large Projects: It can take a couple of days for data to be visible.
X-Large Projects: Data from very large projects, such as GitHub repositories with tens of thousands of commits and PRs, may take a few days to a few weeks to show up.
There are several reasons for differences between the data in CM and GitHub itself, including:
Bot Account Exclusion: CM does not collect data from bot accounts or contributions made by these accounts. In some cases, bot activities can account for as much as 50% of the total activities in a GitHub repository.
Data Delay: It is typical for CM to experience a delay in data collection. This delay can range from a few hours to a few days.
If data still isn't appearing after 24 hours after onboarding or enabling new integration, reach out to the Onboarding team for assistance.
Contributors' details are gathered from the information they provide on platforms like GitHub, Twitter, Slack, etc., and from their LinkedIn profiles.
An enrichment service is used to gather information about contributors' LinkedIn profiles and work history using their email and/or GitHub usernames.
To resolve this, ensure that Git integration is enabled for all repositories added in the GitHub or Gerrit integration. Data will not appear in Insights until this Git integration is enabled. It's important to note that if a repository is not added to Git, Insights will not display data for it, regardless of whether GitHub integration is enabled and synced. To improve this process, there is a plan to introduce a feature that automatically populates Git integration based on the GitHub integration settings. If you are uncertain about the integration status, it is advisable to enable GitHub integration and seek assistance from the Onboarding Team.
An enrichment service regularly updates each contributor shortly after they are added to CM and every few months thereafter. Some contributors may not be found in the enrichment databases and therefore will not be enriched.
Check if integrations for your projects are set up correctly. If you do not have access to see and manage integrations, contact the Onboarding Team. Check if you have set the correct filter options. For example, you may be looking at data for the entire Foundation instead of a single project and may need to add a Project Filter. If the data is still incorrect, contact the Onboarding team.
Yes, after organizations and contributors are added to CM, they undergo enrichment through a dedicated service. This service enhances their profiles with additional details such as work history, location, organization logos, descriptions, and more.
If you find inaccuracies in the enriched data for contributors or organizations, you have the option to manually edit and update this information. These manual updates will not be overridden by subsequent enrichment processes.
Duplicates in organizations often occur due to varying information sources, such as LinkedIn or inputs from contributors, leading to slight differences in organization names. CM team is proactively working on merging these duplicates through automatic and manual processes. However, some duplicates might still exist. Efforts are underway to develop a feature that will allow users to merge these duplicate organizations themselves.
In CM, contributors might have accounts on different platforms like GitHub, Git, Twitter, Slack, etc., known as “Identities.” Sometimes, a contributor uses the same name on multiple platforms, causing duplicates in CM. To solve this, CM uses an auto-merge feature to combine these identities.
We also manually merge identities, especially for top contributors or when requested. However, you might still see duplicate contributors in CM. We’re developing a “merge” feature that will let users merge contributors, helping to remove these duplicates.
In CM, a GitHub identity encompasses a user's GitHub profile, including their name, GitHub ID, logo, and public details like company information. Conversely, a Git identity is more basic, typically consisting of just the name and email address as they appear in the Git log.
Default auto-affiliation, derived from sources like LinkedIn or GitHub identities, represents a user's general work history without specific start and end dates. Manual affiliation, or project-level affiliation, is an alternative used to specifically link a developer's activities to a particular project, ideal for correcting or fine-tuning affiliations.
Our testing includes both automated and manual methods. We use an internal QA automation framework for high-level validation of data from most onboarded repositories, primarily for platforms like GitHub. For detailed scrutiny, such as with groups.io, we conduct manual testing to ensure the accuracy and completeness of the data integration.
Merge suggestions for organizations and contributors are based on their similarities. For organizations, suggestions consider similarities in names and domains. For contributors, the suggestions are based on names and email addresses.
To ensure the integrity and accuracy of our data management, we have decided to restrict the task of organization and contributor merges exclusively to our internal team. This decision is due to the irreversible nature of these merges – currently, we lack a straightforward method to cleanly reverse or unmerge them once completed. We believe this approach is essential to maintain the quality and reliability of our organizational data.
Merging two contributors or organizations involves choosing a primary profile. For contributors, some details like the name and profile picture are taken from the primary profile, while others like work history, emails, and activities are combined from both profiles. For organizations, certain information like the logo, domain, and description are from the primary organization, while other details are merged. Note that organization merges are irreversible, and contributor merges are partially reversible but require manual intervention. For manual individual contributor unmerges, requests can be made in CM.
An automatic "unmerge" feature for contributors and organizations is planned, allowing users to reverse previous merges. We are also developing an audit log to track individual merges.
The Onboarding team plays a crucial role in helping projects and maintainers integrate their work with the CM tool. They can be reached for support via the Slack channel 'lfx-insights-onboarding-support' or through a Jira ticket.