Re: [RELEASE]: new snapshot and final integration of language updates
2013/9/6 Jürgen Schmidt jogischm...@gmail.com Hi, we are currently uploading a new snapshot build based on the SNAPSHOT tag revision 1520285 (corresponding rev. on AOO401 branch 1520244). The upload is ongoing and takes some time. The wiki page reflects the new build and if a link is not yet working, please try again later. This snapshot includes additional languages Serbian Cyrillic and Vietnamese and further lang updates. Vietnamese is currently not available on Windows due to build problems. For creating the download package we have to use the unicode version of nsis which have support for Vietnamese. But there is some more work necessary and I won't be able investigate in this problem for this snapshot. Easy and fast switch to the unicode version doesn't work. Sorry but Vietnamese is on risk. For details please check http://people.apache.org/~jsc/developer-snapshots/snapshot/snapshot_rev1520244.htm Details of the former snapshot can be found under http://people.apache.org/~jsc/developer-snapshots/snapshot/snapshot_rev1518667.htm My plan is to finally update the languages on Monday, that means an indirect extension of the translation deadline until Sunday Sep 7th. I plan also to integrate further bug fixes until Wednesday 11th. Please work with the snapshots and report issues asap that we can take potential problems into account. With AOO 4.1 we will shift to a beta release cycle but not for the 4.0.1. There is a small problem with the md5 and sha256 files for Linux builds that makes the -c parameter fail: instead of listing the file name there is a path, for example check-sume-code /tmp/snapshots/Apache_OpenOffice_4.0.1_Linux_x86-64_install-rpm_es.tar.gz instead of just check-sume-code Apache_OpenOffice_4.0.1_Linux_x86-64_install-rpm_es.tar.gz Win and Mac files are OK. Regards Ricardo Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Wrong vendor on last dev build
Under Help → About OpenOffice it seems that the build system name is used as vendor: AOO401m3(Build:9712) - Rev. 1520285 2013-09-05 14:04 - Linux x86_64 Copyright © 2013 aoo_centos5_64. Este producto fue creado por aoo_centos5_64, basado en Apache OpenOffice Regards Ricardo
Problem with PayPal donations to the Apache Software Foundation
To the Apache fundraisers: a user (see below for context) reported a problem with PayPal donations to the Apache Software Foundation account, used for Apache OpenOffice donations. Indeed the button at http://www.apache.org/foundation/contributing.html#Paypal leads to the following error message: --- Apache Software Foundation Your purchase couldn't be completed This recipient is currently unable to receive money. Your purchase couldn't be completed There's a problem with the merchant's PayPal account. Please try again later. --- Can this be analyzed/fixed? Thanks, Andrea. On 06/09/2013 Andrea Pescetti wrote: Bill LLD wrote: I tried to donate via PayPal. It says there's something wrong with the recipient's (your) PayPal account. Thanks for contacting us (and for the intention to donate!). To allow us to investigate this, could you provide the address of the page where you clicked the Paypal link/button? Regards, Andrea. - 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: requirements for vm-admins of forum/translate/wiki
On 6 September 2013 19:49, Rob Weir robw...@apache.org wrote: On Fri, Sep 6, 2013 at 12:14 PM, janI j...@apache.org wrote: On 6 September 2013 15:27, Dave Fisher dave2w...@comcast.net wrote: On Sep 4, 2013, at 11:37 PM, Jürgen Schmidt wrote: On 9/4/13 10:17 PM, Rob Weir wrote: On Wed, Sep 4, 2013 at 12:36 PM, janI j...@apache.org wrote: Hi. We have had some longer discussions on different ML/IRC about how a vm-admin should behave and which level of service we expect for our servers. We need new admins, so this is also a request for anyone interested to chip in. We have had some unfortunate incidents on all 3 vm, of different nature, which made me question if we as a community: I assume we have vms for Forums and for Wiki. But what is the 3rd one? a) want servers, that are cared for professionally or by happening. b) want to (are capable to) maintain the servers ourself. c) are prepared to support a change that make a), b) possible. I assume we want well-maintained servers that help us get our project-related tasks done, and also help serve our users. +1 that is the main goal, a working reliable infra structure that helps to run our project. In the past, before you got involved, we were not very proactive. It seemed like we just waited for something to break, and then tried to fix it. Exactly and doing it proactive is much better and in the end probably less work. I assume another goal is that we have several people helping with the admin, to share the work, avoid burnouts, cover for vacation, etc. And that is a very important goal, we need an environment where we can at any time step in if somebody is not available. I now very well in the same way as Jan how it is to be a bottleneck. Well it#s true for many others of us in different areas. But if the servers are not running or the services not available more people are affected faster I have formulated some thoughts on how admins could work, but in general I believe we should convince infra to take over the vm responsibility and keep our well functioning forum/wiki admins. We have a vm-team in place, that was created with the purpose of not having a single person as admin. I my opinion the team have not lived up to that purpose but I am still thankful for the help I have received. Remarks the ideas below are my personal thought, which I have used during the time where I maintained the servers: === The server should at all times be maintained with the following priority: 1) security (the backside of being popular is to have the attention of people who want to gain merit by breaking our servers) 2) stability (we have limited cpu/ram/disk so we must optimize) 3) add user wishes (we already have stable systems, 1,2 are far more important that enhancing the systems). and maybe 3b) Try to evolve systems so users can implement their own wishes, in a way compatible with 1) and 2). For example, if routine logos and footers are synched to resources in the project's SVN tree, then any committer can update things. I really like this idea. I am impressed, is this real serious ? Think about all the fuzz we have had on several MLs because one committer successfully convinced a vm-admin to change our logo, and the suggestion is to make that automatic. Any committer who wants a change, just do a svn commit, is that really wanted ? It also makes it possible for any committer to fix a problem if one occurs. A couple of questions to that: Committer X want extension translate, and do a svn commit the config is updated, but does not work because of other dependencies, who clears up the work ? for sure THAT is not a vm-admin task. Same as when a committer checks in code that breaks the build. Committer X changes the logo, but doing a svn commit, Committer Y dont like it and does a svn commit, where are our users in this process or our decision process ? Same as when a committer checks in code that someone doesn't like. We have a community-based process that handles these things already. Your proposal doesn't really avoid these issues. It handles it by having an admin judge the will of the community. yes like all other vms I know. 3b) is a sure way to scare any prof. SA away, thats pure anarchy. In the good sense of the word anarchy, yes. Note: I wouldn't do this for config files and core system files. But why should the logo or banner or footer of the forums or the wiki be any harder for a committer to edit than the same content of our website? Maybe because the CMS are laid out for that our apps are not. If you change logo to e.g. a different size you will also need to edit - css - php (for mwiki) - update symlinks (for php2bb) and you
Re: Introduction.
Forwarding to Gunwant who is not subscribed to the list. Andrea On 04/09/2013 Alexandro Colorado wrote: Welcom Gunwant please read ou getting involved website as well as the introductory modules we have documented for you to choose which project suits you better. Then proceed to sign in to the mailing list that best suit the category and join the team. On Wed, Sep 4, 2013 at 12:25 AM, Gunwant Khairnargunwan...@gmail.comwrote: Hello My name id Gunwant Khairnar, from pune, India. And I am working as a Jr system Administrator(Linux). I wish to contribute in this openoffice project. Thanks Gunwant. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Authentication Example
Hello, I want an example code or code snippet or wiki link for using InteractionHandler to get authentication details like user credentials for my ucp. Please provide me an example. -- Rajath S, M.Sc(Hons.) Physics, B.E.(Hons.) Computer Science Birla Institute of Technology and Science - Pilani, Pilani
Re: permission problem with Windows SDK from snapshot 4.0.1
Hi Regina, On 9/6/2013 9:03 PM, Regina Henschel wrote: when I click on Windows version of SDK in https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds I get an error Forbidden You don't have permission to access /~jsc/developer-snapshots/snapshot/windows/Apache_OpenOffice-SDK_4.0.1_Win_x86_install_en-US.exe on this server. that usually happens, if the access controls (ACL) are not set to allow everyone to do everything with it. :) If that is the cause for your problem, then you can fix this as an Administrator on your Windows machine using the command line tool cacl (change access control list). In your example, and assuming you are running a German version of Windows, you might want to try the following command in a command line window: cacls /~jsc/developer-snapshots/snapshot/windows/Apache_OpenOffice-SDK_4.0.1_Win_x86_install_en-US.exe /g jeder:f Altghough it looks a little bit strange to see /~jsc/ on a Window machine. Hope that helps one way or the other, ---rony P.S.: On a non-German Windows machine you need to change jeder to your local name for everyone.
Re: permission problem with Windows SDK from snapshot 4.0.1
Ah, on second reading I see that it is not a Windows installation problem you were referring to, but the access rights on the web server. Sorry for my noice, probably need still more sleep ... ;) ---rony On 9/7/2013 1:14 PM, Rony G. Flatscher (Apache) wrote: Hi Regina, On 9/6/2013 9:03 PM, Regina Henschel wrote: when I click on Windows version of SDK in https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds I get an error Forbidden You don't have permission to access /~jsc/developer-snapshots/snapshot/windows/Apache_OpenOffice-SDK_4.0.1_Win_x86_install_en-US.exe on this server. that usually happens, if the access controls (ACL) are not set to allow everyone to do everything with it. :) If that is the cause for your problem, then you can fix this as an Administrator on your Windows machine using the command line tool cacl (change access control list). In your example, and assuming you are running a German version of Windows, you might want to try the following command in a command line window: cacls /~jsc/developer-snapshots/snapshot/windows/Apache_OpenOffice-SDK_4.0.1_Win_x86_install_en-US.exe /g jeder:f Altghough it looks a little bit strange to see /~jsc/ on a Window machine. Hope that helps one way or the other, ---rony P.S.: On a non-German Windows machine you need to change jeder to your local name for everyone. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Bad links to API module pages
To whom it may concern: On the following page: http://www.openoffice.org/api/modules.html, none of the links to the Modules in the API Project work, but produce a 404 error. Ron Blanshine*:** *
Bad link to SDK download.
To whom it may concern: On the following page, http://www.openoffice.org/api/SDK/, The link to Download the SDK, produces a 404 error. Ron Blanshine - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Bugzilla Index
On 30/08/2013 Rory O'Farrell wrote: Is the Bugzilla index up to date? I've tried a few searches for words in 123129 subject with no success. It would find the 123129 issue, given the number, but not using any of the subject words. acknak (on en-Forum) found similarly. Note that the default search options ignore RESOLVED issues. If in that moment the issue was marked as RESOLVED (as it is now), to see it you need to open https://issues.apache.org/ooo/query.cgi then select (CTRL-Click) all values for Status and Resolution, and the issue will appear in the search results. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wrong vendor on last dev build
On Sat, Sep 7, 2013 at 1:39 AM, Ricardo Berlasso rgb.m...@gmail.com wrote: Under Help → About OpenOffice it seems that the build system name is used as vendor: AOO401m3(Build:9712) - Rev. 1520285 2013-09-05 14:04 - Linux x86_64 Copyright © 2013 aoo_centos5_64. Este producto fue creado por aoo_centos5_64, basado en Apache OpenOffice Regards Ricardo I saw this too on the last couple of Linux builds and was going to ask about it. -- - MzK Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities. Truth isn't. -- Following the Equator, Mark Twain
Reporting a problem with the OpenOffice website
excuse me i will write in french bonjour je viens de télécharger votre logiciel open office supposé gratuit sur le site: http://fr.softwis.com/ on m'a demandé d'envoyé un sms pour recevoir le code d'activation et je viens de me rendre compte qu'ils m'ont fait payer 4.50€ pour le sms. Il ont revendu votre logiciel ! Vous pouvez me répondre sur mon adresse mail: haykel.khal...@gmail.com cordialement -- Haykel BEN KHALIFA
Re: Reporting a problem with the OpenOffice website
Bonjour, Ceci est une liste en anglais, merci de ne pas utiliser le français. Vous n'avez pas télécharger la version officielle. La bonne version se trouve ici : http://www.openoffice.org/download/ User redirected to the official download page. The site does not even propose the latest version. Hagar Le 07/09/2013 18:17, HAYKEL KHALIFA a écrit : excuse me i will write in french bonjour je viens de télécharger votre logiciel open office supposé gratuit sur le site: http://fr.softwis.com/ on m'a demandé d'envoyé un sms pour recevoir le code d'activation et je viens de me rendre compte qu'ils m'ont fait payer 4.50€ pour le sms. Il ont revendu votre logiciel ! Vous pouvez me répondre sur mon adresse mail: haykel.khal...@gmail.com cordialement - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Wiki logo update
On Sep 7, 2013, at 4:46 AM, Andrea Pescetti wrote: On 23/08/2013 janI wrote: On 22 August 2013 23:51, Alexandro Coloradoj...@oooes.org wrote: just get a final confirmation if there a 'go' on the Wiki logo update which was reverted due to a regression by infra when setting the SVN. Infra did not revert anything. As you very well know the revert on wiki was done by me, because a) the logos was installed in a wrong place, that made updates very difficult b) the standard procedure to make a backup/commit was not followed All something that had nothing to do with consensus, but how admins work on the vm. I'm coming late to this part of the discussion, but this was definitely the right thing to do. We care about a professional-level maintenance of our Infrastructure (and actually Apache Infra demands and enforces it). Everyone can make mistakes, but when we can correct them we must do so. And this is the technical part. I agree. My default position is that I support Jan's sysadmin work. For me silence is assent. I'll make it clear here. I respects these concerns and feel reel consensus is much more important than a technicality, even if it takes 400+ hours. As vm-admin, I will not install a new logo and/or change html/css before I see a broad acceptance. Other vm-admins might feel different. And now coming to the community part: this was very right too. An administrator must check consensus before doing changes. And consensus reaching may well take weeks (the larger and simpler the issue -and this is large since it affects several sites and simple since everybody can have a say- the longer the discussion). The important thing is that eventually we get things done! Hagar restarted the constructive discussion at http://forum.openoffice.org/en/forum/viewtopic.php?f=50t=63523 recently and I hope we can move forward there. When the decision is made please bring it back here and flag it with a [CONSENSUS] subject tag. We can then test that here and then proceed after the consensus is proven. Either way we should be vetting the new html, it's look, etc. The sysadmin team is then responsible for implementation on MWiki and forums and communication about that to the appropriate lists. The admin team is responsible for maintaining these servers and needs to manage all configuration changes in a manner that any server can be rebuilt from scratch using private svn archives including a runbook and data backups. This has to be co-ordinated. A change that is apparently simple and seemingly 10 minutes is not. Sysadmins are correct to insist on process here. Volunteer sysadmins even more so. Don't expect them to be happy if you make them volunteer when they have real plans and other activities. But, Alexandro seems to want to discuss a full branding change to all AOO assets if that is so then that decision must be made on this list, is much larger and it requires a full proposal with willingness to discuss everyone's ideas. In that case the co-ordination is large and complete consensus followed by a conversion plan is required. - Sysadmin team MWiki Forums - Committers Websites - Infra / bz admins Bugzilla - PMC / Infra CWiki Blogs - Sourceforge Extensions Templates Regards, Dave Regards, Andrea. - 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: requirements for vm-admins of forum/translate/wiki
On Sep 7, 2013, at 2:24 AM, janI wrote: On 6 September 2013 19:49, Rob Weir robw...@apache.org wrote: On Fri, Sep 6, 2013 at 12:14 PM, janI j...@apache.org wrote: On 6 September 2013 15:27, Dave Fisher dave2w...@comcast.net wrote: On Sep 4, 2013, at 11:37 PM, Jürgen Schmidt wrote: On 9/4/13 10:17 PM, Rob Weir wrote: On Wed, Sep 4, 2013 at 12:36 PM, janI j...@apache.org wrote: Hi. We have had some longer discussions on different ML/IRC about how a vm-admin should behave and which level of service we expect for our servers. We need new admins, so this is also a request for anyone interested to chip in. We have had some unfortunate incidents on all 3 vm, of different nature, which made me question if we as a community: I assume we have vms for Forums and for Wiki. But what is the 3rd one? a) want servers, that are cared for professionally or by happening. b) want to (are capable to) maintain the servers ourself. c) are prepared to support a change that make a), b) possible. I assume we want well-maintained servers that help us get our project-related tasks done, and also help serve our users. +1 that is the main goal, a working reliable infra structure that helps to run our project. In the past, before you got involved, we were not very proactive. It seemed like we just waited for something to break, and then tried to fix it. Exactly and doing it proactive is much better and in the end probably less work. I assume another goal is that we have several people helping with the admin, to share the work, avoid burnouts, cover for vacation, etc. And that is a very important goal, we need an environment where we can at any time step in if somebody is not available. I now very well in the same way as Jan how it is to be a bottleneck. Well it#s true for many others of us in different areas. But if the servers are not running or the services not available more people are affected faster I have formulated some thoughts on how admins could work, but in general I believe we should convince infra to take over the vm responsibility and keep our well functioning forum/wiki admins. We have a vm-team in place, that was created with the purpose of not having a single person as admin. I my opinion the team have not lived up to that purpose but I am still thankful for the help I have received. Remarks the ideas below are my personal thought, which I have used during the time where I maintained the servers: === The server should at all times be maintained with the following priority: 1) security (the backside of being popular is to have the attention of people who want to gain merit by breaking our servers) 2) stability (we have limited cpu/ram/disk so we must optimize) 3) add user wishes (we already have stable systems, 1,2 are far more important that enhancing the systems). and maybe 3b) Try to evolve systems so users can implement their own wishes, in a way compatible with 1) and 2). For example, if routine logos and footers are synched to resources in the project's SVN tree, then any committer can update things. I really like this idea. I am impressed, is this real serious ? Think about all the fuzz we have had on several MLs because one committer successfully convinced a vm-admin to change our logo, and the suggestion is to make that automatic. Any committer who wants a change, just do a svn commit, is that really wanted ? It also makes it possible for any committer to fix a problem if one occurs. A couple of questions to that: Committer X want extension translate, and do a svn commit the config is updated, but does not work because of other dependencies, who clears up the work ? for sure THAT is not a vm-admin task. Same as when a committer checks in code that breaks the build. Committer X changes the logo, but doing a svn commit, Committer Y dont like it and does a svn commit, where are our users in this process or our decision process ? Same as when a committer checks in code that someone doesn't like. We have a community-based process that handles these things already. Your proposal doesn't really avoid these issues. It handles it by having an admin judge the will of the community. yes like all other vms I know. 3b) is a sure way to scare any prof. SA away, thats pure anarchy. In the good sense of the word anarchy, yes. Note: I wouldn't do this for config files and core system files. But why should the logo or banner or footer of the forums or the wiki be any harder for a committer to edit than the same content of our website? Maybe because the CMS are laid out for that our apps are not. If you change logo to e.g. a different size you will also need to edit - css - php (for mwiki) - update symlinks (for php2bb) and you might also need to change in the httpd caching scheme, if the new logo has a
Re: Another 4.0 review, in ComputerBild (German)
On 01/09/2013 Hagar Delest wrote: Le 17/08/2013 14:32, Rob Weir a écrit : http://www.openoffice.org/product/reviews.html This is the original reviews page. Someone (maybe me?) updated it for 3.4. If you want to add some 4.0 reviews, that would be great. I've also listed and updated the coverage here: http://forum.openoffice.org/en/forum/viewtopic.php?f=5t=63026p=279440#p279440 The wiki page should be updated I think. Assuming that by wiki page you actually mean http://www.openoffice.org/product/reviews.html I ported some French links that were missing. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: requirements for vm-admins of forum/translate/wiki
On Sep 7, 2013 10:28 PM, Dave Fisher dave2w...@comcast.net wrote: On Sep 7, 2013, at 2:24 AM, janI wrote: On 6 September 2013 19:49, Rob Weir robw...@apache.org wrote: On Fri, Sep 6, 2013 at 12:14 PM, janI j...@apache.org wrote: On 6 September 2013 15:27, Dave Fisher dave2w...@comcast.net wrote: On Sep 4, 2013, at 11:37 PM, Jürgen Schmidt wrote: On 9/4/13 10:17 PM, Rob Weir wrote: On Wed, Sep 4, 2013 at 12:36 PM, janI j...@apache.org wrote: Hi. We have had some longer discussions on different ML/IRC about how a vm-admin should behave and which level of service we expect for our servers. We need new admins, so this is also a request for anyone interested to chip in. We have had some unfortunate incidents on all 3 vm, of different nature, which made me question if we as a community: I assume we have vms for Forums and for Wiki. But what is the 3rd one? a) want servers, that are cared for professionally or by happening. b) want to (are capable to) maintain the servers ourself. c) are prepared to support a change that make a), b) possible. I assume we want well-maintained servers that help us get our project-related tasks done, and also help serve our users. +1 that is the main goal, a working reliable infra structure that helps to run our project. In the past, before you got involved, we were not very proactive. It seemed like we just waited for something to break, and then tried to fix it. Exactly and doing it proactive is much better and in the end probably less work. I assume another goal is that we have several people helping with the admin, to share the work, avoid burnouts, cover for vacation, etc. And that is a very important goal, we need an environment where we can at any time step in if somebody is not available. I now very well in the same way as Jan how it is to be a bottleneck. Well it#s true for many others of us in different areas. But if the servers are not running or the services not available more people are affected faster I have formulated some thoughts on how admins could work, but in general I believe we should convince infra to take over the vm responsibility and keep our well functioning forum/wiki admins. We have a vm-team in place, that was created with the purpose of not having a single person as admin. I my opinion the team have not lived up to that purpose but I am still thankful for the help I have received. Remarks the ideas below are my personal thought, which I have used during the time where I maintained the servers: === The server should at all times be maintained with the following priority: 1) security (the backside of being popular is to have the attention of people who want to gain merit by breaking our servers) 2) stability (we have limited cpu/ram/disk so we must optimize) 3) add user wishes (we already have stable systems, 1,2 are far more important that enhancing the systems). and maybe 3b) Try to evolve systems so users can implement their own wishes, in a way compatible with 1) and 2). For example, if routine logos and footers are synched to resources in the project's SVN tree, then any committer can update things. I really like this idea. I am impressed, is this real serious ? Think about all the fuzz we have had on several MLs because one committer successfully convinced a vm-admin to change our logo, and the suggestion is to make that automatic. Any committer who wants a change, just do a svn commit, is that really wanted ? It also makes it possible for any committer to fix a problem if one occurs. A couple of questions to that: Committer X want extension translate, and do a svn commit the config is updated, but does not work because of other dependencies, who clears up the work ? for sure THAT is not a vm-admin task. Same as when a committer checks in code that breaks the build. Committer X changes the logo, but doing a svn commit, Committer Y dont like it and does a svn commit, where are our users in this process or our decision process ? Same as when a committer checks in code that someone doesn't like. We have a community-based process that handles these things already. Your proposal doesn't really avoid these issues. It handles it by having an admin judge the will of the community. yes like all other vms I know. 3b) is a sure way to scare any prof. SA away, thats pure anarchy. In the good sense of the word anarchy, yes. Note: I wouldn't do this for config files and core system files. But why should the logo or banner or footer of the forums or the wiki be any harder for a committer to edit than the same content of our website? Maybe because the CMS are laid out for that our apps are not. If you change logo to e.g. a different size you
Starting Introduction to Contributing to Apache OpenOffice Module
Hello, My name is Covert Nelson and I live in Summerville SC. I have been a computer hobbyist since the early 80's. My first computer was a commodore 64 on which I taught myself some very basic machine language coding. I then built my first pc with an 8088 processor. I have built my own systems with just about every new processor targeted at consumers as they became available. I taught myself BASIC and coded some applications I used at my job as a land surveyor. I now have been tasked with creating a database linked to a spread sheet to assist our field crews in collecting data. I have been using OpenOffice for the last 5 or 6 years at home and want to expand my skills with this project. How better to do this than to assist in contributing to the Apache Openoffice community. I just hope I can contribute as much as I learn. -- Covert Nelson My Facebook https://www.facebook.com/covert.nelson
Re: Wiki logo update
On Sat, Sep 7, 2013 at 2:47 PM, Dave Fisher dave2w...@comcast.net wrote: On Sep 7, 2013, at 4:46 AM, Andrea Pescetti wrote: On 23/08/2013 janI wrote: On 22 August 2013 23:51, Alexandro Coloradoj...@oooes.org wrote: just get a final confirmation if there a 'go' on the Wiki logo update which was reverted due to a regression by infra when setting the SVN. Infra did not revert anything. As you very well know the revert on wiki was done by me, because a) the logos was installed in a wrong place, that made updates very difficult b) the standard procedure to make a backup/commit was not followed All something that had nothing to do with consensus, but how admins work on the vm. I'm coming late to this part of the discussion, but this was definitely the right thing to do. We care about a professional-level maintenance of our Infrastructure (and actually Apache Infra demands and enforces it). Everyone can make mistakes, but when we can correct them we must do so. And this is the technical part. I agree. My default position is that I support Jan's sysadmin work. For me silence is assent. I'll make it clear here. I respects these concerns and feel reel consensus is much more important than a technicality, even if it takes 400+ hours. As vm-admin, I will not install a new logo and/or change html/css before I see a broad acceptance. Other vm-admins might feel different. And now coming to the community part: this was very right too. An administrator must check consensus before doing changes. And consensus reaching may well take weeks (the larger and simpler the issue -and this is large since it affects several sites and simple since everybody can have a say- the longer the discussion). The important thing is that eventually we get things done! Hagar restarted the constructive discussion at http://forum.openoffice.org/en/forum/viewtopic.php?f=50t=63523 recently and I hope we can move forward there. That discussion only applies to forum. When the decision is made please bring it back here and flag it with a [CONSENSUS] subject tag. We can then test that here and then proceed after the consensus is proven. There has been 0 comments on the wiki proposal. Is this a consensus? Either way we should be vetting the new html, it's look, etc. The sysadmin team is then responsible for implementation on MWiki and forums and communication about that to the appropriate lists. The admin team is responsible for maintaining these servers and needs to manage all configuration changes in a manner that any server can be rebuilt from scratch using private svn archives including a runbook and data backups. This has to be co-ordinated. A change that is apparently simple and seemingly 10 minutes is not. Sysadmins are correct to insist on process here. Volunteer sysadmins even more so. Don't expect them to be happy if you make them volunteer when they have real plans and other activities. But, Alexandro seems to want to discuss a full branding change to all AOO assets if that is so then that decision must be made on this list, is much larger and it requires a full proposal with willingness to discuss everyone's ideas. There has been no comments on this list for the wiki logo proposal. Which should by default be a Consensus AFAIK, that's the 'lazy' part of the consensus. In that case the co-ordination is large and complete consensus followed by a conversion plan is required. It seems there is no timeline, even if there is no comments, things are not getting done. The process is pretty much broken, since there seems to be no actual consensus process beside waiting which has been done, and still hasn't been applied. - Sysadmin team MWiki Forums - Committers Websites - Infra / bz admins Bugzilla - PMC / Infra CWiki Blogs - Sourceforge Extensions Templates ATM there is only proposed patches for Mwiki, Forum index and Forum logos. Extensions and Templates were already updated on Roberto's design. Blogs logos were somewhat updated without much discussion (AFAIK). Regards, Dave Regards, Andrea. - 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 -- Alexandro Colorado Apache OpenOffice Contributor http://www.openoffice.org
