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

Preparation for going public #62

Closed
7 tasks done
semanticphilosopher opened this issue Dec 9, 2024 · 7 comments
Closed
7 tasks done

Preparation for going public #62

semanticphilosopher opened this issue Dec 9, 2024 · 7 comments

Comments

@semanticphilosopher
Copy link
Collaborator

semanticphilosopher commented Dec 9, 2024

Steps we want to do before we make this public

Making public means

  • Rename the repository to something more meaningful
  • upload appropriate parts to hackage

To do this we need to

@semanticphilosopher
Copy link
Collaborator Author

Can we have some suggestions for the repository name (reply to here)?
Am assuming that the hackage name is 'DeltaQ'?

@HeinrichApfelmus
Copy link
Collaborator

The popular choice for package names on Hackage seems to be lower-case: deltaq.

@semanticphilosopher
Copy link
Collaborator Author

The popular choice for package names on Hackage seems to be lower-case: deltaq.

I think that I prefer mixed case over hyphen:

  • DeltaQ
  • over delta-q
  • over deltaq (which might get pronouced as 'del-tak')

HeinrichApfelmus added a commit that referenced this issue Dec 9, 2024
This pull request sets the package versions to `1.0.0.0` and constrains
the versions of dependencies.

Part of #62
@HeinrichApfelmus
Copy link
Collaborator

HeinrichApfelmus commented Dec 11, 2024

Concerning naming choice for the package on Hackage: For the record, there is a StackOverflow answer with the following recommendation:

The package name is an arbitrary identifier […]. Its conventional to make it all lower case with hyphens between words
[…]
Also thanks to the different rules about capital letters in pathnames between Windows and Linux there can be confusion, so its best to stick to lower case.

(Package names will appear in file path names.)

According to Microsoft,

Windows file system treats file and directory names as case-insensitive. FOO.txt and foo.txt will be treated as equivalent files.

All Apple file systems are case-insensitive as well — that includes the old HFS, HFS Journaled, and the current APFS. However, all of them can be instantiated in a case-sensitive variant.

🤓😅

@semanticphilosopher
Copy link
Collaborator Author

ok, I am persuaded - deltaq it is - we can tell people how to pronounce it and why it is the 'change in quality' as part of the package description

@HeinrichApfelmus
Copy link
Collaborator

In order to finalize the decision on names, I have taken the liberty to add pronunciation information in #86.

@HeinrichApfelmus
Copy link
Collaborator

Preparations complete. Engage!

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

2 participants