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...
Release Date: 27/March/2023
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
Committees - Updated table to allow the user to click the member's name to view and edit committee members to reduce clicks
Committees - Updated committee members table to allow users to set numbers of rows loaded per page
Committees - Added ability to manage committee mailing lists directly from the committee's page
The following list provides new updates to the existing features:
Cloud Providers - Updated text describing AWS billing reflect that costs will be charged for the current month's costs up to today.
PCC - Fixed a bug where searching for projects was showing archived projects while the archive toggle was turned off
Mailing Lists - Updated error handling when adding a new mailing list and it fails due to primary domain being a delegated domain
The following list provides you the bug fixes that are applied in this release:
PCC - Fixed a bug where our issue where our in-memory cache for the BFF was not working properly in production Meetings - Fixed query for getting past meetings where recordings were not visible for past meetings
Meetings - Fixed recurring dropdown options on manage meeting with custom selection and you the user changes the start date
Mailing Lists - Fixed column separator alignment of the secondary subscribed email per user in the mailing list
NA
Release Date: 02/March/2023
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our
Tools Onboarding
Meeting Management - Updated UI/UX for managing a meeting where the meeting details and participants are now on a single page
Mailing Lists - Fixed a bug causing specific lists to not load due to a member missing user_id field
Project Details - Fixed description text UI overflowing into next element
EasyCLA - Fixed issue where grandchild projects are allowed to enroll in foundation CLA group
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
IT services
Tools Onboarding
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
General - PCC now shows dynamic page titles in browser tabs for easier identification for users who have multiple PCC tabs open
Committees - Added verification status on committee members to show if the member has a verified LFID or is pending email verification
The following list provides new updates to the existing features:
General - Updated sidebar logo container to have a minimum height that stops the navigation links from moving during load
Email Forwards - Migrated email forwarding management under Domains for LF-managed domains
Committees - Updated committee meeting statistics to follow the updated design
Mailing Lists - Updated page loading waterfall to show elements as soon as it's available, providing a better UX.
The following list provides you the bug fixes that are applied in this release:
Domains - Fixed domain transfer status refresh on code submission
Committees - Fixed bug where searching via email was case sensitive
Docker Hub - Fixed issue where admin users were not able to delete Docker Hub repositories
NA
Release Date: 08/February/2023
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
General - Updated LFX header to an updated design
General - Updated PCC's left navigation to an updated design
Meeting Management - Added the ability to clone upcoming meetings
The following list provides new updates to the existing features:
General - Ability to open links on the left navigation in new tabs
Committee - Updated the way committees and committee member pages are loaded to display data as soon as it is available for better UX
Committee - Updated toast error message when trying to add a committee with a duplicate name to be more clear on why there is an error
The following list provides you the bug fixes that are applied in this release:
Meeting Management - Fixed issue where the meeting time was incorrectly displayed due to a deprecated library
Meeting Management - Fixed an issue where the calendar was expanding and shrinking during the initial load
Meeting Management - Fixed an issue where the longest meeting recording was not linked to past meetings
NA
Tools Onboarding
Committee - Fixed an issue where adding a committee member was not populating the member's first and last name correctly
Committee - Fixed an issue where getting members were returning a 404 when one or more of the members had bad data from the user service
Source Control - Fixed documentation link for adding a user to an organization
Release Date: 24/January/2023
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
NA
The following list provides new updates to the existing features:
Insights - Updated GitHub repositories to be sorted by repository name
Committee - Added committee voting status on the committee table
Cypress - Removed login requirement for end-to-end testing and stub remaining endpoints
The following list provides you the bug fixes that are applied in this release:
Committees - Fixed remaining committee routes that were not updated to reflect the new navigation structure
Project Definition - Fixed issue where the parent project field was incorrectly being set to required in certain scenarios
Project Details - Truncate project details website when text exceeds the allowed width
NA
Tools Onboarding
EasyCLA - Added ability to disassociate GitHub organization from EasyCLA
EasyCLA - Removed GitLab project added under grandchild from CLA group
Mailing List - Added ability to list mailing lists that are part of the current projects' subproject in the mailing lists table
Mailing List - Fixed issue where users were unable to navigate from the mailing lists page
Mailing List - Fixed separator alignment issue on the mailing list table
Mailing List - Fixed bug where Voting Status and Role columns were not displayed when committee voting was enabled
Mailing List - Fixed remaining mailing lists routes that were not updated to reflect the new navigation structure
Meeting Management - Fixed width issue with time picker on meeting management
Meeting Management - Fixed issue where committee members were not filtered based on voting status while managing participants
Meeting Management - Fixed issue where the current user is added to meetings was being duplicated in meeting participants
Meeting Management - Fixed navigation bug where users were not able to view legacy Zoom users
Source Control - Fixed refreshing of the page when a GitHub organization is added for the first time, or when it is removed
EasyCLA - Fixed organization status colors based on the organization's connection status
Insights - Fixed GitHub updated repositories visibility when viewing a filtered list
LFX Tools allows you to onboard various projects and data connectors related to Security, Insights and EasyCLA.
The LFX Security tool provides automated vulnerability scanning and provides visibility into potential vulnerabilities to help projects address top security concerns.
The Security service tool allows you to perform the following:
GitHub Onboarding
Manage Vulnerabilities
Manage False Positives
Manage Inclusive Naming
For more information on Security Services, visit .
In certain scenarios, if the administrator wants to ignore specific secret types, secret values, or paths, they can do so by creating an ignore.yaml file. On creating the ignore.yaml file, the file should be placed into the root directory of the repository, within a .blubracket folder.
When a match of the ignore file is made, an alert will not be created (but an event will still be generated).
For example, below is a repository called Test1, which has a .blubracket folder and within the folder is the ignore.yaml file.
A sample .blubracket/ignore.yaml is provided below:
Content Credit from .
Ignore by file path
- paths:
- "**/*_test.go"
- cli/cmd/default-sensitive-words-config.yaml
- cli/cmd/data/*
# Ignore by secret value
# Equivalent to 'secret_value == my_password OR secret_value == my_token'
- secret_values:
- my_password
- my_token
# Ignore by secret type
# Equivalent to 'secret_type == password_assignment OR secret_type == secret_assignment'
- secret_types: password_assignment
Currently, you can only set up email forwarding for the Primary Domain.
To enable email forwarding, follow these steps:
1.Go to the domains list and click the icon from the primary domain and select Email Forwarding.
2.The flyer message is displayed with status Ok message. Click Enable to enable the Email Forwarding.
3.A pop confirmation message appears. Click OK to proceed with email forwarding.
4.A flyer message appears informing that the email forwarding is successfully enabled.
You can add the email recipients after enabling the email forwarding service.
To add email recipients, perform the following:
1.After enabling the email forwarding service, the Email Forwarding page appears. Click + Add Forward.
2.The Add Email Forwarding dialog box appears. Enter the Alias name. Click Add Recipient and enter the email ID and click Add.
Manage false positives allows you to define few parameters and assign values to them which can be used to signal false positive at the time of scanning for code secrets. When you define a parameter as a false positive, you can easily detect these
PCC Security tool allows you to add a false positive parameter which allows the
To add a false positive pattern, perform the following steps:
1.Login into .
2. Search for the required project. The Project dashboard appears. Click Security from the LFX Tools STATUS tab.
You can also navigate to Security from the Vertical Sidebar navigation menu. Click LFX Tools and then select Security.
3.The Security page appears. From the Manage False Positive tab, click Proceed.
4.The Manage False Positive page appears with the list of defined false positive parameters. Click Add False Positive Pattern to add a new false positive parameter.
You can delete the existing false positive parameter by click of delete icon.
You can update the existing false positive parameter by click of edit icon.
5.The Add False Positive Pattern dialog box appears. There are three parameters that are available for you to select and define. After defining the parameter, click Add to add the parameter as false positive. The three parameters are:
Path - Define the path for which you want to flag
Secret Type - You can select the required secret type from the drop-down list. Some of the secret types are password assignment, JWT toke, AWS key and many other secret types are available for your to select.
Secret Value - You should use a regular expression in order to define a value for Secret Value.
A regular expression (regex or regexp) is a sequence of characters that specifies a search pattern. Usually such patterns are used by string-searching algorithms for "find" or "find and replace" operations on strings, or for input validation. For more information, refer .
You can add the words which depict people unfairly in an insulting manner and exclude people based on their ethnicity, gender or color. LFX will scan for these non inclusive words in the code. You refer Non Inclusive Language section for more information.
To add non inclusive words, perform the following steps:
1.Login into PCC.
2. Search for the required project. The Project dashboard appears. Click Security from the LFX Tools STATUS tab.
You can also navigate to Security from the Vertical Sidebar navigation menu. Click LFX Tools and then select Security.
3.The Security page appears. From the Manage Inclusive Naming tab, click Proceed.
4.Enter the non inclusive word in the Add word box and click +Add. The added non inclusive words are listed under NON-INCLUSIVE LANGUAGE.
To delete a non inclusive word, perform the following steps:
1.From the Manage Inclusive Naming tab, click icon that you want to delete from the list.
2. The Delete Keyword dialog box appears. Click Delete to confirm the deletion of the word.
Release Date: 03/October/2022
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
Committees - Added support to add subcommittees
Insights - Ability to onboard projects to Insights (GitHub)
Meetings - Updated invite participant to allow name searching and field population
The following list provides new updates to the existing features:
MISC - Update DataDog RUM instrumentation to enable screen recording
Setup - Reenable project artifact management (uploading project files to share in Organization Dashboard)
Mailing List - Updated name field to be readonly and remove prefix on label
The following list provides you the bug fixes that are applied in this release:
Meetings - Fixed issues relating to attendees roster
Mailing List - Added custom error messages on edit mailing list screen when list is private
Committees - Fixed If there is no committee next meeting display None
NA
You can add service records such as Pantheon, Netlify, and GitHub pages for your domain.
To setup a service record, perform the following steps:
1.Go to the Domains page for the required project. The domain page appears with the list of domains registered with the project.
2.Click icon and select Manage Records.
3.Click +Add Service Record from the Manage Records page.
3.The Add Service Record dialog box appears. Click Services, select the required Service from the list and click Add.
4.The service records are listed under Existing Service Records list.
You can redirect a domain or subdomain to another URL. Redirects are a way to forward visitors and search engines to a different URL than the one they requested. You can use redirects when you’re moving content around and you want the content to retain its value.
To redirect a domain from one domain to another domain, perform the following:
Go to the Domains page for the required project. The domain page appears with the list of domains registered with the project.
Click icon and select Manage Records.
3.Click +Add Redirect from the Manage Records page.
4.The Add Redirect dialog box appears. Enter the redirect domain under To box and click Add.
5.The redirected domain is listed under Redirects list.
If you want to update the redirect domain, click the edit icon.
If you want to delete the redirect domain, click the delete icon.
Release Date: 22/December/2022
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
NA
The following list provides new updates to the existing features:
General - Reorganized our navigation elements into Operations, Collaboration, Development, and LFX Tools
General - Add a release-notification popup which can tell users about changes or new features after a PCC upgrade
The following list provides you the bug fixes that are applied in this release:
Projects - Fixed chopped link between project and child projects
Projects - Fixed start trim on Formal Name on project Legal page
Projects - Fixed vertical scrollbar appearing on elements
NA
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our website.
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
Meetings - Added option to resend meeting invitation.
Meetings - Added UTC suffix to recurring options.
Committees - Added Appointed by value visible in table view
The following list provides you the bug fixes that are applied in this release:
Mailing Lists - User is now able to change lists posting permission from custom to any other available option.
Committees - Added loading handler to avoid over pagination from the server.
NA
EasyCLA streamlines the management and execution of Contributor License Agreements (CLAs), to help projects ensure that contributions are made in accordance with project policies. It is the only CLA management tool to correctly support both individual and corporate CLA workflows in an automated environment.
To setup the EasyCLA service using PCC:
1.Login into PCC.
2. Search for the required project. On Project dashboard , click CLA under the LFX Tools tab.
You can also navigate to EasyCLA from the Vertical Sidebar navigation menu. Click LFX Tools and then select EasyCLA.
3.For detailed information on how to setup the CLA, see .
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Tools Onboarding
DataDog - Added user to RUM traces.
Meetings - Updated meetings to hide or display host keys based on time.
Projects - Added tooltips to file inputs.
Generic - Added maintenance feature flag guard for all services.
Tools Onboarding
Meetings - Removed “Add Yourself” CTA and adds logged in user by default when scheduling a meeting
Domains - Improved the validation behavior of subdomains and custom domain targets
Email Forwarding - Updated alias recipient email validation
Legal - Updated legal parent from searchable input to dropdown
DockerHub - Updated feature flag for DockerHub
Legal - Improved validation messages coming from unexpected Salesforce errors
Membership - Fixed an issue in removing newly added tier
Dashboard - Fixed long project name appearing chopped
EasyCLA - Fixed download ICLA on Safari Browser issue
EasyCLA - Fixed download CCLA bug
Tools Onboarding
Meetings - Correctly populate Recording and Transcript enabled/access values on Manage Meeting popup form
Meetings - Correctly populate Committee filter value on Manage Meeting modal form
Meetings - Fixed issue on Manage Participants page if the meeting has no additional invitee list
Meetings - Show the correct visibility for the meeting on Manage Meeting popup form
Meetings - Show a validation error if the user sets the date of a meeting to a date later than the "ends after" date of that meeting's custom recurring schedule.
Insights - Ensure that "foreign" GitHub organizations are hidden when configuring Insights for that project. (Repos instrumented in Insights without the GitHub organization being connected to the project or its parent, are not supported in PCC and require manual resolution via Support.)
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
IT services
Tools Onboarding
This sections provides you with list of new features and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
Meeting Management - Ability to enable Recording and Transcripts on meetings
Meeting Management - View Recording and Transcripts on Past Meetings
Meeting Management - Ability to view and share the registration link for public meetings
Security - Activity Logs for repositories showcasing various updates made to the security settings
Security - When all repositories within an organization are linked to projects other than the current one you’re viewing, links are provided to other projects directly within the table for better UX
The following list provides you the bug fixes that are applied in this release:
AWS - Implemented ellipsis on long email text
Domains - Fixed bug relating to delegating DNS
Meeting Management - Various bug fixes relating to parsing and selecting meeting times
Meeting Management - Various fixes relating to selecting meeting hosts for committee members
Meeting Management - Various fixes relating to setting recurring invites for recurring meetings
Meeting Management - Set max custom recurrence of a meeting to 49
Meeting Management - Ability to create meetings with zero participants
Meeting Management - Hide Meeting Host column when managing participants until feature is ready (admins are still able to claim host using the host key available in PCC).
MISC - Fixed table pagination issue when deleting rows results in one less page - user will be navigated to the new last page/previous page
NA
Enter the domain name that you want to transfer to your project, and click Check Availability.
Once done, it will show that the domain has been taken. Select Yes; transfer Domain to proceed.
On the Next page, you will be asked if you want to delegate the DNS to the Linux Foundation or keep DNS management at its current location. In most cases, you will want The Linux Foundation to manage DNS.
Obtain the Zone File: The current domain owner needs to get the Zone File from their registrar. If they do not know where to find it, they should contact their registrar's support team for help.
Import the Zone File:
Once you have the Zone File, upload it using the Import DNS zone file feature.
If the domain does not have an active Zone File, skip to step 4.
Verify the Zone File:
After uploading, verify that all records are correct. If any of the records are missing from PCC, it might cause issues after the transfer.
4. Update Name Server (NS) Records:
Copy the following NS records ns1.dnsimple.com, ns2.dnsimple-edge.net, ns3.dnsimple.com, ns4.dnsimple-edge.org and send them to the current domain owner. The owner needs to update these records in their registrar's settings. If they need assistance, they should contact their registrar's support team.
Verify NS Delegation:
After the NS records are updated, it may take up to 24 hours for the changes to sync globally. Click Verify NS Delegation to check if the process is complete.
If the domain is not delegated after 24 hours, wait another 24 hours and check again.
Skip DNS Zone Migration: If you prefer to keep the DNS management with the current domain owner, select the option Skip DNS Zone migration. IMPORTANT: If the domain's DNS is hosted by the registrar being transferring from, ensure those DNS records are moved elsewhere to prevent service interruption upon transfer.
Enter the Transfer Code: You will be asked to provide a transfer code. Obtain this code from the current domain owner.
Confirm DNSSEC:
The current domain owner can verify if DNSSEC is enabled. If DNSSEC is active, contact support for assistance.
DNSimple Users:
If the current domain owner is also using DNSimple (the Linux Foundation's registrar), reach out to support for further guidance.
Begin the Transfer:
Click Begin Transfer to initiate the process. Be aware that the transfer can take up to 7 days to complete.
The Domain will be listed in your project with the status Transfer Code Needed.
Provide the transfer code to complete the domain transfer. To provide the transfer code, click icon, select Continue Transfer and enter the transfer code that you will receive from the registrar of your domain. Select My Domain is unlocked and My DNS Service is not hosted and click Begin Transfer.
Release Date: 13/December/2022
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our .
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features, updates and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
Meetings: Release Flexible Meeting Scheduling, part 1
EasyCLA: Added support to create "CLA group" at a child-project level, even when a foundation-level "CLA group" is present
Mailing Lists: Added user search for new subscribers, for consistency with Committees & Meetings
The following list provides new updates to the existing features:
General: Added "Community Forum" link to the Get Help dropdown on the LFX Header
Project Setup: Update CII Best Practices Badge field to be OpenSSF Best Practices Badge
Project Setup: Updated "Escalate Review" link on Draft projects to contact LF Formation Team instead of LFX support team
The following list provides you the bug fixes that are applied in this release:
Project Setup: Update error handling to display more helpful messages for various errors returned by the LFX API
Project Setup: Fixed an issue with the color picker for Branding colors
Committees: Fixed a bug where a user could not clear the date picker when managing a committee
NA
Manage Vulnerabilities allows you to perform the following tasks:
Enable or disable vulnerability scanning for a repository to refine scanning report of the project.
Auto enabling repositories for scanning vulnerabilities.
You can enable or disable a repository for vulnerability scanning in PCC from the Manage Vulnerabilities tab. If you enable a repository for vulnerability scanning, the repository is scanned for the vulnerabilities. If you disable the vulnerability scanning for a repository, the scanning will be skipped for the selected repository and vulnerabilities are not detected.
To enable or disable a repository for vulnerability scan, perform the following steps:
1.Login into .
2. Search for the required project. The Project dashboard appears. Click Security from the LFX Tools tab.
You can also navigate to Security from the Vertical Sidebar navigation menu. Click LFX Tools and then select Security.
3.The Security page appears. Click Manage Vulnerabilities tab, all repositories of the project are listed in alphabetical order.
The fail scan details for the repository such as time and date of the is displayed when you click the icon.
4.Under Scan Vulnerabilities tab, toggle scan button to enable or disable a repository from scanning.
You can also enable or disable scanning for all repositories by toggle of Scan Vulnerabilities.
5. Under Last Scan Results tab, you can see whether the repository scan has been successful or failed while scanning the repository.
When the scan of the repository is successful, it is displayed as Successful and if there are any errors, it will be displayed as Failed.
The fail scan details for the repository such as time and date of the is displayed when you click the icon.
You have an option to auto enable scanning of repositories for vulnerability scanning when a new repository is added in the GitHub project. When you select the Auto enable option, all new repositories are scanned for the vulnerabilities.
You can the Auto Enable New Repositories toggle button to set the auto scanning of the new repositories. This button is available in the Manage Vulnerabilities tab.
Tools Onboarding
Security: Added new Snyk status on Manage Vulnerabilities page
EasyCLA: Added necessary info to complete a Gerrit installation after enabling the service from PCC
Confluence & Jira: Hide Cloud Provider column when the Jira or Confluence are unmanaged and the cloud provider is not known
LFX Tools onboarding: Updated a message explaining why Archived & Formation projects cannot be onboarded to other LFX Tools
Groupsio: Fixed an issue that caused the subscriber table to be mis-aligned sometimes
Domains: Updated empty list message when there are no service records or redirects
Jira: Fixed an issue where errors were not handled correctly
Insights: Fixed various layout issues on the connector overview page
Insights: Fixed various edge cases related to onboarding GitHub Organizations
Troubleshoot Delegation Issues:
If after 48 hours the domain is still not delegated, visit zone.vision, enter the domain name, and check the Name Servers section:
If the correct NS records (ns1.dnsimple.com, ns2.dnsimple-edge.net, ns3.dnsimple.com, ns4.dnsimple-edge.org) are not showing, repeat step 4.
If the correct NS records are showing, contact support for assistance.
Complete the Transfer:
Once the NS delegation is verified, enter the transfer code provided by the current domain owner.
If DNSSEC is enabled on the domain, or if both you and the current owner use DNSimple, contact support for further assistance.
Begin Transfer:
Click Begin Transfer to start the process. The transfer can take up to 7 days to complete.
Onboarding projects into LFX Security is done from the PCC (Project Control Center). As part of this onboarding, a Security Bot is installed on GitHub Organizations of the project.
To setup the Security service using PCC, perform the following steps:
1.Login into PCC.
2. Search for the required project. The Project dashboard appears. Click Security from the LFX Tools dropdown menu.
You can also navigate to Security from the Vertical Sidebar navigation menu. Click LFX Tools and then select Security.
3.The Security page appears. From the GitHub Onboarding tab, click the icon available next to Connect.
4.Enter the GitHub organization name in the Organization Name and click Connect.
Make sure that you logged into the GitHub.
5.The Install Security Bot on GitHub.org instructions page appears. You can read the instructions on how to install the Security Bot from this page. Click Install Security Bot button.
6. A list of GitHub organizations associated with the login account are listed and displayed. Select the required organization for which you want to install the Security bot.
7.The Install & Authorize LFX Security GitHub App page appears. This page provides the following information:
Information on the permission requested for the selected repositories. The LFX Security requests the following permissions from the GitHub:
Read access to administer, code, check commit status, lookup members, and other metadata.
Read and write access to organization hooks, pull requests, and repository hooks.
Click Install & Authorize to install the LFX Security GitHub App.
8.The LFX Security Service GitHub app is installed successfully. You can see the installation success message.
You will also receive an email after successful installation of the LFX Security GitHub App.
9.In the PCC page, you need to click I'm Done Installing the Security Bot after completing the installation process.
10.You can see the list of GitHub organizations along with the repositories for which the Security bot has been successfully configured.
A green dot present with the GitHub organization name indicates that the Security bot is successfully installed.
You can uninstall the security bot at any point of time from the PCC. When you uninstall the security bot, the security scanning for the GitHub organization is discontinued. You cannot see the vulnerabilities associated with your GitHub organizations.
To uninstall Security service from PCC, perform the following steps:
1.Login into .
2. Search for the required project. The Project dashboard appears. Click Security from the LFX Tools dropdown menu. The GitHub organizations are listed. Select the settings icon and click Disassociate GitHub Org.
3.The Uninstall Security Bot on GitHub.org instructions page appears. You can read the instructions on how to uninstall the Security Bot from this page. Click Uninstall Security Bot button.
4.The LFX Security GitHub App opens in a new tab. Click Uninstall from the Danger Zone.
You can uninstall the Security bot from all the repositories associated with your GitHub organization by selecting All Repositories or select specific repositories for which you want to uninstall the Security bot by selecting Only Select Repositories.
5. A pop message appears informing that the Security bot will be uninstalled for the selected repositories. Click OK to continue with the uninstallation process.
6.In the PCC page, you need to click I'm Done Uninstalling the Security Bot after completing the uninstallation process.
7.The GitHub repositories will be removed from the Security dashboard. But, you can see the GitHub organization name in the Security dashboard.
A red dot present with the GitHub organization name indicates that the Security bot is successfully uninstalled.
8.If you want to remove the GitHub organization completely from the Security dashboard, click Disassociate Organization.
9.A popup message appears informing that the GitHub organization will be disassociated. Click Disassociate to continue with the disassociation process.
You have an option to suspend the Security service scanning without uninstalling the Security bot. When you suspend the Security service, the bot will not be uninstalled. You can revoke the suspension at any point of time by Unsuspending.
To suspend the Security service, perform the following steps:
1.Login into .
2. Search for the required project. The Project dashboard appears. Click Security from the LFX Tools dropdown menu. The GitHub organizations are listed, select the settings icon and click Configure Security Bot.
3.The LFX Security GitHub App opens in a new tab. Click Suspend from the Danger Zone.
4.A popup message appears informing that the Security bot will be suspended. Click OK to continue with the suspension process.
5.The GitHub repositories are suspended from the Security dashboard.
A orange dot present with the GitHub organization name indicates that the Security bot is suspended.
To revoke the suspended Security service, click settings icon and click Configure Security Bot and click Unsuspend from the Danger Zone.
You can associate an individual repository to a project. PCC allows you to select an individual repository and allows you to assign it to a project.
To associate an individual repository, perform the following:
1.Login into PCC.
2.Select the required project and click Security from the LFX Tools dropdown menu.
Make sure you see Security bot configured status under Configuration Status column. You can only select the required repository if the security bot is configured. \
If the status shows as Security bot not configured, you cannot select the repository.
3. Select the required individual repository from the Assigned to Project column that you want to assign to the project.
The below table provides the list of roles and respective permissions associated with Project Setup for Project Definition:
Create a subproject (subject to review)
✅
X
The below table provides the list of roles and respective permissions associated with Committees for Project Definition:
Access Control Service (ACS) provides the capability to regulate access to various services by providing authorization and authentication to internal as well as external resources.
ACS provides policy access to manage users by providing authentication and authorization. ACS defines a role and assigns these roles to the users. This helps the Linux platform provide secure and safe access to various services.
Role-based access control (RBAC) is an approach to restrict a system access to authorized users. RBAC acts as an authorized system to manage resource access by assigning the required permissions and restrictions.
Roles are created and assigned to a member. Scope provides a limited boundary for the role to access their rights and permissions. You can create a role that are are specific for a particular boundary and are limited for a particular scope of actions.
Various scopes are available in the LFX platform. Some of the scopes are:
Project
Organization
Project and Organization
These sections provide various roles that are created for Linux Foundation platform. The various roles are listed below:
CLA Signatory is a member belonging to an organization who has the signing authority for CCLA contracts.
Company Admin is an individual member belonging to an organization who has been authenticated by the Owner with full control over projects, organization, and users.
Owner can assign the company Admin role to more than one member.
Company Owner is an individual member belonging to an organization who has been authenticated with full control over projects, organization, and users. The owner also has control over ACS.
Contact is a member of an organization that is also a Linux Foundation customer.
A contributor may be an individual member or a member belonging to any organization. The contributor is assigned and authenticated to update and work on their own projects.
The donor may be an individual member or a member belonging to any organization who donates to a project. Donor has access to the projects to which they are donating.
LF Events is an internal employee of Linux Foundation who can create and manage events.
LF Exec is an internal employee of Linux Foundation who can manage sales operations.
LF Finance is an internal employee of Linux Foundation who can manage financial operations.
LF Legal is an internal employee of Linux Foundation who can manage legal operations.
LF Ops is an internal employee of Linux Foundation who can manage all administrative activities of the organization.
LF PM is an internal employee of Linux Foundation who can manage multiple projects.
LF Training is an internal employee of Linux Foundation who can manage the role of trainer and trains the members on various projects.
Mentee may be an individual member or a member belonging to any organization who can enroll in a project as an apprentice or trainee. Mentees will get training and guidance on the project that can help the mentee to advance in their careers.
Mentor may be an individual member or a member of any organization who contributes to various open source projects and helps to train and guide mentees on their apprentice programs.
Project Maintainer is an individual member who has been assigned administrative rights to control and manage activities related to mentorship programs and open source projects.
Project Manager is a member of an organization who has been authenticated to create and manage projects and users.
Project Managers can manage only projects created by them and users associated with the projects
An authenticated individual who has been assigned predefined roles and permissions by the administrator. A user can view all projects and organizations.
Training
Events
X
X
View project committee member email addresses
✅
✅
✅
✅
X
View project committee member names & roles (no emails)
✅
✅
✅
✅
X
View project committees
✅
✅
✅
✅
X
X
X
X
Update project category, description, branding, social handles, and basic metadata
X
X
X
X
X
Manage project membership benefits
X
X
X
X
X
Update project personnel roster
X
X
X
X
X
Manage project artifacts (files & links)
✅
X
X
X
X
View project artifacts (files & links)
✅
✅
X
X
X
View project legal entity settings & charter
✅
✅
✅
X
X
View project personnel roster
✅
✅
✅
X
X
View project membership tiers & benefits
✅
✅
✅
X
X
View project name, stage, description, branding, social handles, and demographic attributes
✅
✅
✅
✅
✅
View the list of IT Services & LFX Tools in use by a project
✅
✅
✅
X
X
Create & manage project committees & committee settings
✅
X
X
X
X
Add & remove project committee members
✅
X
X
Installing and authorizing LFX Security GitHub App grants these permissions on your account:
Read access to emails
Access to the repositories. You can either provide access to all the repositories or selected repositories within the GitHub Organization.
Source control is a critical component of software development, enabling teams to track and manage updates to their codebase.
Key Features:
Track and manage updates to your codebase
Maintain control over the right version of your code
Collaborate with team members and stakeholders efficiently
The Linux Foundation platform requires access to each GitHub organization hosting your code
The governance body and authorized community members are responsible for day-to-day administration of repositories, teams, and users, unless covered by a specific managed-services agreement with the Linux Foundation.
You can add the following Source Controls tools to your projects:
GitHub is a web and cloud-based service that helps developers to store and manage their code, as well as to track and control changes to their code base.
You can use GitHub as a source control tool to manage your project.
To connect the GitHub account to the PCC, perform the follow steps:
Log in to PCC.
2. Search for the required project. The Project dashboard appears. Click Source Control from the Development tab.
You can also navigate to Source Control from the Vertical Sidebar navigation menu. Click IT Services and then select Development.
The Source Control page appears. Click GitHub and click the icon available in front of Connect.
The Connect GitHub Organization dialog box appears. Enter the Organization Name and click Connect.
Make sure to enter a valid GitHub organization name.
For more information on how to create an organization, refer to .
For more information on how to transfer a repository, refer to .
Once the connection is set, you can see the status of GitHub project and its repositories.
If you change the name of your GitHub organization, you'll need to reconnect it to the PCC. The renamed organization won't be automatically connected, even if the original organization was previously connected.
You can manually add the repositories to the configured GitHub server.
To add repositories to the GitHub server, perform the following steps:
Go to the GitHub server in the Source Control and click + Add Repository.
The Add Repository dialog box appears. Enter the Repository Name, Website, and Description. Click Add to add the repository.
You can also enable the DCO, Issues and Wiki by using the Enable DCO, Enable Issues and Enable Wiki toggle button respectively.
Install the DCO app before enabling the DCO on the repository. Refer to for configuration. After configuring the DCO in GitHub, you can enable the DCO in the PCC.
Enabling DCO in the PCC:
Adds branch protection rules for the default branch, so that PRs must be made before changes can be merged.
It adds a required DCO status check for PRs
If the DCO app is not installed and configured for the organization before DCO is enabled on a repository, all changes to the default branch will be blocked until the app is added.
Further troubleshooting: Private Repositories cannot have DCO unless the organization is on a Github Pro plan.
Your project should have its own GitHub organization, separate from your company's GitHub organization, and which is not shared with other, non-Linux-Foundation projects.
If you need to, create a new GitHub organization for this project, and have a user who is an owner in both organizations transfer each project repository to this organization.
Then, invite the user “thelinuxfoundation” as an owner at the organization level (not per repository) to the GitHub organization, and connect them in Project Control Center.
We cannot accept invites unless the organization is associated with a project. Please make sure to add the project to the PCC before sending an invite to 'thelinuxfoundation" user, or the invite will not be accepted and will expire after 7 days.
For more information on how to invite users to join organization, refer .
If your invite has expired, you must delete it and send a new invite.
You can delete the added GitHub organization from the PCC.
To delete the GitHub organization that is added in the PCC, follow these steps:
Click the Source Control.
Under GitHub, click on the required GitHub organization that you want to delete.
Click the icon and click Disassociate.
The Confirm Disassociation dialog box appears, click Delete to delete the GitHub Organization.
GitLab is an open source code repository and collaborative software development platform for large DevOps and DevSecOps projects. GitLab helps you to automate the builds, integration, and verification of your code.
You can use GitLab as a source control tool to manage your project.
To setup the GitLab account to your project, perform the following steps:
1.Login into PCC.
2. Search for the required project. The Project dashboard appears. Click Source Control from the Development tab.
You can also navigate to Source Control from the Vertical Sidebar navigation menu. Click IT Services and then select Development.
3.The Source Control page appears. Click GitLab and click the icon available in front of Connect.
4.The Connect GitLab Group dialog box appears. Enter the Group Name and click Connect.
The name of the group should be added and not the url or the ID.
5.Once the connection is setup, you can see the status of GitLab project and its repositories.
Gerrit is a web-based code review tool, which is integrated with Git and built on top of Git version control system (helps developers to work together and maintain the history of their work). It allows merging changes to Git repository when you are done with the code reviews.
1.Login into PCC.
2. Search for the required project. The Project dashboard appears. Click Source Control from the Development tab.
You can also navigate to Source Control from the Vertical Sidebar navigation menu. Click Development and then select Source Control.
3.The Source Control page appears. Click Gerrit and then click File Ticket to submit a ticket to configure Gerrit server for your project.
4. In the Support Form, provide details such as summary, project name, Gerrit URL and description. Click Create to submit the request to the support team.
5.Once the support team configures the Gerrit server, the Gerrit server is added in the source control along with the associated repositories.
You can manually add the repositories to the configured Gerrit server.
To add repositories to the Gerrit server, perform the following steps:
1.Go to the Gerrit server in the Source Control and click + Add Repository.
2.The Add Repository dialog box appears. Enter the Repository Name and Description and click Add.
You can use the toggle button if you want to enable the repository as the parent repositories for other repositories.
You can update the repository name and other changes with respect to the listed repository.
To update the repository details, perform the following steps:
1.Go to the required repository and click the ellipsis icon and select Edit Repository.
2.The Edit Repository dialog box appears. You can update the Repository Name, Enable DCO and Description and click Save to update the changes.
You can set a repository as readable from writeable or from writeable to readable. To set the repository as readable or writeable, click the ellipsis icon and select Set Repository as Readable or Set Repository as Writeable.
When the repository is set as Writeable, the Read-only column is set as Yes and when the repository is set as Readable, the Read-only column is set to No.
You can hide a repository and restrict all access to the repository by clicking the ellipsis icon and selecting the Hide Repository and Restrict All Access.
You can delete the listed repository by clicking the ellipsis icon and selecting the Delete Repository.
Private repositories will show as DCO not enabled unless the Github Organization is on a Pro plan or above.
For more information on how to transfer a repository, refer .
A regular expression (regex or regexp) is a sequence of characters that specifies a search pattern. Usually such patterns are used by string-searching algorithms for "find" or "find and replace" operations on strings, or for input validation.
The below tables assists you on how to use different regular expressions:
Character
Explanation
.
Anything. Any character except newline
a
The character a
ab
The below table provides the list of roles and respective permissions associated with IT Services for Operations services:
Match the named group Y
(?R)
Recurse into entire pattern
(?Y)
Recurse into numbered group Y
(?&Y)
Recurse into named group Y
\g{Y}
Match the named or numbered group Y
\g<Y>
Recurse into named or numbered group Y
(?#...)
Comment
One non-whitespace
\w
One word character
\W
One non-word character
Start of match
(?=...)
Positive lookahead
(?!...)
Negative lookahead
(?<=...)
Positive lookbehind
(?<!...)
Negative lookbehind
(?()|)
Conditional
Set flags within regex
Hexadecimeal character YY
\cY
Control character Y
Visible characters, except space
[:lower:]
Lowercase letters
[:print:]
Visible characters
[:punct:]
Visible punctuation characters
[:space:]
Whitespace
[:upper:]
Uppercase letters
[:word:]
Word characters
[:xdigit:]
Hexadecimal digits
The string ab
a|b
a or b
a*
0 or more a's
\
Escapes a special character
Character
Explanation
*
0 or more
+
1 or more
?
0 or 1
{2}
Exactly 2
{2, 5}
Between 2 and 5
{2,}
2 or more
Character
Explanation
(...)
Capturing group
(?P<Y>...)
Capturing group named Y
(?:...)
Non-capturing group
(?>...)
Atomic group
(?|...)
Duplicate group numbers
\Y
Match the Y'th captured group
Character
Explanation
[ab-d]
One character of: a, b, c, d
[^ab-d]
One character except: a, b, c, d
[\b]
Backspace character
\d
One digit
\D
One non-digit
\s
One whitespace
Character
Explanation
^
Start of string
\A
Start of string, ignores m flag
$
End of string
\Z
End of string, ignores m flag
\b
Word boundary
\B
Non-word boundary
Character
Explanation
i
Ignore case
m
^ and $ match start and end of line
s
. matches newline as well
x
Allow spaces and comments
J
Duplicate group names allowed
U
Ungreedy quantifiers
Character
Explanation
Newline
Carriage return
Tab
\0
Null character
\YYY
Octal character YYY
\xYY
Hexadecimal character YY
Character
Explanation
[:alnum:]
Letters and digits
[:alpha:]
Letters
[:ascii:]
Ascii codes 0 - 127
[:blank:]
Space or tab only
[:cntrl:]
Control characters
[:digit:]
Decimal digits
(?P=Y)
\S
\G
(?iLmsux)
\x{YY}
[:graph:]
X
X
Manage project domains, services & URL redirects
✅
X
X
X
X
View project domains, services & URL redirects
✅
✅
✅
X
X
Manage project email forwards
✅
X
X
X
X
View project email forwards
✅
✅
X
X
Manage cloud providers
✅
X
X
X
X
View cloud providers
✅
✅
✅
X
X
The below table provides the list of roles and respective permissions associated with IT Services for Collaboration services:
Create & manage project meetings & participants
✅
X
X
X
✅
View project meetings and participants
✅
✅
The below table provides the list of roles and respective permissions associated with IT Services for Development services:
Connect GitHub, GitLab organizations to a project
✅
X
X
X
X
Disconnect project GitHub, GitLab organizations
✅
X
Register & transfer project domains
✅
✅
X
X
X
X
Deploy Groups.io for a project
✅
X
X
X
X
Delete project mailing lists
✅
X
X
X
X
Create & manage project mailing lists, add/remove subscribers & moderators
✅
X
X
X
X
View project private mailing lists and subscribers
✅
✅
X
X
X
View project public mailing lists and subscribers
✅
✅
X
X
X
View project public mailing lists (no subscribers)
✅
✅
✅
X
X
Deploy Confluence for a project
✅
X
X
X
X
Manage project Confluence spaces
✅
X
X
X
X
View project Confluence deployment & spaces
✅
✅
✅
X
X
Deploy Jira for a project
✅
X
X
X
X
View project Jira deployment
✅
✅
✅
X
X
X
X
X
Deploy Gerrit for a project - coming soon
✅
X
X
X
X
Add & configure project SCM repositories
✅
X
X
X
X
Delete project SCM repositories
✅
X
X
X
X
View project private SCM repositories
✅
✅
✅
X
X
View project public SCM repositories
✅
✅
X
X
X
Connect DockerHub organizations to a project
✅
X
X
X
X
Add & configure project DockerHub repositories
✅
X
X
X
X
Delete project DockerHub repositories
✅
X
X
X
X
View project DockerHub organizations & repositories
✅
✅
✅
X
X
Create, manage, and delete project CI templates - coming soon
✅
X
X
X
X
View project CI templates - coming soon
✅
✅
✅
X
X
Project Control Center (PCC) is a platform that allows project administrators to set up the projects when they get associated with The Linux Foundation. You can set up the projects to use various services that are provided by The Linux Foundation.
PCC assists you in onboarding an open source project with great ease. Project Control Center helps you get started quickly by providing all the support that you need with self-service configuration for governance, membership, IT, developer and collaboration tools, documentation, and community roles. You can read more about PCC by visiting our website.
Some of the prominent features of PCC are listed in the following list:
PCC Dashboard
Creating Projects and Sub Projects
Generic setup services
This sections provides you with list of new features and bug fixes for this release.
The following list provides you an overview of new features implemented in this release:
Insights - Insights now displays a status bar at the top of the page for activated services to indicate the service status.
Security - Updated info text for a false-positive pattern to be more descriptive.
MISC - Updated DataDog logging to be in line with IT Services requirements.
The following list provides you the bug fixes that are applied in this release:
Security - Fixed issue where last scan time for failed scans was showing NaN values due to the API not returning the required key.
Meeting Management - Fixed a bug where the add yourself to meeting link was causing an issue by setting a host value.
Meeting Management - Fixed a DST bug where the user was seeing an incorrect time value for a meeting that was before a DST change.
NA
Tools Onboarding
Setup - Updated field-level validation for new roles (admin, viewer, controller) to give better data management access.
Meeting Management - Fixed the recurrence dropdown to use dynamic weeks instead of static.
Current release notes are now found in the PCC under "Changelog"