I'm concerned about this, though maybe I'm missing some context. A maintainer saying “I don't want AI-assisted patches in this project” seems fair enough. A forge-wide ban feels like a different thing. Code usually doesn't tell you how it was written, so a rule like this may mostly teach people not to disclose AI use rather than not to use it. Honest disclosure gets punished, concealment doesn't. That seems like the opposite of what the policy wants.
@hongminhee@hollo.social
2 likes
- AstroHyde
@AstroHyde@mastodon.social
Director, Allan I Carswell Observatory, Associate Prof @ YorkU Toronto, Astrophys Data Science Telescope person. 2nd VP #RASC TO. Operating in-above the cloud. prof/dr. she/her
https://www.yorku.ca/science/observatory
wanted to leave the planet before it was cool: SX stars, Sgr dwarf, #spectra, ML, Mars, Fats Domino, Hole, Marty Robbins, Enya, the Roop, art, old books, #cats #astronomy #outreach, TOS, TNG, DS9, movie Tank Girl #fedi22 #telescopes #observatory #science #opensource #linux #iraf #python #retro
