Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readme.md and README.md conflict #35

Open
tim-moody opened this issue Oct 6, 2020 · 5 comments
Open

readme.md and README.md conflict #35

tim-moody opened this issue Oct 6, 2020 · 5 comments

Comments

@tim-moody
Copy link

Having both readme.md and README.md causes errors on case insensitive operating systems like windows.

@georgejhunt
Copy link
Contributor

georgejhunt commented Oct 6, 2020 via email

@tim-moody
Copy link
Author

@holta
Copy link
Member

holta commented Oct 8, 2020

Certainly older docs need to be labeled as such, and duplicate names avoided!

But regarding PR #37, personally I find it unfortunate when design docs hinting at structure/motivation/inspiration are hidden from view. From a docs directory especially...as even historical such docs can greatly help maintainers, new map devs and other community enthusiasts...understanding the lay-of-the-land here (i.e. the years of hard work @georgejhunt has put into this, even if there's no map of the map just yet!)

At minimum we really should try to preserve a prominent link to... https://github.com/iiab/maps/blob/ebcb43e54979023b33720f51dc3b07c6673c7e42/docs/readme.md
...being that we're in the library/cartography business after all ;)

@holta
Copy link
Member

holta commented Oct 8, 2020

To that end (software archeology/anthropology was my dad's career after all, and how to elicit understanding of legacy software across its life cycles) I've added a link here:

https://github.com/iiab/iiab/wiki/IIAB-Maps#links--advanced-topics

Probably we can close this tkt now.

@tim-moody
Copy link
Author

there was no need to remove readme.md; a rename would have been sufficient. or do nothing if you prefer software archeology/anthropology to enabling people with case insensitive file systems to work on this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants