chore: W-18839348 - missing required files for ospo compliance #610
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CristiCanizales
changed the title
mshanemc
approved these changes
Jul 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This pull request updates the licensing information across the repository to reflect the current year and company name, and provides comprehensive guidelines for license usage. The most important changes include updating the
LICENSE.txtfile, adding detailed instructions inhow_to_license.md, and ensuring consistency in license text formatting.Updates to licensing information:
LICENSE.txt: Changed the year to 2025 and updated the company name from "Salesforce.com" to "Salesforce, Inc." to reflect current branding.LICENSE.txt: Adjusted references to "Salesforce.com" and "copyright holders" to "Salesforce" for consistency and clarity.Added licensing guidelines:
how_to_license.md: Added a new file with detailed instructions on using the BSD 3-Clause License, including sample license text for source code and recommendations for automating license header updates. Also included guidelines for using the Unlicense for sample/demo code.What issues does this PR fix or reference?
@W-18839348@