Patrick seems to have taken the lead for getting documentation ready for 1.0. At least he was very active in the Doc chatroom recently. I thought he already was leading, until I realized there's not already a formal team. (Actually I thought there was once a Documentation Team on the website, but when I looked for it, didn't find.)
I'd be glad to either co-lead or be 2nd chair. Since I don't get along very well with GitLab, and since GL is where most of the documentation is kept, I hesitate to lead it alone. (For example, I would not be able to teach a newbie how to use it.)
I already did reach out to tutorial authors. But we could make it much wider. I'm not exactly sure what a recruitment drive is, but I'll help however I can.
I fear the agenda for the upcoming Vectors meeting is big enough for the next 2 meetings already. It might have to wait for the next meeting. Unless we can have 2 meetings in a month?
brynn
On 1/24/2020 9:05 AM, Martin Owens wrote:
The website admin stands ready to make you a team if you need one.
For community management though, I would put together a recruitment drive with the vector's team. You'll want to encourage new people who've never contributed to join you a space that they'll be comfortable with. That might be the rocket chat, or it could be the forums. But having that soft landing page with a warm welcome will be really important to growing the team.
The other thing is leadership. I've seen a few different people working on documentation and tutorials and such. Do you have any idea about who might want to lead the team, organise meetings or prioritise work?
Best Regards, Martin Owens