They’re usually email threads for Linux and on whatever system the maintainers use for other things. Like GitLab, GitHub, Bugzilla, Google Issue Tracker, and Launchpad for Ubuntu are a few.
I don’t know of a single unified store of all of them, you’ll just have to monitor the projects you’re interested in and check for available RSS feeds.
I steal his homework and check the citations and bookmark the links he includes since they’re usually directly to issue tracker feeds and discussion threads. The only one I monitor regularly for myself is the Python Discourse site since I can get a good feeling for new PEPs and timelines for implementation of new features I want to use.
Also, honorable mention here is fossil which was created for SQLite as their Git alternative. Neat little SCM solution that specifically solves issues the SQLite devs were having with Git (which you probably won’t run into). Basically everyone has something different and you’ll need to research it. This site used to use Gittea, and now it uses Codeberg with a GitHub mirror. Most dev conversations happen in a Matrix chat too, so even with one project you might find multiple ingress points for issues/discussions/PRs
Honestly, most of that is probably off like subreddits and hacker news. Discord too, especially for a bigger channel like this where they can just have people feed them info to cover. Still best to get directly to the primary source if you can.
They’re usually email threads for Linux and on whatever system the maintainers use for other things. Like GitLab, GitHub, Bugzilla, Google Issue Tracker, and Launchpad for Ubuntu are a few.
I don’t know of a single unified store of all of them, you’ll just have to monitor the projects you’re interested in and check for available RSS feeds.
I steal his homework and check the citations and bookmark the links he includes since they’re usually directly to issue tracker feeds and discussion threads. The only one I monitor regularly for myself is the Python Discourse site since I can get a good feeling for new PEPs and timelines for implementation of new features I want to use.
Also, honorable mention here is fossil which was created for SQLite as their Git alternative. Neat little SCM solution that specifically solves issues the SQLite devs were having with Git (which you probably won’t run into). Basically everyone has something different and you’ll need to research it. This site used to use Gittea, and now it uses Codeberg with a GitHub mirror. Most dev conversations happen in a Matrix chat too, so even with one project you might find multiple ingress points for issues/discussions/PRs
Sorry meant like on a forum or something where he curated all that. Or again just a blog, like phoronoxic or distrowatch.
Sources like what shared often have rss or at least email subscriptions access. It’s important to be literate in the primary sources anyway.
Honestly, most of that is probably off like subreddits and hacker news. Discord too, especially for a bigger channel like this where they can just have people feed them info to cover. Still best to get directly to the primary source if you can.