Changes between Version 5 and Version 6 of projects/internationalization

Jan 16, 2012, 8:41:11 AM (9 years ago)
Enrique Rosas



  • projects/internationalization

    v5 v6  
    11This page will guide us through our transition to a bilingual organization.
    3 === First Meeting Agenda: December 2, 2011 @ 5pm Eastern / 4pm Central ===
     3=== Notes taken from each meeting ===
    5 (Meeting on Skype)
     5[wiki:/projects/internationalization/20111220_meeting Second Meeting: December 20, 2011]
    7 == Notes from Internationalization Meeting ==
     7[wiki:/projects/internationalization/20111202_meeting First Meeting: December 2, 2011]
    9 * Background on the collaboration between LaNeta and MF/PL:
    10 In addition to the technical merger and language stuff, we're also
    11 trying to address what does it mean political and cultural ofr an
    12 organization based in the united states that has a few international
    13 members that is going to get for the first time 50 to 100 members in
    14 Mexico, changing significantly our organization.
    16 Concerns with MF/PL about capacity and political vision from leadership
    17 within MF/PL and with LaNeta members. The internal debate is about
    18 international work fundamentally and the continuation of an internal
    19 struggle tha twe're used to.
     10=== Call for volunteer work on MFPL's translation team ===
    21 LaNeta's concerns were presented by Enrique. The main concern is how can
    22 the people in Mexico get support, the day-to-day work. Also, there is a
    23 more long-term expectation about a democratic space that could be
    24 developed so all of the members can exchange their points of view.
    25 Regional meetings of membership groups could take place before the MF/PL
    26 membership meeting as a way to focus on the main ideas from the Mexican
    27 members to try to express them more effectively in a general assembly.
    28 Alfredo pointed out one big challenge that the diversification and
    29 internationalization of MF/PL makes MF/PL members knowing one another
    30 intimately much more difficult. The internationalization team has to
    31 recognize not only the job immediately before us of daily commnication,
    32 but the entire vision of bringing us all together.
     12[wiki:/projects/internationalization/call_volunteers Call for volunteers in Lowdown bulletin of January 2012]
    34 * General challenges and bigger pictures
    35 Building trust to buy into the idea to continue cooperation based in
    36 history and building. Both sides have to believe that the other are very
    37 solid. The cultural things need to be brought forward more. Is there a
    38 way to do the actual transfer of the server and technology stuff low-key
    39 so that we can do the cultural brokering piece to give people an
    40 opportunity to work together. The majority of the membership is in
    41 Mexico City that could give us time to figure out how to bring people
    42 together, which might culminate in a meet-and-greet.
    44 > > LaNeta went through a process to decide to work with MF/PL in a
    45 community meeting in which Ross was present.
     15=== Planning the work in MFPL's translation team ===
    47 It's important that everything be equal on both sides of the language
    48 issue. Integrating different source material into Spanish, or being
    49 up-front during the process of migrating the content into Spanish is a
    50 priority but a reasonable amount of time. When you enter the website
    51 that isn't actually fully translated, it can be frustrated. We have to
    52 have an explicity plan for that.
     17[wiki:/projects/internationalization/call_volunteers Call for volunteers in Lowdown bulletin of January 2012]
    54 Everything that gets posted is already ready to go in terms of both
    55 English and Spanish, not the Spanish later on.
    57 It's easy to segregate people linguistically. If our goal is to
    58 integrate our organizations into one on a culturally deep level, it's
    59 okay to have all of our communication to have everything English/Spanish
    60 jammed together. Everyone gets the same thing because it's one
    61 organization. They get two messages and are free to disregard the
    62 language that they can't read.
     20=== Workflow for translations to main web site ===
    64 > > Enrique agrees based on his experience working with language diversity
    65 within Indigenous groups in Mexico.
     22[wiki:/projects/internationalization/workflow workflow]
    67 Add bi-lingualism to all of our existing help nodes and documentation,
    68 where necessary. Be upfront.
    70 * Major Pieces
    71 - Broadcast Communications (mallory)
    72 - (mallory)
    73 - interface and content-plugin (ross)
    74 - (jamie)
    75 - Meetings face-to-face in Mexico with MF/PL people
    76 - Organizing translation team (enrique) and [wiki:/projects/internationalization/workflow workflow] (mallory)
    77  -- Scheduled communications
    78  -- First-time sweep of content online
    79  -- Ongoing updates, flagging outdated translations
    80  -- Emergency communications: templates
    82 * Plan
    83 - Jamie is going to get Roberto a list of members to help him recruit a
    84 translation team
    85 - Roberto is going to write a LD article on our internationalization plans
    86 - Ross is going to recruit dkg to help with Trac internationalization
    87 - Mallory's going to work on a translation workflow
    88 - Jamie's got some lone coding to do with red
    89 - Next meeting on December 20th (tentative) at 5pm Eastern / 4pm Central
    90 to discuss timeline and report back on the progress we've made on our tasks.
    92 - Enrique also took notes in Spanish on the wiki page.
    94 1. Sitio web principal
    95  * sitio está listo para la internacionalización, ahora todo el contenido puede presentarse en inglés o en español, la
    96  * un criterio que debe ser considerado es que siempre que sea posible publicar contenido en ambos idiomas.
    98 2. Sitio de soporte
    99  * trac, para traducir la interfase es necesario actualizar la versión y agregar el idioma que por ahora está en variante argentino y español de España
    100  * podríamos hacer los ajustes a alguna de estas variantes y hacer
    102 3. Panel de control
    103  * El panel de control fue desarrollado por Jamie y confía en que éste pueda ser traducido con relativa sencillez.
    105 4. Service-advisories
    106  * son enviados en cuestión de minutos y la traducción podría ser adelantada a través de plantillas en español
    108 5. Trabajo de interpretación en los espacios de toma de decisión