Update content in facilitators-docs.md (previously leader-docs.md)

[adiati98]

Description

This PR updates the following things:

• Renamed leader-docs.md to facilitators-docs.md.
• Update the content in facilitators-docs.md.

Related Issue

Refers to #324

[danieltott]

It's hard to tell if any content here changed aside from the name change - in the future if you can make the name change (without any content changes) it's own commit, then make changes, that allows a much easier time diffing 👍🏼

My only change here would be do add a big link somewhere in the main README to this file so that it's easy to find.

[adiati98]

I can close this PR and open a new one as per your suggestion to:

1. Change the file name & commit.
2. Update the content & commit.

[danieltott]

@adiati98 you don't need to close this one just something to keep in mind in the future 👍🏼

[BekahHW]

So far, everything looks good to me.

I wonder if it's worth asking for volunteer facilitators on a monthly basis. So the facilitators would be responsible for reaching out to the community to see if anyone was up for facilitation for the month.

[adiati98]

@BekahHW now you mentioned that, I'm thinking that we can ask support in the months only when we need volunteers. We don't need to do that on a monthly basis.

But I think it's worth it to ask for opinions on what folks want to see differently in a challenge or if they have ideas for a new challenge that they want to do. It's also a way for us to let folks know the upcoming challenge.
We can do that on a monthly basis. Or we do only for the challenges that are not getting enough interest/engagements. Thoughts?

Once we compiled the async check-in scripts for all challenges, I think we're good with the async tasks.

I feel that the only thing we lack is volunteers who can take on sync events such as sync check-ins. Although we don't have to force ourselves to do that when we don't have anyone to do it.

[adiati98]

It's hard to tell if any content here changed aside from the name change - in the future if you can make the name change (without any content changes) it's own commit, then make changes, that allows a much easier time diffing 👍🏼

My only change here would be do add a big link somewhere in the main README to this file so that it's easy to find.

@danieltott maybe we can move this and put it under the procedures on README?

Also, how about the files that we want to archive? Should we compile them all in one file called archive that lives on the root? Or should we make an archive file inside every challenge file?

[danieltott]

@adiati98 I think this is big enough that it deserves its own file.

As for archives, I'd keep them in their own folders 👍🏼

[adiati98]

@danieltott Sorry, but I don't get what you mean by its own file 😅.

Procedure is a folder, right? Can we move this file there then?

[adiati98]

@danieltott @BekahHW I'm currently updating this file.
If you both approved the content here, can we merge this in?

I'll create a new PR for the update to avoid this PR getting much longer. Thank you! 😊

[danieltott]

@adiati98 DONE! 😃

[adiati98]

Thanks, @danieltott 😄