chore: W-18839348 - missing required files for ospo compliance #674
+75
−6
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
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 includes updates to ownership assignments, licensing information, and documentation. The most important changes involve modifying the
CODEOWNERSfile to reflect a new team ownership, updating the copyright information in theLICENSE.txtfile, and adding a new licensing guide inhow_to_license.md.Ownership Updates:
.github/CODEOWNERS: Changed ownership from@forcedotcom/pdtto@forcedotcom/ide-experience, reflecting a shift in responsibility to the IDE Experience Team.Licensing Updates:
LICENSE.txt: Updated copyright year from 2022 to 2025 and replaced references to "Salesforce.com" with "Salesforce" in the copyright notice and disclaimer. [1] [2]Documentation Additions:
how_to_license.md: Added a new guide explaining licensing practices, including the use of the BSD 3-Clause License for source code and the Unlicense for sample/demo code. Includes examples of license headers and recommendations for automation tools.What issues does this PR fix or reference?
@W-18839348@