SPDX headers?

[rossabaker]

I have swallowed a bunch of defaults I don't like in the interest of comity, but typelevel/jawn#402 has me wondering about whether this is our opportunity to wave the flag for SPDX. It accomplishes the same, is more terse, and is machine readable. SPDX is good.

[rossabaker]

We should crap or get off the pot on this one before we migrate too many more projects.

[armanbilge]

I would merge a PR that makes this change 👍

With that said, once we have a prePR command and we teach Scala Steward to run it for us, we should be able to make changes like this and propagate them without manual intervention. See also:

• Support Scalafix migrations that target build files scala-steward-org/scala-steward#2308

[rossabaker]

I'm less worried about being able to do it and more worried about defaults churn now that this has been rolled out to more than a couple obscure repositories.

[armanbilge]

Fair enough. But it would already be a sort of defaults churn since for most/all repos the de-facto default seems to be non-SPDX headers.

[rossabaker]

Yeah, that's a fair point. I was focued on the repos that have no headers.

There should be a high bar to changing defaults, and this appears to be one that only I care about.

[DavidGregory084]

I had a quick look at this one and it seems like it could be awkward as I don't think sbt-header will regenerate existing headers into the new style in headerCreate, but it will complain about them using the wrong style for headerCheck.

All I did to test this was to add the headerLicenseStyle to the projectSettings of TypelevelPlugin in sbt-typelevel, so it might be that more configuration was needed.

[rossabaker]

This is when http4s migrated from SPDX to the default: https://github.com/Banno/mobile-data-services/pull/8954. I wish I remembered whether that regeneration commit just worked or if I did black sed magic to strip the original header before recreating. 🤔