This repository is for DP0 delegates to contribute and share DP0.2-related materials (e.g., code, analysis tools, tutorials).
Tutorials could be Jupyter Notebooks, or markdown-formatted demonstrations of a DP0-related analysis with command-line tasks or the Portal Aspect.
Please contribute only code that you have verified to run.
All are welcome to become a member of the Delegates or Friends teams of this GitHub Org in order to contribute. Please contact Melissa Graham to be added to a team.
- Make a branch for your work, and name it u/(your github username).
- Add and edit content in your branch until you're ready to share it with everyone.
- Start a new Pull Request (PR) from your branch to main.
- Request a review from another delegate or Rubin staff (safety feature; see below).
- Merge your branch into
main.
Do not commit changes directly to main.
For this repository, all PRs to merge to the main branch must be reviewed.
Reviewers should confirm that the PR is adding or editing only the user's own files in their own folder.
Reviewers should not evaluate the additions or changes: this is not a code review nor a peer review.
These reviews are just a saftey feature to avoid, e.g., this README.md being accidentally deleted (which has happened).
If the PR is deleting a file the reviewer should confirm that the user intended this deletion.
Reviewers can provide comments and approve the PR, but should not edit files, merge, or close the PR.
Any delegate who is unsure about how to request a review for a PR, or needs a reviewer, can ask Melissa Graham.
All materials should be organized into directories.
An example directory is provided as an illustration.
Anyone may make a directory for a specific science topic, a specific tool or type of analysis, etc.
Directory creators should create a README.md file within the directory that identifies them as the directory maintainer and describes the contents of the directory.
Contact the directory creator if you want to contribute content to their directory.
Direct messages between delegates in Community.lsst.org is an appropriate mode of contact.
Please always:
- document your code for non-experts
- provide links to background information
- clear notebook outputs before committing changes
All tutorials should have a header containing:
- the author's name
- the date the tutorial was last tested
- the goals of the notebook
Do not use the Rubin logo in the header unless you are Rubin staff preparing a tutorial under the guidelines of RTN-045. Consider rebranding your notebook with your own institute's logo or a personal logo or picture.
See the example directory for guidance on formatting notebooks and markdown files.
Git is already installed in the Notebook Aspect of the Rubin Science Platform.
The best place to start in the extensive GitHub documentation is with the quickstart setup guide. There is also a GitHub Cheat Sheet of commonly used commands, and a GitHub Glossary.
Git Tutorial for Beginners: Command-Line Fundamentals (a YouTube tutorial that includes git command line basics, but if you are not installing Git, you might want to skip a section of it describing the installation).
What college students should learn about Git (a medium.com article that includes fundamental git concepts and basic git commands).
Phil Marshall's notes on "Getting Started with git and GitHub".
Generating a new SSH key and adding it to the ssh-agent, a guide to setting up git credentials so that you can push changes back to your remote repositories.
See also the GitHub Cheat Sheet provided in this repository. This cheat sheet was developed by Douglas Tucker for the LSST Science Collaborations Stack Club and altered to be appropriate for Data Preview 0 by Greg Madejski.