3 ms·

>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 so

>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.

jeremyjh 1y ago
"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 1y ago
I'd say, in this case "chore" means "boring, nothing to see here".
- layer8 1y ago
  It's interesting, because "chore" to me has strong connotations of "tedious, unpleasant".
  - staunton 1y ago
    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 1y ago
      I don’t find it appropriate nor useful to place such a sentiment in a commit message, much less as a standard tag.
      - skc 1y ago
        It's a nerdy colloquialism. ie, it's not that serious
        layer8 1y ago
        That’s part of the reason why I’d object to it in a commit message, in a professional setting.
        staunton 1y ago
        Some organizations strongly encourage marking all commits as one of a list of categories such as "feature/fix/chore/...". The tags are then bound to loose all meaning (literal or figurative) very soon. Unless there was some "conspiracy" to violate the license (my original comment was an attempt at playfully hinting at that possibility, though I don't find it very likely), I'm sure the person who wrote that commit message thought about it for less than three seconds.
croemer 1y ago
"chore" is a common conventional commit message type, see https://www.conventionalcommits.org/en/v1.0.0/ https://www.conventionalcommits.org/en/v1.0.0/

jeremyjh 1y ago

"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 1y ago

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

layer8 1y ago
It's interesting, because "chore" to me has strong connotations of "tedious, unpleasant".
- staunton 1y ago
  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 1y ago
    I don’t find it appropriate nor useful to place such a sentiment in a commit message, much less as a standard tag.
    - skc 1y ago
      It's a nerdy colloquialism. ie, it's not that serious
      - layer8 1y ago
        That’s part of the reason why I’d object to it in a commit message, in a professional setting.
        staunton 1y ago
        Some organizations strongly encourage marking all commits as one of a list of categories such as "feature/fix/chore/...". The tags are then bound to loose all meaning (literal or figurative) very soon. Unless there was some "conspiracy" to violate the license (my original comment was an attempt at playfully hinting at that possibility, though I don't find it very likely), I'm sure the person who wrote that commit message thought about it for less than three seconds.

croemer 1y ago

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