{"action":"created","issue":{"url":"https://api.github.com/repos/WordPress/gutenberg/issues/3354","repository_url":"https://api.github.com/repos/WordPress/gutenberg","labels_url":"https://api.github.com/repos/WordPress/gutenberg/issues/3354/labels{/name}","comments_url":"https://api.github.com/repos/WordPress/gutenberg/issues/3354/comments","events_url":"https://api.github.com/repos/WordPress/gutenberg/issues/3354/events","html_url":"https://github.com/WordPress/gutenberg/issues/3354","id":271555794,"number":3354,"title":"Provide plain language outline of project scope, direction, and goals","user":{"login":"mor10","id":1132200,"avatar_url":"https://avatars0.githubusercontent.com/u/1132200?v=4","gravatar_id":"","url":"https://api.github.com/users/mor10","html_url":"https://github.com/mor10","followers_url":"https://api.github.com/users/mor10/followers","following_url":"https://api.github.com/users/mor10/following{/other_user}","gists_url":"https://api.github.com/users/mor10/gists{/gist_id}","starred_url":"https://api.github.com/users/mor10/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mor10/subscriptions","organizations_url":"https://api.github.com/users/mor10/orgs","repos_url":"https://api.github.com/users/mor10/repos","events_url":"https://api.github.com/users/mor10/events{/privacy}","received_events_url":"https://api.github.com/users/mor10/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":34,"created_at":"2017-11-06T17:24:42Z","updated_at":"2017-12-01T16:00:10Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nBEFORE POSTING YOUR ISSUE:\r\n- These comments won't show up when you submit the issue.\r\n- Try to add as much detail as possible. Be specific!\r\n- Please add the version of Gutenberg you are using in the description\r\n- If you're requesting a new feature, explain why you'd like it to be added.\r\n- Search this repository for the issue and whether it has been fixed or reported already.\r\n- Ensure you are using the latest code before logging bugs.\r\n- Disable all plugins to ensure it's not a plugin conflict issue.\r\n-->\r\n\r\n## Issue Overview\r\nMy observation is the community is struggling to see the wider scope of the Gutenberg project due to lack of a single authoritative plain language resource containing this information. This creates a high degree of speculation, miscommunication, and frustration from all parties and the project suffers as a consequence. \r\n\r\nThe Gutenberg project needs plain language scope and process documentation: What is the end goal (everything in the view is a block), how are we going to get there (staged releases starting with the editor), and what will that mean for the future of various WordPress components (shortcodes, metaboxes, fields, etc). All (or most of) this information exists as individual comments, pull requests, blog posts, Slack updates, and other satellite information, but to my and the wider community's knowledge there is no single canonical resource where all the pieces are put together in a plain language easy to understand way.\r\n\r\n## Steps to Reproduce (for bugs)\r\n<!-- Provide a link to a live example, or an unambiguous set of steps to -->\r\n<!-- reproduce this bug. Include code to reproduce, if relevant -->\r\n1. Any discussion of Gutenberg in social media / blogs.\r\n2. Discussion in \"Are iframes a viable long-term solution for metaboxes?\" #3304 \r\n3. Ask WordPress users outside the Gutenberg bubble \"what is Gutenberg?\" and \"What will Gutenberg eventually become?\"\r\n<!-- Provide what browser you are using and any other specifics to your setup -->\r\n\r\n## Expected Behavior\r\n<!-- If you're describing a bug, tell us what should happen -->\r\n<!-- If you're suggesting a change/improvement, tell us how it should work -->\r\nThose familiar with (but not necessarily contributing to) the Gutenberg project should have a clear picture of a) what Gutenberg does now and how it'll impact them immediately, and b) where Gutenberg is headed.\r\n\r\n## Current Behavior\r\n<!-- If describing a bug, tell us what happens instead of the expected behavior -->\r\n<!-- If suggesting a change/improvement, explain the difference from current behavior -->\r\n- Awareness of the Gutenberg project is small but growing.\r\n- Understanding of Gutenberg's purpose beyond \"the editor is changing\" is rare even among those who are aware of the project.\r\n- Awareness and understanding of the direction of Gutenberg beyond the immediate editor scope is lacking even among those who follow the project closely.\r\n- Awareness of the consequences, immediate and long-term, of Gutenberg on users, administrators, designers, and developers is more or less absent.\r\n- Understanding, even at a general level, of what Gutenberg means for core WordPress features like widgets, fields, metaboxes, shortcodes, etc is close to or equal to nill.\r\n- Lack of an authoritative resource for project information leads to speculation and misunderstandings.\r\n- Lack of shared understanding of project scope and goals leads to a breakdown of communication and escalation of tensions.\r\n\r\n## Possible Solution\r\n<!-- Not obligatory, but suggest a fix/reason for the bug, -->\r\n<!-- or ideas how to implement the addition or change -->\r\nThe Gutenberg project should publish a comprehensive and plain language central resource outlining the project scope, intended direction, realistic and stretch goals, timelines, sprints, and other information directly tied to the project (ideally the README.md file in the project itself.\r\n\r\nCurrently this information exists, in parts, in various [Make posts](https://make.wordpress.org/core/tag/gutenberg/), @mtias' post \"[Gutenberg and the Ship of Thesus](http://matiasventura.com/post/gutenberg-or-the-ship-of-theseus/)\", @m's \"[We Called it Gutenberg for a Reason](https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/)\", in the history of Slack chats, and in pull requests and tickets in this repository. \r\n\r\nDue to the fractured nature of this information it is challenging for anyone to get a clear picture of the entire project, and though @mtias and @m's posts do a good job at explaining the grand vision of the project, they lack concrete plain language breakdowns of the essentials the community need to get a firm understanding of what this project is and where it's headed. They also exist as independent satellites of information circling the project rather than core parts of the project itself.\r\n\r\nA single resource explaining \r\na) why Gutenberg exists (a simplified version of @m's post?), \r\nb) where it's headed (end-goals + grand vision), \r\nc) why the project is currently focussing on the editor, and \r\nd) that the editor focus is the first building block in a larger plan, \r\nwill go a long way in resolving some of the confusion and discomfort felt by all parties involved in these conversations and can serve as a unified resource and reference when questions about issues around metaboxes, locking Gutenberg to the editor, etc arise. \r\n\r\nThe key to success here is a common understanding of where we are, where we're going, and what the terms we use actually mean. That starts with clear language documentation in one easy to access location.  "},"comment":{"url":"https://api.github.com/repos/WordPress/gutenberg/issues/comments/348532714","html_url":"https://github.com/WordPress/gutenberg/issues/3354#issuecomment-348532714","issue_url":"https://api.github.com/repos/WordPress/gutenberg/issues/3354","id":348532714,"user":{"login":"karmatosed","id":253067,"avatar_url":"https://avatars3.githubusercontent.com/u/253067?v=4","gravatar_id":"","url":"https://api.github.com/users/karmatosed","html_url":"https://github.com/karmatosed","followers_url":"https://api.github.com/users/karmatosed/followers","following_url":"https://api.github.com/users/karmatosed/following{/other_user}","gists_url":"https://api.github.com/users/karmatosed/gists{/gist_id}","starred_url":"https://api.github.com/users/karmatosed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/karmatosed/subscriptions","organizations_url":"https://api.github.com/users/karmatosed/orgs","repos_url":"https://api.github.com/users/karmatosed/repos","events_url":"https://api.github.com/users/karmatosed/events{/privacy}","received_events_url":"https://api.github.com/users/karmatosed/received_events","type":"User","site_admin":false},"created_at":"2017-12-01T16:00:10Z","updated_at":"2017-12-01T16:00:10Z","author_association":"MEMBER","body":"Just adding here that wordpress.org/gutenberg and the readme now have updates. Work in progress but a step in right direction."}}
{"actor":{"display_login":"karmatosed"}}