{"action":"created","issue":{"url":"https://api.github.com/repos/cozy/cozy-guidelines/issues/5","labels_url":"https://api.github.com/repos/cozy/cozy-guidelines/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/cozy/cozy-guidelines/issues/5/comments","events_url":"https://api.github.com/repos/cozy/cozy-guidelines/issues/5/events","html_url":"https://github.com/cozy/cozy-guidelines/issues/5","id":55284493,"number":5,"title":"Process discussion: bug report","user":{"login":"jsilvestre","id":568111,"avatar_url":"https://avatars.githubusercontent.com/u/568111?v=3","gravatar_id":"","url":"https://api.github.com/users/jsilvestre","html_url":"https://github.com/jsilvestre","followers_url":"https://api.github.com/users/jsilvestre/followers","following_url":"https://api.github.com/users/jsilvestre/following{/other_user}","gists_url":"https://api.github.com/users/jsilvestre/gists{/gist_id}","starred_url":"https://api.github.com/users/jsilvestre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsilvestre/subscriptions","organizations_url":"https://api.github.com/users/jsilvestre/orgs","repos_url":"https://api.github.com/users/jsilvestre/repos","events_url":"https://api.github.com/users/jsilvestre/events{/privacy}","received_events_url":"https://api.github.com/users/jsilvestre/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-01-23T14:06:10Z","updated_at":"2015-01-23T15:41:36Z","closed_at":null,"body":"I have questions about https://github.com/cozy/cozy-guidelines/blob/master/process/bug-report.md\r\n\r\n> Once a developer is statisfied with his development he informs the right people\r\n* Technical Referant of the repository for merging (discussion on the PR, mention the TR in the PR).\r\n* Product Owner of the repository for closing the issue (discussion is made on the issue, add the label QA to the issue).\r\n\r\n1. Is the fact the PO has to make functional comment within the issue rather than within the PR itself an uneeded overhead?\r\n2. Do you think the PO shouldn't review a PR from a technical point of view?\r\n3. If the PO can review a PR from a technical PoV, separating functional comment and technical comment in two separate places seems weird.\r\n4. What about the PR status. If the PO doesn't do the merge, does he add a tag that say \"it's okay to merge that PR for me\" like `functional ok`?\r\n5. When does the PO close the issue: when the PR is merged or when the version is published?\r\n"},"comment":{"url":"https://api.github.com/repos/cozy/cozy-guidelines/issues/comments/71211612","html_url":"https://github.com/cozy/cozy-guidelines/issues/5#issuecomment-71211612","issue_url":"https://api.github.com/repos/cozy/cozy-guidelines/issues/5","id":71211612,"user":{"login":"m4dz","id":471486,"avatar_url":"https://avatars.githubusercontent.com/u/471486?v=3","gravatar_id":"","url":"https://api.github.com/users/m4dz","html_url":"https://github.com/m4dz","followers_url":"https://api.github.com/users/m4dz/followers","following_url":"https://api.github.com/users/m4dz/following{/other_user}","gists_url":"https://api.github.com/users/m4dz/gists{/gist_id}","starred_url":"https://api.github.com/users/m4dz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/m4dz/subscriptions","organizations_url":"https://api.github.com/users/m4dz/orgs","repos_url":"https://api.github.com/users/m4dz/repos","events_url":"https://api.github.com/users/m4dz/events{/privacy}","received_events_url":"https://api.github.com/users/m4dz/received_events","type":"User","site_admin":false},"created_at":"2015-01-23T15:41:36Z","updated_at":"2015-01-23T15:41:36Z","body":"You'll say that I'm a little bit obtuse, but I'm convinced that a tool like (HuBoard)[https://huboard.com/] can resolve our workflow-by-tags processes. This way, the tags can be added/remove to issues, following the kanban, and preserves from human errors or misused. We can add more steps to reflects the life-cycle of an issue, like:\r\n- assigned\r\n- in-progress\r\n- review\r\n- to merge\r\n- to release\r\n\r\nThe issue will be close when the new version is released."}}