> The line is open to interpretation precisely where it needs to be enforceable.
It is way too arbitrary and open to interpretation and biases.
> the main property I need from infrastructure [is for] it to be predictable, dependable, and reasonably neutral towards the legal Open Source software hosted on it.
I do not like to build on a foundation that could be ripped away from under my feet at any moment for arbitrary reasons.
Way to not at all engage with any of that and just go on your merry way...
Sure, if you fail to acknowledge that the other side has valid points, it is easy to act like you're completely right and they are morons, and we all need to Kumbaya together, and forget about their views.
No. They don't. This isn't a "you just have to deal". You can say no. It's OK to decide that it's not worth the smaller amount of positives to deal with the massive amount of negatives. If you disagree, start your own community.
The only people dividing and ruining open source are those paid for it by AI companies. Sometimes indirectly, like NumPy through its various sponsors. Then suddenly a bureaucrat appears on a mailing list or elsewhere and announces that AI contributions need to be allowed.
https://news.ycombinator.com/item?id=49015635 Protecting our FLOSS commons from LLMs (blog.codeberg.org) 1 day ago, 144 comments
https://news.ycombinator.com/item?id=49003386 Codeberg bans vibe coded projects (codeberg.org/codeberg) 2 days ago, 279 comments
And maybe a statement that: Pre-existing clearly "vibe coded" projects providing little value to the community may be subject to review. Our resources are limited. Don't abuse them.
Instead it got framed in moralistic terms in many places, the actual voting process actively resisted all calls for clarification ("if you're a vibe coder you'll know, so stop trying to ask for clarification", the tone in online forums became nasty, and the result is both ambiguous and culturally poisoned and I decided to move my project ("good riddance!" call out the victors, "we got one of them!")
I do think the one substantial argument that was made through the threads, was around IP ownership laws. However I remain unconvinced.
Frankly if there's anywhere where I would most like to see AI generated work -- which is frankly based on weights generated from the broad and indiscriminate harvesting of other people's works -- is in copylefted software that takes the distillations of the efforts of the community and makes it available as free software with free software protections.
I understand not everyone shares that opinion, and they're welcome to different interpretations.
Like the author of the article I'm saddened to see this split. I am honestly curious to see where we are in 2-3 years on this topic.
Wrong category. It doesn't want to. It's not a company. Might as well act on their beliefs.
Devs are so spoiled with free CI, running nonsensical workflows all the time for free. Imagine that multiplied by magnitudes thanks to AI. Just a waste of resources.
The fact that the rule is open for interpretation means that they can effectively shut down malicious actors (i.e those who intentionally misrepresent the degree of AI assistance in writing their code) before they become a problem. It becomes an exercise in judgement instead of a potentially exploitable/loophole-able set of hard and fast rules.
There's no issue with this. This isn't the supreme court. Your income is not on the line. It's a code hosting repository. Go to GitHub if it bothers you.
Only time will tell if this set of values holds up. Personally, I think they will, and that the rules will end up being less strict than people are making them out to be, and that relatively few projects will be removed from the platform.
Why is that? Is it because you believe there would be a new policy that would exclude your workflow? What would such a policy be? Do you really, reasonably believe it would be implemented "tomorrow"? Do you think adapting to such a policy would be unreasonable?
Or is it because you don't trust the judgement of the people enforcing these new rules?
If not one of the two, what is the reason?
The point I'm trying to make here is that this just sounds like a slippery slope argument. If you don't have a concrete reason to believe you won't be welcome "tomorrow" then my mind has not been changed.
Github allows private repos, organization access control etc. I don't see how Codeberg is competition.
I'm faced with the question on whether all my investment can go up in flames on the whims of a shadow group.
What "shadow group" would that be? The paying members of Codeberg e.V. who voted to pass this motion?Because literally no one will use Codeberg for anything that matters. It was already niche, now Codeberg will just be a couple of unemployed nerds with their useless toy projects.
It's already dead, Jim.
There were decades of software written before modern LLMs, and a lot of people choose to hand write their software as a form of maintaining their skill. Just like people practice martial arts even though we have guns.
If you reflect on your words, you might see another side to this.
Too many people are afraid to offend and waste everyone's time going along with things they don't really agree with and end up pretending to be somebody they're not to get along with people they don't really like.
No! Get your most polarizing takes out quickly. Either you and the other person stop wasting time because there's no fit, or you will deepen the relationship and both know it's a good fit. Either way, it's better for everyone involved.
There's enough people out in this big world that you don't need to always make everyone happy. It's much better to quickly comb through to find the gems.
infecto•50m ago