New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Confirmation Hackathon/"Bug Barbeque" #18
Comments
I think this issue was closed by mistake. |
Love the name "bug barbecue" |
I have contacted the useR! 2022 organizing team suggesting the following sessions on Thursday/Friday June 23/24: Session 1 (APAC): Session 2 (EMEA): Session 3 (AMER): See here for most timezones: Of course this relies on some facilitators being available in each session. It would be great if people could add their name and timezone on the second tab of the above spreadsheet if they are willing to help (I've added a few folks already, please add a note if you can't make the session(s) in your timezone). Put the date in your diary! I've allowed 4 hours, but expect much of the time to be unstructured drop-in style (maybe zoom rooms open, slack channel available). We could have a kick-off talk for 20-30min at the start which could be live or pre-recorded (same for all sessions) and perhaps a wrap-up time at the end. Maybe short regrouping to check progress after each hour? (N.B. not all time zones will be "on the hour"!). |
This satellite to useR! went ahead as planned, we should open a new issue for any future Bug BBQ/hackathon. |
One idea could be having a ”bug barbecue”, with involvement from R Foundation, or R-core
Probably not to fix things, but to have a big “replication/confirmation” push in a short amount of time with high engagement
As opposed to longer term mentoring, or in addition to it.
I know that the Carpentries run this type of thing one or maybe a couple times a year, I could find out how often.
The core idea is that you'd have a short span of time (a half day, maybe) with really high engagement, rather than a slow trickle over a long period of time.
I do think it would work better with some amount of R-foundation/R-core involvement, but if a couple different R core members could be involved for an hour or two each over the course of the day and we could get a high number of contributors blocking out that half day or so to focus on helping them out, iteration could get much faster and we might get a lot done. Thats the theory anyway.
The text was updated successfully, but these errors were encountered: