Participation guidelines

All DP0 delegates must:

Rubin data rights policy

Rubin data rights are required to hold an account in the Rubin Science Platform (RSP).

RSP accounts are not transferable and delegates must not share their password with others.

Who has Rubin data rights? All scientists and students affiliated with an institution in the US and Chile have data rights, as well as the international scientists and students whose names appear on the list of international data rights holders.

For more information about data rights, please refer to the Rubin Observatory Data Policy.

Anyone with uncertainty about their Rubin data rights can contact Melissa Graham at or with a direct message in the Rubin Community Forum.

Risks and caveats


DP0 delegates are being given access to a shared-risk developmental version of the RSP and the accompanying documentation, and should understand the risks and caveats.

Code of conduct

Review the Rubin Code of Conduct (CoC) at

To summarize the CoC:

  • Bullying and harassment will not be tolerated.

  • Research inclusion and collaborative work must not be impeded by poor behavior.

  • Discussion should be constructive and civil at all times.

If you experience or witness a violation of the CoC in the Community Forum, please flag the post. Forum moderators will handle the issue from there. Please note that there are a few reasons why posts get flagged, and CoC violations are only one of them. Here are some guidelines on how to react if your post is flagged.

If you experience or witness a violation of the CoC in another venue, please reach out to Sandrine Thomas, one of the Rubin Observatory Workplace Culture Advocates who has agreed to be the contact person for DP0 delegates.

Citation policies

Cite the DESC’s publications for the DC2 simulated data set, which is being used for DP0.1 and DP0.2. If you publish work based on the DP0.1 or DP0.2 data set, you must cite “CosmoDC2: A Synthetic Sky Catalog for Dark Energy Science with LSST” (Korytov et al 2019), “The LSST DESC DC2 Simulated Sky Survey” (arXiv:2010.05926), and potentially “DESC DC2 Data Release Note” (arXiv:2101.04855) if you used the Object or Truth-Match tables, which are presented in that release note.

Consider extending co-authorship or acknowledgments to DP0 delegates whose work you used, or who have helped you, as appropriate. Delegates are encouraged to openly share their DP0-related work and/or code during Virtual events, via the Community Forum, and in the shared GitHub shared repositories delegate-contributions-dp02 or delegate-contributions-dp03. This is intended to facilitate collaboration, which requires proper acknowledgments. For example, if you use another delegate’s Jupyter Notebook as a starting point for your Notebook, give credit to that person at the top of your Notebook. If another delegate’s work contributed to your DP0-related publication, consider including an acknowledgment, citing their relevant publications, and/or extending co-authorship, as appropriate.

Be aware that DP0-related work done by Science Collaboration (SC) members might be subject to the publication policies of their Science Collaborations. Significant overlap between the DP0 working groups and SC working groups, committees, or task forces is to be expected, because the science goals of DP0 and the SCs overlap (i.e., preparing for LSST). Each SC has their own policies regarding collaboration, co-authorship, and publications and delegates are responsible for following the policies of their SCs, if and when they pertain to their DP0-related work. If cases of real or perceived conflict between the general open nature of DP0 collaboration and any SC policies arise, delegates are expected to understand and abide by their SC’s policies. In other words, the fact that work is DP0-related does not nullify any SC policies that might apply to a delegate’s work. Example scenarios might include sharing SC-developed software with delegates who are not members of that SC, or using code or analysis results collaboratively by delegates in a SC publication.

Note that the Rubin Observatory Publication Policy does not apply to publications by delegates that are based on their DP0 work.