Thanks for vale!

It appears that (at least) the latest Microsoft and Google packages do not contain the LICENSE file from the repository in their distributed media.

Concretely, on this repo: this could be documented as an additional meta.json field (e.g. "license_files": ["path-to-license-file", "path-to-upstream-license-file"]) rather than expecting a specifically-named file. Checking that this key exists, and the references paths exist in the as-downloaded archive, could be automated for PR review.

After there is a documented approach, this would then be worthwhile to add to the "first-party" repackagings in this org, and encourage others (such as RedHat) to include this information.

As for those first-party ones (and the list of license files): attribution in the README is good, but it seems like distributing the upstream's additional documents (e.g. Microsoft's MIT, CC and ThirdParty) might actually be required to meet the intent of the license granted to downstreams, even if a hard requirement isn't triggered by this manner of derived work in all cases.

Motivation: I am interested in re-re-packaging some of these archives for conda-forge (as well as integrating with our re-packaging of hunspell-en), which pretty much requires accurate attribution to be accepted. Assembling all these from source is... fine, but historically has been difficult to keep accurate at scale, whereas a convention-based approach (e.g. spacy-models) has worked well.

Actionables for #1 :

• Update docs to make it clear that a clone into StylesPath is supported (all the readme's suggest manual copying
• Add this project which is more a comprehensive collection of styles: vale-styles

Could you please create a package for gitlab?
The code base is located here: https://gitlab.com/gitlab-org/charts/gitlab/-/tree/master/doc/.vale/gitlab

With the release of v2.16.0, it's now possible to create sharable configurations. This is particularly useful for providing a better out-of-the-box experience with popular site generators.

I've released the first version of such a package for Hugo, and I'd like to get 3 more released soon:

• Jekyll
• Gatsby
• Docusaurus

Gatsby and Docusaurus should both probably inherit from a more general MDX package.

Would you consider moving vale style development here and then using something like splitsh
to create read-only mirrors? This would allow for a more integrated development workflow.
The reason I am requesting this is that the docs for errata-ai/Microsoft

Download the latest release, copy the "Microsoft" directory to your StylesPath, and include it in your configuration file

That doesn't appear ideal in a git environment. If all the development was instead done here and the Microsoft directory was split into its own git mirror (without the tests etc), it would simply be a matter of using git submodules or git subtree commands to keep those rules updated (on the consumer side). Meanwhile, all the tests can exist here in this repo as the single source of truth.

Reference: https://github.com/splitsh/lite
This is used with success by the PHP symfony framework e.g. https://github.com/symfony/asset

Red Hat is providing a Vale configuration of their style guide. it would be nice to provide a package for it.

the zip currently attached to the tag is matching the requirements.https://github.com/redhat-documentation/vale-at-red-hat/releases/tag/v143 contains a folder and then the .vale.ini file. I guess it can be used as-is. To be checked.

What is the relationship between this repository, and the other like-named repositories to those found in pkg?

• https://github.com/errata-ai/alex
• https://github.com/errata-ai/Google
• https://github.com/errata-ai/hugo
• https://github.com/errata-ai/joblint
• https://github.com/errata-ai/Microsoft
• https://github.com/errata-ai/proselint
• https://github.com/errata-ai/readability
• https://github.com/errata-ai/write-good

Should this repo, or the specific other ones, be considered "canonical"?

It looks like they all accept PRs and cut releases (with seemingly unrelated version lines), so it's a bit hard to tell.

Would it be possible to have something like Hemingway Editor functionality as a style?

Hi - I am looking for a way to check for when to use a vs an.

A interesting ... > incorrect
An interesting ... > correct

Is there any plan to include the Chicago Style Guide?