Live data from Hacker News

We need a clearer framework for AI-assisted contributions to open source

samsaffron.com

61–70 of 161 posts

Re: We need a clearer framework for AI-assisted contributions to open source

#61
post #45

Maybe we need open source credit scores. PRs from talented engineers with proven track records of high quality contributions would be presumed good enough for review. Unknown, newer contributors could have a size limit on their PRs, with massive PRs rejected automatically.

We don't need more KYC, no.

Reputation building is not kyc. It is actually the thing that enables anonymization to work in a more sophisticated way.

Re: We need a clearer framework for AI-assisted contributions to open source

#62

Anyone else feel like we're cresting the LLM coding hype curve? Like a recognition that there's value there, but we're passing the frothing-at-the-mouth stage of replacing all software engineers?

I've been skeptical about LLMs being able to replace humans in their current state (which has gotten marginally better in the last 18 months), but let us not forget that GPT-3.5 (the first truly useful LLM) was only 3 years ago. We aren't even 10 years out from the initial papers about GPTs.

Re: We need a clearer framework for AI-assisted contributions to open source

#63

> Some go so far as to say “AI not welcome here” find another project. This feels extremely counterproductive and fundamentally unenforceable to me. But it's trivially enforceable. Accept PRs from unverified contributors, look at them for inspiration if you like, but don't ever merge one . It's probably not a satisfying answer, but if you want or need to ensure your project hasn't been infected by AI generated code y…

This is sad. The barrier of entry will be raised extremely high, maybe even requiring some real world personal connections to the maintainer.

Re: We need a clearer framework for AI-assisted contributions to open source

#64

Anyone else feel like we're cresting the LLM coding hype curve? Like a recognition that there's value there, but we're passing the frothing-at-the-mouth stage of replacing all software engineers?

I was extremely skeptical at the beginning, and therefore critical of what was possible as my default stance. Despite all that, the latest iterations of cli agents which attach to LSPs and scan codebase context have been surprising me in a positive direction. I've given them tasks that require understanding the project structure and they've been able to do so. Therefore, for me my trajectory has been from skeptic to big proponent of the use, of course with all the caveats that at the end of the day, it is my code which will be pushed to prod. So I never went through the trough of disillusionment, but am arriving at productivity and find it great.

Re: We need a clearer framework for AI-assisted contributions to open source

#65
post #13

Nice jewish word mostly meant to mock. Why would I care what a plugin that I don't even see in use has to say to my face (since I had to read this with all the interpretation potential and receptiveness available). The same kind of inserted judgment that lingers similar to "Yes, I will judge you if you use AI".

There’s nothing wrong with judgment. Judging someone’s character based on whether they use generative “AI” is a valid practice. You may not like being judged, but that’s another matter entirely.

>There’s nothing wrong with judgment. Judging someone’s character based on whether they use generative “AI” is a valid practice. You may not like being judged, but that’s another matter entirely.

You and I know that using AI is a metric to consider when judging ability and quality.

The difference is that it's not judgment but a broadcast, announcement.

In this case a snotty one from Discourse.

I mention that it lingers because I think that is a real psychological effect that happens.

Small announcements like this carry over into the future and flood any evaluation of yourself which can be described as torture and sabotage since it has an effect on decisions you make sometimes destroying things.

Re: We need a clearer framework for AI-assisted contributions to open source

#66
I guess the main question I'm left with after reading this is "what good is a prototype, then?" In a few of the companies I've worked at there was a quarterly or biannual ritual called "hack week" or "innovation week" or "hackathon" where engineers form small teams and try to bang out a pet project super fast. Sometimes these projects get management's attention, and get "promoted" to a product or feature. Having worked on a few of these "promoted" projects, to the last they were unmitigated disasters. See, "innovation" doesn't come from a single junior engineer's 2AM beer and pizza fueled fever dream. And when you make the mistake of believing otherwise, what seemed like some bright spark's clever little dream turns into a nightmare right quick. The best thing you can do with a prototype is delete it.

Re: We need a clearer framework for AI-assisted contributions to open source

#67

Anyone else feel like we're cresting the LLM coding hype curve? Like a recognition that there's value there, but we're passing the frothing-at-the-mouth stage of replacing all software engineers?

Maybe, maybe not, it’s hard to tell from articles like this from OSS projects what is generally going on, especially with corporate work. There is no such rhetoric at $job, but also, the massive AI investment seemingly has yet to shift the needle. If it doesn’t they’ll likely fire a bunch of people again and continue.

Re: We need a clearer framework for AI-assisted contributions to open source

#68

Essay is way more interesting than the title, which doesn't actually capture it.

The title seems perfectly engineered to get upvotes from people who don't read the article, which puts the article in front of more people who would actually read it (which is good because the article is, as you say, very interesting and worth sharing).

I don't like it but I can hardly blame them.

Re: We need a clearer framework for AI-assisted contributions to open source

#69
This is a problem everywhere now, and not just in code. It now takes zero effort to produce something, whether code or a work plan or “deep research” and then lob it over the fence, expecting people to review and act upon it.

It’s an extension of the asymmetric bullshit principle IMO, and I think now all workplaces / projects need norms about this.

Re: We need a clearer framework for AI-assisted contributions to open source

#70
post #45

Maybe we need open source credit scores. PRs from talented engineers with proven track records of high quality contributions would be presumed good enough for review. Unknown, newer contributors could have a size limit on their PRs, with massive PRs rejected automatically.

The Forgejo project has been gently trying to redirect new contributors into fixing bugs before trying to jump into the project to implement big features (https://codeberg.org/forgejo/discussions/issues/337). This allows a new contributor to get into the community, get used to working with the codebase, do something of clear value... but for the project a lot of it is about establishing reputation.

Will the contributor respond to code-review feedback? Will they follow-up on work? Will they work within the code-of-conduct and learn the contributor guidelines? All great things to figure out on small bugs, rather than after the contributor has done significant feature work.

Post reply on HN