{"action":"opened","issue":{"url":"https://api.github.com/repos/portphp/boilerplate/issues/6","labels_url":"https://api.github.com/repos/portphp/boilerplate/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/portphp/boilerplate/issues/6/comments","events_url":"https://api.github.com/repos/portphp/boilerplate/issues/6/events","html_url":"https://github.com/portphp/boilerplate/issues/6","id":85943040,"number":6,"title":"Small list of improvements","user":{"login":"sagikazarmark","id":1226384,"avatar_url":"https://avatars.githubusercontent.com/u/1226384?v=3","gravatar_id":"","url":"https://api.github.com/users/sagikazarmark","html_url":"https://github.com/sagikazarmark","followers_url":"https://api.github.com/users/sagikazarmark/followers","following_url":"https://api.github.com/users/sagikazarmark/following{/other_user}","gists_url":"https://api.github.com/users/sagikazarmark/gists{/gist_id}","starred_url":"https://api.github.com/users/sagikazarmark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sagikazarmark/subscriptions","organizations_url":"https://api.github.com/users/sagikazarmark/orgs","repos_url":"https://api.github.com/users/sagikazarmark/repos","events_url":"https://api.github.com/users/sagikazarmark/events{/privacy}","received_events_url":"https://api.github.com/users/sagikazarmark/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-06-07T21:06:12Z","updated_at":"2015-06-07T21:06:12Z","closed_at":null,"body":"I spent some time with the boilerplate repo, here is a small list of changes I suggest:\r\n\r\n1. Line length restriction applies to PSR2 coding standard, but not markdown files. I think it is confusing that the lines are broken after hitting 80 characters. The IDE will handle that. In general: line length restriction does not make sense in continuous text.\r\n\r\n2. @ddeboer you mentioned that you would like to keep instructions simple.\r\n\r\n> Open a command console\r\n\r\nWhile this is simple, I think it is not necessary.  The longest paragraph in the readme is the installation instruction part which is weird to me. I also think that the 'Issues and feature requests' should probably go into the Contribution guide.\r\n\r\n3. security@portphp.org.sec\r\n\r\n???\r\n\r\nWhat is this email address? Also, while github automatically transforms it into a link, I would rather add a formal MD anchor here with a `mailto:` link.\r\n\r\n4. portphp/something also feels weird to me. Port Something is much more attractive IMO. :wink: \r\n\r\n5. I am missing a link to the packagist site of the package. I suggested a downloads badge earlier. Actually, I don't mind, but I think a link to that page is useful.\r\n\r\n6. I would add PSR2 checking to scrutinizer:\r\n\r\n``` yml\r\ntools:\r\n  php_code_sniffer:\r\n    config:\r\n      standard: \"PSR2\"\r\n```\r\n\r\n7. In markdown files it increases the readability (in IDE) if there are empty lines before each headline.\r\n\r\n8. I think the support part in the composer config file is not necessary. Everything (except the docs link) is automatically guessed by packagist.\r\n\r\nI didn't open a PR as these things depend on personal preference as well. So take them into practice if you wish."}}