[libreoffice-projects] Re: Workflow between dev, UX and l10n teams
Hi, Le 30 janv. 2015 12:25, Lionel Elie Mamane lio...@mamane.lu a écrit : On Fri, Jan 30, 2015 at 12:14:04PM +0100, Bjoern Michaelsen wrote: On Fri, Jan 30, 2015 at 10:06:36AM +0100, Lionel Elie Mamane wrote: Interestingly, doing a web search for pootle git synchronisation leads me to http://weblate.org/en/features/ :-) Well, once we dont require to be self-hosted anymore, https://translations.launchpad.net/ certainly would be an option too. However, IMHO there are very good reasons to be self-hosted with translations. From glancing at the webpage, Weblate is a software that we can host ourselves. This is something the l10n team has already in his radar. But please, before changing our tool and our workflow, let's discuss at Fosdem with Dwayne from the Pootle team what we can achieve. Cheers Sophie -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] Re: [libreoffice-l10n] Re: Workflow between dev, UX and l10n teams
Hi Rimas, all Le 27 janv. 2015 19:32, Rimas Kudelis r...@akl.lt a écrit : Hi Jan, 2015.01.26 16:43, Jan Holesovsky rašė: Mihovil Stanić píše v Po 26. 01. 2015 v 10:25 +0100: Cosmetic changes (~ to _ or Status to Status: or ... to … or those different quote styles I don't even have on my keyboard) and anything similliar - NOT OK if you don't script it for all languages Cosmetic changes (Big brown fox - Big Brown Fox) - NOT OK at all, change just for en_us, don't change my strings and don't even notify me you did it in en_us I see 2 problems here: 1) There is no tool that would detect these trivial changes, and would act accordingly. Regarding 1) - I thought that Pootle is detecting the trivial changes some way, and offering the original translation. Is it not? What can be done to improve that, so that for translators it is just a matter of checking; not a matter of translating? [Or even what you suggest - that it would just update the source strings without touching the translations?] Pootle does offer the original translation, but the localizer still has to approve it. Furthermore, Pootle does not apply any automatic changes. If you had e.g. Some ~string, and you change it to Some _string, Pootle will show the original translation as a hint, but the user will still have to port this trivial change to the translation manually. Needless to say, sometimes these minor differences avoid being noticed by the localizers, which results in errors in the locale (I've seen incorrect access key identifiers in the menus at least once). However, while you are correct that there is no tool to detect these changes, I don't think there has to be. The person who implements the change knows better than anyone whether or not it can be automated, perhaps they even automated it themselves. For example, I seriously doubt that somebody went over all L10n files and changed triple dots to ellipses manually, this was most likely a scripted change. Same, or very similar, script would have probably worked with all other locales, but I guess that person simply didn't think about it. Similarly, changes in used quote characters most likely could have been isolated and transplanted to locales. Adding colons to certain strings only would probably have been slightly more difficult, but still scriptable. And none of that requires any tool to detect trivial changes... ;) That's the point of this discussion, thanks Rimas to make it :-) L10n team can always react, and earlier now, but making the scripting part of the commit or part of the 'one making the change' is more natural in the workflow. In other words, our product is not en_US only. 2) The texts for translations are updated in big 'code' drops, without possibility for translators to affect the process in any way - for them it is too late. Regarding 2) - I'm glad that you say that the strings will be now getting to Pootle immediately after the code / string changes in master. I think it is important that the translators will be able to deal with the changes immediately, not several months later, so that they can cooperate, and not only react. In general, I don't think that setting extremely strict rules works, unless you have means how to enforce them - like via a commit hook or so (and it is extremely unpopular way to do things). It is always much better to communicate - if you see a developer who commits a change that causes you grief, please _do_ tell _him/her_ immediately, and - if possible - in a friendly way. I'm sure he/she will do much better the next time. Unfortunately I did not see any signs of notice that this or that change was problematic for localization on the development mailing list - were there such warnings there? Like commit XY caused AB - please don't do such things, unless we agree how to do that effectively / without pain? Or was it impossible so far because the strings in Pootle were not synced with master? I fully agree with you here, and yes, so far communicating these issues was really difficult because these massive changes appeared in front of the localizers' eyes way too late in the process. What we should take care though is to not over complicate the work of l10n team by relying on this fact. So as I already said, it should be a shared work and vigilance by the concerned teams. Cheers Sophie -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] Re: [libreoffice-website] Website maintainers: make sure to update the release-line to show on download-pages
May be something I should add to the wiki :-) Cheers Sophie GSM Le 27 nov. 2014 19:16, Christian Lohmaier lohma...@googlemail.com a écrit : Hi *, just a reminder for Native-Lang website editors: make sure to update the shortcodes on the download pages to include the 4.4 versions. In other words: add [devDL,ver=4.4] on the pre-release download pages so that the 4.4.0 beta will show up there :-) ciao Christian -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Big Thank You page
Hi all, On Fri, Jun 27, 2014 at 10:17 PM, Robinson Tryon bishop.robin...@gmail.com wrote: On Thu, Jun 26, 2014 at 11:40 PM, K-J LibreOffice k...@libreoffice.org wrote: Hi Sophie, Am 24.06.2014 15:46, schrieb Sophie: [...] Let me know if you have any question or remark. How to differentiate between UK, Canada, USA for EN? I guess we could create sections for EN_US, EN_UK, etc..? yes, we could add subsections for a language and his locales Also, regarding where the content lives on the wiki, the current url is https://wiki.documentfoundation.org/Contributors but the emphasis seems to be on NLP contributors, so perhaps we can move the page to https://wiki.documentfoundation.org/Language/Contributors Yes, why not :) Cheers Sophie ? Cheers, --R -- Robinson Tryon LibreOffice Community Outreach Herald Senior QA Bug Wrangler The Document Foundation qu...@libreoffice.org -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Membership Certification Committee Member - Co-founder The Document Foundation -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Re: [libreoffice-marketing] Re: Engaging Users?
Thanks :-) Kind regards Sophie GSM Le 29 oct. 2013 21:44, Charles-H. Schulz charles.sch...@documentfoundation.org a écrit : Sophie, Italo, I will register you to LimeSurvey tomorrow morning. Best, Charles. Italo Vignoli it...@italovignoli.com a écrit : On 10/29/13 5:25 PM, Charles-H. Schulz wrote: Please let me know if you're interested in translating it and I will add you to the Lime Survey instance (judging by the admin panel there it looks like I can do that otherwise Florian will help me out). I would like to translate the survey into Italian, but from the document on the pad it is impossible to understand what has to be translated because is part of the final text. It would be nice to get a clean final version. I am sure that a good number of LibreItalia G+ members will answer the survey. -- Italo Vignoli - it...@italovignoli.com mob +39.348.5653829 - sip 5316...@messagenet.it skype italovignoli - hangout italo.vign...@gmail.com -- Envoyé de mon téléphone avec Kaiten Mail. Excusez la brièveté. -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] Fwd: Release configuration QA builds for Windows from 4-1 branch
Hi all, Forwarding Friedrich mail with the link : http://dev-builds.libreoffice.org/daily/libreoffice-4-1/Win-x86_9-Voreppe/ Kind regards Sophie Original Message Subject: Release configuration QA builds for Windows from 4-1 branch Date: Thu, 30 May 2013 09:31:46 +0200 From: Fridrich Strba fridrich.st...@graduateinstitute.ch To: Libreoffice-qa libreoffice...@lists.freedesktop.org, libreoff...@lists.freedesktop.org Hello, all beta testers, To make it a bit easier to test the Windows versions of our upcoming 4.1 release, we set a tinderbox that produces in principle every day a build of the libreoffice-4-1 branch in the release configuration with all supported languages and with all helppacks that are normally distributed in the release builds. Please, when confirming bugs for Windows, or looking for regressions, please use those builds so that we have a early alert in case a regression is introduced between an official build and the time of testing. Note, that properly triaged bug with a good instructions to reproduce will have increased chance to be fixed quickly. Cheers and thanks for your hard work Fridrich ___ LibreOffice mailing list libreoff...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] [ANN] LibreOffice 4.1.0 Beta1 available
Hi, On 26/05/2013 11:08, khagaroth wrote: Is anyone else getting a crash (no error message) when selecting Format - Character..., Format - Paragraph... etc. etc.? (Win7 x64) I didn't test it by myself, but it just has been reported on the QA FR list, with Format Page. Kind regards Sophie On Sun, May 26, 2013 at 1:04 AM, Thorsten Behrens t...@documentfoundation.org wrote: Dear Community, The Document Foundation is pleased to announce the first Beta release of our new LibreOffice 4.1. The upcoming 4.1 will be our sixth major release in two and a half years, and comes with a nice set of new features. Please be aware that LibreOffice 4.1 Beta1 is not ready yet for production use, you should continue to use LibreOffice 4.0.3 for that. For further milestones towards 4.1, please refer to our release plan timings here: https://wiki.documentfoundation.org/ReleasePlan/4.1#4.1.0_release The release is available for Windows, Linux and Mac OS X from our QA builds download page at http://www.libreoffice.org/download/pre-releases/ Should you find bugs, please report them to the FreeDesktop Bugzilla: https://bugs.freedesktop.org A good way to assess the release candidate quality is to run some specific manual tests on it, our TCM wiki page has more details: http://wiki.documentfoundation.org/QA/Testing/Regression_Tests#Full_Regression_Test For other ways to get involved with this exciting project - you can e.g. contribute code: http://www.libreoffice.org/get-involved/developers/ translate LibreOffice to your language: http://wiki.documentfoundation.org/LibreOffice_Localization_Guide or help with funding our operations: http://donate.libreoffice.org/ A list of known issues and fixed bugs with 4.1.0 Beta1 is available from our wiki: http://wiki.documentfoundation.org/Releases/4.1.0/Beta1 Let us close again with a BIG Thank You! to all of you having contributed to the LibreOffice project - this release would not have been possible without your help. Yours, The Document Foundation Board of Directors The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany Rechtsfähige Stiftung des bürgerlichen Rechts Legal details: http://www.documentfoundation.org/imprint -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted -- Sophie Gautier sophie.gaut...@documentfoundation.org Tel:+33683901545 Membership Certification Committee Member - Co-founder The Document Foundation -- To unsubscribe e-mail to: projects+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] Fwd: [libreoffice-design] 4.0 Branding poll
Hi all, Mirek is organizing a poll on the start center and splash screen for the next version after 4.0.Please try to get feedback from your communities and report it here or directly to the design project. The proposals are here https://wiki.documentfoundation.org/Design/Whiteboards/4.0_Branding Thanks in advance :) Kind regards Sopĥie Original Message Subject: [libreoffice-design] 4.0 Branding poll Date: Tue, 29 Jan 2013 00:32:35 +0100 From: Mirek M. maz...@gmail.com To: des...@global.libreoffice.org des...@global.libreoffice.org Because of disagreements over the 4.0 branding, we're setting up a poll to help us reach a solution. To vote for a proposal, add 1 to the number next to it. To vote against it, subtract 1. You may vote for as many proposals as you'd like, but you may only vote once and you may not change your vote. You may also leave comments below the poll. The deadline for voting is February 9th, 2013, 16:00 UTC, after which we'll discuss the results and determine whether the winning proposal is shippable. Branding from version 3.6: 0 Proposal by Aexyn.com: 0 V1 by Javier Antonio Nisa Ávila: 0 V2 by Javier Antonio Nisa Ávila: 0 V3 by Javier Antonio Nisa Ávila: 0 GIn-V1 by k-j: 0 GIn-V2 by k-j: 0 Minimal by Medieval: 0 ages by Medieval: 0 Proposal by Pedro: 0 Clear_Full_Official.png by Mateus.m.luna: 0 Clear_Full_Pref.png by Mateus.m.luna: 0 Clear_Green_Official.png by Mateus.m.luna: 0 Clear_Green_Pref.png by Mateus.m.luna: 0 Proposal by Alexander Wilms (original PNG): 0 Proposal by Alexander Wilms (at the right of the new SVG): 0 Proposal by Maxim Darák: 0 Proposal by H.Sparks: 0 Proposal by G Sparks: 0 -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted -- Unsubscribe instructions: E-mail to projects+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] About forum in native language
Hi all, This is just to let you know that an English forum is planed to be launched in some days now. Following after their will be forum in native language for the groups who want it. There is still some time before it's done but I wanted to keep you informed. The description of what is actually done and planed is here : https://wiki.documentfoundation.org/Forum-planning The discussion is taking place on the website list (so don't discuss it here please :-) May be opening the discussion in your language communities to prepare the work would help your group to know if you need a forum or not. Make sure to have moderators before requesting for a forum, it's a task that request some time but a forum can't work without it. There is no obligation, you can still use the mailing list or both, only for users help or for other categories, it's up to you to decide ! Kind regards Sophie -- Unsubscribe instructions: E-mail to projects+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] QA manual test Litmus session on 3.3.3Rc
Hi Cor, On 07/06/2011 01:58, Cor Nouws wrote: Hi Sophie, *, Sophie Gautier wrote (05-06-11 22:36) I would like to try to organize a first session of manual tests - release scenarios - on Litmus [1]. Mostly to see how it goes and fine tune what needs to be done to go further. We need to push our QA process further and log what is done in the language community. [...] Thanks a lot for this :-) Thanks a lot for jumping in :) Just created an account and is gives me this welcome Thank you for your contribution to Mozilla QA. ;-) Oh, yes, we are very keen in supporting Mozilla effort, you know ;) I'll see if we can correct this, thanks for the feedback I'll translate the wiki-info and poke some people on the Dutch language lists to take a look too. If we have any questions, we know where to find you :-) Yes, don't hesitate, and welcome to the Dutch speaking community! Kind regards Sophie Cheers, -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] QA manual test Litmus session on 3.3.3Rc
Hi Michael, On 06/06/2011 08:57, Michael Münch wrote: Hi Sophie, Am Sonntag, den 05.06.2011, 23:36 +0300 schrieb Sophie Gautier: Hi all, *please, follow up on the projects list, thanks in advance* I would like to try to organize a first session of manual tests - release scenarios - on Litmus [1]. Mostly to see how it goes and fine tune what needs to be done to go further. We need to push our QA process further and log what is done in the language community. The first version will 3.3.3 RC. Yifan (thanks a lot! ) did upload a session for 3.4, but I guess we were a bit distracted by what happened to the OOo code. But we can use this basis for the next session. Should a test run 3.3.3 already be visable? As soon as I, or another admin, have create them :) but surely today Tests already exists in US - DE - FR, it's a first set that needs to be improved and made available for all languages. Would a additional testgroup with those bugs that occured as blockers for past releases make sense at this early stage of the process? They should be easily found in the bugzilla. Oh, yes, that's a good idea. Another question, would tests against the daily builds of the 3.4 series go into the libreoffice 3.4 test run or should there just be tests against beta and/or RC versions? all releases should be tested and have the results log in Litmus, but not everybody will be able to follow the rate. There is a trunk category that Yifan (I think) has open, may be we can put branches here? Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] QA manual test Litmus session on 3.3.3Rc
Hi Klaus-Jürgen, On 06/06/2011 13:56, klaus-jürgen weghorn ol wrote: Hi Sophie, QAlies, Am 05.06.2011 22:36, schrieb Sophie Gautier: Hi all, *please, follow up on the projects list, thanks in advance* I would like to try to organize a first session of manual tests - release scenarios - on Litmus [1]. Mostly to see how it goes and fine tune what needs to be done to go further. We need to push our QA process further and log what is done in the language community. The first version will 3.3.3 RC. Yifan (thanks a lot! ) did upload a session for 3.4, but I guess we were a bit distracted by what happened to the OOo code. But we can use this basis for the next session. Tests already exists in US - DE - FR, it's a first set that needs to be improved and made available for all languages. So please, join the projects@ list and let us organize a nice and fun QA process for our future versions. For testing, you don't need technical skills, only about 3/4 hours available (for beginners, less if you have already participate) per tested version and some curiosity for the new features and the bug you will find. For translation, understanding of English will be enough, the tests and the process are simple and most of the time written by non English speakers. If you run VCLTesTool, we will also try to centralize the feedback, so don't hesitate to jump in either. Process and info on Litmus are available on the wiki [2], but don't hesitate to come on the list, I'll help and answer your questions from there, also on irc #libreoffice [1] https://tcm.documentfoundation.org/ [2] http://wiki.documentfoundation.org/Litmus Thanks in advance for your help on the organization and your participation. Some things Christian K. mentioned on the German-ml [1]: 1. Should we re-place Litmus on the Wiki-menu? Yes, why not 2. The German tests are different from the English. Is there any problem with it? Yes, because, the English one should be the master set. Frequently, when we lack of one tester (you know the OOo rule of 2 testers/plateform to validate it) I check the other language to help validate the version. If there is an issue with one test, it's easier to see if it's language dependent or not. And we want to offer the same level of quality for all the versions, so really we need to ensure the English is the master. 3. Obviously the testcases can only be changed by admins although there is an option in the menu. If only admins can do this we should give some more people admin rights especially mindst 2 persons per l10n. And it should be unlighted for the others. This will be done on demand. I can also upload tests for the other language who don't have enough resources or don't want to deal with Litmus 4. Who are the admins now? Volker Heggerman, Jean-Baptiste Faure and me. Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-projects] QA manual test Litmus session on 3.3.3Rc
Hi all, *please, follow up on the projects list, thanks in advance* I would like to try to organize a first session of manual tests - release scenarios - on Litmus [1]. Mostly to see how it goes and fine tune what needs to be done to go further. We need to push our QA process further and log what is done in the language community. The first version will 3.3.3 RC. Yifan (thanks a lot! ) did upload a session for 3.4, but I guess we were a bit distracted by what happened to the OOo code. But we can use this basis for the next session. Tests already exists in US - DE - FR, it's a first set that needs to be improved and made available for all languages. So please, join the projects@ list and let us organize a nice and fun QA process for our future versions. For testing, you don't need technical skills, only about 3/4 hours available (for beginners, less if you have already participate) per tested version and some curiosity for the new features and the bug you will find. For translation, understanding of English will be enough, the tests and the process are simple and most of the time written by non English speakers. If you run VCLTesTool, we will also try to centralize the feedback, so don't hesitate to jump in either. Process and info on Litmus are available on the wiki [2], but don't hesitate to come on the list, I'll help and answer your questions from there, also on irc #libreoffice [1] https://tcm.documentfoundation.org/ [2] http://wiki.documentfoundation.org/Litmus Thanks in advance for your help on the organization and your participation. Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] [ANN] LibreOffice 3.3.3 RC1 available
Hi, On 03/06/2011 19:49, Webmaster for Lungstrom.com wrote: On 06/03/2011 10:29 AM, Thorsten Behrens wrote: Hi *, for 3.3.3 rc1, we're now uploading builds to a public (but non-mirrored - so don't spread news too widely!) place, as soon as they're available. Grab them here: I did not know we were doing a 3.3.3 since we had 3.4.0 come out. 3.4 is for contributors (they need to be feed, you know ;), 3.3.3 is for corporates and conservator users. So the 3.x.x will be maintained until the end of the year, while 3.4.1 will be for corporates, etc... Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [Duplicate] Re: [libreoffice-projects] [Proposal] A central employment-office-like web structure for TDF/LibO volunteers
Hi Gianluca, On 23/05/2011 09:31, Gianluca Turconi wrote: In data 22 maggio 2011 alle ore 18:34:41, Sophie Gautier gautier.sop...@gmail.com ha scritto: It's ok, I've understand, but for me there is no need of a formal process, just a need of motivate people to participate. OK, I've to start the recruiting campaign, then. :) I'll start with the website ML and other local Italian lists and forums so that I can see what kind of feedback I'll receive about the technical implementation of the tool. Maybe, people with more knowledge of the modern collaboration tools may suggest a easier and more efficient tool than a wiki or hive other good suggestions and help. Just a word on this, be careful that people will always come with his best tool and will try to promote it, so you may end up with 10 people = 10 tools ;) Thanks for your help, Sophie. you're welcome Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] [Proposal] A central employment-office-like web structure for TDF/LibO volunteers
On 18/05/2011 10:04, Gianluca Turconi wrote: Sophie Gautier wrote: So let's refine what we were discussing so far. BTW, is there already any official or unofficial draft document that can be used for proposal like this, so that there is a homogeneous approval/rejection process for project proposals? No, I don't think so. OK. Just let me know *exactly* where (wiki section?) I can post a preliminary draft of the proposal and I'll try to post it there. Pay attention: I'm not particularly expert in wiki modifications, so mistakes are highly likely. ;) A wiki is done to handle mistakes by design: you can always undo your final action :) If it's only the development of the tool, it should be placed under the LibreOffice Wiki section I think: http://wiki.documentfoundation.org/Website/LibreOfficeWiki Later, the tool itself, if it must be visible when arriving on the wiki, the Start page is the best to place it. There is already such a posting on the wiki for the easy hacks things: http://wiki.documentfoundation.org/Development/Easy_Hacks I see. This page should be modified once there will be an agreement about a wiki template, but we'll think about that if/when the community will agree on the proposal. yes /me don't like private mail :) Mailing list, to get the archive and the information available to all is better, I think Well, it can be done after the creation of a ad hoc mailing list. It can be done manually by the coordinators or automatically by the wiki warning system for page modifications, though I don't know how flexible that system is for our purposes. [...] I think it's harder to write it down in this email than doing it as real process. ;) yes, but it's very clear, you have writer skills no? ;) I usually write SF/fantasy/horror fictions, not technical docs. :-P oh, you can put horror or fantasy in your proposal, no problem ;) [...] Yes, I agree about the too much complexity, I don't like it too but I can't do anything about it. You should send your proposal to the website list, may be that will open the discussion about the enhancement of the pages. I'll surely send that proposal too, as soon as we've completed this one. Ok, thanks a lot. Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] [Proposal] A central employment-office-like web structure for TDF/LibO volunteers
On 17/05/2011 11:11, Gianluca Turconi wrote: Sophie Gautier wrote: I'm not sure you will have feedback before having done something, see we're only two in the conversation for now. So lets implement a first draft and a description of the process, we may get more feedback later. OK, no problem. So let's refine what we were discussing so far. BTW, is there already any official or unofficial draft document that can be used for proposal like this, so that there is a homogeneous approval/rejection process for project proposals? No, I don't think so. Then: I think we are now agreeing that such central system has to be a wiki with a simplified template for direct access of the open tasks of the different projects. See below other thoughts of mine about different topics below. Yes *About coordinators* I think, but I may be wrong, that if we force developers directly to post their requests for help in a wiki, and waste coding time, they may find that central system just useless and a duplication of bugzilla. There is already such a posting on the wiki for the easy hacks things: http://wiki.documentfoundation.org/Development/Easy_Hacks So, I'm in favor of a more important role of the coordinators. They should actually gather the requests *and* post them in the wiki. Yes, I think both could be handled with no difficulty That would ease the whole work process. In fact, the current maintainers/contributors may send a simply email or compile a web form with their requests directed to a coordinator who, afterwards, will post them in the wiki. No further knowledge of the wiki (sections, tags, other formalities) would be needed for the current maintainers/contributors. Yes, the most difficult for a contributor would be to understand the structure of the system, more than the syntax of the wiki For wannabe contributors, the coordinators would be like the marketing contacts: people who are /trait d'union/ between outside and inside realities. Again, the coordinators may be contacted via email or web form or other means. Yes However, I think it's important, after the first contact and for more complex tasks (see classification below), to involve the new potential contributor in the larger discussion (mailing lists or via private mail with other developers/contributors). /me don't like private mail :) Mailing list, to get the archive and the information available to all is better, I think It may build (a kind of) loyalty and not just a one time contribution. +1 *About the granularity of classification of the requests for help* At the beginning of this discussion there were doubts about the manageability of a system that includes even 1-hour tasks. After further consideration, I agree too that it would be difficult to manage such system. Maybe, we need less granularity. We may classify the requests in a broader way according their difficulty and needed time to complete: Easy, Medium, Complex. a) Easy: basic skills needed, shortest time involved to complete them; b) Medium: average skills needed, average time involved to complete them; c) Complex: high level skills needed, longest time involved to complete them. So, the work flow in this central system should be: 1) a current maintainer/contributor contacts a coordinator via email/web form/any-chosen-mean and sends a request for help, by providing at least: 1a) a detailed description of the task; 1b) needed skills (i.e. specific coding language); 1c) estimated complexity of the task; 1d) possible deadline for contribution; Yes 2) the coordinator classify the request according the wiki classification (Web Level 1: skills needed; Web Level 2: Complexity; Web Level 3: list of tasks) Yes 3) a wannabe contributor picks a task up in the wiki and gives confirmation of such activity, via email/web form/modification of the wiki/other means; -- wiki has to be updated by the coordinator anyway 4) the coordinator, for more complex tasks or activities with a deadline, contacts the maintainers/contributors and communicate that the important/complex task has a new potential contributor. Automation of this phase would be greatly appreciated; Yes 5) the task is completed by the new contributor on his own or in collaboration with core contributors, and everybody are happy :) Yes, it seems :) 6) the coordinator regularly checks open, taken by new potential contributor, tasks and verify that there has not been any mistake in assignation or that the potential contributor has not lost interest. I think it's harder to write it down in this email than doing it as real process. ;) yes, but it's very clear, you have writer skills no? ;) BTW, I'm still puzzled from the @libreoffice.org @documentfoundation.org and @lists.freedesktop.org division for mailing lists. It's nearly a nightmare for a potential contributor to understand where to write and why. :( We could may be reduce the gap between @freedesktop and the @libreoffice
Re: [libreoffice-projects] [Proposal] A central employment-office-like web structure for TDF/LibO volunteers
Gianluca, On 15/05/2011 13:27, Gianluca Turconi wrote: Hello *, here it is an idea of mine I've started to discuss with Sophie: http://www.mail-archive.com/discuss@documentfoundation.org/msg06252.html It's still in a very raw and theoretical form and it likely has to be refined a lot. The main purpose of such a proposal is to increase efficiency in managing help requests and contributions, both casual and core ones. While I was thinking about it a little more, I've already found 3 more critical points: 1) appreciation of the proposal by and its utility for developers. They already have bugzilla; 2) manageability of such a system by the maintainers and contributors of the projects. They have, like everybody else, few free time and the addition of another system and its maintenance may reduce that available time. A huge automation of the system is absolutely needed; 3) native languages projects/tasks may create barriers in a management system of this kind without the key effort of few local coordinators, usually the same maintainers and core contributors of the NL projects who are already overloaded with work. My main concern, even before the technical implementation of this proposal, it's not to create more and unwanted overload for the *current* contributors. So that could be a task for somebody who has recurrent time slots available to [partly] manage the tasks planning. If the tool really provide efficiency in time management, we should be able to avoid harassing volunteers already overwhelmed. Kind regards Sophie -- Founding member of The Document Foundation -- Unsubscribe instructions: E-mail to projects+h...@libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/www/projects/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] This list is now at GMANE
Hi * On 19/03/2011 14:29, Florian Effenberger wrote: Hello, this list is now also archived at GMANE, as soon as the next few messages come in: http://dir.gmane.org/gmane.comp.documentfoundation.libreoffice.projects Thank you Florian :) Kind regards Sophie -- Founding member of The Document Foundation -- E-mail to projects+h...@libreoffice.org for instructions on how to unsubscribe List archives are available at http://listarchives.libreoffice.org/www/projects/ All messages you send to this list will be publicly archived and cannot be deleted
Re: [libreoffice-projects] Re: libreofficebox teams and subsites
On 19/03/2011 22:04, Erich Christian wrote: Hi Sophie, Daniel, Am 18.03.2011 09:02, schrieb Sophie Gautier: On 18/03/2011 02:43, Daniel A. Rodriguez wrote: We're looking forward to hear from you what kind of subs you would want to use, just for example could be es.libreofficebox.org together with devel.es.libreofficebox.org or whatever fits better to your requirements. your suggestion it's just fine for me +1 and count me in Please register your account at http://devel.libreofficebox.org/register/ and let me know. Well, that should be done provided that after 2/3 glasses of white wine, my German still exists ;-) Subsites are prepared, Thanks a lot :) Kind regards Sophie -- Founding member of The Document Foundation -- E-mail to projects+h...@libreoffice.org for instructions on how to unsubscribe List archives are available at http://listarchives.libreoffice.org/www/projects/ All messages you send to this list will be publicly archived and cannot be deleted
