No subject

Wed Aug 17 18:42:36 UTC 2011

all levels and skills.

Welcome and thanks!

Lorelle

On Tue, May 29, 2012 at 6:24 AM, Wayne Hatter
<wayne at wordpresslivehelp.com>wrote:

> On 5/16/2012 8:00 AM, wp-docs-request at lists.**automattic.com<wp-docs-request at lists.automattic.com>wrote:
>
>> Send wp-docs mailing list submissions to
>>        wp-docs at lists.automattic.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>> or, via email, send a message with subject or body 'help' to
>>        wp-docs-request at lists.**automattic.com<wp-docs-request at lists.automattic.com>
>>
>> You can reach the person managing the list at
>>        wp-docs-owner at lists.**automattic.com<wp-docs-owner at lists.automattic.com>
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of wp-docs digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: Joining Forces: Support (Lorelle on WordPress)
>>
>>
>> ------------------------------**------------------------------**
>> ----------
>>
>> Message: 1
>> Date: Tue, 15 May 2012 15:32:42 -0700
>> From: Lorelle on WordPress<lorelleonwordpress@**gmail.com<lorelleonwordpress at gmail.com>
>> >
>> Subject: Re: [wp-docs] Joining Forces: Support
>> To: WordPress Documentation<wp-docs at lists.**automattic.com<wp-docs at lists.automattic.com>
>> >
>> Message-ID:
>>        <CAN2v4ZTr=1q-**ng3DtvrFS85jTR3zGYeWYREB+**
>> qS6U3ykPZhuag at mail.gmail.com<1q-ng3DtvrFS85jTR3zGYeWYREB%2BqS6U3ykPZhuag at mail.gmail.com>
>> >
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> I've worked with some three person teams on many projects and love it for
>> that reason, Andrea. There are a LOT of plates to spin when it comes to
>> the
>> Codex. We've never been able to get someone to coordinate the
>> international
>> versions and I fear for what are on those pages, for example.
>>
>> The WordPress Meetup group here in Portland has asked me to do a WordPress
>> Codex evening followed by a Codex Day. I'll be posting about that in a
>> bit,
>> and I'd love to see more such projects from WordCamps and WordPress
>> Meetups, too, and that takes some team coordination as well.
>>
>> Lorelle
>>
>>
>> On Tue, May 15, 2012 at 12:57 PM, Andrea Rennick<andrea at ronandandrea.**
>> com <andrea at ronandandrea.com>>wrote:
>>
>>  Ideally a team of three. One is too few (what if they get busy? then it
>>> stalls), and two can disagree (another stall) while a third can be a
>>> tiebreaker if needed. Or a sane person, depending. :P
>>>
>>> I'm just tossing out ideas here.
>>>
>>> a.
>>>
>>>
>>> On Tue, May 15, 2012 at 4:28 PM, Doug Sparling<doug.sparling at gmail.**com<doug.sparling at gmail.com>
>>> >wrote:
>>>
>>>  I like the idea as well.
>>>>
>>>>
>>>> On Tue, May 15, 2012 at 2:22 PM, Lorelle on WordPress<
>>>> lorelleonwordpress at gmail.com>  wrote:
>>>>
>>>>  This is so exciting. The Docs team has been walking on egg shells for
>>>>> years over the confusion of the WordPress Handbook, and I'm eager to
>>>>> see
>>>>> new energy being sent in this direction.
>>>>>
>>>>> The close ties between the Forum and Codex have been there since the
>>>>> beginning. However, time and skills serving the Forum and the time and
>>>>> skills serving documentation are distinctive, as several people
>>>>> mentioned.
>>>>> I agree that there needs to be one or two people overseeing the
>>>>> organizational structure, management, and maintenance of the Codex.
>>>>>
>>>>> Having a site of our own has been essential and lacking, which is why
>>>>> we
>>>>> created the unofficial docs task list not long ago. It was critical
>>>>> that we
>>>>> find a better way of communicating and keeping our community connected
>>>>> than
>>>>> the mailing list. As it was "unofficial," we haven't done much to
>>>>> promote
>>>>> it or work with it, but it was a start. We need to have a place to
>>>>> support
>>>>> and educate each other on how to write for the Codex and offer task
>>>>> lists
>>>>> beyond those we've had in the past on the Codex, so I'm excited about
>>>>> having our own space or making the current blog on WordPress.com
>>>>> official.
>>>>>
>>>>> The mailing list has not been the sole line of communication either. As
>>>>> many do, I work with many people one on one to help them write and
>>>>> edit for
>>>>> the Codex and assign tasks, communicating with the mailing list when
>>>>> necessary for edits and such.
>>>>>
>>>>> As we struggled to understand the role the WordPress Handbook and
>>>>> WordPress Lessons played in the role of documentation in the WordPress
>>>>> Community, we've come to realize the Codex best serves the WordPress
>>>>> Community by providing support for issues found within the Forums,
>>>>> expanding upon Learn WordPress instructions for the WordPress Lessons
>>>>> section, and developing more extensive documentation and guides beyond
>>>>> the
>>>>> basics found within the help files, especially servicing developers and
>>>>> programmers.
>>>>>
>>>>> While melding together Forum and Codex sounds great on the surface, I
>>>>> agree with Andrea and others that we need to have one or more people
>>>>> focused on the bigger picture overseeing the Codex, thus supporting the
>>>>> overall WordPress Community better.
>>>>>
>>>>> Thanks for the survey, Jane, and for helping with all of this.
>>>>>
>>>>> Lorelle
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, May 15, 2012 at 8:28 AM, Andrea Rennick<andrea at ronandandrea.**
>>>>> com <andrea at ronandandrea.com>
>>>>>
>>>>>> wrote:
>>>>>> It makes totally sense, because Support&  Docs are two sides of the
>>>>>> same coin. :) If users can't understanding docs or can't find them,
>>>>>> they
>>>>>> post in the forums. ;P
>>>>>>
>>>>>> Better docs mean less support issues, because people don't scale. And
>>>>>> the people answering questions are the first ones who see the need
>>>>>> for new
>>>>>> docs. Because they answer the same questions over and over (and over)
>>>>>> again.
>>>>>>
>>>>>> Getting people to read docs is a separate issue, but having support
>>>>>> and
>>>>>> docs work hand in hand in tandem is a big first step.
>>>>>>
>>>>>> I think half the people overlap anyway, yes?
>>>>>>
>>>>>> a.
>>>>>>
>>>>>>
>>>>>> On Tue, May 15, 2012 at 11:51 AM, Chip Bennett<chip at chipbennett.net>*
>>>>>> *wrote:
>>>>>>
>>>>>>  Personally, I love the idea. Speaking as a contributor group member
>>>>>>> who tries to keep in the loop regarding support and/or Codex issues
>>>>>>> that
>>>>>>> impact our group (or issues where our contributor group can be
>>>>>>> helpful),
>>>>>>> such consolidation is welcome.
>>>>>>>
>>>>>>> Chip
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 15, 2012 at 7:09 AM, Jane Wells<jane at automattic.com>**
>>>>>>> wrote:
>>>>>>>
>>>>>>>  Hi everyone. The results of the recent surveys to identify active
>>>>>>>> contributors and elect team reps made it pretty clear that the docs
>>>>>>>> team is
>>>>>>>> in a bit of a slump, organizationally speaking. Only 5 people from
>>>>>>>> the
>>>>>>>> wp-docs post responded, and of those, 2 were new or not yet
>>>>>>>> contributing,
>>>>>>>> and there was no consensus re reps among the remaining 3
>>>>>>>> respondents. It
>>>>>>>> got me thinking about how we organize contributors, what has worked
>>>>>>>> well
>>>>>>>> elsewhere in the WP ecosystem and in other free software projects,
>>>>>>>> and
>>>>>>>> leads me to this proposal: what if we combined forums and docs into
>>>>>>>> one
>>>>>>>> Support team?
>>>>>>>>
>>>>>>>> Looking back at the Codex activity from the past six months or year,
>>>>>>>> chunks of it have been tied to forum mods (like Ipstenu and
>>>>>>>> Andrea_r),
>>>>>>>> other contributor groups (like Chip on the Theme Review Team), and
>>>>>>>> new
>>>>>>>> releases. Not that how Automattic/WordPress.com organizes itself
>>>>>>>> should
>>>>>>>> decide anything, but their support team manages forums, email
>>>>>>>> support, and
>>>>>>>> docs, and it seems to work pretty well. They have a schedule for
>>>>>>>> reviewing
>>>>>>>> existing documentation so it never gets too far out of date, and
>>>>>>>> the people
>>>>>>>> on the front lines with users in the forums and via email can see
>>>>>>>> very
>>>>>>>> clearly where they need to beef up documentation. I'm thinking this
>>>>>>>> could
>>>>>>>> work well for .org, too. Those who are strong writers and just want
>>>>>>>> to
>>>>>>>> contribute to documentation could still do so, but within a context
>>>>>>>> of what
>>>>>>>> our user support needs are at any given time based on the actual
>>>>>>>> support
>>>>>>>> requests.
>>>>>>>>
>>>>>>>> What I'm envisioning is less siloing of contributor personnel, with
>>>>>>>> one group blog at make.wordpress.org/support that uses tags like
>>>>>>>> forums and codex to organize posts, and has pages to help orient new
>>>>>>>> contributors and get them started. These mailing lists could fade
>>>>>>>> away in
>>>>>>>> favor of email subscriptions from the blog, which are more easily
>>>>>>>> searchable and would be more visible to potential contributors.
>>>>>>>> Within the
>>>>>>>> uber-group, some people would naturally gravitate toward specific
>>>>>>>> tasks
>>>>>>>> while others would multi-task as they have been doing.
>>>>>>>>
>>>>>>>> Over time we could expand the purview of the group to include things
>>>>>>>> like moderating instructional videos and comments at wordpress.tv(and
>>>>>>>> start embedding appropriate videos into codex), possibly helping to
>>>>>>>> staff in-person help desks in local communities and/or at events
>>>>>>>> like
>>>>>>>> WordCamps and Meetups, etc. I think the prospects are pretty
>>>>>>>> exciting, and
>>>>>>>> I could see this becoming the biggest and most active of all the
>>>>>>>> contributor groups, which would be awesome.
>>>>>>>>
>>>>>>>> If there are any strong objections to this approach, please reply to
>>>>>>>> this thread today so we can discuss. If not, and everyone is
>>>>>>>> willing to
>>>>>>>> give this a shot and all work together (at least as an experiment
>>>>>>>> for, say,
>>>>>>>> the next release cycle or two), I'll go ahead and set up the group
>>>>>>>> blog
>>>>>>>> tomorrow.
>>>>>>>>
>>>>>>>> Jane
>>>>>>>> ______________________________****_________________
>>>>>>>> wp-docs mailing list
>>>>>>>> wp-docs at lists.automattic.com
>>>>>>>> http://lists.automattic.com/****mailman/listinfo/wp-docs<http://lists.automattic.com/**mailman/listinfo/wp-docs>
>>>>>>>> <http:**//lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>>>>>>> >
>>>>>>>>
>>>>>>>>
>>>>>>> ______________________________**_________________
>>>>>>> wp-docs mailing list
>>>>>>> wp-docs at lists.automattic.com
>>>>>>> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Andrea Rennick, http://wpebooks.com and http://ronandandrea.com
>>>>>> Co-author of WordPress All-In-One For Dummies http://rml.me/aio
>>>>>>
>>>>>>
>>>>>> ______________________________**_________________
>>>>>> wp-docs mailing list
>>>>>> wp-docs at lists.automattic.com
>>>>>> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>>>>>
>>>>>>
>>>>>>  ______________________________**_________________
>>>>> wp-docs mailing list
>>>>> wp-docs at lists.automattic.com
>>>>> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>>>>
>>>>>
>>>>>  ______________________________**_________________
>>>> wp-docs mailing list
>>>> wp-docs at lists.automattic.com
>>>> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>>>
>>>>
>>>>
>>> --
>>> --
>>> Andrea Rennick, http://wpebooks.com and http://ronandandrea.com
>>> Co-author of WordPress All-In-One For Dummies http://rml.me/aio
>>>
>>>
>>> ______________________________**_________________
>>> wp-docs mailing list
>>> wp-docs at lists.automattic.com
>>> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>>
>>>
>>>  -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:<http://lists.automattic.**com/pipermail/wp-docs/**
>> attachments/20120515/560f5849/**attachment-0001.htm<http://lists.automattic.com/pipermail/wp-docs/attachments/20120515/560f5849/attachment-0001.htm>
>> >
>>
>> ------------------------------
>>
>> ______________________________**_________________
>> wp-docs mailing list
>> wp-docs at lists.automattic.com
>> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>>
>>
>> End of wp-docs Digest, Vol 80, Issue 10
>> *****************************************
>>
> Hello, I would like to know how I get involved in helping out in the
> Wordpress community?
>
> Thanks
> Wayne Hatter
> ______________________________**_________________
> wp-docs mailing list
> wp-docs at lists.automattic.com
> http://lists.automattic.com/**mailman/listinfo/wp-docs<http://lists.automattic.com/mailman/listinfo/wp-docs>
>

--20cf3074b31cedcca904c133d865
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Almost lost your reply. We tend to reply at the TOP of the notes rather tha=
n the bottom. :D Check out <a href=3D"http://wpdocsteam.wordpress.c=
om">http://wpdocsteam.wordpress.com</a> for a to do list and information wi=
th links to Codex Guidelines, styles, and how to contribute. We need people=
 to just click the Random Page button to check links and grammar and detail=
s, and people to fix articles that need updating and fixing, and people to =
contribute new articles. All the information is at that site.

Begin by logging in through the WordPress Support Forum, then logging i=
n again through the Docs link at <a href=3D"http://codex.wordpress.org/inde=
x.php?title=3DSpecial:UserLogin">http://codex.wordpress.org/index.php?title=
=3DSpecial:UserLogin</a> Edit the page and write a little about yourself so=
 we know who you are and your skill set, and use that page to practice writ=
ing in Mediawiki code. At the bottom of the Edit preview is a link to Editi=
ng Help with all the examples of how to write in Mediawiki.

From there, hit the to do list and see what needs doing. We need people=
 of all levels and skills. Welcome and thanks! Lorelle <b=
r>
 <div class=3D"gmail_quote">On Tue, May 29, 2012 at 6:24 AM, Wayne H=
atter &lt;<a href=3D"mailto:wayne at wordpresslivehelp.com" =
target=3D"_blank">wayne at wordpresslivehelp.com</a>&gt; wrote: <blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">

On 5/16/2012 8:00 AM, <a href=3D"mailto:wp-docs-request at lists.automattic.co=
m" target=3D"_blank">wp-docs-request at lists.<u></u>automattic.com</a> wrote:=
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Send wp-docs mailing list submissions to<br>
 =A0 =A0 =A0 =A0<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_=
blank">wp-docs at lists.automattic.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
 =A0 =A0 =A0 =A0<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-=
docs" target=3D"_blank">http://lists.automattic.com/<u></u>mailman/listinfo=
/wp-docs</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
 =A0 =A0 =A0 =A0<a href=3D"mailto:wp-docs-request at lists.automattic.com" tar=
get=3D"_blank">wp-docs-request at lists.<u></u>automattic.com</a><br>
<br>
You can reach the person managing the list at<br>
 =A0 =A0 =A0 =A0<a href=3D"mailto:wp-docs-owner at lists.automattic.com" targe=
t=3D"_blank">wp-docs-owner at lists.<u></u>automattic.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of wp-docs digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
 =A0 =A01. Re: Joining Forces: Support (Lorelle on WordPress)<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>-=
---------<br>
<br>
Message: 1<br>
Date: Tue, 15 May 2012 15:32:42 -0700<br>
From: Lorelle on WordPress&lt;<a href=3D"mailto:lorelleonwordpress at gmail.co=
m" target=3D"_blank">lorelleonwordpress@<u></u>gmail.com</a>&gt;<br>
Subject: Re: [wp-docs] Joining Forces: Support<br>
To: WordPress Documentation&lt;<a href=3D"mailto:wp-docs at lists.automattic.c=
om" target=3D"_blank">wp-docs at lists.<u></u>automattic.com</a>&gt;<br>
Message-ID:<br>
 =A0 =A0 =A0 =A0&lt;CAN2v4ZTr=3D<a href=3D"mailto:1q-ng3DtvrFS85jTR3zGYeWYR=
EB%2BqS6U3ykPZhuag at mail.gmail.com" target=3D"_blank">1q-<u></u>ng3DtvrFS85j=
TR3zGYeWYREB+<u></u>qS6U3ykPZhuag at mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;iso-8859-1&quot;<br>
<br>
I&#39;ve worked with some three person teams on many projects and love it f=
or<br>
that reason, Andrea. There are a LOT of plates to spin when it comes to the=
<br>
Codex. We&#39;ve never been able to get someone to coordinate the internati=
onal<br>
versions and I fear for what are on those pages, for example.<br>
<br>
The WordPress Meetup group here in Portland has asked me to do a WordPress<=
br>
Codex evening followed by a Codex Day. I&#39;ll be posting about that in a =
bit,<br>
and I&#39;d love to see more such projects from WordCamps and WordPress<br>
Meetups, too, and that takes some team coordination as well.<br>
<br>
Lorelle<br>
<br>
<br>
On Tue, May 15, 2012 at 12:57 PM, Andrea Rennick&lt;<a href=3D"mailto:andre=
a at ronandandrea.com" target=3D"_blank">andrea at ronandandrea.<u></u>com</a>&gt=
;wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Ideally a team of three. One is too few (what if they get busy? then it<br>
stalls), and two can disagree (another stall) while a third can be a<br>
tiebreaker if needed. Or a sane person, depending. :P<br>
<br>
I&#39;m just tossing out ideas here.<br>
<br>
a.<br>
<br>
<br>
On Tue, May 15, 2012 at 4:28 PM, Doug Sparling&lt;<a href=3D"mailto:doug.sp=
arling at gmail.com" target=3D"_blank">doug.sparling at gmail.<u></u>com</a>&gt;w=
rote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I like the idea as well.<br>
<br>
<br>
On Tue, May 15, 2012 at 2:22 PM, Lorelle on WordPress&lt;<br>
<a href=3D"mailto:lorelleonwordpress at gmail.com" target=3D"_blank">lorelleon=
wordpress at gmail.com</a>&gt; =A0wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This is so exciting. The Docs team has been walking on egg shells for<br>
years over the confusion of the WordPress Handbook, and I&#39;m eager to se=
e<br>
new energy being sent in this direction.<br>
<br>
The close ties between the Forum and Codex have been there since the<br>
beginning. However, time and skills serving the Forum and the time and<br>
skills serving documentation are distinctive, as several people mentioned.<=
br>
I agree that there needs to be one or two people overseeing the<br>
organizational structure, management, and maintenance of the Codex.<br>
<br>
Having a site of our own has been essential and lacking, which is why we<br=
>
created the unofficial docs task list not long ago. It was critical that we=
<br>
find a better way of communicating and keeping our community connected than=
<br>
the mailing list. As it was &quot;unofficial,&quot; we haven&#39;t done muc=
h to promote<br>
it or work with it, but it was a start. We need to have a place to support<=
br>
and educate each other on how to write for the Codex and offer task lists<b=
r>
beyond those we&#39;ve had in the past on the Codex, so I&#39;m excited abo=
ut<br>
having our own space or making the current blog on WordPress.com official.<=
br>
<br>
The mailing list has not been the sole line of communication either. As<br>
many do, I work with many people one on one to help them write and edit for=
<br>
the Codex and assign tasks, communicating with the mailing list when<br>
necessary for edits and such.<br>
<br>
As we struggled to understand the role the WordPress Handbook and<br>
WordPress Lessons played in the role of documentation in the WordPress<br>
Community, we&#39;ve come to realize the Codex best serves the WordPress<br=
>
Community by providing support for issues found within the Forums,<br>
expanding upon Learn WordPress instructions for the WordPress Lessons<br>
section, and developing more extensive documentation and guides beyond the<=
br>
basics found within the help files, especially servicing developers and<br>
programmers.<br>
<br>
While melding together Forum and Codex sounds great on the surface, I<br>
agree with Andrea and others that we need to have one or more people<br>
focused on the bigger picture overseeing the Codex, thus supporting the<br>
overall WordPress Community better.<br>
<br>
Thanks for the survey, Jane, and for helping with all of this.<br>
<br>
Lorelle<br>
<br>
<br>
<br>
<br>
<br>
On Tue, May 15, 2012 at 8:28 AM, Andrea Rennick&lt;<a href=3D"mailto:andrea=
@ronandandrea.com" target=3D"_blank">andrea at ronandandrea.<u></u>com</a><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
wrote:<br>
It makes totally sense, because Support&amp; =A0Docs are two sides of the<b=
r>
same coin. :) If users can&#39;t understanding docs or can&#39;t find them,=
 they<br>
post in the forums. ;P<br>
<br>
Better docs mean less support issues, because people don&#39;t scale. And<b=
r>
the people answering questions are the first ones who see the need for new<=
br>
docs. Because they answer the same questions over and over (and over) again=
.<br>
<br>
Getting people to read docs is a separate issue, but having support and<br>
docs work hand in hand in tandem is a big first step.<br>
<br>
I think half the people overlap anyway, yes?<br>
<br>
a.<br>
<br>
<br>
On Tue, May 15, 2012 at 11:51 AM, Chip Bennett&lt;<a href=3D"mailto:chip at ch=
ipbennett.net" target=3D"_blank">chip at chipbennett.net</a>&gt;<u></u>wrote:<=
br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Personally, I love the idea. Speaking as a contributor group member<br>
who tries to keep in the loop regarding support and/or Codex issues that<br=
>
impact our group (or issues where our contributor group can be helpful),<br=
>
such consolidation is welcome.<br>
<br>
Chip<br>
<br>
<br>
On Tue, May 15, 2012 at 7:09 AM, Jane Wells&lt;<a href=3D"mailto:jane at autom=
attic.com" target=3D"_blank">jane at automattic.com</a>&gt;<u></u>wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi everyone. The results of the recent surveys to identify active<br>
contributors and elect team reps made it pretty clear that the docs team is=
<br>
in a bit of a slump, organizationally speaking. Only 5 people from the<br>
wp-docs post responded, and of those, 2 were new or not yet contributing,<b=
r>
and there was no consensus re reps among the remaining 3 respondents. It<br=
>
got me thinking about how we organize contributors, what has worked well<br=
>
elsewhere in the WP ecosystem and in other free software projects, and<br>
leads me to this proposal: what if we combined forums and docs into one<br>
Support team?<br>
<br>
Looking back at the Codex activity from the past six months or year,<br>
chunks of it have been tied to forum mods (like Ipstenu and Andrea_r),<br>
other contributor groups (like Chip on the Theme Review Team), and new<br>
releases. Not that how Automattic/WordPress.com organizes itself should<br>
decide anything, but their support team manages forums, email support, and<=
br>
docs, and it seems to work pretty well. They have a schedule for reviewing<=
br>
existing documentation so it never gets too far out of date, and the people=
<br>
on the front lines with users in the forums and via email can see very<br>
clearly where they need to beef up documentation. I&#39;m thinking this cou=
ld<br>
work well for .org, too. Those who are strong writers and just want to<br>
contribute to documentation could still do so, but within a context of what=
<br>
our user support needs are at any given time based on the actual support<br=
>
requests.<br>
<br>
What I&#39;m envisioning is less siloing of contributor personnel, with<br>
one group blog at <a href=3D"http://make.wordpress.org/support" target=3D"_=
blank">make.wordpress.org/support</a> that uses tags like<br>
forums and codex to organize posts, and has pages to help orient new<br>
contributors and get them started. These mailing lists could fade away in<b=
r>
favor of email subscriptions from the blog, which are more easily<br>
searchable and would be more visible to potential contributors. Within the<=
br>
uber-group, some people would naturally gravitate toward specific tasks<br>
while others would multi-task as they have been doing.<br>
<br>
Over time we could expand the purview of the group to include things<br>
like moderating instructional videos and comments at <a href=3D"http://word=
press.tv" target=3D"_blank">wordpress.tv</a>(and start embedding appropriat=
e videos into codex), possibly helping to<br>
staff in-person help desks in local communities and/or at events like<br>
WordCamps and Meetups, etc. I think the prospects are pretty exciting, and<=
br>
I could see this becoming the biggest and most active of all the<br>
contributor groups, which would be awesome.<br>
<br>
If there are any strong objections to this approach, please reply to<br>
this thread today so we can discuss. If not, and everyone is willing to<br>
give this a shot and all work together (at least as an experiment for, say,=
<br>
the next release cycle or two), I&#39;ll go ahead and set up the group blog=
<br>
tomorrow.<br>
<br>
Jane<br>
______________________________<u></u>**_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/**mailman/listinfo/wp-docs" target=
=3D"_blank">http://lists.automattic.com/**<u></u>mailman/listinfo/wp-docs</=
a>&lt;<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" targ=
et=3D"_blank">http:<u></u>//lists.automattic.com/<u></u>mailman/listinfo/wp=
-docs</a>&gt;<br>

<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
<br>
<br>
</blockquote>
<br>
--<br>
--<br>
Andrea Rennick, <a href=3D"http://wpebooks.com" target=3D"_blank">http://wp=
ebooks.com</a> and <a href=3D"http://ronandandrea.com" target=3D"_blank">ht=
tp://ronandandrea.com</a><br>
Co-author of WordPress All-In-One For Dummies <a href=3D"http://rml.me/aio"=
 target=3D"_blank">http://rml.me/aio</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
<br>
<br>
</blockquote>
<br>
--<br>
--<br>
Andrea Rennick, <a href=3D"http://wpebooks.com" target=3D"_blank">http://wp=
ebooks.com</a> and <a href=3D"http://ronandandrea.com" target=3D"_blank">ht=
tp://ronandandrea.com</a><br>
Co-author of WordPress All-In-One For Dummies <a href=3D"http://rml.me/aio"=
 target=3D"_blank">http://rml.me/aio</a><br>
<br>
<br>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
<br>
<br>
</blockquote>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:&lt;<a href=3D"http://lists.automattic.com/pipermail/wp-docs/attachment=
s/20120515/560f5849/attachment-0001.htm" target=3D"_blank">http://lists.aut=
omattic.<u></u>com/pipermail/wp-docs/<u></u>attachments/20120515/560f5849/<=
u></u>attachment-0001.htm</a>&gt;<br>

<br>
------------------------------<br>
<br>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
<br>
<br>
End of wp-docs Digest, Vol 80, Issue 10<br>
******************************<u></u>*********<br>
</blockquote>
Hello, I would like to know how I get involved in helping out in the Wordpr=
ess community?<br>
<br>
Thanks<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Wayne Hatter<br>
______________________________<u></u>_________________<br>
wp-docs mailing list<br>
<a href=3D"mailto:wp-docs at lists.automattic.com" target=3D"_blank">wp-docs at l=
ists.automattic.com</a><br>
<a href=3D"http://lists.automattic.com/mailman/listinfo/wp-docs" target=3D"=
_blank">http://lists.automattic.com/<u></u>mailman/listinfo/wp-docs</a><br>
</font></span></blockquote></div><br>

--20cf3074b31cedcca904c133d865--