naming convention for package zoo

[cbeleites]

How do we name the new packages?

• @GegznaV proposes to go short names:

  I would prefer to have some shorter names as hy.import, hy.manager, hy.plot, hyperImport, hyperWrangler hyperPlot, etc.

  I agree => (+3)

Does anyone have a strong opinion on

• CamelCase (hyperChemoBridge) vs.
• dots (hyperSpec.dplyr or hy.dplyr) (+3) vs.
• underscores (hy_io_spc, hy_dplyr) not possible according to @GegznaV

=> please edit this comment and +1 behind your choice.

Bryan: no strong opinion as to name convention, you might consider hyS.X (add an "S") rather than just hy.X so that users might see that it goes with hyperSpec if they are browsing around.

[eoduniyi]

I agree with @bryanhanson: I think it should be more than just hy.X as there is potential confusion between the hyperSpec universe and the Hy programming language, the interesting Hy.ly startup, or the English phonetic abbreviation hy.

I have a preference for the following: hyS.X,hySp.X (could be confused with this or this), or my favorite hySpc.X.

# Install and load hyperSpec bridge packages
install.packages("hySpc.import") # this may get installed/loaded with library(hyperSpec) as default
library(hySpc.import)
.
.
.
# Import/read Kaiser file
hySpc.import::Kaiser()

[bryanhanson]

hySpc.X is Excellent!

[GegznaV]

I'd prefer to use all non-capital letters. Of course, with RStudio's auto-complete possibilities it is not a big problem, but still...
hy.etc was just an example of an idea as some functions, e.g., hyperSpec::hy.getOption() and chk.hy(), use this abbreviation.

[ximeg]

@eoduniyi you've done some legwork 😄 hySpc.<X> is a great suggestion, but I agree with Vilmantas, that lower-case would be easier to type: hyspc.<X>.

[ximeg]

Naming convention for the package zoo

[ximeg]

Together we agreed on hySpc.<x> naming. The capitalization is there to be consistent with hyperSpec, where S is capitalized.

[bryanhanson]

Closing as this has been resolved.