{"action":"created","issue":{"url":"https://api.github.com/repos/ethereumproject/volunteer/issues/36","repository_url":"https://api.github.com/repos/ethereumproject/volunteer","labels_url":"https://api.github.com/repos/ethereumproject/volunteer/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/ethereumproject/volunteer/issues/36/comments","events_url":"https://api.github.com/repos/ethereumproject/volunteer/issues/36/events","html_url":"https://github.com/ethereumproject/volunteer/issues/36","id":175432545,"number":36,"title":"Rename the github organizations","user":{"login":"sethfork","id":7088679,"avatar_url":"https://avatars.githubusercontent.com/u/7088679?v=3","gravatar_id":"","url":"https://api.github.com/users/sethfork","html_url":"https://github.com/sethfork","followers_url":"https://api.github.com/users/sethfork/followers","following_url":"https://api.github.com/users/sethfork/following{/other_user}","gists_url":"https://api.github.com/users/sethfork/gists{/gist_id}","starred_url":"https://api.github.com/users/sethfork/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sethfork/subscriptions","organizations_url":"https://api.github.com/users/sethfork/orgs","repos_url":"https://api.github.com/users/sethfork/repos","events_url":"https://api.github.com/users/sethfork/events{/privacy}","received_events_url":"https://api.github.com/users/sethfork/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":26,"created_at":"2016-09-07T07:32:34Z","updated_at":"2016-09-28T19:09:12Z","closed_at":null,"body":"## Rename the github orgs\r\n\r\n**If the schism in the Ethereum community wasn’t already confusing enough for outsiders, it’s obscured even further by the names of our two github organizations - and to our own detriment.**\r\n\r\nConsider this scenario:\r\nIf an outside party had just heard of the Ethereum Classic Project and wanted to examine our development efforts, they would instinctively search 'ethereum classic' or 'ethereumclassic' on github. Should they follow that most natural search path, they'd soon find an [organization](https://github.com/ethereumclassic) with exclusively marketing-focussed repos. Seeing no evidence of actual development; they would then naturally conclude that our project is a sham, which is as [certifiably false](https://github.com/ethereumproject) as it is insulting to the outstanding work you've all done thus far.\r\n\r\nThe effects of these conclusions stand in direct opposition to the best interest of our community. We’ll miss out on opportunities for bringing in contributors, community members, and third parties that could potentially be valuable additions to our ecosystem.\r\n\r\nIf unrealized potential value-add isn’t enough cause for concern; I’d like to also point out that this misrepresentation is neither new nor self-contained. Given the (rebellious) nature of our project, we have enemies with both the ideological and financial motivations for invalidating our cause and efforts. The most common attack by non-subscribers is that we have “_no devs_” and that we haven’t accomplished much beyond the creation of a logo and some nice words about immutability. With the spotlight on us right now, we can’t afford to lend any fuel to this absurd attack.\r\n\r\n**In the interest of fortifying our outward-facing brand and more accurately representing the talent and persistence of our contributors; I propose we rename our github organizations.**\r\n\r\n\r\n# The proposal:\r\n\r\n### 1. Rename the [ethereumclassic](https://github.com/ethereumclassic) github organization to something more indicative of it’s purpose as a hub for marketing resources **OR** transfer all it’s repos to the [ethereumproject](https://github.com/ethereumproject) organization.\r\n\r\n### 2. Change the name of the [ethereumproject](https://github.com/ethereumproject) organization to ‘ethereumclassic’\r\n\r\n## To prepare for the change, developers should: \r\n\r\n- Point to the new remote origin on any local code checkouts.\r\n- Validate any 3rd party webservice integrations. (Repo owners)\r\n- Validate any OAuth apps (Project owners)\r\n\r\nTo help developers prepare for the change we suggest an announcement be made one week prior to the change on all channels, e.g., Github, Slack, IRC, Telegram, Reddit, etc. This should ensure each contributor has enough time to make any necessary changes and development efforts are left unhindered.\r\n"},"comment":{"url":"https://api.github.com/repos/ethereumproject/volunteer/issues/comments/250268435","html_url":"https://github.com/ethereumproject/volunteer/issues/36#issuecomment-250268435","issue_url":"https://api.github.com/repos/ethereumproject/volunteer/issues/36","id":250268435,"user":{"login":"sethfork","id":7088679,"avatar_url":"https://avatars.githubusercontent.com/u/7088679?v=3","gravatar_id":"","url":"https://api.github.com/users/sethfork","html_url":"https://github.com/sethfork","followers_url":"https://api.github.com/users/sethfork/followers","following_url":"https://api.github.com/users/sethfork/following{/other_user}","gists_url":"https://api.github.com/users/sethfork/gists{/gist_id}","starred_url":"https://api.github.com/users/sethfork/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sethfork/subscriptions","organizations_url":"https://api.github.com/users/sethfork/orgs","repos_url":"https://api.github.com/users/sethfork/repos","events_url":"https://api.github.com/users/sethfork/events{/privacy}","received_events_url":"https://api.github.com/users/sethfork/received_events","type":"User","site_admin":false},"created_at":"2016-09-28T19:09:12Z","updated_at":"2016-09-28T19:09:12Z","body":"![screenshot 2016-09-28 13 19 58](https://cloud.githubusercontent.com/assets/7088679/18924586/b9ad4e72-857e-11e6-9fd4-424ab1e4fb4f.png)\r\n\r\n-\r\n\r\nAt some point, we're going to have to make this switch. The counterintuitive naming convention presents an unforced roadblock in the growth of our ecosystem by creating an unnecessary point of friction in our developer acquisition flow. \r\n\r\n-\r\n\r\nGiven the current workload of each of our contributors; we should not be doing anything that makes it more difficult for developers to discover us and get involved - especially not out of spite for an incidental battle. Squatting on the ethereumproject org name provides little to no long-term benefit outside of the pride we might get from our defiance.\r\n\r\nThe immutable truth of our blockchain speaks for itself. The resolve of our community when it's values were challenged -- the impressive work we've done since -- speaks for itself. But that's all been under the \"Ethereum Classic\" moniker. We can continue to hardline the claim to \"Ethereum Vanilla\" to our own detriment; or we can own \"Ethereum Classic\" and start leveraging the growing power of the brand that represents the movement we're proud to be a part of."}}
{"actor":{"display_login":"sethfork"}}