[throwaway277432]

>chore: change to MIT license

What does "chore" mean in this context? Is the license just leftover from some MS open source template? If so there is perhaps some leeway, and the author maybe just didn't realize he needed to use the original MIT license file including the notices and not just a template one grabbed from the internet.

Any other explanation for such a "relicensing" would be extremely worrisome.

[croemer]

"chore" is a common conventional commit message type, see https://www.conventionalcommits.org/en/v1.0.0/

[jeremyjh]

"chore" just means the type of change; as opposed to a fix, a feature, refactoring, there are some things that you have to do in the repo that can be called "chores".

[staunton]

I'd say, in this case "chore" means "boring, nothing to see here".

[layer8]

It's interesting, because "chore" to me has strong connotations of "tedious, unpleasant".

[staunton]

Right. It derives from the idea that programmers are supposed to find "solving interesting problems" pleasant. On the other hand, boring, repetitive tasks are called "chores".

[layer8]

I don’t find it appropriate nor useful to place such a sentiment in a commit message, much less as a standard tag.

[skc]

It's a nerdy colloquialism. ie, it's not that serious

[layer8]

That’s part of the reason why I’d object to it in a commit message, in a professional setting.