Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Linux Foundation is a technology association of several companies that help scale open source projects. The Linux Foundation provides platforms to support the sustainability of the open source ecosystem by providing various services, events, and training.
LFX is a suite of tools built by the Linux Foundation to facilitate every aspect of open source development. The toolkit operationalizes the organization’s proven methodology for transforming projects into category leaders, providing direct support to projects, and empowering open source developers to write better, more secure code and grow sustainable ecosystems.\
The world runs on open source, and projects need more than a version control or source control system to scale. The Linux Foundation has developed a proven methodology to transform projects into category leaders. LFX operationalizes this approach, providing a suite of tools built to facilitate every aspect of open source development.
Available tools include...
Insights give you complete visibility into project performance and ecosystem trends. Understand your contributor community and make informed decisions with our analytics and reporting tools.
Security (Beta Available) gives you more visibility into your project's security by automatically monitoring thousands of open source repositories for possible vulnerabilities and weaknesses.
Individual Dashboard is your self-service hub for all of your open source activity. Build your profile, manage your credentials and contact details, update your affiliations, and track your community participation all in one place.
EasyCLA streamlines the management and execution of Contributor License Agreements (CLAs) so you can stay compliant with project policies.
Mentorship Streamline the process of connecting up-and-coming open source contributors with seasoned mentors. By investing in this effort, you can foster a more robust, diverse pool of skilled developers and engineers.
Crowdfunding makes it possible for open source projects to raise money from individuals and organizations who believe in what they're building. Projects receive 100% of donations and manage their funds.
Project Control Center (Limited Access Beta Early 2021) provides seamless operations support across governance, IT, and product management needs so you can focus on getting the work done.
The Organization Dashboard, also referred to as the company dashboard, serves as a central location to manage and track your organization's open source activities.
If you're developing or supporting open source projects under the Linux Foundation, you have access to several useful tools. Just sign in with your LFID to begin.
Other tools, including Crowdfunding and Mentorship, provide valuable resources to community projects and the extended open source community.
The LFX tools are provided as a value to developers and sponsors of open source projects hosted by the Linux Foundation. The platform does not charge any fees for open source projects.
Log in to Project Control Center (PCC) using your Linux Foundation account and follow the step-by-step instructions. The application process takes just a few minutes, and then the LFX team will review your submission. You’ll receive communication from us once the project setup is completed.
Note: Only project maintainers or collaborators with administrative control can set up a project in LFX.
LFX supports one maintainer per project at this time. This user serves as the administrator of the project within the platform.
The Linux Foundation's SSO service provides secure access and protects the identities of all its community members. The Linux Foundation's SSO service secures systems and services like Events Registration, Training and Certification, Jenkins, JIRA, Confluence, Crowdfunding, Mentorship, EasyCLA, Insights, and Security.
To create an account and log in, you need an email address. You can also sign in using third-party authentication service providers such as Google, Facebook, GitHub, and LinkedIn.
When you log in to a program or a tool for a project, you will likely be asked to create your LF account.
The LF account you will create will also allow you to authenticate using services like Google, LinkedIn, Facebook, and GitHub in addition to your username and password.
For example, if you sign up for or log in to your mailing list via the Groups.io web portal, you will be asked to log in through the new SSO interface and create an LF account if you don't have one.
The SSO helps to secure your access to a service, whether it is registering for an event, subscribing to a mailing list, or accessing a community meeting or webinar.
In addition to increased security, it is also a greater convenience. Since you already use the identity provider for your common workflows, you have one less password to remember and can often sign in quickly depending on the browser or client you are using.
You can view emails associated with your LF Account at your Individual Dashboard at https://myprofile.lfx.linuxfoundation.org/.
On the Individual Dashboard, you can also:
View which email addresses are associated with your LF Account
View the username for your LF Account
View the Identity Providers (IdPs) you have enabled
If you're experiencing an issue, you can create a ticket that will be addressed by our product support team by navigating to: https://support.linuxfoundation.org
The Individual Dashboard (also known as My Profile) is a self-service hub for all of your open source activity. Using the dashboard, you can:
Build your personal community profile.
Manage credentials and contact details.
Display badges for completing certifications and other accomplishments.
A seamless login experience across the major systems used by the Linux Foundation projects.
Most importantly, the Linux Foundation values your privacy and your ability to control your data. Share what you want to share, and keep private what you wish.
Information in your profile is subjected to the Linux Foundation's Privacy Policy.
The Linux Foundation values your privacy and does not share or use your data for marketing.
When you log in for the first time to any Linux Foundation-managed service that is protected with Single Sign On (SSO), you must create an account. To create an LF account, follow these steps:
1. Navigate to the LFX Platform and click CREATE LFX PROFILE (2) at the top right corner of the main menu. Alternatively, you can also click the Create Your LFX Profile (3) link from the page. If you already have an LF profile, click My LF Profile (1) to go to the next page.
2. On the SIGN IN page, click Create an account to create an LF account. If you already have an LF account, then enter your username or Email ID and password. Click SIGN IN to continue with your LF Account.
You can also sign in using one of the options given on the SIGNIN page. For more information, see Sign-in options.
3. On the CREATE YOUR ACCOUNT page, enter your first name, last name, Email address, username, and password. Click the Create Account CTA button.
4. You will receive a verification link to verify your account on your email address. If you do not receive the email, click the Resend Email CTA button.
5. Check your inbox for mail from The Linux Foundation:Create Account
email and open it. Click Verify Email CTA button. Below is an example of the email you will receive.
6. Once you click on the link, you will be redirected to the Sign In page of the Linux Foundation service you are trying to access. Your email and password will be auto-populated from the account creation step.
7. Verify your information and click SIGN IN CTA button. You will be navigated to the Linux Foundation service you are trying to access.
You can use your Facebook login to access the protected Linux Foundation service instead of creating an LF account. The first time, you will enter your Facebook credentials to authenticate your account. Subsequent logins will just require a click on the Facebook icon. This one-click approach simplifies the login process.
1. On the SSO page, click on the Facebook icon to continue to sign in with your Facebook account.
2. Enter your Facebook login credentials, and click Log In.
3. If you have an existing LF account, the Linux Foundation will map it to your Facebook login. If you don't have an LF Account associated with the email address you're using, you will be navigated to Create your LF Account page.
4. Enter username, and click Create Account. You will be redirected to the Linux Foundation tool page that you are trying to access.
This username will be your new LF Account username, and will be synced with your email address.
You can use your Gmail login to access the protected Linux Foundation service. The first time, you'll enter your Gmail credentials to authenticate your Google account. Afterward, you can simply click the Google icon to sign in, streamlining the login process.
1. On the SSO Sign In page, click on the Google icon to sign in with your Google account.
2. Enter your email address and click Next.
3. Enter your password and click Next.
4. If you don't have an LF Account associated with the email address you're using, you will be navigated to Create your LF Account page.
5. Enter your username, and click on the Create Account CTA button. You will be redirected to the Linux Foundation service page that you are trying to access.
This username will be your new LF account username and will be synced with your email address.
You can use your GitHub login credentials to sign in to the protected Linux Foundation service instead of creating an LF account. The first time you sign in, you will enter your GitHub credentials to authenticate your GitHub account. Subsequent logins will not require you to enter the credentials⏤you will simply click the GitHub icon to sign in. This one-click approach simplifies your login process.
1. On the SSO login page, click on the GitHub icon to sign in with your GitHub account.
2. Enter your GitHub login credentials and click on Sign in CTA icon.
You will be presented with the two-factor authentication page if your account has two-factor authentication turned on. Based on your choice of delivery mechanism, you may receive authentication code via email or text on your device.
4. After entering the authentication code, you will be able access the Linux Foundation service. If you already have an existing LF account, the Linux Foundation will map it to your GitHub login.
5. If you don't have an LF Account associated with the email address you're using, you will be navigated to Create your LF Account page.
6. Enter username, and click on Create Account CTA button. You will be redirected to the Linux Foundation service page that you are trying to access.
This username will be your new LF Account username, and will be synced with your email address.
To access the Linux Foundation's tools, you must sign in using your LF account credentials. If you already have an LF account, use your credentials to sign in. If you just created a new account, follow these steps:
1. On the Sign In window, enter your SSO account credentials and click SIGN IN.
2. The Single Sign-On service allows users to authenticate with social and external authentication providers instead of a username and a password.
3. When using an external authentication provider, you will be prompted to create a username if you don't have an existing username.
4. If you create your LF account by signing in with an external authentication provider, the Linux Foundation will map your LF account to the external login.
Learn more about using external secure authentication systems to log in to the Linux Foundation services:
Follow these steps to reset your password.
Note: A password change invalidates any of your active sessions for the secure services you are currently logged in to, so you need to sign in again to restore your settings.
1. On the Sign In page, click the Forgot Password? link.
2. Enter your email address or username and click Reset Password.
3. You will receive a verification link to verify your account on your email address. If you don't receive the email, click Did not Receive Link CTA button.
4. Check your inbox for a The Linux Foundation: Reset Password
email, and click on the Reset Password CTA button. You will be navigated to a page where you can reset your password.
6. Enter a new password, confirm it and and click on the Submit CTA button to view a confirmation that your password is reset successfully.
Get your questions answered simply by reading the documentation, or get help by creating a ticket with the Linux Foundation support team.
At the bottom of the Sign-in page, you will see two options:
Click Contact Us to navigate the product support page to create a ticket with the Linux Foundation support team.
Complete the form and click Send. You will receive a confirmation email with your ticket number and request description.
Click Read Documentation to read the user documentation.
Navigate to the top-right corner of the main navigation bar, and from the My Profile drop-down, click Logout.
1. To manage your profile, after signing in select Manage Profile from My Profile dropdown.
2. For details on profile management, please see Individual Dashboard (MyProfile).
You can use your LinkedIn login credentials to sign in to the protected Linux Foundation service instead of creating an LF account. The first time you sign in, you will enter your LinkedIn credentials to authenticate your LinkedIn account. Subsequent logins will not require you to enter the credentials⏤you will simply click the LinkedIn icon to sign in. This one-click approach simplifies your login process.
1. On the SSO login page, click on the LinkedIn icon to sign in with your LinkedIn account.
2. Enter your LinkedIn login credentials, and click on Sign in CTA icon.
4. If you have an existing LF account, the Linux Foundation will map it to you LinkedIn login. If you don't have an LF Account associated with the email address you're using, you will be navigated to Create your LF Account page.
5. Enter username, and click on Create Account CTA button. You will be redirected to the Linux Foundation service page that you are trying to access.
This username will be your new LF Account username, and will be synced with your email address.
Individual Dashboard is your self-service hub for all of your open-source activity. Build your personal community profile, manage credentials and contact details, display badges for completing certifications and other accomplishments, and enjoy a seamless login experience across the major systems used by the Linux Foundation projects.
For more information, visit our website.
Release notes for the Individual Dashboard and APIs can be found at https://github.com/LF-Engineering/myprofile/releases.
Getting Started With Individual Dashboard
When you log in to https://openprofile.dev, the Home page is your default landing page. This is your starting point, offering a snapshot of your profile and recent activities.
On the Individual Dashboard, you can access Events, register for visa letters, raise travel funding requests, access your meeting details and host keys, manage your email IDs, training and certification, etc.
Release date: 31 January 2023
This section provides you with a list of new features, updates, and bug fixes for this release.
The following list provides an overview of new features implemented in this release:
Email Management - new Email Management page is added.
The Email Management URL is changed.
The following list provides new updates to the existing features:
The Email Management is updated for LF staff in V.0.6.26.
User Interface labels and design have been updated.
The following list provides you with the bug fixes that are applied in this release:
NA
You can visit the following links for more information on Individual Dashboard:
The Home page is your default landing page. This is your starting point, offering a snapshot of your profile and recent activities.
The Home page also includes quick links or shortcuts to frequently used features and the LFX tools within your dashboard. These shortcuts can help you navigate more efficiently.
You must register for the event before raising a visa letter or a travel funding request.
From the left-side navigation pane, navigate to EVENTS>LF Events.
To view your upcoming events, select the Upcoming tab.
Click Register to navigate to the Linux Foundation events page and explore events.
On the Past Meetings tab, you can view past events that you have already attended or that have expired.
Visa letters are required for events that involve international participants. These letters are official documentation to support visa applications, assisting attendees in obtaining the necessary travel documentation to enter the host country.
On the MY EVENTS page, click the Visa Letters tab. Click the New Letter Application CTA to access the application page.
Follow the step-by-step procedure to complete the application and submit your application.
A travel funding request is a formal request made by an individual or group to a funding source, such as an employer or organization, to pay the expenses of attending an event, such as travel, accommodation, meals, and registration fees.
On the MY EVENTS page, click the Travel Funding tab. Click the New Funding Application CTA to access the application page. For a step-by-step procedure, see Travel Funding Guide.
This section provides you with a list of new features, updates, and bug fixes for this release.
The following list provides an overview of the new features implemented in this release:
Visa Request: new visa request page is added.
Travel Funding Request: new travel funding request page is added.
The following list provides new updates to the existing features:
The Visa letter request application flow is integrated.
The travel funding form is integrated.
The following list provides you with the bug fixes that are applied in this release:
NA
You can visit the following links for more information on Individual Dashboard:
On the left navigation pane of the Individual Dashboard, you will see the Profile section. Navigating through the various options on this page will help you get acquainted with your dashboard.
Here you can build your profile, add something about yourself, your contributions, the projects you support, the training that you have completed, the certificates you received, your skill sets, and your badges, and change your profile photos. Moreover, you can keep your profile either private or visible to your community.
After completing your LFX profile, if you do not see your details on the Profile page, click Request Addition to raise a support ticket.
Streamline your meetings with the My Meetings feature
Get organized and boost productivity with our Meetings Hub! See what’s coming up and review past meetings with notes and recordings—all in one place.
Maximize efficiency, elevate collaboration, and stay ahead with easy access to crucial meeting details.
You can view your meetings in List View and Calendar View.
One super exciting feature that you will find here is the notification of upcoming meetings and the Join Meeting CTA. This ensures that you never miss an important meeting.
On the My Meetings Page, you will find all your upcoming meetings under the Upcoming Meetings tab. Click on the meeting to check the meeting details, such as the meeting agenda passcode, meeting links, passcode, meeting IDs, etc.
You will find all the past meeting recordings and transcripts under the Past Meetings tab.
For more information, read the .
For more information, see .
This page presents a data analytics dashboard highlighting my contributions to various open-source projects over a selected period.
It includes detailed metrics and visualizations to help understand the impact and scope of my involvement in the open-source community.
To see your open source project contributions on My Insights, you must connect at least one identity to the data source.
Explore the purchase feature in the left navigation
The purchase feature is designed to enhance your experience by allowing you to view training coupons and transactions, purchase subscriptions, and enroll as an individual supporter. Here's how you can navigate through it:
Click the Purchase> Coupons feature in the left navigation.
In My Rewards, you can view all your training coupons.
Under the Purchase feature, go to the Transactions tab.
Here, you can see a comprehensive history of all your transactions.
You will find a section for Linux.com Email Subscriptions within the Purchase feature.
Click on this section and follow the prompts to purchase a subscription to Linux.com emails.
In the Purchase feature, look for the Enroll as an Individual Supporter section.
Click on this section and follow the instructions to enroll and show your support for the community.
The Settings feature of your Individual Dashboard allows you to manage your account information and preferences. The feature includes the following sub-features:
You can view and edit your basic account information such as name, email address, phone number, current organization, and address.
Go to Settings>Password to change your current password.
If you forgot your password, click Send Password Reset Link CTA to receive a reset link to your preferred email address.
The Email Management page helps you manage your emails more efficiently.
Go to Settings>Email Management to add your primary email address and emails for meeting invitations.
For more information, see Email Management.
When you connect to your LinkedIn account, your open source contributions are automatically affiliated, or you can manually populate your work history.
Your work history may be populated based on your profile. You need to connect and sync your LinkedIn account.
Go to Settings>My Work History page to add your work experience.
This sub-feature allows you to control the visibility of your profile to other users. For more information, see Manage Profile Visibility.
After you log in to https://openprofile.dev, the Home page is your default landing page. This is your starting point, offering a snapshot of your profile and recent activities.
The Home page also includes quick links or shortcuts to frequently used features or sections within your dashboard. These shortcuts can help you navigate more efficiently.
As you explore your dashboard further, you can always return to the Home page by clicking on the Home option in the left navigation menu.
On the left navigation pane of the individual dashboard, you will see the Profile section. Navigating through the various options on this page will help you get acquainted with your Individual Dashboard.
The My Profile section provides details, such as your name, profile image, your organization's name, your role in the organization, an introduction about you, and technical and social accounts that are highlighted if you have connected any of them with your Linux Foundation account.
The status shows your profile's progress. It shows the steps that are required to be completed before profile completion.
Connect your GitHub and LinkedIn accounts to complete your profile. After completing the profile, you will receive a discount coupon worth 50% discount for LF training or certification on your profile under My Rewards> Coupons.
Click LEARN MORE to complete your profile.
2. On the next pop-up window, click Get Started.
3. To claim your contributions, link your GitHub and LinkedIn accounts. Click Link GitHub Account to connect and authorize your GitHub account. After linking, you can claim your code contributions. Click Set up later if you do not want to link your accounts.
4. Click Connect LinkedIn to complete your profile. Connecting to LinkedIn will Quickly populate your work history through LinkedIn and verify that your technical contributions match up with your employers.
Click REVIEW EMAIL ADDRESSES to review all the email addresses that you use to contribute or want to associate with your open-source profile.
Click Add Email Address to add your other Email addresses.
The About Me section provides a rich markdown editor where you can write some interesting facts and information about yourself that reflect your interests, influence, or contributions to the open source community.
Click Get Started to write about yourself and your open source work experience.
Click Save to save your information.
The Linux Foundation values your privacy and does not share or use your data for marketing.
From the right side pane of the window, you can view and manage profile visibility, view, and complete profile completion details, view any upcoming Linux Foundation events that you have registered for, and many more.
On the right side panel, you can see basic details, such as your profile image, your organization name, designation, and location. Click the pencil icon to navigate to the Basic Information section to make changes.
Below the basic details section, the icons of social accounts (LinkedIn) and technical accounts such as GitHub are listed. The icons are greyed or highlighted depending on their configuration. Connect your LinkedIn and Git accounts to add your open-source experience to your profile.
Connecting with LinkedIn and GitHub is the fastest and easiest way to affiliate your open-source contributions with your employment history. Your contributions are retrieved and displayed based on your unique usernames and email addresses that you have used to contribute to the open-source community.
Your affiliations also get published to LFX Insights Community Dashboards and your Organization Dashboards, highlighting your efforts to your employer.
To connect your LinkedIn account with your LF account, follow these steps:
On the LinkedIn login page, enter your credentials. Click Sign in.
3. Review the Settings > My Work History page that displays your work history based on the work experience you have provided in your LinkedIn account.
To connect your GitHub account with your LF account, follow these steps:
On the next page, authorize your GitHub account.
To showcase your contribution on your open source profile, you can connect multiple GitHub accounts.
This section displays if your profile is public or private. Click the pencil icon to navigate to the Profile Visibility section to make changes. The URL includes the individual dashboard URL and your unique username, in the format https://myprofile.dev.platform.linuxfoundation.org/profile/{{
unique_username
}}
Your Ideas Matter: Please give us feedback to improve
Your ideas matter! Click anywhere on the Feedback card on the Individual Dashboard to share your thoughts and suggestions.
Help us shape the future of our community by providing your valuable feedback.
Quick Start Guide:
Click: Tap anywhere on the Feedback card to get started.
Submit: Enter your email address and click the Submit button to share your thoughts!
Your input helps in our growth and helps us make your experience even better. Join us in making a difference!
Thank you for being a crucial part of our community's journey!
Your LFX Profile is your entry point to our open collaboration portal. To avail the discounts on training and certifications, you need to complete your profile. Once you complete your profile, you can:
showcase your open-source participation.
access all of our LFX tools
review your open-source meeting recordings and transcripts
earn rewards
and more
To set up your LFX profile, you need to complete the following three steps:
You can see your profile completion progress on the left navigation pane of the individual dashboard.
When you create your LF account and enter your Name and Email addresses, you complete the first step.
Click Claim Code Contributions to link your GitHub account to verify your contributions and identify your maintainer badges. You can continue to connect your LinkedIn account and complete step 3 or follow the next step.
3. Click Link Work History to connect your LinkedIn account and link your work history. After connecting to your LinkedIn account, confirm your employment history and add your project affiliations.
4. Click Save & Continue to add your project affiliations.
5. Click Save & Continue. On the next page, If you have contributed to open source using any other email addresses, add them here.
6. Click Done. Now that your account has been set up, you’re all set to start collaborating.
Upon successful completion, you will receive a notification of your reward points.
On the top right corner of the Individual Dashboard, you will see the Tools menu. Click to explore our other LFX tools such as; Insights to learn about projects you care about, mentorship to increase your impact as a mentor, or learn about open source as a mentee, or Security.
From the right-side pane of the window, you can view the badges that you have earned and your skill sets.
The Badges pane shows the digital community badges that you have earned. Your expertise may be published on LFX Insights Community Dashboards and Organization Dashboards, recognizing your efforts.
In the future, you can add non-Linux Foundation badges to your profile. Community badges are generated from the following sources:
Digital badges are generated from the following sources:
For the Linux Foundation Certifications, you have successfully passed.
For speaking engagements at various Linux Foundation Events or participation in program committees for these events.
Individual enrollments in projects.
Using this section, you can highlight your skills in open source and also become a mentor for people who want to follow you and learn from you. Your expertise may be published on LFX Insights and LFX Mentorship, recognizing your efforts.
To add or remove your skill sets:
3. On the Skills subpage, click +Add Another Skill, type your skill set in the search box, and select the skills from the displayed list.
4. To remove or edit a skill set, click the pencil icon, and then click the cross mark next to an added skill.
3. On the Skills subpage, enter your skill set and select the skill from the displayed list.
4. Click +Add Another Skill to add another skill to the list.
shows that the Email address is your primary Email address.
Click icon to edit About Me section if you want to update your information.
Click icon on the profile complete page.
Click icon on the profile completion page.
Share: On the page, click the Submit idea CTA to tell us your ideas, suggestions, or feedback.
Note: Clicking on a badge will take you to the page where you can see to whom the badge has been issued, and you can verify the badge.
1. Log in to .
2. From the right-side pane of the window, scroll down to the Skills section and click icon.
This section lets you add or update an open-source event that you attended as a speaker. You can add any open-source events outside of the Linux Foundation as well. Adding your speaking experience greatly enhances your profile in the open-source community.
To add an event that you attended as a speaker, follow these steps:
Provide event details such as title, date of the event, presentation file, and youtube URL if there is any, and click Submit.
The following screen is displayed when you add one or more events that you attended as a speaker. You can edit or delete an event by clicking the edit (pencil icon) or delete icon on the event name.
Click icon to Add Speaking Experience.
This section displays your contribution history to the open source projects, depending upon the configuration (the technical account you have connected). If you have not connected any of the accounts, it displays the options to connect. Click Connect to GitHub or Connect to LinkedIn to connect to the respective accounts.
Technical contributions also get published to LFX Insights Community Dashboards, recognizing your efforts.
For the configured or connected Git accounts, this section shows:
Projects you are contributing to or have contributed in the past.
Contribution history for the last 12 months displays your monthly contribution to a project on a daily basis. The green-colored small rectangular boxesrepresent less or more contributions you have made to the open source projects on a particular day.
This section displays the Linux Foundation certifications that you have acquired after successfully completing the certification programs.
Your open source industry certifications issued by the Linux Foundation are automatically discovered. Your expertise may be published on LFX Insights Community dashboards and your Organization dashboards, recognizing your efforts.
In the future, you can publish industry certifications from other non-Linux Foundation entities.
You can view the certifications you have completed.
Log in to https://openprofile.dev
To view completed certifications, scroll down to the Linux Foundation & Project Issued Certifications section. If your certification names are not displaying, click Request Addition to submit a ticket to get it added on your profile page.
To view the roles you hold or have been elected to as an active member of the open-source community, follow these steps:
Log in to https://openprofile.dev
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.
Supported projects include individual annual memberships.
You can view the projects that you support by enrolling as an individual supporter.
Log in to https://openprofile.dev
Scroll down to the Supported Projects section.
It displays the project name and the date when you enrolled as an individual supporter.
My Meetings provides you with a list of upcoming and past meetings. My Meetings also allows you to view past meeting recordings and transcript copies of the meetings.
You can view meetings in List View and Calendar View.
You can access My Meetings from the Individual Dashboard.
To access My Meetings, follow these steps:
Log into My Profile using your LF account, and from the left-side navigation pane, click Meetings.
You can view upcoming and past meetings in the List View.
To view meetings in List View, perform the following steps:
Log into My Profile using your LF account, and from the left side navigation pane, click Meetings.
On the My Meetings page, select List View.
Under the Upcoming Meetings tab, you can view the list of meetings that provide details such as Next Meeting details, Project, and Title of the meeting.
Click the Edit icon to change the meeting invitation email settings.
On the top of the MY MEETINGS page, you can see the upcoming meetings notifications. Click Join Meeting CTA to join the meeting.
Under the Past Meetings tab, you can view a list of past meetings that provides details such as Date, Project, Title, Recording, Transcript, and Passcode.
On the Upcoming Meetings tab, you will see the list of meetings.
Click on the meeting row to see the meeting details.
On the Meeting Details pop-up window, you will see the following details:
1. Zoom link that you can copy and share.
2. Resend Invitation CTA.
3. Add to Calendar CTA.
The calendar view provides details of the scheduled meetings on a calendar. The number of meetings planned for the day is shown on the date and day of the calendar. A table with details of the meetings is also available to check the following information related to the discussion:
Time of the meeting
Meeting Name
Number of participants in the meeting
Status of the attendance
You can categorize the meetings based on:
All upcoming meetings
Recurring meetings
Non-recurring meetings
Past meetings
To view meetings in List View, perform the following steps:
Log into My Profile using your LF account, and from the left navigation pane, click Meetings.
On the My Meetings page, select Calendar View.
Your participation in open source training hosted by the Linux Foundation is automatically discovered. Your learning may be published on LFX Insights Community dashboards and your Organization dashboards, recognizing your efforts.
The section will display the following details:
Training course name and date of enrollment.
If you have not enrolled into trainings, the Take Advantages of Linux Foundation Training Programs CTA button navigates you to the Linux Foundation Training course catalogues.
If your training enrollments are not displayed, for any reason, Click Request Addition to raise a support ticket to get your training enrollment added to your profile.
This page presents a data analytics dashboard highlighting my contributions to various open-source projects over a selected period.
It includes detailed metrics and visualizations to help understand the impact and scope of my involvement in the open-source community.
Follow these steps to analyze your contributions to open-source projects using the Insights dashboard:
Select a Project: At the top of the dashboard, select the project you want to analyze from the drop-down. By default, metrics are displayed for ALL Projects
.
Choose a Period: Next to the project dropdown, you can select the period for which you want the data to be analyzed.
Overview Section
This section gives you a broad perspective on your contributions.
Contributions Trend: This graph displays the number of contributions you've made during the selected period, along with the total commits per active day. This metric helps in evaluating your activity and consistency.
Productivity Metrics: Under this category, you will see the data on your overall contribution, including total commits, issues raised, pull requests, and lines of code. This information is key to understanding what and how much you contribute.
Details Section
Dive deeper into specifics with these metrics:
Projects We Contribute Code To: Here, you can see a detailed breakdown of your contributions to various projects.
Work Time Distribution: This metric shows how your contributions are distributed over time, allowing you to understand your work patterns better and plan your participation in projects more effectively.
Major Open Source Projects
The dashboard lists the two most popular open source projects with the maximum contributions. If you want, you can contribute to these projects.
By following these steps and analyzing the provided metrics, you can gain valuable insights into your open-source project contributions, identify areas for improvement, and better plan your future involvement.
On the My Events page, you have the following tabs:
Upcoming
Past
Visa Letters
Travel Funding
view the past events that you have already attended or that have expired, select the Past tab.
To view your upcoming events, select the Upcoming tab.
Click Register to navigate to the Linux Foundation events page to explore events.
In this section, you can view the following event details:
Event name
Event location
Event dates and duration
Event role, participant role, such as attendee, speaker, sponsor, and so on.
A travel funding request is a formal request made by an individual or group to a funding source, such as an employer or organization, to pay the expenses of attending an event, such as travel, accommodation, meals, and registration fees.
The request includes a detailed budget and justification for the request.
The funding source assesses the request based on various factors, including budget and significance to their objectives.
The decision to approve or deny the request depends on the funding source's evaluation of the request.
To apply for the new fund requests, follow these steps:
Navigate to the Individual Dashboard login page.
Enter your login credentials and sign in. For more information, see the Sign in to Your Account page. If your login credentials are correct, you will be directed to the main dashboard or home page of the web UI.
From the left-side navigation pane, navigate to EVENTS>LF Events.
On the MY EVENTS page, click the Travel Funding tab. Click the New Funding Application CTA to access the application page.
5. On the Travel Funding Application page, scroll down and check the event that you want to attend. Click the Select button to choose the event. After selecting the event, click Next.
6. On the Terms and Conditions page, read the terms and conditions for the visa application and click Next.
Click the Cancel button if you want to cancel your new travel fund application.
Click the Previous Step button to go back to the event selection page.
For questions, please contact travelfund@linuxfoundation.org.
7. On the About Me page, fill out the following information to complete the application. Click Next Step.
8. Click Next Step. On the Expenses, fill in your expense details and submit the application.
Once you submit your request, you can see your application status on the Travel Funding page.
Once your request is approved by the event team, you can see the status change as Approved on the Travel Funding page.
Community events are non-LF events that the Linux Foundation can sponsor if proper justification is provided. You can raise a travel funding request on the LF Events page.
To apply for the new fund requests, follow these steps:
On the MY EVENTS page, click the Travel Funding tab. Click the New Funding Application CTA to access the application page.
On the Travel Funding Application page, scroll down and select the Community Event. Click Next.
On the Terms and Conditions page, read the terms and conditions for the visa application and click Next.
On the About Me page, fill out the following information to complete the application:
Click Next Step.
On the Expenses page, fill in your expense details and submit the application.
In the Purchases section, you can:
Check the earned coupons that you have gained when you purchased any events, training, or certifications from the Linux Foundation.
Earn reward points when you purchase any training and certification products. For every $1.00 spent on training and certification products, you earn 1 point. You need a minimum of 500 reward points to redeem a discount coupon.
View the transactions related to the purchases you have made through the Linux Foundation.
View the Individual Enrollments.
Purchase a Linux.com email.
The Coupons section provides a list of training, certifications, or events for which you are eligible to claim coupons using the coupon codes.
You can use these coupon codes by redeeming the reward points.
This section provides details of the training, certifications, events, discounts, and reward points you can redeem.
Earned coupons allow you to claim a discount for training, certifications, and events. You are eligible for earned coupons:
If you have previously registered for any event or purchased any training or certifications from the Linux Foundation, For example, if you have registered for an event, say the Cloud Native conference, you will receive an earned coupon for that.
If you have purchased any training and certification products. You earn 1 point for every $1 spent on training and certification products. You can redeem a coupon by using these reward points.
You need a minimum of 500 reward points to redeem a coupon.
1. Log in to My Profile using your LF account, and from the left-side navigation pane, navigate to Purchases > Coupons.
2. The Redeemable Coupons section appears with the list of training and certifications for which you are eligible to claim the coupon code. Click the Redeem with 500 Points CTA.
3. A pop-up message appears. Click Claim Code.
Copy the discount code and paste it at checkout on the Training Portal.
The Individual Enrollments page of the individual dashboard lets you view and manage your individual subscriptions as a user. By enrolling as an individual member or supporter, you show support for the Linux Foundation and its projects.
Get big discounts on certification, training, and events.
Individual membership in the Linux Foundation saves you $100 off certification examinations, which you can utilize once.
Log in to https://openprofile.dev.
From the left navigation pane, navigate to Purchases> Individual Enrollments.
From the list of the available projects , click Enroll as an Invidual Supporter CTA to enroll.
On the Member Enrollment page, enter you contact details and click Next.
On the next page, enter your oder details and payment information.
confirm your purchase.
For each project, you can have one of the below individual status:
If you have never enrolled in that certain project. You can take the step and enroll from this page.
Enrolled and Expired
If your enrollment have been expired, and you didn't renew it. You can take the step and renew from this page.
Enrolled and Expiring Soon
If your enrollment will expire within 30 days, and you have disabled the Auto renew. You can activate the auto renew from this page to ensure the continues of your membership and its benefits.
Enrolled and Active
If your enrollment is active and the auto renew is enabled.
In this case you will have your membership to be renewed automatically.
3. Auto Renew:
Auto renew is a toggle to enable or disable the yearly automatic renewal on your behalf.
Enabling the auto renew, will automatically renew your next cycle before it will be expired in 1 day.
Disabling the auto renew, allow you to renew manually.
6. To view all individual projects that you have enrolled in from my profile.
2. From the left-side navigation pane, navigate to ABOUT ME > Email Management > Linux.com Email.
3. Click Purchase Email.
3. After you have completed the transaction, go to your account on My Profile Dashboard and navigate to ABOUT ME > Email Management > Linux.com Email page to request the linux.com alias and add the forwarding email address.
Note:
You can request any Linux.com email address, but issuance is subject to availability.
Emails sent to the Linux.com email alias will be sent to the forwarding email address you specify. They will not be sent to the linux.com email alias.
You cannot edit the linux.com email alias after you purchase the linux.com alias email; however, you can anytime edit the forwarding email.
You can purchase a lifetime Linux.com email alias if you are an active individual supporter. For more information on individual supporters, see web page.
1. Log in to .
4. On the page, you will be navigated to Lifetime Linux.com Email Alias Add-On form if you are enrolled in the Individual Supporter program. You need to enroll in the Individual Supporter Program before you can purchase a Linux.com email alias.
To access the Settings feature, follow these steps:
Log in to your Individual Dashboard.
Click on the Settings icon located on the left navigation pane.
Select the sub-feature you want to manage from the left-hand menu.
Access the "Data Visibility" settings to customize who can view specific elements of your profile.
Access the "Data Visibility" settings to customize who can view specific elements of your profile. You can adjust your privacy settings according to your preferences. your data will either be visible or hidden based on your preference.
To view your transactions for all the purchases you made through the Linux Foundation:
In this section, you can view the following transaction details:
All Transactions
Event Tickets Training and Certifications
Individual Support and Linux.com Purchase
In this section, you can view the following transaction details:
Name, which is the name of the product, event, training, or certification course
Order ID number, which is also displayed on the order confirmation email
Transaction Date
Transaction Status, i.e. Completed
Transaction Value, which provides the purchase amount
All Transactions provides the transaction details related to all the transactions.
Event tickets provide transaction details related to the event.
Training and Certifications provide the transaction details related to training and certifications.
Individual Supporter Program and Linux.com Purchase provide transaction details related to the individual support program and Linux.com purchases.
Log into using your LF account, and from the left-side navigation pane, navigate to Purchases > Transactions.
Currently, LF Project Administrators can gain access to community management in our new version of Insights. To gain access, create a support ticket and provide the following details:
Your LFID.
Your email registered with this LFID.
The Project you need access to.
2. In Community Management, mark your project’s maintainers as a maintainer by selecting the 3 dots to the right and selecting Add Maintainer Tag.
3. The maintainer tag should now be shown in the Community Management dashboard.
Reach out to Craig Ross at,ccr@linuxfoundation.org
and we can assist projects with designing their own Credly Badges.
The following template mock-ups are available for project maintainers:
Once your maintainers are identified in Community Management and you have issued your maintainers a badge via Credly.
We are all aware that an open source maintainer's work is important to the success of our open source projects. When the code is not resolved, they resolve it. Similarly, when the code is not reviewed, they review it. Maintainers are the maestros of an open source opera.
It is reasonable that our maintainers are acknowledged and valued. As a result, LFX has added support for maintainer Credly badges on the Individual Dashboard.
For our maintainers, the process is simple. Follow these simple steps:
Navigate to the Individual Dashboard, and sign in using your LF account.
Maintainer badges are verified through your GitHub identities, so ensure your GitHub identities are connected to your LFX Profile. For more information, see connect GitHub.
Skip step 2 if you are already connected to you GitHub account.
Congratulations, that's all! We will now verify that you are a maintainer by cross-checking your project's maintainer documentation on the back end. Our maintainer badge validation process takes 7 days. You will be notified.
Tux Rewards Membership is our loyalty program that rewards you for purchasing training and certification from us! There is no fee, and it’s easy to join! You earn 1 point for every $1 spent with us, up to 500 per day. 500 points earn you a 50% off coupon code to be used toward (1) one course, certification exam, bundle, or boot camp.
Connect your GitHub and LinkedIn accounts to receive a 50% discount coupon for LF training or certification.
This is a one-time reward, and you can get a maximum of 500 reward points.
If you already have 500 reward points applied to your profile or have been previously rewarded 500 points, you will not qualify for these new 500 points.
Complete the following steps:
Connect to your Github account. You can connect as many Github accounts as you like, but the reward point will be granted only once per identity.
Populate your work history by connecting your LinkedIn account.
Complete your project affiliations. This ensures that you have some code contributions (at least 1) that you can affiliate with some organizations or as an individual.
The reward points are awarded to a single LF profile.
The coupon for 50% off is generated as soon as the above conditions are met. You can link your accounts independently and then perform affiliations later.
When you spend $500 with us, you will be automatically enrolled as a Tux Rewards member.
If you spent $500 or more with us between October 11, 2019, and October 11, 21 you will be automatically enrolled in the Tux Rewards program and receive a 50% discount coupon code to be used toward all courses, certification exams, bundles, and boot camps.
A refunded order will disqualify that order from counting toward your Tux Rewards balance.
You can claim your benefits online directly from your user profile. In addition, you will receive emails alerting you to exclusive member offers throughout the year!
How to Redeem Your Coupon Code:
1. Sign in to MyProfile from the Linux Foundation website using your LFID.
2. On the left navigation pane, click Rewards > Coupons.
3. On the My Coupons subpage, you can view a list of coupons, discounts, and promotions associated with your account.
4. Click on Redeemable Coupons to claim the coupon code.
5. Once you finish generating the coupon code, go to the Training and Certification catalog select the product you are interested in purchasing, choose to enroll, and log into your Linux Foundation account. Then paste the coupon code into the box and proceed through the rest of the checkout process.
6. If you experience issues with your coupon code, please click the orange ‘Get Help’ button on the top right corner of your MyProfile Dashboard.
To remain enrolled in the Tux Reward program, you will need to make at least one purchase (of any amount) from us every three years.
Tux Rewards points are tied to a single Linux Foundation account and may not be combined.
Tux Rewards points are not accumulated for purchases made with an invoice or when using a redemption code.
Once you earn your Tux Rewards 50% coupon by making a purchase of $500 or more, you have two years to use the coupon code generated.
You earn 1 point for every $1 spent with us, with a max of 500 points earned per day. (If your purchase for 1 day exceeds $500, you will earn 500 points and the amount over $500 will not roll over to another day.)
When you reach 500 points, you will receive a 50% discount coupon that you may use on any new purchase from training.linuxfoundation.org.
Once you make a purchase that qualifies for Tux Rewards points, it may take up to 72 hours for the points to show up in your portal account.
Insights gives you complete visibility into project performance and ecosystem trends. Understand your contributor community and make informed decisions with our analytics and reporting tools.
The new release of Insights is now live with a refreshed user interface and new dashboards that make it easier to navigate and find the information that matters most.
The Email Management page helps you manage your emails more efficiently. Update your email addresses to stay connected with the Linux Foundation and LF-hosted projects.
Email Addresses feature is the standard feature available on the Email Management page.
On this page, you can add all your email addresses that help identify all your technical contributions. You can customize your email settings for different purposes, such as login and basic communication, as well as meeting invitations.
Follow these steps to add your email addresses:
Navigate to Settings > Email Management.
On the EMAIL MANAGEMENT page, enter your email address in the text box and click Add.
After adding your email address, you will receive a verification notification on your email address.
Once you verify your email address, it will be displayed on this page.
A maximum of 10 email addresses can be added to this page.
Follow this step-by-step procedure to efficiently manage your email preferences:
On the EMAIL MANAGEMENT page, you will see a list of email addresses associated with your account.
If you have added only one email address, then by default the same email address will be used for Primary and meeting invitations.
Click on the radio button next to the chosen email address for Meeting Invitations. A checkmark should appear, indicating your selection.
After selecting your preferences, you will receive the following email at your preferred email address.
If you change or modify your email preferences from one email to another, you will get a notification on your old email address.
To change your primary email, repeat the above steps.
To delete your email address, click Delete next to the chosen email address.
You can only delete the email address that you have not selected for any communication preferences. If you have selected your email ID for Primary or meeting invitations, you cannot delete that.
On the pop-up window, click the Delete button.
If you encounter any issues or do not receive the expected emails, ensure the chosen email addresses are valid and properly configured. If you still face the same problem, contact the support team.
You can update your profile information, such as basic information, affiliations, and identities.
To change your basic information, such as name, email address, postal address, and so on:
1. Log in to https://openprofile.dev/
2. Under the Basic Information section, you can update the following details:
First Name: Update your first name.
Last Name: Update your last name.
Pronoun: Select the pronoun from the list.
Current Organization: Add or update your organization.
The organization name is pre-populated based on your profile information.
To add a new organization.
Enter the required organization name, if the name is already available in the date base, it will be listed in the drop-down list. You can select the required name of the organization.
If it is a new organization, you have to click the +Add button.
The Add Organization dialog box appears. Enter the Organization URL of your organization, enter the Organization Name, and click Add.
3. Under the Additional Information section, you can update the following details:
T-Shirt Size: Select your T-shirt size from the Select Size drop-down.
Street: Provide the name of the street as per your postal address where you currently live.
City/District: Provide the name of the city or district where you currently live in.
State/Province: Provide the name of the state or province where you currently live.
Country: Select the name of the country where you currently live in.
Postal Code: Provide the postal code of your residence address where you currently live.
Phone Number: Provide your contact number.
After you finish making the changes, click Save Changes.
If any of your data is inaccurate or needs to be updated, you can reach out to the Linux Foundation Support Team by creating a support ticket.
2. From the left-side navigation pane, click the arrow to expand, and navigate to Settings > Basic Information.
Profile Photo: Click the edit icon next to your profile photo to upload your profile photo.
click the icon from the Current Organization field.
Beta Version
Welcome to Insights, an open-source project analytics tool that empowers you with valuable data-driven insights.
Important: Insights is currently in the beta phase, which means it is actively being developed and refined to provide you with the best experience possible.
Insights is a pre-release software version made available to users for testing and feedback. This means you may encounter occasional changes to the user interface, features, and functionality.
Encourage you to actively participate in the Insights community by providing feedback, reporting bugs, and suggesting improvements.
Your feedback plays a crucial role in shaping the direction of feature development and prioritization.
The tool fetches data from various sources, including your open-source project repositories, and updates this information regularly.
You may see some delays in real-time data because the tool fetches data from various sources.
Note: The Community Management tool focuses exclusively on publicly available GitHub, Git, or Gerrit repositories. Forks and certain repositories are purposely excluded from monitoring to streamline the data integration process.
Date: February 29, 2024
Insights V3 is an open-source analytical tool that provides insights from analyzing open source software (OSS) projects.
Insights V3 helps project leads and technical managers understand their team members' engagement and participation in open source projects, and identify the most active and productive contributors.
No new features have been added in this release.
UI Enhancements
Text changes:
Column names on organization-related tables from 'Name' to 'Organization'.
Column name: Foundation overview -> Project Velocity table from 'Authors' to 'Contributors'.
changed the card description for the Contributions Outside Work Hours component.
Fix column alignment issues on leaderboard tables
Enable the filtering of the table in the Project Velocity section on the Foundation overview page
Fix issues with downloading PNG on the Reports -> Activities page components
Fix the issue with French Polynesia not showing up on the activities by Geographical Distribution metrics
Some of the projects are still onboarding, so the data may not be correct.
The date range filter in the dashboard module may not always display the correct data when selecting custom date ranges.
You may encounter occasional inconsistencies in data synchronization between Insights V3 and external data sources, leading to discrepancies in reporting.
Date: February 22, 2024
Insights V3 is an open-source analytical tool that provides insights from analyzing open-source software (OSS) projects.
Insights V3 helps project leads and technical managers understand their team members' engagement and participation in open-source projects, and identify the most active and productive contributors.
No new features have been added in this release.
Optimized Individual Project Card Data Retrieval: The data fetching for individual project cards has been significantly optimized, resulting in quicker load times and an enhanced user experience.
Enhanced Loading Performance for Foundation -> Projects Page: Loading times for the Foundation > Projects page have been drastically reduced through the implementation of advanced loading techniques, ensuring smoother user navigation.
Integration of DBT Models: All data within Insights V3 now utilize DBT (Data Build Tool) models, offering more scalable and robust data handling capabilities.
Model rendering and performance optimization with Cube Cloud: All dbt models are mapped to cubes and views with defined pre-aggregations in Cube Cloud’s semantic layer, optimizing load times.
Overall System Performance Improvements: A series of system optimizations have been carried out, leading to noticeable improvements in the tool's performance and reliability.
UI Enhancements
Enhanced Responsiveness: We have improved the alignment of cards across various screen sizes for a seamless viewing experience.
Report Filters Redesign: Filters in the Reports section that were previously considered "extra" have now been integrated into the top filter box for easier access.
New Default Period: The default period for viewing data has been updated to the Last 12 months, allowing for more relevant insights.
Color Palette Refresh: The site now follows a new color palette to maintain consistency and enhance visual appeal.
UI Consistency Improvements: Adjustments in alignment, padding, and margins across the platform ensure a unified and more polished look for all cards.
Project Status Indicator: Projects still in the onboarding phase will now be highlighted with a subtle red color for better visibility.
Updated Navigation: Clicking the LFX Logo will now redirect users to the Insights landing page, streamlining navigation.
Clarified Chart Descriptions: The description for the "Contribution outside working hours" chart has been refined for clarity.
Rectify the Best Practices category mismatch issue
Update the tooltip data for the Reports -> Active Contributors chart to reflect the Last 10 Years time range accurately
Ensure the presence of the Hyperledger Foundation logo on the Hyperledger card
Address the rounding-off error in the Software Value calculation
Fix the pagination bug on the Foundation -> Projects page
Eliminate the 100-row loading limit for sub-projects
Some of the projects are still onboarding, so the data may not be correct.
The date range filter in the dashboard module may not always display the correct data when selecting custom date ranges.
You may encounter occasional inconsistencies in data synchronization between Insights V3 and external data sources, leading to discrepancies in reporting.
Insights V3 has a user-friendly interface that is easy to navigate. The tool is designed to be intuitive, which means that you can quickly learn how to use it and start gaining insights from your data.
Insights is the perfect tool for you if you:
Track the performance of open source projects in real time.
Want to analyze data quickly?
Are looking for an online reporting tool.
Want to download the reports in CSV or any other format?
Compare the reports for the selected time period.
Measure the project's growth and the team's performance.
Track historical data to identify trends and patterns.
Detect potential issues early and take corrective actions.
The target audience for Insights can vary depending on its specific features and functionalities. Here are some of the key target audience groups that can benefit from this tool:
Insights is an open source analytical tool that provides insights from analyzing open source software (OSS) projects.
Insights V3 helps project leads and technical managers understand their team members' engagement and participation in open source projects, and identify the most active and productive contributors.
The tool has many features that can be very useful in several ways, such as:
Data Visualization and Reporting: Insights will use data visualization techniques to make it easier to understand the metrics and reports generated by the software.
Code Analysis: Insights V3 analyzes the project's codebase for metrics such as code complexity, and code quality that help project leads and managers identify potential areas for improvement.
Development metrics: Metrics such as commit frequency, pull request acceptance rates, and time-to-resolution for issues can provide insights into the project's development process and help project leads and managers identify areas for improvement.
Integration with other tools: Integration with other tools commonly used in software development, such as Git, GitHub, or Jira, can provide a more competent view of the project's development and make it easier for contributors and managers to track progress.
Customization and flexibility: Providing users with the ability to customize the analytics tool to fit their specific needs and workflows can increase its usefulness and adoption.
To see the detailed definition, click > to expand.
To use the new Insights user interface, follow these steps:
Visit the Insights web URL. You will be redirected to the Insights home page.
The Insights Dashboard is the default dashboard.
You can see all the foundation and project cards on the main page. Alternatively, search the project or a foundation using the Search Bar.
The Landing Page provides all the important analytics about your foundations and projects. It is designed to give you a quick overview of your data and help you navigate the tool easily.
This page focuses on the Foundation Cards and the individual Project Cards, which serve as the core navigational elements, presenting the key data metrics.
Select the Projects and the Foundations: The search box at the top of the main menu helps you find a particular project or repository.
Foundation Cards: Foundation Cards are like summary cards that provide key insights into different open source foundations. When you click on one of these cards, you will be redirected to a Foundation Overview dashboard specifically dedicated to that foundation.
When you click on a foundation card that has only one project, you will be redirected to the Project Overview page.
Project Cards: On the main page, you will see the project cards. Each card represents an individual open source project. When you click on a project card, it takes you to a dedicated Overview Page for that project. These cards show you real-time data about each project, such as important numbers and updates.
On the landing page, the foundation cards are designed to show you real-time data and key metrics related to the foundation and its projects.
A foundation card displays the following key metrics:
When you click on a foundation card, it opens up a Foundation Dashboard dedicated to that foundation. Here, you will find more detailed information about the foundation's contributions to the open source community.
A foundation card has the following details:
It shows the key metrics of the foundation.
Software Value: Constructive Cost Modal (COCOMO) is a procedural cost estimate model for software projects.
Click on a Foundation Card from the Landing Page or search (2) for the foundation using the search box at the top.
Scroll down to see all the listed foundations and projects.
Click on theicon to open the GitHub page of the foundation.
Click on the icon to open the foundation's webpage.
Hover over the to see the inception year of the foundation.
Download Icon: click icon (2) to download the foundation card.
On the Foundation Overview page, you will find the Project Ecosystem Metrics. This section includes two informative charts.
Project Ecosystem Metrics in an open source foundation represent quantitative measurements that provide insights into the health, growth, and diversity of projects within the foundation's ecosystem. These metrics involve data analysis across various dimensions, such as:
Project Maturity Levels: Categorization of projects based on their developmental stage, community engagement, and stability.
Growth Trends: Analysis of the number of projects being accepted over time, indicating the expansion and attraction of the foundation's ecosystem.
Diversity Indices: Evaluation of the diversity within projects and their communities, assessing the inclusiveness and global reach of the foundation's ecosystem.
Sustainability Indicators: Insights into the long-term viability of projects, including funding, resource allocation, and project continuity plans.
Disclaimer: It is not necessary that all the foundations follow the same maturity level categorization. So, the Foundation Overview page may look different for your foundation.
You will see the total number of projects of the foundation as per their maturity level.
The chart enables visualization of growth and acceptance patterns for new projects.
Hovering over the chart reveals the count of projects accepted during specific time frames.
It presents a historical trend of project acceptances into your foundation over time.
Provides analysis of acceptance rates to identify periods of high or low project acceptance.
The subsequent chart illustrates the trend of projects approved by your foundation.
The Foundation Overview page in Insights V3 provides a comprehensive snapshot of your open source foundation, enabling you to gain valuable insights into your projects' performance and growth.
Disclaimer: It is not necessary that all the foundations follow the same maturity level categorization. So, the Foundation Overview page may look different for your foundation.
At the top of the page, you will find the header section, which includes the following elements:
The name of your foundation is displayed prominently at the top of the page, providing clear identification.
This feature allows you to search for specific projects within your foundation, making it easy to find and access project information quickly. Select a project to go to the project overview page.
At the top, you will see the following four high-level metrics:
Projects: The metric shows the total projects within the foundation.
Contributors: It shows the total number of contributors among all the projects within the foundation.
Lines of Code: Displays the total lines of code written for all the projects within the foundation.
Organizations: The metric shows the total number of organizations that have contributed to the projects within the foundation.
Using this search box, you can select another foundation or a project.
From the left navigation pane, click the icon to return to the Landing Page.
Distribution of project based on maturity level and rating
The metric categorizes your projects based on their maturity level and rating.
This helps you see how projects are distributed across different maturity levels and ratings, allowing you to make informed decisions about resource allocation and project management.
At each maturity level, projects are further segregated as per rating.
For example: Click on the pie chart under the Incubating Projects card to see the projects' categorization as per the ratings.
Project velocity in open source projects refers to the rate at which development tasks are completed and features are delivered. It measures the amount of work completed in a specific amount of time.
A higher velocity suggests increased efficiency and progress, while a lower velocity may indicate challenges or bottlenecks.
Monitoring project velocity helps teams assess their performance and plan future tasks accordingly, ensuring steady project advancement.
The Project Velocity chart displays data from the last calendar year.
On the Y-axis, there's a logarithmic scale representing PRs and Issues.
On the X-axis, there's a logarithmic scale representing commits.
The chart visualizes the correlation between code changes and collaboration.
To further understand the project's velocity, create a leaderboard. This ranks projects based on their commit numbers and provides a comparative view of their commits, PRs, and issues. This leaderboard can help in identifying the most active projects at a glance.
Review the top projects based on their commit numbers.
Compare their commit count, PRs, and issues in a single view.
On the landing page, the project cards are designed to show you real-time data and key metrics related to each project.
A project card displays the following key metrics:
Key metrics on a project card may vary as per the data sources. Projects with Git data sources will have fewer metrics.
When you click on a project card, it opens up an overview page dedicated to that specific project. This overview page provides more detailed information about the project, such as in-depth analytics, charts, and other relevant data.
The Project Card has the following details:
GitHub Icon: Click the (1) GitHub icon to go to the GitHub repositories of the project.
Aggregated data: it shows the real-time data of contributions, commits, PRs, issues, stars, and forks for the project.
Info Icon: shows the date and the time when the Best Practice Score was last updated.
Software Value: Constructive Cost Modal (COCOMO) is a procedural cost estimate model for software projects.
Download Icon: click the icon (2) to download the project card.
Within Insights V3, the "Filter the Date" feature allows you to customize your analytics view based on specific date ranges. This feature provides flexibility and control over the time period for which data is displayed.
Follow these steps to utilize the date-filtering feature:
On the right side of the analytics dashboard, locate the "Date Filter" section.
Click on the "Date Filter" section to expand the options.
Choose from the predefined date range options: Today, Last Week, Last 30 days, Last Quarter, Last Year, Last Two Years, or All Time.
Select the desired option by clicking on it.
Click the Bots checkbox if you want to hide the bots' data from the analytics.
The filter has This Year as a default time period.
To specify a custom date range, click on the Custom option within the date range selection menu.
On the calendar widget, select the start and end dates for your custom range.
The analytics dashboard will automatically update to display data within the selected custom date range.
After selecting a predefined date range or setting a custom date range, click the Apply button to apply the date filter.
The analytics dashboard will refresh to reflect the chosen date range, displaying data only for the selected period.
To display data for the entire available range and remove the date filter, click on the Clear Dates button.
Constructive Cost Model
The COCOMO (Constructive Cost Model) is a widely used model that estimates the effort, time, and cost associated with software development projects.
The model takes into account factors such as project size, complexity, team experience, and development environment.
The COCOMO model consists of three different levels or modes:
Basic COCOMO: This mode is used for early-stage project estimates and focuses on estimating effort based on lines of code (LOC). It uses a simple formula to calculate the effort required for a project, taking into account the project size in KLOC (thousands of lines of code).
Insights V3 uses the basic model to calculate the software estimates for the selected open source projects.
Constants based on Software Project Types (stored in the DB):
For more information, see:
The overview page should provide a high-level summary of the project's activity, contributors, and performance metrics, including:
The number of contributors and their distribution by location or organization.
The total number of commits, pull requests, and issues.
The average time to resolve issues and merge pull requests.
The overall health of the codebase, including code quality and security vulnerabilities.
The level of community engagement, such as the number of comments on pull requests.
The analytics tools on the overview page provide a range of features and visualizations that can help you gain insights into the project's performance, identify areas for improvement, and make informed decisions about development and collaboration.
The primary data sources for Insights V3 are the code repositories and the publicly available GitHub and Git databases. Refer to to learn more about data connectors.
The Overview page's Key Metrics and Detailed Analysis section includes six cumulative charts highlighting significant trends and patterns within your analytics data.
The cumulative charts help you compare different metrics on single charts. This comparative analysis helps identify relationships and draw meaningful conclusions.
The six cumulative charts show quick snapshots of the analytical data and the detailed analysis chart that helps you with the more profound analysis.
The data visualization on the overview page shows real-time data on the total number of contributors and the total number of active contributors across all monitored repositories during the selected time period.
On the Overview page, select the project and repositories (1) for which you want to see the data.
Select the specific time period using the filter option (2).
The high-level tile (3) shows you the total unique contributors (calculated based on their member ID) for the selected time range.
The detailed analysis chart shows you the active contributors and the cumulative count of total contributors for the selected period. On the left side, the chart shows the chart trend summary (4).
Hover over the chart (5) to see the number of active contributors and the total contributors for the selected month.
This interactive download feature (6) enables you to download the chart in CSV and PNG file formats.
When you want to see the health of your open source project, the Contributor Chart is a crucial project performance indicator.
Visualizing the number of contributors over time makes it easier to identify trends, patterns, and overall community interest. The trend helps project maintainers and other stakeholders act based on the charts.
Tracking the number of contributors can provide insights into the health and vitality of your project.
By analyzing changes in the contributor count, project managers can gain insights into the effectiveness of their community outreach and development strategies.
The Commits metric refers to the analysis of contributor's code commits within a specified timeframe. A code commit represents a unit of change to the software's source code repository.
Each commit includes the following:
committed-commit
("Default Branch" only)
In this chart, only commits are counted, not the Roles. Each commit with a unique Commit SHA is counted as one Commit. The roles do not matter here.
The dashboard shows the commits snapshot and a detailed chart. The detailed chart is a combined chart (line chart and bar chart) that shows new commits vs. total commits.
On the Overview page, select the project and repositories (1) for which you want to see the data.
Select the specific period using the filter option (2).
The high-level tile (3) shows you the total commits for the selected time range.
The detailed analysis chart shows you the New commits and the cumulative count of total commits for the selected period. On the left side, the chart shows the chart trend summary (4).
Hover over the chart (5) to see the new commits and the total commits for the selected month.
This interactive download feature (6) enables you to download the chart in CSV and PNG file formats.
The metric enables project maintainers and stakeholders to gain valuable insights into code changes and progress within a specified period.
It provides insights into the volume and frequency of code changes made by contributors. By visualizing commit data in a bar chart, you can track the progress of development efforts over time.
Changes in commit counts provide periods of intense development, periods of slower activity, or the impact of specific events or milestones on the project.
The Issue Metric measures the number of issues reported and tracked within a specified period. It compares the number of issues opened, the number of issues closed, and the total commits for the selected time period.
The metric is based on the following activity types:
issues-closed
issues-opened
The analytics tool employs a combined chart (a line chart and bar charts) on its dashboard to analyze the Issue Metric. The line on the chart connects the data points, allowing you to observe trends and patterns over time.
The dashboard shows the issues (opened +
closed issues) in a snapshot and a detailed chart (open, closed, and the total issues).
On the Overview page, select the project and repositories (1) for which you want to see the data.
Select the specific time period using the filter option (2).
The high-level tile (3) shows you the total issues (open + closed) for the selected time range.
Hover over chart (5) to see the open issues, closed issues, and total issues for the selected month.
This interactive download feature (6) enables you to download the chart in CSV and PNG file formats.
Issues Tracking and Management: By visualizing the data on a line chart, it becomes easier to identify the increase or decrease in issue activity, allowing for effective resource allocation and prioritization.
Performance Evaluation: The Issue Metric helps in evaluating the performance of the development team and the project as a whole. Changes in issue count over time indicate improvements in software quality, bug-fixing efficiency, or the impact of development efforts.
Community Engagement: A higher number of reported issues indicates the active participation and involvement of the community in the open source project.
The detailed analysis chart shows you the open issues, closed issues, and the count of total issues for the selected period. On the left side, the chart shows the chart trend summary (4).
The Fork Metric measures and analyzes the number of times a project has been forked by other developers.
Forking is the process of creating a copy of a project's source code repository to either modify and enhance the project or use it as a starting point for a new project.
The bar chart on the dashboard represents the analysis, displaying the number of forks over time. Hover over a specific bar to access the detailed fork information for that particular month within the selected period.
The interactive download feature (Icon) enables you to download the chart in CSV and PNG file formats.
How popular is the project? The Fork Metric provides insights into the popularity of your project. A higher number of forks generally indicates that the developers find your project useful and valuable enough to build it or adapt it to their specific needs.
Code Reuse: By analyzing the Fork Metric, you can get data on code reuse and identify potential opportunities for improvement.
Community Engagement: A growing number of forks indicates an active and involved community, contributing to the project's growth.
Project Evolution: By monitoring forks over time, you can identify significant milestones.
The Star Metric measures and analyzes the number of stars a project receives on a code hosting platform like GitHub.
The metric gives you a real-time data analysis of projects' popularity, community engagement, and overall project visibility.
Stars represent a way for you to bookmark or indicate your interest in and appreciation for a particular project. Each star serves as a measure of the project's popularity.
To analyze the Star Metric, the analytics tool employs a line chart on its dashboard. The line connecting the data points on the chart showcases the trend and changes in the number of stars over time.
When you hover over a specific point on the line chart, detailed information about the number of stars for that particular month within the selected period is displayed.
The metric helps you analyze your project's popularity. A higher number of stars generally suggests a widely recognized and appreciated project, potentially attracting more contributors.
This check determines whether the project has generated executable (binary) artifacts in the source repository. For more details, see the check documentation.
ID: code_review
This check determines whether the project requires code review before pull requests (merge requests) are merged. For more details, see the check documentation.
ID: dangerous_workflow
This check determines whether the project’s GitHub Action workflows has dangerous code patterns. For more details, see the check documentation.
ID: dependency_update_tool
This check tries to determine if the project uses a dependency update tool, specifically dependabot or renovatebot. For more details, see the check documentation.
ID: maintained
This check determines whether the project is actively maintained. For more details, see the check documentation.
ID: sbom
List of components in a piece of software, including licenses, versions, etc.
This check passes if:
The latest release on Github includes an asset which name contains sbom. Regexps used:
The repository’s README
file contains a SBOM section that explains where they are published to, format used, etc. Regexps used to locate the title header:
ID: security_policy
Clearly documented security processes explaining how to report security issues to the project.
This check passes if:
A security policy file is found in the repository. Globs used:
A security policy reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A security policy file is found in the default community health files repository.
ID: signed_releases
This check tries to determine if the project cryptographically signs release artifacts. For more details, see the check documentation.
ID: token_permissions
This check determines whether the project’s automated workflows tokens are set to read-only by default. For more details, see the check documentation.
ID: adopters
List of organizations using this project in production or at stages of testing.
This check passes if:
An adopters file is found in the repository. Globs used:
An adopters reference is found in the repository’s README
file. This is in the form of a title header or a link. Regexps used:
ID: changelog
A curated, chronologically ordered list of notable changes for each version.
This check passes if:
A changelog file is found in the repository. Globs used:
A changelog reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A changelog reference is found in the last GitHub release content body. Regexps used:
ID: code_of_conduct
Adopt a code of conduct to establish community standards, promote an inclusive and welcoming initiative, and outline procedures for handling abuse.
This check passes if:
A code of conduct file is found in the repository. Globs used:
A code of conduct reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A code of conduct file is found in the default community health files repository, for example.
ID: contributing
A contributing file in your repository provides potential project contributors with a short guide to how they can help with your project.
This check passes if:
A contributing file is found in the repository. Globs used:
A contributing reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A contributing file is found in the default community health files repository.
ID: governance
Document that explains how the governance and committer process works in the repository.
This check passes if:
A governance file is found in the repository. Globs used:
A governance reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
The maintainers file contains a list of the current maintainers of the repository.
This check passes if:
A maintainers file is found in the repository. Globs used:
A maintainers reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
ID: readme
The readme file introduces and explains a project. It contains information that is commonly required to understand what the project is about.
This check passes if:
A readme file is found in the repository. Globs used:
ID: roadmap
Defines a high-level overview of the project’s goals and deliverables ideally presented on a timeline.
This check passes if:
A roadmap file is found in the repository. Globs used:
A roadmap reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
ID: summary_table
The Projects Summary Table is a CNCF Business Value Subcommittee initiative to supplement the CNCF Landscape and include further information about CNCF projects for the wider Cloud Native community.
This check passes if:
At least one of the summary_* fields has been set in the project's extra section in the Landscape YAML file.
ID: website
A url
that users can visit to learn more about your project.
This check passes if:
A website url
is configured in the GitHub repository.
On a regular basis, a number of checks are performed on each repository listed in the database.
Checks are grouped into check sets.
One or more check sets
are applied to a single repository, and each check set specifies the number of checks that will be performed on the repository.
The check’s file must declare the following information:
ID
: check identifier.
WEIGHT
: weight of this check, used to calculate scores.
CHECK_SETS
: check sets this new check belongs to.
A Contribution Leadership board visualization displays the contributions made by individual contributors to an open source project. It ranks contributors based on the number of code commits, pull requests, issues closed, or other metrics and visually represents their relative activity levels and impact on the project.
Merging contributors refers to combining the contributions of a single individual who may have been working under different user accounts.
This can happen when a contributor has multiple git configurations or submits pull requests from different email addresses.
Merging these accounts into a single identity ensures the accuracy of the leaderboard and gives a true representation of an individual’s contributions.
Recognition and Motivation: The Contributor Leaderboard recognizes and acknowledges the efforts of individual contributors. It highlights their contributions, encourages ongoing engagement, and motivates contributors to continue their valuable work.
Community Engagement: It creates a sense of community and healthy competition, encouraging collaboration and inspiring others to contribute and improve their ranking on the leaderboard.
Collaboration Opportunities: The leaderboard helps project maintainers and community members identify potential collaborators or subject-matter experts within the project. It will be easier to identify the most active contributors and connect with them.
A best practice score visualization is a tool that helps project leads and managers assess the overall health and quality of an open source software project.
It typically evaluates the project against a set of best practices or standards for software development, such as the categories Documentation
,
Standards
,
Security
``
Legal` and `Reliance`
.
It generates a score or rating based on how well the project meets these criteria.
On the Overview page, select the project and repositories for which you want to see the best practice score.
Select the specific time period using the filter option.
Scroll down to find the best practice score dashboard.
You can see the aggregated score (3) and each category's score on the dashboard.
Click on any category to see the expanded page where you can see the detailed analysis for each repository.
Click the Create Issue button to create an issue for each repository.
ID: analytics
Project websites provide some web analytics.
This check passes if:
A Google Analytics 3 (Universal Analytics) Tracking ID is found in the source of the website configured in GitHub. Regexps used:
A Google Analytics 4 Measurement ID is found in the source of the website configured in Github. Regexps used:
The HubSpot tracking code is found in the source of the website configured in Github. Regexps used:
ID: artifacthub_badge
Projects can list their content on Artifact Hub to improve their discoverability.
This check passes if:
An Artifact Hub
badge is found in the repository’s README
file. Regexps used:
ID: cla
The CLA defines the conditions under which intellectual property is contributed to a business or project.
This check passes if:
A CLA check is found in the latest merged PR on GitHub. Regexps used:
This check will be automatically marked as exempt if the DCO check passes but this one does not.
ID: community_meeting
Community meetings are often held to engage community members, hear more voices, and get more viewpoints.
This check passes if:
A reference to the community meeting is found in the repository’s README
file. Regexps used:
ID: dco
Mechanism for contributors to certify that they wrote or have the right to submit the code they are contributing.
This check passes if:
The last commits in the repository have the DCO signature (Signed-off-by). Merge pull request and merge branch commits are ignored for this check.
A DCO check is found in the latest merged PR on GitHub. Regexps used:
This check will be automatically marked as exempt if the CLA check passes, but this one does not.
ID: github_discussions
Projects should enable GitHub discussions in their repositories.
This check passes if:
A discussion that is less than one year old is found on GitHub.
ID: openssf_badge
The Open Source Security Foundation (OpenSSF) Best Practices badge is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices.
This check passes if:
An OpenSSF
(CII) badge is found in the repository’s README
file. Regexps used:
ID: openssf_scorecard_badge
This check passes if:
An OpenSSF
Scorecard badge is found in the repository’s README
file. Regexps used:
ID: recent_release
The project should have released at least one version in the last year.
This check passes if:
A release that is less than one year old is found on GitHub.
ID: slack_presence
Projects should have presence in the CNCF Slack or Kubernetes Slack.
This check passes if:
A reference to the CNCF Slack or Kubernetes Slack is found in the repository’s README
file. Regexps used:
This chart displays individual identities, not merge contributors, as in tool. Even if we combine some identities in CM, they will still show up as different ones in the Insights V3 leaderboard.
Click the Download icon to download the dashboard.
For more information, see .
Scorecard assesses open source projects for security risks through a series of automated checks. For more information about the Scorecard badge please see .
ID: license_approved
Whether the repository uses an approved license or not.
This check passes if:
The license identified matches any of the following:
ID: license_scanning
License scanning software scans and automatically identifies, manages, and addresses open source licensing issues.
This check passes if:
A FOSSA
or Snyk
link is found in the repository’s README
file. Regexps used:
A link pointing to the license scanning results is provided in the .clomonitor.yml metadata file.
ID: Apache_2.0
A permissive license whose main conditions require preserving copyright and license notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
ID: trademark_disclaimer
Project sites should have the Linux Foundation trademark disclaimer.
This check passes if:
The Linux Foundation trademark disclaimer is found in the content of the website configured in Github. Regexps used:
Calculating a global score for a best practice score in an open-source project involves evaluating various aspects of the project against predefined best practices and assigning weights to those aspects based on their importance. Let's understand this with the sample example.
Define the following set of best practices that are important for the success and quality of the open-source project. Each category should have a set of criteria that can be evaluated.
Assign weights to each category based on their relative importance. These weights should add up to 100%. The weights reflect how much each category contributes to the overall quality of the project.
Evaluate Each Criterion
For each criterion within a category, evaluate the project and assign a score.
Use a numerical scale (0–10) or any other suitable scale.
Code of conduct: 8
Governance: 9
Maintainer: 8
Website: 7
Analytics: 9
GitHub Discussion: 10
Community meetings: 8
Binary Artifacts: 8
Dangerous Workflow: 9
Approved Licenses: 9
It is calculated by the average score* weights
Documentation : ((8+9+8+7)/4)*.4= 3.2
Standards: ((9+10+8)/3)*.30= 2.7
Security: ((8+9)/2)*.20= 1.7
Legal: 9*.10= .9
Calculate Global Score
Sum up the category scores to obtain the global score for the best practice score of the open-source project.
Documentation+ Standards+Security+Legal= 3.2+2.7+1.7+.9 = 15.58
Insights V3 often incorporates a Geographical Distribution metric to provide insights into the locations from which contributions originate.
Geographical Distribution analyzes and visualizes the contributions made by contributors across different regions around the world. It provides a breakdown of the top regions based on the total number of contributors, providing a clear understanding of the project's global engagement and scope.
Hover over the chart to view the number of contributors for each region during the selected period. This information provides a more granular view of contributor activity within specific regions.
Global Impact: Geographical Distribution allows you to assess the global impact of the open source project by providing insights into the regions where contributions are coming from.
Regional Comparison: Compare the contribution numbers across different regions to identify any notable variations. Assess whether certain regions show consistent contribution levels or if there are fluctuations that require further investigation.
Top Contributing Regions: It helps to identify the top five regions based on the total number of contributions. These regions represent areas where the project has significant engagement and impact.
The Active Days metric measures the number of days a contributor has made at least one contribution to a project. It counts the number of days on which a contributor has been actively engaged in the project's development.
The Active Day chart also displays two bars for the current data and the previous data, allowing you to compare them.
The Active Days dashboard provides you with the following insights:
You can monitor progress and identify trends. This information can be used to set goals and benchmarks for the project and measure success.
The active days metric provides a quick snapshot of the project's activity level. It helps determine whether the project is actively maintained or not.
The visualization can be used to quickly assess the activity level of a repository. A repository with a high number of active days is likely to be more active and healthy than one with a low number of active days.
By highlighting the importance of active days, project managers can encourage new contributors to become more involved in the project.
The Organization Leaderboard ranks organizations based on their contributions to the project. The leaderboard provides insights into the collective efforts of organizations to drive the success and growth of your projects.
It helps you determine if your project has a healthy contribution from multiple organizations and if new organizations are coming to contribute to the project.
Recognition: The Organization Leaderboard recognizes and showcases the contributions made by various organizations.
Project Sustainability: The Organization Leaderboard evaluates the involvement of organizations and assesses the project's long-term sustainability and growth potential.
Trust and Credibility: When organizations are actively engaged in your projects and their contributions are recognized through the leaderboard, it enhances the overall trust and credibility of the project.
Gerrit data connector is a tool that allows you to connect Gerrit, a web-based code review system for Git repositories, with other data sources or systems. This connector enables you to extract, transform, and load data between Gerrit and Insights.
Following are the different Gerrit activity types:
Contributor Dependency measures and analyzes the dependencies or relationships between different contributors within a project. It explores how contributors rely on each other, collaborates, and interact in terms of code contributions, reviews, and other collaborative activities.
Contributor dependency shows the relationship between contributors or entities within a project, where the actions or outputs of one contributor depend on the inputs or outputs of another.
Collaboration: It identifies which contributors frequently interact, exchange ideas, review each other's work, and collaborate on code changes.
Knowledge Sharing and Expertise: Understanding these dependencies can help project maintainers identify subject matter experts, encourage knowledge sharing, and allocate resources effectively.
Project Health and Sustainability: By analyzing Contributor Dependency, project maintainers can evaluate the health and sustainability of the project. Dependencies that are concentrated around a few contributors may pose risks if those contributors become less active or leave the project.
The metric provides insights into the technical contribution breakdown across weekdays and weekends. It shows the time of day when most of the contributions happen so that you have maximum participation in the project. Each day is categorized by its level of activity, indicating low to high contribution levels.
Commits are recorded in the individual contributors' local time zone.
Only commit data is used for this dashboard.
Commits
committed-commit
co-authored-commit
authored commit
Activity Level Assessment: Work Time Distribution allows you to assess the technical activities across different days of the week. By analyzing the chart, project managers can identify contribution patterns and trends, such as peak activity days or days with lower participation.
Productivity Monitoring: Work Time Distribution helps you to monitor contributors' productivity and engagement. By analyzing the breakdown of contributions, you can identify periods of high productivity and low engagement.
Work Optimization: By understanding the distribution of contributions across weekdays and weekends, project managers can identify potential collaboration challenges due to varying availability.
Weekday vs. Weekend Contributions: Compare the contribution levels between weekdays and weekends. Assess significant activities differences, and identify any patterns or preferences in contributor engagement during these periods.
Maximum Participation: As an Executive Director or Maintainer, when you want to set up a community call for your project, you view the time when most of the contributions happen so that you can have maximum participation.
The Contributor Leaderboard on the Confluence Dashboard displays a ranking of users based on their contributions to Confluence activities within a specified date range.
Contributors are ranked based on metrics including new pages, comments, attachments uploaded, and blog posts on the platform.
The leaderboard provides valuable insights into user engagement and productivity within the Confluence environment.
To access the Contributor Leaderboard in Confluence, follow these steps:
On the Overview page, select the project and repositories (1) for which you want to see the data.
On the left navigation pane, click Data Integrations> Confluence.
Select the specific date range using the filter option (2).
Scroll down and you will see the Contributors Leaderboard widget.
Use the drop-down menu to filter the leaderboard based on specific confluence activities such as page edits, comments, attachments, and blog posts.
The leaderboard will dynamically update to display rankings based on the selected date range and activity filter.
The leaderboard serves several purposes:
Enhancing Engagement: Motivates users to participate more actively.
Tracking Productivity: Offers insights into who is the most active contributor.
Identifying Knowledge Leaders: Helps in recognizing contributors who are pivotal in spreading knowledge and expertise across the organization.
By effectively utilizing the Confluence Contributor Leaderboard, organizations can foster a more engaged and productive community, driving the collective success of their projects.
Organization Dependency Metric shows the analysis of how much a project's contributions depend on or are associated with different organizations.
With Organization Dependency Metrics, you can assess which organizations are significantly contributing to your project.
Engagement Assessment: For organizations involved in the project, this metric helps assess their level of engagement and impact. It can encourage healthy competition among contributors, resulting in greater involvement.
Risk Management: Dependency on a single organization for contributions can be risky. If that organization reduces its involvement, the project might face challenges.
A mailing list is a communication platform where you can sign up to communicate messages via email. It acts as a centralized hub for discussions, announcements, and collaborations among a specific group sharing common interests or working towards a common project.
Groups.io is an online platform that offers mailing list management and hosting facilities. It offers features for creating, managing, archiving mailing lists, and facilitating email communication. To learn more, see https://groups.io/.
The Mailing Lists Dashboard within Insights V3, integrated with Groups.io, provides data insights into project communications. Its primary objectives and goals include:
Objective: Centralizing and analyzing communication data from Groups.io mailing lists.
Goals:
Communication Analysis: Understand the frequency, nature, and trends of interactions within mailing lists.
Engagement Measurement: Measure user engagement levels, message frequency, and active contributors.
Community Insights: Identify contributors and organizations involved, fostering collaboration and understanding community dynamics.
The Organization Leaderboard ranks organizations based on their activity types on Confluence pages for the selected date range. These activity types include new pages, blog posts, attachments, total pages, and page comments.
The leaderboard ranks organizations on the Confluence platform according to the following criteria:
New Pages: The number of new pages created by the organization.
Blog Posts: The frequency and quality of blog posts published.
Attachments: The number of files and documents attached to pages and posts.
Page Comments: The level of engagement is demonstrated by comments on pages.
The Activities Breakdown chart provides a detailed breakdown of various activities on your Confluence pages, including new pages, blog posts, attachments, total pages, and page comments.
To access the Activities Breakdown, follow these steps:
On the Overview page, select the project and repositories (1) for which you want to see the data.
On the left navigation pane, click Data Integrations> Confluence.
Select the specific date range using the filter option (2).
Scroll down and you will see the Activities Breakdown widget.
Analyze the distribution of activities to understand user engagement patterns and trends over time.
Click icon to download the chart in PNG or CSV format.
The ranking is based on the number of messages or contributions from newly onboarded contributors to the mailing lists during a specific period.
This dashboard provides insights into the new contributor's activity for the selected projects. It integrates data from Groups.io to help you understand how new contributors are engaging with your project's mailing lists.
On the Overview page, select the project and repositories for which you want to see the new contributor leaderboard.
From the left navigation, click Mailing Lists.
Look for the date filter in the top-right corner of the dashboard.
Click on the calendar icon and select the timeframe you want to analyze. You can choose predefined options like "Last year," or "this year," or set a custom date range.
Scroll down the Mailing Lists dashboard to see the leaderboard.
The leaderboard displays the top contributors based on their message count during the chosen period.
Each entry shows:
Rank: Position on the leaderboard based on message count.
Contributor Name: Username of the contributor.
Messages: Total number of messages posted.
Last Message Date: Date of the most recent message posted.
Click Show More to expand the list.
Identify Potential Contributors: Discover individuals who are actively engaging and might be interested in contributing to other project areas.
Measure Community Growth: Track the rate at which new people are joining the mailing list, which can indicate overall community health.
Regularly review the leaderboard to identify any trends or patterns in new contributor activity.
Click the Download icon to download the leaderboard.
This leaderboard ranks contributors by their engagement level across all mailing lists within the specific timeframe, showcasing the most engaged and active contributors.
The leaderboard integrates data from Groups.io to help you understand how new contributors are engaging with your project's mailing lists.
On the Overview page, select the project and repositories for which you want to see the new contributor leaderboard.
From the left navigation, click Mailing Lists.
Look for the date filter in the top-right corner of the dashboard.
Click on the calendar icon and select the timeframe you want to analyze. You can choose predefined options like "Last year," or "this year," or set a custom date range.
Scroll down the Mailing Lists dashboard to see the most active contributors leaderboard.
The leaderboard displays the most active contributors based on their message count during the chosen period.
Each entry shows:
Rank: Position on the leaderboard based on message count.
Contributor Name: Username of the contributor.
Messages: Total number of messages posted.
Last Message Date: Date of the most recent message posted.
Click Show More to expand the list.
The Key Metrics and Detailed Analysis section includes four high-level tiles with charts highlighting significant trends and patterns within your analytics data.
The cumulative charts help you compare different metrics on single charts. This comparative analysis helps identify relationships and draw meaningful conclusions.
Mailing Lists: Indicates the total number of mailing lists associated with the project for the selected period.
Messages: Displays the total count of messages exchanged within the selected mailing list(s) for the selected period.
Contributors: shows the total number of contributors actively participating in discussions.
Organizations: highlights the involved organizations or entities contributing to the discussions within the mailing lists.
On the Overview page, select the project and repositories (1) for which you want to see the data.
From the left navigation, click Mailing List.
Select the specific period using the filter option (2).
Click the high-level tile (3), which shows the total number of themailing lists/ messages/ contributors/ organizations
for the selected time range.
The detailed analysis charts show the following details:
Mailing Lists: shows Active mailing lists vs. total mailing lists.
Messages: shows new messages vs. the total messages for the selected period.
Contributors: shows new contributors vs. the total contributors for the selected period.
Organizations: shows new organizations vs. total organizations for the selected period.
Click the Download icon to download the leaderboard.
The Confluence Data Analytics Dashboard available in the open-source analytics application, Insights V3, provides a comprehensive suite of tools designed for deep analysis of user interactions, collaboration patterns, and content efficiency within the Confluence platform. Here is an overview of its features:
Track peak times for user engagement and contributions.
User Interaction Graphs: Visualize the network of collaborations among users.
Page Views and Edits Tracking: Monitor the popularity and evolution of content over time.
Most Engaged Content: Identify the content that receives the most views, comments, and shares.
Team Performance Metrics: Evaluate the productivity and collaboration levels of different teams.
Individual Contribution Insights: Assess the input of individual team members in the collaborative process.
Flexible Filtering: Create custom reports by applying filters based on users, time frames, and content types.
Export Features: Export reports in various formats for sharing or further analysis.
The dashboard integrates seamlessly with Confluence, leveraging its API to pull real-time data. This enables teams to make data-driven decisions, enhance collaboration, and improve content quality on the Confluence platform.
The Geographical Distribution chart is a feature in the Mailing Lists dashboard of the open-source analytics application, Insights V3. This interactive chart provides a visual representation of the geographical locations of contributors to your mailing lists.
It allows you to see where your contributors are located and the extent of their contributions during a selected period.
With this chart, you can:
View the distribution of contributors globally.
Understand the extent of contributions from different regions.
Filter data by a specified period to analyze trends.
To access this feature:
Navigate to the Insights V3 dashboard.
Click on the Mailing Lists section.
Locate and select the Geographical Distribution
chart.
This tool is invaluable for community managers looking to understand and grow their global contributor base.
This ranking displays the most recent discussions based on the timing of the last messages posted. It highlights the latest and most active discussions within the mailing lists for the selected period.
The table below provides a snapshot of the most active discussions within our mailing lists, ranked by the timing of the last message posted. This ensures you are always informed about the freshest and most relevant conversations.
Please ensure to join these discussions to share your insights and contribute to our community's knowledge.
Rank | Discussion Topic | Last Message Date |
---|---|---|
This chart ranks public mailing lists based on their overall activity, considering total messages, unique authors, and contributions from different organizations. It highlights the most active and engaged mailing lists within the project for the selected period.
The Leaderboard provides a snapshot of the most vibrant mailing lists within your project for a selected time period. Here's how to interpret the information:
Ranking: Indicates the position of each mailing list based on activity levels, with #1 being the most active.
Name: The name of the mailing list.
Threads: The count of discussion threads initiated in the mailing list.
Messages: Total number of messages posted in all threads.
Subscribers: The number of individuals subscribed to receive updates from the mailing list.
Contributors: Unique individuals who have posted at least one message to the mailing list.
Organization: The entities (like companies or institutions) that contributors are affiliated with.
Each category also displays a change (+/-) compared to the previous period, helping you see trends like growth or reduction in activity.
The ranking is based on the number of messages or contributions from newly onboarded organizations to the mailing lists during a selected period.
It highlights the engagement level of these organizations by showcasing their rankings derived from the quantity of messages contributed across the entire spectrum of mailing lists.
On the Overview page, select the project and repositories for which you want to see the new contributor leaderboard.
From the left navigation, click Mailing Lists.
Look for the date filter in the top-right corner of the dashboard.
Click on the calendar icon and select the timeframe you want to analyze. You can choose predefined options like "Last year," or "this year," or set a custom date range.
Scroll down the Mailing Lists dashboard to see the leaderboard.
The leaderboard displays the new organizations based on their message count during the chosen period.
Each entry shows:
Rank: Position on the leaderboard based on message count.
Name: Username of the contributor.
Messages: Total number of messages posted.
Last Message Date: Date of the most recent message posted.
Click the Download icon to download the leaderboard.
This ranking showcases the top messages based on the number of responses generated by these messages. It highlights the most engaging and widely discussed topics within the mailing lists for the selected period.
On the Overview page, select the project and repositories (1) for which you want to see the data.
From the left navigation, click Mailing List.
Select the specific period using the filter option (2).
Scroll down the main webpage where the leaderboard is hosted.
The leaderboard shows the rankings based on the number of messages. Look through the list to see which messages or topics are most engaging.
The leaderboard includes a feature to compare the increase or decrease of messages over a selected period.
Click Show More to expand the list.
If you want to download the list, click .
Insights V3 incorporates a Performance Metric to provide insights into key performance indicators such as time to merge pull requests, build frequency, and build failure rate.
The dashboard presents this information using a bar chart, allowing you to visualize and analyze these performance metrics over a selected time period.
The dashboard presents this information using a bar chart, allowing project managers to visualize and analyze these performance metrics over a selected time period.
Time to Merge Pull Requests: Evaluate the average time taken to merge pull requests. Identify any significant variations or trends in the time-to-merge, which can indicate potential inefficiencies in the code review and merge processes.
Build Frequency: Assess the frequency of software builds. A higher build frequency signifies more frequent integration of code changes and adherence to continuous integration practices. A consistent and regular build schedule ensures rapid feedback and promotes collaboration among contributors.
Build Failure Rate: Analyze the percentage of build failures. Higher build failure rates indicate issues in the build process, such as compilation errors, test failures, or compatibility issues. Identifying and addressing these failures promptly ensures a more stable and reliable software product.
A Velocity dashboard in Insights V3 is a visual representation that provides insights into the development team's velocity. Velocity refers to the rate at which the team completes work or delivers features over a specific period. This dashboard tracks and measures the team's productivity and progress.
It typically displays key metrics related to the team's velocity, such as Performance Metrics, Lead Time, Average Review Time, Average Wait Time for First Review, and Code Engagement.
A Velocity dashboard can help project managers and stakeholders understand the team's capacity and performance over time. The dashboard is useful to project managers, leads, development teams, and stakeholders in several ways:
The dashboard helps project managers estimate the team's capacity, progress, and performance over time. It provides insights into the team's historical productivity and better resource allocation.
The velocity dashboard allows development teams to assess their own performance and productivity. They can track their progress, identify patterns, and improve their estimation accuracy by comparing planned work with actual velocity.
The velocity dashboard provides stakeholders with visibility into the progress and productivity of the development team. It enables you to track the status of deliverables, understand the team's capacity, and make informed decisions based on real-time data.
Overall, a velocity dashboard is a useful tool for project management, performance evaluation, collaboration, and decision-making, benefiting all stakeholders involved in the open source software development process.
Lead time metric measures the average time between the time when a Pull Request is raised to the time it is merged.
It shows the entire lifecycle of a pull request, including the PR raised> Review started>PR accepted>PR merged.
The Lead Time metric can be effectively visualized using box plots. Box plots can provide a visual representation of the distribution of lead times.
Project Efficiency: you can analyze the complete PR review cycle Lead Time that provides efficiency in the software development process. By analyzing the time it takes for code changes to move through the development pipeline, project managers can identify delays or inefficiencies.
Quality Assurance: Lead time can provide insights into the quality assurance process. Longer lead times may indicate delays in testing or quality assurance activities, potentially leading to issues and bugs reaching production.
Insights V3 incorporates the Average Wait Time for First Review metrics to provide insights into the duration it takes for pull requests to receive their first review.
The Average Wait Time for First Review refers to the average time it takes for pull requests to receive their first review after being opened. It measures the time span between the creation of a pull request and when it receives its initial feedback or review.
In the vertical bar chart, each bar displays the Average Wait Time for 1st Review with x-Axis showing the date and the y-axis showing "Time in Hours".
The Average Wait Time for a selected time period can be computed by summing up the time it took for the first review for all PRs, divided by the number of pull requests and results displayed in minutes/hours/days.
Each data point on the chart represents the average wait time for the first review during that specific time period.
Code Quality and Bug Resolution: Longer wait times may delay the identification and resolution of code issues or bugs, potentially affecting the overall quality of the software.
Faster Development Cycle: Reducing the wait time for the first review contributes to a faster development cycle. This allows projects to deliver new features, bug fixes, or improvements in a timely manner, increasing the project's overall efficiency.
Collaboration and Iteration: The Average Wait Time for First Review metric directly impacts collaboration and iteration among contributors. Timely feedback on pull requests allows contributors to address issues or make improvements promptly.
A Productivity page provides consolidated insights to enhance efficiency and measure productivity in software development.
It offers visual representations of data, such as commits per active day, New contributors, Drifting away contributors, Engagement gap, Work time distribution impact, and Effort by pull request size, allowing contributors and project managers to monitor progress, identify bottlenecks, and optimize workflows.
By providing real-time information and actionable analytics, the productivity dashboard empowers open source projects to make data-driven decisions, improve collaboration, and deliver high-quality software more effectively.
In Insights V3, the Code Review Engagement metric assesses the level of involvement and participation in code review activities.
Following are the various factors that are considered in the Pull Request review process:
Number of Pull Request Participants
Pull Requests reviewed
Review comments for Pull Request
Code reviews
Process Improvement: Tracking the Code Review Engagement metric over time allows you to assess the effectiveness of code review processes and identify areas for improvement. Continuous improvement of the code review process leads to higher-quality code and improved productivity.
Quality Assurance: Code review plays a vital role in ensuring code quality and identifying potential issues or bugs. By tracking this metric, managers can identify areas where additional attention or improvement may be needed to maintain high code quality standards.
The Work Time Distribution Impact Dashboard analyzes how contributors allocate their work time and the impact of different activities on project progress.
The chart shows the trends of commits and finds patterns if long hours, non-business hours, or weekends have contributed to burnout. Burnout can be thought of as a lower number of commits over a long period, before which there was heightened activity (commits).
The purpose of the chart is to find out if there is a risk of burnout among contributors due to long hours.
Workload Distribution: Monitoring the Work Time Distribution Impact helps identify potential workload imbalances among contributors. If one or a few contributors are consistently spending a disproportionate amount of time on specific activities, it can lead to burnout or reduced productivity.
Performance Evaluation: The Work Time Distribution Impact metric can contribute to performance evaluation and feedback processes. By analyzing how contributors allocate their work time, project managers can identify patterns of efficiency or areas that require improvement.
The Commits per Active Day Dashboard provides insights into code commit frequency on active development days. It measures the average number of code commits contributors make on active development days.
Early Issue Detection: A higher number of commits per active day increases the likelihood of early issue detection. Regular code commits provide more opportunities for contributors to identify potential issues or bugs during the development process.
Code Quality and Stability: A consistent number of commits indicates ongoing code enhancements and maintenance, leading to improved code quality over time.
Productivity Assessment: A higher number of commits per active day suggests that contributors are actively working on code changes, implementing new features, fixing bugs, and making improvements.
The Effort By Pull Request Batch Size metric analyzes the relationship between the size of pull requests (measured by lines of code changed) and the time contributors spend reviewing and merging them.
Here are ways you can interact with the chart to gain deeper insights:
Filter by Date Range: This allows users to analyze the metrics across different periods to observe how the trends have evolved.
Compare Trends: The chart compares previous periods, enabling you to spot differences or improvements.
The metric shows the distribution of pull requests across different size categories, from "Very Small" to "Gigantic."
This information can help identify potential bottlenecks or areas where the team may need additional support or process improvements.
The metric tracks the average time required for reviewing and merging pull requests in each size category.
Longer review and merge times for larger pull requests may indicate a need for better code organization, more thorough review processes, or additional resources.
The metric includes information on the number of participants and comments associated with each pull request size category.
Higher numbers of participants and comments for larger pull requests suggest increased collaboration and coordination efforts, which can be both positive (better code quality) and negative (potential delays or inefficiencies).
Development Cycle Time: The Effort By Pull Request Batch Size metric provides insights into the overall development cycle time. By analyzing the relationship between batch size and effort, you can identify trends that affect the time taken to review and merge pull requests.
Review Efficiency: The Effort By Pull Request Batch Size metric helps project managers evaluate the efficiency of the pull request review process. By analyzing the effort required for different batch sizes, You can identify patterns and trends that impact the speed and quality of reviews.
Q: What does the Effort By Pull Request Batch Size metric measure? A: It measures the relationship between the size of pull requests, in terms of lines of code changed, and the amount of time contributors spend reviewing and merging them.
Q: Why is it important to analyze the Effort By Pull Request Batch Size metric? A: Understanding this metric helps optimize the review process by identifying the most efficient batch sizes for pull requests, thus reducing review time and improving workflow efficiency.
Q: How can I interact with the chart to get more insights? A: You can filter the analysis by date range to observe trends over time and compare these trends with previous periods to identify improvements or regressions in efficiency.
Q: Can analyzing this metric reveal trends over specific periods? A: Yes, by filtering the data by specific date ranges, it's possible to observe how the trends in pull request batch sizes and review times have evolved, helping teams adapt their strategies accordingly.
The Reports Dashboard gives you a comprehensive view of the project's performance through four primary metrics. The dashboard utilizes intuitive data visualizations such as charts, graphs, and tables. These visual representations make it easier to interpret complex data and identify patterns.
The Reports Dashboard enables you to generate comprehensive reports based on the selected metrics and filters. These reports can be exported in various formats, such as PDF or CSV, making sharing the insights with team members or external stakeholders convenient.
At the core of the Reports Dashboard are the following four major metrics:
The Engagement Gap metric measures the difference between expected and actual levels of contributor engagement. The dashboard shows the ratio of the difference between the contributor who comments the most over PRs vs. the contributor who comments the least.
Performance Assessment: The Engagement Gap metric enables you to assess the project's overall engagement level by comparing it to the expected or desired level. It provides a quantitative measure of how actively contributors are participating and helps identify any gaps between the expected and actual engagement levels.
Community Health: The Engagement Gap metric provides valuable insights into the health and dynamics of the project community. Large engagement gaps may indicate potential challenges, such as communication issues, a lack of mentorship, or unclear contribution guidelines.
How to Improve Engagement Gap?
Set Clear Expectations: Clearly define the expected engagement levels for each project to provide a benchmark for comparison.
Encourage Collaboration: Foster a culture of collaboration within your team by encouraging open communication and sharing of ideas.
Provide Feedback: Regularly review the Engagement Gap metrics with your team and provide feedback on areas that need improvement.
Recognize Achievements: Acknowledge and reward team members who actively contribute to reducing the Engagement Gap, motivating others to follow suit.
The Contributors' reports provide insights into the individuals who have contributed to the project. This dashboard allows for the selection of data sources and provides specialized insights.
Select the project from the landing page or from the foundation page.
On the left navigation pane, click Reports>Contributors.
In the top-right corner, you will find the date filter option.
Click on the date filter to open a calendar.
Select the desired start and end dates for the data you want to analyze.
Click Apply to update the dashboard with the selected date range.
For more information, see Filter Date Range.
Locate the drop-down menu for data source selection.
Choose the desired data source from the available options.
The dashboard will update to display data specific to the selected source.
Currently, both GitHub and Git are selected as the data sources by default.
Locate the Display Only New Contributors toggle button.
Toggle it on to display data only for new contributors within the selected period.
Toggle it off to view data for all contributors.
Explore the Total Contributors chart section. When you toggle the New Contributors button, it displays the total new contributors.
Hover over the data points to view specific counts for that time.
Explore Active Contributors Today, Active Contributors This Week, or Active Contributors This Month charts. The Charts are date filter independent. They show real-time data
Click View to expand the list on the right side and see the list of contributors.
The chart shows new contributors when you toggle on the Display Only New Contributors Button.
Move to the "Active Contributors vs. Returning Contributors" chart.
click the drop-down to filter the data.
Understand the comparison between contributors who are active for the first time and those who have returned.
Navigate to the "Leaderboard" section.
You will find a list of the most active contributors.
Review their names and corresponding activity levels.
You will need the meeting link and host key provided in the invitation to join as a host. The following steps help you through the process of joining a meeting as a host that you have been invited to and assigned the host role.
For more information about meeting management in PCC, see Meetings.
You must have been invited to the meeting and assigned the host role.
You must have valid credentials to log in to the Individual Dashboard.
On the Individual Dashboard Home page, you will see all the upcoming meetings under Activities.
Click View More to see the meeting details, such as the meeting link, meeting ID, host key, etc.
Alternatively, you can visit Meetings>MY Meetings> Upcoming Meetings from the left navigation to see the details of upcoming meetings.
You can only find the host key if you are assigned as a host for that meeting. The host key appears within one hour of the meeting and is valid for the next 40 minutes.
Look for the Meeting Link
within the meeting details.
Click on the link to open the meeting in your web browser or preferred meeting application.
You will be prompted to join the meeting.
Click on Join a Meeting to join as an attendee.
Look for the option to "Claim as a Host" within the meeting interface. Click on this option.
Enter the host key provided in the meeting invitation.
Click on Confirm to claim the host role.
You will be notified if the host key is valid and you have been successfully assigned the host role.
On this tab, you can view past events that you have already attended or that have expired.
To change your Linux Foundation password, follow these steps:
1. Log in to https://openprofile.dev.
2. From the left-side navigation pane, click the arrow to expand and navigate to Settings > Password.
3. Provide details in the respective fields, and click Save.
Click Send Password Reset Link from the right side of the window to receive the reset link in your registered email address that you provided while creating your account.
Go to your email address, and click the Reset Password CTA button in the email that you have received from The Linux Foundation.
Provide details in the respective fields, and click Submit.
To correct your date of birth or passport number after submitting the visa letter application, please follow these instructions:
On the Visa Letters page, click the application that you want to edit.
After updating, click OK.
Your application will be updated immediately.
If your visa letter is issued, you can download it from the LF Events> Visa Letters.
Check if the passport number and DOB in your letter is correct. If not, then update your passport number and DOB and download the updated letter.
If any other information is incorrect in your visa letter then you need to contact the events team.
Visa letters are needed for events with international participants. They provide official documentation to support visa applications, helping attendees obtain travel documentation to enter the host country.
Providing visa letters helps expedite the visa application procedure and ensures that event attendees receive the required travel documents to enter the host country.
You can raise a visa letter request only if you have registered for an event.
To apply for the new visa letter, follow these steps:
Navigate to the Individual Dashboard login page. Type your login credentials and sign in. For more information, see the Sign in to Your Account page. If your login credentials are correct, you will be directed to the main dashboard or home page of the web UI.
From the left-side navigation pane, navigate to LF EVENTS> MY Events.
On the MY EVENTS page, click the Visa Letters tab. Click the New Letter Application CTA to access the application page.
On the Visa Letter Application page, scroll down and check the events that you have registered. Click Select to choose the event. After selecting the event, click Next.
If you have not registered for an event, then you must register for the event first. Click Navigate to LF Events CTA.
On the Terms and Conditions page, read the terms and conditions for the visa application and click Next Step.
Click the Cancel button if you want to cancel your new visa application.
Click the Previous Step button to go back to the event selection page.
For questions, contact visaletters@linuxfoundation.org.
On the Apply page, fill out the following information to complete the application:
I am applying for: From the drop-down, select if you are applying for yourself or someone else.
Attendee Type: Select whether you are attending the event or are invited as a speaker.
LFID Username: Enter your LFID if you are applying for yourself.
First and Last Name: Enter your name if you are applying for yourself; otherwise, enter the name for whom you are applying.
Name as per passport: Enter your name the same as the passport. (Many countries do not have first and last names on passports).
Email Address: Enter your email address if you are applying for yourself; otherwise, enter the email address for whom you are applying.
Passport Number: Enter the passport number.
Date of Birth: Enter your date of birth or the person's date of birth for whom you are applying.
Country of Birth: Enter your country or the person's country of birth for whom you are applying.
Phone Number, Job Title, and Company: Enter the mandatory details.
Accommodation paid by: Select the accommodation paid from the drop-down.
Mailing Address: Enter your mailing address for future communication.
Click the Submit Application button.
After you submit your application, the event team reviews your visa letter application.
You can see your application status on the Visa Letters page.
Once your request is approved by the events team, your application status is changed to 'Approved'.
Click the download icon next to the Status to download your visa letter.
When you connect to your LinkedIn account, your open source contributions are automatically affiliated, or you can manually populate your work history.
Your work history may be populated based on your profile. You need to connect and sync your LinkedIn account.
Click Add Position to add your work history manually.
Click Save.
You can manage your profile visibility by making your achievements, such as basic information, technical contributions, etc. You can keep all your profile information private or public based on your choice.
Note: By default, your profile visibility is private.
3. From the top right corner, click the Public Radio button to make your profile's basic information visible to the open source community.
Note: Even if you click Public, your profile's only basic information becomes public (visible to the community). To, make other information public, you must manually turn on each of them.
4. To make your profile private (all information visible only to you, not to the community), click the Private Radio button.
On the next page, click to edit the passport number and DOB.
Log in to .
2. From the left side navigation pane, click the arrow to expand, and navigate to Settings > Visibility.
The Pull Requests Metric measures and analyzes the three key activities related to pull requests:
Pull requests opened
Pull requests closed
Pull requests merged
Pull requests are a mechanism for proposing changes to a codebase, allowing developers to collaborate, review, and merge code changes into the project.
Analyzing the high-level tile (1) representing unique pull requests (opened, closed, and merged) provides valuable insights into the health of the codebase.
The detailed chart displays data related to pull requests opened, closed-unmerged, closed-merged, and the total cumulative pull requests over the selected time period. On the left side, the chart shows the chart trend summary (4).
Collaboration and Code Review: It provides insights into the active participation of developers and the effectiveness of the code review process. If the number of Pull Requests opened is high, the user can complement this data with other Pull Request metrics such as first time to Review, and Pull Request Cycle Time to find out the cause of the high number of Pull Requests open but not acted upon/closed/merged.
Community Engagement: A higher number of pull requests indicates an engaged community that actively contributes to the project.
Quality and Maintenance: By analyzing the number of pull requests opened, closed, and merged, you can assess the health of the codebase, identify areas that need attention, and ensure timely reviews and merging of contributions.
Date: April 08, 2024
Insights is an open-source analytical tool that provides insights from analyzing open source software (OSS) projects.
Insights helps project leads and technical managers understand their team members' engagement and participation in open source projects, and identify the most active and productive contributors.
No new features have been added in this release.
Backend Performance: Strengthened backend performance for Organization Dependency, Contributor Dependency, and Leaderboard tables on the Overview page by integrating DBT Platinum models, significantly improving data processing times.
UI Enhancements: Initiated a clean-up of the plugin's interface to streamline user experience.
Project Metrics: Enhanced the efficiency of fetching key project metrics data, ensuring more accurate and timely insights.
UI Enhancements
Active Days Chart Width and Sizing Adjustments: Modified to align with the sizing of other bar charts for visual consistency.
New Sidebar Navigation: Implemented an enhanced sidebar navigation system for improved user experience.
Progress Bar Styling Updates: Revised progress bar designs to match our latest stylistic preferences.
UI Card Alignment: Updated user interface cards to adhere to the new LFX Style Guide, ensuring a cohesive look and feel.
Resolved issues with exporting PNG files in the Geographical Distribution section, mailing list components, and velocity charts.
Bug fixes in Pagination for Organization and Contributor Dependency charts
Resolved issues where the Active Contributors chart wasn't loading in the Reports Contributors section.
Fixed bug on Best Practices flyout sidebar error.
Some of the projects are still onboarding, so the data may not be correct.
The date range filter in the dashboard module may not always display the correct data when selecting custom date ranges.
You may encounter occasional inconsistencies in data synchronization between Insights and external data sources, leading to discrepancies in reporting.
On the Projects page, you can see the project cards of the selected foundation with their project maturity tags.
You can filter the project cards using the Maturity Level, Rating, and Accepted filter options.
Insights V3 uses the Average Review Time by Pull Request Time metric to provide insights into the duration it takes for pull requests to be reviewed.
Average Review Time by Pull Request Time refers to the average duration it takes for pull requests to be reviewed by peers or project maintainers. It measures the time span between the creation of a pull request and when it receives thorough review feedback.
The chart consists of 5 bars, each of a different color. Each bar displays the average lead time in hours or days for pull requests based on the size of the request.
We have 5 buckets of Pull Request Sizes. They are:
1-9 lines
10-49 Lines
50-99 Lines
100-499 Lines
500+ Lines
Pull Request Size is computed by Lines "Changed". Lines changed could be lines of code added, deleted, or updated.
The length of the color inside the bar is determined by the average Review time. i.e., the longer it takes, the longer the length of the color inside the bar.
Code Quality Assurance: The metric helps you monitor the speed at which pull requests are reviewed. By minimizing the average review time, you can enhance the chances of identifying and resolving code issues promptly, resulting in higher code quality and overall project success.
Collaboration and Engagement: Prompt review feedback encourages active collaboration among contributors. It helps to maintain a responsive and interactive process. When pull requests receive timely reviews, contributors can address feedback and iterate on their code changes faster.
Project Velocity: Timely code reviews contribute to higher project velocity. The Average Review Time metric provides insights into the responsiveness of the review process, identifying areas for improvement. Minimizing review times helps ensure that code changes are integrated swiftly, allowing projects to deliver new features or updates faster.
The Drifting Away Contributors metric focuses on identifying contributors who were once active in an open-source project but have gradually become less engaged over time.
This chart is not impacted by time filter changes. That means the data will always show with respect to "today".
Drifting Away Contributors are:
Users who made at least 5 code contributions at all times for the project.
At least one of those contributions must be made in the last 6 months.
The contributor disappeared over the last 3 months.
The Drifting Away Contributors metric is essential for maintaining a healthy and active contributor community. By identifying contributors who are gradually becoming less engaged, project managers can take proactive measures to understand their reasons for disengagement and find ways to re-engage them.
Insights V3 uses the Average Lead Time by Pull Request Time metric to provide insights into the time it takes for pull requests to be completed.
Average Lead Time by Pull Request Time refers to the average duration it takes for pull requests to progress from opening to merging. It measures the time span between the creation of a pull request and its successful inclusion into the project's codebase.
The chart consists of five bars, each of a different color. Each bar displays the average lead time in hours/days for pull requests based on the pull request size.
We have five buckets of Pull Request Sizes. They are:
1-9 lines
10-49 Lines
50-99 Lines
100-499 Lines
500+ Lines
Pull Request Size is computed by Lines Changed. Lines changed could be lines of code added, deleted, or updated.
The length of the color inside the bar is determined by the average lead time. i.e., the longer it takes, the longer the length of the color inside the bar.
It is the "Average" Lead Time, so compute the average lead time for all PRs for a certain size and display the lead time in minutes/hours/days
Workflow Efficiency: This metric provides valuable insights into the efficiency of the pull request workflow. Optimizing the lead time results in a faster integration of code changes and promotes collaboration among contributors.
Collaboration and Feedback: It reflects the speed at which contributors receive feedback on their code changes. A shorter lead time indicates a more responsive review process, encouraging contributors to engage actively..
Project Velocity: Monitoring the average lead time enables project managers to assess the overall project velocity. A shorter lead time helps maintain a high project velocity, ensuring rapid innovation and faster delivery of software features.
The New Contributors Dashboard analyzes the participation of new contributors in the project. It provides a leaderboard of the number of new contributors and ranks them based on their contributions over a selected period.
Sustainability and Succession Planning: The continuous involvement of new contributors ensures the long-term sustainability of open-source projects. As existing contributors may move on or take up different responsibilities, new contributors play a vital role in filling those gaps.
Fresh Perspectives and Ideas: New contributors bring fresh perspectives, ideas, and diverse skill sets to the project. They may offer innovative solutions, identify areas for improvement, and contribute to the overall project evolution.