Skip to content

Update generative-tooling.md various edits to improve readabiity#683

Open
cottage14 wants to merge 1 commit intomainfrom
cottage14-patch-1
Open

Update generative-tooling.md various edits to improve readabiity#683
cottage14 wants to merge 1 commit intomainfrom
cottage14-patch-1

Conversation

@cottage14
Copy link
Copy Markdown
Contributor

@cottage14 cottage14 commented Mar 31, 2026

line 11 - removed unneeded commas
line 13 - removed repetition
line 21 - fixed tense of verb to match that of the previous verb in the sentence.
line 43 - passive voice makes it unclear who or what is to apply caution, so adjusted the text to active voice
line 49 - changed "vendor's" to "vendors'" to match the plural assumption in the next sentence
line 55 - "The" is part of the Foundation's name, so should be capitalized; 'second-guess' needs a hyphen, so added it;
added a comma to improve readability

line 11 - removed unneeded commas
line 13 - removed repetition
line 21: fixed tense of verb to match that of the previous verb in the sentence.
line 43: passive voice makes it unclear who or what is to apply caution, so adjusted the text to active voice
line 49 changed "vendor's" to "vendors'" to match the plural assumption in the next sentence
line 55: "The" is part of the Foundation's name, so should be capitalized
'second-guess' needs a hyphen, so added it
added a comma to improve readability
@cottage14 cottage14 requested a review from sebbASF March 31, 2026 11:25
The Apache-2.0 license and the Apache Individual Contribution License Agreement both remind contributors that they are responsible for disclosing any copyrighted materials in submitted contributions that are not their original creation. This is as true when using generative AI tooling as it is when using materials from public websites or code from other open-source projects.

When disclosing these materials, contributors should also identify the licensing for these materials. The ASF maintains a [3rd Party Licensing Policy](/legal/resolved.html) that provides guidance on which licenses are acceptable, along with instructions on the treatment of [3rd Party Works](/legal/src-headers.html#3party).
When disclosing these materials, contributors should also identify their licensing. The ASF maintains a [3rd Party Licensing Policy](/legal/resolved.html) that provides guidance on which licenses are acceptable, along with instructions on the treatment of [3rd Party Works](/legal/src-headers.html#3party).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The word 'their' is ambiguous - does it refer to 'contributors' or 'materials'?

I think this particular change is not an improvement

> “For example, a human may select or arrange AI-generated material in a sufficiently creative way that “the resulting work as a whole constitutes an original work of authorship.” Or an artist may modify material originally generated by AI technology to such a degree that the modifications meet the standard for copyright protection. In these cases, copyright will only protect the human-authored aspects of the work, which are ‘independent of’ and do ‘not affect’ the copyright status of the AI-generated material itself.”

These portions authored by a human may simply come from the prompt the human provided or subsequent changes they make. However, a prominent concern with generative AI is the risk of reproducing copyrightable portions of materials that they were trained on, some of which may be copyrightable subject matter. Thus, a recommended practice when using generative AI tooling is to use tools with features that identify any included content that is similar to parts of the tool’s training data, as well as the license of that content.
These portions authored by a human may simply come from the prompt the human provided or subsequent changes they made. However, a prominent concern with generative AI is the risk of reproducing copyrightable portions of materials that they were trained on, some of which may be copyrightable subject matter. Thus, a recommended practice when using generative AI tooling is to use tools with features that identify any included content that is similar to parts of the tool’s training data, as well as the license of that content.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Seems to me that 'make' is correct here, as it appears to be referring to future changes.


## The tool we want to use may rely on other tools. What terms of use do we need to consider when following this guidance? {#tools-rely-on-other-tools}
Don't second guess vendor's terms of use (TOU). Your usage of their tools is bound by the totality of the given TOU and you are not expected to go outside of the TOU text for further clarifications.
Don't second-guess vendors' terms of use (TOU). Your usage of their tools is bound by the totality of the given TOU and you are not expected to go outside of the TOU text for further clarifications.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The original was correct (vendor is singular), but it might be better as

"... guess a vendor's terms..."

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.

2 participants