{"action":"opened","issue":{"url":"https://api.github.com/repos/dagwieers/dstat/issues/104","repository_url":"https://api.github.com/repos/dagwieers/dstat","labels_url":"https://api.github.com/repos/dagwieers/dstat/issues/104/labels{/name}","comments_url":"https://api.github.com/repos/dagwieers/dstat/issues/104/comments","events_url":"https://api.github.com/repos/dagwieers/dstat/issues/104/events","html_url":"https://github.com/dagwieers/dstat/issues/104","id":141018231,"number":104,"title":"Planning for the new release of dstat","user":{"login":"scottchiefbaker","id":3429760,"avatar_url":"https://avatars.githubusercontent.com/u/3429760?v=3","gravatar_id":"","url":"https://api.github.com/users/scottchiefbaker","html_url":"https://github.com/scottchiefbaker","followers_url":"https://api.github.com/users/scottchiefbaker/followers","following_url":"https://api.github.com/users/scottchiefbaker/following{/other_user}","gists_url":"https://api.github.com/users/scottchiefbaker/gists{/gist_id}","starred_url":"https://api.github.com/users/scottchiefbaker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/scottchiefbaker/subscriptions","organizations_url":"https://api.github.com/users/scottchiefbaker/orgs","repos_url":"https://api.github.com/users/scottchiefbaker/repos","events_url":"https://api.github.com/users/scottchiefbaker/events{/privacy}","received_events_url":"https://api.github.com/users/scottchiefbaker/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-15T15:56:39Z","updated_at":"2016-03-15T15:56:39Z","closed_at":null,"body":"Paging: @svenstaro, @dagwieers, @thinrope, @SpamapS, @kdave\r\n\r\nFirst and foremost I'd like to thank @dagwieers for opening up dstat and letting the community help. Dstat is too important a project to wither away. :+1: :+1: :+1: \r\n\r\nWe decided to close down #55 to re-focus our efforts on a new release without all the > 2+ year old cruft on that old issue. I'd like to start planning what people would like to see in a new release. Here are my suggestions\r\n\r\n1. Release early, release often. It won't be perfect, but we should let people know the project isn't dead\r\n1. Do we want to establish a consistent release schedule?\r\n1. Update documentation to reflect any changes in commits since last release\r\n1. Any low hanging fruit among the existing pull-requests we can pull in?\r\n1. Or should we just release what we have in git already without pulling in new code\r\n1. Do we want to establish a Github \"organization\" for dstat that we can have all support? Or do we leave it where it is?\r\n1. Are there any known bugs that we should address right away?\r\n1. Anything else at all?\r\n\r\nI'll be the first to admit my Python skills are severely lacking (I'm a Perl guy), so I may not be able to contribute any whiz-bang code, but I can help coordinate.\r\n\r\n#longlivedstat"}}