Re: [NOMINATION REQUEST] Next Chair of AOO Project Management Committee
+1 Marcus, Thanks for volunteering !! Carl On 09/14/2016 02:36 PM, Marcus wrote: I could write much and more but to keep a long story short: I will volunteer to take over the role as next Chair. Planned is a time frame of 1 year. But of course also a bit longer if it fits better for any (time) contraints. I don't want to write here what should be done better or faster or ... as it doesn't make sense because - I'm pretty sure - it will always work out differently. Furthermore, this is not the thread to talk about this. Just one addition: For ASF the Chair role is not to say what to do or where to go. The tasks are in more formal way and well described here [1] and here [2]. So, you shouldn't expect anything else. Of course I'll do the same in the project (or more if my spare time permits) but than as an usual committer. And at the end: If there are any other candidates please speak up now. Then we can start a discussion. Thanks for your attention. [1] http://www.apache.org/dev/pmc.html#chair [2] http://www.apache.org/foundation/how-it-works.html#roles Marcus Am 08/30/2016 10:30 PM, schrieb Dennis E. Hamilton: [BCC to PMC] I am now ready to begin the Chair nomination process. Because of delays, the next change of Chair has moved to October 19. REQUEST FOR NOMINATIONS This message starts the nomination process for the next Chair for the Apache OpenOffice PMC. The term of the next Chair will start on 2016-10-19 and my resignation will be effective on that date. Members of the PMC can nominate themselves, expressing their willingness to serve. You can also place the names of others in nomination. Those individuals must accept the nomination to be considered as eligible. The identification of Nominees will end on Tuesday, 2016-09-13. The nature of subsequent discussion will depend on the number of Nominees. TIMELINE Here's the new timeline that has the replacement be ratified by the October 19, 2016 meeting of the ASF Board: 2016-10-19 ASF Board Meeting - Board rules on the resolution to install the new Chair. 2016-10-12 (latest) Resolution from AOO PMC to accept the new Chair is added to the Agenda for the 2016-10-19 Board Meeting (latest possible date) 2016-10-05 (latst) [RESULT][VOTE] on election of next Chair is reported. 2016-09-28 (latest) [VOTE] on election of next Chair begins. This could be by lazy consensus if there is already a single acceptable candidate. 2016-09-14 [NOMINEE DISCUSSION] process begins formally and any discussion on and among candidates willing to serve takes place. 2016-08-30 [NOMINATIONS] Individuals are recommended or offer themselves, indicate their availability to serve for at least one single-year term, and also have their own questions answered. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:orc...@apache.org] Sent: Sunday, July 31, 2016 20:44 To: dev@openoffice.apache.org Subject: [DISCUSS] Process: Elect Next Chair of AOO Project Management Committee [BCC to PMC] [From the Chair] It is time for the selection of the next chair for the Apache OpenOffice Project Management Committee. INCUMBENT CHAIR I officially began my term on the third Wednesday of September, 2015. My commitment was to serve for one full year and then be replaced. I will complete that one-year term and step down on the third Wednesday of September, 2016. My successor will then be established by the Apache Software Foundation Board. Although I will continue as a member of the Project Management Committee and as a contributor to the Apache OpenOffice project, I am not available to continue as Chair beyond the 2016-09-21 ASF Board Meeting. I am available to assist the incoming Chair in any manner required for successfully transferring duties of the Chair. CHAIR ELECTION Based on previous practice, nomination, discussion, and election periods are held. Here is my proposed time-line, from endgame backwards: 2016-09-21 ASF Board Meeting - Board rules on the resolution to install the new Chair. 2016-09-14 Resolution from AOO PMC to accept the new Chair is added to the Agenda for the 2016-09-21 Board Meeting (latest possible date) 2016-09-07 [RESULT][VOTE] on election of next Chair is reported. 2016-08-31 [VOTE] on election of next Chair begins (with allowance for US Holiday weekend). This could be by lazy consensus if there is already a single acceptable candidate. 2016-08-17 [NOMINEE DISCUSSION] process begins formally and any discussion on and among candidates willing to serve takes place. 2016-08-03 [NOMINATIONS] Individuals are recommended or offer themselves, indicate their availability to serve for at least one single-year term, and also have their own questions answered. This process can be accelerated where it is seen that discussions have quieted and consensus for moving forward is evident. - To unsubscribe, e-mail:
Re: dmake
> On Sep 14, 2016, at 6:40 PM, Jim Jagielskiwrote: > > > epm is required and not under our control. In fact, epm 4.3 is out > and work much better for AOO since it removes the need for the > long-since deprecated PackageMaker app and instead uses the > official pkgbuild stuff. Part of my configure.in changes (to > be submitted to trunk) notices that. > FWIW, this is for MacOS - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: dmake
> On Sep 14, 2016, at 5:28 PM, Andrea Pescettiwrote: > > Jim Jagielski wrote: >> Tarballs are at: >> https://github.com/jimjag/dmake/releases >> My goal was to try to combine all the flavors of dmake into one >> "canonical" version we can use. > > Is there a reason for that? > The only reason I saw was that it was a dependency that we haven't tracked at all (see the req to fix configure.am/in with the correct URL) and was/is easy to lose. There seemed to have been some improvements since 4.12 that also looked like they might have been useful. All in all, have a tarball w/ no real source version control, and a tarball whose location has changed and been lost, up to now, seems like an easy thing to resolve. Hence the repo. > > Our build is designed to succeed based only on resources under control of the > project, namely: the SVN repository; the OOoExtras site; the Extensions site. > Depending on yet another online resource (a personal account on GitHub) seems > an additional issue. > epm is required and not under our control. In fact, epm 4.3 is out and work much better for AOO since it removes the need for the long-since deprecated PackageMaker app and instead uses the official pkgbuild stuff. Part of my configure.in changes (to be submitted to trunk) notices that. Or is this the typical warm and inviting behavior that all "new" AOO contributors are subjected to? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: building on Windows 10 breaks at guistdio.exe
If it can be of any use to understand better the problem, I'm using this configuration: SDK_PATH="D:\Microsoft_SDKs\Windows\v7.0" ./configure --with-frame-home="$SDK_PATH" --with-psdk-home="$SDK_PATH" --with-midl-path="$SDK_PATH/bin" --with-directx-home="D:\Microsoft_DirectX_SDK_June_2010" --with-ant-home="/cygdrive/d/apache-ant/apache-ant-1.9.7" --with-jdk-home="C:\Program Files (x86)\Java\jdk1.8.0_73" --with-csc-path="C:\Windows\Microsoft.NET\Framework\v3.5" --with-dmake-url=" http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2; --with-epm-url="http://www.msweet.org/files/project2/epm-3.7-source.tar.gz; --disable-pch --disable-atl --disable-activex --without-junit On Wed, Sep 14, 2016 at 9:39 PM, John D'Orazio < john.dora...@cappellaniauniroma3.org> wrote: > So I've taken courage thanks also to the work done by Patricia Shanahan on > building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and > I've sorted through the first few obstacles and my build has now been > running for 5-6 hours without any trouble. Until now that is. It just broke > while building "guistdio.exe" in the desktop module. I'm not really seeing > much information that can help me though, can any pick out what the trouble > might be? Here is the last part of the build output: > > Compiling: desktop/test/deployment/active/active_native.cxx > Making:test_deployment_active.lib > Making:module definition file active_native.uno.def > Making:itest_deployment_active_t1.lib > lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P > Microsoft (R) Library Manager Version 9.00.30729.01 > Copyright (C) Microsoft Corporation. All rights reserved. > > -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib > -def:../../../wntmsci12.pro/misc/active_native.uno.def >Creating library ../../../wntmsci12.pro/lib/ > itest_deployment_active_t1.lib and object ../../../wntmsci12.pro/lib/ > itest_deployment_active_t1.exp > Making:active_native.uno.dll > Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 > Copyright (C) Microsoft Corporation. All rights reserved. > > Microsoft (R) Incremental Linker Version 9.00.30729.01 > Copyright (C) Microsoft Corporation. All rights reserved. > > /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE > -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ > wntmsci12.pro/bin/active_native.uno.dll -map:../../../wntmsci12.pro/ > misc/active_native.uno.map ../../../wntmsci12.pro/lib/ > itest_deployment_active_t1.exp ../../../wntmsci12.pro/slo/ > active_native.obj ../../../wntmsci12.pro/slo/active_native.uno_version.obj > icppuhelper.lib icppu.lib isal.lib msvcrt.lib msvcprt.lib uwinapi.lib > kernel32.lib user32.lib oldnames.lib ../../../wntmsci12.pro/misc/ > active_native.uno.res > linking ../../../wntmsci12.pro/bin/active_native.uno.dll.manifest ... > Making:all_test_deployment_active.dpslo > mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/ > /bin/rm -f ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar > /bin/rm -f -r ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip > mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip > mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/META-INF \ > ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/com/sun/star/comp/test/deployment/active_java > cp MANIFEST.MF ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/META-INF/ > cp ../../../wntmsci12.pro/class/com/sun/star/comp/test/ > deployment/active_java/Dispatch.class ../../../wntmsci12.pro/class/ > com/sun/star/comp/test/deployment/active_java/Provider.class ../../../ > wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/ > Services.class \ > ../../../wntmsci12.pro/misc/test_deployment_active/active_ > java.jar-zip/com/sun/star/comp/test/deployment/active_java/ > cd ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip > && zip ../active_java.jar \ > META-INF/MANIFEST.MF com/sun/star/comp/test/ > deployment/active_java/Dispatch.class com/sun/star/comp/test/ > deployment/active_java/Provider.class com/sun/star/comp/test/ > deployment/active_java/Services.class > adding: META-INF/MANIFEST.MF (deflated 9%) > adding: com/sun/star/comp/test/deployment/active_java/Dispatch.class > (deflated 54%) > adding: com/sun/star/comp/test/deployment/active_java/Provider.class > (deflated 52%) > adding: com/sun/star/comp/test/deployment/active_java/Services.class > (deflated 54%) > /bin/rm -f ../../../wntmsci12.pro/misc/active.oxt > /bin/rm -f -r ../../../wntmsci12.pro/misc/test_deployment_active/active. > oxt-zip > mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active. > oxt-zip > mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/active. > oxt-zip/META-INF > sed -e
Re: dmake
Jim Jagielski wrote: Tarballs are at: https://github.com/jimjag/dmake/releases My goal was to try to combine all the flavors of dmake into one "canonical" version we can use. Is there a reason for that? So far it has been enough for us to get a specific dmake tarball from a certain URL specified at build time. We just use that version of dmake, without working on it any further since we have no need for that, unless I'm missing something. Our build is designed to succeed based only on resources under control of the project, namely: the SVN repository; the OOoExtras site; the Extensions site. Depending on yet another online resource (a personal account on GitHub) seems an additional issue. Under the assumption that this new repository is useful, https://github.com/jimjag/dmake/commit/e9edbf3228af898e6832b4346355f1e4c9ed867a should be fixed to include the correct name of the project. But at this time I can't find a good reason for it, except the usual "one new standard to unify them all" joke. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: building on Windows 10 breaks at guistdio.exe
I've never seen this failure before. The only suggestion I can make is to retry. That sometimes fixes failed builds. On 9/14/2016 12:39 PM, John D'Orazio wrote: ... dmake: '../../../wntmsci12.pro/bin/guistdio.exe' removed. 1 module(s): desktop need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making /cygdrive/d/source/aoo-trunk/main/desktop/win32/source/guistdio When you have fixed the errors in that module you can resume the build by running: build --all:desktop Do I perhaps need to enable a verbose output to have more information to go on? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: dmake
Tarballs are at: https://github.com/jimjag/dmake/releases My goal was to try to combine all the flavors of dmake into one "canonical" version we can use. > On Sep 14, 2016, at 3:12 PM, John D'Orazio >wrote: > > I myself just ran into the problem of the missing apache-extras link, I've > used a sourceforge link for my build: > http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2. > Most of the links indicated in your github repo's README are dead links... > I believe a downloadable tarball is useful for the building process, the > sourceforge tarball seems to be working for me so far (it's my first build, > and it's still building, but it's gotten past the initial dmake > installation stage at least). > > On Wed, Sep 14, 2016 at 5:25 PM, Jim Jagielski wrote: > >> Seeing that there is a dependency, still, on dmake, I've gone >> ahead and created >> >>https://github.com/jimjag/dmake >> >> based on what I've been using... Suggestions and patches >> welcome. Hoping we can use this to replace the apche-extras >> links. >> >> It's based on (https://github.com/mohawk2/dmake) >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > > > -- > John R. D'Orazio - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
building on Windows 10 breaks at guistdio.exe
So I've taken courage thanks also to the work done by Patricia Shanahan on building OpenOffice in Windows 7 and Windows 8.1. I'm using Windows 10, and I've sorted through the first few obstacles and my build has now been running for 5-6 hours without any trouble. Until now that is. It just broke while building "guistdio.exe" in the desktop module. I'm not really seeing much information that can help me though, can any pick out what the trouble might be? Here is the last part of the build output: Compiling: desktop/test/deployment/active/active_native.cxx Making:test_deployment_active.lib Making:module definition file active_native.uno.def Making:itest_deployment_active_t1.lib lib -machine:IX86 @D:/cygwin/tmp/mktDdH6P Microsoft (R) Library Manager Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. -out:../../../wntmsci12.pro/lib/itest_deployment_active_t1.lib -def:../../../wntmsci12.pro/misc/active_native.uno.def Creating library ../../../ wntmsci12.pro/lib/itest_deployment_active_t1.lib and object ../../../ wntmsci12.pro/lib/itest_deployment_active_t1.exp Making:active_native.uno.dll Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. /MAP /OPT:NOREF -safeseh -nxcompat -dynamicbase -NODEFAULTLIB -RELEASE -DEBUG -INCREMENTAL:NO /SUBSYSTEM:CONSOLE /DLL -out:../../../ wntmsci12.pro/bin/active_native.uno.dll -map:../../../ wntmsci12.pro/misc/active_native.uno.map ../../../ wntmsci12.pro/lib/itest_deployment_active_t1.exp ../../../ wntmsci12.pro/slo/active_native.obj ../../../ wntmsci12.pro/slo/active_native.uno_version.obj icppuhelper.lib icppu.lib isal.lib msvcrt.lib msvcprt.lib uwinapi.lib kernel32.lib user32.lib oldnames.lib ../../../wntmsci12.pro/misc/active_native.uno.res linking ../../../wntmsci12.pro/bin/active_native.uno.dll.manifest ... Making:all_test_deployment_active.dpslo mkdir.exe -p ../../../wntmsci12.pro/misc/test_deployment_active/ /bin/rm -f ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar /bin/rm -f -r ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip mkdir.exe ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip mkdir.exe -p ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/META-INF \ ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/com/sun/star/comp/test/deployment/active_java cp MANIFEST.MF ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/META-INF/ cp ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/Dispatch.class ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/Provider.class ../../../ wntmsci12.pro/class/com/sun/star/comp/test/deployment/active_java/Services.class \ ../../../ wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip/com/sun/star/comp/test/deployment/active_java/ cd ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar-zip && zip ../active_java.jar \ META-INF/MANIFEST.MF com/sun/star/comp/test/deployment/active_java/Dispatch.class com/sun/star/comp/test/deployment/active_java/Provider.class com/sun/star/comp/test/deployment/active_java/Services.class adding: META-INF/MANIFEST.MF (deflated 9%) adding: com/sun/star/comp/test/deployment/active_java/Dispatch.class (deflated 54%) adding: com/sun/star/comp/test/deployment/active_java/Provider.class (deflated 52%) adding: com/sun/star/comp/test/deployment/active_java/Services.class (deflated 54%) /bin/rm -f ../../../wntmsci12.pro/misc/active.oxt /bin/rm -f -r ../../../ wntmsci12.pro/misc/test_deployment_active/active.oxt-zip mkdir.exe ../../../wntmsci12.pro/misc/test_deployment_active/active.oxt-zip mkdir.exe -p ../../../ wntmsci12.pro/misc/test_deployment_active/active.oxt-zip/META-INF sed -e 's|@PATH@|active_native.uno.dll|g' \ -e 's|@PLATFORM@|windows_x86|g' < manifest.xml \ > ../../../ wntmsci12.pro/misc/test_deployment_active/active.oxt-zip/META-INF/manifest.xml cp description.xml Addons.xcu ProtocolHandler.xcu ../../../ wntmsci12.pro/bin/active_native.uno.dll \ ../../../wntmsci12.pro/misc/test_deployment_active/active_java.jar active_python.py \ ../../../wntmsci12.pro/misc/test_deployment_active/active.oxt-zip/ cd ../../../wntmsci12.pro/misc/test_deployment_active/active.oxt-zip && zip ../../active.oxt \ META-INF/manifest.xml description.xml Addons.xcu ProtocolHandler.xcu \ active_native.uno.dll active_java.jar active_python.py adding: META-INF/manifest.xml (deflated 58%) adding: description.xml (deflated 50%) adding: Addons.xcu (deflated 67%) adding: ProtocolHandler.xcu (deflated 61%) adding: active_native.uno.dll (deflated 58%) adding: active_java.jar (deflated 13%) adding: active_python.py
Re: I want to support OO development
On 9/14/2016 12:23 PM, John D'Orazio wrote: On Sun, Sep 11, 2016 at 2:36 PM, Patricia Shanahanwrote: In the long term, work on the build system would be extremely valuable. That would make it easier to convert initial interest to long term contributions. [...] I made some changes recently to the step-by-step instructions for Windows, https://wiki.openoffice.org/wiki/Documentation/Building_Guid e_AOO/Step_by_step#Windows_7.2C_Windows_8.1. They should be tested by building on a machine that has not previously been used to build OpenOffice. Thank you Patricia for your contribution to this, it has encouraged me to give the building process a shot on my own Windows 10 system. I've made a couple of changes to the step-by-step instructions as I followed along and ran into a few issues, for example the dmake url was dead and needed to be substituted with a working link from sourceforge, and the paths for the Windows 7 SDK and DirectX SDK needed to be changed to paths without any spaces (the build process was getting blocked by this). Also the necessary perl modules hadn't been mentioned so I've added those in also. My build has been running for about 5-6 hours now and has not yet finished, at least it hasn't terminated with any errors so far! If it does terminate successfully then I'll add "Windows 10" alongside Windows 7 and Windows 8.1 in the step-by-step guide. Thanks. That sort of continuous improvement is just what the build instructions need. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: I want to support OO development
On Sun, Sep 11, 2016 at 2:36 PM, Patricia Shanahanwrote: > > In the long term, work on the build system would be extremely valuable. > That would make it easier to convert initial interest to long term > contributions. > > [...] I made some changes recently to the step-by-step instructions for Windows, > https://wiki.openoffice.org/wiki/Documentation/Building_Guid > e_AOO/Step_by_step#Windows_7.2C_Windows_8.1. They should be tested by > building on a machine that has not previously been used to build OpenOffice. > Thank you Patricia for your contribution to this, it has encouraged me to give the building process a shot on my own Windows 10 system. I've made a couple of changes to the step-by-step instructions as I followed along and ran into a few issues, for example the dmake url was dead and needed to be substituted with a working link from sourceforge, and the paths for the Windows 7 SDK and DirectX SDK needed to be changed to paths without any spaces (the build process was getting blocked by this). Also the necessary perl modules hadn't been mentioned so I've added those in also. My build has been running for about 5-6 hours now and has not yet finished, at least it hasn't terminated with any errors so far! If it does terminate successfully then I'll add "Windows 10" alongside Windows 7 and Windows 8.1 in the step-by-step guide. -- John R. D'Orazio
Re: dmake
I myself just ran into the problem of the missing apache-extras link, I've used a sourceforge link for my build: http://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2. Most of the links indicated in your github repo's README are dead links... I believe a downloadable tarball is useful for the building process, the sourceforge tarball seems to be working for me so far (it's my first build, and it's still building, but it's gotten past the initial dmake installation stage at least). On Wed, Sep 14, 2016 at 5:25 PM, Jim Jagielskiwrote: > Seeing that there is a dependency, still, on dmake, I've gone > ahead and created > > https://github.com/jimjag/dmake > > based on what I've been using... Suggestions and patches > welcome. Hoping we can use this to replace the apche-extras > links. > > It's based on (https://github.com/mohawk2/dmake) > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- John R. D'Orazio
Re: [NOMINATION REQUEST] Next Chair of AOO Project Management Committee
I could write much and more but to keep a long story short: I will volunteer to take over the role as next Chair. Planned is a time frame of 1 year. But of course also a bit longer if it fits better for any (time) contraints. I don't want to write here what should be done better or faster or ... as it doesn't make sense because - I'm pretty sure - it will always work out differently. Furthermore, this is not the thread to talk about this. Just one addition: For ASF the Chair role is not to say what to do or where to go. The tasks are in more formal way and well described here [1] and here [2]. So, you shouldn't expect anything else. Of course I'll do the same in the project (or more if my spare time permits) but than as an usual committer. And at the end: If there are any other candidates please speak up now. Then we can start a discussion. Thanks for your attention. [1] http://www.apache.org/dev/pmc.html#chair [2] http://www.apache.org/foundation/how-it-works.html#roles Marcus Am 08/30/2016 10:30 PM, schrieb Dennis E. Hamilton: [BCC to PMC] I am now ready to begin the Chair nomination process. Because of delays, the next change of Chair has moved to October 19. REQUEST FOR NOMINATIONS This message starts the nomination process for the next Chair for the Apache OpenOffice PMC. The term of the next Chair will start on 2016-10-19 and my resignation will be effective on that date. Members of the PMC can nominate themselves, expressing their willingness to serve. You can also place the names of others in nomination. Those individuals must accept the nomination to be considered as eligible. The identification of Nominees will end on Tuesday, 2016-09-13. The nature of subsequent discussion will depend on the number of Nominees. TIMELINE Here's the new timeline that has the replacement be ratified by the October 19, 2016 meeting of the ASF Board: 2016-10-19 ASF Board Meeting - Board rules on the resolution to install the new Chair. 2016-10-12 (latest) Resolution from AOO PMC to accept the new Chair is added to the Agenda for the 2016-10-19 Board Meeting (latest possible date) 2016-10-05 (latst) [RESULT][VOTE] on election of next Chair is reported. 2016-09-28 (latest) [VOTE] on election of next Chair begins. This could be by lazy consensus if there is already a single acceptable candidate. 2016-09-14 [NOMINEE DISCUSSION] process begins formally and any discussion on and among candidates willing to serve takes place. 2016-08-30 [NOMINATIONS] Individuals are recommended or offer themselves, indicate their availability to serve for at least one single-year term, and also have their own questions answered. - Dennis -Original Message- From: Dennis E. Hamilton [mailto:orc...@apache.org] Sent: Sunday, July 31, 2016 20:44 To: dev@openoffice.apache.org Subject: [DISCUSS] Process: Elect Next Chair of AOO Project Management Committee [BCC to PMC] [From the Chair] It is time for the selection of the next chair for the Apache OpenOffice Project Management Committee. INCUMBENT CHAIR I officially began my term on the third Wednesday of September, 2015. My commitment was to serve for one full year and then be replaced. I will complete that one-year term and step down on the third Wednesday of September, 2016. My successor will then be established by the Apache Software Foundation Board. Although I will continue as a member of the Project Management Committee and as a contributor to the Apache OpenOffice project, I am not available to continue as Chair beyond the 2016-09-21 ASF Board Meeting. I am available to assist the incoming Chair in any manner required for successfully transferring duties of the Chair. CHAIR ELECTION Based on previous practice, nomination, discussion, and election periods are held. Here is my proposed time-line, from endgame backwards: 2016-09-21 ASF Board Meeting - Board rules on the resolution to install the new Chair. 2016-09-14 Resolution from AOO PMC to accept the new Chair is added to the Agenda for the 2016-09-21 Board Meeting (latest possible date) 2016-09-07 [RESULT][VOTE] on election of next Chair is reported. 2016-08-31 [VOTE] on election of next Chair begins (with allowance for US Holiday weekend). This could be by lazy consensus if there is already a single acceptable candidate. 2016-08-17 [NOMINEE DISCUSSION] process begins formally and any discussion on and among candidates willing to serve takes place. 2016-08-03 [NOMINATIONS] Individuals are recommended or offer themselves, indicate their availability to serve for at least one single-year term, and also have their own questions answered. This process can be accelerated where it is seen that discussions have quieted and consensus for moving forward is evident. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Last call for 4.1.3 patches
On 14 Sep, Patricia Shanahan wrote: > Should this go in 4.1.3 or in 4.1.4? > > 4.1.3 will not be able to move on to building and testing unless we cut > off additions at some point. I think that point has already passed, but > I'm open to arguments. Have all of the necessary download site changes made it from trunk to 4.1.3? The released source tarball for 4.1.3 won't include anything in ext_sources that comes from svn, so we need to verify that bootstrap succeeds with an empty ext_sources directory. It would also be nice to merge r1758093 from trunk to update configure.ac to suggest the proper download URL for the dmake source. The old URL no longer works. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.3_release_blocker granted: [Issue 127113] Xcode 10.11 SDK not recognized
Patricia Shanahanhas granted 4.1.3_release_blocker: Issue 127113: Xcode 10.11 SDK not recognized https://bz.apache.org/ooo/show_bug.cgi?id=127113 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Last call for 4.1.3 patches
Good argument. I've granted it 4.1.3 release blocker. On 9/14/2016 10:29 AM, Jim Jagielski wrote: All other OSX 10.11 "blockers" can be worked around by adding some depedencies (like openssl...) but this one stops configure in its tracks. On Sep 14, 2016, at 1:03 PM, Jim Jagielskiwrote: 4.1.3 won't build on 10.11 w/o this since the Xcode provided just has the 10.11 SDX and configure doesn't see it and so the configure process dies. You have to hand edit configure to push thru. On Sep 14, 2016, at 12:59 PM, Patricia Shanahan wrote: Should this go in 4.1.3 or in 4.1.4? 4.1.3 will not be able to move on to building and testing unless we cut off additions at some point. I think that point has already passed, but I'm open to arguments. On 9/14/2016 9:53 AM, Jim Jagielski wrote: Didn't see this addressed so opened a new blocker: https://bz.apache.org/ooo/show_bug.cgi?id=127113 On Sep 13, 2016, at 6:26 PM, Patricia Shanahan wrote: Please make sure all patches for 4.1.3 are checked in to the AOO413 branch. - 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: 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: Last call for 4.1.3 patches
All other OSX 10.11 "blockers" can be worked around by adding some depedencies (like openssl...) but this one stops configure in its tracks. > On Sep 14, 2016, at 1:03 PM, Jim Jagielskiwrote: > > 4.1.3 won't build on 10.11 w/o this since the Xcode provided just > has the 10.11 SDX and configure doesn't see it and so the configure > process dies. You have to hand edit configure to push thru. > >> On Sep 14, 2016, at 12:59 PM, Patricia Shanahan wrote: >> >> Should this go in 4.1.3 or in 4.1.4? >> >> 4.1.3 will not be able to move on to building and testing unless we cut off >> additions at some point. I think that point has already passed, but I'm open >> to arguments. >> >> On 9/14/2016 9:53 AM, Jim Jagielski wrote: >>> Didn't see this addressed so opened a new blocker: >>> >>> https://bz.apache.org/ooo/show_bug.cgi?id=127113 >>> On Sep 13, 2016, at 6:26 PM, Patricia Shanahan wrote: Please make sure all patches for 4.1.3 are checked in to the AOO413 branch. - 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: dev-h...@openoffice.apache.org
Re: Last call for 4.1.3 patches
4.1.3 won't build on 10.11 w/o this since the Xcode provided just has the 10.11 SDX and configure doesn't see it and so the configure process dies. You have to hand edit configure to push thru. > On Sep 14, 2016, at 12:59 PM, Patricia Shanahanwrote: > > Should this go in 4.1.3 or in 4.1.4? > > 4.1.3 will not be able to move on to building and testing unless we cut off > additions at some point. I think that point has already passed, but I'm open > to arguments. > > On 9/14/2016 9:53 AM, Jim Jagielski wrote: >> Didn't see this addressed so opened a new blocker: >> >> https://bz.apache.org/ooo/show_bug.cgi?id=127113 >> >>> On Sep 13, 2016, at 6:26 PM, Patricia Shanahan wrote: >>> >>> Please make sure all patches for 4.1.3 are checked in to the AOO413 branch. >>> >>> - >>> 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: Last call for 4.1.3 patches
Should this go in 4.1.3 or in 4.1.4? 4.1.3 will not be able to move on to building and testing unless we cut off additions at some point. I think that point has already passed, but I'm open to arguments. On 9/14/2016 9:53 AM, Jim Jagielski wrote: Didn't see this addressed so opened a new blocker: https://bz.apache.org/ooo/show_bug.cgi?id=127113 On Sep 13, 2016, at 6:26 PM, Patricia Shanahanwrote: Please make sure all patches for 4.1.3 are checked in to the AOO413 branch. - 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: Last call for 4.1.3 patches
Didn't see this addressed so opened a new blocker: https://bz.apache.org/ooo/show_bug.cgi?id=127113 > On Sep 13, 2016, at 6:26 PM, Patricia Shanahanwrote: > > Please make sure all patches for 4.1.3 are checked in to the AOO413 branch. > > - > 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: Status of ASF Ubuntu Buildbots
Gavin McDonald wrote: What we do have is two (imho) useless ‘snapshot’ builds (based on openoffice/tags/SNAPSHOT - Which hasn’t had a commit in 10 months and never will have because its a ‘tag’. ...which would be true if we were using SVN the textbook way, but for historical reasons we aren't. The SNAPSHOT tag is meant to be moved (deleted and recreated with svn copy) by the release manager to mark a milestone towards the next release. So I’ll remove those builds and replace them with 413 branch builds. Unless someone objects. This would make sense and align us to more "normal" practices. The convenience of the SNAPSHOT tag was that people providing binary releases had a simple reference for the build (i.e., just SNAPSHOT instead of a revision number). With more stable builbots we can probably use the latest commit at build time, i.e., simply track AOO413 HEAD as you suggest. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
dmake
Seeing that there is a dependency, still, on dmake, I've gone ahead and created https://github.com/jimjag/dmake based on what I've been using... Suggestions and patches welcome. Hoping we can use this to replace the apche-extras links. It's based on (https://github.com/mohawk2/dmake) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.3_release_blocker granted: [Issue 127112] Update bundled dictionaries for AOO 4.1.3 release
Patricia Shanahanhas granted Ariel Constenla-Haile 's request for 4.1.3_release_blocker: Issue 127112: Update bundled dictionaries for AOO 4.1.3 release https://bz.apache.org/ooo/show_bug.cgi?id=127112 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.1.3_release_blocker requested: [Issue 127112] Update bundled dictionaries for AOO 4.1.3 release
Ariel Constenla-Hailehas asked for 4.1.3_release_blocker: Issue 127112: Update bundled dictionaries for AOO 4.1.3 release https://bz.apache.org/ooo/show_bug.cgi?id=127112 --- Description --- Created attachment 85671 --> https://bz.apache.org/ooo/attachment.cgi?id=85671=edit Patch to update bundled dictionaries Some dictionaries on main/extensions.lst have an outdated download URL. They should be updated with the latest available versions. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org