{"action":"created","issue":{"url":"https://api.github.com/repos/cfpb/capital-framework/issues/241","labels_url":"https://api.github.com/repos/cfpb/capital-framework/issues/241/labels{/name}","comments_url":"https://api.github.com/repos/cfpb/capital-framework/issues/241/comments","events_url":"https://api.github.com/repos/cfpb/capital-framework/issues/241/events","html_url":"https://github.com/cfpb/capital-framework/issues/241","id":115981126,"number":241,"title":"[VZ] Vision / roles for upcoming CF improvements","user":{"login":"cfarm","id":702526,"avatar_url":"https://avatars.githubusercontent.com/u/702526?v=3","gravatar_id":"","url":"https://api.github.com/users/cfarm","html_url":"https://github.com/cfarm","followers_url":"https://api.github.com/users/cfarm/followers","following_url":"https://api.github.com/users/cfarm/following{/other_user}","gists_url":"https://api.github.com/users/cfarm/gists{/gist_id}","starred_url":"https://api.github.com/users/cfarm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cfarm/subscriptions","organizations_url":"https://api.github.com/users/cfarm/orgs","repos_url":"https://api.github.com/users/cfarm/repos","events_url":"https://api.github.com/users/cfarm/events{/privacy}","received_events_url":"https://api.github.com/users/cfarm/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cfpb/capital-framework/labels/planning","name":"planning","color":"fad8c7"},{"url":"https://api.github.com/repos/cfpb/capital-framework/labels/voltrazord","name":"voltrazord","color":"ff69b4"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/cfpb/capital-framework/milestones/3","html_url":"https://github.com/cfpb/capital-framework/milestones/Voltrazord","labels_url":"https://api.github.com/repos/cfpb/capital-framework/milestones/3/labels","id":1080793,"number":3,"title":"Voltrazord","description":"The goal of this release is speed. Using CF quickly, contributing to CF quickly, squashing CF bugs quickly.","creator":{"login":"contolini","id":1060248,"avatar_url":"https://avatars.githubusercontent.com/u/1060248?v=3","gravatar_id":"","url":"https://api.github.com/users/contolini","html_url":"https://github.com/contolini","followers_url":"https://api.github.com/users/contolini/followers","following_url":"https://api.github.com/users/contolini/following{/other_user}","gists_url":"https://api.github.com/users/contolini/gists{/gist_id}","starred_url":"https://api.github.com/users/contolini/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/contolini/subscriptions","organizations_url":"https://api.github.com/users/contolini/orgs","repos_url":"https://api.github.com/users/contolini/repos","events_url":"https://api.github.com/users/contolini/events{/privacy}","received_events_url":"https://api.github.com/users/contolini/received_events","type":"User","site_admin":false},"open_issues":25,"closed_issues":3,"state":"open","created_at":"2015-04-23T15:40:40Z","updated_at":"2015-11-13T20:40:44Z","due_on":"2016-01-25T05:00:00Z","closed_at":null},"comments":3,"created_at":"2015-11-09T22:23:18Z","updated_at":"2015-11-17T20:00:33Z","closed_at":null,"body":"I called a meeting with the following folks to talk about vision and roles for planning the upcoming CF improvements that we've already started through our FEWD standards meetings.\r\n\r\n## Background\r\n* @virtix asked @Scotchester, @jimmynotjim, @KimberlyMunoz, and @cfarm to spend time improving CF and its adoption.\r\n* @ascott1 has made CF/Voltrazord the focus of the FEWD meetings now that we've got [front-end standards 1.0](https://github.com/cfpb/front-end).\r\n* @Scotchester and @contolini have been the historical creators and maintainers of Capital Framework.\r\nSo, how do we coordinate all of our time most effectively and enjoyably to get work done?\r\n\r\n## Agenda\r\n* How do we want to divvy up the work for Capital Framework improvements moving forward? \r\n* What do you see as your role in improving Capital Framework? What do you want to work on?\r\n* How do we approve changes/pull requests?\r\n* How do we delegate work amongst FEWDs?\r\n* What's the vision for the future of Capital Framework? This will guide our decisions on the above questions + technical changes.\r\n\r\n### What do you see as your role while working on CF?\r\n@cfarm - improve the developer experience when using CF in our projects and referring to documentation so we can find what we need and easily identify gaps\r\n@jimmynotjim - wants to get code pattern coverage to a place where we have stuff we can all use confidently.\r\n@KimberlyMunoz  - wants to make it easier for *everyone* to contribute changes to CF\r\n@contolini - wants to make it easier to contribute and so people don't just complain but actually fix stuff when they have a problem.\r\n@ascott1 - make it one work stream to add new UI components to your project WHILE adding it to Capital Framework\r\n@Scotchester - vision: minimize disruption to project teams when using/contributing to CF. Role: coordinate changes to Capital Framework, spend more of his time on this, set priorities, keep backlog updated.\r\n  @Scotchester's proposed focus areas for individual contributors: accessibility, js, build process, html/markup, documentation + community engagement. \r\n Discussion on assigning these to specific people brought up the following concerns: \r\n  * Limits our contributions and potential for making improvements.\r\n  * Could be a blocker if we wait only for certain people to work on certain areas. What happens if those people are out?\r\n  * Can we make these our focus areas/priorities for everyone instead of assigning each area to a specific person? That way we are all responsible.\r\n  * Risk of not having a focus for individual contributors: 'everyone else can do it' attitude so nothing ends up getting done. \r\n    * Can we solve this problem with a Code Review process? \r\n    * And with delegating during sprint planning at FEWD Friday meetings?\r\n\r\n## Code Review workflow\r\n* Contributors assign PR to specific reviewer from above folks- based on 'focus areas' ? or just who is available?\r\n* Time limit: PR needs reviewing in 1 week or gets self-merged. :trollface: \r\n\r\n## Vision\r\nWe need some vision statements about how we want CF to work on a high level and long-term. These will guide our decisions around priorities and implementation.\r\n* Each of us contributes to vision based on the following focus areas and posts in this thread, we'll add to the readme for guiding us during FEWD meetings.\r\n  * [ ]  @KimberlyMunoz - accessibility vision\r\n  * [ ] @contolini - js + build process\r\n  * [ ] @jimmynotjim - html/markup lead\r\n  * [ ] @ascott1 - FEWD user experience\r\n  * [ ] @cfarm - documentation + community engagement. \r\n\r\n## Totally unrelated update + discussion on the one repo changes to CF.\r\n@contolini demoed his one repo changes to get feedback. He'll demo for everyone else at FEWD Friday - will present the contributing workflow & the publishing changes workflow.\r\n\r\n**How it works** \r\n* Components have been moved to the `capital-framework` repo and maintain their existing structure with src files, plus a parent directory contains a new markdown file for documenting HTML snippets + you can add a screenshot there too.\r\n* Anything merged to master will get published to NPM by Travis for each component. master will always be the latest releases. Each component gets automated contributing + license docs, readme, etc\r\n* With voltrazord we will publish the whole CF github repo as one bower package, for use in things like design manual. currently they are individual packages for each component and that is going away for time being.\r\n* @contolini will post some notes to Github (including todos/next steps for other FEWDs to pick up) and share the link so @ascott1 and @cfarm can work off his usage.md file to produce docs. line 32 of template.js gulp script - produces the markdown file and compiles to usage.html template\r\n* @contolini is out next week. so if you have questions about how this stuff works ask him this week!!!!!!!!!"},"comment":{"url":"https://api.github.com/repos/cfpb/capital-framework/issues/comments/157488795","html_url":"https://github.com/cfpb/capital-framework/issues/241#issuecomment-157488795","issue_url":"https://api.github.com/repos/cfpb/capital-framework/issues/241","id":157488795,"user":{"login":"cfarm","id":702526,"avatar_url":"https://avatars.githubusercontent.com/u/702526?v=3","gravatar_id":"","url":"https://api.github.com/users/cfarm","html_url":"https://github.com/cfarm","followers_url":"https://api.github.com/users/cfarm/followers","following_url":"https://api.github.com/users/cfarm/following{/other_user}","gists_url":"https://api.github.com/users/cfarm/gists{/gist_id}","starred_url":"https://api.github.com/users/cfarm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cfarm/subscriptions","organizations_url":"https://api.github.com/users/cfarm/orgs","repos_url":"https://api.github.com/users/cfarm/repos","events_url":"https://api.github.com/users/cfarm/events{/privacy}","received_events_url":"https://api.github.com/users/cfarm/received_events","type":"User","site_admin":false},"created_at":"2015-11-17T20:00:33Z","updated_at":"2015-11-17T20:00:33Z","body":"My first stab at some ~vision statements~ :crystal_ball: \r\n\r\n### Vision for documentation \r\n\r\nCapital Framework documentation is easy to navigate, code snippets have clear use-cases and examples, and developers can update the documentation quickly and easily in one place alongside their changes to the codebase.\r\n\r\n### Vision for community engagement\r\nInternal:\r\nCapital Framework fulfills the needs of CFPB developers to quickly build and customize websites and code patterns so that we can focus on serving performant and usable websites to consumers, customers, and internal partners.\r\n\r\nExternal:\r\nneeded"}}