{"action":"created","issue":{"url":"https://api.github.com/repos/ipfs/go-ipfs/issues/5781","repository_url":"https://api.github.com/repos/ipfs/go-ipfs","labels_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/5781/labels{/name}","comments_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/5781/comments","events_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/5781/events","html_url":"https://github.com/ipfs/go-ipfs/issues/5781","id":381352800,"node_id":"MDU6SXNzdWUzODEzNTI4MDA=","number":5781,"title":"process: Improving how we work","user":{"login":"eingenito","id":281571,"node_id":"MDQ6VXNlcjI4MTU3MQ==","avatar_url":"https://avatars3.githubusercontent.com/u/281571?v=4","gravatar_id":"","url":"https://api.github.com/users/eingenito","html_url":"https://github.com/eingenito","followers_url":"https://api.github.com/users/eingenito/followers","following_url":"https://api.github.com/users/eingenito/following{/other_user}","gists_url":"https://api.github.com/users/eingenito/gists{/gist_id}","starred_url":"https://api.github.com/users/eingenito/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eingenito/subscriptions","organizations_url":"https://api.github.com/users/eingenito/orgs","repos_url":"https://api.github.com/users/eingenito/repos","events_url":"https://api.github.com/users/eingenito/events{/privacy}","received_events_url":"https://api.github.com/users/eingenito/received_events","type":"User","site_admin":false},"labels":[{"id":384920816,"node_id":"MDU6TGFiZWwzODQ5MjA4MTY=","url":"https://api.github.com/repos/ipfs/go-ipfs/labels/meta","name":"meta","color":"8AE833","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":26,"created_at":"2018-11-15T21:45:57Z","updated_at":"2018-11-29T03:08:00Z","closed_at":null,"author_association":"NONE","body":"## Context\r\n\r\nWe don't currently have a routine place where go-ipfs contributors can reflect on the challenges of working on the project and iterate on improvements. This team doesn't get much time together synchronously, so I want to find a constructive async way to do so. This team *is* really good at commenting on issues and PRs, thus....\r\n\r\n## Proposal\r\n\r\nLet's use this issue to enumerate our challenges and suggest (and agree to try out) solutions.\r\n\r\n- For a bounded period (weekish) let's reflect on how we can improve the go-ipfs project. It can be challenges (assuming any exist) with or without proposed solutions, or things we currently do and want to do even more of. Consider starting comments with \"I wish...\" or \"I like....\"\r\n- Then we'll vote for the challenges we think are most important to address first - maybe because they're the most acute, or maybe because they're the ones that don't seem intractable. Up to the voter. We may group similar ideas to avoid vote splitting. You get three votes.\r\n- Then I'll create new issue/PR summarizing the most popular challenges and solutions. The team will have an opportunity to refine the solution part, I'll restate the solution and after a final call for dissenters we'll agree to try our solution out. Keep in mind these might be as un-momentous as say 'Make a PR template for go-ipfs with these fields ...'. We don't have to solve everything at once.\r\n- Then we'll do it again, and this time we'll also reflect on how our changes have gone.\r\n\r\n## Guidelines\r\n\r\n- We agree not to create another issue discussing the process defined by this one. This is the top issue.\r\n- We don't have to be super ambitious; I always like simple changes to repeated behaviors. This project isn't going away, so we can feel free to defer tough questions if we don't have good answers.\r\n- This is a public forum, and people with zero context can read this issue, so just frame things constructively. We don't want to scare away passers by.\r\n- One 'I wish/like' per comment so we can easily vote on them afterwards.\r\n\r\n## Notes\r\n\r\nObviously David already interviewed the team and produced a list of challenges and possible solutions in the [Golang Core Dev Team Update, August 2018](https://docs.google.com/document/d/1t2dv6b-IiZrQ6P68CdAvdebpmqL9Yey0wwbS8MY6DlE/edit#heading=h.aysjg69aac5n). Those are all fair game. I'll add them if they're not added by someone else - but they're all pretty big, and these don't have to be that big."},"comment":{"url":"https://api.github.com/repos/ipfs/go-ipfs/issues/comments/442690036","html_url":"https://github.com/ipfs/go-ipfs/issues/5781#issuecomment-442690036","issue_url":"https://api.github.com/repos/ipfs/go-ipfs/issues/5781","id":442690036,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjY5MDAzNg==","user":{"login":"kevina","id":1271492,"node_id":"MDQ6VXNlcjEyNzE0OTI=","avatar_url":"https://avatars2.githubusercontent.com/u/1271492?v=4","gravatar_id":"","url":"https://api.github.com/users/kevina","html_url":"https://github.com/kevina","followers_url":"https://api.github.com/users/kevina/followers","following_url":"https://api.github.com/users/kevina/following{/other_user}","gists_url":"https://api.github.com/users/kevina/gists{/gist_id}","starred_url":"https://api.github.com/users/kevina/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kevina/subscriptions","organizations_url":"https://api.github.com/users/kevina/orgs","repos_url":"https://api.github.com/users/kevina/repos","events_url":"https://api.github.com/users/kevina/events{/privacy}","received_events_url":"https://api.github.com/users/kevina/received_events","type":"User","site_admin":false},"created_at":"2018-11-29T03:08:00Z","updated_at":"2018-11-29T03:08:00Z","author_association":"CONTRIBUTOR","body":"> I (selfishly) wish that we had a more collaborative development process. I'm not used to being on a team that defaults to communication in github so I don't have a lot of insight into how to improve efficiency (apart from being more collaborative which is like a tautology). I miss synchronous story writing and backlog grooming meetings which are important parts of of how I'm used to learning.\r\n\r\nI am almost the opposite.  I don't really like in-person meetings via zoom but will reluctantly agree to join them when required.  I prefer IRC first when more imminent feedback is helpful and then when that fails a video call.\r\n\r\nI am also not sure of the value of having a video call all the time and would sometimes prefer the option of a simple phone call or audio only zoom call.\r\n\r\nAnd again, doing things over IRC provides an automatic transcript that we can copy and paste into an issue, of which I often do."}}
{"actor":{"display_login":"kevina"}}