Merged
Conversation
tomcollins
previously approved these changes
Apr 4, 2025
Collaborator
tomcollins
left a comment
There was a problem hiding this comment.
Look good and is useful and concise.
Wondering if it needs a disclaimer about running random models locally and the nature of data you give the model access to?
Member
Author
|
@tomcollins any suggested wording? |
Collaborator
|
Something light like: "Please ensure you consider and adhere to any policies and restrictions your organisation places on the use of data with AI and the selection of AI models". ? |
Member
Author
|
Added disclaimer |
tomcollins
approved these changes
Apr 9, 2025
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
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.
Content Guidelines
Post content must not include:
Content Guidelines - Security
Consider if the content of your post, including and images, has any security concerns:
If you have any doubt please seek support from the cyber security team before publishing your content.
Content Guidelines - Reputation
You must consider if the content of your post could cause damage to the reputation of the organisation.
If you have any doubt please seek support from the communications team before publishing your content.
Approval Process
All changes to content must be approved by at least one person from the engineering review control group. This takes the form of a github pull request and is automatically enforced.
Formal approval within the wider organisation is not required by default but may be requested based on e.g. security or reputational concerns.