there are three “special” teams in the LSST Github org (though all our teams are special to me, etc etc)
- Data Management
- DM Externals
- DM Auxilliaries
These are used in the release process in the following way:
- Data Management repos that are a dependency of lsst_distrib are tagged with the bare release version, eg. ‘14.0’
- ‘DM Externals’ that are a dependency of lsst_distrib are tagged with ‘v14.0’ (so that eups does not show it and confuse people who want the upstream semantic versioning to show up)
- ‘DM Auxilliaries’ are repos that we want to snapshot as part of a relase (eg sdss_demo) but are not an eups dependancy of lsst_distrib
When you create a new repo that is part of the stack, please take a moment to consider if they should belong to one of the above teams.
Below is a list of team-less repos if anyone made theirs team-less by mistake. I am thinking we should have a team like ‘DM Other’ to triage those into, unless anybody thinks it would be confusing.
meas_mosaic git-lfs-testing git-lfs-more-testing miniconda2 LDM-230 LDM-129 pipelines_lsst_io validation_data_decam validation_data_hsc LDM-472 lsst_ci syseng_db lsst_qa jointcal_cholmod deploy_testing_distrib miniconda3 pybind11 ephem sims_catalogs sims_skybrightness_pre sims_integrated sims_survey_fields LDM-493 meas_extensions_convolved starlink_ast display_ginga community_contactdb_merge qserv_testscale os-docker-registry os-qserv-build-node ndarray-1 lacquer pandas suit-onlinehelp sims_featureScheduler LDM-148 verify_metrics obs_comCam LDM-512 LDM-294 obs_ctio0m9 LDM-502 LDM-503 all_sky_phot LSE-63 meas_extensions_astrometryNet shebangtron LDM-522 LDM-482 libyaml LSE-61 LDM-542 LDM-552 LDM-534 LDM-553 LDM-556 LDM-555 marshmallow ci_ctio0m9 LDM-554 daf_io repos ap_verify_hits2015 treecorr LDM-563 LDM-564 pytest pytest_flake8 python_mccabe pyflakes pycodestyle flake8 LDM-572 pytest_session2file pytest_xdist python_execnet pytest_forked display_matplotlib python_coverage pytest_cov pep8_naming