-
Notifications
You must be signed in to change notification settings - Fork 17
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
R Contribution Working Group at R@IISA? #13
Comments
cc @bnaras. |
@hturner I don't know but will find out. It would be very helpful to identify a group of people from useR!2021 who would be willing to help with the local organization etc. Then a strong proposal can be made to keep the momentum going from useR!2021 where Indian participation was only behind USA and Germany. |
Hello! I did participate in R@IISA in 2019, and was also a part of the useR! 2021 global organizing team. I would like to volunteer, if possible. I am currently based in Bangalore. Thanks |
@adithirgis can you raise this at the upcoming AsiaR community meeting and see if there is interest from people there? I think between us we might be able to suggest some other names, but that group seems the best place to start to form a core team. Perhaps you can forward an invite to @bnaras if he's not already on the distribution list? |
Thanks for pointing me to this, @hturner. Adithi & I recently reached out to AsiaR folks for a follow-up meeting this/next month (incl. @bnaras). And absolutely, I will be sure to mention R@IISA in the following email. Naras, if you'd like, we can add it to the agenda too. Let us know ([email protected]). If there's a virtual component, I will take part in the next IISA conf. Thanks, all! |
I don't know if there are any plans to repeat R@IISA at IISA2022 which is planned to be in Bangalore, India, presumably at a a similar time of year to previous instances (last few days of December). If another R@IISA is held, it could be good to connect with this conference in a similar way to the plans for LatinR 2021 (#9). This is some way off, but might need a bit of planning ahead, so I'm noting it for future consideration.
The text was updated successfully, but these errors were encountered: