Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt https://github.com/GeekZoneHQ/recommended-language #108

Closed
jamesgeddes opened this issue Apr 21, 2022 · 2 comments
Closed

Adopt https://github.com/GeekZoneHQ/recommended-language #108

jamesgeddes opened this issue Apr 21, 2022 · 2 comments

Comments

@jamesgeddes
Copy link

jamesgeddes commented Apr 21, 2022

As one of the INI's newest members, Geek.Zone would like to propose/request that the INI adopts the JSON word list at

https://github.com/GeekZoneHQ/recommended-language

as the official source of truth.

To do this, repo ownership will need to be transferred to the INI. I am happy to do this myself, given permissions, or am happy to provide an appointed INI representative with GZ permissions to do so.

This will then serve as the source for building everything that relates to the INI word list, including but not limited to,

  • human readable documentation
  • machine automations

Thanks!

@markcmiller86
Copy link

@jamesgeddes your timing couldn't be more fortuitous 🙌🏻 .

Another contributor, @abuango, has started a PR to address basically the same issue.

However, the goal of that PR is more than just the json API endpoint bootstrap file, which you have provided an excellent example of in your suggestion here.

In fact, in that PR, the goal is for authors of INI approved language recommendations (composed in GFM and one file per word/phrase as well as its derivatives) to simply do their work and have the website wordlist and json files get auto-generated from them.

So, my view is that you have provided a great example of what a generated json file should maybe look like (sans the URLs to the authored recommendations which were suggested in the PR mentioned above).

For now, I think your best bet to contribute in these directions is to participate in the dialog related to that PR. I am going to reference this issue from that PR.

@jamesgeddes
Copy link
Author

the goal is for authors of INI approved language recommendations (composed in GFM and one file per word/phrase as well as its derivatives) to simply do their work and have the website wordlist and json files get auto-generated from them

Agreed - JSON is not an overly human-compatible format. This would simply be the initial version that is "officially" adopted. How to update it would be a separate matter. The great thing about having it in a repo is that it could be done via PR or via a GUI.

@abuango abuango closed this as completed Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants