Re: [ApacheCon EU] China: Visas to Germany
On 10/23/2012 12:39 PM, Dave Fisher wrote: On Oct 22, 2012, at 7:50 PM, Peter Junge wrote: On 10/23/2012 10:40 AM, Louis Suárez-Potts wrote: Sorry for top post but: Are there not other Apache EU projects suffering the same effects? Indeed, I also considered to sending this information to the ApacheCon list but the only Chinese names I can discover on the schedule (http://www.apachecon.eu/schedule/) are affiliated with AOO. As well, I'm also following the ApacheCon list and didn't notice the issue there, except Chinese AOO committers asking for invitation letters. Do the AOO committers require invitation letters from The Apache Software Foundation, or the com-com committee? As far as I know yes, there have been several requests for such letters on the ApacheCon mailing list. Do these letters need to be addressed to any particular insititution? Germany, China, ... ? This needs to be checked with the German embassy or the visa agent that I have been linking yesterday. However, I would guess that the persons are aware of the procedures. The problem usually is that the German embassy issues visas very slowly. Time is the limiting factor. Peter Regards, Dave Peter Louis On 22 October 2012 22:34, Peter Junge peter.ju...@gmx.org wrote: Hi, I have heard several Chinese speakers who want to present at the ApacheCon EU 2012 are having problems with getting their visa in time. Indeed, the recent situation was very bad because the German embassy doesn't have the resources to handle the strong demand for German visas in China, e.g. they have only two telephone lines to make appointments for submitting visa applications. Just last week the German embassy started to outsource the visa application process to a private agency which will certainly make everything easier, e.g. they are checking each application for completeness and correctness while previously visa applications were declined deliberately without giving any information about what went wrong. The website of the visa agency can be found here: https://cn.tlscontact.com/cnBJS2de/splash.php The service is available in English, Chinese and German. Additional information from the German embassy (in Chinese) can be found here: http://www.china.diplo.de/Vertretung/china/zh/01-service/visa/tls/0-s.html Hope it's not to late. Peter
Re: [ApacheCon EU] China: Visas to Germany
On 2012/10/23 10:34, Peter Junge said: Hi, I have heard several Chinese speakers who want to present at the ApacheCon EU 2012 are having problems with getting their visa in time. Who and how many speakers from China are having this VISA problem? Indeed, the recent situation was very bad because the German embassy doesn't have the resources to handle the strong demand for German visas in China, e.g. they have only two telephone lines to make appointments for submitting visa applications. Just last week the German embassy started to outsource the visa application process to a private agency which will certainly make everything easier, e.g. they are checking each application for completeness and correctness while previously visa applications were declined deliberately without giving any information about what went wrong. The website of the visa agency can be found here: https://cn.tlscontact.com/cnBJS2de/splash.php The service is available in English, Chinese and German. Additional information from the German embassy (in Chinese) can be found here: http://www.china.diplo.de/Vertretung/china/zh/01-service/visa/tls/0-s.html Hope it's not to late. Peter -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/ signature.asc Description: OpenPGP digital signature
Re: [WWW]: shared ideas and looking for feedback
On 19/10/2012 Jürgen Schmidt wrote: 1. a clear structure for the English content as well as the translated pages. .../press/msg_20121019.html .../de/press/msg_20121019.html .../it/press/msg_20121019.html Means we have for all pages a translated version in the related sub directory. Same path and same name only the content is translated. This may work for News and announcements, even if often, in that case, the English announcement is posted on the ASF blog, so outside the openoffice.org domain. For the whole structure, this is easy only for NL sites that we will be rebuilding from scratch, but for other sites we can start to harmonize paths at least for announcements. Regards, Andrea.
Re: User list and donations
On 10/24/12 1:37 AM, Karl Glode wrote: Hi I have just updated my Apache Home Office. I have tried to contact you by clicking the appropiate button but Microsoft email site wants to open.I never use MS email these days, i use Yahoo7. How do I make this happen that Y7 opens instead of MS Karl the mail is moderated but I have no idea what he is doing and how we can help. Does anybody else have an idea? Juergen
Re: User list and donations
Probably he talks about the URL embedded on the UI like get extensions here, and this launch some MS email client like outlook. He would need to configure his OS to use yahoo webmail. http://uk.answers.yahoo.com/question/index?qid=20070217130008AAsCjy1 That said, this user seems a bit unsophisticated to perform this tasks or tell the difference between email clients and mailing list. On 10/24/12, Jürgen Schmidt jogischm...@gmail.com wrote: On 10/24/12 1:37 AM, Karl Glode wrote: Hi I have just updated my Apache Home Office. I have tried to contact you by clicking the appropiate button but Microsoft email site wants to open.I never use MS email these days, i use Yahoo7. How do I make this happen that Y7 opens instead of MS Karl the mail is moderated but I have no idea what he is doing and how we can help. Does anybody else have an idea? Juergen -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: OpenOffice graduation: translations of press release
On 22/10/2012 Guy Waterval wrote: 2012/10/18 Andrea Pescetti We welcome translations of today's press release about the OpenOffice graduation. What about the translations of the press release about the OpenOffice graduation?. Are we authorized to diffuse them or not. Somebody has asked me to use my french translation, but as I don't know if a validation process is ongoing, I asked to wait. Sorry for the delay, I've uploaded the French translation to http://www.openoffice.org/fr/news/2012-10-graduation.html and Rob will then link to it from https://blogs.apache.org/OOo/entry/openoffice_graduates_from_the_apache If we may diffuse, what is the right way? Links to the above pages will work. But the text can be republished too. In that case, though, I would insert a link to the original post/page. Regards, Andrea.
Re: AOO volunteers: essential skills and tasks
+1, that was something I could really have used some weeks ago :-) Maybe a word about active volunteers might not be harmful (I think I am in that state now) Jan I. On 23 October 2012 23:30, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? Quick update. I have drafts of a few of the pages ready. 1) New Volunteer Orientation root page: http://incubator.apache.org/openofficeorg/orientation/ 2) Introduction to Contributing to Apache OpenOffice (Level 1): http://incubator.apache.org/openofficeorg/orientation/level-1.html 3) Intermediate Social and Technical Tools (Level 2): http://incubator.apache.org/openofficeorg/orientation/level-2.html (around half done). I could really use some help drafting the area-specific Level 3 and Level 4 pages, from subject matter experts. -Rob
Re: Need new logo for openoffice.apache.org
On Tue, Oct 23, 2012 at 9:07 PM, Kevin Grignon kevingrignon...@gmail.comwrote: On Tuesday, October 23, 2012, Graham Lauder wrote: On Tue, Oct 23, 2012 at 7:59 PM, Andrea Pescetti pesce...@apache.org javascript:; wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/**confluence/download/**attachments/27834483/** ApacheOpenOfficeTM.svg https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). The SVG was done by Alexandro from Michael's bitmap IIRC. Michael's was never official, it was just the one that happened to be available. There was never any consensus that Michael's was going to be anything other than a stop-gap for a first release from the ApacheOO podling. Going forward there needs to be proposals and discussion and a new branding that reflects the New OpenOffice. KG01 - agreed, lets start exploring design directions. I'll share my designs shortly. On training this week, just need some time at home office :) I've put up a graphical text first proposal on the wiki to explore the concept of a purely Graphical logo that doesn't use a particular font. This would avoid secondary licensing issues that could go with using a Typeface from a Forge. The graphic was created in Inkscape from scratch just using inkscape drawing tools with out recourse to using fonts even as a guide. https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.x+-+Logo+Explorations Cheers GL
Re: Need new logo for openoffice.apache.org
On 10/23/12, Andrea Pescetti pesce...@apache.org wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly Who made Michael Acevedo the offical artist of AOO? If we are going to have a 'new' logo that automatically disqualify using MA logo as a whole. So far Nobody wants a proprietary fonts. So this logo is out. Now the issue is if there is any problem using an OpenType License font. done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). We have two separate issues here: 1) Collecting and consolidating all versions of the logo we are using; here a 95% accuracy is not acceptable. These versions should be placed under http://www.openoffice.org/images/AOO_logos/ or anyway under SVN. Most logos are variation of the first one. We can generate a whole new set for 4.0, or we can even go back to the pre-Oracle OpenOffice brand refresh and get the OpenOffice with the gulls. The Orb was never part of the logo, it was label a 'symbol' to be used in a different context of the logo, just like the wireframe gulls was for 2.4. 2) Collecting proposals that can be useful as inspiration for a new visual identity; here it is of course acceptable to have variants of the official logos, but these should remain proposals and be placed in the wiki or such, possibly in pages that do not confuse a reader who types OpenOffice logo in a search engine. We need a framework to make decisions lazy conscensus, voting schemes, etc. But it seems there is a generalized knowledge that this is not only the logo but Application Icons, Mime Icons, and Module icons. Keeping a fresh logo with a very dated iconset is just not a good practice, specially for a 4.0 release. Regards, Andrea. Should this be taken to marketing list? Is really a non-coding topic and traditionally was handled by the art Project which was a subproject of marketing. Most of the visual identity and design need to be upstreamed to marketing to develop marketing kits. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Need new logo for openoffice.apache.org
On 10/24/12, Graham Lauder g.a.lau...@gmail.com wrote: On Tue, Oct 23, 2012 at 9:07 PM, Kevin Grignon kevingrignon...@gmail.comwrote: On Tuesday, October 23, 2012, Graham Lauder wrote: On Tue, Oct 23, 2012 at 7:59 PM, Andrea Pescetti pesce...@apache.org javascript:; wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/**confluence/download/**attachments/27834483/** ApacheOpenOfficeTM.svg https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). The SVG was done by Alexandro from Michael's bitmap IIRC. Michael's was never official, it was just the one that happened to be available. There was never any consensus that Michael's was going to be anything other than a stop-gap for a first release from the ApacheOO podling. Going forward there needs to be proposals and discussion and a new branding that reflects the New OpenOffice. KG01 - agreed, lets start exploring design directions. I'll share my designs shortly. On training this week, just need some time at home office :) I've put up a graphical text first proposal on the wiki to explore the concept of a purely Graphical logo that doesn't use a particular font. This would avoid secondary licensing issues that could go with using a Typeface from a Forge. The graphic was created in Inkscape from scratch Is ther any licensing issue using a Open license font? Was there any license issue in the past to use a closed source license, if so where is this clearance? Is there an advantage of having our own proprietary font (developed in-house). just using inkscape drawing tools with out recourse to using fonts even as a guide. https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.x+-+Logo+Explorations Do they need to reflect the same attitudes as the one shown on the wiki? global open transparent accessible clean strong...? Do we want to be more web-enabled, cloud, feather, social? (this from other conversations about making OO more social) Finally is there a template of proposals like: - font - visual element - logo - symbol - Application logo - Module logo (writer, calc, impress...) - Mime-logo (odt, ods, odp, odg..) - Design guidelines Cheers GL -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Need new logo for openoffice.apache.org
KG03 - see comments inline On Oct 24, 2012, at 4:50 PM, Alexandro Colorado j...@oooes.org wrote: On 10/23/12, Andrea Pescetti pesce...@apache.org wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly Who made Michael Acevedo the offical artist of AOO? If we are going to have a 'new' logo that automatically disqualify using MA logo as a whole. So far Nobody wants a proprietary fonts. So this logo is out. Now the issue is if there is any problem using an OpenType License font. done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). We have two separate issues here: 1) Collecting and consolidating all versions of the logo we are using; here a 95% accuracy is not acceptable. These versions should be placed under http://www.openoffice.org/images/AOO_logos/ or anyway under SVN. Most logos are variation of the first one. We can generate a whole new set for 4.0, or we can even go back to the pre-Oracle OpenOffice brand refresh and get the OpenOffice with the gulls. The Orb was never part of the logo, it was label a 'symbol' to be used in a different context of the logo, just like the wireframe gulls was for 2.4. 2) Collecting proposals that can be useful as inspiration for a new visual identity; here it is of course acceptable to have variants of the official logos, but these should remain proposals and be placed in the wiki or such, possibly in pages that do not confuse a reader who types OpenOffice logo in a search engine. We need a framework to make decisions lazy conscensus, voting schemes, etc. But it seems there is a generalized knowledge that this is not only the logo but Application Icons, Mime Icons, and Module icons. Keeping a fresh logo with a very dated iconset is just not a good practice, specially for a 4.0 release. Regards, Andrea. Should this be taken to marketing list? Is really a non-coding topic and traditionally was handled by the art Project which was a subproject of marketing. Most of the visual identity and design need to be upstreamed to marketing to develop marketing kits. KG03 - our branding is tightly bound to visual elements (gui) in tools. Let's keep this activity with UX in design and dev discussions. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Need new logo for openoffice.apache.org
KG04 - see comments inline. On Oct 24, 2012, at 4:58 PM, Alexandro Colorado j...@oooes.org wrote: On 10/24/12, Graham Lauder g.a.lau...@gmail.com wrote: On Tue, Oct 23, 2012 at 9:07 PM, Kevin Grignon kevingrignon...@gmail.comwrote: On Tuesday, October 23, 2012, Graham Lauder wrote: On Tue, Oct 23, 2012 at 7:59 PM, Andrea Pescetti pesce...@apache.org javascript:; wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/**confluence/download/**attachments/27834483/** ApacheOpenOfficeTM.svg https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). The SVG was done by Alexandro from Michael's bitmap IIRC. Michael's was never official, it was just the one that happened to be available. There was never any consensus that Michael's was going to be anything other than a stop-gap for a first release from the ApacheOO podling. Going forward there needs to be proposals and discussion and a new branding that reflects the New OpenOffice. KG01 - agreed, lets start exploring design directions. I'll share my designs shortly. On training this week, just need some time at home office :) I've put up a graphical text first proposal on the wiki to explore the concept of a purely Graphical logo that doesn't use a particular font. This would avoid secondary licensing issues that could go with using a Typeface from a Forge. The graphic was created in Inkscape from scratch Is ther any licensing issue using a Open license font? Was there any license issue in the past to use a closed source license, if so where is this clearance? Is there an advantage of having our own proprietary font (developed in-house). just using inkscape drawing tools with out recourse to using fonts even as a guide. https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.x+-+Logo+Explorations Do they need to reflect the same attitudes as the one shown on the wiki? global open transparent accessible clean strong...? KG04 - Hopefully. We need a unified voice. These attributes represent criteria for success. Do we want to be more web-enabled, cloud, feather, social? (this from other conversations about making OO more social) KG04 - when we are actually social and in the cloud. Then yes. KG04 - Re: feather, I will post a mockup as an example. Finally is there a template of proposals like: - font - visual element - logo - symbol - Application logo - Module logo (writer, calc, impress...) - Mime-logo (odt, ods, odp, odg..) - Design guidelines KG01 - when I post my design explorations, I will create a template. These items are part of the graphic inventory. Cheers GL -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Table of Contents Usability?
A recent thread on the en-Forum threw up problems with the interface of the Table of Contents generation. Perhaps Kevin Grignon might care to note this as an area worthy of improvement. http://forum.openoffice.org/en/forum/viewtopic.php?f=7t=56908 -- Rory O'Farrell ofarr...@iol.ie
Re: Need new logo for openoffice.apache.org
On 10/24/12, Kevin Grignon kevingrignon...@gmail.com wrote: KG03 - see comments inline On Oct 24, 2012, at 4:50 PM, Alexandro Colorado j...@oooes.org wrote: On 10/23/12, Andrea Pescetti pesce...@apache.org wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly Who made Michael Acevedo the offical artist of AOO? If we are going to have a 'new' logo that automatically disqualify using MA logo as a whole. So far Nobody wants a proprietary fonts. So this logo is out. Now the issue is if there is any problem using an OpenType License font. done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). We have two separate issues here: 1) Collecting and consolidating all versions of the logo we are using; here a 95% accuracy is not acceptable. These versions should be placed under http://www.openoffice.org/images/AOO_logos/ or anyway under SVN. Most logos are variation of the first one. We can generate a whole new set for 4.0, or we can even go back to the pre-Oracle OpenOffice brand refresh and get the OpenOffice with the gulls. The Orb was never part of the logo, it was label a 'symbol' to be used in a different context of the logo, just like the wireframe gulls was for 2.4. 2) Collecting proposals that can be useful as inspiration for a new visual identity; here it is of course acceptable to have variants of the official logos, but these should remain proposals and be placed in the wiki or such, possibly in pages that do not confuse a reader who types OpenOffice logo in a search engine. We need a framework to make decisions lazy conscensus, voting schemes, etc. But it seems there is a generalized knowledge that this is not only the logo but Application Icons, Mime Icons, and Module icons. Keeping a fresh logo with a very dated iconset is just not a good practice, specially for a 4.0 release. Regards, Andrea. Should this be taken to marketing list? Is really a non-coding topic and traditionally was handled by the art Project which was a subproject of marketing. Most of the visual identity and design need to be upstreamed to marketing to develop marketing kits. KG03 - our branding is tightly bound to visual elements (gui) in tools. Let's keep this activity with UX in design and dev discussions. Not really, actually if you look at UX between 2.4 and 3.0 the tool visual element never changed, except for icons, but wee are not discussing about creating a new set of icons, or are we? -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Table of Contents Usability?
On Wed, 24 Oct 2012 10:53:47 +0100 Rory O'Farrell ofarr...@iol.ie wrote: A recent thread on the en-Forum threw up problems with the interface of the Table of Contents generation. Perhaps Kevin Grignon might care to note this as an area worthy of improvement. http://forum.openoffice.org/en/forum/viewtopic.php?f=7t=56908 A further note on this in http://forum.openoffice.org/en/forum/viewtopic.php?f=106t=56976p=250998 -- Rory O'Farrell ofarr...@iol.ie
Re: Directory main/swext/mediawiki
On Tue, Oct 23, 2012 at 10:49 AM, jan iversen jancasacon...@gmail.com wrote: Thanks. I have not sent a specific request to you, but asked it as a general question (because I did not know who to ask). In the meantime, I found out that the sources in swext/mediawiki are in use, so I have compiled AOO with --enable-wiki-publisher. As far as I know http://extensions.openoffice.org/en/project/wikipublisher is based on 2009 source code, and it has not been updated since. Now my only problem is that, when I install the ocx via extension manager, I get a dialog box, stating that there might be a problem with description.xml because there is a license problem. I have tried to configure --with-lang=en, and rebuilt AOO, but that does not seem to help. I have no clue about why you get warnings, but I'm pretty sure this is not related to Extensions. Roberto So if you have an idea I would be thankfull. Are you working with the mediawiki sources, because the reason I do this was to fix a couple of problems I have found. Jan. On 23 October 2012 10:06, Roberto Galoppini rgalopp...@geek.net wrote: On Sun, Oct 21, 2012 at 6:24 PM, jan iversen jancasacon...@gmail.com wrote: I have looked for a newer source, since it was moved, but our own extensions has a broken link and sourceForge does not offer any help. Any ideas ?? Hi Jan, I don't think I've received any request from you, please let me know what's the problem, and I'll do my best to help you. Roberto It is a sun part, so we should have inherited it or not ? jan. On 20 October 2012 23:52, Alexandro Colorado j...@oooes.org wrote: On Sat, Oct 20, 2012 at 2:50 PM, jan iversen jancasacon...@gmail.com wrote: I am a bit confused. We have a directory named main/swext/mediawiki. Is that the sun wiki publisher 1.1 or are there 2 different mediawiki export extensions ? I ask because I sun wiki publisher 1.1 installed, but if I change the XLS and rebuilt AOO but it does not seem to have an effect. Yes I think it was started on core, and then sent to a separate extensions. Same thing happened with smarttags IIRC. Either I make a wrong assumption or life is not so simple as I would it to be :-) thanks in advance. jan. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org -- This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
[SOURCE]: code repo move after graduation
Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. Any opinions? Juergen
Re: [SOURCE]: code repo move after graduation
On 10/24/12 1:40 PM, Jürgen Schmidt wrote: Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. ok, I noticed that Dave suggested already to use the complete name openoffice in the issue which is of course the best solution. This makes my email obsolete. Juergen
Re: [SOURCE]: code repo move after graduation
On 2012/10/24 19:43, Jürgen Schmidt said: On 10/24/12 1:40 PM, Jürgen Schmidt wrote: Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. ok, I noticed that Dave suggested already to use the complete name openoffice in the issue which is of course the best solution. openoffice agree! ^_*' This makes my email obsolete. Juergen -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/ signature.asc Description: OpenPGP digital signature
Re: Deadline for mailing llist changes
On Wed, Oct 24, 2012 at 3:45 AM, Alexandro Colorado j...@oooes.org wrote: Wonder if we have a deadline on mailing list naming? and if we know if the transition would be automagically or would need manual registration? I am sure the Apache Mentors know how INFRA works these transitions better. The instructions are here: http://incubator.apache.org/guides/graduation.html#transfer The JIRA issue for Infra is here: https://issues.apache.org/jira/browse/INFRA-5412 This is one of a set of graduation-related tasks that Infra will help with: https://issues.apache.org/jira/browse/INFRA-5407 -Rob Regards. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Need new logo for openoffice.apache.org
KG05 - see comments inline On Oct 24, 2012, at 6:05 PM, Alexandro Colorado j...@oooes.org wrote: On 10/24/12, Kevin Grignon kevingrignon...@gmail.com wrote: KG03 - see comments inline On Oct 24, 2012, at 4:50 PM, Alexandro Colorado j...@oooes.org wrote: On 10/23/12, Andrea Pescetti pesce...@apache.org wrote: Alexandro Colorado wrote: On 10/22/12, Kay Schenk wrote: hmmm...well, OK. I think I remember something like this now. Should we use Alexandro's new one at: https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg AFAIK there was no resolution on the fonts, the discussion ended on asking Michael Acevedo, but he never replied. Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly Who made Michael Acevedo the offical artist of AOO? If we are going to have a 'new' logo that automatically disqualify using MA logo as a whole. So far Nobody wants a proprietary fonts. So this logo is out. Now the issue is if there is any problem using an OpenType License font. done in SVG and it is the only SVG version of the orb we have available, since we never received one from Oracle; but the text has a slightly different formatting). We have two separate issues here: 1) Collecting and consolidating all versions of the logo we are using; here a 95% accuracy is not acceptable. These versions should be placed under http://www.openoffice.org/images/AOO_logos/ or anyway under SVN. Most logos are variation of the first one. We can generate a whole new set for 4.0, or we can even go back to the pre-Oracle OpenOffice brand refresh and get the OpenOffice with the gulls. The Orb was never part of the logo, it was label a 'symbol' to be used in a different context of the logo, just like the wireframe gulls was for 2.4. 2) Collecting proposals that can be useful as inspiration for a new visual identity; here it is of course acceptable to have variants of the official logos, but these should remain proposals and be placed in the wiki or such, possibly in pages that do not confuse a reader who types OpenOffice logo in a search engine. We need a framework to make decisions lazy conscensus, voting schemes, etc. But it seems there is a generalized knowledge that this is not only the logo but Application Icons, Mime Icons, and Module icons. Keeping a fresh logo with a very dated iconset is just not a good practice, specially for a 4.0 release. Regards, Andrea. Should this be taken to marketing list? Is really a non-coding topic and traditionally was handled by the art Project which was a subproject of marketing. Most of the visual identity and design need to be upstreamed to marketing to develop marketing kits. KG03 - our branding is tightly bound to visual elements (gui) in tools. Let's keep this activity with UX in design and dev discussions. Not really, actually if you look at UX between 2.4 and 3.0 the tool visual element never changed, except for icons, but wee are not discussing about creating a new set of icons, or are we? KG05 - I'm interested in exploring a broader rebrand, including app icons. Again, I have some design concepts to share. The styling would extend into other elements under consideration, such as start page updates. I'll post to ux wiki. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: Table of Contents Usability?
Thanks for sharing. We should add this issue to the ux design exploration backlog. On Oct 24, 2012, at 6:14 PM, Rory O'Farrell ofarr...@iol.ie wrote: On Wed, 24 Oct 2012 10:53:47 +0100 Rory O'Farrell ofarr...@iol.ie wrote: A recent thread on the en-Forum threw up problems with the interface of the Table of Contents generation. Perhaps Kevin Grignon might care to note this as an area worthy of improvement. http://forum.openoffice.org/en/forum/viewtopic.php?f=7t=56908 A further note on this in http://forum.openoffice.org/en/forum/viewtopic.php?f=106t=56976p=250998 -- Rory O'Farrell ofarr...@iol.ie
Re: Table of Contents Usability?
On 24.10.2012 12:14, Rory O'Farrell wrote: On Wed, 24 Oct 2012 10:53:47 +0100 Rory O'Farrell ofarr...@iol.ie wrote: A recent thread on the en-Forum threw up problems with the interface of the Table of Contents generation. Perhaps Kevin Grignon might care to note this as an area worthy of improvement. http://forum.openoffice.org/en/forum/viewtopic.php?f=7t=56908 A further note on this in http://forum.openoffice.org/en/forum/viewtopic.php?f=106t=56976p=250998 Maybe also user generated indices which cannot be hyperlinked. This is strange as well, as it seems to be natural that any generated table links to the references giving the page number, but not allowing one to hyperlink the entries. Hence exporting such documents to PDF will have hyperlinks on the TOC, but not on the user generated tables. (Rather, one needs to use a cumbersome trick that has to do with unused heading levels; something a regular writer user won't know about.) ---rony
Re: IPR PERMISSION
Sorry to say but there aren't any attachments, however often you sent this mail. Maybe you can upload it somewhere and send a link. Am 23.10.2012 12:21, schrieb ILLL Copyright: Please find the attachments.
[ApacheCon EU 2012] - travel subsidy ticket discount
Hi everyone, this is short notice to let the community know about the travel subsidies and ticket discounts that have been granted (from the old funds of SPI, http://www.spi-inc.org/) for the ApacheCon EU 2012: Travel subsidies: Yang Shih-Ching (imacat), Taiwan: 600,- Euro Dwayne Bailey, South Africa: 600,- Euro Ticket discount: Jean-Marie Daniel Lamaziere, France: 100,- Euro Best regards, Peter
Re: IPR PERMISSION
On 10/23/2012 7:42 PM, Rob Weir wrote: On Tue, Oct 23, 2012 at 6:18 AM, Peter Junge peter.ju...@gmx.org wrote: Dear Sumanyu Satpathy, we have been receiving several emails with attached documents in the moderation queue of this mailing list. As far as I understand it, you want to obtain permissions to use several screenshots of OpenOffice in publications. Hi Peter, If they are asking to use screenshots of OpenOffice in a book, we've received several requests like this in the past. The policy for this is here: http://www.apache.org/foundation/marks/faq/#insidebook If there use matches that description they could contact tradema...@apache.org directly, per the above policy. Well, I wanted to wait until Sumanyu Satpathy sends a usable request to the mailing list here. So far the mails that have been landing here refer attachments that have been stripped off. Peter -Rob Please, do not send one request for permission per every screen shot. Just contact this list (ooo-dev@incubator.apache.org) and describe your concern in general. I'm sure we'll find an easy solution. For now, I'm not moderating your other messages through because the attachments will be stripped of anyway. Best regards, Peter On 10/23/2012 5:30 PM, ILLL Copyright wrote: Please find the attachment.
Re: Deadline for mailing llist changes
Mailing list changes are transparent- we include an internal alias from the old name to the new one so there should be no interruption in service once the move is made. From: Rob Weir robw...@apache.org To: ooo-dev@incubator.apache.org Sent: Wednesday, October 24, 2012 8:29 AM Subject: Re: Deadline for mailing llist changes On Wed, Oct 24, 2012 at 3:45 AM, Alexandro Colorado j...@oooes.org wrote: Wonder if we have a deadline on mailing list naming? and if we know if the transition would be automagically or would need manual registration? I am sure the Apache Mentors know how INFRA works these transitions better. The instructions are here: http://incubator.apache.org/guides/graduation.html#transfer The JIRA issue for Infra is here: https://issues.apache.org/jira/browse/INFRA-5412 This is one of a set of graduation-related tasks that Infra will help with: https://issues.apache.org/jira/browse/INFRA-5407 -Rob Regards. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org
Re: OpenOffice graduation: translations of press release
On Wed, Oct 24, 2012 at 3:56 AM, Andrea Pescetti pesce...@apache.org wrote: On 22/10/2012 Guy Waterval wrote: 2012/10/18 Andrea Pescetti We welcome translations of today's press release about the OpenOffice graduation. What about the translations of the press release about the OpenOffice graduation?. Are we authorized to diffuse them or not. Somebody has asked me to use my french translation, but as I don't know if a validation process is ongoing, I asked to wait. Sorry for the delay, I've uploaded the French translation to http://www.openoffice.org/fr/news/2012-10-graduation.html and Rob will then link to it from https://blogs.apache.org/OOo/entry/openoffice_graduates_from_the_apache Done. If we may diffuse, what is the right way? Links to the above pages will work. But the text can be republished too. In that case, though, I would insert a link to the original post/page. Right. I think the French AOO community within the project would know best how to spread the news: social networking sites, Francophone forums, local journalists, bloggers, etc. -Rob Regards, Andrea.
Re: [QA BUG] - some regression defects were found by GUI perfromance test
Hi, On 24.10.2012 07:34, Linyi Li wrote: I did GUI performance test of AOO trunk build. I found some defects[1][2][3], and two of them are regression ones[1][2]. Great finds and great bug reports, thank you! And kudos to the wonderful automated testing framework that allows to run such extensive tests with that thoroughness and frequency. I think defects[1][2] are severe which will block users‘ normal use of AOO, so is there anyone who can help to fix these defects? I looked into them and updated their status: [1] Bug 121199 - [Automation][Regression]Crashed when loading 2 docx files. The patch that caused the crashes is known and reverting it solves the problem. But probably the patch can be updated to fix both the new and the original issues. The developers knowing the patch best were CC'ed. [2] Bug 121200 - [Regression][Automation][Performance]Severe downgrade to save xls sample files. This seems to be fixed in the current trunk revision. [3] Bug 121256 - Crash when saving ppt on Linux. This cannot be reproduced here. If anyone sees the problem please attach a stack trace in the issue. If possible for a build with sufficient debug info. Herbert
[RELEASE]: new snapshot base don revision r1400866
Hi, a new snapshot build is available for MacOS and Windows. Linux will be available later. See https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds I have called it 3.5 snapshot but we haven't really confirmed if our next release will be a 3.5 or 4.0. That can be discussed and decided when we have finalized our plans. The snapshot is build on top of revision r1400866. I have provided full install set for all supported languages and a further language pack for en-US + the SDK and src release. Supported languages are: ar cs da de en-GB en-US es fi fr gd gl hu it ja km ko nb nl pt-BR ru sk sl zh-CN zh-TW @Ariel: I have changed columns in the wiki and moved MacOS before Linux, it makes it easier for me ;-) Juergen
Re: [SOURCE]: code repo move after graduation
+1 openoffice Ditto for bugzilla. Pedro. ps. FWIW, it would've been nice to attempt to rescue the history and put it under the carpet (even just the SVN stuff was useful) but it's a lot more work than anyone would care to do at this point. - Original Message - From: imacat Subject: Re: [SOURCE]: code repo move after graduation On 2012/10/24 19:43, Jürgen Schmidt said: On 10/24/12 1:40 PM, Jürgen Schmidt wrote: Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. ok, I noticed that Dave suggested already to use the complete name openoffice in the issue which is of course the best solution. openoffice agree! ^_*' This makes my email obsolete. Juergen -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/
Re: Directory main/swext/mediawiki
Roberto: I cannot tell if the problem is in the extension, but the behavior is as follow: 1) I do a confgure --with-lang --enable-wiki-publisher IT WORKS. 2) I do a configure --enable-wiki-publisher I get the license problem 3) I modify description.xml and remove the tag simple_license, and rebuilt/reinstall main/swext/mediawiki IT WORKS. So, please excuse me, but it seems to me that the extension do have a problem, or ??? rgds Jan I. On 24 October 2012 12:52, Roberto Galoppini rgalopp...@geek.net wrote: On Tue, Oct 23, 2012 at 10:49 AM, jan iversen jancasacon...@gmail.com wrote: Thanks. I have not sent a specific request to you, but asked it as a general question (because I did not know who to ask). In the meantime, I found out that the sources in swext/mediawiki are in use, so I have compiled AOO with --enable-wiki-publisher. As far as I know http://extensions.openoffice.org/en/project/wikipublisher is based on 2009 source code, and it has not been updated since. Now my only problem is that, when I install the ocx via extension manager, I get a dialog box, stating that there might be a problem with description.xml because there is a license problem. I have tried to configure --with-lang=en, and rebuilt AOO, but that does not seem to help. I have no clue about why you get warnings, but I'm pretty sure this is not related to Extensions. Roberto So if you have an idea I would be thankfull. Are you working with the mediawiki sources, because the reason I do this was to fix a couple of problems I have found. Jan. On 23 October 2012 10:06, Roberto Galoppini rgalopp...@geek.net wrote: On Sun, Oct 21, 2012 at 6:24 PM, jan iversen jancasacon...@gmail.com wrote: I have looked for a newer source, since it was moved, but our own extensions has a broken link and sourceForge does not offer any help. Any ideas ?? Hi Jan, I don't think I've received any request from you, please let me know what's the problem, and I'll do my best to help you. Roberto It is a sun part, so we should have inherited it or not ? jan. On 20 October 2012 23:52, Alexandro Colorado j...@oooes.org wrote: On Sat, Oct 20, 2012 at 2:50 PM, jan iversen jancasacon...@gmail.com wrote: I am a bit confused. We have a directory named main/swext/mediawiki. Is that the sun wiki publisher 1.1 or are there 2 different mediawiki export extensions ? I ask because I sun wiki publisher 1.1 installed, but if I change the XLS and rebuilt AOO but it does not seem to have an effect. Yes I think it was started on core, and then sent to a separate extensions. Same thing happened with smarttags IIRC. Either I make a wrong assumption or life is not so simple as I would it to be :-) thanks in advance. jan. -- Alexandro Colorado PPMC Apache OpenOffice http://es.openoffice.org -- This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: [SOURCE]: code repo move after graduation
Question: If have made a svn co on the incubator version, will I have to do a new svn co on the new path, or will svn update (as usual) work ??? rgds Jan I. On 24 October 2012 18:16, Pedro Giffuni p...@apache.org wrote: +1 openoffice Ditto for bugzilla. Pedro. ps. FWIW, it would've been nice to attempt to rescue the history and put it under the carpet (even just the SVN stuff was useful) but it's a lot more work than anyone would care to do at this point. - Original Message - From: imacat Subject: Re: [SOURCE]: code repo move after graduation On 2012/10/24 19:43, Jürgen Schmidt said: On 10/24/12 1:40 PM, Jürgen Schmidt wrote: Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. ok, I noticed that Dave suggested already to use the complete name openoffice in the issue which is of course the best solution. openoffice agree! ^_*' This makes my email obsolete. Juergen -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/
Re: [SOURCE]: code repo move after graduation
On Wed, Oct 24, 2012 at 12:19 PM, jan iversen jancasacon...@gmail.com wrote: Question: If have made a svn co on the incubator version, will I have to do a new svn co on the new path, or will svn update (as usual) work ??? There is a command: svn switch that you will need to execute: http://svnbook.red-bean.com/en/1.6/svn.ref.svn.c.switch.html Hopefully someone will send out the specific command once the tree is moved. -Rob rgds Jan I. On 24 October 2012 18:16, Pedro Giffuni p...@apache.org wrote: +1 openoffice Ditto for bugzilla. Pedro. ps. FWIW, it would've been nice to attempt to rescue the history and put it under the carpet (even just the SVN stuff was useful) but it's a lot more work than anyone would care to do at this point. - Original Message - From: imacat Subject: Re: [SOURCE]: code repo move after graduation On 2012/10/24 19:43, Jürgen Schmidt said: On 10/24/12 1:40 PM, Jürgen Schmidt wrote: Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. ok, I noticed that Dave suggested already to use the complete name openoffice in the issue which is of course the best solution. openoffice agree! ^_*' This makes my email obsolete. Juergen -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/
Re: [SOURCE]: code repo move after graduation
On Wed, Oct 24, 2012 at 12:16 PM, Pedro Giffuni p...@apache.org wrote: +1 openoffice Ditto for bugzilla. And maybe the blog, which is current: http://blogs.apache.org/ooo/ Or ideally we would promote a shortcut URL like blogs.openoffice.org and have it redirect. Pedro. ps. FWIW, it would've been nice to attempt to rescue the history and put it under the carpet (even just the SVN stuff was useful) but it's a lot more work than anyone would care to do at this point. I don't think we lose any history. It is just an svn mv. - Original Message - From: imacat Subject: Re: [SOURCE]: code repo move after graduation On 2012/10/24 19:43, Jürgen Schmidt said: On 10/24/12 1:40 PM, Jürgen Schmidt wrote: Hi, jira issue https://issues.apache.org/jira/browse/INFRA-5417 covers the move of the source repository into the new final place as part of our post graduation tasks. I am thinking if we can and should rename it from ooo to aoo to reflect the name Apache OpenOffice instead of OpenOffice .org. ok, I noticed that Dave suggested already to use the complete name openoffice in the issue which is of course the best solution. openoffice agree! ^_*' This makes my email obsolete. Juergen -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/
Re: AOO volunteers: essential skills and tasks
After a day of work, maybe I should elaborate on what I mean: Having read your documents in detail, which I really find SUPER, I see one challenge: old people in the mailing list pretty much knows who is working on (sort of responsible for) a given part, so they have no problems with proposals since they know who to approach, and the JFDI methods works well. new volunteers who wants to follow what happens and do a little here and there, will typically not make [proposals] but do JFDI on the wiki, and otherwise look for questions. The last part, those who want to be integrated and help move things, do have a slight problem: [proposals] might not even be responded to, especially if they fall in one of two catagories: - this is something we have discussed before - somebody is working on the theme JFDI method might be even worse, because you spent hours doing something sent it off to a committer and zero I believe in both methods, but I really believe that JFDI should be AFJFDI (asf first if anyone is working on it), and then do it. The proposal part is a bit harder, and maybe your document should state wait with proposals until you are integrated in the commnity. once again, your document are SUPER...the rest is just my experience. jan. On 24 October 2012 10:09, jan iversen jancasacon...@gmail.com wrote: +1, that was something I could really have used some weeks ago :-) Maybe a word about active volunteers might not be harmful (I think I am in that state now) Jan I. On 23 October 2012 23:30, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list them. Also indicate that you have now completed Level 2. Get the idea? After Level 2 this then could branch off into area-specific lists of start up tasks: how to download and build. How to submit patches. How to update a translation. How to define a new test case. Is any one interested in helping with this? Quick update. I have drafts of a few of the pages ready. 1) New Volunteer Orientation root page: http://incubator.apache.org/openofficeorg/orientation/ 2) Introduction to Contributing to Apache OpenOffice (Level 1): http://incubator.apache.org/openofficeorg/orientation/level-1.html 3) Intermediate Social and Technical Tools (Level 2): http://incubator.apache.org/openofficeorg/orientation/level-2.html (around half done). I could really use some help drafting the area-specific Level 3 and Level 4 pages, from subject matter experts. -Rob
Re: [SOURCE]: code repo move after graduation
Rob Weir wrote on Wed, Oct 24, 2012 at 12:24:29 -0400: On Wed, Oct 24, 2012 at 12:19 PM, jan iversen jancasacon...@gmail.com wrote: Question: If have made a svn co on the incubator version, will I have to do a new svn co on the new path, or will svn update (as usual) work ??? There is a command: svn switch that you will need to execute: http://svnbook.red-bean.com/en/1.6/svn.ref.svn.c.switch.html Hopefully someone will send out the specific command once the tree is moved. Assuming % svn info | grep URL URL: http://svn.apache.org/repos/asf/incubator/ooo/foo you'd run % svn switch ^/openoffice/foo This will also update to HEAD as part of the operation.
Re: User list and donations
On 10/24/2012 12:43 AM, Alexandro Colorado wrote: Probably he talks about the URL embedded on the UI like get extensions here, and this launch some MS email client like outlook. He would need to configure his OS to use yahoo webmail. http://uk.answers.yahoo.com/question/index?qid=20070217130008AAsCjy1 That said, this user seems a bit unsophisticated to perform this tasks or tell the difference between email clients and mailing list. It sounds like he doesn't have Yahoo mail configured as his default mail client...maybe we just send him this link from Yahoo Help http://help.yahoo.com/l/us/yahoo/mail/yahoomail/settings/settings-10.html I suspect this may be one of the few times he's used something that requires an automatic open of an email window/interface. On 10/24/12, Jürgen Schmidt jogischm...@gmail.com wrote: On 10/24/12 1:37 AM, Karl Glode wrote: Hi I have just updated my Apache Home Office. I have tried to contact you by clicking the appropiate button but Microsoft email site wants to open.I never use MS email these days, i use Yahoo7. How do I make this happen that Y7 opens instead of MS Karl the mail is moderated but I have no idea what he is doing and how we can help. Does anybody else have an idea? Juergen -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: AOO volunteers: essential skills and tasks
On Wed, Oct 24, 2012 at 12:30 PM, jan iversen jancasacon...@gmail.com wrote: After a day of work, maybe I should elaborate on what I mean: Having read your documents in detail, which I really find SUPER, I see one challenge: old people in the mailing list pretty much knows who is working on (sort of responsible for) a given part, so they have no problems with proposals since they know who to approach, and the JFDI methods works well. new volunteers who wants to follow what happens and do a little here and there, will typically not make [proposals] but do JFDI on the wiki, and otherwise look for questions. The last part, those who want to be integrated and help move things, do have a slight problem: [proposals] might not even be responded to, especially if they fall in one of two catagories: - this is something we have discussed before - somebody is working on the theme JFDI method might be even worse, because you spent hours doing something sent it off to a committer and zero This is also a possible conflict between two new volunteers, or even two old volunteers. If you go off and work on something for a month without telling anyone, then you risk that someone old or new does the same thing, or similar. That is a point worth mentioning, that for larger jobs, you might want to mention it on the list, not because it is controversial, but just for coordination purposes, so others are aware. Maybe they even offer to help or give some helpful ideas. I can include these ideas in the text. I believe in both methods, but I really believe that JFDI should be AFJFDI (asf first if anyone is working on it), and then do it. The proposal part is a bit harder, and maybe your document should state wait with proposals until you are integrated in the commnity. Certainly for larger tasks, this makes sense. But if it is a quick operation then JFDI works. I suppose it depends on the time-to-JFDI/time-to-post-and-wait-72-hours ratio. For new volunteers they don't have access to SVN, so everything they do is essentially RTC. So submitting their patches is essentially like making a proposal. But the same considerations apply. It might make sense to float the idea first before investing a lot of time in the work. once again, your document are SUPER...the rest is just my experience. jan. On 24 October 2012 10:09, jan iversen jancasacon...@gmail.com wrote: +1, that was something I could really have used some weeks ago :-) Maybe a word about active volunteers might not be harmful (I think I am in that state now) Jan I. On 23 October 2012 23:30, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more
Re: AOO volunteers: essential skills and tasks
On 10/24/2012 09:40 AM, Rob Weir wrote: On Wed, Oct 24, 2012 at 12:30 PM, jan iversen jancasacon...@gmail.com wrote: After a day of work, maybe I should elaborate on what I mean: Having read your documents in detail, which I really find SUPER, I see one challenge: old people in the mailing list pretty much knows who is working on (sort of responsible for) a given part, so they have no problems with proposals since they know who to approach, and the JFDI methods works well. new volunteers who wants to follow what happens and do a little here and there, will typically not make [proposals] but do JFDI on the wiki, and otherwise look for questions. The last part, those who want to be integrated and help move things, do have a slight problem: [proposals] might not even be responded to, especially if they fall in one of two catagories: - this is something we have discussed before - somebody is working on the theme JFDI method might be even worse, because you spent hours doing something sent it off to a committer and zero This is also a possible conflict between two new volunteers, or even two old volunteers. If you go off and work on something for a month without telling anyone, then you risk that someone old or new does the same thing, or similar. That is a point worth mentioning, that for larger jobs, you might want to mention it on the list, not because it is controversial, but just for coordination purposes, so others are aware. Maybe they even offer to help or give some helpful ideas. I can include these ideas in the text. I believe in both methods, but I really believe that JFDI should be AFJFDI (asf first if anyone is working on it), and then do it. The proposal part is a bit harder, and maybe your document should state wait with proposals until you are integrated in the commnity. Certainly for larger tasks, this makes sense. But if it is a quick operation then JFDI works. I suppose it depends on the time-to-JFDI/time-to-post-and-wait-72-hours ratio. For new volunteers they don't have access to SVN, so everything they do is essentially RTC. So submitting their patches is essentially like making a proposal. But the same considerations apply. It might make sense to float the idea first before investing a lot of time in the work. once again, your document are SUPER...the rest is just my experience. jan. On 24 October 2012 10:09, jan iversen jancasacon...@gmail.com wrote: +1, that was something I could really have used some weeks ago :-) Maybe a word about active volunteers might not be harmful (I think I am in that state now) Jan I. On 23 October 2012 23:30, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4) Introduction to the various functional groups within the project: development, qa, marketing, UX, documentation, support, localization, etc. 5) Pick one or more functional groups that you want to help with. Edit the volunteer wiki and list
svn update, simple question.
Hi. If I do a svn update trunk (I have all sources stored in directory trunk, do I then need to run configure again ??? my system seems to be spinning, after svn update I cannot run build in the single directories that all worked before svn update. Simple question, hopefully simple answer :-) jan.
Re: AOO volunteers: essential skills and tasks
+1 Anything is better than nothing !!! and afterwards it can be improved. jan On 24 October 2012 18:49, Kay Schenk kay.sch...@gmail.com wrote: On 10/24/2012 09:40 AM, Rob Weir wrote: On Wed, Oct 24, 2012 at 12:30 PM, jan iversen jancasacon...@gmail.com wrote: After a day of work, maybe I should elaborate on what I mean: Having read your documents in detail, which I really find SUPER, I see one challenge: old people in the mailing list pretty much knows who is working on (sort of responsible for) a given part, so they have no problems with proposals since they know who to approach, and the JFDI methods works well. new volunteers who wants to follow what happens and do a little here and there, will typically not make [proposals] but do JFDI on the wiki, and otherwise look for questions. The last part, those who want to be integrated and help move things, do have a slight problem: [proposals] might not even be responded to, especially if they fall in one of two catagories: - this is something we have discussed before - somebody is working on the theme JFDI method might be even worse, because you spent hours doing something sent it off to a committer and zero This is also a possible conflict between two new volunteers, or even two old volunteers. If you go off and work on something for a month without telling anyone, then you risk that someone old or new does the same thing, or similar. That is a point worth mentioning, that for larger jobs, you might want to mention it on the list, not because it is controversial, but just for coordination purposes, so others are aware. Maybe they even offer to help or give some helpful ideas. I can include these ideas in the text. I believe in both methods, but I really believe that JFDI should be AFJFDI (asf first if anyone is working on it), and then do it. The proposal part is a bit harder, and maybe your document should state wait with proposals until you are integrated in the commnity. Certainly for larger tasks, this makes sense. But if it is a quick operation then JFDI works. I suppose it depends on the time-to-JFDI/time-to-post-and-**wait-72-hours ratio. For new volunteers they don't have access to SVN, so everything they do is essentially RTC. So submitting their patches is essentially like making a proposal. But the same considerations apply. It might make sense to float the idea first before investing a lot of time in the work. once again, your document are SUPER...the rest is just my experience. jan. On 24 October 2012 10:09, jan iversen jancasacon...@gmail.com wrote: +1, that was something I could really have used some weeks ago :-) Maybe a word about active volunteers might not be harmful (I think I am in that state now) Jan I. On 23 October 2012 23:30, Rob Weir robw...@apache.org wrote: On Fri, Oct 19, 2012 at 12:17 PM, Rob Weir robw...@apache.org wrote: I am thinking about what new project volunteers need to get started. Obviously there are area-specific things. For example, developers need to know how to download and build. Translation volunteers need to understand Pootle, etc. But there are also some basic things that all volunteers should probably do. Although we have all of this information (or at least most of it) on the website or wikis or mailing list archives, it is scattered all over the place. I think it would be good if we could collect this information (or at least links to this information) into one place and put a linear order behind it, a step of specific steps we want new volunteers to take. Now, I can hear the objections already -- you can't tell volunteers what to do. That is why they are volunteers. You can't regiment them, etc. This is true. But at the scale we need to operate at -- I'm aiming to attract dozens of new volunteers on the project by the end of the year -- we need some structure. So what can we do to make their first 2 weeks in the project easier for them, and easier for us? One idea: Think of the new volunteer startup tasks in terms of stages or levels, a defined set of reading and other activities that leads them to acquire basic skills in our community. For example: Level 1 tasks: 1) Read the following web pages on the ASF, roles at Apache and the Apache Way 2) Sign up for the following accounts that every volunteer should have: ooo-announce, ooo-dev, ooo-users, MWiki, CWiki, BZ, Forums 3) Read this helpful document on hints for managing your inbox with rules and folders 4) Read this code of conduct page on list etiquette 5) Send a note to ooo-dev list and introduce yourself 6) Edit this wiki page containing project volunteers. Add your name and indicate that you have completed Level 1. Level 2 tasks: 1) Using the Apache CMS in anonymous mode 2) Readings on decision making at Apache 3) Readings on project life cycle and roles within the AOO project 4)
Re: discussion on new l10n workflow
Hi Jan, On 12-10-16, at 12:22 , jan iversen jancasacon...@gmail.com wrote: Finally I have finished describing the current process, and also combining all the notes on open issues I could find. Thanks. A lot of work. Last it was dealt with was probably (prior to Apache's advent) back in…. I hate to say, last century. Please have a look at: http://wiki.openoffice.org/wiki/File:L10proc.pdf Indeed. and http://wiki.openoffice.org/wiki/Localization_AOO I hope we can have a discussion on the open issues, and then I will make a design document for a changed workflow. I look forward to hear your opinion, either through wiki or mail. These comments will be worked into the document. have a nice day. jan I I'll go over it. Usually, as others no doubt will mention, my impression is that a big issue has always been qualifying the outcome, incorporating input, and normalizing it, so that what happens in, say, January, can be expected to continue on into the future. A sidle point has perhaps also do with working with the LibreOffice team—and others working using similar strings, e.g., those nice people at that Mozilla project, among others. Under the Sun regime, licensing issues foreclosed that option. I'd hate to think we are still hobbled by political considerations and that these undercut the terrific enterprise of people like you. Thanks Louis
Re: discussion on new l10n workflow
Thanks for your kind words. see below please: On 24 October 2012 19:49, Louis Suárez-Potts lui...@gmail.com wrote: Hi Jan, On 12-10-16, at 12:22 , jan iversen jancasacon...@gmail.com wrote: Finally I have finished describing the current process, and also combining all the notes on open issues I could find. Thanks. A lot of work. Last it was dealt with was probably (prior to Apache's advent) back in…. I hate to say, last century. Please have a look at: http://wiki.openoffice.org/wiki/File:L10proc.pdf Indeed. and http://wiki.openoffice.org/wiki/Localization_AOO I hope we can have a discussion on the open issues, and then I will make a design document for a changed workflow. I look forward to hear your opinion, either through wiki or mail. These comments will be worked into the document. have a nice day. jan I I'll go over it. Usually, as others no doubt will mention, my impression is that a big issue has always been qualifying the outcome, incorporating input, and normalizing it, so that what happens in, say, January, can be expected to continue on into the future. It was a big job, first describing the current process and run it several times to make sure I understood it, and then think about how to do more robust and future oriented. I have had a helping hand from my professional background where I used to manage project with these kind of problemsets. I would appreciate any input, this is a floating process, development/discussion. A sidle point has perhaps also do with working with the LibreOffice team—and others working using similar strings, e.g., those nice people at that Mozilla project, among others. Under the Sun regime, licensing issues foreclosed that option. I'd hate to think we are still hobbled by political considerations and that these undercut the terrific enterprise of people like you. I am very open minded to that respect, but honestly I have no idea what the apache policy is. Thanks Louis
Re: discussion on new l10n workflow
May I politely ask if there are other comments or more importantly objections ? If not I will continue with the process and keep you posted, please remember comments are also welcome as the new workflow takes shape. Jan I. On 24 October 2012 20:18, jan iversen jancasacon...@gmail.com wrote: Thanks for your kind words. see below please: On 24 October 2012 19:49, Louis Suárez-Potts lui...@gmail.com wrote: Hi Jan, On 12-10-16, at 12:22 , jan iversen jancasacon...@gmail.com wrote: Finally I have finished describing the current process, and also combining all the notes on open issues I could find. Thanks. A lot of work. Last it was dealt with was probably (prior to Apache's advent) back in…. I hate to say, last century. Please have a look at: http://wiki.openoffice.org/wiki/File:L10proc.pdf Indeed. and http://wiki.openoffice.org/wiki/Localization_AOO I hope we can have a discussion on the open issues, and then I will make a design document for a changed workflow. I look forward to hear your opinion, either through wiki or mail. These comments will be worked into the document. have a nice day. jan I I'll go over it. Usually, as others no doubt will mention, my impression is that a big issue has always been qualifying the outcome, incorporating input, and normalizing it, so that what happens in, say, January, can be expected to continue on into the future. It was a big job, first describing the current process and run it several times to make sure I understood it, and then think about how to do more robust and future oriented. I have had a helping hand from my professional background where I used to manage project with these kind of problemsets. I would appreciate any input, this is a floating process, development/discussion. A sidle point has perhaps also do with working with the LibreOffice team—and others working using similar strings, e.g., those nice people at that Mozilla project, among others. Under the Sun regime, licensing issues foreclosed that option. I'd hate to think we are still hobbled by political considerations and that these undercut the terrific enterprise of people like you. I am very open minded to that respect, but honestly I have no idea what the apache policy is. Thanks Louis
Volunteers, Contributors, Committers, PMC members -- is there any way to consolidate these lists?
We have the following today: 1) http://incubator.apache.org/openofficeorg/people.html -- This lists a variety of people involved in the project, independent of status. 2) I'd like to have a place for new volunteers to put their names, preferably on the wiki or some place where a non-committer has easy access. 3) We have a list of Committers here, automatically generated: http://people.apache.org/committers-by-project.html#ooo 4) We don't have anything that indicates which Committers are also PMC members. 5) We have this credits page, which is linked to from our Help/About dialog box. But it does not appear to be updated for AOO 3.4.0 or 3.4.1: http://www.openoffice.org/welcome/credits.html 6) Wiki User pages 7) Any others? As we all know, with multiple lists like this things will get out of synch. In fact they already have. One simplification idea might be: 1) Convert the people.html page into a wiki page 2) Have that page indicate who is a Committer or PMC member. That can be manual for now. 3) Point our Help/About box to the wiki page, and add sentence at the end of the wiki that says, OpenOffice has a long history and we also thank those who contributed to it before our move to Apache and then link to credits.html Any objections to this general idea? Any improvements? And if we did want a place to have a big table of volunteers, where on the wiki should we put it (CWiki or MWiki)? -Rob
[PROPOSAL] difficulty field for Bugzilla
As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. Regards, -Rob
Re: Volunteers, Contributors, Committers, PMC members -- is there any way to consolidate these lists?
On 24 October 2012 20:56, Rob Weir robw...@apache.org wrote: We have the following today: 1) http://incubator.apache.org/openofficeorg/people.html -- This lists a variety of people involved in the project, independent of status. 2) I'd like to have a place for new volunteers to put their names, preferably on the wiki or some place where a non-committer has easy access. +1, very good idea...but may I suggest that we formalize the skill set description a bit (sort of check boxes), and add a field interest in AOO, (e.g. l10n) making it easier for others to see where help can come from. 3) We have a list of Committers here, automatically generated: http://people.apache.org/committers-by-project.html#ooo I would be nice to know the same about committers, and especially which areas the commit, I know in theory all, but I assume in praxise the areas they know well. 4) We don't have anything that indicates which Committers are also PMC members. Is that an important difference in daily life ? 5) We have this credits page, which is linked to from our Help/About dialog box. But it does not appear to be updated for AOO 3.4.0 or 3.4.1: http://www.openoffice.org/welcome/credits.html 6) Wiki User pages 7) Any others? As we all know, with multiple lists like this things will get out of synch. In fact they already have. One simplification idea might be: 1) Convert the people.html page into a wiki page +1 and merge with contributors ?? 2) Have that page indicate who is a Committer or PMC member. That can be manual for now. 3) Point our Help/About box to the wiki page, and add sentence at the end of the wiki that says, OpenOffice has a long history and we also thank those who contributed to it before our move to Apache and then link to credits.html Any objections to this general idea? Any improvements? And if we did want a place to have a big table of volunteers, where on the wiki should we put it (CWiki or MWiki)? MWiki...that is OUR wiki, CWiki is for whole apache or ? -Rob
Re: [PROPOSAL] difficulty field for Bugzilla
+1 On 24 October 2012 21:08, Rob Weir robw...@apache.org wrote: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. Regards, -Rob
Re: discussion on new l10n workflow
On 12-10-24, at 14:35 , jan iversen jancasacon...@gmail.com wrote: May I politely ask if there are other comments or more importantly objections ? Press on. And expect to be patient: this is a volunteer effort. I'd also, if I were you, see about highlighting this effort at ApacheCon EU or NA (next year). If you cannot personally make the EU event, you can ask a surrogate, perhaps. But the issue is indeed very important, at least as I see it. For it leads to expanding the AOO contributor base, being that localization efforts are among the most interesting to a range of audiences, who rightly see a localized AOO as much easier to work with than one in English. If not I will continue with the process and keep you posted, please remember comments are also welcome as the new workflow takes shape. Please! also, don't hesitate to use other channels, such as Facebook, our wikis, etc. best louis Jan I. On 24 October 2012 20:18, jan iversen jancasacon...@gmail.com wrote: Thanks for your kind words. see below please: On 24 October 2012 19:49, Louis Suárez-Potts lui...@gmail.com wrote: Hi Jan, On 12-10-16, at 12:22 , jan iversen jancasacon...@gmail.com wrote: Finally I have finished describing the current process, and also combining all the notes on open issues I could find. Thanks. A lot of work. Last it was dealt with was probably (prior to Apache's advent) back in…. I hate to say, last century. Please have a look at: http://wiki.openoffice.org/wiki/File:L10proc.pdf Indeed. and http://wiki.openoffice.org/wiki/Localization_AOO I hope we can have a discussion on the open issues, and then I will make a design document for a changed workflow. I look forward to hear your opinion, either through wiki or mail. These comments will be worked into the document. have a nice day. jan I I'll go over it. Usually, as others no doubt will mention, my impression is that a big issue has always been qualifying the outcome, incorporating input, and normalizing it, so that what happens in, say, January, can be expected to continue on into the future. It was a big job, first describing the current process and run it several times to make sure I understood it, and then think about how to do more robust and future oriented. I have had a helping hand from my professional background where I used to manage project with these kind of problemsets. I would appreciate any input, this is a floating process, development/discussion. A sidle point has perhaps also do with working with the LibreOffice team—and others working using similar strings, e.g., those nice people at that Mozilla project, among others. Under the Sun regime, licensing issues foreclosed that option. I'd hate to think we are still hobbled by political considerations and that these undercut the terrific enterprise of people like you. I am very open minded to that respect, but honestly I have no idea what the apache policy is. Thanks Louis
Re: [PROPOSAL] difficulty field for Bugzilla
Emphatic +1 Louis On 12-10-24, at 15:08 , Rob Weir robw...@apache.org wrote: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. Regards, -Rob
Re: [PROPOSAL] difficulty field for Bugzilla
Hi Rob, that's a cool idea. +1 but I would use the word complexity instead of difficulty. Usually the issue tracker database is customer driven (severity) but a helper field to sort bugs by complexity will help developers to focus on more complex issues. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD Kind regards, Joost
Re: discussion on new l10n workflow
Where can I read more about ApacheCon EU or NA ? I cannot quite follow you here (mainly due to terms), is this about getting sponsor money to AOO ? It should be easy to get somebody from EU and others, I could call on the NLC to help QA and general testing. jan. On 24 October 2012 21:53, Louis Suárez-Potts lui...@gmail.com wrote: On 12-10-24, at 14:35 , jan iversen jancasacon...@gmail.com wrote: May I politely ask if there are other comments or more importantly objections ? Press on. And expect to be patient: this is a volunteer effort. I 'd also, if I were you, see about highlighting this effort at ApacheCon EU or NA (next year). If you cannot personally make the EU event, you can ask a surrogate, perhaps. But the issue is indeed very important, at least as I see it. For it leads to expanding the AOO contributor base, being that localization efforts are among the most interesting to a range of audiences, who rightly see a localized AOO as much easier to work with than one in English. If not I will continue with the process and keep you posted, please remember comments are also welcome as the new workflow takes shape. Please! also, don't hesitate to use other channels, such as Facebook, our wikis, etc. best louis Jan I. On 24 October 2012 20:18, jan iversen jancasacon...@gmail.com wrote: Thanks for your kind words. see below please: On 24 October 2012 19:49, Louis Suárez-Potts lui...@gmail.com wrote: Hi Jan, On 12-10-16, at 12:22 , jan iversen jancasacon...@gmail.com wrote: Finally I have finished describing the current process, and also combining all the notes on open issues I could find. Thanks. A lot of work. Last it was dealt with was probably (prior to Apache's advent) back in…. I hate to say, last century. Please have a look at: http://wiki.openoffice.org/wiki/File:L10proc.pdf Indeed. and http://wiki.openoffice.org/wiki/Localization_AOO I hope we can have a discussion on the open issues, and then I will make a design document for a changed workflow. I look forward to hear your opinion, either through wiki or mail. These comments will be worked into the document. have a nice day. jan I I'll go over it. Usually, as others no doubt will mention, my impression is that a big issue has always been qualifying the outcome, incorporating input, and normalizing it, so that what happens in, say, January, can be expected to continue on into the future. It was a big job, first describing the current process and run it several times to make sure I understood it, and then think about how to do more robust and future oriented. I have had a helping hand from my professional background where I used to manage project with these kind of problemsets. I would appreciate any input, this is a floating process, development/discussion. A sidle point has perhaps also do with working with the LibreOffice team—and others working using similar strings, e.g., those nice people at that Mozilla project, among others. Under the Sun regime, licensing issues foreclosed that option. I'd hate to think we are still hobbled by political considerations and that these undercut the terrific enterprise of people like you. I am very open minded to that respect, but honestly I have no idea what the apache policy is. Thanks Louis
Re: [PROPOSAL] difficulty field for Bugzilla
Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL sounds devaluating to me. Perhaps BEGINNER or STARTER is more neutral? Being able to start is not only a question, whether the task is easy or not from an objective point of view. Beyond that a mentor is needed. Perhaps a category MENTORED instead of TRIVIAL is useful. A senior developer would set it (and put himself in CC) if he is willing to guide a newcomer. (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. In general I thing it is a good idea. Using Bugzilla has the advantage, that it is not necessary to hold a Wiki page in sync with Bugzilla. Kind regards Regina
Re: Automatically Generated extension.update.xml
On Mon, Oct 22, 2012 at 6:33 PM, imacat ima...@mail.imacat.idv.tw wrote: So, who is managing extensions.openoffice.org? Is it possible that we can turn on the online update and try to solve this problem now? When an extension is loaded on extensions.openoffice.org the XML file is automatically built correctly. Apparently this was causing traffic problems as well as functional issues '(for example, if only the Windows version of an extension is updated also Mac/LInux users would get the information that an update is now available). As far as I know at some point Oracle started using empty XML files indicating that there are no updates. We might have a look at the code, do some performance testing and eventually get it back. I will add this to the list of the 'nice to have' features/changes I'll cover at Apache Con session dedicated to Extensions and Templates. Roberto On 2012/10/22 19:27, Jürgen Schmidt said: On 10/21/12 11:13 PM, Andrea Pescetti wrote: imacat wrote: I wonder if it is possible to generate the extension update information files extension.update.xml automatically on http://extensions.openoffice.org, instead of maintaining the update information files by the authors manually? This requires a slightly complex answer since there are differences between theory and practice. In theory, when you upload an extension to extensions.openoffice.org, you needn't provide an update XML file: the repository knows about the mechanism and automatically generates it. Moreover, OpenOffice knows where to ask for the update so, if you use the official repository to host your extension, updates will magically work with no need of actions from the developer (not even specify an update URL), aside possibly from making sure that the version number always increases. In practice, the process is broken. The point where it breaks is the fact that extensions.openoffice.org does not provide the real update information but it sends a hardcoded answer instead, saying that no updates are available. This was done back in the Oracle times for some reasons - probably traffic, but I have no clue here, maybe it was just broken. Fact is, what you ask for is already available in theory and I have seen it working for a period before it was disabled in 2010. But it isn't available in practice at the moment, and it hasn't been for years. On the application side (the OpenOffice program) everything should still be working, even though I've recently seen an issue where Ariel explained we might have some regressions on the OpenOffice side too: https://issues.apache.org/ooo/show_bug.cgi?id=121201 mmh, I was not ware that this function was disabled in 2010 and I don't know the reason for it. But Roberto has explained it quite well and the idea behind it was exactly that for extensions hosted in our repo the update information is generated automatically and the extensions shouldn't add further update information in their description.xml. We should figure out if the mechanism still works and should enable it. Ariel reported indeed a problem with his updates but we have to check this in general because I at least was not able to reproduce all reported problems. But this is a separate issue and have to fixed independently. Juergen -- Best regards, imacat ^_*' ima...@mail.imacat.idv.tw PGP Key http://www.imacat.idv.tw/me/pgpkey.asc Woman's Voice News: http://www.wov.idv.tw/ Tavern IMACAT's http://www.imacat.idv.tw/ Woman in FOSS in Taiwan http://wofoss.blogspot.com/ Apache OpenOffice http://www.openoffice.org/ EducOO/OOo4Kids Taiwan http://www.educoo.tw/ Greenfoot Taiwan http://greenfoot.westart.tw/ -- This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
Re: discussion on new l10n workflow
Hi Jan, more information about ApacheCon can be found here: http://www.apachecon.eu/ Am 24.10.2012 22:03, schrieb jan iversen: Where can I read more about ApacheCon EU or NA ? I cannot quite follow you here (mainly due to terms), is this about getting sponsor money to AOO ? It should be easy to get somebody from EU and others, I could call on the NLC to help QA and general testing. Kind regards, Joost
Re: discussion on new l10n workflow
On 12-10-24, at 16:03 , jan iversen jancasacon...@gmail.com wrote: Where can I read more about ApacheCon EU or NA ? I cannot quite follow you here (mainly due to terms), is this about getting sponsor money to AOO ? http://www.apachecon.com/ No. That may be too late. It's about asking via the lists for your work to have a hearing among those present and a discussion if they are willing and able to have that. The reason for this: simply to get the work you are doing the investigation it merits. It should be easy to get somebody from EU and others, I could call on the NLC to help QA and general testing. Yes; something like that to promote the workflow reappraisal. We at OOo went through this numerous times but not enough, probably, and it was always layered with corporate expectations, and these rubbed against community interests. (A good case being the RU localization of the early 2000s.) Best Louis jan. On 24 October 2012 21:53, Louis Suárez-Potts lui...@gmail.com wrote: On 12-10-24, at 14:35 , jan iversen jancasacon...@gmail.com wrote: May I politely ask if there are other comments or more importantly objections ? Press on. And expect to be patient: this is a volunteer effort. I 'd also, if I were you, see about highlighting this effort at ApacheCon EU or NA (next year). If you cannot personally make the EU event, you can ask a surrogate, perhaps. But the issue is indeed very important, at least as I see it. For it leads to expanding the AOO contributor base, being that localization efforts are among the most interesting to a range of audiences, who rightly see a localized AOO as much easier to work with than one in English. If not I will continue with the process and keep you posted, please remember comments are also welcome as the new workflow takes shape. Please! also, don't hesitate to use other channels, such as Facebook, our wikis, etc. best louis Jan I. On 24 October 2012 20:18, jan iversen jancasacon...@gmail.com wrote: Thanks for your kind words. see below please: On 24 October 2012 19:49, Louis Suárez-Potts lui...@gmail.com wrote: Hi Jan, On 12-10-16, at 12:22 , jan iversen jancasacon...@gmail.com wrote: Finally I have finished describing the current process, and also combining all the notes on open issues I could find. Thanks. A lot of work. Last it was dealt with was probably (prior to Apache's advent) back in…. I hate to say, last century. Please have a look at: http://wiki.openoffice.org/wiki/File:L10proc.pdf Indeed. and http://wiki.openoffice.org/wiki/Localization_AOO I hope we can have a discussion on the open issues, and then I will make a design document for a changed workflow. I look forward to hear your opinion, either through wiki or mail. These comments will be worked into the document. have a nice day. jan I I'll go over it. Usually, as others no doubt will mention, my impression is that a big issue has always been qualifying the outcome, incorporating input, and normalizing it, so that what happens in, say, January, can be expected to continue on into the future. It was a big job, first describing the current process and run it several times to make sure I understood it, and then think about how to do more robust and future oriented. I have had a helping hand from my professional background where I used to manage project with these kind of problemsets. I would appreciate any input, this is a floating process, development/discussion. A sidle point has perhaps also do with working with the LibreOffice team—and others working using similar strings, e.g., those nice people at that Mozilla project, among others. Under the Sun regime, licensing issues foreclosed that option. I'd hate to think we are still hobbled by political considerations and that these undercut the terrific enterprise of people like you. I am very open minded to that respect, but honestly I have no idea what the apache policy is. Thanks Louis
Re: Volunteers, Contributors, Committers, PMC members -- is there any way to consolidate these lists?
On 10/24/2012 11:56 AM, Rob Weir wrote: We have the following today: 1) http://incubator.apache.org/openofficeorg/people.html -- This lists a variety of people involved in the project, independent of status. yes, and I don't think it's up to date...it may need to go soonish. 2) I'd like to have a place for new volunteers to put their names, preferably on the wiki or some place where a non-committer has easy access. Here's an idea... we have/had the old credits page on the user portal web server: http://www.openoffice.org/welcome/credits.html I suggest we port this in its entirety to the wiki -- maybe even put in a new People navigation item -- and continue to let people add themselves to the list. 3) We have a list of Committers here, automatically generated: http://people.apache.org/committers-by-project.html#ooo 4) We don't have anything that indicates which Committers are also PMC members. We probably should list them on the project site...maybe a PMC page instead of the outdated people page, if this is important. Maybe a topic for further discussion. 5) We have this credits page, which is linked to from our Help/About dialog box. But it does not appear to be updated for AOO 3.4.0 or 3.4.1: http://www.openoffice.org/welcome/credits.html I see no reason why this page: http://www.openoffice.org/welcome/credits.html can't be moved in its entirety to the wiki -- maybe even put in a new People navigation item in the main wiki navigation -- and continue to let people add themselves to the list. 6) Wiki User pages these are already there by the way, but some are quite outdated 7) Any others? As we all know, with multiple lists like this things will get out of synch. In fact they already have. One simplification idea might be: 1) Convert the people.html page into a wiki page 2) Have that page indicate who is a Committer or PMC member. That can be manual for now. 3) Point our Help/About box to the wiki page, and add sentence at the end of the wiki that says, OpenOffice has a long history and we also thank those who contributed to it before our move to Apache and then link to credits.html Any objections to this general idea? Any improvements? And if we did want a place to have a big table of volunteers, where on the wiki should we put it (CWiki or MWiki)? -Rob -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: discussion on new l10n workflow
Got it, I did not think of the upcoming meeting. I think it is too early for that (maybe somebody has opinions??) I would like to present it, when it is ready to be launched...I dont like to present hot air :-) But as I understood it there is another conference early next year, that would be just perfect. jan. On 24 October 2012 22:08, Joost Andrae joost.and...@gmx.de wrote: Hi Jan, more information about ApacheCon can be found here: http://www.apachecon.eu/ Am 24.10.2012 22:03, schrieb jan iversen: Where can I read more about ApacheCon EU or NA ? I cannot quite follow you here (mainly due to terms), is this about getting sponsor money to AOO ? It should be easy to get somebody from EU and others, I could call on the NLC to help QA and general testing. Kind regards, Joost
RE: [PROPOSAL] difficulty field for Bugzilla
@Regina, Yes, Wizard is a reference to the level of mastery that a solver must possess, and is one of those which one of these words does not belong solutions. There is a well-known *logarithmic* difficulty scale that has been used over 40 years for problem difficulty. It might be worth adapting: (after unknown), 00 easy - immediately solvable by someone willing to do it 10 simple - takes minutes 20 medium, average - quarter hour 30 moderate, an evening 40 difficult, challenging, non-trivial (term project, GSoC...) 50 unsolved, deep, requires a breakthrough, research (PhD dissertation) 60 intractable (that I just made up - probably not something that is technically feasible regardless of skill, Nobel Prize, P = NP, etc.) I suspect this scale has too much at the low end and perhaps not enough steps at the high end. Perhaps there are two factors - skills and work factor - how long for someone of the necessary skills? Or else work factor is suggestive of the level of skill? easy - minutes (fixing a typo on a web page) simple - hour(s) moderate - days difficult, challenging - weeks hard, demanding - months stubborn - years (aka, intractable) All of these assume fluency with basic tools and facility with the subject matter of the issue. For example, fixing change-tracking is at least hard. - Dennis -Original Message- From: Regina Henschel [mailto:rb.hensc...@t-online.de] Sent: Wednesday, October 24, 2012 13:04 To: ooo-dev@incubator.apache.org Subject: Re: [PROPOSAL] difficulty field for Bugzilla Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL sounds devaluating to me. Perhaps BEGINNER or STARTER is more neutral? Being able to start is not only a question, whether the task is easy or not from an objective point of view. Beyond that a mentor is needed. Perhaps a category MENTORED instead of TRIVIAL is useful. A senior developer would set it (and put himself in CC) if he is willing to guide a newcomer. (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. In general I thing it is a good idea. Using Bugzilla has the advantage, that it is not necessary to hold a Wiki page in sync with Bugzilla. Kind regards Regina
Re: [PROPOSAL] difficulty field for Bugzilla
On 10/24/2012 01:04 PM, Regina Henschel wrote: Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD We have a severity field right now as well. Will these two fields be confusing to some? How can we differentiate them, and, more's to the point, to the reporter? Or do you see this as something that the responder to the bug changes? WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL sounds devaluating to me. Perhaps BEGINNER or STARTER is more neutral? Being able to start is not only a question, whether the task is easy or not from an objective point of view. Beyond that a mentor is needed. Perhaps a category MENTORED instead of TRIVIAL is useful. A senior developer would set it (and put himself in CC) if he is willing to guide a newcomer. (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. In general I thing it is a good idea. Using Bugzilla has the advantage, that it is not necessary to hold a Wiki page in sync with Bugzilla. Kind regards Regina -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
RE: [PROPOSAL] difficulty field for Bugzilla
+1 Great question I think severity has to do with the significance to the reporter. It is generally not for the resolver to deal with. Difficulty is an assessment about the effort/skill required to resolve the (confirmed) issue. The cause may be deep and the resolution deeper. -Original Message- From: Kay Schenk [mailto:kay.sch...@gmail.com] Sent: Wednesday, October 24, 2012 13:28 To: ooo-dev@incubator.apache.org Subject: Re: [PROPOSAL] difficulty field for Bugzilla On 10/24/2012 01:04 PM, Regina Henschel wrote: Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD We have a severity field right now as well. Will these two fields be confusing to some? How can we differentiate them, and, more's to the point, to the reporter? Or do you see this as something that the responder to the bug changes? WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL sounds devaluating to me. Perhaps BEGINNER or STARTER is more neutral? Being able to start is not only a question, whether the task is easy or not from an objective point of view. Beyond that a mentor is needed. Perhaps a category MENTORED instead of TRIVIAL is useful. A senior developer would set it (and put himself in CC) if he is willing to guide a newcomer. (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. In general I thing it is a good idea. Using Bugzilla has the advantage, that it is not necessary to hold a Wiki page in sync with Bugzilla. Kind regards Regina -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: [PROPOSAL] difficulty field for Bugzilla
On 12-10-24, at 16:28 , Dennis E. Hamilton dennis.hamil...@acm.org wrote: @Regina, Yes, Wizard is a reference to the level of mastery that a solver must possess, and is one of those which one of these words does not belong solutions. There is a well-known *logarithmic* difficulty scale that has been used over 40 years for problem difficulty. It might be worth adapting: (after unknown), 00 easy - immediately solvable by someone willing to do it 10 simple - takes minutes 20 medium, average - quarter hour 30 moderate, an evening 40 difficult, challenging, non-trivial (term project, GSoC...) 50 unsolved, deep, requires a breakthrough, research (PhD dissertation) 60 intractable (that I just made up - probably not something that is technically feasible regardless of skill, Nobel Prize, P = NP, etc.) I suspect this scale has too much at the low end and perhaps not enough steps at the high end. Perhaps there are two factors - skills and work factor - how long for someone of the necessary skills? Or else work factor is suggestive of the level of skill? easy - minutes (fixing a typo on a web page) simple - hour(s) moderate - days difficult, challenging - weeks hard, demanding - months stubborn - years (aka, intractable) All of these assume fluency with basic tools and facility with the subject matter of the issue. For example, fixing change-tracking is at least hard. - Dennis One aspect that has been used and not used enough is to consider this in light of how a student or neophyte might approach the task and whether it demands the added help a mentor can offer. Louis -Original Message- From: Regina Henschel [mailto:rb.hensc...@t-online.de] Sent: Wednesday, October 24, 2012 13:04 To: ooo-dev@incubator.apache.org Subject: Re: [PROPOSAL] difficulty field for Bugzilla Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL sounds devaluating to me. Perhaps BEGINNER or STARTER is more neutral? Being able to start is not only a question, whether the task is easy or not from an objective point of view. Beyond that a mentor is needed. Perhaps a category MENTORED instead of TRIVIAL is useful. A senior developer would set it (and put himself in CC) if he is willing to guide a newcomer. (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. In general I thing it is a good idea. Using Bugzilla has the advantage, that it is not necessary to hold a Wiki page in sync with Bugzilla. Kind regards Regina
Re: Need new logo for openoffice.apache.org
2012/10/24 Andrea Pescetti pesce...@apache.org Alexandro Colorado wrote: On 10/23/12, Andrea Pescetti wrote: Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly Who made Michael Acevedo the offical artist of AOO? If we are going to have a 'new' logo that automatically disqualify using MA logo Nobody made Michael Acevedo the official artist, but a mailing list vote approved his logo as the Apache OpenOffice logo for the 3.4.x series (at that time, we believed that the version after 3.4.x would be 4.x). So, again: for 3.4 and all official communication in 3.4 the reference logo is that one, and not something that is 95% similar to it or that tweaks colors/fonts. We must be consistent. This is the reason why we cannot use your SVG version now. But it is understood, as Graham wrote, that this is a temporary solution. For future releases we are free to adopt any new logo, having a similarity to the current one anywhere between 0% and 100%, and since we are not under pressure at the moment we can explore possibilities for a full rebranding: logo, site, palette, icons... If we go for a full rebranding, it is good to make it coincident with the 4.0 release since it would be easier to communicate and less suspicious to users. +1. 4.0 is the time for a full rebranding, not before. Of course we need to start with this sooner than later, but IMO it is not urgent. Regards Ricardo Regards, Andrea.
Re: Volunteers, Contributors, Committers, PMC members -- is there any way to consolidate these lists?
On Wed, Oct 24, 2012 at 4:14 PM, Kay Schenk kay.sch...@gmail.com wrote: On 10/24/2012 11:56 AM, Rob Weir wrote: We have the following today: 1) http://incubator.apache.org/openofficeorg/people.html -- This lists a variety of people involved in the project, independent of status. yes, and I don't think it's up to date...it may need to go soonish. 2) I'd like to have a place for new volunteers to put their names, preferably on the wiki or some place where a non-committer has easy access. Here's an idea... we have/had the old credits page on the user portal web server: http://www.openoffice.org/welcome/credits.html I suggest we port this in its entirety to the wiki -- maybe even put in a new People navigation item -- and continue to let people add themselves to the list. But most of these people are no longer involved with the project, right? So the table would have names only for most of the entries, with no other details, interests, country, etc., like our current people.html page has. 3) We have a list of Committers here, automatically generated: http://people.apache.org/committers-by-project.html#ooo 4) We don't have anything that indicates which Committers are also PMC members. We probably should list them on the project site...maybe a PMC page instead of the outdated people page, if this is important. Maybe a topic for further discussion. 5) We have this credits page, which is linked to from our Help/About dialog box. But it does not appear to be updated for AOO 3.4.0 or 3.4.1: http://www.openoffice.org/welcome/credits.html I see no reason why this page: http://www.openoffice.org/welcome/credits.html can't be moved in its entirety to the wiki -- maybe even put in a new People navigation item in the main wiki navigation -- and continue to let people add themselves to the list. With this approach, would it be possible to have two tables, one for active and another for inactive or emeritus? That might reduce the clutter. Most of the time you are looking for info about a current project volunteer. So it would be nice to make that task easy. -Rob 6) Wiki User pages these are already there by the way, but some are quite outdated 7) Any others? As we all know, with multiple lists like this things will get out of synch. In fact they already have. One simplification idea might be: 1) Convert the people.html page into a wiki page 2) Have that page indicate who is a Committer or PMC member. That can be manual for now. 3) Point our Help/About box to the wiki page, and add sentence at the end of the wiki that says, OpenOffice has a long history and we also thank those who contributed to it before our move to Apache and then link to credits.html Any objections to this general idea? Any improvements? And if we did want a place to have a big table of volunteers, where on the wiki should we put it (CWiki or MWiki)? -Rob -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: [PROPOSAL] difficulty field for Bugzilla
Apache Camel uses an Estimated Complexity custom field in the Apache Issues Tracker. Current values in it are Any, Unknown, Novice, Moderate, Advanced, Guru and Needs James Gosling. Had to look him up: http://en.wikipedia.org/wiki/James_Gosling Don On Wed, Oct 24, 2012 at 4:45 PM, Louis Suárez-Potts lui...@gmail.com wrote: On 12-10-24, at 16:28 , Dennis E. Hamilton dennis.hamil...@acm.org wrote: @Regina, Yes, Wizard is a reference to the level of mastery that a solver must possess, and is one of those which one of these words does not belong solutions. There is a well-known *logarithmic* difficulty scale that has been used over 40 years for problem difficulty. It might be worth adapting: (after unknown), 00 easy - immediately solvable by someone willing to do it 10 simple - takes minutes 20 medium, average - quarter hour 30 moderate, an evening 40 difficult, challenging, non-trivial (term project, GSoC...) 50 unsolved, deep, requires a breakthrough, research (PhD dissertation) 60 intractable (that I just made up - probably not something that is technically feasible regardless of skill, Nobel Prize, P = NP, etc.) I suspect this scale has too much at the low end and perhaps not enough steps at the high end. Perhaps there are two factors - skills and work factor - how long for someone of the necessary skills? Or else work factor is suggestive of the level of skill? easy - minutes (fixing a typo on a web page) simple - hour(s) moderate - days difficult, challenging - weeks hard, demanding - months stubborn - years (aka, intractable) All of these assume fluency with basic tools and facility with the subject matter of the issue. For example, fixing change-tracking is at least hard. - Dennis One aspect that has been used and not used enough is to consider this in light of how a student or neophyte might approach the task and whether it demands the added help a mentor can offer. Louis -Original Message- From: Regina Henschel [mailto:rb.hensc...@t-online.de] Sent: Wednesday, October 24, 2012 13:04 To: ooo-dev@incubator.apache.org Subject: Re: [PROPOSAL] difficulty field for Bugzilla Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL sounds devaluating to me. Perhaps BEGINNER or STARTER is more neutral? Being able to start is not only a question, whether the task is easy or not from an objective point of view. Beyond that a mentor is needed. Perhaps a category MENTORED instead of TRIVIAL is useful. A senior developer would set it (and put himself in CC) if he is willing to guide a newcomer. (I'm certainly open to variations on the names) I'd then rely on other developers to help seed the database with some TRIVIAL and EASY bugs, so new volunteers will have something to work with as they familiarize themselves with the project. I'll wait 72 hours, etc. In general I thing it is a good idea. Using Bugzilla has the advantage, that it is not necessary to hold a Wiki page in sync with Bugzilla. Kind regards Regina
Re: Volunteers, Contributors, Committers, PMC members -- is there any way to consolidate these lists?
On Wed, Oct 24, 2012 at 6:23 PM, Dave Fisher dave2w...@comcast.net wrote: Thanks Rob. Sent from my iPhone On Oct 24, 2012, at 11:56 AM, Rob Weir robw...@apache.org wrote: We have the following today: 1) http://incubator.apache.org/openofficeorg/people.html -- This lists a variety of people involved in the project, independent of status. Let's convert this page into an official list of PMC members and Committers. Maintained by the PMC. I volunteer to update this by next week. 2) I'd like to have a place for new volunteers to put their names, preferably on the wiki or some place where a non-committer has easy access. +1 this can be dynamic and self organizing. 3) We have a list of Committers here, automatically generated: http://people.apache.org/committers-by-project.html#ooo This is from the ASF and comes from karma as granted by the PMC chair. 4) We don't have anything that indicates which Committers are also PMC members. The new people page will show the differences. 5) We have this credits page, which is linked to from our Help/About dialog box. But it does not appear to be updated for AOO 3.4.0 or 3.4.1: http://www.openoffice.org/welcome/credits.html 6) Wiki User pages 7) Any others? As we all know, with multiple lists like this things will get out of synch. In fact they already have. One simplification idea might be: 1) Convert the people.html page into a wiki page I'd like to keep it as a CMS page. 2) Have that page indicate who is a Committer or PMC member. That can be manual for now. 3) Point our Help/About box to the wiki page, and add sentence at the end of the wiki that says, OpenOffice has a long history and we also thank those who contributed to it before our move to Apache and then link to credits.html Any objections to this general idea? None other than the committer / PMC page should remain in the CMS. That works for me. Maybe, in order to reduce duplication/overlap and the sync issues that come from that, the wiki page would only have volunteers who are not also committers? And since we're all people maybe rename the people.mdtext and nav link to say Committers? -Rob Regards, Dave Any improvements? And if we did want a place to have a big table of volunteers, where on the wiki should we put it (CWiki or MWiki)? -Rob
Re: [PROPOSAL] difficulty field for Bugzilla
On Thursday, October 25, 2012, Donald Whytock wrote: Apache Camel uses an Estimated Complexity custom field in the Apache Issues Tracker. Current values in it are Any, Unknown, Novice, Moderate, Advanced, Guru and Needs James Gosling. Had to look him up: http://en.wikipedia.org/wiki/James_Gosling Don On Wed, Oct 24, 2012 at 4:45 PM, Louis Suárez-Potts lui...@gmail.com wrote: On 12-10-24, at 16:28 , Dennis E. Hamilton dennis.hamil...@acm.org wrote: @Regina, Yes, Wizard is a reference to the level of mastery that a solver must possess, and is one of those which one of these words does not belong solutions. There is a well-known *logarithmic* difficulty scale that has been used over 40 years for problem difficulty. It might be worth adapting: (after unknown), 00 easy - immediately solvable by someone willing to do it 10 simple - takes minutes 20 medium, average - quarter hour 30 moderate, an evening 40 difficult, challenging, non-trivial (term project, GSoC...) 50 unsolved, deep, requires a breakthrough, research (PhD dissertation) 60 intractable (that I just made up - probably not something that is technically feasible regardless of skill, Nobel Prize, P = NP, etc.) I suspect this scale has too much at the low end and perhaps not enough steps at the high end. Perhaps there are two factors - skills and work factor - how long for someone of the necessary skills? Or else work factor is suggestive of the level of skill? easy - minutes (fixing a typo on a web page) simple - hour(s) moderate - days difficult, challenging - weeks hard, demanding - months stubborn - years (aka, intractable) All of these assume fluency with basic tools and facility with the subject matter of the issue. For example, fixing change-tracking is at least hard. - Dennis One aspect that has been used and not used enough is to consider this in light of how a student or neophyte might approach the task and whether it demands the added help a mentor can offer. Louis -Original Message- From: Regina Henschel [mailto: rb.hensc...@t-online.de rb.henschel@t-online. rb.hensc...@t-online.dederb.hensc...@t-online.de ] Sent: Wednesday, October 24, 2012 13:04 To: ooo-dev@incubator.apache.org Subject: Re: [PROPOSAL] difficulty field for Bugzilla Hi Rob, Rob Weir schrieb: As you have probably noticed, I'm engaged in a variety of initiatives to grow the community, bring in more volunteers, etc. One additional piece that I think would be useful is to add a new field to Bugzilla to indicate the difficulty level of the bug. Of course, this will often not be known. But in some cases, we do know, and where we do know we can indicate this. What this allows us to do is then have search filters that return only open easy bugs. These are ideal for new developer volunteers on the project who are looking for items that match their lesser familiarity with the code. It also allows a developer to step up to more challenging bugs over time. A similar approach, which they called easy hacks, was successfully used by LibreOffice. If there are no objections, I'll add a new field to Bugzilla called cf_difficulty_level, and which a drop down UI with the following choices: UNKNOWN (default) TRIVIAL EASY MODERATE HARD WIZARD WIZARD is used in AOO UI in the meaning of 'assistant' or step by step workflow. Therefore it might be not understood here. I need to look up other meanings in a dictionary. I would drop it. HARD as highest step is sufficient. TRIVIAL KG01 - Perhaps we need to separate complexity from size? While this adds yet another field, it does help triage and scope work items.
Re: Need new logo for openoffice.apache.org
On Thursday, October 25, 2012, RGB ES wrote: 2012/10/24 Andrea Pescetti pesce...@apache.org javascript:; Alexandro Colorado wrote: On 10/23/12, Andrea Pescetti wrote: Exactly. And this means we cannot use Alexandro's SVG since it is not a 100% reproduction of the bitmap by Michael Acevedo (the orb is perfectly Who made Michael Acevedo the offical artist of AOO? If we are going to have a 'new' logo that automatically disqualify using MA logo Nobody made Michael Acevedo the official artist, but a mailing list vote approved his logo as the Apache OpenOffice logo for the 3.4.x series (at that time, we believed that the version after 3.4.x would be 4.x). So, again: for 3.4 and all official communication in 3.4 the reference logo is that one, and not something that is 95% similar to it or that tweaks colors/fonts. We must be consistent. This is the reason why we cannot use your SVG version now. But it is understood, as Graham wrote, that this is a temporary solution. For future releases we are free to adopt any new logo, having a similarity to the current one anywhere between 0% and 100%, and since we are not under pressure at the moment we can explore possibilities for a full rebranding: logo, site, palette, icons... If we go for a full rebranding, it is good to make it coincident with the 4.0 release since it would be easier to communicate and less suspicious to users. +1. 4.0 is the time for a full rebranding, not before. Of course we need to start with this sooner than later, but IMO it is not urgent. Regards Ricardo KG01 - Agreed, this is my view as well. For now, we need to update some graphics and remove the incubation reference. while these graphics include the logo, we don't need to update the logo in those graphics. Moving forward, we are free to explore some design alternatives for rebranding which could be consumed in an AOO 4.0 release. In the short term we should update the graphics, and in the mid term, we should start exploring design options for a refresh. As any branding should be associated with the look and feel of the tools, we should ensure the branding design explorations align with any UI design explorations. Regards, Kevin Regards, Andrea.
Re: [QA BUG] - some regression defects were found by GUI perfromance test
Thanks Herbert. I will check[1][2] in current build:) On Wed, Oct 24, 2012 at 11:03 PM, Herbert Duerr h...@apache.org wrote: Hi, On 24.10.2012 07:34, Linyi Li wrote: I did GUI performance test of AOO trunk build. I found some defects[1][2][3], and two of them are regression ones[1][2]. Great finds and great bug reports, thank you! And kudos to the wonderful automated testing framework that allows to run such extensive tests with that thoroughness and frequency. I think defects[1][2] are severe which will block users‘ normal use of AOO, so is there anyone who can help to fix these defects? I looked into them and updated their status: [1] Bug 121199 - [Automation][Regression]**Crashed when loading 2 docx files. The patch that caused the crashes is known and reverting it solves the problem. But probably the patch can be updated to fix both the new and the original issues. The developers knowing the patch best were CC'ed. [2] Bug 121200 - [Regression][Automation][**Performance]Severe downgrade to save xls sample files. This seems to be fixed in the current trunk revision. [3] Bug 121256 - Crash when saving ppt on Linux. This cannot be reproduced here. If anyone sees the problem please attach a stack trace in the issue. If possible for a build with sufficient debug info. Herbert -- Best wishes. Linyi Li
[QA CALLFORREVIEW] Bug 121272 -[testuno]insert frame,frame backcolor,frame backgraphic,frame border,spacing to content,frame shadow automation script
Hi all, Is there anyone can help me review the test script?It is include these test point: insert frame,frame shadow,frame border,frame border spacing to content,frame backcolor,frame backgraphic https://issues.apache.org/ooo/show_bug.cgi?id=121272 Thanks~ Du Jing
Re: OpenOffice graduates from the Apache Incubator
On 18/10/2012 Larry Gusaas wrote: On 2012-10-18 9:38 AM Dave Fisher wrote: The old lists will forward to the new when these are created. Will the feeds on gmane also be renamed? This will probably need some coordination with them after the mailing list have been relocated. I've added this task to http://s.apache.org/openoffice-graduation-changes Regards, Andrea.
CWS notes11
Does anybody know the status of CWS notes11? It is mentioned here (for a minor wording issue regarding Notes/Comments) https://issues.apache.org/ooo/show_bug.cgi?id=109265 and apparently it is not integrated yet, and it was not yet marked as Ready for QA; so it appears to be unfinished work. Regards, Andrea.
Re: [RELEASE]: new snapshot base don revision r1400866
I'm downloading windows and mac install package and will do BVT and general testing against it. 2012/10/24 Jürgen Schmidt jogischm...@gmail.com Hi, a new snapshot build is available for MacOS and Windows. Linux will be available later. See https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds I have called it 3.5 snapshot but we haven't really confirmed if our next release will be a 3.5 or 4.0. That can be discussed and decided when we have finalized our plans. The snapshot is build on top of revision r1400866. I have provided full install set for all supported languages and a further language pack for en-US + the SDK and src release. Supported languages are: ar cs da de en-GB en-US es fi fr gd gl hu it ja km ko nb nl pt-BR ru sk sl zh-CN zh-TW @Ariel: I have changed columns in the wiki and moved MacOS before Linux, it makes it easier for me ;-) Juergen -- Thanks Best Regards, Yan Ji
Re: [QA BUG] - some regression defects were found by GUI perfromance test
Hi Herbert, I checked defect[2] on r1401602, it still has this problem. Could you tell me which build you tested? About defect[1], I saw there is a response: --- Comment #5 from wujinl...@gmail.com --- This is a known bug, and I have already had a fix for it. Please see bug 121134 for details. CC to wujinlong, is this fix already commited to trunk build? Defect[3] is found on ubuntu12.04, 32bit. It is OK on ubuntu12.04 64bit. On Thu, Oct 25, 2012 at 9:41 AM, Linyi Li lilinyi921...@gmail.com wrote: Thanks Herbert. I will check[1][2] in current build:) On Wed, Oct 24, 2012 at 11:03 PM, Herbert Duerr h...@apache.org wrote: Hi, On 24.10.2012 07:34, Linyi Li wrote: I did GUI performance test of AOO trunk build. I found some defects[1][2][3], and two of them are regression ones[1][2]. Great finds and great bug reports, thank you! And kudos to the wonderful automated testing framework that allows to run such extensive tests with that thoroughness and frequency. I think defects[1][2] are severe which will block users‘ normal use of AOO, so is there anyone who can help to fix these defects? I looked into them and updated their status: [1] Bug 121199 - [Automation][Regression]**Crashed when loading 2 docx files. The patch that caused the crashes is known and reverting it solves the problem. But probably the patch can be updated to fix both the new and the original issues. The developers knowing the patch best were CC'ed. [2] Bug 121200 - [Regression][Automation][**Performance]Severe downgrade to save xls sample files. This seems to be fixed in the current trunk revision. [3] Bug 121256 - Crash when saving ppt on Linux. This cannot be reproduced here. If anyone sees the problem please attach a stack trace in the issue. If possible for a build with sufficient debug info. Herbert -- Best wishes. Linyi Li -- Best wishes. Linyi Li
