I personally opt for having my Github projects match gem names - and so lowercase with hyphens or underscores is how I roll. Thus, simple_csv and imp_uri is what I'd opt for.
Ideally - gem name matches project name matches what goes in the require call. Granted, I've not always been perfect with that - I prefer hyphens instead of underscores (reads nicely with my hyphenated Github username in URLs), but from what I understand that's not best practice unless you're replacing the hyphen with a slash in your require - a valid example is net-ssh and net/ssh. -- Pat On 18/07/2011, at 8:14 PM, thoran wrote: > Hi, > > Anybody have an opinion about this? > > I'm putting up a bunch more code somewhere public, ie. Github, and in > addition to the usual dilemma of naming a project, I have the additional > dilemma of case selection, since part of me wants to use mixed case and part > of me wants to use underscores... > > eg. > > SimpleCSV cf. simple_csv (current) > ImpURI (current) cf. impuri > > Additionally, even if the project name is underscored, the file names may > not---I have been using mixed case for filenames as well. > > So while I realise that there is something of a convention in Rubyland to use > underscores, is there any merit in doing it the way I have been doing it > privately up to now? > > > thoran > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
