{"action":"opened","issue":{"url":"https://api.github.com/repos/yiisoft/yii-core/issues/129","repository_url":"https://api.github.com/repos/yiisoft/yii-core","labels_url":"https://api.github.com/repos/yiisoft/yii-core/issues/129/labels{/name}","comments_url":"https://api.github.com/repos/yiisoft/yii-core/issues/129/comments","events_url":"https://api.github.com/repos/yiisoft/yii-core/issues/129/events","html_url":"https://github.com/yiisoft/yii-core/issues/129","id":394890812,"node_id":"MDU6SXNzdWUzOTQ4OTA4MTI=","number":129,"title":"Yii3 Dev organization","user":{"login":"machour","id":304450,"node_id":"MDQ6VXNlcjMwNDQ1MA==","avatar_url":"https://avatars2.githubusercontent.com/u/304450?v=4","gravatar_id":"","url":"https://api.github.com/users/machour","html_url":"https://github.com/machour","followers_url":"https://api.github.com/users/machour/followers","following_url":"https://api.github.com/users/machour/following{/other_user}","gists_url":"https://api.github.com/users/machour/gists{/gist_id}","starred_url":"https://api.github.com/users/machour/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/machour/subscriptions","organizations_url":"https://api.github.com/users/machour/orgs","repos_url":"https://api.github.com/users/machour/repos","events_url":"https://api.github.com/users/machour/events{/privacy}","received_events_url":"https://api.github.com/users/machour/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-30T18:10:42Z","updated_at":"2018-12-30T18:10:42Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Hi there,\r\n\r\nThe team have been on vacations the past few days, and it was the perfect occasion for me to discover Yii3 state in peace (without big changes happening). That wasn't enough time to fully dive into all the changes, but enough to have a fair grasp, with the awesome help of @hiqsol 🙏 \r\n\r\nI'd like to propose some ideas regarding how Yii 3 development is organized, because from my outside point of view, the current workflow (or lack of it) is one of the main blocking point if we want to get Yii 3 out.\r\n\r\nMaybe something like this is already in use, and I've missed it, but if it doesn't, then I personally think it's a must.\r\n\r\n\r\n### Tests\r\n \r\nAs you may have noticed, I've been working with @FabrizioCaldarelli on fixing travis setups, tests & various breakages in code. Figured out it will be a good way to get started and see what changed.\r\n\r\nYou can see the progress here: https://github.com/yiisoft/docs/blob/master/000-packages.md#yii-framework (merging https://github.com/yiisoft/docs/pull/9 would make it more accurate)\r\n\r\nI personally think that turning **and keeping** all Travis badges green should be the first focus of the Team as it gets back to working on Yii. \r\n\r\n#### Proposed solution:\r\n\r\nFix them all in a collective effort, then enforce the following rules:\r\n\r\n - Every PR merged in a repo, should have passed the travis build for that repo\r\n \r\n - If the PR introduce breakages in other packages, it should clearly mention it, along with instructions\r\n on how to fix them (if the author don't have the time to fix other packages).\r\n \r\nWe also need to come up with a way to trigger a travis build of all projects once in a while.\r\n\r\n### Centralize Discussions\r\n\r\nThere are quiet a few important points being discussed for Yii3 development, sometimes on Slack, sometimes it's sparks on the 14th comment of a merged PR, .. The big picture have been split along with the packages, and that's not good project-wise.\r\n\r\n#### Proposed solution:\r\n\r\nCreate a `yiisoft/rfcs` or `yiisoft/todo` repo and open an issue in it for every important decisions/discussion currently happening.\r\n\r\nWe would then either continue the dialog in the newly created issue, or just add a link to point at where the discussion is taking place.\r\n\r\nOnce concensus have been reached (when it's needed), the issue would be updated with the final decision, making it easier to know that there's a final word, and what that word is.\r\n\r\n### Project Management\r\n\r\nIt's currently unclear who's working on what, and where the global situation at.\r\n\r\n#### Proposed solution:\r\n\r\nSet up GitHub Projects on the `rfcs` repo mentioned above, and use it to schedule some kind of roadmap for development.\r\n\r\nColumns would go something like:\r\n\r\n- `Discussing` : Decisions currently being discussed\r\n- `Todo`: Decision have been made, awaiting PR\r\n- `Ready` : Task completed & PR up for reviews / feedback\r\n- `Spreading` : PR merged but other repos needs updates\r\n- `Done` : The change have been made, and all other packages are adapted.\r\n- `Postponed` : Discussed & approved, but to be implemented after 3.0.0\r\n\r\n2019 looks like a promissing year for the framework!"}}
{"actor":{"display_login":"machour"}}