# \#dm-policy **URL:** https://www.rubin.community/tag/dm-policy/107.md [Latest](https://www.rubin.community/latest.md) · [Categories](https://www.rubin.community/categories.md) · [Tags](https://www.rubin.community/tags.md) --- ## [Scheme of the LSST Unique Identifier (Object ID)](https://www.rubin.community/t/scheme-of-the-lsst-unique-identifier-object-id/11974)
**Author:** [@lionandjelka](https://www.rubin.community/u/lionandjelka)\ **Replies:** 3\ **Last updated:** [August 13, 2026, 5:06pm UTC](https://www.rubin.community/t/scheme-of-the-lsst-unique-identifier-object-id/11974 "2026-08-13T17:06:06Z")
Hi. Could you please describe how the LSST Unique Identifiers (e.g. Object ID) are constructed? It was requested by a journal Reviewer of one DP1 related paper. Thank you. --- ## [A memo for the science community regarding DM-provided support](https://www.rubin.community/t/a-memo-for-the-science-community-regarding-dm-provided-support/4422)
**Author:** [@leanne](https://www.rubin.community/u/leanne)\ **Replies:** 1\ **Last updated:** [January 29, 2021, 4:04pm UTC](https://www.rubin.community/t/a-memo-for-the-science-community-regarding-dm-provided-support/4422 "2021-01-29T16:04:32Z")
Summary: The DM team provides support for use of the Rubin Observatory data products, pipelines, and services on a best-effort basis during Construction. This support will henceforth be done via the Community.lsst.org Fo… --- ## [Clarification on the state of DM's license and copyright policies](https://www.rubin.community/t/clarification-on-the-state-of-dms-license-and-copyright-policies/185)
**Author:** [@jsick](https://www.rubin.community/u/jsick)\ **Replies:** 14\ **Last updated:** [January 20, 2016, 4:27pm UTC](https://www.rubin.community/t/clarification-on-the-state-of-dms-license-and-copyright-policies/185 "2016-01-20T16:27:14Z")
I'm writing a new Python package (not associated with the stack) and I'd like to use our current best-practices for declaring copyright and license information. RFC-45 provides some guidance on how to include a copyright… --- ## [Please ensure the results of RFCs are clearly documented](https://www.rubin.community/t/please-ensure-the-results-of-rfcs-are-clearly-documented/282)
**Author:** [@swinbank](https://www.rubin.community/u/swinbank)\ **Replies:** 23\ **Last updated:** [October 14, 2015, 6:04pm UTC](https://www.rubin.community/t/please-ensure-the-results-of-rfcs-are-clearly-documented/282 "2015-10-14T18:04:37Z")
This came up during the recent stack bootcamp, but I think it's worth calling out specifically here: Over the last several months, we've adopted (or considered adopting) several changes to our development practices: Py… --- ## [Obsolete packages or code in the LSST stack](https://www.rubin.community/t/obsolete-packages-or-code-in-the-lsst-stack/283)
**Author:** [@isullivan](https://www.rubin.community/u/isullivan)\ **Replies:** 1\ **Last updated:** [October 8, 2015, 8:52pm UTC](https://www.rubin.community/t/obsolete-packages-or-code-in-the-lsst-stack/283 "2015-10-08T20:52:52Z")
How do we handle obsolete code and packages in the LSST stack? As an example, during the October 2015 "boot camp", we decided to update references throughout the stack to boost::unordered\_map that are now included in … --- ## [Current DM Code Review Process?](https://www.rubin.community/t/current-dm-code-review-process/160)
**Author:** [@hsinfang](https://www.rubin.community/u/hsinfang)\ **Replies:** 2\ **Last updated:** [September 8, 2015, 5:57pm UTC](https://www.rubin.community/t/current-dm-code-review-process/160 "2015-09-08T17:57:05Z")
What is the current policy for code review? I see this Trac document from Confluence DM Developer Standards and Policies, but it is noted as "TO BE UPDATED" in the section of "Needs Major Revision or Obsolete."