[documentation] String freeze Dec 1st!

Boris Doesborg bdoesborg at gmail.com
Sat Nov 28 08:47:55 UTC 2009


Steve,

All the help-file texts of the modules that will appear in Drupal7 are
being reviewed, discussed and improved via this issue queue :

http://drupal.org/project/issues/search/drupal?text=&assigned=&submitted=&participant=&version[]=7.x&issue_tags_op=or&issue_tags=d7help

You can review the texts and submit improvements in the comments
section of each issue.

Each issue includes screenshots that show what the result will look
like after the suggested text changes are applied.

Go check out the queue.

Boris.

2009/11/28 Ariane Khachatourians <arianekhachatourians at gmail.com>:
> Hi Steve -
>
> I'm not sure I totally understand what you're asking, ie. what part of the
> process you need more info about.
>
> That said - if you think that a section of text needs updating, you can post
> an issue for it on the issue queue http://drupal.org/node/add/project-issue
> and post a patch there. If it's a major change (not just fixing a
> grammatical error), it will need to be discussed/reviewed/okayed by other
> members of the doc team or whoever works on that project.
>
> This Tuesday is a deadline for changing strings though, so that translators
> can start their work, so the patch would have to be reviewed and committed
> by then if it is more than just a bug.
>
> Hope that helps,
> Ariane
>
>
>
> On Fri, Nov 27, 2009 at 9:24 AM, Steve Kessler <skessler at denverdataman.com>
> wrote:
>>
>> How do we submit patches for specific strings...like the explanation of
>> cron
>> on admin/config/system/site-information
>>
>> Thanks,
>> Steve
>>
>> Steve Kessler
>> Denver DataMan
>> 303-587-4428
>> Sign up for the Denver DataMan Free eNewsletter
>>
>>
>> -----Original Message-----
>> From: Jennifer Hodgdon [mailto:yahgrp at poplarware.com]
>> Sent: Thursday, November 19, 2009 10:36 PM
>> To: A list for documentation writers
>> Subject: [documentation] String freeze Dec 1st!
>>
>> Hello Doc Team,
>>
>> I just want to say first how exciting it has been that so many of you
>> pitched in to help with the help system overview! Tremendous progress
>> has been made; now it's mostly a matter of reviewing/updating patches
>> and getting them committed. See http://drupal.org/node/537828 if you
>> are curious about what's been happening and get involved.
>>
>> Anyway... I found out today that the upcoming User Experience (UX)
>> freeze for Drupal 7 is also supposed to include a "string freeze".
>> Which is to say, all of the text within Drupal 7 that needs to be
>> translated (help text and user interface text) is supposed to be
>> frozen on December 1st -- less than 2 weeks away -- aside from "bugs"
>> (which after December 1st means just spelling and minor grammatical
>> errors, not totally rewriting or rearranging). That includes the D7
>> help effort!
>>
>> So, I would like to suggest that both programming and non-programming
>> members of the Drupal Documentation team (this means you, if you are
>> subscribed to this email list) -- if you have some free time between
>> now and December 1st, you can try:
>>
>> a) Installing Drupal 7 (you can download the latest version at
>> http://drupal.org/project/drupal if you are not using CVS) and
>> reviewing the text you see on its user interface and help. My
>> suggestion is to enable all of the core modules (especially the Help
>> module), try out some of the features/tasks/screens, and if you find
>> something in the user interface that doesn't make sense, file an issue.
>>
>> Hints on filing an issue:
>> - Start from http://drupal.org/node/add/project-issue/drupal
>> - Version: 7.x
>> - Component: The module or theme the problem is in, or "documentation"
>> if it is in a help file.
>> - Category: Bug report
>> - It is very helpful to put in a good summary in the Title, and a full
>> description of the problem you saw, where you saw it (what screen --
>> give the Drupal path), when you saw it (if you had to enter or do
>> something to get this bad text to appear), why you think it is bad,
>> and if possible your suggested better text.
>>
>> b) Reviewing proposed patches. Search using the Advanced Search
>> interface starting at http://drupal.org/project/issues/search/drupal
>> for issues that have status "needs review", version 7.x, and one of
>> the following:
>> - Tagged with "ui-text" [without the quotes, of course]
>> - Tagged with "Help text"
>> - Tagged with "d7help"
>>
>> Hints on patch review:
>> - Even if you are not a programmer, you can still review the text in
>> these patches. Scroll down to the bottom of the issue's comments, and
>> find the latest patch attachment. Click on the attachment, and the
>> lines with + are being added, lines with - are being removed.
>> - If you think the patch is good, add a comment saying what part you
>> reviewed and that you thought it was good.
>> - If you think the patch needs some work, change the status of the
>> issue to "needs work", and add a specific comment about what you think
>> should be changed (if possible, with a suggestion of what to change it
>> to).
>>
>> c) Participate in the D7 Usability sprint this weekend if you can:
>> http://webchick.net/node/72
>>
>> Thanks, and keep up the good work!
>>
>>    --Jennifer
>>
>> ps: If you need help with filing issues or reviewing patches, you can
>> get advice from the doc team on our IRC channel - #drupal-docs. See
>> http://groups.drupal.org/node/2326 for info on IRC if you don't know
>> how to connect. There are also useful links on
>> http://drupal.org/node/540308
>>
>> --
>> 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/
>
>
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/
>



-- 
boris


More information about the documentation mailing list