search

inclusivenaming / org

Pre-release organization info, meeting notes, collaboration, etc.
43 stars 9 forks source link

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

Closed jamesgeddes closed 7 months ago

jamesgeddes commented 2 years ago

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,

Thanks!

markcmiller86 commented 2 years ago

@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 commented 2 years ago

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.