I can't remember if we discussed this or not. It's been on the nu google group once or twice...
What kind of naming conventions do we want to push for the packages themselves?
Examples of differing case and "." versus "-"
My preference is the first. All lower case names, and if someone decides to capitalize, PLEASE make sure that we are not case sensitive. It doesn't make for a good time for the user. For example, with ruby gems if you were to "gem install magnum"
it would error, but if you type "gem install Magnum" it works perfectly. I'm not picking on anyone because we were learning. The convention for ruby gems is "lower-case."
My personal preference is "lower.case" - We are DOT net, so we should use dots. :D
We should also talk about version conventions.
With versioning, I want to see the version of the package be the same as the assembly reference. Four octets. 0.0.0.0. It keeps things easy and when someone opens up the assembly to find out what the references are, they get the four octets for the version.
They could take that and specifically
Add-Reference log4net 184.108.40.206
If the log4net project uses just the first three to talk about their versioning (1.2.9) that is fine, but when I'm trying to add a reference, I want to go to the source of truth for the version and that is the assembly version. So mimicking that with
versioning conventions will be awesome. It keeps me from having to keep it in my head that "this project uses 3 and this other project uses 2 octets" because all projects really have four octets whether they decide to use them or not.