compose initial resolution for onboarding process #333

2026-09-28T14:38:00Z

oxaliq commented

2026-09-28 14:38:00 +00:00

Includes "onboarding buddy" role and proposal for new resources

❤️ 3

oxaliq added 1 commit 2026-09-28 14:38:01 +00:00

compose initial resolution for onboarding process 66657e17d1

decentral1se commented

2026-09-28 16:46:50 +00:00

I really like it, great work! It seems like it mightn't be implementable in a consistent way however, based on my experiences of our fedi membership participation. Here are some ideas, adjust/take on/throw away as desired!

I think the majority of the resolution could be implemented as 1) a checklist for new members 2) a checklist for vouch/buddy member, aka "we need better checklists and docs that people can follow".

That doesn't eliminate the proposal for new people to have a clear place to ask their questions but it does allow for extremely infrequent capacity which characterises federation membership at this current juncture.

So, I think we'll have the intended improvement if the new people have a solid and clear checklist to read and know the handle of the person they can DM directly for support and questions. Then we're still building, people have direct support from their buddy and the process can continue async / when time allows (vs. scheduling in a meeting which might be it's own demoralising exercise as it sometimes is 🙃)

I really like it, great work! It seems like it mightn't be implementable in a consistent way however, based on my experiences of our fedi membership participation. Here are some ideas, adjust/take on/throw away as desired! I think the majority of the resolution could be implemented as 1) a checklist for new members 2) a checklist for vouch/buddy member, aka "we need better checklists and docs that people can follow". That doesn't eliminate the proposal for new people to have a clear place to ask their questions but it does allow for extremely infrequent capacity which characterises federation membership at this current juncture. So, I think we'll have the intended improvement if the new people have a solid and clear checklist to read and know the handle of the person they can DM directly for support and questions. Then we're still building, people have direct support from their buddy and the process can continue async / when time allows (vs. scheduling in a meeting which might be it's own demoralising exercise as it sometimes is 🙃)

👍 1

oxaliq commented

2026-09-28 19:25:57 +00:00

@decentral1se Thanks for the response!

I definitely agree that most of this could be distilled into checklists and I will change the "further proposes [...]" language to reflect that. One of the roles of the buddy would then be to keep new members in phase with the inevitable documentation drift.

I also understand the limited capacity that Federation members have. My personal hope for this role is that new members are quickly integrated in a way that allows us all to make better use of that limited capacity. Does an estimated upper bound on 1 hour of work per week for the buddy feel too excessive?

Yr definitely probably right about synchronous communication as well, especially as there is a current push for meetings and new members could always attend kite-flyings. I'll strike that.

@decentral1se Thanks for the response! I definitely agree that most of this could be distilled into checklists and I will change the "further proposes [...]" language to reflect that. One of the roles of the buddy would then be to keep new members in phase with the inevitable documentation drift. I also understand the limited capacity that Federation members have. My personal hope for this role is that new members are quickly integrated in a way that allows us all to make better use of that limited capacity. Does an estimated upper bound on 1 hour of work per week for the buddy feel too excessive? Yr definitely probably right about synchronous communication as well, especially as there is a current push for meetings and new members could always attend kite-flyings. I'll strike that.

❤️ 1

p4u1 commented

2026-09-28 19:39:18 +00:00

Love this 😍
I See the concern from @decentral1se regarding the struggle of finding time for a meeting but I really like that this is part of the responsibility of the buddy role as this allows building real connections and allocating a budget for the role hopefully somewhat solves it. I also like @decentral1se emphasis on lists and async documentation. Maybe we can find a middle ground? Reduce the hours for the buddy role a little but expect at least one real time meeting?

Love this 😍 I See the concern from @decentral1se regarding the struggle of finding time for a meeting but I really like that this is part of the responsibility of the buddy role as this allows building real connections and allocating a budget for the role hopefully somewhat solves it. I also like @decentral1se emphasis on lists and async documentation. Maybe we can find a middle ground? Reduce the hours for the buddy role a little but expect at least one real time meeting?

❤️ 2

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u https://git.coopcloud.tech/oxaliq/docs.coopcloud.tech resolution/onboarding:oxaliq-resolution/onboarding

git checkout oxaliq-resolution/onboarding

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/docs.coopcloud.tech#333

Allow edits from maintainers