Added community fellow agreement, changed name of folder to personnel

This commit is contained in:
Nathan Schneider
2026-03-30 08:54:51 -06:00
parent 9218f9e7c1
commit a19cb2f29b
5 changed files with 60 additions and 2 deletions

View File

@@ -16,7 +16,7 @@ In this handbook, we document our own processes, to support our own work and for
- [Technology](docs/technology.md)
- [On-boarding](docs/on_boarding.md)
- [Radio](docs/radio.md)
- [RAships](docs/RAships/)
- [Personnel](docs/personnel/)
- [Background reading](docs/background_reading.md)
## How to contribute
@@ -29,4 +29,4 @@ Once in that team, navigate to the page you want to edit. To edit, press the pen
Once you press the edit icon, you should see an editable text field. Make your changes in Markdown—[syntax is here](https://docs.gitea.com/usage/markdown).
When your edits are complete, go to the bottom of the page to "Commit Changes." Type a simple summary of your changes in the top field. Choose "Commit directly to the `main` branch" and press the "Commit Changes" button.
When your edits are complete, go to the bottom of the page to "Commit Changes." Type a simple summary of your changes in the top field. Choose "Commit directly to the `main` branch" and press the "Commit Changes" button.

View File

@@ -0,0 +1,55 @@
# MEDLab Community Fellow Agreement
Dear {Fellow},
Welcome to a community fellowship with MEDLab! Community fellows represent MEDLab's commitment to active, accountable collaboration outside the university. It is an honorary position that acknowledges an ongoing collaboration relationship. We hope that you will benefit from your participation in the lab, and that you will contribute to the educational and research mission of the lab in turn.
The purpose of this letter is to clarify our shared expectations. If you have any questions or concerns about anything here, let's discuss them immediately to avoid any misunderstandings.
## Expectations
Here are some of the basics of your RAship:
- Period: {Start date} - {End date}
- MEDLab contact: {Contact}
The MEDLab community fellowship is an unpaid position. However, community fellows may receive honorariums, paid contracts, or other support from the lab on an ad hoc basis. Those forms of support are separate from this agreement.
Each community fellowship is different, depending on the capacity and interest of the fellow. But one way or another, all community fellows should actively participate in the MEDLab community. Please select your planned forms of participation below:
- [ ] Attend weekly lab meetings
- [ ] Attend MEDLab events
- [ ] Coordinate work independently with your supervisor and collaborators
- [ ] Be active and attentive to the Matrix chat and other collaboration tools on the MEDLab Cloud
- [ ] Conduct at least one interview for the podcast, in consultation with the producer
- [ ] Produce at least one blog post for the lab website
- [ ] Facilitate a Sunset Talks event
We expect that what you'll be working on may change during the fellowship, and we should have ongoing discussions about them. Our goal is for your MEDLab work to align as much as possible with your own interests and research, although that may not be entirely possible. At this stage, this is how we currently envision your role:
- {Specify focus and deliverables for the period}
You are responsible for establishing a rhythm of meetings with the MEDLab team that enables you to accomplish your goals.
## Accountability
Accountability is both an important theme in MEDLab's work and in how we work together.
Plan to maintain an ongoing dialogue with your MEDLab contact about mutual expectations. At minimum, your supervisor and you should discuss your progress and performance—as well as the supervisory relationship—at the midterm of a given appointment.
In the event of egregious or unprofessional behavior, or consistent under-performance in agreed-on duties, CF roles may be subject to at-will termination by either party. MEDLab will seek to pursue all possible opportunities for repair, consistent with meeting our commitments to collaborators and protecting the safety of our community.
MEDLab makes no claim of ownership for community fellows' work products, unless they are part of an explicit contract for work. In turn, community fellows must not represent themselves as speaking for or representing MEDLab leadership without further, explicit agreement. Community fellows may use their MEDLab title in media appearances or other public venues if they wish.
## On-boarding
If you have not already, please review the MEDLab Handbook and especially follow the guide on the On-Boarding page.
Welcome aboard!
## Approval
We the undersigned commit to the terms of this agreement. If this agreement needs to be changed we will discuss, agree on, and commit to a revised version.
* {MEDLab contact} ({date})
* {CF name} ({date})

3
docs/personnel/README.md Normal file
View File

@@ -0,0 +1,3 @@
# MEDLab personnel documents
This directory contains documents related to personnel working with MEDLab.