Salimma

Michel Lind

Personal information
Pronouns:	he/him
Location:	Greater Chicago Area, Illinois, USA
Homepage:	https://michel-slm.name/
GPG key:	5DCE2E7E9C3B1CFFD335C1D78B229D2F7CCC04F2
Contact information
IRC:	@salimma:fedora.im on irc.libera.chat
	#devel, #epel, #rust
LinkedIn:	michellind
Fediverse:	@michelin@hachyderm.io
GitHub:	michel-slm
GitLab:	michel-slm
Fedora-specific information
FAS name:	salimma
Fedora e-mail:	salimma@fedoraproject.org
Fedora homepage:	salimma.fedorapeople.org

README

Inspired by Manager Readmes

Setting expectations: I am employed to work on improving Linux distributions, and try to focus on tooling and policies that make maintaining packages easier across Fedora, EPEL, and CentOS Hyperscale SIG. With that in mind, and juggling family life, I cannot dedicate my full time to package maintenance - especially those I pick up as dependencies.

These are some tips on how to interact with me:

I normally operate on US Central Time, i.e. UTC-6 outside of US DST or UTC-5 timezone during DST
I don't work weekends. I might have some hours to wrap things up but family life and rest and recreation are sacrosanct
If I'm traveling, my Matrix display name will show my current timezone and rough location
If I'm on vacation, this is normally reflected in my Matrix display name, my Discourse status, and the Fedora vacation calendar
Let's be respectful of each other's time
- If you send a PR, make sure it builds _and_ installs (use mock --postinstall or fedpkg mockbuild -- --postinstall) at least on your local machine
- If you have a PR, and it relates to a Bugzilla issue, please mention the bug in your PR (e.g. "Fixes: rhbz#..." or "Resolves: rhbz#...") and that it shows in the changelog when you generate an SRPM
- If I don't respond to your PR (especially if it builds and installs both locally and per the scratch build and installability tests), and I'm not on vacation, feel free to ping me on Matrix after one working day
- If a PR is work in progress, please title it so (e.g. prefix it with [WIP])
- If a non-WIP PR is broken for more than two weeks I reserve the right to close it to unclutter my packager dashboard
Dealing with broken tooling
- Pagure's activity feed breaks for those with too many repositories, so the only notification I effectively get is via email and the packager dashboard after a long lag
  - Bear this in mind if I don't respond quickly. Those of us with group access to many packages are inundated
  - Go to the Bugzilla issue your PR fixes and add a link to your PR. This increases the chance I'll see it
Things not to do
- If you are affected by a broken package, *do not* pile on release monitoring issues for the package to ask for updates. By definition those are low-priority. File a bug for your issue and mark it as depending on the release monitoring issue if you think that version will fix your issue

Fedora activities

SIGs

Changes

Fedora 41
- Remove Python Mock Usage
Fedora 37
- Fallback Hostname
Fedora 36
- Relocate RPM database to /usr
- Cockpit File Sharing
Fedora 35
Fedora 34
- Enable Btrfs transparent zstd compression
- Enable systemd-oomd
Fedora 33
- Switch Fedora desktops to Btrfs

Packaging

I maintain quite a few packages, see the package database for the complete list:

Packages owned and co-maintained

My packaging interests falls under several categories; if there is any package you'd want to see packages that I might be interested in, feel free to send an email!

Programming languages

Functional languages (esp. Lisp dialects and Lua)
compiler frameworks (e.g. LLVM)
scripting languages (esp. Python)
GNOME-related languages (e.g. Vala)

Desktop

GNOME
GNUstep
ROX

Games

Board games
Cross-platform games

Console

bti, a command-line Twitter client
rlwrap, a wrapper for readline

Reviewer

See the full list

Sponsor

I am a packager sponsor; if you are new to Fedora and am looking for sponsorship, do contact me; especially (but not necessarily) if your packaging interests coincide with mine.

I was sponsored by Toshio Kuratomi, and have sponsored the following wonderful folks:

Proven packager

I am a proven packager, and can commit to packages I do not directly maintain; if you need a packaging bug fixed and the primary maintainer is non-responsive, let me know.

Porting

I have an interest in porting useful software from *BSD operating systems to Linux. My first port is cpdup, and I am currently porting the DragonFly Mail Agent. Both are from DragonFly BSD.