{"action":"created","issue":{"url":"https://api.github.com/repos/symphonycms/www-issues/issues/3","repository_url":"https://api.github.com/repos/symphonycms/www-issues","labels_url":"https://api.github.com/repos/symphonycms/www-issues/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/symphonycms/www-issues/issues/3/comments","events_url":"https://api.github.com/repos/symphonycms/www-issues/issues/3/events","html_url":"https://github.com/symphonycms/www-issues/issues/3","id":132705474,"number":3,"title":"Dedicated repo for \"symphonyextensions.com\"","user":{"login":"twiro","id":870227,"avatar_url":"https://avatars.githubusercontent.com/u/870227?v=3","gravatar_id":"","url":"https://api.github.com/users/twiro","html_url":"https://github.com/twiro","followers_url":"https://api.github.com/users/twiro/followers","following_url":"https://api.github.com/users/twiro/following{/other_user}","gists_url":"https://api.github.com/users/twiro/gists{/gist_id}","starred_url":"https://api.github.com/users/twiro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/twiro/subscriptions","organizations_url":"https://api.github.com/users/twiro/orgs","repos_url":"https://api.github.com/users/twiro/repos","events_url":"https://api.github.com/users/twiro/events{/privacy}","received_events_url":"https://api.github.com/users/twiro/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2016-02-10T13:52:29Z","updated_at":"2016-02-11T18:22:28Z","closed_at":null,"body":"This new issue tracker repo for getsymphony.com reminded me of [my request](https://github.com/symphonycms/symphony-2/issues/2469#issuecomment-128973071) for introducing a dedicated github-repo for [symphonyextensions.com](http://symphonyextensions.com/).\r\n\r\nThat repo wouldn't need to actually host the code of symphonyextensions.com _(though possibly helpful)_ but could be used for tracking website issues, managing extension-related tasks and promoting knowledge and best practices regarding extension development.\r\n\r\n### Purpose of a dedicated \"symphonyextensions.com\" repo\r\n\r\n1. **Report and discuss general issues** on symphonyextensions.com.\r\n2. **Report and discuss abandoned extensions** (organize transfer of ownership, mark obsolete extensions as deprecated, set links to recommended/supported alternatives).\r\n3. **Promote and discuss extensions standards** (like [Extension Metadata Schema](http://symphonyextensions.com/schemas/extension/1.0/), best practices for readme-files or coding guidelines).\r\n4. **Promote and discuss resources** that might be of interest for extensions development (including the rather hidden [migration guides](https://github.com/symphonycms/symphony-2/wiki) in the symphony wiki)\r\n5. **Report and discuss general extensions ideas/requests**\r\n6. **...**\r\n\r\nThe separate tasks should be listed/documented in the repo's readme so that it's easy to understand what the repo is about. I'd be happy to help with that but would prefer if a native english speaker with more knowledge of symphony's extension-eco-system could jump in here.\r\n\r\n### One issue tracker for all Symphony Network Websites?\r\n\r\nOne might also think about using a combined issue-tracker-repo for both **getsymphony.com** and **symphonyextensions.com** _(and maybe other network websites too)_, but as most of the tasks described above are extension-specific and extend the scope of simply reporting issues I suppose  a dedicated repo that offers a clean, focused and well-documented environment for the dasks described above would be the better and more helpful solution.\r\n\r\n### How to name the repo?\r\n\r\nI think simply naming the repo _\"symphonyextensions.com\"_ would be ok, but if one thinks about that repo as a general place for managing extension related tasks (beyond the context of the extensions website) _\"Symphony Extension Network\"_ or simply _\"Symphony Extensions\"_ might even make more sense.\r\n\r\n---\r\n\r\n@nitriques - what do you think about it? Worth a try? _(And big thanks for already fixing some of the recent issues on symphonyextensions.com)_\r\n\r\n@brendo, @michael-e - would like to hear your opinion too.\r\n\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/symphonycms/www-issues/issues/comments/182990192","html_url":"https://github.com/symphonycms/www-issues/issues/3#issuecomment-182990192","issue_url":"https://api.github.com/repos/symphonycms/www-issues/issues/3","id":182990192,"user":{"login":"nitriques","id":771169,"avatar_url":"https://avatars.githubusercontent.com/u/771169?v=3","gravatar_id":"","url":"https://api.github.com/users/nitriques","html_url":"https://github.com/nitriques","followers_url":"https://api.github.com/users/nitriques/followers","following_url":"https://api.github.com/users/nitriques/following{/other_user}","gists_url":"https://api.github.com/users/nitriques/gists{/gist_id}","starred_url":"https://api.github.com/users/nitriques/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nitriques/subscriptions","organizations_url":"https://api.github.com/users/nitriques/orgs","repos_url":"https://api.github.com/users/nitriques/repos","events_url":"https://api.github.com/users/nitriques/events{/privacy}","received_events_url":"https://api.github.com/users/nitriques/received_events","type":"User","site_admin":false},"created_at":"2016-02-11T18:22:28Z","updated_at":"2016-02-11T18:22:28Z","body":":rocket: "}}