Closed steffilazerte closed 3 years ago
This ~90-min issue label-athon fits super well as preparation for a comm call -hackathon #18. Not restricted to packages in one domain.
Relates to community call Set up your package to get the most out of your community #21
I think some of us could use tips and tricks to minimize manual repetition. For example, I have not found a good way to port labels from one repo to another.
Perhaps a workflow with usethis::use_github_labels()
?
Definitely something to think about!
Thanks! How did I ever live without this?
Just wrote https://github.com/wlandau/dotfiles/blob/main/helpers/label_repo.R for future repos.
What a nice event idea :clap:
Should a helpful contributing guide be a pre-requisite or something that could be added to repos during the labe-athon? Especially for packages where there are some important things to know/set up (account at a developer sandbox for instance).
The idea is that it's the developers themselves who will be adding labels, issues, contributing guides, etc. to their own packages. So it's not necessarily a pre-requisite, but definitely something that the developers could work on during the label-athon. I've added this to the list of things to work on. Good idea!
I also clarified the idea that developers work on their own packages.
My current thinking is that the labelathon would follow nicely after the comm call "Set up your package to get the most out of your community #21" where we can coach folks on what things to set up, and during the labelathon they take time to do them, with us around (in zoom) to answer questions.
First Labelathon Apr 29 has been a blast and we'll schedule more. https://ropensci.org/events/labelathon01/
Folks can co-work on implementing some of these recommendations....or to hang out and work on their own package, but with company
Summary blog post: https://ropensci.org/blog/2021/04/28/commcall-pkg-community/
Landing page with video and links to resources, incl collaborative notes doc: https://ropensci.org/commcalls/apr2021-pkg-community/
Success! We're turning these into monthly social co-working / office hours sessions, at alternating times to satisfy different timezones.
Virtual gathering label-athon
Virtual gathering to give developers a set time to make their packages more contributor-friendly, including:
1) Labelling issues (e.g., "help wanted", "good first issue") (see Issues in the Contributing Guide) 2) Creating and labelling issues specifically for outside contributors 3) Adding design plans and road maps for the package to help potential contributors better understand the coding framework and future plans 4) Adding/updating contributing guides (including set up, etc.)
Who is the audience?
Any R developer with a package on an online platforms with issue trackers (ideally rOpenSci packages, but all welcome). Not restricted to packages in one domain. This activity involves developers working on their own packages.
Why is this important?
One strength of open source software is that it can be community driven. However, developers do need to ensure their packages are contributor-friendly. When packages are created in spare time, these tasks often occupy a lower priority. Improving/increasing community contributions is a goal of rOpenSci
Getting together for a dedicated time with other developers (meeting and networking with your people) can be fun AND productive, especially now when many of us feel isolated. Who are the rOpenSci community? Are we a community if we never interact? Let's meet each other!
What will we do?
*Work means:
Resources you would recommend to the audience