home.social

#softwaremaintenance — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #softwaremaintenance, aggregated by home.social.

  1. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  2. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  3. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  4. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  5. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  6. Ah, yet another riveting tome on the thrilling world of software maintenance via continuous integration 🤓. Because clearly, we need AI agents to fix our code while we sip artisanal lattes and attend endless meetings on Zoom ☕💻. Remember, the real challenge is not the code, but staying awake through this "groundbreaking" reading. 💤📚
    arxiv.org/abs/2603.03823 #softwaremaintenance #continuousintegration #AIagents #techhumor #productivity #HackerNews #ngated

  7. 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 joanwestenberg.com/the-rime-of

    #FOSS #OSS #SoftwareMaintenance

  8. We called it "support", but okay.
    mastodon.social/@planetaryecol
    [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.

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  9. We called it "support", but okay.
    mastodon.social/@planetaryecol
    [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.

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  10. We called it "support", but okay.
    mastodon.social/@planetaryecol
    [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.

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  11. We called it "support", but okay.
    mastodon.social/@planetaryecol
    [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.

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  12. We called it "support", but okay.
    mastodon.social/@planetaryecol
    [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.

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  13. 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...

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  14. 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...

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  15. 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...

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  16. 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...

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  17. 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...

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  18. 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: linkedin.com/pulse/build-evolv

    #productdevelopment #SoftwareCompany #SoftwareMaintenance

  19. 🧹 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 […]

    amedee.be/%f0%9f%a7%b9-tidying

  20. 🧹 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 […]

    amedee.be/%f0%9f%a7%b9-tidying

  21. 🧹 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 […]

    amedee.be/%f0%9f%a7%b9-tidying

  22. 🧹 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 […]

    amedee.be/%f0%9f%a7%b9-tidying

  23. 🧹 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 […]

    amedee.be/%f0%9f%a7%b9-tidying

  24. 🎸🤖 Taylor Otwell gives us a masterclass in stating the obvious: maintaining software is important! After 14 years of #Laravel, he's finally cracked the code on why not to mix spaghetti with your codebase. 🍝💻
    maintainable.fm/episodes/taylo #TaylorOtwell #SoftwareMaintenance #CodeQuality #SpaghettiCode #HackerNews #ngated

  25. 🔒🚨 Breaking news! In a shocking twist, maintaining software turns out to be important! Who knew? 🐛 #FreeBSD users, dust off your resumes, because it looks like libxslt's job opening for a maintainer just got urgent. 😅🔥
    vuxml.freebsd.org/freebsd/b0a3 #BreakingNews #SoftwareMaintenance #libxslt #JobOpening #HackerNews #ngated

  26. 🇪🇺 #GitHub is calling for a new #EU #techfund (€350M) to support #critical #opensource #softwaremaintenance, highlighting its economic importance and the need for #sustainablefunding.

    😏 While acknowledging the need for #publicfunding, there is concern about big #techcompanies offloading their #responsibilities and the potential for the fund to become a subsidy for them.

    👉 omgubuntu.co.uk/2025/07/github #Fedizen #Fediverse #ActivityPub #News

  27. Thought of the day: having lots of open issues in your project isn't a problem. "Stale issue" bots are doing way more harm than unanswered issues.

    #SoftwareDevelopment #SoftwareQuality #SoftwareMaintenance #IssueTracking #AnnoyingBots

  28. 1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software dependencies versions up to date (you are keeping your dependencies up to date, right?).

    Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

    docs.renovatebot.com/

    #devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

  29. 1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software versions up to date (you are keeping your dependencies up to date, right?).

    Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

    docs.renovatebot.com/

    #devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

  30. Good on the German authorities who set up the Sovereign Tech Fund. To help fund the maintenance of core software that most people have never heard, but depend on every day. I want to see every government in the world setting up a similar fund, and having them coordinate their efforts.

    sovereigntechfund.de/

    #FreeCode #OpenSource #SoftwareMaintenance #Germany #STF

  31. Allow Neomind to assist you on your quest.⁠

    ⁠-Regular Updates and Patching⁠
    -Performance Monitoring and Optimization⁠
    -Security Audits and Enhancements⁠
    -Database Tuning and Scalability Improvements⁠
    We ensure your application remains efficient and secure⁠


    Learn at: neomindlabs.com/services


    #neomindlabs #RubyonRails #developer #philadelphia #fullstackdeveloper #rubyrailsapp #appdeveloper #reuse #maintain #conserve #sustainability #services #SoftwareMaintenance
    #TechSupport #ITServices

  32. Allow Neomind to assist you on your quest.⁠

    -Tailored training programs to meet your specific needs.⁠
    -Comprehensive codebase walkthroughs and documentation.⁠
    -Consultancy on best practices and performance optimization to ensure a capable in-house Rails team.⁠

    Learn more at: neomindlabs.com/services

    #neomindlabs #RubyonRails #developer #philadelphia #fullstackdeveloper #rubyrailsapp #appdeveloper #reuse #maintain #conserve #sustainability #services #SoftwareMaintenance
    #TechSupport

  33. Our CTO, Rachel Laycock, highlights warning signs of technical debt and offers advice on fixing it and building adaptable systems, allowing your business to thrive in a rapidly evolving digital landscape.

    Explore the article: ter.li/ce8um6

    #TechDebt #SoftwareMaintenance #Tech

  34. 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...

    en.wikipedia.org/wiki/Software

    #SoftwareEvolution #Evolution #SoftwareMaintenance

  35. Respect the Code

    Do you have a different perspective? Share with your network and follow for more content like this!

    #CodeRespect #Understanding #SoftwareMaintenance

  36. Respect the Code

    Do you have a different perspective? Share with your network and follow for more content like this!

    #CodeRespect #Understanding #SoftwareMaintenance

  37. Respect the Code

    Do you have a different perspective? Share with your network and follow for more content like this!

  38. Respect the Code

    Do you have a different perspective? Share with your network and follow for more content like this!

    #CodeRespect #Understanding #SoftwareMaintenance

  39. Respect the Code

    Do you have a different perspective? Share with your network and follow for more content like this!

    #CodeRespect #Understanding #SoftwareMaintenance