I think AI is pushing me toward the AGPL – by Julio Merino
Julio Merino는 AI 코딩 에이전트의 등장으로 오픈소스 라이선스에 대한 기존 신념에 의문을 제기한다. AI가 기존 프로젝트를 쉽게 변형하고 확장할 수 있게 되면서, BSD 라이선스처럼 느슨한 라이선스는 프로젝트의 무분별한 포크와 유지보수 부담 증가를 초래할 수 있다고 본다. 이에 대응책으로 AGPLv3 같은 강력한 카피레프트 라이선스가 필요할지 고민하며, AI 시대에 오픈소스 기여와 유지 관리의 새로운 도전과제를 제기한다. 또한, 테스트 스위트를 비공개로 유지하는 전략도 논의하지만, 이는 오픈소스 정신과 상충할 수 있음을 지적한다.
Package Darwinism, the Furture of Open Source, Adapt or Get Archived
오픈 소스 생태계가 '패키지 다윈주의' 단계에 접어들고 있으며, 단일 유지보수자가 관리하는 긴 꼬리 패키지는 AI 에이전트의 빠른 공격과 경쟁에 대응하기 어려워지고 있다. 앞으로는 소수의 패키지만이 AI 에이전트를 활용해 신속한 보안 패치와 기능 업데이트를 수행하며 살아남을 것이고, 유지보수자는 코드 작성자가 아닌 AI 에이전트들을 지휘하는 역할로 변화할 것이다. 이는 오픈 소스가 사라지는 것이 아니라 집중화되는 현상으로, 유지보수자들은 이에 적응해야 한다는 메시지를 담고 있다.
https://twitter.com/pelaseyed/status/2052345682984407067
#opensource #aiautomation #security #softwaremaintenance #packageecosystem
Is Your Software Slowing Down Your Business Growth?
Launching software is just the beginning - maintaining it is where real success happens. Software maintenance helps reduce downtime, optimize performance, and cut operational costs.
Discover more at the link:
https://prishusoft.com/blog/software-maintenance-outsourcing-guide
Prishusoft shall help with all the ways and more.
Ready to optimize your digital infrastructure? Connect with Prishusoft today.
#ITServices #ITServices #SoftwareMaintenance #DigitalTransformation #ITOutsourcing
Large language model (LLM)-powered agents have demonstrated strong capabilities in automating software engineering tasks such as static bug fixing, as evidenced by benchmarks like SWE-bench. However, in the real world, the development of mature software is typically predicated on complex requirement changes and long-term feature iterations -- a process that static, one-shot repair paradigms fail to capture. To bridge this gap, we propose \textbf{SWE-CI}, the first repository-level benchmark built upon the Continuous Integration loop, aiming to shift the evaluation paradigm for code generation from static, short-term \textit{functional correctness} toward dynamic, long-term \textit{maintainability}. The benchmark comprises 100 tasks, each corresponding on average to an evolution history spanning 233 days and 71 consecutive commits in a real-world code repository. SWE-CI requires agents to systematically resolve these tasks through dozens of rounds of analysis and coding iterations. SWE-CI provides valuable insights into how well agents can sustain code quality throughout long-term evolution.
I used to think of myself as an "innovator" 20 years ago. Today I'm probably better described as "ancient maintainer" as I'm mostly working on projects I've started 10-15 years ago. I used to believe a good maintainer churns out new and exciting features all the time, but I now I think that a good maintainer:
- keeps the lights on
- doesn't frustrate the users of their projects (less breaking changes and controversial/divisive features)
- tries to build a welcoming and enduring community around their projects
- values simplicity and the power of "saying no"/"less is more"
This article definitely resonated strongly with me https://www.joanwestenberg.com/the-rime-of-the-ancient-maintainer/
Every culture produces heroes that reflect its deepest anxieties. The Greeks, terrified of both mortality and immortality, gave us Achilles. The Victorians, haunted by social mobility, gave us the self-made industrialist. And Silicon Valley, drunk on exponential curves and both terrified and entranced by endless funding rounds, has given us
We called it "support", but okay.
https://mastodon.social/@planetaryecologist/115543979074318056
[email protected] - Software evolution (Evolution 🧬)
Software evolution is the continual development of a piece of software after its initial release to address changing stakeholder and/or market requirements. ... organizations invest large amounts of money in their software and are completely dependent on this software.
Software evolution (Evolution 🧬)
Software evolution is the continual development of a piece of software after its initial release to address changing stakeholder and/or market requirements. Software evolution is important because organizations invest large amounts of money in their software and are completely dependent on this software. Software evolution helps software adapt to changing bus...
Build. Evolve. Maintain. - Partner with Prishusoft for Complete Product Success
Discover how Prishusoft helps businesses design, develop, and maintain scalable products across Transport, Healthcare, Retail, and other industries. With over 15 years of product engineering experience, Prishusoft ensures long-term product success through innovation, reliability, and continuous improvement.
Read more: https://www.linkedin.com/pulse/build-evolve-maintain-partner-prishusoft-complete-product-e69mf/
🧹 Tidying Up After Myself: Automatically Deleting Old GitHub Issues
At some point, I had to admit it: I’ve turned GitHub Issues into a glorified chart gallery. Let me explain. Over on my amedee/ansible-servers repository, I have a workflow called workflow-metrics.yml, which runs after every pipeline. It uses yykamei/github-workflows-metrics to generate beautiful charts that show how long my CI pipeline takes to run. Those charts are then posted into a GitHub Issue—one per run. It’s neat. It's visual. It's entirely unnecessary to keep them […]https://amedee.be/%f0%9f%a7%b9-tidying-up-after-myself-automatically-deleting-old-github-issues/
Taylor Otwell looks back on 14 years of building and maintaining Laravel. From four stars on GitHub to a full-fledged ecosystem, he shares what it takes to design software that lasts—and why simple often wins.
sayzard
Prishusoft
N-gated Hacker News
Bozhidar Batsov (a.k.a. Bug)
Flatbush Gardener 🌈
Planetary Ecologist
Amedee