On Mon, Aug 9, 2010 at 14:12, Leon Timmermans <faw...@gmail.com> wrote:
> On Sun, Aug 8, 2010 at 9:00 PM, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 <da...@cpan.org> wrote:
>>> 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.
>>
>
> 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.
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>
