apd issueshttps://gitlab.cern.ch/lhcb-dpa/analysis-productions/apd/-/issues2022-05-25T10:36:20+02:00https://gitlab.cern.ch/lhcb-dpa/analysis-productions/apd/-/issues/5Package naming2022-05-25T10:36:20+02:00Eduardo RodriguesPackage namingHi @bcouturi, @cburr, yet another AProds package. I wonder if it would not make sense to have the package/repository name follow a bit more the "conventions" of the other package names, see https://gitlab.cern.ch/lhcb-dpa/analysis-produc...Hi @bcouturi, @cburr, yet another AProds package. I wonder if it would not make sense to have the package/repository name follow a bit more the "conventions" of the other package names, see https://gitlab.cern.ch/lhcb-dpa/analysis-productions? This would then be LbAPData I guess?
You could still keep the subdir as `apt` if you like, or at least have the scripts as `apd` since easy. Though `lb-ap-data` as a script would seem more natural for users, to be more consistent with `lb-ap ...` in `https://gitlab.cern.ch/lhcb-dpa/analysis-productions/lbaplocal`.Chris BurrBen CouturierChris Burr