Hi Patrick, Martin, and all,
Ok, that would work for me. When you have a chance, Martin, could you set up the Documentation team on the website? And whenever I see it, then I can write the description. I don't think there's any real rush.
I think open membership would probably be appropriate for this team, right? So people can sign themselves up.
I'll try and quickly mention it at the next Vectors meeting (or maybe the next), and maybe we can send out an invite via all the media outlets?
Thank you very much, brynn
On 1/27/2020 12:38 PM, Patrick Storz wrote:
Hi Brynn,
I'd be happy to fill in the role of "technical lead" if that's required. (It's basically what I'm doing already anyway).
I'd certainly prefer if others feel in charge of content, though (I can do it, but I'm rather slow, so it does not feel like an efficient use of my time). If you want to have an eye on the content-side of things that would be much appreciated!
In both cases I fully agree with Martin - it would be great if we could manage documentation as a (hopefully quickly growing) team. It's always better when there are multiple shoulders to distribute the workload and it never hurts if people are able to fill in for each other.
Best Regards, Patrick
Am 27.01.2020 um 09:59 schrieb Martin Owens:
Hi Brynn,
Patrick will likely weigh in on if he's putting himself forwards for a leadership role in the docs team. My sense is that very few teams have a secure leadership and mostly bits of work from other teams (like translations, vectors etc) looks like an active team/people who are in control; but it's a bit of a mirage.
So do take it forwards. You may even choose to use say the wiki and the mailing list is GitLab is an issue. This is something that can be discussed between all the people who want to contribute about which tools work best. Delegating to a person who can set up GitLab is totally fine if that's what you need.
Best Regards, Martin Owens
On Sun, 2020-01-26 at 05:54 -0700, brynn wrote:
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
Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org To unsubscribe send an email to inkscape-docs-leave@lists.inkscape.org
Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org To unsubscribe send an email to inkscape-docs-leave@lists.inkscape.org