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

Separation of the project and the language #1133

Closed
darol100 opened this Issue Nov 1, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@darol100
Contributor

darol100 commented Nov 1, 2015

Problem / Motivation

At Drupal Badcamp @jmolivas , @phenaproxima and myself we were discussing on how we are going to implement the Samuel Jack Language (#1106) into this project without been committed in the main project because does not look professional. This brings some interesting point because as today this project ships with all languages, which it should not it IMO because I'm not going to be using other languages that are not English. I think this project should be ship with English and if the user needs another language they can download it and integrated it to the project. Ships with all languages make the project a lot bigger instead of having it separate from the project.

Solution

  • We need to open new repositories called console_[languagecode] for instance for Spanish console_es in Github and Drupal.org.
    • We should provide admin rights to the people that contribute to languages often. So they can take care of the languages.
  • We should have a command that can easily download the language if is under hechoendrupal GitHub organization.
  • We should try to have a travis job that creates a PR in all languages every time a new command get added to the project English.

Note: English is the only language that we are going to shipping with the Drupal Console because English is used for development purpose and not for translation purpose.

Benefits

  • Separates the development work with the translation work.
  • Project get smaller.
  • We can provide git access to translator without the need of getting access to the entire project.

@jmolivas jmolivas modified the milestone: must-have Nov 3, 2015

@darol100

This comment has been minimized.

Contributor

darol100 commented Dec 17, 2015

Asking one more time about this issue. Since is been tag as "must-have".

@jmolivas

My understating was that you was going to talk with one of the composer maintainer about how to implement this. Did you get any response about this ?

@darol100 darol100 modified the milestones: 0.10.13, must-have Feb 25, 2016

@jmolivas jmolivas modified the milestones: 0.10.13, 1.0.0-alpha-1, 1.0.0-beta-1 Mar 18, 2016

@jmolivas jmolivas modified the milestones: 1.0.0-beta1, 1.0.0-beta2 May 5, 2016

@jmolivas jmolivas modified the milestones: 1.0.0-beta2, 1.0.0-beta3 Jun 2, 2016

@jmolivas jmolivas modified the milestones: 1.0.0-beta3, 1.0.0-beta4 Jun 27, 2016

@jmolivas jmolivas modified the milestones: 1.0.0-beta4, 1.0.0-rc1 Jul 14, 2016

@jmolivas

This comment has been minimized.

Member

jmolivas commented Nov 17, 2016

Fixed

@jmolivas jmolivas closed this Nov 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment