{"action":"reopened","issue":{"url":"https://api.github.com/repos/skaut/fio-bank-transactions/issues/3","repository_url":"https://api.github.com/repos/skaut/fio-bank-transactions","labels_url":"https://api.github.com/repos/skaut/fio-bank-transactions/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/skaut/fio-bank-transactions/issues/3/comments","events_url":"https://api.github.com/repos/skaut/fio-bank-transactions/issues/3/events","html_url":"https://github.com/skaut/fio-bank-transactions/issues/3","id":253878519,"number":3,"title":"[WordPress Plugin Directory] Request: Fio Bank transactions","user":{"login":"kalich5","id":8988898,"avatar_url":"https://avatars3.githubusercontent.com/u/8988898?v=4","gravatar_id":"","url":"https://api.github.com/users/kalich5","html_url":"https://github.com/kalich5","followers_url":"https://api.github.com/users/kalich5/followers","following_url":"https://api.github.com/users/kalich5/following{/other_user}","gists_url":"https://api.github.com/users/kalich5/gists{/gist_id}","starred_url":"https://api.github.com/users/kalich5/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kalich5/subscriptions","organizations_url":"https://api.github.com/users/kalich5/orgs","repos_url":"https://api.github.com/users/kalich5/repos","events_url":"https://api.github.com/users/kalich5/events{/privacy}","received_events_url":"https://api.github.com/users/kalich5/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-08-30T04:58:41Z","updated_at":"2017-08-31T16:44:48Z","closed_at":null,"author_association":"MEMBER","body":"## We cannot accept your plugin with this name\r\n\r\nYour autogenerated plugin slug was this: fio-bank-transactions\r\n\r\nSince you don’t appear to legally represent that group, we need to change the plugin slug.\r\n\r\nWe recommend the following: sakut-fio-bank-transactions\r\n\r\nA rather lengthy explanation of why is included below, but the tl;dr is that we're no longer accepting plugins that begin with (or are in total) a trademarked product name or term as the name or slug of a plugin (ex: Facebook or google-maps-bathrooms). Nor are we accepting plugins that include the name of another plugin at the beginning of the name/slug (eg: contact-form-7-music), UNLESS you legally represent that service/plugin/theme/etc.\r\n\r\nPlease reply to this email with what slug you’d like. We’ll edit it slug for you.\r\n\r\nYou DO NOT need to edit your code for this. ALL we need is to be on the same page for the plugin slug :)\r\n\r\nIf you DO work for the company, reply to this email and tell us. We can fix your submission.\r\n\r\nHere's the long stuff.\r\n\r\nThe slug for your plugin is generated based on the name you put in your main plugin file, with hyphens inserted in place of spaces. This means if you were to name your plugin \"My Really Cool Cookie Jam\" then your URL on WordPress.org would be http://wordpress.org/plugins/my-really-cool-cookie-jam\r\n\r\nThis becomes a larger issue when plugins use the names of other plugins in their own.\r\n\r\nFor example, if you have written an add-on plugin for WooCommerce, you may not name it \"WooCommerce Improved Product Search\" as that would generate the slug \"woocommerce-improved-product-search\" and that would conflict with the trademark of 'WooCommerce.' That said, it would be acceptable to submit the name \"Woo Improved Product Search\" which would use the slug \"woo-improved-product-search\" (woo not being trademarked you see).\r\n\r\nAs another example, if you have a plugin that integrates a service with a Easy Digital Downloads, you may call it \"My Service Integration for Easy Digital Downloads\", but you may not use \"Easy Digital Downloads - My Service Integration\". Alternately you could use 'EDD My Service Integration' and that too would be permitted.\r\n\r\nNone of this impacts your display name of your plugin. The display name is generated from your readme.txt, and that can be whatever you'd like. Keep in mind, you should use \"My Product for Other Product\" as the description. Consider the example of Keurig. If you made an eco-friendly brew cup, you could market it \"EcoBrew Pod for Keurig\" but you could NOT attempt to market it as \"Keurig EcoBrew Pod.\" The latter implies a direct relationship to Keurig and is actually against the law in some countries.\r\n\r\nYou are more than welcome, and encouraged, to include it in the description of the plugin in the ReadMe.txt file, but it cannot be in the name/slug of the plugin as described above.\r\n\r\nIf you got all the way down here and forgot what to do next, just press reply to this email and tell us what slug you’d like, or if you need to transfer the plugin to a different account. We can fix the plugin."}}
{"actor":{"display_login":"kalich5"}}