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
AIM is a large project and starting on it can be pretty daunting; it would be nice to have onboarding documentation for the various roles within AIM in this repo.
I think it'd be helpful to have documentation specific to the different positions people have - e.g. working for AIM vs. AIM RSF.
To-do
figure out how many versions of the onboarding make sense -> always have the boiler plate be the most up to date
figure out a way to keep the various versions synced but separate (if possible) -> have a boiler plate that gets updated and then archive the new starter files into a folder
create first drafts
get feedback from people in those positions
finalise the documents
make sure they're easy to find
Stakeholders
This is relevant for everyone working in AIM/AIM RSF with the primary contacts being EZ and SB.
I will move the onboarding docs @eirini-zormpa drafted out of Getting Started as the Getting Started repo was also for consortia members and not just Turing employees.
They look awesome Eirini! I'm happy to move them maybe into community management and then make a PR?
* [ ] figure out how many versions of the onboarding make sense
* [ ] figure out a way to keep the various versions synced but separate (if possible)
My thoughts is to have the core docs as templates, and then just a file for each person. Then what gets updated is only every the core docs and whoever the new starter's file is?
That should work! Though my main uncertainty was about keeping the templates synced with each other (e.g. AIM RSF at the Turing, AIM RSF outside the Turing, AIM consortium member)
About
AIM is a large project and starting on it can be pretty daunting; it would be nice to have onboarding documentation for the various roles within AIM in this repo.
I think it'd be helpful to have documentation specific to the different positions people have - e.g. working for AIM vs. AIM RSF.
To-do
Stakeholders
This is relevant for everyone working in AIM/AIM RSF with the primary contacts being EZ and SB.
Activity
EZ added some drafts to the onboarding branch (https://github.com/aim-rsf/Getting-Started/blob/onboarding-docs/onboarding/rsf-turing-staff.md) . These are based on the documentation that SB created.
The text was updated successfully, but these errors were encountered: