documenting l.d.o, where should it happen?

[Gábor Hojtsy]

Hi,

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?

Gábor
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/

[Jennifer Hodgdon]

I would vote for putting it into the d.o Handbook, to keep all the
docs in the same place.

--Jennifer

Post by Gábor Hojtsy
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?

[John Noceda]

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)

I would vote for putting it into the d.o Handbook, to keep all the docs in
the same place.
--Jennifer

Post by Gábor Hojtsy
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/

[Marcello Testi]

Post by John Noceda
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.

We have one also for Italian: http://www.drupalitalia.org/glossary
It's linked from every translation page in l10n.drupalitalia.org and I
think it should be a default item for every translation team.
So I think the glossary should be a feature of l10n server; or, as
interim solution, language admins should be able to manage a block/
menu with links to reference regarding their own language.
As for other docs, while content-wise their best place would be in the
handbook, again there must be something for local teams to manage
visibility of such docs from any part of the translation interface.

Ciao.
Marcello.

--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/

[Gábor Hojtsy]

Post by Marcello Testi

Post by John Noceda
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.

We have one also for Italian: http://www.drupalitalia.org/glossary
It's linked from every translation page in l10n.drupalitalia.org and I think
it should be a default item for every translation team.
So I think the glossary should be a feature of l10n server; or, as interim
solution, language admins should be able to manage a block/menu with links
to reference regarding their own language.

Translation teams of course have a queue of nodes in the organic group
on l.d.o with sticky nodes displayed on top on the translation
overview page for their language.

Gábor
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/

[Jennifer Hodgdon]

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

Post by John Noceda
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)

I would vote for putting it into the d.o Handbook, to keep all the docs in
the same place.
--Jennifer

Post by Gábor Hojtsy
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/

[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

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

Post by John Noceda
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)

I would vote for putting it into the d.o Handbook, to keep all the docs in
the same place.
 --Jennifer

Post by Gábor Hojtsy
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/

--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/

[Gábor Hojtsy]

Post by John Noceda
We rewrote docs regarding contributing to translations a few months back....
under the Getting Involved handbook (Translate Drupal to your language).
There are already existing subpages like How to contribute using a
localization server and Translation guidelines, etc. We probably need to
rewrite them again.

Yeah. Started to rewrite at http://drupal.org/contribute/translations
But of course since some deep links require modifications in
themselves, it is not entirely perfect yet.

Gábor
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/

[Hilde Austlid]

Hi!
I think the best place for this kind of documentation is in the d.o
handbooks. If you're new to Drupal and want to help, you'll
(hopefully!) look there, under "Getting involved". You won't look for
the localization server until you learn that it exists.

Currently "How to contribute using a localization server"
(http://drupal.org/node/302194) is outdated, and "How to set up a
localization server" (http://drupal.org/node/302196) should probably
be moved to docs for the contrib module l10n_server, as it's not
relevant for people who want to get involved with Drupal translations
anymore. I started those pages, but am pretty busy these days, so
right now I'll stay on the sidelines and applaud anyone who does the
next update :-)

Hilde (zirvap on d.o)
--
Pending work: http://drupal.org/project/issues/documentation/
List archives: http://lists.drupal.org/pipermail/documentation/