You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: community/events/sprints.md
+15-10Lines changed: 15 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -341,7 +341,9 @@ steps to take:
341
341
and community highlights.
342
342
-**GitHub**: Remind them to continue following and contributing to pyOpenSci
343
343
[repositories on GitHub](https://github.com/pyopensci).
344
+
:::{todo}
344
345
- Discourse?
346
+
:::
345
347
346
348
4.**Stay Connected**:
347
349
-**Upcoming Events**: Inform participants about upcoming sprints, webinars,
@@ -350,26 +352,29 @@ steps to take:
350
352
By thanking contributors you are helping to maintain the momentum generated during the sprint, while also
351
353
fostering a sense of community, and encourage ongoing contributions to pyOpenSci projects.
352
354
355
+
### Final wrap up activities
353
356
357
+
We will have several outcome tasks to do to wrap up a sprint. These
358
+
are listed below:
354
359
360
+
* Blog post about the event with stats around activity (number of participants, pull requests, issues, etc). This post might highlight wins both big and "small"!
361
+
* Social media promoting the success of the event and above metrics
362
+
* LinkedIn newsletter reusing that blog post content
355
363
364
+
### Welcome new contributors to slack
356
365
357
-
Help for sprint event triage after the event
358
-
Event outputs
359
-
Blog post(s)
360
-
Social
361
-
Welcome new ppl to slack
362
-
Community Content “owners”
363
-
Related to above - help post event. We have a lot of issues and pr’s now. Can the community help with triage?
364
-
365
-
366
+
Because some participants come to sprints to learn, they may not stage engaged with pyOpenSci after a sprint event. As such it's best to invite
367
+
people who continue to stay engaged with us either via GitHub or some
368
+
other mechanism (becoming a reviewer, editor, submitting a package, etc).
366
369
367
370
:::{admonition} Meeting metrics that pyOpenSci collects
368
371
:class: info
369
372
* Number of pull request submitted
370
373
* Number of issues submitted
371
374
* Number of contributors contributed
372
-
* Where are the contributors from (country, place of work, other things??)
375
+
* Where are the contributors from (country, place of work / organization)
376
+
* Type of user - student, professional, non profit/ public sector.
0 commit comments