Skip to content

Commit 0c9edf5

Browse files
committed
current notes
1 parent 1086e90 commit 0c9edf5

File tree

1 file changed

+72
-0
lines changed

1 file changed

+72
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
# Meeting Notes 17 May 2021
2+
3+
###### tags: `Meeting`
4+
5+
:::info
6+
- **Date:** Nov 1, 2030 2:30 PM (CET)
7+
- **Agenda**
8+
1. Sofware Review sync `10min`
9+
2. Editorial Board `20min`
10+
+ domain area "buckets"
11+
+ how to find editors for each "bucket"
12+
+ onboarding
13+
4. SciPy mentored sprints `15min`
14+
- **Participants:**
15+
- Leah Wasser (LW)
16+
- Ivan Ogasawara (OW)
17+
- David Nicholson (DN)
18+
19+
:::
20+
21+
## Notes
22+
<!-- Other important details discussed during the meeting can be entered here. -->
23+
1. softare review sync
24+
+ devicely
25+
+ ask on twitter about reviewers
26+
+ OW: could act as reviewer, worked on related tool
27+
+ pymedphys
28+
+ LW: pymedphys -- actually a set of tools - similar to astropy
29+
+ some issues we should close - close all of the old presumbissions
30+
2. editorial board
31+
+ Lets start with Ivan, David and Leah
32+
+ We might consider domain "buckets"
33+
+ ROpenSci + JOSS like model
34+
+ who do we want, how long do they serve
35+
+ we have onboarded them
36+
37+
## Action Items
38+
- LW: close older issues w/invitation to submit
39+
- LW: will get back to simon about PyMedPhys
40+
- DN: add suggestion to editor guide to update initial comment w/reviewers etc. so it's right at top of issue
41+
- DN: post on twitter asking for reviewrs for devicely
42+
- DN: figure out if there's overlap for phylup
43+
- DN: follow up w/LW + IO about mentored sprints at SciPy
44+
45+
## SciPy Mentored Sprints (David) - Tania Allard
46+
* they are doing these springs at pycon
47+
* https://mentored-sprints.netlify.app/
48+
* https://www.youtube.com/watch?v=SGUHyP8ki_Q
49+
* could we use pyopensci maintainers to participate in the mentored sprints?
50+
* Have them bring friends who can contribute to the sprints?
51+
* maintainers would need to identify things to fix
52+
* Then they would come to the sprint
53+
* Do they have to register for scipy?
54+
* sprints are run in discord
55+
* git help desk
56+
* maintainers volunteer time to
57+
* find issues ahead of time
58+
* work with people who want to submit PRs
59+
* ask them to do things that aren't code contributions like run through a tutorial and raise issues, etc.
60+
* Open science labs - they do hae training materials already in (spanish?)
61+
62+
63+
Challenges with mentored sprints
64+
* getting envt setup
65+
* knowing what issue to work on
66+
67+
68+
# Outcomes
69+
we will go to scipy and SPY
70+
71+
ducky app for video chat?!
72+

0 commit comments

Comments
 (0)