Hi Victor, This message is more about creating the team page on the website, along with all the other teams. There really is not a team currently, so I'm just asking, should there be one? I'm thinking there should be.

I remember that Patrick was recently lamenting about the lack of enough people to review tutorials before 1.0 is released. And having a formal team would go a long way toward making sure there are enough people to do the work, in the future. But in general, the team would work on any kind of documentation, which would include not just existing documentation, but potentially new tutorials or even a manual, in the future.

Thanks, brynn

On 1/22/2020 6:18 PM, Victor Westmann wrote:

Hi Brynn,

Hope you are well. The idea is good! What is in your/our road map in the documentation team?

What do you believe we will need to work on? ;)

On Wed, Jan 22, 2020, 4:38 PM brynn, <brynn@frii.com mailto:brynn@frii.com> wrote:

Hi Friends,

          In conjunction with the new Tutorials page, and call for new
tutorial authors to join, I'm thinking maybe a Documentation team
should
be created (on the website Teams page)?  It might at least be a good
starting place, to think about a new community-managed manual, and all
kinds of other documentation.

          Comments?


All best,

brynn

_______________________________________________
Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org
<mailto:inkscape-docs@lists.inkscape.org>
To unsubscribe send an email to
inkscape-docs-leave@lists.inkscape.org
<mailto:inkscape-docs-leave@lists.inkscape.org>

I am ready to assist with reading materials from time to time but I am afraid I will not have time to fully dedicate to this initiative. I want to make sure I deliver what I commit to.

Are we able to recruit someone new from our community? Do we have anyone?

I am going to admit here that one of my plans was to do a simple and basic Inkscape course, all based on YouTube videos, in my native language (Brazilian Portuguese) after noticing that there is no single source of learning the basics of Inkscape with good quality and consistency.

I have never recorded videos before but I have created multiple written training material both in step by step, user guides and in tutorial fashion. I even bought the basic course from Nick Saporito about Inkscape so I could learn all the basics as well as to learn with his teaching style and to close my gaps on the features I was not aware of before

Wish me good luck. Planning this for this year. Just trying to decide if the course would be for 0.92.x or 1.0 release

On Fri, Jan 24, 2020, 8:05 AM Martin Owens, doctormo@gmail.com 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

On Fri, 2020-01-24 at 08:25 -0700, brynn wrote:

...

Hi Victor, This message is more about creating the team page on the website, along with all the other teams. There really is not a team currently, so I'm just asking, should there be one? I'm thinking there should be.

  I remember that Patrick was recently lamenting about the lack

of enough people to review tutorials before 1.0 is released. And having a formal team would go a long way toward making sure there are enough people to do the work, in the future.

  But in general, the team would work on any kind of

documentation, which would include not just existing documentation, but potentially new tutorials or even a manual, in the future.

Thanks, brynn

On 1/22/2020 6:18 PM, Victor Westmann wrote:

...

Hi Brynn,

Hope you are well. The idea is good! What is in your/our road map in the documentation team?

What do you believe we will need to work on? ;)

On Wed, Jan 22, 2020, 4:38 PM brynn, <brynn@frii.com mailto:brynn@frii.com> wrote:

Hi Friends,

          In conjunction with the new Tutorials page, and call

for new tutorial authors to join, I'm thinking maybe a Documentation team should be created (on the website Teams page)? It might at least be a good starting place, to think about a new community-managed manual, and all kinds of other documentation.

          Comments?


All best,

brynn

_______________________________________________
Inkscape Docs mailing list -- inkscape-docs@lists.inkscape.org
<mailto:inkscape-docs@lists.inkscape.org>
To unsubscribe send an email to
inkscape-docs-leave@lists.inkscape.org
<mailto: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

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

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

Wow! Ok, I'll see if I can get started today. I'm going to have to sign off in about an hour. But tomorrow I can get into it more.

One thing I'm curious about. I remember in the Moderation team, there is a Charter. But a lot of the teams don't have Charters. I always have wondered why?

Thanks for the speedy works!

brynn

On 1/28/2020 6:55 AM, Martin Owens wrote:

The team is created:

https://inkscape.org/*docs/

But it needs details, descriptions, full descriptions, charters, links that sort of thing to make the page more useful.

Martin,

On Tue, 2020-01-28 at 06:33 -0700, brynn wrote:

...

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