Current state of Perl 5 Documentation Team

[Maik Hentsche]

Hi,
I read that you wanted to form a Perl 5 Documentation team. The mailing
list archive shows a lot of activity at the beginning of July but since
then nothing more occurred. Now several deadlines expired without any
update. Does that mean the Perl 5 Documentation team was closed down
again or is this simply a lack of information?

Thanks for your information, so long
Maik Hentsche

[Chas. Owens]

Simply a lack of communication and my missing the deadlines I
announced (they make such a wonderful sound when they go whizzing
past).

Currently a bunch of people are working on getting perlopquick into
shape to replace perlop and I am slowly applying them. You can follow
the progress on [GitHub][0].

If you want a task, just speak up, there is still lots to do.

[0]: http://github.com/cowens/perlopquick

--
Chas. Owens
wonkden.net
The most important skill a programmer can have is the ability to read.

[Naveed Massjouni]

I would like a task.
Thanks,
Naveed

[Ali Nabavi]

On Sat, Aug 7, 2010 at 10:42, Chas. Owens <chas....@gmail.com> wrote:

Currently a bunch of people are working on getting perlopquick into

shape to replace perlop and I am slowly applying them.  You can follow
the progress on [GitHub][0].

If you want a task, just speak up, there is still lots to do.

Yes, please!  Perl novice, but would like to get involved.  :-)(

-Ali

[Chas. Owens]

On Sat, Aug 7, 2010 at 16:30, Naveed Massjouni <nave...@gmail.com> wrote:
snip

> I would like a task.
> Thanks,
> Naveed
>

The thing we need most right now is for people to read
[perlopquick][0] on [GitHub][1] and find any errors, inconsistencies,
or unclear explanations.

Read about an operator, play with it, make sure it does what the text
describes, test the examples. Post your questions or approvals to the
list for each operator.

[0]: http://github.com/cowens/perlopquick/raw/master/perlopquick.pod
[1]: http://github.com/cowens/perlopquick

[Chas. Owens]

On Sat, Aug 7, 2010 at 11:03, Maik Hentsche <ma...@mm-double.de> wrote:
> "Chas. Owens" <chas....@gmail.com> wrote:
>
>> If you want a task, just speak up, there is still lots to do.
>

> I do. I'm not a native speaker so a little help with phrasing certain
> things would be welcome. Do we already have an IRC channel?
snip

I don't tend to use IRC for some unfathomable reason. This list or
contacted me directly is the best way to get a hold of me.

The thing we need most right now is for people to read
[perlopquick][0] on [GitHub][1] and find any errors, inconsistencies,
or unclear explanations.

Read about an operator, play with it, make sure it does what the text
describes, test the examples. Post your questions or approvals to the
list for each operator.

[0]: http://github.com/cowens/perlopquick/raw/master/perlopquick.pod
[1]: http://github.com/cowens/perlopquick

[Chas. Owens]

The thing we need most right now is for people to read

[perlopquick][0] on [GitHub][1] and find any errors, inconsistencies,
or unclear explanations.

Read about an operator, play with it, make sure it does what the text
describes, test the examples. Post your questions or approvals to the
list for each operator.

[0]: http://github.com/cowens/perlopquick/raw/master/perlopquick.pod
[1]: http://github.com/cowens/perlopquick

[Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯]

> I don't tend to use IRC for some unfathomable reason. This list or
> contacted me directly is the best way to get a hold of me.

IRC is about many-to-many communication; much more often I'd like to discuss
something with fellow documenters for which mail is not suitable.

I suggest we join MagNET #p5p <irc://irc.perl.org/p5p>. This has the advantage
that the experienced established users there can help out spotting technical
errors.

I know that channel and I don't think that the IRC-affine faction of the docs
team is large enough to become a burden due to increased message volume, but
in that case then there's always the possibility to establish a new one, e.g.
#docs.

Chas, I'd like you to pick a channel and bless it as official for use of the
docs team even if you won't use it.

[Leon Timmermans]

There is already #perldoc. It isn't very busy right now, mostly
translation of documentation and such. We could reuse that one too
I suppose.

Leon

[Ævar Arnfjörð Bjarmason]

I think the point was to use #p5p so that the docs team isn't sitting
in its own corner on #perldoc.

I signed up for this list and check it every once in a while when I
think "hey, I wonder what those docs guys are doing". Here's how you
(IMO) could fix some of that:

* Use existing communication channels (like #p5p) whenever
possible. #perldoc isn't so high traffic that #p5p can't take it,
and you'll get valuable feedback.

* Try to get patches in early and often. I see there's a
perlopquick.pod being worked on, that should:

* Be in a fork of the mirrors/perl repo on GitHub, so that it can
be easily merged back.

* Probably be in perl.git already, it looks good enough to me.

</me telling other people what to do>