Go to file
Jeremy Stanley 9f6e4921c4 Comply with Policy for AI Generated Content
While probably not meeting most people's definition of artificial
intelligence these scripts do create patches. The OpenInfra Policy
for AI Generated Content recommends to:

> Add a "Generated-By:" label to the commit message, and explain in
> comments or the commit message any prompts or background context
> the reviewers might need to fully understand the change and how
> much of the change was generated by the tool.

Even though it also has a carve-out for these sorts of scripts:

> The exception to the rule is that we do allow submissions from
> well documented automated processes, such as release tooling or
> for internationalization updates.

https://openinfra.org/legal/ai-policy

Nevertheless, documenting within the commit message the location of
the script which was used to generate that contribution is helpful
for a number of obvious reasons. Let's do it anyway, even though
it's not technically required.

Change-Id: I36c1a0a796781cdbc87a7e5f1058ae6afe14db4c
2025-05-23 16:31:48 +00:00
2025-05-19 20:32:14 +01:00
2016-04-24 17:21:18 -05:00
2021-06-02 06:23:55 +00:00
2020-08-03 09:42:34 -05:00
2019-04-19 19:43:33 +00:00
2018-05-21 14:58:48 -07:00
2024-06-20 12:50:19 +10:00
2025-04-03 07:56:35 +00:00
2024-01-24 15:49:09 +01:00
2019-10-17 15:50:57 +08:00
2025-05-06 15:37:27 +02:00
2018-03-22 13:50:56 -05:00

Global Requirements and Constraints for OpenStack Projects

image

Resources and Documentation

Please refer to the dependency management documentation linked below for up to date documentation on how to use and interact with the requirements project.

Description
Global requirements for OpenStack
Readme 123 MiB
Languages
Python 89.8%
Shell 10.2%