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

Finalize name and format for manifest #11

Open
zkat opened this issue Nov 9, 2019 · 2 comments
Open

Finalize name and format for manifest #11

zkat opened this issue Nov 9, 2019 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@zkat
Copy link
Contributor

zkat commented Nov 9, 2019

This is an important cross-cutting concern with the Entropic server and we really need to have this hashed out and finalized before we can really commit to a lot of things.

@zkat zkat added the help wanted Extra attention is needed label Nov 9, 2019
@chrisdickinson
Copy link
Collaborator

Naming-wise, I'm okay with Entropic.toml.

Re: the format, we should discuss in our next video meeting so we're all on the same page, then one of us can take a stab at writing a proposal (or editing our existing RFC), to be reviewed/edited in a PR to entropic-dev/entropic's RFCs dir?

@boneskull
Copy link

(drive-by comment follows; I did not check to see if this had been considered)

some of us with case-insensitive filesystems find any sort of capitalization in a filename to be a source of pain when such a file is under version control. if the name needs to change for whatever reason (e.g. somebody manually created entropic.toml).

if you choose to go with capital-E, this isn’t the end of the world, but the client should be able recognize small-e in case someone on apfs/ntfs created it and someone on ext4 needs to consume it. this would hopefully avoid the need to commit a change to the file’s capitalization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants