-
Notifications
You must be signed in to change notification settings - Fork 121
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
Move locales.php into a separate repo #350
Comments
We should probably even go farther than that and allow a site to update their locales independently of GlotPress. I agree it should be it's own repo and a submodule to GlotPress-WP, but beyond that:
|
|
Example: https://github.com/ocean90/gp-locales/commits/develop/locales.php $ git clone git@github.com:ocean90/GlotPress-WP.git
$ cd GlotPress-WP
$ git filter-branch --prune-empty --subdirectory-filter locales develop
$ git remote set-url origin git@github.com:ocean90/gp-locales.git
$ git push origin HEAD Based on https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/. |
I'm thinking we need to take a closer look at how the locales are managed, #385 is a good example where we probably need some more rigor around how locales are changed. I think we need to separate the class from the data and build out the class to handle adding, updating and deleting locales, probably as data in a table. |
There is https://github.com/GlotPress/gp-locales now. The is only one issue with a separate repo: It's not possible to include just one file as a submodule. Not sure if it's a good idea to include all the upcoming tests and readmes too. |
We could add them to https://github.com/GlotPress/GlotPress-WP/blob/develop/bin/release.ini#L21 |
Closing as a wontfix for now. |
Proposal:
Why? To separate the flow of adding new locales from the plugin. For example we can use templates (https://github.com/blog/2111-issue-and-pull-request-templates). It makes it also easier to use for other projects which don't need the whole GlotPress, just the list of locales.
We can and should also try to make some of the pre-checks, like valid ISO codes or locale names, automated via Travis CI.
The text was updated successfully, but these errors were encountered: