@glyph Can you make sure this is documented in an obvious...

@glyph Can you make sure this is documented in an obvious place for contributors? e.g. PR templates on packages you maintain?

Like 9 Nov 2023 at 22:53 | Wall-to-wall | Open on oldos.me

6 comments

Glyph

@jay I am tooting it out here because it is a truly obnoxious amount of unpaid work that just got dumped on me, to do this across a hundred or so repos (not to mention hashing it out with other contributors on bigger projects) but yeah, I am going to need to do this.

9 Nov 2023 at 23:05 | Open on mastodon.social

Glyph

@jay also it's not really particular to copilot, other LLMs may not have that indemnification policy you mentioned and are therefore arguably worse, but also there isn't an ad for those LLMs on every single UI element in github now

9 Nov 2023 at 23:07 | Open on mastodon.social

Glyph

@jay so I've got to write a *general* policy

9 Nov 2023 at 23:07 | Open on mastodon.social

JayF

@glyph honestly, I don't contribute to many of your open source projects so I don't think it'll actually impact me, but I do leave copilot enabled on my IDE for most work that I do.

I would hate for someone to characterize an accidental PR pushed by me as trying to sneak AI generated code through just because I forgot that this was a repo where submitting code with this add-on enabled in my IDE was forbidden.

9 Nov 2023 at 23:19 | Open on oldos.me

Mark Eichin

@jay
Have you signed any CLAs? They often have traceability clauses that implicitly have the same result.
@glyph

10 Nov 2023 at 1:06 | Open on mastodon.mit.edu

Eleanor Saitta

@jay
I mean, that's your choice though, yes? Maintainers have an obligation to the viability of the project.
@glyph

10 Nov 2023 at 17:03 | Open on infosec.exchange

Go Up