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