sure. One step after another.
Thanks the welcome :-)
On 11.09.2016 16:49, JZA wrote:
Bare in mind most of AOO is based on C++ code. So this would be most
of the actual development time. There are many bugs that have been
documentated, so before squashing them, you should read the wiki and
also consult the list for possible outdated documentation. This is one
of the biggest hurdles to get really into AOO.
On Sun, Sep 11, 2016 at 7:36 AM, Patricia Shanahan <p...@acm.org
<mailto:p...@acm.org>> wrote:
Welcome aboard!
On 9/11/2016 3:40 AM, Peter Kovacs wrote:
Hello Open Office Dev Community,
Dennis E. Hamilton forwarded my message to this list. Thank
you for this
activity. I was in the opinion that I have no time and
therefore can not
join the list or help.
However OpenOffice devlopment is on my mind for a complete
week now. So
I decided I free up time and will focus on developing for
Apache Open
Office.
The activity of freeing up time is not that easy, and I am
still working
on it. So for starters I will use 4h per week for OO trying to
move up
to 8h.
However I have to solve some other topics for this.
Whatever time you can spend will be useful and valued.
...
Long story short. I know
# a lot of languages badly
# a language that is itself a mess.
# how to development in crappy envoirments.
I value
# maintainability
# necessary documentation
# comments
# smart easy to use code.
I would privatly like to achieve to improve
# build times
# maintainability
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.
In the short term, we are preparing release 4.1.3. We need to get
all the changes checked in. After than, the more building and
testing the better.
I made some changes recently to the step-by-step instructions for
Windows,
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Windows_7.2C_Windows_8.1
<https://wiki.openoffice.org/wiki/Documentation/Building_Guide_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.
There is an ongoing activity that needs good user skills without
requiring immediate programming: Monitoring bug tracking at
https://bz.apache.org/ooo/. Each new bug report needs to be tested
to see if it reproduces. If there is insufficient information to
reproduce it, the bug report needs a comment saying so and
requesting additional information. If you can reproduce a bug you
can do as much analysis as you have time for.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
<mailto:dev-unsubscr...@openoffice.apache.org>
For additional commands, e-mail: dev-h...@openoffice.apache.org
<mailto:dev-h...@openoffice.apache.org>
--
Alexandro Colorado
Apache OpenOffice Contributor
9060 55AB FFD2 2F02 0E1A 3409 599C 14FC 9450 D3CF
