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
useR! repositories are managed on GitLab: https://gitlab.com/rconf. Currently there are 2 private repos:
useRadmin (information on useR! finance, sponsors, etc, shared only with main useR! co-ordinators)
useRorganization (information on useR! organization to share with all organizers)
In addition, the organizers for a specific conference have a website repo and a general organization repo, so have a lot of information to take on board already.
How best to integrate the conferences HOW-TOs/event best practices with this?
Two possible options
Keep this info on Forwards GitLab, add links to it in the useRorganization repo to help organizers find it. Pros: simple, keeps Forwards guidance somewhat generic to any conference. Cons: harder to collaborate with useR! organizers on updates and benefit from their input/experience, easier for useR! organizers to overlook.
Move this info to useRorganization. Pros: easier for useR! organizers to find and help maintain. Cons: currently useRorganization is private (still some relatively confidential info, e.g. example emails, past sponsorship amounts) - could possibly make generic/move this info to useRadmin); have to add Forwards folk e.g. Noa and Liz to this repo (no big deal).
Let's discuss when Noa returns from break.
The text was updated successfully, but these errors were encountered:
useR! repositories are managed on GitLab: https://gitlab.com/rconf. Currently there are 2 private repos:
In addition, the organizers for a specific conference have a website repo and a general organization repo, so have a lot of information to take on board already.
How best to integrate the conferences HOW-TOs/event best practices with this?
Two possible options
Keep this info on Forwards GitLab, add links to it in the useRorganization repo to help organizers find it. Pros: simple, keeps Forwards guidance somewhat generic to any conference. Cons: harder to collaborate with useR! organizers on updates and benefit from their input/experience, easier for useR! organizers to overlook.
Move this info to useRorganization. Pros: easier for useR! organizers to find and help maintain. Cons: currently useRorganization is private (still some relatively confidential info, e.g. example emails, past sponsorship amounts) - could possibly make generic/move this info to useRadmin); have to add Forwards folk e.g. Noa and Liz to this repo (no big deal).
Let's discuss when Noa returns from break.
The text was updated successfully, but these errors were encountered: