See below please.
On 20 October 2012 22:21, Rob Weir <[email protected]> wrote: > On Fri, Oct 19, 2012 at 2:41 PM, jan iversen <[email protected]> > wrote: > > As agreed with Rob, I have put together a list of information, that would > > have me problems and time for all those that helped me. > > > > This list is just a starting point (all the information is out there, so > it > > should just be a list with links) > > > > Suggested reading for all volunteers: > > - Where do I find information (wiki, cwiki, mailing lists) ? > > - What can I do to help ? > > - How is the organization (contributor, committer etc....all the way up) > ? > > - Who is who ? (It would be good to have a list of the key persons) ? > > - What are our relationship to other openOffice packages (can I use my > > contribution elsewhere) ? > > > > OK. The above corresponds to what I've been calling "level-1" (until > I find a better term). The documentation for this is in progress, > > Suggested reading for Wiki contributors > > - Which writing rules do we have (do I change a page directly or use > talk) > > - How is the content controlled, basically I can write anything, are > there > > any QA ? > > - How is the structure of Wiki ? (and temporary, which parts are old and > > outdated) ? > > - Who do I contact if I have problems/questions/need guidance ? > > > > Personally I think of the wiki as a tool, not a role. So developers, > QA, translators, support, doc, we all use the wiki and contribute > content. It is a general skill, something I might put in a general > "level-2" doc. > You are right, that is not part of the first stumping steps, and it is a general skill. > > > Suggested reading for a translator > > - Where do I find correct information about localization (some wiki pages > > are misguiding, and l10n.openoffice.org is NOT a good starting point) > > - Where can I see status of the ongoing translations ? > > . Which tools do I need and how do I use them (any standards) ? > > - Who do I contact to get started ? > > > > Now we get to the meat of it. Or the tofu of it, if you are vegetarian ;-) > Each volunteer has their own particular interests, and it is a little > dangerous to generalize, but I think in practice these are the common > profiles: > You are right in dividing the volunteers, and I think the majority are class 1, but might grow into the other classes. > > 1) Volunteer wants to help maintain a translation of AOO for their > language. They don't desire broader engagement with the project. In > fact they find the traffic level on the lists annoying. They might > pop in once or twice during the development of a release, but in > general are not engaged with the project. > maybe l10n.openoffice.org would be a perfect media for them. We could use that place to show ongoing translation, have pointers to to country specific wiki information and contact mails. > > 2) Volunteers who want be more engaged with enabling AOO for their > locale. So they help maintain the translation, but also an NL > website. They might help on an NL discussion forum. They might > control a NL-specific Twitter account or Facebook page. They might > help organize local events related to AOO. In their country, they are > "Mr. OpenOffice". So such a volunteer is cross-functional, but > focused on activities related to that single language. > This type will for sure want to participate on the l10n mailing list and on country specific pages. I think for class 1,2 we need active country specific wiki pages, which has a local part (maintained by themself) and a general part where development/integrators can write news concerning the process (this could be l01n.openoffice.org) > > 3) Volunteers interested in the general internationalization process > with the project. So not just a single language, but end-to-end, > including the parts that intersect with the programmers and admins. > They define and support the processes and tools that support the > localization volunteers. > That sounds like me :-) These need to be fully integrated (excuse my wording), they will eventually also discuss development themes. I think however if we have documents for 1,2 then 3 would be a lot a question of guidance. I had a good experience some years ago in another project. When you had shown that you were serious (going through your 1,2 and showing good intentions) you were "connected" with a mentor, who helped answer your questions and helped you understand the process. That way the person did not have to send embarrassing questions to the mailing list. Would something like that work for us ?? (I would for sure like it). > > So it might make sense to split this into two "levels" (until I find a > better word!), one focused on localization. They don't need to > understand the tools and SDF files and the messiness that occurs > behind the scenes. They just need to know how to get the files to > translate, how to translate, how to submit the translations, and how > to get a test build to verify the translation. So it is a loop of > translate-test-fix. > +1 > > My group 2 above would benefit from further documentation about > marketing, about website design, etc., but that is best covered by > those groups. It is not really a localization question. > +1 > > Group 3 volunteers -- that involves procedures that are not fully > defined and which require manual intervention. So I think we'll be > documenting and improving in parallel. > Or use mentors ? > > The big question we should ask ourselves is this: when do we feel > good enough about our documentation for localization voluntees that we > can do a broader "call for volunteers" on the website? If next week > we had 10 volunteers introduce themselves on the mailing list, for 10 > different languages, could we handle it? I don't think so, not > without a great deal of confusion. So I think we need two basic > things: > 1) Accurate, current documentation for volunteers that are focused on > translating. > YES, that is an issue we need to address AFTER we have the new workflow in place. Today it would be very hard to do! > > 2) A more automated way to process PO files, so we don't drive > Juergen, our Release Manager, crazy with requests for special > translation builds. Maybe if we can get to a steady heart beat of > snapshot builds (say every week or every two weeks) we can > automatically include any updated translation in that build? > I am happy to tell you, that my proposal will remove all the manual point, and has a direct coupling between developer and translator (online). However I already know that it will be a hurdle to get a decision on it...because it changes a couple of "stones", just to mention one: I suggest that the only repository is SVN, and pootle gets files directly from that. Also in my suggestion is the snapshot build, which needs to be regularly (I cannot determine if 1 or 2 weeks is correct), that is the latest point where text would be available to the translators. My document is hopefully ready monday. One item is still outstanding, if it was 10 new languages it is totally out of the scope of my document ! I am working on l10n.openoffice.org, but that will take sometime before I have a proposal. > > > Suggested reading for a tester > > - How can I help testing ? > > - Is it possible to test in my native language ? > > - Which tools do I need ? > > - How do I report bugs ? > > - Who do I contact, if I want to be a tester ? > > > > Suggested reading for a developer > > - Where do I find guidance on how to write a source code (naming > standards > > etc.) ? > > - Where do I find build instructions (I found 5 different for > Ubuntu...the > > last one was pretty good, but I still had to ask on dev for the last bit > (a > > simple flag was wrong)) > > - Where do I find source ? > > - When do I need to use the sources, and when to use extensions ? > > - Where do I find the bug reporting system ? > > - How can I "reserve" a bug for me to solve ? > > > > > > Then of course as you grow more into the community you get more questions > > (like CMS etc), but I think to cover that would be too much. >
