{"issue":{"title":"Migrate plugins documentation to their own repos","user":{"login":"dadoonet","id":274222,"url":"https://api.github.com/users/dadoonet","gravatar_id":"20049a614b7f6838dc87b4bc39c42079","avatar_url":"https://secure.gravatar.com/avatar/20049a614b7f6838dc87b4bc39c42079?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"created_at":"2011-12-26T15:32:48Z","milestone":null,"state":"open","updated_at":"2011-12-26T15:40:55Z","labels":[],"id":2658689,"closed_at":null,"html_url":"https://github.com/elasticsearch/elasticsearch.github.com/issues/127","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"Hi,\r\n\r\nI would like to suggest to migrate plugins documentation in their own website.\r\nFor example : elasticsearch:elasticsearch-river-couchdb webpages should be under a gh-pages branch and available at \r\nhttp://elasticsearch.github.com/elasticsearch-river-couchdb/\r\n\r\nWhat do you think ?\r\n\r\nIf you agree with that, I can start migrate the pages from elasticsearch:elasticsearch.github.com to gh-pages branches using a template as I did for the RSS River : http://dadoonet.github.com/rssriver/\r\n\r\nHTH\r\nDavid.","number":127,"url":"https://api.github.com/repos/elasticsearch/elasticsearch.github.com/issues/127","comments":2,"assignee":null},"comment":{"user":{"login":"kimchy","id":41300,"url":"https://api.github.com/users/kimchy","gravatar_id":"fd44bb3c96e34e000c5453a0078900d6","avatar_url":"https://secure.gravatar.com/avatar/fd44bb3c96e34e000c5453a0078900d6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"created_at":"2011-12-26T15:40:55Z","updated_at":"2011-12-26T15:40:55Z","id":3275148,"body":"I suggest migrating the docs to the readme, most plugins don't require heavy docs, so the readme is good enough (and simpler).","url":"https://api.github.com/repos/elasticsearch/elasticsearch.github.com/issues/comments/3275148"},"action":"created"}