{"action":"created","issue":{"url":"https://api.github.com/repos/dereckson/wp-cli-polylang/issues/5","repository_url":"https://api.github.com/repos/dereckson/wp-cli-polylang","labels_url":"https://api.github.com/repos/dereckson/wp-cli-polylang/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/dereckson/wp-cli-polylang/issues/5/comments","events_url":"https://api.github.com/repos/dereckson/wp-cli-polylang/issues/5/events","html_url":"https://github.com/dereckson/wp-cli-polylang/issues/5","id":163021601,"number":5,"title":"future of wp-cli-polylang","user":{"login":"diggy","id":1071337,"avatar_url":"https://avatars.githubusercontent.com/u/1071337?v=3","gravatar_id":"","url":"https://api.github.com/users/diggy","html_url":"https://github.com/diggy","followers_url":"https://api.github.com/users/diggy/followers","following_url":"https://api.github.com/users/diggy/following{/other_user}","gists_url":"https://api.github.com/users/diggy/gists{/gist_id}","starred_url":"https://api.github.com/users/diggy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/diggy/subscriptions","organizations_url":"https://api.github.com/users/diggy/orgs","repos_url":"https://api.github.com/users/diggy/repos","events_url":"https://api.github.com/users/diggy/events{/privacy}","received_events_url":"https://api.github.com/users/diggy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-06-29T20:41:55Z","updated_at":"2016-06-30T11:54:27Z","closed_at":null,"body":"Hi,\r\n\r\nI'd like to start a discussion about the future of this package with the people involved, some more than others: @dereckson @Chouby @nwoetzel @danielbachhuber \r\n\r\nThe WP-CLI [package index](https://github.com/wp-cli/package-index) contains an entry pointing to this repo, but the code hasn't been updated in quite a while. I recently submitted a [PR](https://github.com/nwoetzel/wp-cli-polylang/pull/1) to @nwoetzel 's fork (resolving issue #4 in this repo) as that fork was more up-to-date than the source.\r\n\r\nWe might start using Polylang frequently at work, and a decent CLI component is indispensable to make the plugin fit in our workflow. I recently spent some time on a serious rewrite of `wp-cli-polylang`, from the ground up actually, and currently at a loss on how to proceed, hence this thread.\r\n\r\nSeveral options come to mind: I could release the package independently, and add a new entry to the package index. This is not desirable, as expressed by @danielbachhuber in a short conversation we had in the WP Slack #cli channel. See also [this post](https://runcommand.io/2016/06/26/my-condolences-youre-now-the-maintainer-of-a-popular-open-source-project/).\r\n\r\nI could submit a PR against the original package (this repo), but then @dereckson would have to agree with the overhaul, for starters. It could also break stuff for people depending on the package. Furthermore, for me, having to submit PRs and wait for merges all the time feels like inefficient and would seriously impede a healthy workflow.\r\n\r\nOther options include giving me (and potentially others) push access to this repo (which might not be desirable), transferring the repo to me (if there is no time for or interest in maintaining the package), or transferring the repo to @Chouby (if interested), the author of the Polylang plugin, so the package can be maintained in the context of the Polylang [organization](https://github.com/polylang) here on Github.\r\n\r\nLong story short, not really sure what to do :) Looking forward to your thoughts and opinions!"},"comment":{"url":"https://api.github.com/repos/dereckson/wp-cli-polylang/issues/comments/229637108","html_url":"https://github.com/dereckson/wp-cli-polylang/issues/5#issuecomment-229637108","issue_url":"https://api.github.com/repos/dereckson/wp-cli-polylang/issues/5","id":229637108,"user":{"login":"danielbachhuber","id":36432,"avatar_url":"https://avatars.githubusercontent.com/u/36432?v=3","gravatar_id":"","url":"https://api.github.com/users/danielbachhuber","html_url":"https://github.com/danielbachhuber","followers_url":"https://api.github.com/users/danielbachhuber/followers","following_url":"https://api.github.com/users/danielbachhuber/following{/other_user}","gists_url":"https://api.github.com/users/danielbachhuber/gists{/gist_id}","starred_url":"https://api.github.com/users/danielbachhuber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danielbachhuber/subscriptions","organizations_url":"https://api.github.com/users/danielbachhuber/orgs","repos_url":"https://api.github.com/users/danielbachhuber/repos","events_url":"https://api.github.com/users/danielbachhuber/events{/privacy}","received_events_url":"https://api.github.com/users/danielbachhuber/received_events","type":"User","site_admin":false},"created_at":"2016-06-30T11:54:27Z","updated_at":"2016-06-30T11:54:27Z","body":"> I'm also not sure if the package should be incorporated in the PLL plugin, or be available as a separate package installable through WP-CLI.\r\n\r\nI don't have a strong preference one way or the other. Plugins sometimes package WP-CLI commands if the plugin developer thinks its something they want to build and maintain. In this case, I think it's perfectly reasonably that you guys maintain WP-CLI commands for Polylang, given you're interest in having them available."}}
{"actor":{"display_login":"danielbachhuber"}}