rename repo? about distance-direction-addin-dotnet

[mfunk]

OK. Going to rename this repo, following management direction. Tomorrow morning I will rename this repo to distance-direction-addin-dotnet.

@kgonzago
@csmoore
@ACueva
@lfunkhouser
@topowright

If you have forked this repo and have changes, please send a Pull Request before tomorrow 8 AM Pacific time.

Also @jmccausland can we remove dead branches for this repo as well?

[jmccausland]

@mfunk I removed what I could. I have some unfinished branches but I'll revive them on the new repo name

[mfunk]

@jmccausland Thanks. I would think that as long as the branch is synced on the ArcGIS repo, then your work is safe. Seems like it should be easy. Any thoughts @csmoore?

[jmccausland]

@mfunk @csmoore I've zipped them up, just in case.

[csmoore]

@mfunk - I haven't been completely following/understanding the rename repo threads, but I've never personally encountered any issues with renaming a repo and needing to refork/delete forks - where did you get this guidance. For example, I was still using the old vehicle-commander name for a long time in my fork and don't recall any issues: https://github.com/csmoore/vehicle-commander (vs. https://github.com/Esri/vehicle-commander-java )

[jmccausland]

google, which never lies, =)

[mfunk]

@jmccausland so trusting. 😈

@csmoore Guidance on renaming the former MA project came from the 'big office team'. For example "Geodesy and Range" should be "Distance and Direction", and "Coordinate Tool" should be "Coordinate Conversion". As window title bar, so repository.

[csmoore]

@mfunk - I wasn't questioning the specific names picked, but asking about the guidance to delete forks/branches/etc. after a rename - if that makes sense

[mfunk]

If we are working off of feature branches, and the feature that was being worked on is now merged into the parent branch, and it's no longer needed, it should removed as to not confuse users with a large branch pick-list. Learned that in the GitHub class. There's a command that is supposed to do that (something like 'prune') ... delete branches that have been merged and have no changes pending.

[csmoore]

@mfunk - thanks for the clarification - I incorrectly thought this request for everyone to delete forks had something to do with the rename.

If the question was about deleting merged/unused forks - that is a good practice - the number of branches can quickly multiply and become unwieldy (I thought GitHub even asked you if you want to do this during the merge if using the web page)

[mfunk]

Done.