Closed kMutagene closed 9 months ago
I agree with renaming the repo to ARCCommander
. But I think we should stick with the tool name arc
for ease of use.
@HLWeil do you intend to publish the API used by the tool as nuget package? If so, i think you should also rename the API namespace. Otherwise it does not really matter.
Can you specify what you mean with API
?
namespace ArcCommander.APIs
or is that basically obsolete now that ARCtrl exists?
or is that basically obsolete now that ARCtrl exists?
That was the plan (at least to my knowledge).
Ah I see. Yeah this definitely won't make it into its own nuget package. It will just be a thin layer combining ARCtrl top-level functions.
Renamed repository to ARCCommander
There are imo too many different naming conventions across our repos. However, some patterns have emerged, which i quite like:
PascalCase for libraries, but with ARC in all caps. examples:
ARCtrl
ARCTokenization
kebap-case for tools examples:
arc-validate
arc-to-invenio
arc-export
arc-from-insdc
so my suggestion would be renaming the API from
ArcCommander
toARCCommander
, and the tool fromarc
toarc-commander
.If these changes are too big, I think we should at least rename the repo accordingly, since the current name -
arcCommander
- does not follow any pattern mentioned above, but is also differing from the current tool name (arc
) and API namespace (ArcCommander
).