Skip to content

Conversation

@BillyRuffian
Copy link
Member

Content Guidelines

Post content must not include:

  • identifiers for production infrastructure e.g. IP addresses, network ranges, cloud provider IDs etc
  • data relating to real customers or staff members

Content Guidelines - Security

Consider if the content of your post, including and images, has any security concerns:

  • would the information be revealing to an attacker?
  • is the content too revealing of backend processes?
  • do we need to make make specific details public?

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.

tomcollins
tomcollins previously approved these changes Apr 4, 2025
Copy link
Collaborator

@tomcollins tomcollins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@BillyRuffian
Copy link
Member Author

@tomcollins any suggested wording?

@tomcollins
Copy link
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".

?

@BillyRuffian
Copy link
Member Author

Added disclaimer

@BillyRuffian BillyRuffian merged commit 3177d89 into master Apr 9, 2025
1 check passed
@BillyRuffian BillyRuffian deleted the feature/experimenting-with-rag-llm branch April 9, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants