Re: Planning for emergency releases

[Patricia Shanahan]

On 8/8/2016 11:14 AM, Marcus wrote:

Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti:

On 07/08/2016 Marcus wrote:

Maybe we are not that far aways from each other. What I want to to avoid
is to provide hundreads of MBs for a single fix. Of course we can do a
4.1.3 with some collected fixes. As I don't know what is coming in the
future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
the calendar is still showing 2016. ;-)


The right trade-off would be between two and three releases a year
(including maintenance releases).

Based on history, we've never been -and we are not- in a "release now
since there is a known critical exploit circulating", so the "emergency
release" is not likely to happen often.

It will be enough to be in a permanent "ready to release" mode (where
work is still mostly on the infrastructure side, the rest is OK) and use
this readiness to ship emergency releases in the unlikely case we need
one, and a few maintenance/feature releases from time to time.


it seems we have the same wish with regard to releases. We can just hope
that this can come true.



+1 on "ready to release" mode. However, rather than just hoping it can
come true, I would like to work on a plan to make it come true.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Building AOO for Windows 10

[Carl Marcum]

On 08/07/2016 08:35 AM, Kirsten S wrote:

Hello together,

I am new to this list and new to the AOO-Project. I've been trying to build
AOO and to get the source code since yesterday. I followed the step by step
guide in this link: https://wiki.openoffice.org/wiki/Documentation/
Building_Guide_AOO/Step_by_step

Everything went fine until i wanted to check out the source code from the
svn-repository. It seems that the directory aoo-trunk doesn't exist
anymore. At least this is what cygwin keeps on telling me.

I tried to execute the command line: svn co https://svn.apache.org./repos/
asf/openoffice/trunk aoo-trunk and then cd aoo-trunk --> Here i get the
message  No such file or directory.

Can anybody help me?

Thanks a lot in advance,
Dany



Hi Kirsten,

Welcome.

If the svn address is the one you used there is a period after 
apache.org that does not belong there.


https://svn.apache.org/repos/asf/openoffice/trunk


The subversion client should create the aoo-trunk locally for you. Just 
be in the parent directory where you want to create it.


Good luck !!

Carl


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: expat upgrade patch needs testing

[Don Lewis]

On  8 Aug, Kay Schenk wrote:
> 
> 
> On 08/07/2016 08:03 PM, Don Lewis wrote:
>> On  5 Aug, To: dev@openoffice.apache.org wrote:
>>> I just submitted a patch to upgrade the bundled expat to version 2.2.0:
>>> 
>>>
>>> I've done some testing on FreeBSD and Windows.  Unfortunately I can't
>>> test Linux at the moment.  After a Virtualbox upgrade, both of my Linux
>>> VMs panic the host system when I try start them in Virtualbox.
>> 
>> I found that if I set the number of processors to 1 for my Linux VMs,
>> then I can get them to run.  I was able to build and test this patch on
>> CentOS 7 and Ubuntu 12.
>> 
>> 
> 
> I can probably do a build tomorrow to test with CentOS 6.8.
> Assuming I get a successful build, what else do I need to do to test?

If you get through the build, that's a pretty good test.  During the
build saxparser uses expat to read the .xml files for all of the
locales.

The other thing that expat seems to get used for is the tree view of
help topics.
Help -> OpenOffice Help -> Contents


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: expat upgrade patch needs testing

[Kay Schenk]

On 08/07/2016 08:03 PM, Don Lewis wrote:
> On  5 Aug, To: dev@openoffice.apache.org wrote:
>> I just submitted a patch to upgrade the bundled expat to version 2.2.0:
>> 
>>
>> I've done some testing on FreeBSD and Windows.  Unfortunately I can't
>> test Linux at the moment.  After a Virtualbox upgrade, both of my Linux
>> VMs panic the host system when I try start them in Virtualbox.
> 
> I found that if I set the number of processors to 1 for my Linux VMs,
> then I can get them to run.  I was able to build and test this patch on
> CentOS 7 and Ubuntu 12.
> 
> 

I can probably do a build tomorrow to test with CentOS 6.8.
Assuming I get a successful build, what else do I need to do to test?

-- 

MzK

"Time spent with cats is never wasted."
   -- Sigmund Freud

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

RE: Planning for emergency releases

[Dennis E. Hamilton]

+1 on the permanent "ready to release" mode.

> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Monday, August 8, 2016 11:15
> To: dev@openoffice.apache.org
> Subject: Re: Planning for emergency releases
> 
> Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti:
> > On 07/08/2016 Marcus wrote:
> >> Maybe we are not that far aways from each other. What I want to to
> avoid
> >> is to provide hundreads of MBs for a single fix. Of course we can do
> a
> >> 4.1.3 with some collected fixes. As I don't know what is coming in
> the
> >> future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
> >> the calendar is still showing 2016. ;-)
> >
> > The right trade-off would be between two and three releases a year
> > (including maintenance releases).
> >
> > Based on history, we've never been -and we are not- in a "release now
> > since there is a known critical exploit circulating", so the
> "emergency
> > release" is not likely to happen often.
> >
> > It will be enough to be in a permanent "ready to release" mode (where
> > work is still mostly on the infrastructure side, the rest is OK) and
> use
> > this readiness to ship emergency releases in the unlikely case we need
> > one, and a few maintenance/feature releases from time to time.
> 
> it seems we have the same wish with regard to releases. We can just hope
> that this can come true.
> 
> 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: Review of the 4.1.2-patch1 MacOSX.README.txt file

[William L. Anderson]

Kay, I have attached a ".txt" file that incorporates the changes suggested. Two 
items are *not* included.

(1) There is a need to provide the md5 and sha256 hash of the
libtl.dylib file. Many Mac users do not have any experience with GnuPG or
OpenPGP keys. However, the Mac comes with tools to verify md5 and sha256
hashes already installed. Instructions on how to use them can be included
in the README file if that is desirable.

(2) Users who choose to use the Finder method of installing the new file
do not have any way to check signatures or hashes without using the
command line.

Let me know what more help I can provide.

Bill A



This file contains two sets of instructions. The first (I) outlines how to
install the new library file using a Terminal window and the command
line. The second (II) outlines how to install the new library file
using the Finder.


I. These directions assume (1) familiarity with using the command line
   in a Terminal window; and (2) that the user has adminstrator privileges.

I.1. Make sure that OpenOffice is not running.

I.2. Download the "libtl.dylib" file to the Downloads folder (or any
 other folder or to the Desktop).

I.3. Open the Finder App (or another file manager of your choice).

I.4. Determine the installation path of the OpenOffice program files;
  (the default path is "/Applications/OpenOffice.app/Contents/program/").

I.5. Rename the old file "libtl.dylib" to "libtl.dylib.original" to keep
 a backup.

I.6. Copy the new libtl.dylib file to the OpenOffice/Contents/program
 folder. (Administrator privileges needed.)

   In a terminal window these commands will accomplish the file copy.

   $ cd ~/Downloads
   $ sudo cp -v libtl.dylib /Applications/OpenOffice.app/Contents/program


II. Directions for updating the file without using a Terminal window.
These instructions assume:
(1) that the user account has Administrator privileges; and
(2) that the file "libtl.dylib" was saved to the Downloads folder.

II.1. In the Finder select the Go menu on the Application menu bar (at
  the top of the screen) and open a window to the Downloads folder.

II.2. In the Finder open another Finder window and in the sidebar select
  the Applications folder.

   Hold down the "control" key and select the OpenOffice application.
   Select Show Package Contents from the drop-down menu.
   Open the Contents folder now displayed in the Finder window.
   Select and open the "program" folder displayed in the Finder window.
   Scroll through the list of files shown and find "libtl.dylib"
   Hold down the "control" key and select the "libtl.dylib" file.
   Select Duplicate from the drop-down menu.
   ( a file named "libtl copy.dylib" is created )
   Select the back button "<" from the Finder window top menu.
   ( the Finder displays the list of files and folders in the Contents folder )

II.3. Now select the Finder window showing the "Downloads" folder contents.

   Hold down the "control" key and select the "libtl.dylib" file.
   Select 'Copy "libtl.dylib"' from the drop-down menu.

   Select the other Finder window showing the list of files in the Contents 
folder.

   Hold down the "control" key and select the "program" folder.
   Select "Paste Item" from the drop-down menu.

   A window appears with the message:
   An older item named "libtl.dylib" already exists in this
   location. Do you want to replace it with the newer one you're
   moving?
   Select the "Replace" button.



> On Aug 8, 2016, at 11:18 AM, Kay Schenk  wrote:
> 
> Hi Bill and thanks for helping out.
> 
> To aid in readability of your edits, would it be possible for you to make
> your proposed changes to the MacOSX readme and include the whole file (with
> your edits) as a ".txt" attachment to this message?
> 
> 
> On Sun, Aug 7, 2016 at 5:10 PM, William L. Anderson  wrote:
> 
>> Dennis Hamilton asked me to look at the 4.1.2-patch1 README file for Mac
>> OSX.
>> I have done so and include the following information.
>> 
>> My test system info: OSX Version 10.11.6 "El Capitan"
>>   Hardware: Macbook Air (Late 2010)
>> 
>> ==
>> (1) The text of the current MacOSX.README.txt file.
>> 
>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
>> patch1/binaries/MacOSX/MacOSX.README.txt
>> 
>> 1. Make sure that OpenOffice is not running.
>> 2. Open a terminal and unpack the downloaded file (e.g., with Archive
>> Utility or WinZip Mac Edition) to an easily
>>   locatable path.
>> 3. Open the Finder App - or another file manager of your choice.
>> 4. Locate the installation path of OpenOffice (e.g.,
>> "/Applications/Utilities/OpenOffice4/program/").
>> 5. Rename the old file "libtl.dylib" to "libtl.dylib.original" to keep a
>> backup.
>> 6. Copy the new file from the unpacked Zip file to the installation path
>>   (e.g, "/Desktop/libtl.dylib" --> "/Applications/Utilities/
>> OpenOffice4/program/").
>> 
>> ===
>> 
>> (2) 

Re: Planning for emergency releases

[Marcus]

Am 08/08/2016 07:28 PM, schrieb Andrea Pescetti:

On 07/08/2016 Marcus wrote:

Maybe we are not that far aways from each other. What I want to to avoid
is to provide hundreads of MBs for a single fix. Of course we can do a
4.1.3 with some collected fixes. As I don't know what is coming in the
future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
the calendar is still showing 2016. ;-)


The right trade-off would be between two and three releases a year
(including maintenance releases).

Based on history, we've never been -and we are not- in a "release now
since there is a known critical exploit circulating", so the "emergency
release" is not likely to happen often.

It will be enough to be in a permanent "ready to release" mode (where
work is still mostly on the infrastructure side, the rest is OK) and use
this readiness to ship emergency releases in the unlikely case we need
one, and a few maintenance/feature releases from time to time.


it seems we have the same wish with regard to releases. We can just hope 
that this can come true.


Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Planning for emergency releases

[Andrea Pescetti]

On 07/08/2016 Marcus wrote:

Maybe we are not that far aways from each other. What I want to to avoid
is to provide hundreads of MBs for a single fix. Of course we can do a
4.1.3 with some collected fixes. As I don't know what is coming in the
future I would not love to see another 4.1.4, 4.1.5, 4.1.6, etc. when
the calendar is still showing 2016. ;-)


The right trade-off would be between two and three releases a year 
(including maintenance releases).


Based on history, we've never been -and we are not- in a "release now 
since there is a known critical exploit circulating", so the "emergency 
release" is not likely to happen often.


It will be enough to be in a permanent "ready to release" mode (where 
work is still mostly on the infrastructure side, the rest is OK) and use 
this readiness to ship emergency releases in the unlikely case we need 
one, and a few maintenance/feature releases from time to time.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

RE: [TESTING] Applying openoffice-4.1.2-patch1 for Windows

[Dennis E. Hamilton]

Alpha version 0.0.1 of README-4.1.2-patch1-apply-Windows.txt has been 
introduced into the files (and the .zip) at 
.

This version reflects suggestions by Marcus Lange, Pedro Lino, and Keith 
McKenna.  Suggestions that are not (yet) implemented will be discussed in 
replies to their messages and on the bugzilla issue at 
.


By its nature, this material is intended for users operating on Windows.  In 
some cases, incompatible forms are used on the Subversion server where the 
above files are situated.  Version 0.0.1 attempts to accommodate for this 
incompatibility.  In continuing to verify the procedure, please indicate 
whether there are (now) difficulties using the text files, especially on 
Windows.

Users of Linux systems may have difficulties with some utilities for which the 
Windows versions of the same tool (e.g., md5sum) do not produce 
Linux-acceptable line endings.  It is useful to know if that is still the case. 
 The files have been confirmed to be usable using the utilities built for use 
on Windows.

For future versions, the use of HTML instead of text will be considered.  HTML 
does not have white-space incompatibility problems across different platforms. 
The HTML will also be digitally-signed as a means of verifying its authenticity.

In addition to possibly using HTML as a better form for cross-platform use of 
text, attention will now move toward introducing scripts that automatically 
apply the change, replacing all of steps 9-18.

Meanwhile, it is valuable to continue testing that the replacement file 
produces no regression or introduction of any defects not seen using an 
unmodified Apache OpenOffice 4.1.2.

 - Dennis


> -Original Message-
> From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org]
> Sent: Tuesday, August 2, 2016 20:31
> To: dev@openoffice.apache.org
> Cc: q...@openoffice.apache.org
> Subject: [TESTING] Applying openoffice-4.1.2-patch1 for Windows
> 
> Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
> 
> The files to be used in testing are at
> .
> 
> The files to be tested and reviewed are
> 
>  * README-4.1.2-patch1-apply-Windows.txt
>The description of the procedure for applying a corrected
>library file to installed copies of Apache OpenOffice 4.1.2
>on Windows.  Read this first before deciding to download
>the Zip file and attempting the procedure.
> 
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
>The Zip archive containing the files to be used in the
>procedure.  There is a copy of the README within the
>archive as well.
> 
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256
>Files that provide a digital signature, an MD5 hash,
>and an SHA256 hash that can be used to verify the
>integrity of the download and, in the case of the
>digital signature, the authenticity and accuracy of
>the download.
> 
> REQUESTED TESTING
> 
>  * [OPTIONAL] If you are able to check any of the .asc,
>.md5, and .sha256 files against the .zip, report any
>difficulties that may have been encountered.
> 
>  * If you performed the procedure, report
> * the version of Microsoft Windows and the type of
>   account used (administrator or standard user).
> * report whether the procedure succeeded
> * if the procedure failed or met with difficulties,
>   please summarize the problems and how you over-
>   came any of them
> 
>  * [IMPORTANT] Identify any missing, incomplete or
>confusing information in the README.  Describe what you
>see as important improvements before making general
>release of the procedure for use by non-expert users of
>Apache OpenOffice on Windows.
> 
> The goal is to provide as much as we can to assist Windows users in
> applying this fix with confidence and success.  The experience of more-
> knowledgable users who appreciate the difficulties of non-experts is
> important in achieving that.
> 
> Thank you for any effort you invest and the feedback you provide.
> 
>  - Dennis
> 
> 
> 
> 
> 
> 
>  -- Dennis E. Hamilton
> orc...@apache.org
> dennis.hamil...@acm.org+1-206-779-9430
> https://keybase.io/orcmid  PGP F96E 89FF D456 628A
> X.509 certs used and requested for signed e-mail
> 
> 
> 
> -
> 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 of the 4.1.2-patch1 MacOSX.README.txt file

[Kay Schenk]

Hi Bill and thanks for helping out.

To aid in readability of your edits, would it be possible for you to make
your proposed changes to the MacOSX readme and include the whole file (with
your edits) as a ".txt" attachment to this message?


On Sun, Aug 7, 2016 at 5:10 PM, William L. Anderson  wrote:

> Dennis Hamilton asked me to look at the 4.1.2-patch1 README file for Mac
> OSX.
> I have done so and include the following information.
>
> My test system info: OSX Version 10.11.6 "El Capitan"
>Hardware: Macbook Air (Late 2010)
>
> ==
> (1) The text of the current MacOSX.README.txt file.
>
> https://dist.apache.org/repos/dist/dev/openoffice/4.1.2-
> patch1/binaries/MacOSX/MacOSX.README.txt
>
> 1. Make sure that OpenOffice is not running.
> 2. Open a terminal and unpack the downloaded file (e.g., with Archive
> Utility or WinZip Mac Edition) to an easily
>locatable path.
> 3. Open the Finder App - or another file manager of your choice.
> 4. Locate the installation path of OpenOffice (e.g.,
> "/Applications/Utilities/OpenOffice4/program/").
> 5. Rename the old file "libtl.dylib" to "libtl.dylib.original" to keep a
> backup.
> 6. Copy the new file from the unpacked Zip file to the installation path
>(e.g, "/Desktop/libtl.dylib" --> "/Applications/Utilities/
> OpenOffice4/program/").
>
> ===
>
> (2) Suggested updates to that file.
>
>
> 1. OK AS WRITTEN
>
> 2. Download the "libtl.dylib" file to the Downloads folder (or any other
> folder or to the Desktop)
> 2.1. Verify the download integrity: see UPDATE NEEDED below.
>
> 3. OK AS WRITTEN
>
> 4. Locate the installation path of OpenOffice (e.g.,
> "/Applications/OpenOffice.app/Contents/program"
>
> 5. OK AS WRITTEN
>
> 6. Copy the new libtl.dylib file to the OpenOffice/Contents/program
> folder. (Administrator privileges needed.)
>In the terminal these commands will work.
>
>$ cd ~/Downloads
>$ sudo cp -v libtl.dylib /Applications/OpenOffice.app/Contents/program
>
> UPDATE NEEDED: need to provide the md5 and sha256 hash of the
> libtl.dylib file. Many Mac users do not have any experience with GnuPG or
> OpenPGP keys. However, the Mac comes with tools to verify md5 and sha256
> hashes already installed. Those instructions can be added to the README.
>
> ===
>
> (3) MacOSX instructions for how to update the dylib file without using a
> Terminal window.
>
> DIRECTIONS FOR UPDATING THE FILE WITHOUT USING A Terminal window.
> Note: Mac users can NOT check file integrity without using a terminal
> window.
>
> These instructions assume:
> (1) that the user account has Administrator privileges; and
> (2) that the file "libtl.dylib" was saved to the Downloads folder.
>
> 1. In the Finder select the Go menu on the Application menu bar (at
> the top of the screen) and open a window to the Downloads folder.
>
> 2. In the Finder open another Finder window and in the sidebar select
> the Applications folder.
>
>Hold down the "control" key and select the OpenOffice application.
>Select Show Package Contents from the drop-down menu.
>Open the Contents folder now displayed in the Finder window.
>Select and open the "program" folder displayed in the Finder window.
>Scroll through the list of files shown and find "libtl.dylib"
>Hold down the "control" key and select the "libtl.dylib" file.
>Select Duplicate from the drop-down menu.
>( a file named "libtl copy.dylib" is created )
>Select the back button "<" from the Finder window top menu.
>( the Finder displays the list of files and folders in the Contents
> folder )
>
> 3. Now select the Finder window showing the "Downloads" folder contents.
>
>Hold down the "control" key and select the "libtl.dylib" file.
>Select 'Copy "libtl.dylib"' from the drop-down menu.
>
>Select the other Finder window showing the list of files in the
> Contents folder.
>
>Hold down the "control" key and select the "program" folder.
>Select "Paste Item" from the drop-down menu.
>
>A window appears with the message:
>An older item named "libtl.dylib" already exists in this
>location. Do you want to replace it with the newer one you're
>moving?
>Select the "Replace" button.
>
> ===
>
> I have tested the replacing the file both ways. AOO seems to start up
> without problem with the new file in place.
>
> Let me know how I can help further.
>
> Bill Anderson
>
>


-- 

Kay Schenk@Apache OpenOffice

“Things work out best for those who make the best of how things work out.”

-- John Wooden

Special project for newcomers

[Patricia Shanahan]

There is a current project for which newcomers to the OpenOffice team
may be able to make a particularly valuable contribution. The objective
is to find out whether a set of instructions are usable and work. For
this, being unfamiliar with the background is an advantage.

To participate, you need to subscribe to dev@openoffice.apache.org, if
you have not already done so. Review the archive at
http://mail-archives.apache.org/mod_mbox/openoffice-dev/ and read the
thread with subject "[TESTING] Applying openoffice-4.1.2-patch1 for
Windows". I have quoted the base message, which contains the most
important information, below.

Please report success, failure, questions, suggestions etc.



On 8/2/2016 8:31 PM, Dennis E. Hamilton wrote:
> Testing of an Apache OpenOffice 4.1.2-patch1 procedure is requested.
>
> The files to be used in testing are at
> 
.

>
> The files to be tested and reviewed are
>
>  * README-4.1.2-patch1-apply-Windows.txt
>The description of the procedure for applying a corrected
>library file to installed copies of Apache OpenOffice 4.1.2
>on Windows.  Read this first before deciding to download
>the Zip file and attempting the procedure.
>
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip
>The Zip archive containing the files to be used in the
>procedure.  There is a copy of the README within the
>archive as well.
>
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.asc
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.md5
>  * apache-openoffice-4.1.2-patch1-apply-Win_x86.zip.sha256
>Files that provide a digital signature, an MD5 hash,
>and an SHA256 hash that can be used to verify the
>integrity of the download and, in the case of the
>digital signature, the authenticity and accuracy of
>the download.
>
> REQUESTED TESTING
>
>  * [OPTIONAL] If you are able to check any of the .asc,
>.md5, and .sha256 files against the .zip, report any
>difficulties that may have been encountered.
>
>  * If you performed the procedure, report
> * the version of Microsoft Windows and the type of
>   account used (administrator or standard user).
> * report whether the procedure succeeded
> * if the procedure failed or met with difficulties,
>   please summarize the problems and how you over-
>   came any of them
>
>  * [IMPORTANT] Identify any missing, incomplete or
>confusing information in the README.  Describe what you
>see as important improvements before making general
>release of the procedure for use by non-expert users of
>Apache OpenOffice on Windows.
>
> The goal is to provide as much as we can to assist Windows users in 
applying this fix with confidence and success.  The experience of 
more-knowledgable users who appreciate the difficulties of non-experts 
is important in achieving that.

>
> Thank you for any effort you invest and the feedback you provide.
>
>  - Dennis
>
>
>
>
>
>
>  -- Dennis E. Hamilton
> orc...@apache.org
> dennis.hamil...@acm.org+1-206-779-9430
> https://keybase.io/orcmid  PGP F96E 89FF D456 628A
> X.509 certs used and requested for signed e-mail
>
>
>
> -
> 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: Hello World

[Damjan Jovanovic]

Hi Aditya

Welcome to Apache OpenOffice! Your skills sound very useful and I see a
promising future for you here. We appreciate all contributions.

If you plan to get into development, please subscribe to this mailing list
if you haven't already, and start by checking out the source code:
http://openoffice.apache.org/source.html
and get it to build:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

Any ideas about what you'd like to contribute?

Please feel free to contact us with any questions.

Damjan


On Sun, Aug 7, 2016 at 8:11 AM, aditya chandran 
wrote:

> Hi guys,
>
> I'm Aditya an enthusiastic student from India I know a little bit java,
> c++, html, css ,php, sql and python i would like to join this amazing
> community to gain more knowledge of tgis mysterious yet fascinating world
> which is quite new to me.  Please pop in an email if you have any
> suggestions where to start from and how to do things right.
>
> Have an  awesome friendship day
>

Help me through this place

[aditya chandran]

Hi ,

Aditya here,
Could anyone please mentor me through this new place I am quite new and young 
to the place
Eagerly awaiting your reply

Aditya