docs: Various updates related to the AI policy#5116
Open
lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
Open
docs: Various updates related to the AI policy#5116lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
Conversation
lgritz
force-pushed
the
lg-aipolicy
branch
3 times, most recently
from
8588b09 to
996cc4b
Compare
Collaborator
Author
|
Amended with one more thing that was discussed at yesterday's OSL TSC meeting this week (OIIO and OSL are basically sharing this policy document, until such time as the projects have divergent needs): I added a brief section explaining that we don't have any specific guidance for how AI tools should or shouldn't be used for "artistically creative" work, since this project repo doesn't really house such things. This is mostly for the benefit of other projects that may use our policy document as inspiration, to warn them that they may have issues that need policy guidance but that we do not address. |
I was reminded by Eric Enderton that we should mention and cross reference the recently-added AI policy docs in other places, since it can easily be overlooked now, buried in the docs directory. * Mention it in the pull request template's checklist. * In the CONTRIBUTING guide. * Briefly mention in the main README in the list of important documentation for developers. * A few very minor touch-ups and wordsmithing in other areas, no substantive changes. Also, responding to comments at the TSC meeting this week, I added a brief section explaining that we don't have any specific guidance for how AI tools should or shouldn't be used for "artistically creative" work, since this project repo doesn't really house such things. This is mostly for the benefit of other projects that may use our policy document as inspiration, to warn them that they may have issues that need policy guidance but that we do not address. Signed-off-by: Larry Gritz <lg@larrygritz.com>
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
1 participant
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.
I was reminded by Eric Enderton that we should mention and cross reference the recently-added AI policy docs in other places, since it can easily be overlooked now, buried in the docs directory.
Also, responding to comments at the OSL TSC meeting this week, I added
a brief section explaining that we don't have any specific guidance for
how AI tools should or shouldn't be used for "artistically creative"
work, since this project repo doesn't really house such things. This
is mostly for the benefit of other projects that may use our policy
document as inspiration, to warn them that they may have issues that
need policy guidance but that we do not address.