-
Notifications
You must be signed in to change notification settings - Fork 71
Home
Welcome to the Jdaviz wiki!
"Seems to work well once I read the docs." -- Kyle C.
"This is like DS9, but better." -- A graduate student
"Wait, how many people actively develop this tool?" -- A graduate student
"I can't believe this exists, and I can't believe I didn't know about this. You've got to tell everyone." -- A graduate student
"This is going to be so useful for my work that I'm almost sick to my stomach." -- Anonymous
"This hour [learning about Jdaviz] just saved me 30 hours of futzing with Python, this is great." -- Anonymous
"Wow!" -- Several MUG members upon seeing Jdaviz working in MAST
"This is so much nicer than DS9!" ⭐⭐⭐⭐⭐ -- Dan W. (and others)
"Why?????" -- Jonathan A. (on discovering Cubeviz can play Baby Shark GIF)
"Got it to work — was exactly what we needed!" -- Anonymous
Jesse's rule-of-thumb:
Points | Meaning |
---|---|
13 | Full sprint |
8 | A bit more than half a sprint |
5 | A few days (if not cursed) |
3 | A day or two |
2 | Half a day |
1 | An hour |
This only applies to STScI developers:
- Check if it already exists first.
- 1.1. If yes, comment on the existing issue. Stop here.
- 1.2. If no, continue to Step 2.
- Is all the info of this issue public?
- 2.1. If yes, continue to Step 3.
- 2.2. If no, continue to Step 4.
- Open issue on both GitHub and JIRA using one of the following methods:
- 3.1. If you want to utilize the nice GitHub feature/bug templates, open issue on GitHub. Then open a new ticket in JIRA and post GitHub issue URL there manually. Also apply the appropriate component label(s) on the JIRA ticket.
- 3.2. If you want to utilize the nice JIRA-GitHub integration bot (no templates), create a new JIRA ticket and remember to put
github
underLabels
field. Also apply the appropriate component label(s).
- Only create a new JIRA ticket without JIRA-GitHub integration bot. Also apply the appropriate component label(s). Do not use the feature described in 3.2 above. If you must have a GitHub counterpart, manually create a GitHub issue with the same title but omit all the sensitive information.
https://github.com/spacetelescope/jdaviz/pulls?q=is%3Aopen+is%3Apr+label%3Adiscussion
Type | Description |
---|---|
Rabbit hole | Code-dive maybe one or two upstream packages. Existing solution can be found after a lot of caffeine. |
Gopher hole | Oh no, you need to submit a small upstream PR. |
Fox hole | Upstream PR is bigger than you like, or you need to submit multiple upstream PRs. |
Sink hole | You are venturing into unchartered waters deep in upstream engine code, possibly adding a completely new feature. |
Bermuda hole | Cannot be fixed without flying/relocating a dev to choice destination. |
Black hole | This is just not possible without divine intervention. |