{"action":"created","issue":{"url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/255","labels_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/255/labels{/name}","comments_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/255/comments","events_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/255/events","html_url":"https://github.com/eris-ltd/eris-cli/issues/255","id":107137057,"number":255,"title":"Recommendation: turn `eris init` into `eris`","user":{"login":"taoeffect","id":138706,"avatar_url":"https://avatars.githubusercontent.com/u/138706?v=3","gravatar_id":"","url":"https://api.github.com/users/taoeffect","html_url":"https://github.com/taoeffect","followers_url":"https://api.github.com/users/taoeffect/followers","following_url":"https://api.github.com/users/taoeffect/following{/other_user}","gists_url":"https://api.github.com/users/taoeffect/gists{/gist_id}","starred_url":"https://api.github.com/users/taoeffect/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taoeffect/subscriptions","organizations_url":"https://api.github.com/users/taoeffect/orgs","repos_url":"https://api.github.com/users/taoeffect/repos","events_url":"https://api.github.com/users/taoeffect/events{/privacy}","received_events_url":"https://api.github.com/users/taoeffect/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-18T05:34:34Z","updated_at":"2015-09-18T08:23:09Z","closed_at":"2015-09-18T08:23:09Z","body":"I think `eris` would do well to follow as best it can the conventions that have been established by other tools, simply for the reason that it will make `eris` easier for newcomers to learn and will be less likely to confuse or turn them off.\r\n\r\nMany commonly used tools have an `init` command (just about every VCS?). Typically, `[tool] init` is a command that is meant to be used on a per-project basis (usually this turns out to be per-directory).\r\n\r\nWhat do other tools do when they need to setup a complicated environment? The established convention seems to be the one that `geth` follows:\r\n\r\n1. When the command is run, however it is run, it displays informative text (unless a `--yes` was passed).\r\n2. Often, this text is accompanied by a request for user input (usually a `y/n` question), such as \"Proceed\" or \"Agree\".\r\n\r\nAfter this intro, it does the setup, and never shows the intro again (unless the essential files are missing).\r\n\r\nSo, to summarize:\r\n\r\n- Following established conventions is good UX.\r\n- `init` has a very established convention, one that does not fit with `eris init`.\r\n- The behavior of `eris init` has a different established convention, one that I'd recommend adopting as it would improve UX."},"comment":{"url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/comments/141379596","html_url":"https://github.com/eris-ltd/eris-cli/issues/255#issuecomment-141379596","issue_url":"https://api.github.com/repos/eris-ltd/eris-cli/issues/255","id":141379596,"user":{"login":"compleatang","id":590037,"avatar_url":"https://avatars.githubusercontent.com/u/590037?v=3","gravatar_id":"","url":"https://api.github.com/users/compleatang","html_url":"https://github.com/compleatang","followers_url":"https://api.github.com/users/compleatang/followers","following_url":"https://api.github.com/users/compleatang/following{/other_user}","gists_url":"https://api.github.com/users/compleatang/gists{/gist_id}","starred_url":"https://api.github.com/users/compleatang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/compleatang/subscriptions","organizations_url":"https://api.github.com/users/compleatang/orgs","repos_url":"https://api.github.com/users/compleatang/repos","events_url":"https://api.github.com/users/compleatang/events{/privacy}","received_events_url":"https://api.github.com/users/compleatang/received_events","type":"User","site_admin":false},"created_at":"2015-09-18T08:23:09Z","updated_at":"2015-09-18T08:23:09Z","body":"This is not the convention we're going to follow. "}}