-
Notifications
You must be signed in to change notification settings - Fork 25
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
name of module #9
Comments
Aligning with the .NET https://github.com/dotnet/corefx/tree/master/src/System.Diagnostics.DiagnosticSource that has exact the same purpose. |
bus is fun though |
I think it'd be great to choose a name which reflects the functionality clearly - it makes advocating in the community for this that much easier 馃槃 . With that in mind, 'diagnostic' is a long word to say and type, and the meaning of 'source' in this context isn't that clear. Is there a reason to align with .NET on the name? And why in fact is the .NET module called DiagnosticSource? Thanks! |
Conclusion in another thread was to rename the repo to |
Can we clarify why we're calling it
node-diagnostic-source
?How about
node-trace-channel
ornode-trace-bus
馃殞 ? "bus" is fun in my opinion 馃槅The text was updated successfully, but these errors were encountered: