Canonical has committed to donating $120,000 (around £90,000) to smaller open-source projects and developers over the next 12 months https://www.omgubuntu.co.uk/2025/05/canonical-commits-funds-open-source-devs
New post on GitHub Actions: avoid double runs of your workflows by using a better 'on' clause.
https://adamj.eu/tech/2025/05/14/github-actions-avoid-simple-on/
There used to be no #github and everything was fine. Find something else worthy of your attention, we can't wait.
(1/2)
Via #ComputerHoy, #CarolinaGonzálezValenzuela
"Now, yes, 
programmers' days are numbered: ChatGPT connects with GitHub and it could be the end
The announcement of the integration between #ChatGPT and #GitHub has set off all the alarm bells in the #programming world. Is this the beginning of the end for developers?... "
"...With all this on the table, one thing is clear, at least for 2025:
programmers...
CC
@rod2ik
Ahora sí, los #programadores tienen los días contados: #ChatGPT se conecta con #GitHub y podría ser el fin
"Why did you folks host the Shufflecake repository on Codeberg instead of GitHub like everyone else does?"
Exhibit nr. 712: https://github.com/orgs/community/discussions/159123
In a move that surprises absolutely noone, GitHub now requires users to login in order to browse public repositories (including open source projects). After a few (~10) requests, you get blocked (I can confirm). In order to fight AI scrapers, I guess.
So, GitHub decided to blanket-limit access to open source projects as a defense against the very scourge that they(r parent company) unleashed on the world.
I won't be hypocrite: it's a bit embarrassing, but undeniably satisfying to say "told you so". I moved away from GitHub long ago and I moved all my stuff to Codeberg instead. And so happy I did!
Next step: radicle.xyz maybe?
this is why we don't github folks
what an absolute waste of time - just reading source files in someone's tree.
The open-source community is filled with beauty. It can truly be a shining light in a world otherwise full of darkness.
https://github.com/ibrahim-sisar/EduLite
I met one of the most inspiring and ambitious new members of the open-source community, and have decided to join him on his quest to make education free and fair (even if you are fleeing a war zone).
Anybody who is as passionate about open-source and education as I am, give this project a look and consider making a discussion post. I am very excited to start working on it.
Anybody who has never contributed to open-source before, message me on discord (smattymatty) and I can help you get started, teach you the fundamentals of github issues/pull requests/forks etc.
I want this community to thrive!!!
@rOpenSci an update: the bug has been fixed in the development version of {pak} and {pkgbuild}. you can down use `pak-version: "devel"` in your workflow to use it in your workflows
see https://github.com/hubverse-org/hubValidations/issues/235#issuecomment-2863055858
Building a more accessible GitHub CLI - The GitHub Blog https://github.blog/engineering/user-experience/building-a-more-accessible-github-cli/ #CLI #Git #GitHub #Accessibility #A11y
If you use a packages from the #RUniverse on #GitHub using r-lib/setup-r-dependencies and are seeing an error that says "malformed DESCRIPTION" it might just be this bug: https://github.com/r-lib/pak/issues/771
In short: A recent deploy of the R Universe added a `File:` field in /src/contrib/PACKAGES that is causing the tarball to be named as the sha256 hash and {pkgbuild} (used by {pak}, which is used by r-lib/setup-r-dependencies) does not like that one bit.
One solution to work around this is to add the GitHub sources to the `packages:` field:
```
with:
packages: |
github::[user]/[repo]@[version]
```
git-next: 
New release v2025.5.0 - Refactoring and isolating features
git-next: trunk-based development manager
Written in Rust
Repo: https://codeberg.org/kemitix/git-next
What's New
- Reimplement git operations to use git2/libgit2
- Renamed features:
forgejo -> forge-forgejo
github -> forge-github
notify-desktop
notify-email
This a significant update to migrate from gix to git2 for git operations. This allows us to drop the gix crate and the need to shelling-out to git for operations that gix doesn't support.
Breaking Change
If you are build from source (e.g. cargo install) and use either email or desktop notifications in your configuration file, you will need to add the appropriate feature, notify-desktop and/or notify-email. If you don't the config file will not be accepted.
The docker images are built with all features enabled.
Install
cargo install git-next@2025.5.0 cargo install git-next@2025.5.0 --features notify-desktop,notify-email
docker pull codeberg.org/kemitix/git-next:v2025.5.0
Run UI in docker
docker run --rm -p 8092:8092 \
-u $(id -u):$(id -g) \
-it \
-v $PWD:/app \
codeberg.org/kemitix/git-next:v2025.5.0 \
server start --xui
I've recently been thinking a lot about the best way to help people move from #GitHub -> @radicle
Radicle has a completely different architecture (#peerToPeer vs. centralised) and identity system (based on #DID), so ... there's quite the learning curve.
There's *quite* the gap to bridge.
While I don't like #Github as a git forge monopolist (and I'm glad there finally are reasonable alternatives,) I appreciate their #accessibility and compatibility work, like this #blogpost/feature on #CLI accessibility: https://github.blog/engineering/user-experience/building-a-more-accessible-github-cli/
