Stephan Druskat

Thanks @mfenner for the issue, and @hainesr for transferring it here. You're not missing anything, Martin, this simply isn't a field we have in CFF right now, but I think...

Thanks @dhimmel for this example. We'll start on planning for the next version soon, and will take this issue into consideration.

@mfenner @dhimmel In running up to the 1.3.0 release, we've discussed this again, and made the decision to not include it in *this* minor version for reasons of time and...

Thanks, @kevinmatthes, for this pull request, and sorry for taking such a long time with it. I think it makes a lot of sense to tighten restrictions, and would be...

Hi @kevinmatthes, thanks for this PR! I agree with what Jurriaan said in https://github.com/citation-file-format/citation-file-format/pull/395#issuecomment-1621692826, so once https://github.com/citation-file-format/citation-file-format/pull/395/commits/d10614d61bd2449fc2b908fe939da65753a81416 is rolled back this is good to be merged 🎉! Do you want...

Thanks for this PR and you continued engagement @kevinmatthes! It's much appreciated :).

Looks great IMHO: 

Closing, as there will always be a bleeding edge in a repo, and it's really hard to keep any "last" or "latest" _persistent version_ up-to-date.

> I fear that with that approach you are slowly reinventing the SPDX expression syntax. In addition, you still miss some cases. For example, if your code is dual-licensed and...

This is still the case in 1.8.4., where ```bash [options.packages.find] include = mypackage, mypackage.* ``` yields a misleading: ```bash pylint: error: argument --include-naming-hint: (None, "Invalid yn value 'mypackage, mypackage.*', should...