#maintainer — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #maintainer, aggregated by home.social.
-
It seems like a matter of time before the controls I put in place are subverted by this tool that gets to pretend to be me. #github #agentic #ai #security #maintainer
-
#Linux für alte Nischenprudukte und Interfaces? Nö, nun nicht mehr. Alle #Kernel Treiber für ältere Hardware, welche keine #Maintainer mehr haben werden entfernt, wenn KI-Bugreports für eben diese eintreffen. Wobei in fast allen Fällen die Treiber keine Updates benötigen. Gleichschaltung durch KI. Leck mich am Arsch... 🤬
https://www.phoronix.com/news/Linux-7.1-PR-Remove-Old-Net
https://www.youtube.com/watch?v=8vDSSxaQ7ZU -
#Linux für alte Nischenprudukte und Interfaces? Nö, nun nicht mehr. Alle #Kernel Treiber für ältere Hardware, welche keine #Maintainer mehr haben werden entfernt, wenn KI-Bugreports für eben diese eintreffen. Wobei in fast allen Fällen die Treiber keine Updates benötigen. Gleichschaltung durch KI. Leck mich am Arsch... 🤬
https://www.phoronix.com/news/Linux-7.1-PR-Remove-Old-Net
https://www.youtube.com/watch?v=8vDSSxaQ7ZU -
#Linux für alte Nischenprudukte und Interfaces? Nö, nun nicht mehr. Alle #Kernel Treiber für ältere Hardware, welche keine #Maintainer mehr haben werden entfernt, wenn KI-Bugreports für eben diese eintreffen. Wobei in fast allen Fällen die Treiber keine Updates benötigen. Gleichschaltung durch KI. Leck mich am Arsch... 🤬
https://www.phoronix.com/news/Linux-7.1-PR-Remove-Old-Net
https://www.youtube.com/watch?v=8vDSSxaQ7ZU -
#Linux für alte Nischenprudukte und Interfaces? Nö, nun nicht mehr. Alle #Kernel Treiber für ältere Hardware, welche keine #Maintainer mehr haben werden entfernt, wenn KI-Bugreports für eben diese eintreffen. Wobei in fast allen Fällen die Treiber keine Updates benötigen. Gleichschaltung durch KI. Leck mich am Arsch... 🤬
https://www.phoronix.com/news/Linux-7.1-PR-Remove-Old-Net
https://www.youtube.com/watch?v=8vDSSxaQ7ZU -
#Linux für alte Nischenprudukte und Interfaces? Nö, nun nicht mehr. Alle #Kernel Treiber für ältere Hardware, welche keine #Maintainer mehr haben werden entfernt, wenn KI-Bugreports für eben diese eintreffen. Wobei in fast allen Fällen die Treiber keine Updates benötigen. Gleichschaltung durch KI. Leck mich am Arsch... 🤬
https://www.phoronix.com/news/Linux-7.1-PR-Remove-Old-Net
https://www.youtube.com/watch?v=8vDSSxaQ7ZU -
Greg Kroah-Hartman zieht klare Grenze für #KI-generierten #Code
KI darf im #Linux_Kernel helfen, aber nicht überall. #Greg_Kroah_Hartman schränkt ihren Einsatz im Bereich drivers/staging jetzt deutlich ein.
Der #Maintainer „clanker“ reagiert auf eine wachsende Zahl automatisch erzeugter Patches. Nach seinen Angaben landen inzwischen immer häufiger Änderungen aus Sprachmodellen im Staging-Bereich. Diese Beiträge will er künftig grundsätzlich ablehnen.
https://fosstopia.de/greg-kroah-hartman-zieht-klare-grenze-fur-ki/
-
Greg Kroah-Hartman zieht klare Grenze für #KI-generierten #Code
KI darf im #Linux_Kernel helfen, aber nicht überall. #Greg_Kroah_Hartman schränkt ihren Einsatz im Bereich drivers/staging jetzt deutlich ein.
Der #Maintainer „clanker“ reagiert auf eine wachsende Zahl automatisch erzeugter Patches. Nach seinen Angaben landen inzwischen immer häufiger Änderungen aus Sprachmodellen im Staging-Bereich. Diese Beiträge will er künftig grundsätzlich ablehnen.
https://fosstopia.de/greg-kroah-hartman-zieht-klare-grenze-fur-ki/
-
Greg Kroah-Hartman zieht klare Grenze für #KI-generierten #Code
KI darf im #Linux_Kernel helfen, aber nicht überall. #Greg_Kroah_Hartman schränkt ihren Einsatz im Bereich drivers/staging jetzt deutlich ein.
Der #Maintainer „clanker“ reagiert auf eine wachsende Zahl automatisch erzeugter Patches. Nach seinen Angaben landen inzwischen immer häufiger Änderungen aus Sprachmodellen im Staging-Bereich. Diese Beiträge will er künftig grundsätzlich ablehnen.
https://fosstopia.de/greg-kroah-hartman-zieht-klare-grenze-fur-ki/
-
Greg Kroah-Hartman zieht klare Grenze für #KI-generierten #Code
KI darf im #Linux_Kernel helfen, aber nicht überall. #Greg_Kroah_Hartman schränkt ihren Einsatz im Bereich drivers/staging jetzt deutlich ein.
Der #Maintainer „clanker“ reagiert auf eine wachsende Zahl automatisch erzeugter Patches. Nach seinen Angaben landen inzwischen immer häufiger Änderungen aus Sprachmodellen im Staging-Bereich. Diese Beiträge will er künftig grundsätzlich ablehnen.
https://fosstopia.de/greg-kroah-hartman-zieht-klare-grenze-fur-ki/
-
Greg Kroah-Hartman zieht klare Grenze für #KI-generierten #Code
KI darf im #Linux_Kernel helfen, aber nicht überall. #Greg_Kroah_Hartman schränkt ihren Einsatz im Bereich drivers/staging jetzt deutlich ein.
Der #Maintainer „clanker“ reagiert auf eine wachsende Zahl automatisch erzeugter Patches. Nach seinen Angaben landen inzwischen immer häufiger Änderungen aus Sprachmodellen im Staging-Bereich. Diese Beiträge will er künftig grundsätzlich ablehnen.
https://fosstopia.de/greg-kroah-hartman-zieht-klare-grenze-fur-ki/
-
[NEWS] The Apache® Software Foundation Announces Apache Magpie, a new Top-Level Project that provides open source maintainers with platform infrastructure for agent-assisted repository maintainership https://buff.ly/SayRxfP
-
[NEWS] The Apache® Software Foundation Announces Apache Magpie, a new Top-Level Project that provides open source maintainers with platform infrastructure for agent-assisted repository maintainership https://buff.ly/SayRxfP
-
[NEWS] The Apache® Software Foundation Announces Apache Magpie, a new Top-Level Project that provides open source maintainers with platform infrastructure for agent-assisted repository maintainership https://buff.ly/SayRxfP
-
[NEWS] The Apache® Software Foundation Announces Apache Magpie, a new Top-Level Project that provides open source maintainers with platform infrastructure for agent-assisted repository maintainership https://buff.ly/SayRxfP
-
[NEWS] The Apache® Software Foundation Announces Apache Magpie, a new Top-Level Project that provides open source maintainers with platform infrastructure for agent-assisted repository maintainership https://buff.ly/SayRxfP
-
As #maintainer of @backintime I do have a question to the community
https://mail.python.org/archives/list/[email protected]/message/7KCB33I3TFE5EP7WFOQKQKBTHODWBDCC/
#foss #opensource #debian #ubuntu #linux #donate #freesoftware
-
As #maintainer of @backintime I do have a question to the community
https://mail.python.org/archives/list/[email protected]/message/7KCB33I3TFE5EP7WFOQKQKBTHODWBDCC/
#foss #opensource #debian #ubuntu #linux #donate #freesoftware
-
As #maintainer of @backintime I do have a question to the community
https://mail.python.org/archives/list/[email protected]/message/7KCB33I3TFE5EP7WFOQKQKBTHODWBDCC/
-
As #maintainer of @backintime I do have a question to the community
https://mail.python.org/archives/list/[email protected]/message/7KCB33I3TFE5EP7WFOQKQKBTHODWBDCC/
#foss #opensource #debian #ubuntu #linux #donate #freesoftware
-
Tip to avoid #maintainer #burnout: don't set unreasonable expectations about response times. If your CONTRIBUTING.md says you will review in 48 hours, people will start bugging you in 40 hours ... over a holiday weekend.
Say things like "3 working days" instead. Or even "best effort, about a week".
-
Tip to avoid #maintainer #burnout: don't set unreasonable expectations about response times. If your CONTRIBUTING.md says you will review in 48 hours, people will start bugging you in 40 hours ... over a holiday weekend.
Say things like "3 working days" instead. Or even "best effort, about a week".
-
Tip to avoid #maintainer #burnout: don't set unreasonable expectations about response times. If your CONTRIBUTING.md says you will review in 48 hours, people will start bugging you in 40 hours ... over a holiday weekend.
Say things like "3 working days" instead. Or even "best effort, about a week".
-
Tip to avoid #maintainer #burnout: don't set unreasonable expectations about response times. If your CONTRIBUTING.md says you will review in 48 hours, people will start bugging you in 40 hours ... over a holiday weekend.
Say things like "3 working days" instead. Or even "best effort, about a week".
-
Tip to avoid #maintainer #burnout: don't set unreasonable expectations about response times. If your CONTRIBUTING.md says you will review in 48 hours, people will start bugging you in 40 hours ... over a holiday weekend.
Say things like "3 working days" instead. Or even "best effort, about a week".
-
I find the recent sneering about #rsync and it's supposed code quality degradation very disheartening. If I go to the repository I see a lone #maintainer trying to keep the code base modernised for a popular tool with an inexorability rising issue list. You don't have to use rsync, you can even fork your artisanal #genai free version if you want. What you shouldn't do is drive-by spam the project because you think the devs should be doing it differently. #opensource
-
I find the recent sneering about #rsync and it's supposed code quality degradation very disheartening. If I go to the repository I see a lone #maintainer trying to keep the code base modernised for a popular tool with an inexorability rising issue list. You don't have to use rsync, you can even fork your artisanal #genai free version if you want. What you shouldn't do is drive-by spam the project because you think the devs should be doing it differently. #opensource
-
I find the recent sneering about #rsync and it's supposed code quality degradation very disheartening. If I go to the repository I see a lone #maintainer trying to keep the code base modernised for a popular tool with an inexorability rising issue list. You don't have to use rsync, you can even fork your artisanal #genai free version if you want. What you shouldn't do is drive-by spam the project because you think the devs should be doing it differently. #opensource
-
I find the recent sneering about #rsync and it's supposed code quality degradation very disheartening. If I go to the repository I see a lone #maintainer trying to keep the code base modernised for a popular tool with an inexorability rising issue list. You don't have to use rsync, you can even fork your artisanal #genai free version if you want. What you shouldn't do is drive-by spam the project because you think the devs should be doing it differently. #opensource
-
I find the recent sneering about #rsync and it's supposed code quality degradation very disheartening. If I go to the repository I see a lone #maintainer trying to keep the code base modernised for a popular tool with an inexorability rising issue list. You don't have to use rsync, you can even fork your artisanal #genai free version if you want. What you shouldn't do is drive-by spam the project because you think the devs should be doing it differently. #opensource
-
sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs
I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility
the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it
-
sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs
I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility
the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it
-
sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs
I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility
the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it
-
sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs
I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility
the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it
-
sooo i tried using the new b4 review TUI for my last U-Boot PR and it was a bit of a disaster. I understand the process being a bit clunky to begin with but the whole process of actually setting up a branch was really involved. It failed to update a bunch of series on pathwork, and the b4 ty emails it generated had completely wrong commit SHAs
I get that the intention is primarily patch review but even for that it feels less like a tool i can utilise to automate the process and more like an imposed workflow that offers little flexibility
the thing that really pissed me off in the end though was realising that b4 review was VIBE CODED, kinda explains everything... This tool had so much potential but i struggle to see now how it will deliver when AI is involved in building it
-
Bit Warden had an issue with a worm that affects many / some? You should at least read / watch about the potential damage, even it is all a bit techy for most. Stay up to date and decide if action is required. #worm #bitwarden #cli #maintainer #youtube youtu.be/-_TWFbw8XjU?...
HUGE password manager got comp... -
May is #maintainermonth
https://maintainermonth.github.com/
A month for open source maintainers to gather, share, and be celebrated.
Are you a maintainer? You can submit your idea!
-
May is #maintainermonth
https://maintainermonth.github.com/
A month for open source maintainers to gather, share, and be celebrated.
Are you a maintainer? You can submit your idea!
-
May is #maintainermonth
https://maintainermonth.github.com/
A month for open source maintainers to gather, share, and be celebrated.
Are you a maintainer? You can submit your idea!
-
May is #maintainermonth
https://maintainermonth.github.com/
A month for open source maintainers to gather, share, and be celebrated.
Are you a maintainer? You can submit your idea!
-
May is #maintainermonth
https://maintainermonth.github.com/
A month for open source maintainers to gather, share, and be celebrated.
Are you a maintainer? You can submit your idea!
-
Nothing against #French people, but literally the only people that reach out to me in a foreign #language (besides English and German as it's obvious I'm located in Germany) are French.
If you open an #issue, you want sth from me, so make sure I understand it.
Do you think it's harsh to ignore these issues or ask for an English translation?
-
Nothing against #French people, but literally the only people that reach out to me in a foreign #language (besides English and German as it's obvious I'm located in Germany) are French.
If you open an #issue, you want sth from me, so make sure I understand it.
Do you think it's harsh to ignore these issues or ask for an English translation?
-
Nothing against #French people, but literally the only people that reach out to me in a foreign #language (besides English and German as it's obvious I'm located in Germany) are French.
If you open an #issue, you want sth from me, so make sure I understand it.
Do you think it's harsh to ignore these issues or ask for an English translation?
-
Nothing against #French people, but literally the only people that reach out to me in a foreign #language (besides English and German as it's obvious I'm located in Germany) are French.
If you open an #issue, you want sth from me, so make sure I understand it.
Do you think it's harsh to ignore these issues or ask for an English translation?
-
Nothing against #French people, but literally the only people that reach out to me in a foreign #language (besides English and German as it's obvious I'm located in Germany) are French.
If you open an #issue, you want sth from me, so make sure I understand it.
Do you think it's harsh to ignore these issues or ask for an English translation?
-
#OpenSourceEconomy allows a #maintainer of #opensource software to market their services to #companies which depend on #software or could benefit from #coaching.
-
I really liked this notice that the @biomejs maintainers put in one of their discussions on GitHub. Hopefully folks read it, sadly I suspect the abusers won't
-
I really liked this notice that the @biomejs maintainers put in one of their discussions on GitHub. Hopefully folks read it, sadly I suspect the abusers won't
-
I really liked this notice that the @biomejs maintainers put in one of their discussions on GitHub. Hopefully folks read it, sadly I suspect the abusers won't
-
I really liked this notice that the @biomejs maintainers put in one of their discussions on GitHub. Hopefully folks read it, sadly I suspect the abusers won't
-
I really liked this notice that the @biomejs maintainers put in one of their discussions on GitHub. Hopefully folks read it, sadly I suspect the abusers won't
-
📬 Autonomer KI-Agent startet Diffamierung gegen Matplotlib-Maintainer
#KünstlicheIntelligenz #OpenSourceKolumne #AutonomeKI #Diffamierung #github #KIAgent #KIMisalignment #Maintainer #Matplotlib #OpenSource #OpenClaw #Plattformverantwortung https://sc.tarnkappe.info/1d0bf5 -
📬 Autonomer KI-Agent startet Diffamierung gegen Matplotlib-Maintainer
#KünstlicheIntelligenz #OpenSourceKolumne #AutonomeKI #Diffamierung #github #KIAgent #KIMisalignment #Maintainer #Matplotlib #OpenSource #OpenClaw #Plattformverantwortung https://sc.tarnkappe.info/1d0bf5 -
📬 Autonomer KI-Agent startet Diffamierung gegen Matplotlib-Maintainer
#KünstlicheIntelligenz #OpenSourceKolumne #AutonomeKI #Diffamierung #github #KIAgent #KIMisalignment #Maintainer #Matplotlib #OpenSource #OpenClaw #Plattformverantwortung https://sc.tarnkappe.info/1d0bf5 -
📬 Autonomer KI-Agent startet Diffamierung gegen Matplotlib-Maintainer
#KünstlicheIntelligenz #OpenSourceKolumne #AutonomeKI #Diffamierung #github #KIAgent #KIMisalignment #Maintainer #Matplotlib #OpenSource #OpenClaw #Plattformverantwortung https://sc.tarnkappe.info/1d0bf5
