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

Namespace #45

Closed
vchekan opened this issue Nov 2, 2018 · 3 comments
Closed

Namespace #45

vchekan opened this issue Nov 2, 2018 · 3 comments

Comments

@vchekan
Copy link

vchekan commented Nov 2, 2018

Shall root namespace be jet.equinox to avoid potential collisions?

@bartelink
Copy link
Collaborator

Good question.

  • While a lot of Jet-sponsored engineering resources and time (and, specifically, on master at the present time, even more of non Jet-sponsored engineering time) has gone into this work as a whole, the code is purposefully not Jet-specific or proprietary in nature
  • There are no Equinox.* NuGets which for me is arguably a defacto name reservation (@troykershaw maybe that should happen before opening the repo?)
  • The medium to long term goal of this work, for me is anything but Jet - for instance it could be used with SSS without a crazy amount of work.

I've tried to cover this in the Contributing section of the README.

Thoughts ?

@bartelink
Copy link
Collaborator

bartelink commented Nov 28, 2018

@troykershaw to verify; informally it has been decided that the general principle is that repo name should match nuget name should match namespace where possible. Troy, can you close to ack ?

@bartelink
Copy link
Collaborator

Closing due to inactivity. Please re-open if desired.

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