decathorpe / @decathorpe:fedora.im
@decathorpe:fedora.im
Too many to list them all: #devel, #rust, #epel, #multimedia, #pride, #python, #quality, #security, ... (on the fedoraproject.org homeserver)
I have contributed to many areas of the project since I joined it over a decade ago, so I think I can bring a broad perspective to FESCo. I want to help insure the project's continued success happens in a sustainable way.
I am the most active package maintainer in Fedora (by count of updates / builds), primarily because I am the main point of contact for most Rust packages. My work includes package updates, package review, triaging build failures and broken dependencies, and pruning packages for obsolete, outdated, or unused Rust crates from Fedora. I regularly contribute to upstream projects through bug reports and pull requests to fix issues that are discovered downstream in Fedora. Additionally, I triage, report, and attempt to fix upgrade path issues caused by missing package updates every release cycle.
Many disagreements I’ve handled were only concerned with details, while the goals of everyone involved were still aligned. So I try to find common ground and / or explore alternative or creative solutions that can work for everyone involved.
I am - in general - wary of becoming dependent on products from companies that are nowhere near profitable and only kept afloat by a combination of inconceivably large amounts of venture capital and "creative" investment arrangements. Additionally, to me these "AI" systems aren't "just tools" and can't be treated solely as such, especially due to externalities like unethical data scraping practices, copyright / license laundering, excessive power and water consumption, noise and greenhouse gas pollution, hardware shortages and price increases, etc. I have yet to see a competitive "AI" product that does not have these problems, and I am unsure whether creating one is even possible.
No pineapple, and definitely not on Pizza.
Metadata Update from @amoloney: - Issue set to the milestone: F44 - Issue tagged with: FESCo
Metadata Update from @amoloney: - Issue private status set to: False (was: True)
Metadata Update from @amoloney: - Issue status updated to: Closed (was: Open)