[documentation] documenting l.d.o, where should it happen?

[Gábor Hojtsy]

Yes, and the localization API docs are sure to kept on the drupal.org
docs IMHO, they are of interest for developers not much for
translators.

Gábor

On Sun, Sep 20, 2009 at 5:59 PM, Jennifer Hodgdon <yahgrp at poplarware.com> wrote:
> If you want all the localization doc to be on l.d.o, I could get behind that
> -- if you move *all* the translation/localization doc there. What I would
> like to see avoided is having some doc in one place and some in the other,
> because then people will start to duplicate documentation (not realizing the
> other spot already has the doc they are writing).
>
>   --Jennifer
>
> John Noceda wrote:
>>
>> We rewrote docs regarding contributing to translations a few months
>> back....
>> under the Getting Involved handbook (Translate Drupal to your
>> language<http://drupal.org/contribute/translations>).
>> There are already existing subpages like How to contribute using a
>> localization server <http://drupal.org/node/302194> and Translation
>> guidelines <http://drupal.org/node/13220>, etc. We probably need to
>> rewrite
>> them again.
>>
>> Basing from experience of being a maintainer of 3 translation projects and
>> maintaining separate translation servers for these, there are actually a
>> lot
>> of useful things we need for the localization docs but the most important
>> factor is that it must be in a central place IMHO. Translators/Local
>> communities already have to go to at least 3 places just to get updated on
>> translation work. They go their respective groups on g.d.o, their local
>> community website, translation project pages, and now l.d.o.
>>
>> A wordlist, for example, helps a lot for the consistency and
>> standardization
>> of Drupal-related words. More explanation on this can be found on
>> http://drupal.org/node/13220 and sharing this to the whole international
>> community would be very beneficial, I think.
>>
>> Personally, it's hard for me to give my vote or suggestion on where it
>> should be placed. As a docs person, I will vote for the d.o. handbooks
>> because simply.... it's docs. But on the other hand, being part of 2 local
>> communities, I would like to have everything on l.d.o so all the
>> information
>> I need about translations are on 1 place. If its on different locations, I
>> can imagine myself checking d.o. then i will see other interesting things
>> and topics, then I will read about that instead and i have totally
>> forgotten
>> about translating, again :-)
>>
>> John
>> (JohnNoc)
>>
>>
>>
>>
>> 2009/9/19 Jennifer Hodgdon <yahgrp at poplarware.com>
>>
>>> I would vote for putting it into the d.o Handbook, to keep all the docs
>>> in
>>> the same place.
>>>
>>>  --Jennifer
>>>
>>> Gábor Hojtsy wrote:
>>>
>>>> I'm thinking about extending the current localize.drupal.org FAQ with
>>>> more information for people. I'd envision a collaborated documentation
>>>> interface, where people could help out and we'd use a book module
>>>> hierarchy. Now, I was thinking setting  this up on localize.drupal.org
>>>> might be counterproductive to the docs effort, and we might as well
>>>> just set up a section in the d.o handbooks and collaborate there.
>>>> After all, all l.d.o users have a d.o account, so they could easily
>>>> contribute there. What do you think?
>>>>
>>> --
>>> Jennifer Hodgdon * Poplar ProductivityWare
>>> www.poplarware.com
>>> Drupal, WordPress, and custom Web programming
>>>
>>>
>>> --
>>> Pending work: http://drupal.org/project/issues/documentation/
>>> List archives: http://lists.drupal.org/pipermail/documentation/
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> --
>> Pending work: http://drupal.org/project/issues/documentation/
>> List archives: http://lists.drupal.org/pipermail/documentation/
>
>
> --
> Jennifer Hodgdon * Poplar ProductivityWare
> www.poplarware.com
> Drupal, WordPress, and custom Web programming
>
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
>