Re: Feature suggestion for AOO 4.x
Marco A.G.Pinto wrote: I mentioned this months ago. There is a need for a button to change the font (uppercase, Capitalize, etc) like Microsoft Office 2010 has. ... Please see the screenshot: http://i.imgur.com/csJy8A0.png We don't have a single button, but we are rather close in functionality. You find the same options under the Format menu, and you can add the individual options to the toolbar. We even provide icons for the all to lowercase and all to uppercase functions. So everything is already available, but having one single button could be a usability enhancement. You may want to file a request tagged ENHANCEMENT in https://issues.apache.org/ooo/ if we don't have a similar one yet. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Use AOO under IBM AIX?
On 30.07.2013 01:54, Rob Weir wrote: As others are saying, this is a big task for one person, but there is sufficient interest, of the kind that leads to more developer volunteers, then anything is possible. Not too long ago some people were apparently working on it on AIX port: http://comments.gmane.org/gmane.comp.openoffice.devel.porting/15002 In that thread you'll find some good suggestions on what needs to be done for that port and names of developers that attempted it. No idea whether they are still interested or how far they got though. Herbert - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Website]
Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. Regards Mattias
Re: Feature suggestion for AOO 4.x
Hi Marco, Marco A.G.Pinto schrieb: Hello!!! I mentioned this months ago. There is a need for a button to change the font (uppercase, Capitalize, etc) like Microsoft Office 2010 has. I tried to add it to AOO 4.0, by looking all over the options, without success and I guess it should appear as default since it is very useful. Find a solution for the setting via Font effects by Ariel attached to issue https://issues.apache.org/ooo/show_bug.cgi?id=27894. The other settings have got commands in the customize dialog and you can easily get a toolbar icon or a shortcut key. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
A suggestion for feature of spread-sheets
30 July 2013 Dear people at Open Office, I will try and keep this simple, I have a suggestion for a feature for your spreadsheet package. (I have no idea which email to send my suggestion to, so I am sending it here, Please pass it on to the correct department). This is for a planning function, All it requires is the ability to rotate a spreadsheet about 30-60 degrees counter-clockwise. Perhaps you are familiar with Gantt charts as a planning aid. Below is one I copied from the internet, (© Ralph Lengler Martin J. Eppler). You will notice that there is a lot of wasted space in the top-right and bottom-left corners. rotating it would just make it easier to print out and display. to show what I mean, I did the following... (using Coreldraw, sorry, I am not prepared to spend days learning the open-office drawing package, just to draw one diagram). The chart above describes a set project with a decisive start and finish. The system would have more use where planning is required for a continuous process, (the number of 'items' stretches indefinitely,) Perhaps it may be easier to achieve the same, by extending the print function, by selecting the relevant cells, rotating them to a suitable angle then printing (or displaying). As i said, just a suggestion. regards Dave Patel.
Source code links are not according to platform.
They are misplaced. .zip file must be for windows. Thanks Devendra
Re: Source code links are not according to platform.
On Tue, Jul 30, 2013 at 8:38 AM, Devendra Shinde india.shinde.deven...@gmail.com wrote: They are misplaced. .zip file must be for windows. The OpenOffice source distributions are in portable C/C++ code. The packages are the same except for the compression format. So pick whatever one you want. The Windows build requires Cygwin anyways, so you can handle the tar.gz on Windows there, as well as zip. Regards, -Rob Thanks Devendra - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.0 and loss of backward compatibility for extensions with toolbar
2013/7/29 Roberto Galoppini roberto.galopp...@gmail.com 2013/7/27 Rob Weir robw...@apache.org On Sat, Jul 27, 2013 at 4:59 PM, Roberto Galoppini roberto.galopp...@gmail.com wrote: 2013/7/27 Rob Weir robw...@apache.org On Fri, Jul 26, 2013 at 5:59 PM, Hagar Delest hagar.del...@laposte.net wrote: Le 26/07/2013 15:40, Roberto Galoppini a écrit : A) a link to a version compatible with AOO 4.0 has been added for http://extensions.openoffice.org/en/project/pdfimport and http://extensions.openoffice.org/en/project/mysql_connector B) 4.0 has been added to the list of possible compatibilities. For example http://extensions.openoffice.org/en/node/287/releases doesn't enlist 4.0 among AOO compatible versions, while new extensions have that set, see for example http://extensions.openoffice.org/en/node/5644/releases. Note that it's up to the author to indicate his/her extension compatibility list, and he/she can update it without the need to upload the file again. But it means that the author has to be aware that there is a change and he has to update the relevant field. There is no script that could add the lack of compatibility if the extension has not been updated yet? The lack of compatibility is somehow implicit if you read that a given extension is compatible with OpenOffice 3.3 or AOO 3.4 and it doesn't mention AOO 4.0. See below about how to make sure such info is up-to-date. For the record, in the case of the Lorem ipsum extension, the author doesn't seem to be willing to update it... If an extension is essentially abandoned then it is only a matter of time before it breaks. Either that or we put ourselves into a position where we can never evolve and improve our API. We should focus on the needs of active extension developers, not the inactive ones. This is what we did to keep extension authors in the loop: 1) We created a special mailing list, a...@openoffice.apache.org for discussions about extensions. 2) We worked with SourceForge to send an email to all registered extension authors to invite them to the new list. This was done before the *.openoffice.org email forwarder was shut down, so they all should have received the note. We might resend an email to all Extensions' authors re-inviting them to subscribe to the API mailing-list and also inviting them to check if their extensions do work with AOO 4.0 and eventually update their extension page accordingly. Does it sound like a plan? Reminders are good. So what do we want to tell them, does anyone want to craft a draft message for AOOE authors? Subject: About Apache OpenOffice New Release and Updating your Extension's Compatibility Info Dear OpenOffice.org Extensions author, As you may have heard, Apache OpenOffice 4.0 is now out, and we'd like to invite you to test your own extension and figure out if it is or is not compatible with Apache OpenOffice 4.0 and its new APIs. If your extension is compatible with AOO 4.0, please take a moment to update the extension's compatibility information so that end-users will know it works with the latest release. If your extension is not compatible we'd encourage you to release a new version if you have time, or ask people to help you with that at the API mailing-list (http://openoffice.apache .org/mailing-lists.html#api-mailing-list-public). How do you like this? Roberto Roberto -Rob Roberto 3) We announce the 4.0 API changes on the API list and answered any questions that came up. True, not everyone is happy about the changes. But we tried to ensure that every active extension author was aware of the changes coming. Regards, -Rob Hagar - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Another new one-day download record yesterday
On Monday we had 212,290 downloads of Apache OpenOffice, beating the previous record (205,202) which was set on July 24th. I'll report the first week's numbers tomorrow. We hit the one-million mark on Sunday, so the full week's count should be impressive. Regards, -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 4.0 and loss of backward compatibility for extensions with toolbar
On Tue, Jul 30, 2013 at 9:30 AM, Roberto Galoppini roberto.galopp...@gmail.com wrote: 2013/7/29 Roberto Galoppini roberto.galopp...@gmail.com 2013/7/27 Rob Weir robw...@apache.org On Sat, Jul 27, 2013 at 4:59 PM, Roberto Galoppini roberto.galopp...@gmail.com wrote: 2013/7/27 Rob Weir robw...@apache.org On Fri, Jul 26, 2013 at 5:59 PM, Hagar Delest hagar.del...@laposte.net wrote: Le 26/07/2013 15:40, Roberto Galoppini a écrit : A) a link to a version compatible with AOO 4.0 has been added for http://extensions.openoffice.org/en/project/pdfimport and http://extensions.openoffice.org/en/project/mysql_connector B) 4.0 has been added to the list of possible compatibilities. For example http://extensions.openoffice.org/en/node/287/releases doesn't enlist 4.0 among AOO compatible versions, while new extensions have that set, see for example http://extensions.openoffice.org/en/node/5644/releases. Note that it's up to the author to indicate his/her extension compatibility list, and he/she can update it without the need to upload the file again. But it means that the author has to be aware that there is a change and he has to update the relevant field. There is no script that could add the lack of compatibility if the extension has not been updated yet? The lack of compatibility is somehow implicit if you read that a given extension is compatible with OpenOffice 3.3 or AOO 3.4 and it doesn't mention AOO 4.0. See below about how to make sure such info is up-to-date. For the record, in the case of the Lorem ipsum extension, the author doesn't seem to be willing to update it... If an extension is essentially abandoned then it is only a matter of time before it breaks. Either that or we put ourselves into a position where we can never evolve and improve our API. We should focus on the needs of active extension developers, not the inactive ones. This is what we did to keep extension authors in the loop: 1) We created a special mailing list, a...@openoffice.apache.org for discussions about extensions. 2) We worked with SourceForge to send an email to all registered extension authors to invite them to the new list. This was done before the *.openoffice.org email forwarder was shut down, so they all should have received the note. We might resend an email to all Extensions' authors re-inviting them to subscribe to the API mailing-list and also inviting them to check if their extensions do work with AOO 4.0 and eventually update their extension page accordingly. Does it sound like a plan? Reminders are good. So what do we want to tell them, does anyone want to craft a draft message for AOOE authors? Subject: About Apache OpenOffice New Release and Updating your Extension's Compatibility Info Dear OpenOffice.org Extensions author, Maybe just OpenOffice Extensions author? As you may have heard, Apache OpenOffice 4.0 is now out, and we'd like to invite you to test your own extension and figure out if it is or is not compatible with Apache OpenOffice 4.0 and its new APIs. If your extension is compatible with AOO 4.0, please take a moment to update the extension's compatibility information so that end-users will know it works with the latest release. If your extension is not compatible Is it clear how to do this? Is there any doc we should point them to for this? we'd encourage you to release a new version if you have time, or ask people to help you with that at the API mailing-list (http://openoffice.apache .org/mailing-lists.html#api-mailing-list-public). How do you like this? Good. -Rob Roberto Roberto -Rob Roberto 3) We announce the 4.0 API changes on the API list and answered any questions that came up. True, not everyone is happy about the changes. But we tried to ensure that every active extension author was aware of the changes coming. Regards, -Rob Hagar - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Website]
On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Service matt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. -Rob Regards Mattias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Website]
On Jul 30, 2013 4:02 PM, Rob Weir robw...@apache.org wrote: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Service matt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? I think it would work. rgds jan i Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. -Rob Regards Mattias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: MWiki is Missing Key Navigation and Apache Trademark information.
@dave: Now I am back on duty :-) The footer info you need are in https://svn.apache.org/repos/infra/infrastructure/trunk/machines/vms/ooo-wiki2-vm.apache.org/x1/wiki/skins/Aoo.php around line 107 and https://svn.apache.org/repos/infra/infrastructure/trunk/machines/vms/ooo-wiki2-vm.apache.org/x1/wiki/includes/SkinTemplate.php around line 335 and of course the css file, artwork (if that need changes): https://svn.apache.org/repos/infra/infrastructure/trunk/machines/vms/ooo-wiki2-vm.apache.org/x1/wiki/skins/aoo https://svn.apache.org/repos/infra/infrastructure/trunk/machines/vms/ooo-wiki2-vm.apache.org/x1/wiki/skins/aoo/main.css Changing the footer is not exactly an easy task when not acquainted with mwiki, but if have a go at it, then I will happily help you review/test/deploy it. We can also do it the other way round, that you supply me with the exact footer layout (e.g. like a html string) and artwork, then I can integrate it. let me know what you think. rgds jan I. Ps. I think we should also look at forums.o.o and bugzilla.
Re: Coverage of 4.0 Release
On Sun, Jul 28, 2013 at 11:13 AM, Rob Weir robw...@apache.org wrote: On Sun, Jul 28, 2013 at 11:13 AM, Andrea Pescetti pesce...@apache.org wrote: A quick selection of articles in Italian that went beyond the simple copy and paste: http://www.melablog.it/post/108539/apache-rilascia-openoffice-4-0-barra-laterale-e-migliore-interoperabilita-con-ms-office http://www.tuxjournal.net/rilasciato-openoffice-4-0-novita-link-al-download/ http://www.oneopensource.it/26/07/2013/apache-openoffice-4-0-disponibile-per-il-download/ http://news.softonic.it/openoffice-versione-4-0-windows-mac Still, note that virtually all articles (including those in English) massively reuse screenshots from the Release Notes. It was a very good idea to provide those materials. Yes. It worked out well. Note though that we have received a note from a print journalist looking for a high-resolution screenshot. So we might consider the needs of print media in the next release also. So what next? One idea is to have a follow up blog post with download numbers and highlights from the media coverage of the 4.0 release. Of course, we could list all of the articles, which would be impressive. But it would be good to have a shorter list of the best coverage also -Rob one more today... http://www.linux-magazine.com/Online/News/Apache-Releases-OpenOffice-4.0 Regards, Andrea. On 25/07/2013 Rob Weir wrote: http://www.theregister.co.uk/2013/07/25/open_office_40_debuts_with_ibm_code_side_and_centre/ On Wed, Jul 24, 2013 at 12:54 PM, Rob Weirrobw...@apache.org wrote: http://www.techradar.com/news/software/applications/apache-bolts-sidebar-onto-new-openoffice-1168196 On Wed, Jul 24, 2013 at 11:16 AM, Rob Weirrobw...@apache.org wrote: http://arstechnica.com/information-technology/2013/07/openoffice-4-0-overhauls-user-interface-boosts-microsoft-compatibility/ On Wed, Jul 24, 2013 at 9:59 AM, Rob Weirrobw...@apache.org wrote: http://www.muylinux.com/2013/07/24/apache-openoffice-4/ (Interesting choice of a logo, one of the other nice ones from the contest) On Wed, Jul 24, 2013 at 8:49 AM, Rob Weirrobw...@apache.org wrote: Important Japanese website: http://www.forest.impress.co.jp/docs/news/20130724_608941.html On Wed, Jul 24, 2013 at 7:35 AM, Rob Weirrobw...@apache.org wrote: http://www.datamation.com/applications/apache-releases-open-source-openoffice-4.html On Tue, Jul 23, 2013 at 5:02 PM, Ricardo Berlasso rgb.m...@gmail.com wrote: http://www.phoronix.com/scan.php?page=news_itempx=MTQxODQ 2013/7/23 Rob Weirrobw...@apache.org http://www.linuxbsdos.com/2013/07/23/apache-openoffice-4-is-here/ http://www.zdnet.com/openoffice-4-0-arrives-718456/ On Tue, Jul 23, 2013 at 3:06 PM, Rob Weirrobw...@apache.org wrote: http://office.about.com/b/2013/07/23/the-new-openoffice-available-today-new-side-bar-and-more.htm http://amanz.my/2013/07/openoffice-4-0-dilancarkan-untuk-pengguna-windows-mac-dan-linux/ http://tech.slashdot.org/story/13/07/23/1643204/apache-openoffice-40-released-with-major-new-features On Tue, Jul 23, 2013 at 12:23 PM, Rob Weirrobw...@apache.org wrote: This is a nice one: http://betanews.com/2013/07/23/apache-releases-openoffice-4/ -Rob On Tue, Jul 23, 2013 at 12:09 PM, Rob Weirrobw...@apache.org wrote: http://www.chip.de/news/OpenOffice-4.0-Gross-Update-mit-neuen-Funktionen_63245985.html (They have a nice gallery of screen shots as well: http://www.chip.de/bildergalerie/Alle-Neuheiten-von-Apache-OpenOffice-4.0-Galerie_63246075.html ) On Tue, Jul 23, 2013 at 11:32 AM, Rob Weirrobw...@apache.org wrote: http://lwn.net/Articles/560203/ (All of three sentences. I thought they got paid by the word?) http://www.dobreprogramy.pl/Apache-OpenOffice-4.0-z-nowym-interfejsem,Aktualnosc,42866.html On Tue, Jul 23, 2013 at 10:07 AM, Rob Weir robw...@apache.org wrote: So far, so good. http://tweakers.net/meuktracker/31036/apache-openoffice-400.html www.ghacks.net/2013/07/23/apache-openoffice-4-released-find-out-what-is-new On Tue, Jul 23, 2013 at 10:02 AM, Ricardo Berlasso rgb.m...@gmail.com wrote: 2013/7/23 Rob Weirrobw...@apache.org http://www.itmagazine.ch/Artikel/53584/Openoffice_4.0_ist_da.html http://denis-sylvain.be/2013/07/apache-openoffice-4-0-est-sorti/ On Tue, Jul 23, 2013 at 9:19 AM, Rob Weirrobw...@apache.org wrote: http://blog.open-office.es/index.php/inicio/2013/07/23/apache-openoffice-4-0-ya-disponible-para-su-descarga http://www.pro-linux.de/news/1/20046/apache-openoffice-40-erschienen.html http://tic-et-net.org/2013/07/23/apache-openoffice-4-fr-est-enfin-disponible-en-version-dfinitive/ On Tue, Jul 23, 2013 at 7:59 AM, Rob Weirrobw...@apache.org
Re: New committer: Christos Stefanidis (christef)
On Mon, Jul 29, 2013 at 12:41 PM, Andrea Pescetti pesce...@apache.orgwrote: The Project Management Committee (PMC) for Apache OpenOffice has asked Christos Stefanidis to become a committer and we are pleased to announce that he has accepted and taken the ID christef. A warm welcome to Christos! Regards, Andrea, on behalf of the Apache OpenOffice PMC --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Welcome Christos! -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi
Re: [Website]
On Tue, Jul 30, 2013 at 10:02 AM, Rob Weir robw...@apache.org wrote: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Service matt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Looking into the issue a little more. It gets a little more complicated. We're still seeing a fair number of update notifications (around 80,000 in the last week) being sent to older OOo installs, 3.3.0 and even 3.2.1. I don't know what this is happening, but it is. Maybe they are finding an old copy of a CD and installing it and then immediately getting the update notification? It can happen. The update notifications are generally sending them to http://www.openoffice.org/download. When this occurs with a language that was included in 3.4.1 but not in 4.0 then this is a problem. They are looking for Swedish, for example, and it cannot be found. For this particular kind of user, I'm not sure a small link labeled Older AOO Versions will help. It would be very unintuitive for the user to look there, because from their perspective they are looking for a newer version and 3.4.1 is newer than what they have, not older. A couple of ways to plug this hole: 1) Enhance the download logic on the main page to offer the most recent version available for the detected language. Or does it already try to do that? or 2) Change the update notifications so the user is sent to the 3.4.1-era other.html page, so they can more easily find their download. Actually, thinking out loud, this might be the easiest solution. And we can still add the Older AOO Versions, which would be good for a different kind of user, someone specifically looking for a 3.4.1 download. This might even be our own QA volunteers ;-) Regards, -Rob Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. -Rob Regards Mattias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: New committer: Edwin Sharp (elish)
On Mon, Jul 29, 2013 at 11:56 AM, Andrea Pescetti pesce...@apache.orgwrote: The Project Management Committee (PMC) for Apache OpenOffice has asked Edwin Sharp to become a committer and we are pleased to announce that he has accepted and taken the ID elish. A warm welcome to Edwin! Regards, Andrea, on behalf of the Apache OpenOffice PMC --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Welcome Edwin! -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi
Re: [DISCUSSION] Should source changes require [discussion] and/or issue submission?
On Mon, Jul 29, 2013 at 3:00 PM, janI j...@apache.org wrote: On 29 July 2013 23:05, Andrea Pescetti pesce...@apache.org wrote: Kay Schenk wrote: http://www.openoffice.org/**marketing/art/galleries/logos/**aoo-working/ http://www.openoffice.org/marketing/art/galleries/logos/aoo-working/ Last week, two of the original svg files -- files prefixed with: Apache_OpenOffice_Logo_ChrisR_**selected_2013-06 were changed. These changes were not discussed in advance, nor an issue submitted for them. Given the events of the day, it was the PMC's decision to not veto these changes, but to copy these changed originals Thank you Kay for the reminder. I added a WARNING.txt file to the aoo-working directory to help avoiding changes that have not been discussed here first. I like the WARNING.txt file, could we agree to use the same file for other sensible (not sure if that is the right word) areas ? I think of e.g. release notes. So, back the original topic. Given recent events, do we want to have a changed policy to require issue submission and/or list discussion before new commits? I'd say we don't need it in general; it will be helpful for all significant code changes, but surely we don't need it for the website. Let's rely on common sense and peer scrutiny. +1, lets not make it too complicated to work, that said with a smile !! For significant code changes, a discussion is a must, but I thought it was already policy ? rgds jan I. Regards, Andrea. --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Here is some information on decision making/discussions: http://openoffice.apache.org/orientation/decision-making.html http://community.apache.org/committers/ http://www.apache.org/foundation/how-it-works.html#roles I could not find any specific rules on when decision making should be used. In OpenOffice, it is used on a regular basis for many different changes, but WHEN to use it doesn't seem to be set in stone. And it looks like, some projects have defined their own criteria. -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi
Do language packs have update notifications?
In OOo 3.3.0 we support Tamil with a language pack, but not a full install. In AOO 4.0 we provide a full install for Tamil, as well as a language pack. Are we able to notify 3.3.0 users of the Tamil language pack about the update? Is that something the update notification system can handle? Or does it only handle updates to the base install? -Rob - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] added security to avoid changes in artifacts.
On Thu, Jul 25, 2013 at 1:17 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 07/25/2013 08:47 PM, schrieb Rob Weir: On Thu, Jul 25, 2013 at 2:21 PM, Kay Schenkkay.sch...@gmail.com wrote: On Wed, Jul 24, 2013 at 12:27 PM, Dave Fisherdave2w...@comcast.net wrote: On Jul 24, 2013, at 11:40 AM, Marcus (OOo) wrote: Am 07/24/2013 07:07 PM, schrieb Rob Weir: On Wed, Jul 24, 2013 at 1:00 PM, janIj...@apache.org wrote: On 24 July 2013 18:34, Rob Weirrobw...@apache.org wrote: On Wed, Jul 24, 2013 at 12:03 PM, janIj...@apache.org wrote: Hi. I have followed the discussions in here, and have seen a number of not wanted changed in our important artifacts happen. I think it is important, that items like our logos, release notes etc. cannot be changed by accident. I believe it happens by accident and that could avoided with a simple measure. It might be useful to think of this in terms of Review-Then-Commit (RTC) versus Commit-Then-Review (CTR) rules. Once we clarify these and when they apply, then we can discuss whether additional technological means are needed to enforce this. For the wiki the general rules is CTR for all users with an account. No additional karma is needed. The for resources in Subversion the general rule is CTR for all commiters. Additionally, the public can submit patches, to the list, attached to BZ issues, or using the CMS anonymous submission tool. This then is effectively RTC since a committer must first reviews the patch. Those are the default postures, but there are exceptions. For example, as we approach a Release Candidate we switch into RTC for the trunk code. We only make changes after a bug has been proposed and approved as a release blocker on the dev list. So we could simply adopt a RTC for certain resources at certain times. For example, Release Notes once a release occurs, are RTC. The project logos, once approved and published, are RTC. If we agree to such things there are lightweight ways of reminding ourselves. For example, we could have a README file in directories that are RTC that explain this. That should be enough for conscientious, well-intentioned volunteers, I am normally strong against limitations, but I would like to suggest that these items are moved to one (or more) subdirs, where the commit right is restricted e.x. to PMC members or even less. Doing so will not prohibit anybody from making their changes but simply avoid that the changes are product wide. Personally I think this is a RTC versus CTR question. This distinction is a tool that we don't invoke as often as we could. Maybe that would be sufficient, at least in SVN. Also, I think even a PMC member should be following CTR rules when it is in effect. I don't think of a PMC member as a higher class of committer in terms of what they have access to. I think you misunderstood me. I agree with the RTC/CTR discussion, but that does not prevent the accidential commit, I think it has happened to most of us, that we commit our changes, and we overlook that another file is also committed. I disagree that we have a a problem with accidental overwrites in SVN in cases where it is clear that RTC is in effect. I think the problem is that it is not clear when CTR is in effect. I don't think that it will help to prevent every error of this kind. Also, I don't see how your solution helps with truly accidental commits. Surely PMC members make errors as well? Of course, as they are humans, too. ;-) But you don't become a PMC member by default. You need to show some things that you have understand how the page is turning. And then I doubt that such error would happen. So, I also think that we should do more than just turn the CTR into RTC and expect that no mistakes will happen after that. My 2 ct. I think that there are a few things to think about. We can all understand when RTC and CTR are in effect. These are different in different systems. In the two years since OpenOffice has been with Apache, in nearly every case we have always had discussion on ANY change/commit in anything we consider source that is not applied to a bug. So this excludes most of the material on the web site with the exception of the new logo svgs. At least that is my impression. This is not really clear in our Orientation modules. And, I think in most people's minds, knowing when to go from CTR to RTC is not particularly clear either. There are some implicit assumptions -- like don't mess with SNAPSHOT builds -- but I think it would be better if we stated this explicitly. I also suggest that any artifact we feel should be considered source -- like the new logo svg files -- be put, if not in /trunk, in an SVN area that has some distinguishing name so that it is clear to committers this is really a RTC area. I like that idea. Something like /branding, a peer of
HELP: roller and strange effects.
Hi I edit a new post (Developer in AOO, 1year celebration) but have a strange problem. I have added a mailto:; link (copied from another post), but in preview it get translated: dev-AT-openoffice.apache-DOT-org and not clickable. Can someone give me a hint what I am missing ? (feel free to have a look at the draft, text is not at all final). thx in advance for some quick help. rgds jan I.
Re: AOO -- should we submit a new acronym?
Am 07/30/2013 12:30 AM, schrieb Kay Schenk: http://acronyms.thefreedictionary.com/AOO Yes, please. :-) Would be great if you can takeover to send a request/proposal to them. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: HELP: roller and strange effects.
Am 07/30/2013 08:29 PM, schrieb janI: Hi I edit a new post (Developer in AOO, 1year celebration) but have a strange problem. I have added a mailto:; link (copied from another post), but in preview it get translated: dev-AT-openoffice.apache-DOT-org and not clickable. Can someone give me a hint what I am missing ? (feel free to have a look at the draft, text is not at all final). thx in advance for some quick help. Maybe a feature to make the life harder for spambots? I've tried to find an example in other drafts or published blog posts but couldn't find one. So, I don't know if the Live post will look the same like the preview in this regard. However, I've seen links to the mailing lists webpage. That means instead of using the mailto URL, just use this as URL: http://openoffice.apache.org/mailing-lists.html#development-mailing-list-public This has the advantage that the webpage will explain a bit about the mailing list. HTH Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Do language packs have update notifications?
Am 07/30/2013 07:04 PM, schrieb Rob Weir: In OOo 3.3.0 we support Tamil with a language pack, but not a full install. In AOO 4.0 we provide a full install for Tamil, as well as a language pack. Are we able to notify 3.3.0 users of the Tamil language pack about the update? Is that something the update notification system can handle? Or does it only handle updates to the base install? Good and important question but I don't know. Maybe Oliver can tell us more? Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: HELP: roller and strange effects.
On Tue, Jul 30, 2013 at 2:29 PM, janI j...@apache.org wrote: Hi I edit a new post (Developer in AOO, 1year celebration) but have a strange problem. I have added a mailto:; link (copied from another post), but in preview it get translated: dev-AT-openoffice.apache-DOT-org and not clickable. Can someone give me a hint what I am missing ? (feel free to have a look at the draft, text is not at all final). Scroll down to the plugins to apply section and see if the email scrambler is enabled. If it is, disable it. -Rob thx in advance for some quick help. rgds jan I. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: first start of AOO 4
Hi Jürgen, Am 30.07.2013 06:15, schrieb Juergen Schmidt: Am Montag, 29. Juli 2013 um 16:52 schrieb Guenter Marxen: ... The Spelling Checker Duden Korrektor 6.0.0 seems to be incompatibel with AOO 4 (loading component library failed...). Or has anybody other informations? The Duden corrector is a C++ extension and they become easier incompatible. But with the stlport change for AOO 4.0 it is natural that it is incompatible and needs at least a recompilation. Especially for C++ extensions the maintainer should use a max version dependency and should ensure if everything works. Even a compiler upgrade can cause an incompatible change. many thanks. I'll ask the Duden publisher and report, when an AOO4-version is available. (If I understand it correctly, since AOO 4 there is no longer extension compatibility with LO. I'm curious what Duden publisher decides.) -- Grüße Günter Marxen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Website]
Am 07/30/2013 04:02 PM, schrieb Rob Weir: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Servicematt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Sure, in general yes. Should be a cheap solution. But I doubt that it is good for the user experience to put more and more into this small green box - BTW: It's called sub-green ;-) I would like to add a link to the documentation (Setup Guilde, User Manual, etc.), too, when it's ready to link to. Slowly but surely I think a redesign is necessary. Am I alone with this gut feeling? Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. Absolutely. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: New Features and Enhancements video
Howdy, Well, I'be not had a chance to read any mail, after my last message, before writing this so if it seems like I've missed something already mentioned that would be the reason. I've been plowing ahead with my ideas here; not just as a single activity to produce one or two videos but rather to start a framework for a project multi-media resources library, from which multiple videos, for multiple purposes, would be generated. It could also be used to generate themed artifacts for fliers/presentations/artwork(wallpapers, etc) that tie in with these videos. The key is to generate small chunks, of high quality, which can then be used to mix final works. By way of example I've uploaded a zip file at: https://docs.google.com/file/d/0Bx7ZNEXlmR0ISV9GcjY5M1l1TTA with the following files: July30/Chunks - AOO4_default_blk.mp4 and AOO4_default_white.mp4 are (should be, more on that later) used as consistent backgrounds in other chunks - WelcomeUsers.mp4, NewLogo.mp4, CommunityActivities.mp4, CommunityActivities.mp4 where created as a reshaping of the wiki features and enhancements page. - Each video includes a voice over (almost) and there is an associated text file with transcript of same. For the initial finished product I had in mind three category of video and one physical video for each category. The categories I had in mind are Flowers - as in 'Congrats on the new birth' - short, punchy and could supply the ending of the other videos to tie them together and for re-use efficiencies. Community - The apache way, recruiting, etc. Features - about the product or services offered by the community. Alright, so I already turned in a 'flowers' type video last week [and since no one else has said it, a not so good one] but do not consider that the final work. For the 'community' category - These pieces: CommunityBeforeCode_loop.mp4, suitable for use at a show table running on a laptop, voice over, no musical background - notice I did not tag this with a license. AOO4_HotTamaleBaby.mp4 and hottamale.mp4 take that basic loop and add a little party music. For the 'features' category - These: NewFeaturesAndEnhancements_loop.mp4 - again, voice over only, note no license AOO_Features_Waltz.mp4, add a nice sound track and pickup my license tag, notice I said MY license tag, I think that is the best way to approach these pieces with CC license material - but that is a subject needing some thought gong forward. In the graphics directory, well, graphics files ;) - some descriptions to follow. So, my vision would be to at the end deliver, somehow, for the projects use an ISO with all the files used to produce the works, this would include the OpenShot and Pitivi (and other) project files, it would include some instructions (which we would build as we do this) on how to make use of the material. What I would hope could be done, if the good folks at source forge are willing which I expect hey would be, is to generate a small and changing over time set of videos and have these dished out to users in round robin fashion. There is a fair bit here to consider, I'm aware, and I will end this mail here. I should be picking up mail again in 2 or 3 days and will also have an update to the files. Best wishes, //drew On Sat, Jul 27, 2013 at 3:09 PM, Andrea Pescetti pesce...@apache.orgwrote: On 25/07/2013 Drew Jensen wrote: https://docs.google.com/file/**d/**0Bx7ZNEXlmR0IUWt5cnUxQ3JNbnM/** edit?usp=sharinghttps://docs.google.com/file/d/0Bx7ZNEXlmR0IUWt5cnUxQ3JNbnM/edit?usp=sharing There is an opening 8 seconds with the logo on a non-white background: 1 - is that acceptable 2 - is the ASF tag line acceptable I think that both are acceptable, but there's no need to display trademark attribution for all the length of the video. It will be enough to have them in the closing credits, maybe with the longer version that is in the http://www.openoffice.org/ page footer. Then there is what would be the body of the piece - a full white background, as this logo really doesn't work to well otherwise it seems to me. 1 - I assume the logo is not an issue here, but thought I'd double check. 2 - I changed the ASF tagline to blue, as you can see 2a - I wonder if I may drop that (the ASF tagline) on the body frames, leaving it on the opening and then bringing it back for the credits at the end, as I will include sub-titles with this piece (in English) and that space would be the place for these to display of course. Yes, it is just visual noise to keep it visible for all the video. Anyway, that is enough for now and to get things started. It's a good start! Regards, Andrea. --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Website]
On 30 July 2013 21:06, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 07/30/2013 04:02 PM, schrieb Rob Weir: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Servicematt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/**download/http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Sure, in general yes. Should be a cheap solution. But I doubt that it is good for the user experience to put more and more into this small green box - BTW: It's called sub-green ;-) I would like to add a link to the documentation (Setup Guilde, User Manual, etc.), too, when it's ready to link to. Slowly but surely I think a redesign is necessary. Am I alone with this gut feeling? no you are not. That page would benefit from a general redesign, instead of pressing all kinds of changes into the current structure. rgds jan I. Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. Absolutely. Marcus --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: HELP: roller and strange effects.
On 30 July 2013 20:57, Rob Weir robw...@apache.org wrote: On Tue, Jul 30, 2013 at 2:29 PM, janI j...@apache.org wrote: Hi I edit a new post (Developer in AOO, 1year celebration) but have a strange problem. I have added a mailto:; link (copied from another post), but in preview it get translated: dev-AT-openoffice.apache-DOT-org and not clickable. Can someone give me a hint what I am missing ? (feel free to have a look at the draft, text is not at all final). @marcus: I copied from the new blog entry, interview with prOOo-box. Scroll down to the plugins to apply section and see if the email scrambler is enabled. If it is, disable it. Thanks that did the trix. Now you have 3 tips for roller newbies :-) rgds jan I. -Rob thx in advance for some quick help. rgds jan I. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: New Features and Enhancements video
OOPS - double post - Just to be clear, the zip file I uploaded today contains nothing that should be considered done - there are lots of issues needing addressed on each before they are ready for use - well, enough to keep a guy busy for a week, at least ;) Please, feel to free to comment on any CHUNK or LOOP file, these are the, IMO, core artifacts on which all he fun stuff hangs. Adios On Tue, Jul 30, 2013 at 3:29 PM, Drew Jensen drewjensen.in...@gmail.comwrote: Howdy, Well, I'be not had a chance to read any mail, after my last message, before writing this so if it seems like I've missed something already mentioned that would be the reason. I've been plowing ahead with my ideas here; not just as a single activity to produce one or two videos but rather to start a framework for a project multi-media resources library, from which multiple videos, for multiple purposes, would be generated. It could also be used to generate themed artifacts for fliers/presentations/artwork(wallpapers, etc) that tie in with these videos. The key is to generate small chunks, of high quality, which can then be used to mix final works. By way of example I've uploaded a zip file at: https://docs.google.com/file/d/0Bx7ZNEXlmR0ISV9GcjY5M1l1TTA with the following files: July30/Chunks - AOO4_default_blk.mp4 and AOO4_default_white.mp4 are (should be, more on that later) used as consistent backgrounds in other chunks - WelcomeUsers.mp4, NewLogo.mp4, CommunityActivities.mp4, CommunityActivities.mp4 where created as a reshaping of the wiki features and enhancements page. - Each video includes a voice over (almost) and there is an associated text file with transcript of same. For the initial finished product I had in mind three category of video and one physical video for each category. The categories I had in mind are Flowers - as in 'Congrats on the new birth' - short, punchy and could supply the ending of the other videos to tie them together and for re-use efficiencies. Community - The apache way, recruiting, etc. Features - about the product or services offered by the community. Alright, so I already turned in a 'flowers' type video last week [and since no one else has said it, a not so good one] but do not consider that the final work. For the 'community' category - These pieces: CommunityBeforeCode_loop.mp4, suitable for use at a show table running on a laptop, voice over, no musical background - notice I did not tag this with a license. AOO4_HotTamaleBaby.mp4 and hottamale.mp4 take that basic loop and add a little party music. For the 'features' category - These: NewFeaturesAndEnhancements_loop.mp4 - again, voice over only, note no license AOO_Features_Waltz.mp4, add a nice sound track and pickup my license tag, notice I said MY license tag, I think that is the best way to approach these pieces with CC license material - but that is a subject needing some thought gong forward. In the graphics directory, well, graphics files ;) - some descriptions to follow. So, my vision would be to at the end deliver, somehow, for the projects use an ISO with all the files used to produce the works, this would include the OpenShot and Pitivi (and other) project files, it would include some instructions (which we would build as we do this) on how to make use of the material. What I would hope could be done, if the good folks at source forge are willing which I expect hey would be, is to generate a small and changing over time set of videos and have these dished out to users in round robin fashion. There is a fair bit here to consider, I'm aware, and I will end this mail here. I should be picking up mail again in 2 or 3 days and will also have an update to the files. Best wishes, //drew On Sat, Jul 27, 2013 at 3:09 PM, Andrea Pescetti pesce...@apache.orgwrote: On 25/07/2013 Drew Jensen wrote: https://docs.google.com/file/**d/**0Bx7ZNEXlmR0IUWt5cnUxQ3JNbnM/** edit?usp=sharinghttps://docs.google.com/file/d/0Bx7ZNEXlmR0IUWt5cnUxQ3JNbnM/edit?usp=sharing There is an opening 8 seconds with the logo on a non-white background: 1 - is that acceptable 2 - is the ASF tag line acceptable I think that both are acceptable, but there's no need to display trademark attribution for all the length of the video. It will be enough to have them in the closing credits, maybe with the longer version that is in the http://www.openoffice.org/ page footer. Then there is what would be the body of the piece - a full white background, as this logo really doesn't work to well otherwise it seems to me. 1 - I assume the logo is not an issue here, but thought I'd double check. 2 - I changed the ASF tagline to blue, as you can see 2a - I wonder if I may drop that (the ASF tagline) on the body frames, leaving it on the opening and then bringing it back for the credits at the end, as I will include sub-titles with this piece (in English) and that space
Re: [Website]
On Tue, Jul 30, 2013 at 3:32 PM, janI j...@apache.org wrote: On 30 July 2013 21:06, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 07/30/2013 04:02 PM, schrieb Rob Weir: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Servicematt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/**download/http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Sure, in general yes. Should be a cheap solution. But I doubt that it is good for the user experience to put more and more into this small green box - BTW: It's called sub-green ;-) I would like to add a link to the documentation (Setup Guilde, User Manual, etc.), too, when it's ready to link to. Slowly but surely I think a redesign is necessary. Am I alone with this gut feeling? no you are not. That page would benefit from a general redesign, instead of pressing all kinds of changes into the current structure. A couple tools/techniques to keep in mind that could help with a page redesign: 1) If we can stabilize the page for a week or two the numbers from Google Analytics will tell us what the most common options from that page are. For example, what % of users click other, what % go for release notes, etc. This might help us bring together the most-used information in a less cluttered way. 2) We have the ability, via Google Experiments, to try alternative designs and have them be randomly shown to different users, to see which one performs best. We did that with different variations on the social sharing icons/links a while back, you may recall. All this requires is that we have some measurable metric to rate the designs by. For example, maybe we want to minimize the number of seconds the user stays on that page? (A long delay might mean it takes too long to find what they want). Or maximize the percentage of visitors who ultimately download AOO? Regards, -Rob rgds jan I. Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. Absolutely. Marcus --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Do language packs have update notifications?
On 30 July 2013 20:56, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 07/30/2013 07:04 PM, schrieb Rob Weir: In OOo 3.3.0 we support Tamil with a language pack, but not a full install. In AOO 4.0 we provide a full install for Tamil, as well as a language pack. Are we able to notify 3.3.0 users of the Tamil language pack about the update? Is that something the update notification system can handle? Or does it only handle updates to the base install? Good and important question but I don't know. Maybe Oliver can tell us more? that would be nice, I am just in the process of splitting the language zip files to find a version number. The language files are packed as extensions, and I am just trying to find out how its ensured that they are only used with the correct release. Maybe oliver or someelse can give a hint on that too. rgds jan I. Marcus --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Where can I find the original files of the release notes?
Ditto - please? On Thu, Jul 25, 2013 at 5:45 PM, Jörg Schmidt joe...@j-m-schmidt.de wrote: Hello, Who has the original files from which the screenshots for the release-notes (eg http://wiki.openoffice.org/w/images/c/c0/120962_MS.jpg) were made? (I do not mean the images of the UI elements, but for example the Calc files.) Can someone please make me available so that I can translate it to German and create German screenshots? Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO -- should we submit a new acronym?
On Tue, Jul 30, 2013 at 11:56 AM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 07/30/2013 12:30 AM, schrieb Kay Schenk: http://acronyms.**thefreedictionary.com/AOOhttp://acronyms.thefreedictionary.com/AOO Yes, please. :-) Would be great if you can takeover to send a request/proposal to them. Marcus Well I did submit AOO = Apache OpenOffice but it isn't showing up. So, I will contact them to fix this...somehow. --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi
Re: 4.0 and loss of backward compatibility for extensions with toolbar
Top posting Same as Rob. Hagar Le 30/07/2013 15:55, Rob Weir a écrit : On Tue, Jul 30, 2013 at 9:30 AM, Roberto Galoppini roberto.galopp...@gmail.com wrote: 2013/7/29 Roberto Galoppini roberto.galopp...@gmail.com 2013/7/27 Rob Weir robw...@apache.org On Sat, Jul 27, 2013 at 4:59 PM, Roberto Galoppini roberto.galopp...@gmail.com wrote: 2013/7/27 Rob Weir robw...@apache.org On Fri, Jul 26, 2013 at 5:59 PM, Hagar Delest hagar.del...@laposte.net wrote: Le 26/07/2013 15:40, Roberto Galoppini a écrit : A) a link to a version compatible with AOO 4.0 has been added for http://extensions.openoffice.org/en/project/pdfimport and http://extensions.openoffice.org/en/project/mysql_connector B) 4.0 has been added to the list of possible compatibilities. For example http://extensions.openoffice.org/en/node/287/releases doesn't enlist 4.0 among AOO compatible versions, while new extensions have that set, see for example http://extensions.openoffice.org/en/node/5644/releases. Note that it's up to the author to indicate his/her extension compatibility list, and he/she can update it without the need to upload the file again. But it means that the author has to be aware that there is a change and he has to update the relevant field. There is no script that could add the lack of compatibility if the extension has not been updated yet? The lack of compatibility is somehow implicit if you read that a given extension is compatible with OpenOffice 3.3 or AOO 3.4 and it doesn't mention AOO 4.0. See below about how to make sure such info is up-to-date. For the record, in the case of the Lorem ipsum extension, the author doesn't seem to be willing to update it... If an extension is essentially abandoned then it is only a matter of time before it breaks. Either that or we put ourselves into a position where we can never evolve and improve our API. We should focus on the needs of active extension developers, not the inactive ones. This is what we did to keep extension authors in the loop: 1) We created a special mailing list, a...@openoffice.apache.org for discussions about extensions. 2) We worked with SourceForge to send an email to all registered extension authors to invite them to the new list. This was done before the *.openoffice.org email forwarder was shut down, so they all should have received the note. We might resend an email to all Extensions' authors re-inviting them to subscribe to the API mailing-list and also inviting them to check if their extensions do work with AOO 4.0 and eventually update their extension page accordingly. Does it sound like a plan? Reminders are good. So what do we want to tell them, does anyone want to craft a draft message for AOOE authors? Subject: About Apache OpenOffice New Release and Updating your Extension's Compatibility Info Dear OpenOffice.org Extensions author, Maybe just OpenOffice Extensions author? As you may have heard, Apache OpenOffice 4.0 is now out, and we'd like to invite you to test your own extension and figure out if it is or is not compatible with Apache OpenOffice 4.0 and its new APIs. If your extension is compatible with AOO 4.0, please take a moment to update the extension's compatibility information so that end-users will know it works with the latest release. If your extension is not compatible Is it clear how to do this? Is there any doc we should point them to for this? we'd encourage you to release a new version if you have time, or ask people to help you with that at the API mailing-list (http://openoffice.apache .org/mailing-lists.html#api-mailing-list-public). How do you like this? Good. -Rob Roberto Roberto -Rob Roberto 3) We announce the 4.0 API changes on the API list and answered any questions that came up. True, not everyone is happy about the changes. But we tried to ensure that every active extension author was aware of the changes coming. Regards, -Rob Hagar - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:
Re: [Website]
Am 07/30/2013 06:39 PM, schrieb Rob Weir: On Tue, Jul 30, 2013 at 10:02 AM, Rob Weirrobw...@apache.org wrote: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Servicematt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Looking into the issue a little more. It gets a little more complicated. We're still seeing a fair number of update notifications (around 80,000 in the last week) being sent to older OOo installs, 3.3.0 and even 3.2.1. I don't know what this is happening, but it is. Maybe they are finding an old copy of a CD and installing it and then immediately getting the update notification? It can happen. The update notifications are generally sending them to http://www.openoffice.org/download. When this occurs with a language that was included in 3.4.1 but not in 4.0 then this is a problem. They are looking for Swedish, for example, and it cannot be found. For this particular kind of user, I'm not sure a small link labeled Older AOO Versions will help. It would be very unintuitive for the user to look there, because from their perspective they are looking for a newer version and 3.4.1 is newer than what they have, not older. A couple of ways to plug this hole: 1) Enhance the download logic on the main page to offer the most recent version available for the detected language. Or does it already try to do that? As we have changed the directory structure it would be a nightmare to create this logic. BTW: Who would volunteer to test this? :-P So, no. The logic tries to guess the right language and platform. But assumes always a single version. or 2) Change the update notifications so the user is sent to the 3.4.1-era other.html page, so they can more easily find their download. Actually, thinking out loud, this might be the easiest solution. And we can still add the Older AOO Versions, which would be good for a different kind of user, someone specifically looking for a 3.4.1 download. This might even be our own QA volunteers ;-) Seems to be the perfect challenge to create a table about availablility for languages and versions. I'm getting a bit lost about the game Find the right versions for the right languages. ;-) Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Website]
On Tue, Jul 30, 2013 at 3:55 PM, Marcus (OOo) marcus.m...@wtnet.de wrote: Am 07/30/2013 06:39 PM, schrieb Rob Weir: On Tue, Jul 30, 2013 at 10:02 AM, Rob Weirrobw...@apache.org wrote: On Tue, Jul 30, 2013 at 4:25 AM, Mattias BIK Servicematt...@bikab.com wrote: Hello For christ sake. Every time i trying to download openoffice there is almost impossible to find the right download page. Im from Sweden and and if the current version is not supported by Swedish, put a link to an older version then. How hard can it be? Tired of searching for download links now. No reply of this mail is needed. I just have to blow of some steem after bringing some time on ur website. One easy way we can improve here. How about modifying this page: http://www.openoffice.org/download/ And where it currently has the line that says: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Legacy Version Change that to: Signatures and Hashes: KEYS , ASC , MD5 , SHA256 | Release Notes | Older AOO Versions | Legacy OpenOffice.org And then make Older AOO Versions link to the old 3.4.1-era download/other.html file, which we could resurrect from SVN. Would that work? Looking into the issue a little more. It gets a little more complicated. We're still seeing a fair number of update notifications (around 80,000 in the last week) being sent to older OOo installs, 3.3.0 and even 3.2.1. I don't know what this is happening, but it is. Maybe they are finding an old copy of a CD and installing it and then immediately getting the update notification? It can happen. The update notifications are generally sending them to http://www.openoffice.org/download. When this occurs with a language that was included in 3.4.1 but not in 4.0 then this is a problem. They are looking for Swedish, for example, and it cannot be found. For this particular kind of user, I'm not sure a small link labeled Older AOO Versions will help. It would be very unintuitive for the user to look there, because from their perspective they are looking for a newer version and 3.4.1 is newer than what they have, not older. A couple of ways to plug this hole: 1) Enhance the download logic on the main page to offer the most recent version available for the detected language. Or does it already try to do that? As we have changed the directory structure it would be a nightmare to create this logic. BTW: Who would volunteer to test this? :-P So, no. The logic tries to guess the right language and platform. But assumes always a single version. The only sane way to do this is to make it data-driven, a data table or even spreadsheet that lists the installed versions and the recommended update paths and then generates either the update XML files or a JSON file that the Javascript can use. Or both. -Rob or 2) Change the update notifications so the user is sent to the 3.4.1-era other.html page, so they can more easily find their download. Actually, thinking out loud, this might be the easiest solution. And we can still add the Older AOO Versions, which would be good for a different kind of user, someone specifically looking for a 3.4.1 download. This might even be our own QA volunteers ;-) Seems to be the perfect challenge to create a table about availablility for languages and versions. I'm getting a bit lost about the game Find the right versions for the right languages. ;-) Unfortuntely the legacy directory structure, with its stable and localized directories is too weird to point users to directly. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CMS PATCH] Asturian translation (work in progress)
This one is complete and in staging: http://ooo-site.staging.apache.org/ast/download/common/instructions.html On Mon, Jul 29, 2013 at 7:24 PM, Anonymous CMS User anonym...@apache.orgwrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/ast%2Fdownload%2Fcommon%2Finstructions.html Partial translation to Asturian. I send it as a caution to avoid a broken link in case someone publish the Download page in Asturian -- Xuacu Saturio Index: trunk/content/ast/download/common/instructions.html === --- trunk/content/ast/download/common/instructions.html (revision 0) +++ trunk/content/ast/download/common/instructions.html (working copy) @@ -0,0 +1,392 @@ +!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Strict//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd; +html xmlns=http://www.w3.org/1999/xhtml; lang=ast / +head + meta http-equiv=Content-Type content=text/html; charset=utf-8 / + titleInstrucciones pa descargar ya instalar Apache OpenOffice 4.0/title +/head + +body + +h2Instrucciones pa descargar ya instalarbr / +Apache OpenOffice 4.0.0/h2 + +pÚltimu anovamientu: 2013-07-21/p + + +pemDende la versión 3.4, yá nun s'empaqueta un JRE (Jave Runtime Environment) con OpenOffice. +Sicasí, inda pue necesitar un JRE pa un functionamientu completu. (Vea a href=java.html +Java y Apache OpenOffice/a). Por favor, asegurese de que'l sistema tien instalao Java 1.6 +o mayor pa un functionamientu completu./em/p + +pemApache OpenOffice 4.0 tien cambios significativos na configuración de direutorios d'OpenOffice qu'afeuten al so perfil d'OpenOffice anterior./em +Les a href= https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=33296031;Notes de la versión Apache OpenOffice 4.0/a dan una esplicación d'estos cambios. Sicasí, habría de tener la oportunidá de +migrae la configuración del perfil antiguu al área del perfil nuevu./p + +ul + liba href=#winWindows/a/b + ul +lia href=#fileassocAsociaciones de ficheros/a/li + /ul + /li + liba href=#appleApple Macintosh/a/b +ul + lia href=#gatekeeperOS X y Gatekeeper/a/li + lia href=#mac-generalRecursos d'instalación en Macintosh/a/li + /ul +/li + liba href=#linuxLinux/a/b + ul +lia href=#linux-preinstallPreInstalación en Linux/a/li +lia href=#linux-generalNotes xenerales d'instalación en Linux: RPM o DEB/a/li +lia href=#linux-rpmLinux basáu en RPM/a/li +lia href=#linux-debLinux basáu en DEB/a/li +lia href=#other_linuxPaquetes pa distribuciones de Linux/a/li +/ul +/li + liba href=#problemsProblemes d'instalación/a/b/li + liba href=#moreMás recursos d'instalación/a/b/li +/ul + +hr / + +h2 id=winWindows XP/2003/Vista/ 7 / 8 Guía d'aniciu rápidu pa Apache OpenOffice 4.0/h2 + +pBienveníos a la Guía d'aniciu rápidu d'Apache OpenOffice pa entornos Windows. Más abaxo alcontrará instrucciones +pasu a pasu pa descargar ya instalar Apache OpenOffice versión 4.0.0 nel sistema. Recomendamos imprimir esta fueya +d'instrucciones como referencia enantes de descargar y principiar la instalación d'Apache OpenOffice./p + +pSi ye expertu col sistema operativu Windows, pue usar les instrucciones que se dan na siguiente seición. +Sinón, pase a la seición a href=#comprehensiveInstrucciones d'instalación completes/a./p + +!-- +pIf you have Windows XP, you may wish to view a +a href= http://www.digitaldistribution.com/community/howtoinstallooo2onxp/;flash presentation/a overview of the +download and installation procedure. Note: The presentation does not include checking the integrity of the downloaded file +and returns you to the Apache OpenOffice home page. At the finish of the presentation click the Back button in your browser +to return to this page./p +-- + +h3Resume del procesu de descarga ya instalación/h3 + +pPa descargar ya instalar Apache OpenOffice 4.0, siga los pasos d'esta llista:/p + +!-- +pBe aware: OOo 2.x replaces an earlier 3.0.x installation/p +-- + +ol + liRevise los a href= http://www.openoffice.org/dev_docs/source/sys_reqs_aoo40.html;Requisitos del sistema/a pa + usar Apache OpenOffice./li + liDescargue ya instale a href=http://www.java.com/;Java JRE/a si necesita les funciones que dependen de Java./li + lia href=http://www.openoffice.org/download/;Descargue Apache OpenOffice 4.0.0/a./li + liAnicie sesión como alministrador (si ye necesario)./li + liDesempaquete ya instale los ficheros d'Apache OpenOffice 4.0.0 descargaos./li + liExecute Apache OpenOffice 4.0.0 p'asegurase de que la instalación ye correuta./li +/ol + +h3 id=comprehensiveInstrucciones d'instalación completes/h3 + +pEsta seición describe detalladamente cómo instalar Apache OpenOffice nel so sistema./p + +pLo primero que tendría de facer ye lleer estes instrucciones
Re: AOO -- should we submit a new acronym?
On Tue, Jul 30, 2013 at 12:53 PM, Kay Schenk kay.sch...@gmail.com wrote: On Tue, Jul 30, 2013 at 11:56 AM, Marcus (OOo) marcus.m...@wtnet.dewrote: Am 07/30/2013 12:30 AM, schrieb Kay Schenk: http://acronyms.**thefreedictionary.com/AOOhttp://acronyms.thefreedictionary.com/AOO Yes, please. :-) Would be great if you can takeover to send a request/proposal to them. Marcus Well I did submit AOO = Apache OpenOffice but it isn't showing up. So, I will contact them to fix this...somehow. a quick update...I sent http://acronyms.thefreedictionary.com/AOO a note about their problems. The site above is a little front-end to the actual acronym finder site: http://www.acronymfinder.com/ in which we are found but the first site's hooks to the second are broken I think. We are on www.acronymfinder.com now, but...they changed my description entry of Apache OpenOffice to Apache Openoffice, so I sent them a note about this. Done with this for now. --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi
Implementation of the new OpenOffice CERT.
hi FYI. I have created a new jira issue, describing the implementation of the new CERT. https://issues.apache.org/jira/browse/INFRA-6608 If possible lets keep any discussion on the list and just add the changes as comment to the jira. rgds jan I.
[REVIEW] draft blog.
Hi A while ago we discussed to get more bloggers. Since I have 1 years birthday in a couple of days, I have made a blog. I am not a native speaker, so I assume there are some mistakes in there, feel free to correct them. But more importantly, is this a post we as community would like to make public ? https://blogs.apache.org/preview/OOo/?previewEntry=developer_in_aoo_1year_celebration Please be gentle this is my first blog. rgds jan I.
Re: [REVIEW] draft blog.
On Tue, Jul 30, 2013 at 5:59 PM, janI j...@apache.org wrote: Hi A while ago we discussed to get more bloggers. Since I have 1 years birthday in a couple of days, I have made a blog. I am not a native speaker, so I assume there are some mistakes in there, feel free to correct them. But more importantly, is this a post we as community would like to make public ? https://blogs.apache.org/preview/OOo/?previewEntry=developer_in_aoo_1year_celebration Please be gentle this is my first blog. rgds jan I. Sometimes, when I'm proofing material from an EFL speaker, I find myself inclined to not try to fix certain things because they look naturally authentic and sincere. Excessive proofing runs the risk of editing out some of the raw passion and enthusiasm being expressed. Especially in cases like this, where passion and enthusiasm are sort of the point of the blog post. But I can give it a shot, if you like...? Don
Re: [REVIEW] draft blog.
On Tue, Jul 30, 2013 at 6:14 PM, Donald Whytock dwhyt...@apache.org wrote: On Tue, Jul 30, 2013 at 5:59 PM, janI j...@apache.org wrote: Hi A while ago we discussed to get more bloggers. Since I have 1 years birthday in a couple of days, I have made a blog. I am not a native speaker, so I assume there are some mistakes in there, feel free to correct them. But more importantly, is this a post we as community would like to make public ? https://blogs.apache.org/preview/OOo/?previewEntry=developer_in_aoo_1year_celebration Please be gentle this is my first blog. rgds jan I. Sometimes, when I'm proofing material from an EFL speaker, I find myself inclined to not try to fix certain things because they look naturally authentic and sincere. Excessive proofing runs the risk of editing out some of the raw passion and enthusiasm being expressed. Especially in cases like this, where passion and enthusiasm are sort of the point of the blog post. +1. A personal-perspective post should not read like a marketing brochure. I thought the post was great. I'd recommend only simple corrections, e.g., standardize capitalization. I think personal posts are enhanced with a photograph, if Jan has a suitable one. But it is fine either way. Regards, -Rob But I can give it a shot, if you like...? Don - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSSION] Should source changes require [discussion] and/or issue submission?
On Jul 30, 2013, at 9:52 AM, Kay Schenk wrote: On Mon, Jul 29, 2013 at 3:00 PM, janI j...@apache.org wrote: On 29 July 2013 23:05, Andrea Pescetti pesce...@apache.org wrote: Kay Schenk wrote: http://www.openoffice.org/**marketing/art/galleries/logos/**aoo-working/ http://www.openoffice.org/marketing/art/galleries/logos/aoo-working/ Last week, two of the original svg files -- files prefixed with: Apache_OpenOffice_Logo_ChrisR_**selected_2013-06 were changed. These changes were not discussed in advance, nor an issue submitted for them. Given the events of the day, it was the PMC's decision to not veto these changes, but to copy these changed originals Thank you Kay for the reminder. I added a WARNING.txt file to the aoo-working directory to help avoiding changes that have not been discussed here first. I like the WARNING.txt file, could we agree to use the same file for other sensible (not sure if that is the right word) areas ? I think of e.g. release notes. So, back the original topic. Given recent events, do we want to have a changed policy to require issue submission and/or list discussion before new commits? I'd say we don't need it in general; it will be helpful for all significant code changes, but surely we don't need it for the website. Let's rely on common sense and peer scrutiny. +1, lets not make it too complicated to work, that said with a smile !! For significant code changes, a discussion is a must, but I thought it was already policy ? I'm ok with adding WARNING.txt as appropriate. I can see that there may be either of two types of warnings. Full RTC - where any change including additions should be discussed. Adds CTR and updates RTC - where changes to existing artifacts require discussion. The branding tree and release notes are examples of where this is in affect. It may be that changes are being made and reviewed during the discussion. We wouldn't be so strict. For example before the 4.1 release. Rob may start to create release notes by adding and then making a series of modifications. There would be a [DISCUSS] Starting release notes. We wouldn't need a discussion for every little change. It is more we want to be aware these are happening. The community can then help in very way from criticism to translation to whatever. Regards, Dave rgds jan I. Regards, Andrea. --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Here is some information on decision making/discussions: http://openoffice.apache.org/orientation/decision-making.html http://community.apache.org/committers/ http://www.apache.org/foundation/how-it-works.html#roles I could not find any specific rules on when decision making should be used. In OpenOffice, it is used on a regular basis for many different changes, but WHEN to use it doesn't seem to be set in stone. And it looks like, some projects have defined their own criteria. -- - MzK Success is falling nine times and getting up ten. -- Jon Bon Jovi - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [REVIEW] draft blog.
On Jul 30, 2013, at 3:32 PM, Rob Weir wrote: On Tue, Jul 30, 2013 at 6:14 PM, Donald Whytock dwhyt...@apache.org wrote: On Tue, Jul 30, 2013 at 5:59 PM, janI j...@apache.org wrote: Hi A while ago we discussed to get more bloggers. Since I have 1 years birthday in a couple of days, I have made a blog. I am not a native speaker, so I assume there are some mistakes in there, feel free to correct them. But more importantly, is this a post we as community would like to make public ? https://blogs.apache.org/preview/OOo/?previewEntry=developer_in_aoo_1year_celebration Please be gentle this is my first blog. rgds jan I. Sometimes, when I'm proofing material from an EFL speaker, I find myself inclined to not try to fix certain things because they look naturally authentic and sincere. Excessive proofing runs the risk of editing out some of the raw passion and enthusiasm being expressed. Especially in cases like this, where passion and enthusiasm are sort of the point of the blog post. +1. A personal-perspective post should not read like a marketing brochure. I thought the post was great. I'd recommend only simple corrections, e.g., standardize capitalization. I think personal posts are enhanced with a photograph, if Jan has a suitable one. But it is fine either way. +1000 - this sure gives me a big smile! Best Regards, Dave Regards, -Rob But I can give it a shot, if you like...? Don - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [REVIEW] draft blog.
On Tue, Jul 30, 2013 at 4:32 PM, Rob Weir robw...@apache.org wrote: On Tue, Jul 30, 2013 at 6:14 PM, Donald Whytock dwhyt...@apache.org wrote: On Tue, Jul 30, 2013 at 5:59 PM, janI j...@apache.org wrote: Hi A while ago we discussed to get more bloggers. Since I have 1 years birthday in a couple of days, I have made a blog. I am not a native speaker, so I assume there are some mistakes in there, feel free to correct them. But more importantly, is this a post we as community would like to make public ? https://blogs.apache.org/preview/OOo/?previewEntry=developer_in_aoo_1year_celebration Please be gentle this is my first blog. rgds jan I. Sometimes, when I'm proofing material from an EFL speaker, I find myself inclined to not try to fix certain things because they look naturally authentic and sincere. Excessive proofing runs the risk of editing out some of the raw passion and enthusiasm being expressed. Especially in cases like this, where passion and enthusiasm are sort of the point of the blog post. +1. A personal-perspective post should not read like a marketing brochure. I thought the post was great. I'd recommend only simple corrections, e.g., standardize capitalization. I think personal posts are enhanced with a photograph, if Jan has a suitable one. But it is fine either way. Regards, -Rob But I can give it a shot, if you like...? Don - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org This is an excellent blog post. I agree that only a very few changes are needed for clarity. The imperfections are minor and make it authentic.
Re: [PROPOSAL] New other.html for all possible download links
Am 07/30/2013 12:25 AM, schrieb Kay Schenk: On Mon, Jul 29, 2013 at 3:21 PM, janIj...@apache.org wrote: On 30 July 2013 00:16, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/29/2013 10:39 PM, schrieb sebb: On 29 July 2013 21:12, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/29/2013 09:45 PM, schrieb sebb: On 29 July 2013 19:27, Marcus (OOo)marcus.m...@wtnet.dewrote: Am 07/26/2013 11:10 PM, schrieb Marcus (OOo): Am 07/26/2013 10:44 PM, schrieb Andrea Pescetti: On 25/07/2013 Marcus (OOo) wrote: I've created a new webpage to offer all possible download links for a release version: http://ooo-site.staging.**apache.org/download/test/** other_tables.html http://ooo-site.staging.apache.org/download/test/other_tables.html This is really nice, looking forward to seeing it online! see below It's especially important to have a link to checksums for those who want a static reference to it or want to verify a package on a different system than the one used for downloading. That was one intension, yes. - all possible downloads for a respective language and OS in a single place I foresee another interesting way to use that page, i.e., getting more localization volunteers. Let's get this version online first, but maybe we could then add another table with something like The following languages are released only as source code:, and then a list of each of the 90+ remaining languages with the link to help us release it (in most cases, it will be a link to http://openoffice.apache.org/** translate.htmlhttp://openoffice.apache.org/translate.html but in some cases it might be different). Good idea. However, I think I've to add more additions than one can thought. But this is no obstacle. @Andrea: I've already considered your smaller font size wish for the checksum links. Thanks, looks great. Thanks. :-) Even when I've missed to state it from the beginning but I expect to use lazy consensus here. If there are no objections I plan to make it Live at ~Sunday evening Hamburg time. As I haven't seen any objections I'll create the new other.html in a the next time. Sorry, but I find the page hard to use. Most people will not need any language packs, so why clutter the table with them? Also if a user does want to add multiple language packs, it's hard work finding them amongst all the full installations. I think it would be a lot clearer for the page to be laid out something like the following: This was the old system and the goal was to integrate all files that belong to a specific language and platform. I'm not sure that goal is particularly useful to the end-user. If it's hard to read due to a small font size, this could be changed. It's not the font size. Otherwise I don't thing that it's too confusing. Well, you are a developer working on OOo. Only for the website, not for the source code. But maybe this is no longer relevant as I do this already for years. I am trying to look at it as a non-developer who wants to download the software. [ cut here ] --- ... [ cut here ] --- If it is possible to provide a dynamic page, then it might be nice to determine the platform first (user selected; perhaps with auto-detected default), and then use the platform to display only the installation sets and language packs for that platform. The dynamic thing is not to continue the data guessing from the main download webpage but to simplify the modification for new releases. The other.html is a kind of fallback when: a) the user is not able to use the green box on the previous main download webpage. b) or when he is searching for a build different from the browser's language / platform. AFAICT it's also used when the user wants to add a new language, in which case they already have the base installation. Yes, and there are maybe some more possibilities. As we don't know the reason(s) for a) there shouldn't be any limitations to give the user the full control to find what he needs. Yes, but that's not relevant to the issue of the page design. And if b) it will help him as well. Which is where the page design is very important. The difference of full installations and language packs is described directly above the table by your suggestion. Yes, but I'm afraid I don't find it easy to read. There's quite a lot of information there which is not particularly relevant to the end user. Also the most common use case - downloading a single base installation and no languag packs - is not actually described. If you think that the text can be better, then please tell me. Based on Apache's famous slogan: Patches are welcome. :-) That would avoid problems with people downloading the language pack for the wrong platform. Sorry, but this can also happen in the current other.html. Of course; I was just making a
Re: Portable version (X-ApacheOpenOffice by winPenPack) updated
Am 07/28/2013 10:18 PM, schrieb Marcus (OOo): Am 07/28/2013 09:55 PM, schrieb Dave Fisher: On Jul 28, 2013, at 11:21 AM, Marcus (OOo) wrote: Am 07/28/2013 06:28 PM, schrieb Dave Fisher: On Jul 28, 2013, at 5:46 AM, Marcus (OOo) wrote: Am 07/28/2013 02:18 PM, schrieb Rob Weir: On Sun, Jul 28, 2013 at 8:12 AM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/28/2013 01:56 PM, schrieb janI: On 28 July 2013 13:47, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/28/2013 12:37 PM, schrieb Andrea Pescetti: On 24/07/2013 Hagar Delest wrote: Huge thanks for such reactivity indeed. But a lot of people are missing it due to the portable version being too hidden in our download infrastructure. What's the best solution to ensure that: 1) Users can actually find the portable version and 2) Users are correctly informed that this is a third-party port? My proposal (subject to lazy consensus or discussion here) would be to modify http://www.openoffice.org/**download/http://www.openoffice.org/download/ as follows: add it to the line that says Get all platforms, languages, language packs | Source Code tarballs and SDK | so that it becomes Get all platforms, languages, language packs | Source Code tarballs and SDK | Third-party and portable versions and to link the additional text to http://www.openoffice.org/**porting/http://www.openoffice.org/porting/ so that people are correctly informed. This also ensures that when/if we have other portable versions available nothing needs to be changed. To have a visible impression see here: http://ooo-site.staging.**apache.org/download/test/**index.htmlhttp://ooo-site.staging.apache.org/download/test/index.html +1, is portings the right word ? my dictionary suggest ports, but I am no native speaker. Hm, my favorite online dictionary says portings. ;-) Let's see what our native speakers will say. ports is more usual in a software context. But portable is ambiguous, since it means two things: 1) capable of being ported to multiple platforms. 2) something you can carry. Since we offer portable code, ports of the binaries and a portable version, it is hard to avoid confusion here ;-) The link says: Portable USB version and other third-party portings I think Third-party ports including a portable USB version is better US English. and the title: Get Apache OpenOffice as portable USB version or choose from other third-party portings Get third-party ports of Apache OpenOffice including a portable USB version. I want to put the portable thing first as it seems to be the more important info. So, how to do it in better English? Link: Portable USB versions and third-party ports. Title: Get Apache OpenOffice software packaged as portable USB versions and third-party ports. Thanks, I've corrected the text. This little change is now also live. Marcus Shouldn't this be enough to make it clear? Or is it better when I replace Portable USB version with Portable USB App? If we say App then users will be thinking App Store. OK Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Portable version (X-ApacheOpenOffice by winPenPack) updated
2013/7/31 Marcus (OOo) marcus.m...@wtnet.de Am 07/28/2013 10:18 PM, schrieb Marcus (OOo): Am 07/28/2013 09:55 PM, schrieb Dave Fisher: On Jul 28, 2013, at 11:21 AM, Marcus (OOo) wrote: Am 07/28/2013 06:28 PM, schrieb Dave Fisher: On Jul 28, 2013, at 5:46 AM, Marcus (OOo) wrote: Am 07/28/2013 02:18 PM, schrieb Rob Weir: On Sun, Jul 28, 2013 at 8:12 AM, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/28/2013 01:56 PM, schrieb janI: On 28 July 2013 13:47, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/28/2013 12:37 PM, schrieb Andrea Pescetti: On 24/07/2013 Hagar Delest wrote: Huge thanks for such reactivity indeed. But a lot of people are missing it due to the portable version being too hidden in our download infrastructure. What's the best solution to ensure that: 1) Users can actually find the portable version and 2) Users are correctly informed that this is a third-party port? My proposal (subject to lazy consensus or discussion here) would be to modify http://www.openoffice.org/download/http://www.openoffice.org/**download/ http://www.**openoffice.org/download/http://www.openoffice.org/download/ as follows: add it to the line that says Get all platforms, languages, language packs | Source Code tarballs and SDK | so that it becomes Get all platforms, languages, language packs | Source Code tarballs and SDK | Third-party and portable versions and to link the additional text to http://www.openoffice.org/porting/http://www.openoffice.org/**porting/ http://www.**openoffice.org/porting/http://www.openoffice.org/porting/ so that people are correctly informed. This also ensures that when/if we have other portable versions available nothing needs to be changed. To have a visible impression see here: http://ooo-site.staging.**apac**he.org/download/test/**index.** html http://apache.org/download/test/**index.html http://ooo-site.staging.**apache.org/download/test/**index.htmlhttp://ooo-site.staging.apache.org/download/test/index.html +1, is portings the right word ? my dictionary suggest ports, but I am no native speaker. Hm, my favorite online dictionary says portings. ;-) Let's see what our native speakers will say. ports is more usual in a software context. But portable is ambiguous, since it means two things: 1) capable of being ported to multiple platforms. 2) something you can carry. Since we offer portable code, ports of the binaries and a portable version, it is hard to avoid confusion here ;-) The link says: Portable USB version and other third-party portings I think Third-party ports including a portable USB version is better US English. and the title: Get Apache OpenOffice as portable USB version or choose from other third-party portings Get third-party ports of Apache OpenOffice including a portable USB version. I want to put the portable thing first as it seems to be the more important info. So, how to do it in better English? Link: Portable USB versions and third-party ports. Title: Get Apache OpenOffice software packaged as portable USB versions and third-party ports. Thanks, I've corrected the text. This little change is now also live. Looks nice! I've tried to implement this on the ES download site but almost break the page... I'm not on good relations with html (it's all OK, in fact I ended correcting a typo...). I'll look at this again later. Regards Ricardo Marcus Shouldn't this be enough to make it clear? Or is it better when I replace Portable USB version with Portable USB App? If we say App then users will be thinking App Store. OK Marcus --**--**- To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.orgdev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [REVIEW] draft blog.
Am 30.07.13 23:59, schrieb janI: Hi A while ago we discussed to get more bloggers. Since I have 1 years birthday in a couple of days, I have made a blog. I am not a native speaker, so I assume there are some mistakes in there, feel free to correct them. But more importantly, is this a post we as community would like to make public ? https://blogs.apache.org/preview/OOo/?previewEntry=developer_in_aoo_1year_celebration Please be gentle this is my first blog. I realy, realy, realy like this blog. Thank you, all of you, for working together. rgds jan I. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [PROPOSAL] New other.html for all possible download links
On Jul 30, 2013, at 3:43 PM, Marcus (OOo) wrote: Am 07/30/2013 12:25 AM, schrieb Kay Schenk: On Mon, Jul 29, 2013 at 3:21 PM, janIj...@apache.org wrote: On 30 July 2013 00:16, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/29/2013 10:39 PM, schrieb sebb: On 29 July 2013 21:12, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/29/2013 09:45 PM, schrieb sebb: On 29 July 2013 19:27, Marcus (OOo)marcus.m...@wtnet.dewrote: Am 07/26/2013 11:10 PM, schrieb Marcus (OOo): Am 07/26/2013 10:44 PM, schrieb Andrea Pescetti: On 25/07/2013 Marcus (OOo) wrote: I've created a new webpage to offer all possible download links for a release version: http://ooo-site.staging.**apache.org/download/test/** other_tables.html http://ooo-site.staging.apache.org/download/test/other_tables.html This is really nice, looking forward to seeing it online! see below It's especially important to have a link to checksums for those who want a static reference to it or want to verify a package on a different system than the one used for downloading. That was one intension, yes. - all possible downloads for a respective language and OS in a single place I foresee another interesting way to use that page, i.e., getting more localization volunteers. Let's get this version online first, but maybe we could then add another table with something like The following languages are released only as source code:, and then a list of each of the 90+ remaining languages with the link to help us release it (in most cases, it will be a link to http://openoffice.apache.org/** translate.htmlhttp://openoffice.apache.org/translate.html but in some cases it might be different). Good idea. However, I think I've to add more additions than one can thought. But this is no obstacle. @Andrea: I've already considered your smaller font size wish for the checksum links. Thanks, looks great. Thanks. :-) Even when I've missed to state it from the beginning but I expect to use lazy consensus here. If there are no objections I plan to make it Live at ~Sunday evening Hamburg time. As I haven't seen any objections I'll create the new other.html in a the next time. Sorry, but I find the page hard to use. Most people will not need any language packs, so why clutter the table with them? Also if a user does want to add multiple language packs, it's hard work finding them amongst all the full installations. I think it would be a lot clearer for the page to be laid out something like the following: This was the old system and the goal was to integrate all files that belong to a specific language and platform. I'm not sure that goal is particularly useful to the end-user. If it's hard to read due to a small font size, this could be changed. It's not the font size. Otherwise I don't thing that it's too confusing. Well, you are a developer working on OOo. Only for the website, not for the source code. But maybe this is no longer relevant as I do this already for years. I am trying to look at it as a non-developer who wants to download the software. [ cut here ] --- ... [ cut here ] --- If it is possible to provide a dynamic page, then it might be nice to determine the platform first (user selected; perhaps with auto-detected default), and then use the platform to display only the installation sets and language packs for that platform. The dynamic thing is not to continue the data guessing from the main download webpage but to simplify the modification for new releases. The other.html is a kind of fallback when: a) the user is not able to use the green box on the previous main download webpage. b) or when he is searching for a build different from the browser's language / platform. AFAICT it's also used when the user wants to add a new language, in which case they already have the base installation. Yes, and there are maybe some more possibilities. As we don't know the reason(s) for a) there shouldn't be any limitations to give the user the full control to find what he needs. Yes, but that's not relevant to the issue of the page design. And if b) it will help him as well. Which is where the page design is very important. The difference of full installations and language packs is described directly above the table by your suggestion. Yes, but I'm afraid I don't find it easy to read. There's quite a lot of information there which is not particularly relevant to the end user. Also the most common use case - downloading a single base installation and no languag packs - is not actually described. If you think that the text can be better, then please tell me. Based on Apache's famous slogan: Patches are welcome. :-)
Re: [PROPOSAL] New other.html for all possible download links
On 31 July 2013 01:41, Dave Fisher dave2w...@comcast.net wrote: On Jul 30, 2013, at 3:43 PM, Marcus (OOo) wrote: Am 07/30/2013 12:25 AM, schrieb Kay Schenk: On Mon, Jul 29, 2013 at 3:21 PM, janIj...@apache.org wrote: On 30 July 2013 00:16, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/29/2013 10:39 PM, schrieb sebb: On 29 July 2013 21:12, Marcus (OOo)marcus.m...@wtnet.de wrote: Am 07/29/2013 09:45 PM, schrieb sebb: On 29 July 2013 19:27, Marcus (OOo)marcus.m...@wtnet.dewrote: Am 07/26/2013 11:10 PM, schrieb Marcus (OOo): Am 07/26/2013 10:44 PM, schrieb Andrea Pescetti: On 25/07/2013 Marcus (OOo) wrote: I've created a new webpage to offer all possible download links for a release version: http://ooo-site.staging.**apache.org/download/test/** other_tables.html http://ooo-site.staging.apache.org/download/test/other_tables.html This is really nice, looking forward to seeing it online! see below It's especially important to have a link to checksums for those who want a static reference to it or want to verify a package on a different system than the one used for downloading. That was one intension, yes. - all possible downloads for a respective language and OS in a single place I foresee another interesting way to use that page, i.e., getting more localization volunteers. Let's get this version online first, but maybe we could then add another table with something like The following languages are released only as source code:, and then a list of each of the 90+ remaining languages with the link to help us release it (in most cases, it will be a link to http://openoffice.apache.org/** translate.htmlhttp://openoffice.apache.org/translate.html but in some cases it might be different). Good idea. However, I think I've to add more additions than one can thought. But this is no obstacle. @Andrea: I've already considered your smaller font size wish for the checksum links. Thanks, looks great. Thanks. :-) Even when I've missed to state it from the beginning but I expect to use lazy consensus here. If there are no objections I plan to make it Live at ~Sunday evening Hamburg time. As I haven't seen any objections I'll create the new other.html in a the next time. Sorry, but I find the page hard to use. Most people will not need any language packs, so why clutter the table with them? Also if a user does want to add multiple language packs, it's hard work finding them amongst all the full installations. I think it would be a lot clearer for the page to be laid out something like the following: This was the old system and the goal was to integrate all files that belong to a specific language and platform. I'm not sure that goal is particularly useful to the end-user. If it's hard to read due to a small font size, this could be changed. It's not the font size. Otherwise I don't thing that it's too confusing. Well, you are a developer working on OOo. Only for the website, not for the source code. But maybe this is no longer relevant as I do this already for years. I am trying to look at it as a non-developer who wants to download the software. [ cut here ] --- ... [ cut here ] --- If it is possible to provide a dynamic page, then it might be nice to determine the platform first (user selected; perhaps with auto-detected default), and then use the platform to display only the installation sets and language packs for that platform. The dynamic thing is not to continue the data guessing from the main download webpage but to simplify the modification for new releases. The other.html is a kind of fallback when: a) the user is not able to use the green box on the previous main download webpage. b) or when he is searching for a build different from the browser's language / platform. AFAICT it's also used when the user wants to add a new language, in which case they already have the base installation. Yes, and there are maybe some more possibilities. As we don't know the reason(s) for a) there shouldn't be any limitations to give the user the full control to find what he needs. Yes, but that's not relevant to the issue of the page design. And if b) it will help him as well. Which is where the page design is very important. The difference of full installations and language packs is described directly above the table by your suggestion. Yes, but I'm afraid I don't find it easy to read. There's quite a lot of information there which is not particularly relevant to the end user. Also the most common use case - downloading a single base installation and no languag packs - is not actually described. If you think that the text can be better, then please tell me. Based on Apache's famous slogan: Patches are welcome. :-) That would avoid problems with
Solaris builds
Happy AOO 4.0 release! But we don't have AOO 4.0 Solaris builds, do we? AOO 4.0 is buildable on Solaris, right? Should we get a volunteer who can build AOO 4.0 on Solaris? Some Japanese Solaris users are asking for AOO 4.0 Solaris build. Thanks, khirano -- khir...@apache.org Apache OpenOffice http://openoffice.apache.org
New OpenOffice volunteer
My name is Edward and I'm from the bay area in California. I'm a university student in my second year studying computer science. I use OpenOffice and I like it. Contributing to this project would improve my coding skills as well as making the project better. I've never worked on an open source project before and was wondering if this is a good first project to contribute to. I realize that the scope of the project is immense, but because there are so many people working on it, I'll get a lot of help too. I'm free most nights during the summer and I figured this would be quite productive for me. Thanks for your time. -Ed
CMIS Workbench problem
Hello,
I have created a new folder Inside the My_Folder-0-0 in the local immemory
repository named moved1 programmatically.
Code:
MapString,String newFolderProps = new HashMapString, String();
newFolderProps.put(PropertyIds.NAME, name);
newFolderProps.put(PropertyIds.OBJECT_TYPE_ID,
ObjectType.FOLDER_BASETYPE_ID);
try
{
getFolder().createFolder(newFolderProps);
return true;
}
catch(CmisBaseException e)
{
return false;
}
Here, name variable is moved1[image: Inline image 1]
This is the screenshot after creation of folder.
Now, when I try to getObjectbyPath from the session:
using: session.getObjectbyPath(/My_Folder-0-0/moved1) I'm getting a
CMisObjectNotFOundException.
the exception caught has a message containing
/My_FOlder-0-0/My_FOlder-0-1 not found.
When I open the moved1 folder from the workbench, [image: Inline image 2]
U can clearly see that there is a conflict in the paths in the two places.
In the address bar, it shows a different path and in the properties bar it
shows the right path.
WHy is it so?
When I try to open /My_Folder-0-0/moved1 why is it trying to open
/My_FOlder-0-0/My_Dolder-0-1 ?
Is this a bug in opencmis?
--
Rajath S,
M.Sc(Hons.) Physics,
Birla Institute of Technology and Science - Pilani,
Pilani
