Closed anselmbradford closed 10 years ago
:thumbsup:
If you do this, make sure all documentation that points here is updated, unless GitHub auto-redirects old name to new name, which would be awesome.
I tried the git rename thing and it didn't work. So I cloned it and created a new repo https://github.com/codeforamerica/OpenReferral
Everything is there except the issues from the wiki, but I'll either replicate them or resolve them.
sophia
On Tue, Feb 25, 2014 at 8:46 AM, Moncef Belyamani notifications@github.comwrote:
If you do this, make sure all documentation that points here is updated, unless GitHub auto-redirects old name to new name, which would be awesome.
Reply to this email directly or view it on GitHubhttps://github.com/codeforamerica/human_services_finder/issues/317#issuecomment-36028546 .
[image: :thumbsup:]
@spara. You don't rename a repo on GitHub with git. You do it from the repo's admin interface on GitHub.com. Git would then be used to rename the remote on your local machine to point to the new name on GitHub.
I can take care of renaming this repo once I've researched the best way to do it. Also, thinking about the name some more, maybe "ohana-web-search" might be more descriptive and generic. "Connect" might not be adopted by all cities.
FYI right now it looks like DC is going with 'DC Service Connect'
On Tue, Feb 25, 2014 at 1:59 PM, Moncef Belyamani notifications@github.comwrote:
@spara https://github.com/spara. You don't rename a repo on GitHub with git. You do it from the repo's admin interface on GitHub.com. Git would then be used to rename the remote on your local machine to point to the new name on GitHub.
I can take care of renaming this repo once I've researched the best way to do it. Also, thinking about the name some more, maybe "ohana-web-search" might be more descriptive and generic. "Connect" might not be adopted by all cities.
Reply to this email directly or view it on GitHubhttps://github.com/codeforamerica/human_services_finder/issues/317#issuecomment-36044229 .
Ahh, I thought you would do it on the command line from the remote.
On Tue, Feb 25, 2014 at 10:59 AM, Moncef Belyamani <notifications@github.com
wrote:
@spara https://github.com/spara. You don't rename a repo on GitHub with git. You do it from the repo's admin interface on GitHub.com. Git would then be used to rename the remote on your local machine to point to the new name on GitHub.
I can take care of renaming this repo once I've researched the best way to do it. Also, thinking about the name some more, maybe "ohana-web-search" might be more descriptive and generic. "Connect" might not be adopted by all cities.
Reply to this email directly or view it on GitHubhttps://github.com/codeforamerica/human_services_finder/issues/317#issuecomment-36044229 .
As far as the actual name used goes, my 2cents would be to keep it short and memorable. I don't think the project needs to be something generic necessarily, as we can't stop cities from naming their projects anything they want (incl. the API name), so I lean toward a name that fits with the current implementation of this repo and ties it to the "ohana family," since this repository kind of acts like an advertising instance for both the capabilities of the Ohana API project and its current implementation.
It looks like GitHub automatically redirects from the old name to the new name, so we don't have to worry about tracking down all links that point to the old name.
I would approach naming this repo like naming a method. I think descriptive is more important than short and memorable. Developers are our target audience, so it should be clear what the app does. "ohana-connect" does not convey much, whereas "ohana-web-search" does.
Unless I hear differently, I'll go ahead and rename it to ohana-web-search.
I just renamed it to ohana-web-search. We can always rename it again if there is strong opposition.
Since we have
ohana-api
andohana-api-admin
let's consider changing this repo toohana-connect
to fit with the software family. What say you @monfresh @spara