Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
In the meantime, check out the #python channel on our AWS Lambda Powertools Discord: Invite link

Hey @meckhardt, thank you for the proactive addition. Could you share some background on how you bumped into this?

All of our PRs need an issue (a maintenance issue template in this case) in order to be merged. We'll check with our OSPO on the appropriate outcome for the LICENSE file.

Hopping on the OSPO side. The title is an optional field ( https://spdx.org/licenses/MIT-0.json ), but it is embarrassing that our predating OSI-approval template didn't include the title.

I'm +1 to merge this PR. It's not necessary, as that field is optional, but I'm going to suggest we update our template to start defaulting to include the title.

Thanks @heitorlessa @hyandell that you take this change seriously.

I had an issue with Sonatype Nexus IQ about MIT-0 being recognized as a proprietary license which led to a rejected build for one of my customers. While searching for the root cause @fabge found a difference between the license text given on https://en.wikipedia.org/wiki/MIT_License#MIT_No_Attribution_License and https://github.com/aws/mit-0. Sonatype Support states that this shouldn't be an issue with their recent Nexus IQ release. However, I wanted to share this finding with you.

I added #1881

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!