Re: [DISCUSS] [PMC] Proposed PMC List

[imacat]

I feel honored to be listed.  I would like to help PMC if there is a
chance.

In any case, I suggest at least one female should be included in the
PMC, to encourage the contribution of females in the community and bring
diverse voices in PMC.  It is very important to encourage more and more
female contributors to join the community, and make them feel that
OpenOffice is theirs', not of some male geeks.

I also suggest to include Asians.  From the past experience of
OpenOffice.org, the main problem of the Asian community is that we are
not included in the project.  The problem of Asian text processing is
very different than that of Latin text.  It was very difficult for many
most important Asian problems to be heard by non-Asian people.  It shall
change and make a significant difference when Asians are included in PMC.

On 2012/09/25 06:31, Andrea Pescetti said:
> On 24/09/2012 Jürgen Schmidt wrote:
>> On 9/24/12 10:26 AM, Ross Gardler wrote:
>>> Just to confirm that I have received no offline nominations.
>>
>> thanks for this info, it shows that the approach was not so wrong and we
>> had no real need for this additional option.
> 
> It's still good to have had this option, so we are sure that everybody
> who wanted to participate in the process had the opportunity to do so.
> And it's even better that in the end everybody decided to make their
> nomination in public.
> 
>> I am looking forward to Andrew's summary and from my perspective we
>> should already start thinking what will be next?
> 
> Before moving on with all the steps you listed (and I agree with all of
> them) we will need to actually see the summary and derive the potential
> PMC from there. So far I've seen opinions ranging from including only
> the 10 most popular nominees to including everybody who received at
> least one nomination. Probably the best solution is somewhere in
> between, but once we have the summary the situation will probably be
> clearer.
> 
> Regards,
>   Andrea.


-- 
Best regards,
imacat ^_*' 
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
Apache OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/
Greenfoot Taiwan http://greenfoot.westart.tw/



signature.asc
Description: OpenPGP digital signature

[ApacheCon] BoF session on AOO community

[Peter Junge]

Dear OpenOffice Community,

During ApacheCon Europe 2012 (ACEU 2012; http://apachecon.eu/), we will 
hold a 90-minute session on the state of the community. Our topic is as 
broad as the community and includes discussion on how to develop and 
further the community of contributors and users making up AOO. We hope 
you can be there and add your voice! We seldom have opportunity to meet 
in person, and this will be a great occasion to go over where we are as 
a community, what we need to do to improve the operations of the 
community, and what can be done by us all to take AOO to top-level 
status. Everyone is invited—and to encourage you further to participate, 
we hope to welcome the Apache mentors who are helping AOO move ahead.


At the moment, I'm responsible for this session but due to the fact that 
I'm located in Beijing I will not be able to attend in person. Hence, it 
would be great to find one or two volunteers to host this BoF session 
about the AOO community at the ApacheCon Europe.


Best regards,
Peter

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Juergen Schmidt]

Am Montag, 24. September 2012 um 21:32 schrieb Andrea Pescetti:
> Louis Suárez-Potts wrote:
> > On 12-09-24, at 10:52 , Rob Weir wrote:
> > > Perhaps it could be de-politicized a little more if the request is
> > > for an "ODF Editors" room, and do with multilateral, with LO,
> > > Calligra, AbiWord, Gnumeric, etc.
> > >  
> >  
> > I'm all for that and tried that in 2011 but not this year (2012).
> >  
>  
>  
> That would definitely be good for me too, and it's enough to declare in
> our application that we are available for such a solution. Note that
> there is no need for a joint proposal: FOSDEM organizers will collect
> the applications and, based on them, propose to co-organize the
> devrooms, see https://fosdem.org/2013/call_for_devrooms.html
>  
> Going on, this is the request I would send, posted here for corrections
> and lazy consensus. Note: the "Saturday" choice below is totally arbitrary.
> ---
> * Devroom name: Apache OpenOffice
>  
> * Description
>  
> Apache OpenOffice, formerly known as OpenOffice.org, is one of the most
> popular Free and Open Source software projects. The project, hosted by
> the Apache Software Foundation since June 2011, had two successful
> releases in 2012, with more than 16 million downloads in 4 months.
> OpenOffice is developed by a large and diverse community, including
> full-time and part-time core developers, translators, testers, user
> experience experts, documentation contributors, developers of
> third-party extensions and templates.
>  
> * Project URLs
> - http://www.openoffice.org
> - http://incubator.apache.org/openofficeorg/
>  
> * Preferred day: Saturday or Sunday
> - Saturday
>  
> * Why should FOSDEM accept this proposal?
>  
> After a period of reorganization at Apache, the OpenOffice project
> managed to come back to a regular release schedule, is attracting new
> volunteers and is now able to successfully engage them. Recent
> contributions, like the donation of the Lotus Symphony code by IBM,
> provide interesting challenges for new developers, and there are a lot
> of tasks available for non-developers too.
>  
> An Apache OpenOffice devroom would allow existing volunteers to meet and
> discuss future developments, and users and potential new volunteers to
> learn how they can help the project, thanks to presentations and
> hacking sessions spanning a broad range of topics.
>  
> The Apache OpenOffice project is definitely willing to consider a
> possible suggestion by the organizers for a joint "ODF editors" devroom,
> dedicated to Apache OpenOffice and to the other Free and Open Source
> editors using OpenDocument as their native format.
> ---
>  
> > The issue: who wants to own this? I have done that and worked with
> > fosdem for several years, as has Juergen, to whom I handed off the
> > task back in 2008 or 2009.
> >  
>  
>  
> I just want to make sure we submit our application in time. I wrote the
> draft above so that we have a concrete basis for discussion, and I'll
> likely attend FOSDEM, as I've done quite regularly in recent years.
>  
> If nobody else steps up, I'll send the application after we have
> consensus on it, but if anybody else wants to take over from now on,
> it's absolutely OK for me, provided we meet the deadlines, i.e., we send
> the application this week.
>  
>  


I like your draft and please move forward with it. I will support you later on 
with further organization...

Juergen  
>  
> Regards,
> Andrea.
>  
>  

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Peter Junge]

On 9/25/2012 3:32 AM, Andrea Pescetti wrote:

[...]


Going on, this is the request I would send, posted here for corrections
and lazy consensus. Note: the "Saturday" choice below is totally arbitrary.
---
* Devroom name: Apache OpenOffice

* Description

Apache OpenOffice, formerly known as OpenOffice.org, is one of the most
popular Free and Open Source software projects. The project, hosted by
the Apache Software Foundation since June 2011, had two successful
releases in 2012, with more than 16 million downloads in 4 months.
OpenOffice is developed by a large and diverse community, including
full-time and part-time core developers, translators, testers, user
experience experts, documentation contributors, developers of
third-party extensions and templates.

* Project URLs
- http://www.openoffice.org
- http://incubator.apache.org/openofficeorg/

* Preferred day: Saturday or Sunday
- Saturday

* Why should FOSDEM accept this proposal?

After a period of reorganization at Apache, the OpenOffice project
managed to come back to a regular release schedule, is attracting new
volunteers and is now able to successfully engage them. Recent
contributions, like the donation of the Lotus Symphony code by IBM,
provide interesting challenges for new developers, and there are a lot
of tasks available for non-developers too.

An Apache OpenOffice devroom would allow existing volunteers to meet and
discuss future developments, and users and potential new volunteers to
learn how they can help the project, thanks to presentations and
hacking sessions spanning a broad range of topics.

The Apache OpenOffice project is definitely willing to consider a
possible suggestion by the organizers for a joint "ODF editors" devroom,
dedicated to Apache OpenOffice and to the other Free and Open Source
editors using OpenDocument as their native format.
---


Great draft: +1

Peter




The issue: who wants to own this? I have done that and worked with
fosdem for several years, as has Juergen, to whom I handed off the
task back in 2008 or 2009.


I just want to make sure we submit our application in time. I wrote the
draft above so that we have a concrete basis for discussion, and I'll
likely attend FOSDEM, as I've done quite regularly in recent years.

If nobody else steps up, I'll send the application after we have
consensus on it, but if anybody else wants to take over from now on,
it's absolutely OK for me, provided we meet the deadlines, i.e., we send
the application this week.

Regards,
   Andrea.

OpenOffice 3.4.1

[Errol Raymond]

Hi,

I am new to OpenOffice, and want to install the new version. I
currently have a imac-g5 ppc, and it is not supported on my
architecture. Is there anyway to get around this issue?

I would like to effectively install, and contribute to OpenOffice.

Thanks,

Errol

Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)

[sebb]

On 24 September 2012 22:35, Shane Curcuru  wrote:
> On 9/24/2012 7:34 AM, Rob Weir wrote:
> ...snip...
>
>> Is there any easy way to track PMC membership?  Maybe that be derived
>> from the authz for the eventual /pmc/openoffice tree?Eventually we
>> want an easy way to generate a roster that lists committers but also
>> identifies PMC members.
>
>
> TLPs have a slightly different way to track PMC members, specified here:
>
>   http://www.apache.org/dev/pmc.html#newpmc
>
> PMC membership is mostly an organizational thing, so I'm not sure there's a
> simple automated way to detect it.

Strictly speaking, PMC members are those that have been agreed by the board.
Either via TLP creation, or subsequent additions/removals which are
done via board request/ACK mails.

However, PMC chairs are supposed to keep the committee-info.txt and
LDAP committee groups up to date.

> However committers can view some of the
> great tools at whimsy, and I'd bet someone could find the code there that
> auto-parses both committer and PMC lists, and repurpose it to create an AOO
> specific page that could be public:

The people.apache.org pages (see else-thread) are public ...

>   https://whimsy.apache.org/
>
> There's a look under the hood link that takes you to the source in the infra
> SVN tree.
>
> - Shane

Re: [DISCUSS] [PMC] Proposed PMC List

[Andrea Pescetti]

On 24/09/2012 Jürgen Schmidt wrote:

On 9/24/12 10:26 AM, Ross Gardler wrote:

Just to confirm that I have received no offline nominations.


thanks for this info, it shows that the approach was not so wrong and we
had no real need for this additional option.


It's still good to have had this option, so we are sure that everybody 
who wanted to participate in the process had the opportunity to do so. 
And it's even better that in the end everybody decided to make their 
nomination in public.



I am looking forward to Andrew's summary and from my perspective we
should already start thinking what will be next?


Before moving on with all the steps you listed (and I agree with all of 
them) we will need to actually see the summary and derive the potential 
PMC from there. So far I've seen opinions ranging from including only 
the 10 most popular nominees to including everybody who received at 
least one nomination. Probably the best solution is somewhere in 
between, but once we have the summary the situation will probably be 
clearer.


Regards,
  Andrea.

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Louis Suárez-Potts]

On 12-09-24, at 15:32 , Andrea Pescetti  wrote:

> That would definitely be good for me too, and it's enough to declare in
> our application that we are available for such a solution. Note that
> there is no need for a joint proposal: FOSDEM organizers will collect
> the applications and, based on them, propose to co-organize the
> devrooms, see https://fosdem.org/2013/call_for_devrooms.html

The only urgency is to do this soonest, as that way the fosdem organizers can 
work with the understanding of our commitment here.

Louis

Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)

[Shane Curcuru]

On 9/24/2012 7:34 AM, Rob Weir wrote:
...snip...

Is there any easy way to track PMC membership?  Maybe that be derived
from the authz for the eventual /pmc/openoffice tree?Eventually we
want an easy way to generate a roster that lists committers but also
identifies PMC members.


TLPs have a slightly different way to track PMC members, specified here:

  http://www.apache.org/dev/pmc.html#newpmc

PMC membership is mostly an organizational thing, so I'm not sure 
there's a simple automated way to detect it.  However committers can 
view some of the great tools at whimsy, and I'd bet someone could find 
the code there that auto-parses both committer and PMC lists, and 
repurpose it to create an AOO specific page that could be public:


  https://whimsy.apache.org/

There's a look under the hood link that takes you to the source in the 
infra SVN tree.


- Shane

Re: Cancel Request for lazy Consensus. Was Re: [User Docs] What do we as a community want for user documentation or AOO)

[Kay Schenk]

On 09/23/2012 03:13 PM, Keith N. McKenna wrote:

Based on much feedback it appears that my enthusiasm got a little wild
and that re Reguest for lazy consensus was not the right approach.


Well I'm not sure I would say this...but...

 Given

that I hereby Rescind the Request or Lazy Consensus on the documentation
and will proceed to JFDI.


Great! I'm sure I speak for quite a few here that we're happy you have 
taken this lead and look forward to the results of the efforts of 
ODFAuthors on the 3.4.x documentation.


 For any that are interested in helping with

this effort more information on working at ODFAuthors can be obtained at
there website: http://www.odfauthors.org/

This will close this thread. Hopefully there will be more as the eort
progresses. Tank you all for your patience with my inexperience and your
guidance. It is truly appreciated.


Thanks again for taking the lead on resuming this effort. I think we'll 
be pleased to link this in when it's complete.




Regards
Keith



Keith N. McKenna wrote:

Keith N. McKenna wrote:

Greetings All;

In order to stimulate some discussion on user documentation I have added
the hollowing page to the User Documentation Plan on the Plannig Wiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/User+Guides+Revisted.


It offers 3 scenarios or the creation of the docs. I believe that we can
no longer put this issue aside.

Please take a look at the page and feel free to comment there and on
this
list. Also feel free to add to or change any content there.

Regards
Keith N. McKenna



Based on the discussion in this thread and on the wiki page it appears
for the short term that Scenario 2 is the best way to go. At this point
I would like to ask for lazy consensus to use ODFAuthors site and the
3.4 documents already there to create and publish updated documentation.
I will leave this open until 2012-09-26 at 05:45 UTC.

Regards
Keith N. McKenna








--

MzK

"Just 'cause you got the monkey off your back
 doesn't mean the circus has left town."
-- George Carlin

RE: LICENSE text in the user interface

[Dennis E. Hamilton]

Right you are.

I have no further concerns.  

 - Dennis



-Original Message-
From: Rob Weir [mailto:robw...@apache.org] 
Sent: Monday, September 24, 2012 12:59
To: ooo-dev@incubator.apache.org
Subject: Re: LICENSE text in the user interface

On Mon, Sep 24, 2012 at 2:45 PM, Dennis E. Hamilton  wrote:
> Oh.
>
> I thought it was *not* the practice of ASF to claim copyright over code.  It 
> is always weird to say all rights reserved and simultaneously offer a license.
>

It is Apache practice to claim copyright on the selection/arrangement
of the source files that comprise the distribution.  This is different
from the copyright on the individual source files in the same way as
the copyright on an anthology of poetry differs from the copyright on
each of the individual poems.

And there is nothing odd/wrong about reserving all rights and offering
a license at the same time.  In fact that is the normal combination.
Any rights not covered by the license are reserved to the copyright
holder(s).

> Is it necessary to include a copyright notice in the About box at all?  ASF 
> has no copyright on any of the source code.  Where is the original tangible 
> expression that has there be such a copyright here?
>

False premise.   Remember, the first line of our NOTICE file is
required to be the Apache copyright:
http://apache.org/legal/src-headers.html#notice   Putting it in the
about box is not making any new claims.  It is just making the claims
more evident.

In any case, if there are remaining doubts about this, II recommend
taking them to legal-discuss for a definitive response.

Regards,

-Rob

[ ... ]

Re: LICENSE text in the user interface

[Rob Weir]

On Mon, Sep 24, 2012 at 2:45 PM, Dennis E. Hamilton  wrote:
> Oh.
>
> I thought it was *not* the practice of ASF to claim copyright over code.  It 
> is always weird to say all rights reserved and simultaneously offer a license.
>

It is Apache practice to claim copyright on the selection/arrangement
of the source files that comprise the distribution.  This is different
from the copyright on the individual source files in the same way as
the copyright on an anthology of poetry differs from the copyright on
each of the individual poems.

And there is nothing odd/wrong about reserving all rights and offering
a license at the same time.  In fact that is the normal combination.
Any rights not covered by the license are reserved to the copyright
holder(s).

> Is it necessary to include a copyright notice in the About box at all?  ASF 
> has no copyright on any of the source code.  Where is the original tangible 
> expression that has there be such a copyright here?
>

False premise.   Remember, the first line of our NOTICE file is
required to be the Apache copyright:
http://apache.org/legal/src-headers.html#notice   Putting it in the
about box is not making any new claims.  It is just making the claims
more evident.

In any case, if there are remaining doubts about this, II recommend
taking them to legal-discuss for a definitive response.

Regards,

-Rob

>  - Dennis
>
>
>
> -Original Message-
> From: Rob Weir [mailto:robw...@apache.org]
> Sent: Monday, September 24, 2012 11:18
> To: ooo-dev@incubator.apache.org
> Subject: Re: LICENSE text in the user interface
>
> [ ... ]
>
> The about box already has this statement:
>
> "Copyright © 2012 Apache Software Foundation. All rights reserved."
>
> It would probably be fine to say, "Applicable licenses and notices for
> included 3rd party components can be found..." and then either have
> the path, URL or a button to bring up the details.
>
> [ ... ]
>

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Marcus (OOo)]

Am 09/24/2012 08:01 AM, schrieb Andrea Pescetti:

On 23/09/2012 Shenfeng Liu wrote:

3. Deliver milestone builds to harvest our development fruits. A
milestone
build is:
(a) a development snapshot that contains the features/enhancements
that implemented till now;
(b) passed regression test to ensure no severe defects;
(c) announced on a development wiki;
(d) with documents on the wiki for the list of features and bug fixes
in this milestone build (like a release notes).


Milestone builds are a good idea: they would not be the same as the
daily snapshots (which by the way are not yet available for all
platforms). I would add:

(e) available in all official supported languages, at least as langpack;

and make the builds available on a monthly basis, so they can be easily
identified and we can engage QA testers more effectively. This, of
course, unless people who provide the builds find it too time-consuming
to upload a build per month.


A clear +1 from me.

Marcus

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Andrea Pescetti]

Louis Suárez-Potts wrote:

On 12-09-24, at 10:52 , Rob Weir wrote:

Perhaps it could be de-politicized a little more if the request is
for an "ODF Editors" room, and do with multilateral, with LO,
Calligra, AbiWord, Gnumeric, etc.

I'm all for that and tried that in 2011 but not this year (2012).


That would definitely be good for me too, and it's enough to declare in
our application that we are available for such a solution. Note that
there is no need for a joint proposal: FOSDEM organizers will collect
the applications and, based on them, propose to co-organize the
devrooms, see https://fosdem.org/2013/call_for_devrooms.html

Going on, this is the request I would send, posted here for corrections
and lazy consensus. Note: the "Saturday" choice below is totally arbitrary.
   ---
* Devroom name: Apache OpenOffice

* Description

Apache OpenOffice, formerly known as OpenOffice.org, is one of the most
popular Free and Open Source software projects. The project, hosted by
the Apache Software Foundation since June 2011, had two successful
releases in 2012, with more than 16 million downloads in 4 months.
OpenOffice is developed by a large and diverse community, including
full-time and part-time core developers, translators, testers, user
experience experts, documentation contributors, developers of
third-party extensions and templates.

* Project URLs
- http://www.openoffice.org
- http://incubator.apache.org/openofficeorg/

* Preferred day: Saturday or Sunday
- Saturday

* Why should FOSDEM accept this proposal?

After a period of reorganization at Apache, the OpenOffice project
managed to come back to a regular release schedule, is attracting new
volunteers and is now able to successfully engage them. Recent
contributions, like the donation of the Lotus Symphony code by IBM,
provide interesting challenges for new developers, and there are a lot
of tasks available for non-developers too.

An Apache OpenOffice devroom would allow existing volunteers to meet and
discuss future developments, and users and potential new volunteers to
learn how they can help the project, thanks to presentations and
hacking sessions spanning a broad range of topics.

The Apache OpenOffice project is definitely willing to consider a
possible suggestion by the organizers for a joint "ODF editors" devroom,
dedicated to Apache OpenOffice and to the other Free and Open Source
editors using OpenDocument as their native format.
   ---


The issue: who wants to own this? I have done that and worked with
fosdem for several years, as has Juergen, to whom I handed off the
task back in 2008 or 2009.


I just want to make sure we submit our application in time. I wrote the
draft above so that we have a concrete basis for discussion, and I'll
likely attend FOSDEM, as I've done quite regularly in recent years.

If nobody else steps up, I'll send the application after we have
consensus on it, but if anybody else wants to take over from now on,
it's absolutely OK for me, provided we meet the deadlines, i.e., we send
the application this week.

Regards,
  Andrea.

Re: LICENSE text in the user interface

[Joost Andrae]

Hi,

a side note: IANAL, but in some countries legal texts have to be 
translated (eg. in France). Means, if you change something witin this 
area you have to accept this requirement.


Kind regards, Joost

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Marcus (OOo)]

Am 09/24/2012 03:13 PM, schrieb Ariel Constenla-Haile:

On Mon, Sep 24, 2012 at 07:56:26AM -0400, Rob Weir wrote:

Maybe also start a "release notes" page on the wiki.  Whenever a new
feature or important bug fix is added to the trunk also add something
to the release notes.   If something can be show with a "before and
after" screen shot, include that.  This might be easier than waiting
until the end to prepare the release notes.


We should come back to the old days, where there was a clear separation
between RC and Dev. Snapshot, see ooo-site/content/development/releases/
for example
http://www.openoffice.org/development/releases/DEV300m106_snapshot.html

I also think we should bring the Dev. Snapshot page back home, I'll try
to make a design with a left side bar, à la
http://www.openoffice.org/product/ and http://www.openoffice.org/why/
so that the download page (the forth, orange item) points to the same
site.


Thanks for bringing up this first. ;-)

When we could agree on to deliver dev builds on a regular basis (e.g., 
every 4 months) then we should offer them also from the main download 
page with clear wording. Like it was done it the previous project.


Marcus

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Marcus (OOo)]

Am 09/24/2012 08:01 AM, schrieb Andrea Pescetti:

On 23/09/2012 Shenfeng Liu wrote:

3. Deliver milestone builds to harvest our development fruits. A
milestone
build is:
(a) a development snapshot that contains the features/enhancements
that implemented till now;
(b) passed regression test to ensure no severe defects;
(c) announced on a development wiki;
(d) with documents on the wiki for the list of features and bug fixes
in this milestone build (like a release notes).


Milestone builds are a good idea: they would not be the same as the
daily snapshots (which by the way are not yet available for all
platforms). I would add:

(e) available in all official supported languages, at least as langpack;

and make the builds available on a monthly basis, so they can be easily
identified and we can engage QA testers more effectively. This, of
course, unless people who provide the builds find it too time-consuming
to upload a build per month.


A clear +1 from me.

Marcus

Re: LICENSE text in the user interface

[Marcus (OOo)]

Am 09/24/2012 08:17 PM, schrieb Rob Weir:

On Mon, Sep 24, 2012 at 1:10 PM, Ariel Constenla-Haile
  wrote:

Hi *,

The About dialog (menu Tools - Help - About OOo) on trunk has now
a button to display the README, LICENSE and NOTICE; you can try with the
following binaries:
Win: http://people.apache.org/~arielch/packages/r1389156/win/
Linux 64 bits:  http://ci.apache.org/projects/openoffice/



So a single button that launches all three in one window?


According to http://markmail.org/message/67kwkxcs5fubpua3 the LICENSE
has to fulfill some legal requirements and include the other licenses,
besides the ALv2. This results in a very large LICENSE file that cannot
be completely displayed in the UI inside a MultilineEdit control due to
a limitation in the tools String class, see STRING_MAXLEN in
tools/inc/tools/string.hxx

Possible solutions:

a) don't display the license at all, only the README and the NOTICE

b) display a stripped down version containing only the ALv2 and a last
paragraph telling to read the licenses from other components



The about box already has this statement:

"Copyright © 2012 Apache Software Foundation. All rights reserved."

It would probably be fine to say, "Applicable licenses and notices for
included 3rd party components can be found..." and then either have
the path, URL or a button to bring up the details.


c) simply add at the end of the text a note telling that the full text
can be found in the office installation

d) kill the tools String class, and use rtl::OUString everywhere
(someone will have to sit down and write the code for this)


Hm, depends on the effort and if it's really worth it.
However, only a core coder can realisitically estimate this. ;-)


e) ...<-- another options are welcome



e1) Launch them in OpenOffice, as (read-only) documents

e2) Launch via the default web browser


+1

In our Internet times nowadays this is IMHO the best solution. A browser 
window should be always opened.


Marcus




e3) Launch via default desktop handler for *.txt file extension





Regards
--
Ariel Constenla-Haile
La Plata, Argentina

Fw: [Plugtest-org] Invitation for the Berlin 2012 plugfest

[robert_weir]

Forwarded with the permission of the author, inviting members of the AOO 
community to attend this worthy event.

Regards,

-Rob

- Forwarded by Robert Weir/Cambridge/IBM on 09/24/2012 03:20 PM -

From:   Michiel Leenaars 
To: ODF Plugfest mailinglist , 
Cc: plugtest-organis...@opendocsociety.org
Date:   09/21/2012 08:45 AM
Subject:[Plugtest-org] Invitation for the Berlin 2012 plugfest
Sent by:plugtest-organisers-boun...@opendocsociety.org



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Dear recipient,


I have the pleasure to invite you on behalf of OpenDoc Society to
participate in the 9th ODF Plugfest, a two day interoperability event
on October 17th/18th 2012 kindly hosted by Bundesmin. fuer Wirtschaft
und Technologie. The event is held in conjunction with the annual
LibreOffice Conference, also to be held in Berlin at the same venue.

The ODF plugfests are a platform where different stakeholders around
Open Document Format join together to combine their knowledge and
technical experience on the details of ODF to improve product,
interoperability and in the end, customer satisfaction. Previous
plugfests have proven to be a useful instrument for vendors to
evaluate the interoperability between each others product in a
private setting.

On the first day a series of presentations will update you on the
status of ODF, present some new R&D projects and highlight
improvements and lessons learned in a number of implementations. On
the second day the actual testing will take place with vendors and
users going through several scenarios for creating and importing ODF
documents. Sitting side by side, the compatibility of documents
between applications in these scenario's can be easily checked and
openly discussed in the privacy of the workshop.

It is essential to have all stakeholders with an interest in ODF
engaged in furthering the implementation of ODF. We hope that you will
send a delegation or attend as a person, as well as participate
directly in the process.Past experience has shown developers and
technical management from larger and smaller vendors as well as
community leaders have valued the chance to attend and work on real
world interoperability.

The meeting host kindly asks you to register at http://odfplugfest.org
no later than October 8th, 2012, with your name and address. They
apologize for the inconvenience, which is due to security regulations
in ministry buildings. There is no fee required to participate in the
ODF plugfest, courtesy of OpenDoc Society. When you register, please
be so kind as to inform us in the comments in case you are registering
for the LibreOffice conference as well. This will help us to avoid
double registrations.

There are still some sponsor opportunities to help make the event even
more attractive, please contact OpenDoc Society for more details
(i...@opendocsociety.org). If you yourself are not able to attend this
plugfest, but are aware of other representatives from your
organisation that are, can you please forward this information to them?

We will gladly help you out with any questions, and are happy to
provide assistance with a visa application. Please visit:
http://odfplugfest.org or contact:

plugtest-organis...@opendocsociety.org

We hope to see you in Berlin!

Regards,

on behalf of the plugfest organisers
Michiel Leenaars
OpenDoc Society

N.B. If you want to host or help organise the 10th ODF plugfest, please
contact us at i...@opendocsociety.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBcYUkACgkQPPKB2FVlk19J0wCfT2vR8hmNuCGzc/UZm8V8UiDX
J1wAnilprbEY1ZtoPAxQgDkPDszb8Ber
=IuxB
-END PGP SIGNATURE-
___
plugtest-organisers mailing list
plugtest-organis...@opendocsociety.org
https://open.nlnet.nl/mailman/listinfo/plugtest-organisers

Re: svn commit: r1388877 - in /incubator/ooo/trunk/main: cui/source/dialogs/ cui/source/inc/ default_images/introabout/ default_images/res/ desktop/zipintro/ sd/source/ui/slideshow/ sfx2/inc/sfx2/ sfx

[Pavel Janík]

> * and the using declaration:
> 
>  using namespace com::sun::star;
> 
> The compiler should detect that system::XSystemShellExecute is
> com::sun::star::system::XSystemShellExecute and so on, unless it
> collides with a system namespace on the system's headers ? 
> 
> Anyway feel free to commit it, if this solves your problem.

I'll wait for other's opinions, because I too thought that it should work as 
written (using c:s:s), weird.

Other parts of the code use

namespace css = com::sun::star;
uno::Reference< css::system::XSystemShellExecute > xSystemShell(...

despite the fact that using namespace com::sun::star is there as well. Maybe 
"system" is somehow strange.

Any ideas about the strangeness? ;-)
-- 
Pavel Janík

Re: svn commit: r1388877 - in /incubator/ooo/trunk/main: cui/source/dialogs/ cui/source/inc/ default_images/introabout/ default_images/res/ desktop/zipintro/ sd/source/ui/slideshow/ sfx2/inc/sfx2/ sfx

[Ariel Constenla-Haile]

Hi Pavel,

On Mon, Sep 24, 2012 at 08:31:35PM +0200, Pavel Janík wrote:
> 
> On Sep 24, 2012, at 8:28 PM, Pavel Janík wrote:
> 
> > Hi,
> > 
> > the following change made about.cxx uncompilable on my system:
> > 
> > Compiling: cui/source/dialogs/about.cxx
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx: In 
> > member function ‘long int 
> > AboutDialog::OpenLinkHdl_Impl(svt::FixedHyperlink*)’:
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> > error: ‘system’ has not been declared
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> > error: ‘XSystemShellExecute’ was not declared in this scope
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> > error: template argument 1 is invalid
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> > error: invalid type in declaration before ‘(’ token
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:541: 
> > error: initializer expression list treated as compound expression
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:542: 
> > error: request for member ‘is’ in ‘xSystemShell’, which is of non-class 
> > type ‘int’
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
> > error: base operand of ‘->’ is not a pointer
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
> > error: ‘system’ has not been declared
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
> > error: ‘DEFAULTS’ was not declared in this scope
> > dmake:  Error code 1, while making '../../unxmacxi.pro/slo/about.obj'
> > ERROR: error 65280 occurred while making 
> > /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs
> 
> The following made it compile again:
> 
> Index: about.cxx
> ===
> --- about.cxx (revision 1389508)
> +++ about.cxx (working copy)
> @@ -534,13 +534,13 @@
>  {
>  uno::Reference< uno::XComponentContext > xContext =
>  ::comphelper::getProcessComponentContext();
> -uno::Reference< system::XSystemShellExecute > xSystemShell(
> +uno::Reference< com::sun::star::system::XSystemShellExecute > 
> xSystemShell(

it looks like this change shouldn't be needed at all:

* there are the include directives:

  #include 
  #include 

* and the using declaration:

  using namespace com::sun::star;

The compiler should detect that system::XSystemShellExecute is
com::sun::star::system::XSystemShellExecute and so on, unless it
collides with a system namespace on the system's headers ? 

Anyway feel free to commit it, if this solves your problem.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpTEaytWp3OJ.pgp
Description: PGP signature

RE: LICENSE text in the user interface

[Dennis E. Hamilton]

Oh.

I thought it was *not* the practice of ASF to claim copyright over code.  It is 
always weird to say all rights reserved and simultaneously offer a license.  

Is it necessary to include a copyright notice in the About box at all?  ASF has 
no copyright on any of the source code.  Where is the original tangible 
expression that has there be such a copyright here?

 - Dennis



-Original Message-
From: Rob Weir [mailto:robw...@apache.org] 
Sent: Monday, September 24, 2012 11:18
To: ooo-dev@incubator.apache.org
Subject: Re: LICENSE text in the user interface

[ ... ]

The about box already has this statement:

"Copyright © 2012 Apache Software Foundation. All rights reserved."

It would probably be fine to say, "Applicable licenses and notices for
included 3rd party components can be found..." and then either have
the path, URL or a button to bring up the details.

[ ... ]

Re: LICENSE text in the user interface

[Ariel Constenla-Haile]

On Mon, Sep 24, 2012 at 02:17:41PM -0400, Rob Weir wrote:
> On Mon, Sep 24, 2012 at 1:10 PM, Ariel Constenla-Haile
>  wrote:
> > Hi *,
> >
> > The About dialog (menu Tools - Help - About OOo) on trunk has now
> > a button to display the README, LICENSE and NOTICE; you can try with the
> > following binaries:
> > Win: http://people.apache.org/~arielch/packages/r1389156/win/
> > Linux 64 bits:  http://ci.apache.org/projects/openoffice/
> >
> 
> So a single button that launches all three in one window?

in one window, on a TabControl, with three tabs.

Giving access to the three items seemed to be the general outcome from
http://markmail.org/thread/ps624fynpzjnr65u Three buttons or links to
launch the three README, NOTICE and LICENSE didn't seem a good design,
so I've chosen a single button that executes a dialog with a TabControl,
with three tabs.

> e1) Launch them in OpenOffice, as (read-only) documents
> 
> e2) Launch via the default web browser
> 
> e3) Launch via default desktop handler for *.txt file extension

we already have an hyperlink control for the contributors page (though
rather updated), I'm not sure if there is room for 3 links more.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpthdxqQQ55f.pgp
Description: PGP signature

Re: svn commit: r1388877 - in /incubator/ooo/trunk/main: cui/source/dialogs/ cui/source/inc/ default_images/introabout/ default_images/res/ desktop/zipintro/ sd/source/ui/slideshow/ sfx2/inc/sfx2/ sfx

[Pavel Janík]

On Sep 24, 2012, at 8:28 PM, Pavel Janík wrote:

> Hi,
> 
> the following change made about.cxx uncompilable on my system:
> 
> Compiling: cui/source/dialogs/about.cxx
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx: In 
> member function ‘long int 
> AboutDialog::OpenLinkHdl_Impl(svt::FixedHyperlink*)’:
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> error: ‘system’ has not been declared
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> error: ‘XSystemShellExecute’ was not declared in this scope
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> error: template argument 1 is invalid
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
> error: invalid type in declaration before ‘(’ token
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:541: 
> error: initializer expression list treated as compound expression
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:542: 
> error: request for member ‘is’ in ‘xSystemShell’, which is of non-class type 
> ‘int’
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
> error: base operand of ‘->’ is not a pointer
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
> error: ‘system’ has not been declared
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
> error: ‘DEFAULTS’ was not declared in this scope
> dmake:  Error code 1, while making '../../unxmacxi.pro/slo/about.obj'
> ERROR: error 65280 occurred while making 
> /Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs

The following made it compile again:

Index: about.cxx
===
--- about.cxx   (revision 1389508)
+++ about.cxx   (working copy)
@@ -534,13 +534,13 @@
 {
 uno::Reference< uno::XComponentContext > xContext =
 ::comphelper::getProcessComponentContext();
-uno::Reference< system::XSystemShellExecute > xSystemShell(
+uno::Reference< com::sun::star::system::XSystemShellExecute > 
xSystemShell(
 xContext->getServiceManager()->createInstanceWithContext(
 rtl::OUString( RTL_CONSTASCII_USTRINGPARAM( 
"com.sun.star.system.SystemShellExecute" ) ),
 xContext ),
 uno::UNO_QUERY_THROW );
 if ( xSystemShell.is() )
-xSystemShell->execute( sURL, rtl::OUString(), 
system::SystemShellExecuteFlags::DEFAULTS );
+ xSystemShell->execute( sURL, rtl::OUString(), 
com::sun::star::system::SystemShellExecuteFlags::DEFAULTS );
 }
 catch( const uno::Exception& e )
 {

-- 
Pavel Janík

Re: svn commit: r1388877 - in /incubator/ooo/trunk/main: cui/source/dialogs/ cui/source/inc/ default_images/introabout/ default_images/res/ desktop/zipintro/ sd/source/ui/slideshow/ sfx2/inc/sfx2/ sfx

[Pavel Janík]

Hi,

the following change made about.cxx uncompilable on my system:

Compiling: cui/source/dialogs/about.cxx
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx: In 
member function ‘long int AboutDialog::OpenLinkHdl_Impl(svt::FixedHyperlink*)’:
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
error: ‘system’ has not been declared
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
error: ‘XSystemShellExecute’ was not declared in this scope
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
error: template argument 1 is invalid
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:537: 
error: invalid type in declaration before ‘(’ token
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:541: 
error: initializer expression list treated as compound expression
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:542: 
error: request for member ‘is’ in ‘xSystemShell’, which is of non-class type 
‘int’
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
error: base operand of ‘->’ is not a pointer
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
error: ‘system’ has not been declared
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs/about.cxx:543: 
error: ‘DEFAULTS’ was not declared in this scope
dmake:  Error code 1, while making '../../unxmacxi.pro/slo/about.obj'
ERROR: error 65280 occurred while making 
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/dialogs


On Sep 22, 2012, at 9:38 PM, arie...@apache.org wrote:

> Author: arielch
> Date: Sat Sep 22 19:38:56 2012
> New Revision: 1388877
> 
> URL: http://svn.apache.org/viewvc?rev=1388877&view=rev
> Log:
> #i119418# - About Dialog improvements

-- 
Pavel Janík

Re: LICENSE text in the user interface

[Rob Weir]

On Mon, Sep 24, 2012 at 1:10 PM, Ariel Constenla-Haile
 wrote:
> Hi *,
>
> The About dialog (menu Tools - Help - About OOo) on trunk has now
> a button to display the README, LICENSE and NOTICE; you can try with the
> following binaries:
> Win: http://people.apache.org/~arielch/packages/r1389156/win/
> Linux 64 bits:  http://ci.apache.org/projects/openoffice/
>

So a single button that launches all three in one window?

> According to http://markmail.org/message/67kwkxcs5fubpua3 the LICENSE
> has to fulfill some legal requirements and include the other licenses,
> besides the ALv2. This results in a very large LICENSE file that cannot
> be completely displayed in the UI inside a MultilineEdit control due to
> a limitation in the tools String class, see STRING_MAXLEN in
> tools/inc/tools/string.hxx
>
> Possible solutions:
>
> a) don't display the license at all, only the README and the NOTICE
>
> b) display a stripped down version containing only the ALv2 and a last
> paragraph telling to read the licenses from other components
>

The about box already has this statement:

"Copyright © 2012 Apache Software Foundation. All rights reserved."

It would probably be fine to say, "Applicable licenses and notices for
included 3rd party components can be found..." and then either have
the path, URL or a button to bring up the details.

> c) simply add at the end of the text a note telling that the full text
> can be found in the office installation
>
> d) kill the tools String class, and use rtl::OUString everywhere
> (someone will have to sit down and write the code for this)
>
> e) ... <-- another options are welcome
>

e1) Launch them in OpenOffice, as (read-only) documents

e2) Launch via the default web browser

e3) Launch via default desktop handler for *.txt file extension


>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina

Re: [DISCUSS] Repo in University Brazil

[Fernando Cassia]

On Mon, Sep 24, 2012 at 3:06 PM, Albino B Neto  wrote:

> We using the repository of Source Force, and is very good. But could
> has others. Ideas?
>
> 1 - ufes.br
> 2 - uvv.br
>

I think nobody can prevent you from creating local mirrors in the above
universities. However, SourceForge.net has its own set of mirrors, which
mirror the entire SourceForge repository.

So if you expect to create local mirrors only of AOO and have these
selected from the sourceforge.net servers, my guess is that it s
impossible, as sourceforge.net redirects based on its pool of SF.net
mirrors on a global (all projects) basis, not on a per-project basis.

BTW: there is a SF.net mirror in Brazil already, UFPR...

ufpr Centro de Computacao Cientifica e Software
Livre Curitiba,
Brazilhttp://sourceforge.net/apps/trac/sourceforge/wiki/Mirrors
FC

-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell

[DISCUSS] Repo in University Brazil

[Albino B Neto]

Hi

I am thinking created repository in an Federal University [1] of state
and private [2].

First I will have to contact IT staff and others. I have two answers
for universities: Yes and No.

I hope so. (:

We using the repository of Source Force, and is very good. But could
has others. Ideas?

1 - ufes.br
2 - uvv.br

Albino

Re: LICENSE text in the user interface

[Albino B Neto]

Hi.

On Mon, Sep 24, 2012 at 2:10 PM, Ariel Constenla-Haile
 wrote:
> Possible solutions:
>
> c) simply add at the end of the text a note telling that the full text
> can be found in the office installation

Understand. One of the most viable options, it could be this.

Albino

LICENSE text in the user interface

[Ariel Constenla-Haile]

Hi *,

The About dialog (menu Tools - Help - About OOo) on trunk has now
a button to display the README, LICENSE and NOTICE; you can try with the
following binaries:
Win: http://people.apache.org/~arielch/packages/r1389156/win/
Linux 64 bits:  http://ci.apache.org/projects/openoffice/

According to http://markmail.org/message/67kwkxcs5fubpua3 the LICENSE
has to fulfill some legal requirements and include the other licenses,
besides the ALv2. This results in a very large LICENSE file that cannot
be completely displayed in the UI inside a MultilineEdit control due to
a limitation in the tools String class, see STRING_MAXLEN in
tools/inc/tools/string.hxx

Possible solutions:

a) don't display the license at all, only the README and the NOTICE

b) display a stripped down version containing only the ALv2 and a last
paragraph telling to read the licenses from other components

c) simply add at the end of the text a note telling that the full text
can be found in the office installation

d) kill the tools String class, and use rtl::OUString everywhere
(someone will have to sit down and write the code for this)

e) ... <-- another options are welcome



Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpo9gTXfJUs3.pgp
Description: PGP signature

Re: [User Docs] What do we as a community want for user documentation or AOO

[Keith N. McKenna]

Juan C. Sanz wrote:

I think these documents are just a copy of OOo-3.3's ones with a new
template to use as a base for the new work, but as I can remember no
work has been made in them but in chapter one. Any case it is a good
point to start
Regards
Juan Carlos


Juan, I believe that Jean did a good deal of work in those before she 
stopped working on them. Then again I have been known to be wrong.




El 23/09/2012 23:57, Keith N. McKenna escribió:

Dennis E. Hamilton wrote:

Hey, let's get review of that document.  I didn't realized it had
been updated beyond being a placeholder for the needed document.

Where is it found on the ODFAUthors repository?

www.odfauthors.org/apache-openoffice/english/user-guides/getting-started-3.4/drafts

is where it resides. There are indivivual chapters and also a full
book. I believe that Jean has notes in the chapters of details she was
unsure of and other things. Chapter one is currently checked out to me
for a review.

Regards
Keith


  - Dennis

-Original Message-
From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
Sent: Sunday, September 23, 2012 12:39
To: ooo-dev@incubator.apache.org
Subject: Re: [User Docs] What do we as a community want for user
documentation or AOO

[ ... ]

... there is
a complete Getting Started Guide or AOO v3.4. The chapters are complete
and waiting for review.

[ ... ]

Re: [CODE] gmake and AOO build system

[Andrew Rist]

On 9/24/2012 4:39 AM, Andre wrote:

On 09/19/2012 09:58 PM, Pedro Giffuni wrote:

Hi Andrew;


- Original Message -
...
I have been provided patches necessary to apply the following CWSes 
to AOO

trunk:

ause131
ause130
writerfilter10
gnumake4
sd2gbuild

As I understand it this is mostly gbuild stuff that we did not want 
to apply to

3.4.x as it might destabilize the build.
This was provided to me by Michael Stahl, and represents work done 
by Oracle

emps when OOo was still at Oracle.

Is there any resistance from checking in these patches?  If I don't 
hear any
opposition in 72 hours and the patches cleanly apply on my dev area, 
I will

check in these changes.

Not an objection at this point but this is likely to break transitorily
the FreeBSD port.

It would be helpful to see the patches before they are applied.


Any news?  (I just came back from my vacation)


I put the patch up at
http://people.apache.org/~arist/patches/ooo-gbuild-cws-patches.tar.gz

A.



Andre



Pedro.




--

Andrew Rist | Interoperability Architect
OracleCorporate Architecture Group
Redwood Shores, CA | 650.506.9847

RE: [REQUEST] Apache OpenOffice (incubating) - fund allocation for ACEU 2012

[Lawrence Rosen]

Oliver-Rainer Wittmann wrote:
> The purpose of this post is to assure ASF's charity status

If you follow the procedures described by Ross Gardler and Chris Mattmann,
there will be no effect upon our non-profit status.  Worry not!

/Larry

Lawrence Rosen
Rosenlaw & Einschlag, a technology law firm (www.rosenlaw.com)
3001 King Ranch Rd., Ukiah, CA 95482
Office: 707-485-1242


-Original Message-
From: Mattmann, Chris A (388J) [mailto:chris.a.mattm...@jpl.nasa.gov] 
Sent: Monday, September 24, 2012 8:15 AM
To: Oliver-Rainer Wittmann
Cc: treasurer Treasurer; ooo-dev@incubator.apache.org;
plann...@apachecon.com; Ross Gardler; Melissa Warnkin; Jim Jagielski
Subject: Re: [REQUEST] Apache OpenOffice (incubating) - fund allocation for
ACEU 2012

Hi Oliver,

Thanks for your message! Comments below:

On Sep 24, 2012, at 4:48 AM, Oliver-Rainer Wittmann wrote:

> Hi ASF treasurer,
> 
> [Apache OpenOffice (incubating) community and ACEU planners on CC]
> 
> the Apache OpenOffice (incubating) community wants to spend some of its
fund for ApacheCon EU (ACEU) 2012 - see the corresponding thread on
ooo-dev@i.a.o [1].
> 
> We are currently discussing the granting processes - see [2].
> 
> The purpose of this post is to assure ASF's charity status and to clarify
the actual spending of the money regarding our planned fund allocation.
> We want to spend the following money for ACEU 2012 participants from the
Apache OpenOffice (incubating) community:
> - 10 x 300/600 EUR for travel expense subsidy
> - 30 x 100 EUR for ticket discounts for non-committers
> 
> Questions regarding assurence of charity status:
> (1) Do the planned spendings violate our charity status?

I'm not the person to definitively answer this -- I believe this has to do
with legal@ too, luckily the VP, Legal is also on the treasurer list :) so
he can help decide if there needs to be a legal@ CC here. To my knowledge
though, I think that you already have approval to proceed based on old
discussions I saw regarding this topic on board@, and also based on Ross
Gardler being a board@ guy and Apache OO mentor and bringing this up too.

> (2) What do we need to consider in our planned granting processes to
assure our charity status?

I think the most important thing is to make sure that the process is
traceable and auditable, IIRC.

> 
> Questions regarding actual spending of the money:
> (1) Is it possible to spend the "ticket discount" money via a special
promotion code in the ACEU 2012 ticket system?

Not sure about this :) The ApacheCon folks, or Mellissa, our EA, would
probably be good people to ask, so I've CC'ed Melissa here.


> (1a) If not, do you have any recommendation how the money should be spent?
> 
> (2) What are the possibilities to spend the "travel expense subsidy"
money?
> (2a) Do you have a recommendation how the money should be spent?

Regarding the above, I'd say come up with a process that is documented, you
guys decide how you want to spend it, come up with a Bill or someone to pay,
provide that information to the Treasurer@ list (me and Sam) and we'll move
forward with the approval process.

Right now, our bills are paid by having someone with the appropriate karma
put a file in:

https://svn.apache.org/repos/private/financials/Bills/received/

Then, they are reviewed by someone with the appropriate budget authority
(e.g., in Travel I believe that's Jim since he's the President) and then
placed in:

https://svn.apache.org/repos/private/financials/Bills/approved/

At that point, the Treasurer's office can pay the bill (via wire transfer;
electronic funds deposit, etc.) provided that all the information is given
to address the payee, and then once we pay, we move the bill into:

https://svn.apache.org/repos/private/financials/Bills/paid/

HTH!

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department University of
Southern California, Los Angeles, CA 90089 USA
++

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Louis Suárez-Potts]

Sylvain,

On 12-09-24, at 12:08 , Sylvain DENIS  wrote:

> Hello
> 
> I am not a developer but user and representative Apache OpenOffice Belgium. I 
> defend Apache OpenOffice in education in Belgium (french).
> I will at FOSDEM. This is an opportunity to meet and discuss even if my 
> English is approximate.
> 
Votre anglais c'est mieux que mon français, je pense :-) but how's your 
Flemish? :-)

I know and am friendly with Nicolas Pettiaux, of Uni. Libre de Bruxelles, who 
used to be with Open@Work and was (and remains, I hope) a strong proponent of 
ODF, open standards, and OpenOffice.

At the time we had our substantive discussions, back in 2008, I think, but 
maybe later, the issue of education and OO and ODF was crucial. My argument was 
and is that ODF and OO should be used and taught (coding) in post-secondary 
schools, but also used generally at all grades.

But little has happened. (Of course, this is also true of much bureaucratic 
movement in Belgium.) Still, I remain hopeful, especially as the issue of ODF 
in Belgium and in the EU at large is increasingly important and recognized as 
not only a vehicle for democratic goodness but also economic sanity.

I, at least, look forward to your kind help and contribution and hope we can 
make this event a really great event!

ciao
louis

> Regards
> 
> Sylvain DENIS
> 
> Le 24/09/12 13:20, Andrea Pescetti a écrit :
>> FOSDEM, one of the biggest Free and Open Source Software events in Europe, 
>> is coming again on 2-3 February 2013 in Brussels.
>> 
>> Attendance is free and, moreover, "Developer Rooms" can be made available 
>> upon request, but they must be requested before the end of September. See 
>> https://fosdem.org/2013/call_for_devrooms.html
>> 
>> I'm available to draft the application for an OpenOffice devroom and post it 
>> here on ooo-dev for lazy consensus, unless:
>> - Someone has already done it (just let us know)
>> - Apache manages applications in a centralized way
>> - No OpenOffice developers can attend (I would appreciate to know that we 
>> will have some full-time developers there)
>> - People believe it is useless (but FOSDEM is a big event and we shouldn't 
>> miss it, since by February we will probably have graduated and version 3.5 
>> could be approaching release).
>> 
>> Regards,
>>  Andrea. 
> 

Re: [User Docs] What do we as a community want for user documentation or AOO

[Juan C. Sanz]

I think these documents are just a copy of OOo-3.3's ones with a new 
template to use as a base for the new work, but as I can remember no 
work has been made in them but in chapter one. Any case it is a good 
point to start

Regards
Juan Carlos
El 23/09/2012 23:57, Keith N. McKenna escribió:

Dennis E. Hamilton wrote:
Hey, let's get review of that document.  I didn't realized it had 
been updated beyond being a placeholder for the needed document.


Where is it found on the ODFAUthors repository?
www.odfauthors.org/apache-openoffice/english/user-guides/getting-started-3.4/drafts 

is where it resides. There are indivivual chapters and also a full 
book. I believe that Jean has notes in the chapters of details she was 
unsure of and other things. Chapter one is currently checked out to me 
for a review.


Regards
Keith


  - Dennis

-Original Message-
From: Keith N. McKenna [mailto:keith.mcke...@comcast.net]
Sent: Sunday, September 23, 2012 12:39
To: ooo-dev@incubator.apache.org
Subject: Re: [User Docs] What do we as a community want for user 
documentation or AOO


[ ... ]

... there is
a complete Getting Started Guide or AOO v3.4. The chapters are complete
and waiting for review.

[ ... ]

Re: [REQUEST] Apache OpenOffice (incubating) - fund allocation for ACEU 2012

[Mattmann, Chris A (388J)]

Hi Oliver,

Thanks for your message! Comments below:

On Sep 24, 2012, at 4:48 AM, Oliver-Rainer Wittmann wrote:

> Hi ASF treasurer,
> 
> [Apache OpenOffice (incubating) community and ACEU planners on CC]
> 
> the Apache OpenOffice (incubating) community wants to spend some of its fund 
> for ApacheCon EU (ACEU) 2012 - see the corresponding thread on ooo-dev@i.a.o 
> [1].
> 
> We are currently discussing the granting processes - see [2].
> 
> The purpose of this post is to assure ASF's charity status and to clarify the 
> actual spending of the money regarding our planned fund allocation.
> We want to spend the following money for ACEU 2012 participants from the 
> Apache OpenOffice (incubating) community:
> - 10 x 300/600 EUR for travel expense subsidy
> - 30 x 100 EUR for ticket discounts for non-committers
> 
> Questions regarding assurence of charity status:
> (1) Do the planned spendings violate our charity status?

I'm not the person to definitively answer this -- I believe this has to do with 
legal@ too, luckily
the VP, Legal is also on the treasurer list :) so he can help decide if there 
needs to be a legal@
CC here. To my knowledge though, I think that you already have approval to 
proceed based on
old discussions I saw regarding this topic on board@, and also based on Ross 
Gardler being a 
board@ guy and Apache OO mentor and bringing this up too.

> (2) What do we need to consider in our planned granting processes to assure 
> our charity status?

I think the most important thing is to make sure that the process is traceable 
and auditable, IIRC.

> 
> Questions regarding actual spending of the money:
> (1) Is it possible to spend the "ticket discount" money via a special 
> promotion code in the ACEU 2012 ticket system?

Not sure about this :) The ApacheCon folks, or Mellissa, our EA, would probably 
be
good people to ask, so I've CC'ed Melissa here.


> (1a) If not, do you have any recommendation how the money should be spent?
> 
> (2) What are the possibilities to spend the "travel expense subsidy" money?
> (2a) Do you have a recommendation how the money should be spent?

Regarding the above, I'd say come up with a process that is documented, you 
guys decide how
you want to spend it, come up with a Bill or someone to pay, provide that 
information
to the Treasurer@ list (me and Sam) and we'll move forward with the approval 
process.

Right now, our bills are paid by having someone with the appropriate karma put 
a file in:

https://svn.apache.org/repos/private/financials/Bills/received/

Then, they are reviewed by someone with the appropriate budget authority (e.g., 
in Travel I 
believe that's Jim since he's the President) and then placed in:

https://svn.apache.org/repos/private/financials/Bills/approved/

At that point, the Treasurer's office can pay the bill (via wire transfer; 
electronic funds deposit, etc.)
provided that all the information is given to address the payee, and then once 
we pay, we
move the bill into:

https://svn.apache.org/repos/private/financials/Bills/paid/

HTH!

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Sylvain DENIS]

Hello

I am not a developer but user and representative Apache OpenOffice 
Belgium. I defend Apache OpenOffice in education in Belgium (french).
I will at FOSDEM. This is an opportunity to meet and discuss even if my 
English is approximate.


Regards

Sylvain DENIS

Le 24/09/12 13:20, Andrea Pescetti a écrit :
FOSDEM, one of the biggest Free and Open Source Software events in 
Europe, is coming again on 2-3 February 2013 in Brussels.


Attendance is free and, moreover, "Developer Rooms" can be made 
available upon request, but they must be requested before the end of 
September. See https://fosdem.org/2013/call_for_devrooms.html


I'm available to draft the application for an OpenOffice devroom and 
post it here on ooo-dev for lazy consensus, unless:

- Someone has already done it (just let us know)
- Apache manages applications in a centralized way
- No OpenOffice developers can attend (I would appreciate to know that 
we will have some full-time developers there)
- People believe it is useless (but FOSDEM is a big event and we 
shouldn't miss it, since by February we will probably have graduated 
and version 3.5 could be approaching release).


Regards,
  Andrea. 

Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)

[sebb]

On 24 September 2012 13:50, Dave Fisher  wrote:
>
> On Sep 24, 2012, at 4:34 AM, Rob Weir wrote:
>
>> On Mon, Sep 24, 2012 at 5:37 AM, sebb  wrote:
>>> On 24 September 2012 03:50, Rob Weir  wrote:
 On Sep 23, 2012, at 10:15 PM, "Dennis E. Hamilton"  
 wrote:

> Rob,
>
> I recently took a look at 
>  to see if I 
> could derive that list from the Roster.
>
> What gave me pause is that the list is apparently maintained in XML.  I 
> could not find anywhere that MarkDown is used.  Is that correct?
>

 Correct.  It is XML. It used to require that I check out the whole
 directory, update the XML, run an ant script to generate the HTML and
 then check in both the XML and HTML.  This is much simplified by the
 CMS which does the template generation behind the scenes.


> I could still mechanically derive the XML elements that are used now, 
> although it is a bit more complicated than search and replace on a CSV of 
> an extract of the roster.  If I were to do that, I would also indicate 
> who is on the PPMC.
>
> Any suggestions?

 I'm not sure we need to maintain that "status file" once we graduate.
 I think it is more of a podling tracking thing. So it might be
>>>
>>> Yes, it is for active podlings only. No need to update it once
>>> graduated, though it does need to be completed before graduation.
>>>
>>> The other file that needs to be updated by podlings is podlings.xml.
>>>
>>> Note that
>>>
>>> http://people.apache.org/committers-by-project.html#ooo
>>>
>>> is created automatically from the SVN authz file (where podling
>>> committers are listed) plus LDAP groups.
>>>
 simplest if we just manually update it for now.  But longer term it
 would be good to be able to generate a page for the project website
 from the Roster.   The ODF Toolkit has an XSLTRunner component that
 could be used for this.
>>>
>>> Not sure that's necessary. You could just link to the appropriate
>>> sections in the above file.
>>>
>>
>> Is there any easy way to track PMC membership?  Maybe that be derived
>> from the authz for the eventual /pmc/openoffice tree?Eventually we
>> want an easy way to generate a roster that lists committers but also
>> identifies PMC members.
>
> Sebb answered, but sometimes examples are needed. PMCs have authz as well. 
> Here is the page for the POI PMC:
>
> http://people.apache.org/committers-by-project.html#poi-pmc

Note that this is derived from the LDAP committee group, but AIUI the
canonical location for PMC membership is

https://svn.apache.org/repos/private/committers/board/committee-info.txt

The LDAP group needs to be kept in sync with the above file; updating
both is the responsibility of the PMC chair (who will have sufficient
karma).

> Regards,
> Dave
>
>>
>> -Rob
>>
>>
 -Rob

>
> - Dennis
>
> -Original Message-
> From: Rob Weir [mailto:robw...@apache.org]
> Sent: Sunday, September 23, 2012 17:41
> To: ooo-dev@incubator.apache.org
> Subject: Re: New committer: Chen ZuoJun
>
> On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton  
> wrote:
>> The Apache OpenOffice PPMC announces the addition of committer
>> Chen ZuoJun, zjchen@ apache.org
>>
>> The list of all current podling committers is at:
>> .
>
> And one other place:  
> http://incubator.apache.org/projects/openofficeorg.html
>
> That page is part of the IPMC's tracking of podling status and feeds
> into their "Status of the Clutch" report:
> http://incubator.apache.org/clutch.html
>
> Some may recall that we had a reporter use the "status of the clutch"
> report to claim that the project was not growing.  That was when we
> were not updating the report.  Since that is the official IPMC view of
> the podlings, it is important that we keep this information
> up-to-date, until the project graduates.
>
> I was updating this status page whenever a new committer was voted in.
> It would be great if someone else could take this over now.
>
> When a new committer is added, the status file needs to be updated in
> two places.
>
> 1) Added as a News item.  Automation depends on the wording, so don't
> be clever.  Just follow the examples there.
>
> 2) Added in the list of committers.
>
> This can most easily be edited via the Apache CMS.
>
> [ ... ]
>
>

Re: [DISCUSS] granting processes for fund allocation for ACEU 2012

[imacat]

Thank you for the hard work for this detailed plan.

On 2012/09/24 19:01, Oliver-Rainer Wittmann said:
> Hi,
> 
> I would like to discuss how the grainting processes for fund allocation
> for ApacheCon EU (ACEU) 2012 could work.
> Two processes are needed. One for granting travel expense subsidy and
> one for ticket discount for non-committers of the OpenOffice community.
> 
> The goal is to reach (lazy) consensus on the granting processes in the
> next 72 hours.
> 
> Here are my ideas regarding such processes:
> (1) ticket discount for non-committers:
> - 30 x 100 EUR ticket discount for non-committers can be granted.
> 
> - To apply for the ticket discount people should send post to
> ooo-private. The details should be:
> -- subject = [ACEU 2012 - ticket discount] 
> -- content:
> --- full name
> --- email address
> --- affiliation to the OpenOffice community (something like: "user",
> "contributing X", "translator", ...)
> --- description why applying for the ticket discount and why support is
> needed.
> --- job or eduation status (something like: "student", "employee",
> "freeflancer", ...)
> 
> - Announce on our mailing lists and in our forum that application
> process is open until  -  should be at
> least 7 days ahead of the .
> 
> - The small group of volunteers collect the applications. The group
> selects not more than 30 and post the decision details on ooo-private.
> The selection process should not take more than 2 days.
> The selection shall be based on the given description and the
> job/eduation status.
> 
> - Send out corresponding notifications and details how to get the ticket
> discount.
> 
> [Note: I will get in contact with ACEU 2012 planners, if it is possible
> to get a promotion code for our ticket discount.]
> [Another note: I will get in contact with treasu...@apache.org to assure
> ASF's charity status and clarify the actual spending of the money]
> 
> 
> (2) travel expense subsidy for OpenOffice community members:
> - 10 x 300 resp. 600 EUR travel expense subsidy can be granted.
> 
> - To apply for the travel expense subsidy people should send a post to
> ooo-private. The details should be:
> -- subject = [ACEU 2012 - travel subsidy] 
> -- content:
> --- full name
> --- email address
> --- affiliation to the OpenOffice community (something like:
> "committer", "user", "contributing X", "translator", ...)
> --- Apache ID (if available)
> --- accepted or stand-by speaker at ACEU?
> --- description why applying for the travel expense subsidy and why
> support is needed.
> --- job or eduation status (something like: "student", "employee",
> "freelancer", ...)
> --- estimated travel expense
> --- estimated needed accommodation - # of nights
> --- other available funding (something like: "corporate", "ACEU - TAC",
> ...)
> --- applying for 300 EUR or 600 EUR?
> 
> - Announce on our mailing lists and in our forum that application
> process is open until  -  should be at
> least 7 days ahead of the .
> 
> - The small group of volunteers collect the applications. The group
> selects not more than 10 and post the decision details on ooo-private.
> The selection process should not take more than 3 days.
> The selection should consider the following:
> -- Application shall hold the following conditions, otherwise it is invalid
> --- no corporate funding and no TAC funding
> --- travel expense must be at least 300 EUR
> --- accommodation needed for at least 2 nights
> -- The selection shall be based on the given description and the
> job/eduation status.
> -- Applications are selected in the following order:
> --- invited (accepted or stand-by) speakers
> --- committers
> --- non-committers
> 
> - Send out corresponding notifications and details how to get the ticket
> discount.
> 
> [Note: I will get in contact with treasu...@apache.org to assure ASF's
> charity status and clarify the actual spending of the money.]
> 
> 
> Please provide your input.
> 
> 
> Best regards, Oliver.


-- 
Best regards,
imacat ^_*' 
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
Apache OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/
Greenfoot Taiwan http://greenfoot.westart.tw/



signature.asc
Description: OpenPGP digital signature

Re: [REQUEST] Apache OpenOffice (incubating) - fund allocation for ACEU 2012

[Ross Gardler]

On 24 September 2012 17:14, Mattmann, Chris A (388J)
 wrote:
> On Sep 24, 2012, at 4:48 AM, Oliver-Rainer Wittmann wrote:
>

...

>> the Apache OpenOffice (incubating) community wants to spend some of its fund 
>> for ApacheCon EU (ACEU) 2012 - see the corresponding thread on ooo-dev@i.a.o 
>> [1].
>>
>> We are currently discussing the granting processes - see [2].
>>
>> The purpose of this post is to assure ASF's charity status and to clarify 
>> the actual spending of the money regarding our planned fund allocation.
>> We want to spend the following money for ACEU 2012 participants from the 
>> Apache OpenOffice (incubating) community:
>> - 10 x 300/600 EUR for travel expense subsidy
>> - 30 x 100 EUR for ticket discounts for non-committers
>>
>> Questions regarding assurence of charity status:
>> (1) Do the planned spendings violate our charity status?
>
> I'm not the person to definitively answer this -- I believe this has to do 
> with legal@ too, luckily
> the VP, Legal is also on the treasurer list :) so he can help decide if there 
> needs to be a legal@
> CC here. To my knowledge though, I think that you already have approval to 
> proceed based on
> old discussions I saw regarding this topic on board@, and also based on Ross 
> Gardler being a
> board@ guy and Apache OO mentor and bringing this up too.

I don't speak for the board, however, the board did approve the
principle of using SPI money for this. I've checked with Jim as
President and he confirms that he see's no problem. The treasurer list
was copied on that communication and I reported it back to the ooo-dev
list. In summary, I believe we are good to go (said with my EVP hat
since Jim spoke with his Pres hat so it's my problem if this is bad
information)

>> (2) What do we need to consider in our planned granting processes to assure 
>> our charity status?
>
> I think the most important thing is to make sure that the process is 
> traceable and auditable, IIRC.

That is correct. We should also add fair and non-discriminatory. The
applications process and evaluation process needs to be public (I'm
assuming this is not a needs based evaluation, if it is needs based it
will be more complex as privacy is also necessary).

>> Questions regarding actual spending of the money:
>> (1) Is it possible to spend the "ticket discount" money via a special 
>> promotion code in the ACEU 2012 ticket system?
>
> Not sure about this :) The ApacheCon folks, or Mellissa, our EA, would 
> probably be
> good people to ask, so I've CC'ed Melissa here.

Yes, it is possible. What we need to know (send to plann...@apachecon.com) is:

- ticket name
- discount code
- discount level
- promotion start and end dates

Ross

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Louis Suárez-Potts]

On 12-09-24, at 10:52 , Rob Weir  wrote:
>>> 
>>> Depending on the feedback of the organizers I can also think about a
>>> joined devroom with the LibreOffice folks. Space for devrooms is limited
>>> and I can of course think about a joined effort here. I am at least open
>>> for this if wanted.
>> 
>> We have previously thought and discussed this option, of a joint room. It'd 
>> be great, I think, but also interesting to arrange. Given the realities, 
>> perhaps propose this idea but also hold open the idea of a devroom specific 
>> to AOO? Previously, I had advocated this idea, only to learn that TDF had 
>> also gone ahead with it—but there's room there, too, for collaboration. Or, 
>> another option that relates interestingly to what we are doing at AOO that 
>> can be of wider interest.
>> 
> 
> Perhaps it could be de-politicized a little more if the request is for
> an "ODF Editors" room, and do with multilateral, with LO, Calligra,
> AbiWord, Gnumeric, etc.
> 

I'm all for that and tried that in 2011 but not this year (2012). Given our new 
identity, I'm more hopeful that it could be done.

The issue: who wants to own this? I have done that and worked with fosdem for 
several years, as has Juergen, to whom I handed off the task back in 2008 or 
2009.

Louis

Re: [CODE] gmake and AOO build system

[Pedro Giffuni]

Welcome back Andre;


- Original Message -
> 
> On 09/19/2012 09:58 PM, Pedro Giffuni wrote:
>>  Hi Andrew;
>> 
>> 
>>  - Original Message -
>>  ...
>>>  I have been provided patches necessary to apply the following CWSes to 
> AOO
>>>  trunk:
>>> 
>>>      ause131
>>>      ause130
>>>      writerfilter10
>>>      gnumake4
>>>      sd2gbuild
>>> 
>>>  As I understand it this is mostly gbuild stuff that we did not want to 
> apply to
>>>  3.4.x as it might destabilize the build.
>>>  This was provided to me by Michael Stahl, and represents work done by 
> Oracle
>>>  emps when OOo was still at Oracle.
>>> 
>>>  Is there any resistance from checking in these patches?  If I don't 
> hear any
>>>  opposition in 72 hours and the patches cleanly apply on my dev area, I 
> will
>>>  check in these changes.
>>>   
>>  Not an objection at this point but this is likely to break transitorily
>>  the FreeBSD port.
>> 
>>  It would be helpful to see the patches before they are applied.
> 
> Any news?  (I just came back from my vacation)
> 

No news yet. I think if there is breakage either Maho or I can fix it
as long as the three main platforms continue working.

Pedro.

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Rob Weir]

On Mon, Sep 24, 2012 at 10:47 AM, Louis Suárez-Potts  wrote:
>
> On 12-09-24, at 07:59 , Jürgen Schmidt  wrote:
>
>> On 9/24/12 1:20 PM, Andrea Pescetti wrote:
>>> FOSDEM, one of the biggest Free and Open Source Software events in
>>> Europe, is coming again on 2-3 February 2013 in Brussels.
>>>
>>> Attendance is free and, moreover, "Developer Rooms" can be made
>>> available upon request, but they must be requested before the end of
>>> September. See https://fosdem.org/2013/call_for_devrooms.html
>>>
>>> I'm available to draft the application for an OpenOffice devroom and
>>> post it here on ooo-dev for lazy consensus, unless:
>>> - Someone has already done it (just let us know)
>>> - Apache manages applications in a centralized way
>>> - No OpenOffice developers can attend (I would appreciate to know that
>>> we will have some full-time developers there)
>>> - People believe it is useless (but FOSDEM is a big event and we
>>> shouldn't miss it, since by February we will probably have graduated and
>>> version 3.5 could be approaching release).
>>>
>>
>> OpenOffice was there present for many years and it can be of course an
>> opportunity to reach out to other open source developers there.
>
> fosdem is very important.
>>
>> Depending on the feedback of the organizers I can also think about a
>> joined devroom with the LibreOffice folks. Space for devrooms is limited
>> and I can of course think about a joined effort here. I am at least open
>> for this if wanted.
>
> We have previously thought and discussed this option, of a joint room. It'd 
> be great, I think, but also interesting to arrange. Given the realities, 
> perhaps propose this idea but also hold open the idea of a devroom specific 
> to AOO? Previously, I had advocated this idea, only to learn that TDF had 
> also gone ahead with it—but there's room there, too, for collaboration. Or, 
> another option that relates interestingly to what we are doing at AOO that 
> can be of wider interest.
>

Perhaps it could be de-politicized a little more if the request is for
an "ODF Editors" room, and do with multilateral, with LO, Calligra,
AbiWord, Gnumeric, etc.


>
>>
>> I will support any activities and will probably join the conference.
>> FOSDEM is a nice event and it makes always fun to meet so many open
>> source freaks. I can only recommend it from this perspective and it is
>> always on a weekend.
>>
>> Juergen
>>
>>
> Fosdem is immensely important. It might also truly offer us here at AOO 
> opportunity to find means to collaborate with TDF/LibreOffice. Personally, 
> I'd like something like that, as I think we probably can help endusers better 
> by such collaboration.
>
> Louis
>

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Louis Suárez-Potts]

On 12-09-24, at 07:59 , Jürgen Schmidt  wrote:

> On 9/24/12 1:20 PM, Andrea Pescetti wrote:
>> FOSDEM, one of the biggest Free and Open Source Software events in
>> Europe, is coming again on 2-3 February 2013 in Brussels.
>> 
>> Attendance is free and, moreover, "Developer Rooms" can be made
>> available upon request, but they must be requested before the end of
>> September. See https://fosdem.org/2013/call_for_devrooms.html
>> 
>> I'm available to draft the application for an OpenOffice devroom and
>> post it here on ooo-dev for lazy consensus, unless:
>> - Someone has already done it (just let us know)
>> - Apache manages applications in a centralized way
>> - No OpenOffice developers can attend (I would appreciate to know that
>> we will have some full-time developers there)
>> - People believe it is useless (but FOSDEM is a big event and we
>> shouldn't miss it, since by February we will probably have graduated and
>> version 3.5 could be approaching release).
>> 
> 
> OpenOffice was there present for many years and it can be of course an
> opportunity to reach out to other open source developers there.

fosdem is very important. 
> 
> Depending on the feedback of the organizers I can also think about a
> joined devroom with the LibreOffice folks. Space for devrooms is limited
> and I can of course think about a joined effort here. I am at least open
> for this if wanted.

We have previously thought and discussed this option, of a joint room. It'd be 
great, I think, but also interesting to arrange. Given the realities, perhaps 
propose this idea but also hold open the idea of a devroom specific to AOO? 
Previously, I had advocated this idea, only to learn that TDF had also gone 
ahead with it—but there's room there, too, for collaboration. Or, another 
option that relates interestingly to what we are doing at AOO that can be of 
wider interest.


> 
> I will support any activities and will probably join the conference.
> FOSDEM is a nice event and it makes always fun to meet so many open
> source freaks. I can only recommend it from this perspective and it is
> always on a weekend.
> 
> Juergen
> 
> 
Fosdem is immensely important. It might also truly offer us here at AOO 
opportunity to find means to collaborate with TDF/LibreOffice. Personally, I'd 
like something like that, as I think we probably can help endusers better by 
such collaboration.

Louis

Re: Hi, AOO 3.4.1 build breaks in Windows XP

[Ariel Constenla-Haile]

Hi,

On Mon, Sep 24, 2012 at 10:51:16AM +0530, tapas wrote:
> Hi Schrieb/ALL,
> 
> I also put same things. But I am facing build problem to build it in
> windows.

note that I've just followed the building guide to set up the
environment, and it worked with:

* MS Visual C++ 2008 Express Edition
* MS Driver Kit 7 (for ATL/ActiveX)
* cygwin set up with http://cygwin.com/setup.exe on Saturday (no idea
  what version will it be, I assume the latest)


> Could please send me atleast below things:
> 1) configure command

http://people.apache.org/~arielch/packages/r1389156/win/dev/config.cmdops
http://people.apache.org/~arielch/packages/r1389156/win/dev/config.parms

> 2) cygwin version

I assume the latest, downloaded on Saturday, set up following the
instructions on the building guide.


> 3) out put of configure command in cygwin shell

I didn't save that, but there is the log:
http://people.apache.org/~arielch/packages/r1389156/win/dev/config.log

> 4) svn revision number of your source tree

rev. 1389156 as the binaries you can find there
http://people.apache.org/~arielch/packages/r1389156/win/

> 5) contents of cygwin path variable in cygwin shell.

*before* sourcing winenv.set.sh

echo $PATH
/usr/local/bin:/usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows

After sourcing winenv.set.sh PATH is set to the value exported in that
script.


> 6) win_env_set.sh file produced by your configure command

http://people.apache.org/~arielch/packages/r1389156/win/dev/winenv.set.sh


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgp5xsu93APMG.pgp
Description: PGP signature

Re: [DISCUSS] [PMC] Proposed PMC List

[Jürgen Schmidt]

On 9/24/12 10:26 AM, Ross Gardler wrote:
> Just to confirm that I have received no offline nominations.

thanks for this info, it shows that the approach was not so wrong and we
had no real need for this additional option.

I am looking forward to Andrew's summary and from my perspective we
should already start thinking what will be next?

This approach as one of many possible approaches to create a PMC list
will have brought us to a list of names. A list of names where the
majority can live with of better which the majority want to have in a
PMC. I believe that this list would be similar to any other outcome of
any other approach we would have taken and I think we should take it. We
have made clear several times that the PMC will grow over time and that
the initial PMC is only a start.

One possible way to move forward is
1. once we have the collected list, we will ask everybody if she/he is
interested to become a final PMC member or not. We should take known
vacation times into account.

2. As result if 1. we will have a PMC list where we can start with for
the graduation.

3. Start thinking of a good candidate for the PMC chair. Probably
somebody of the list but not necessarily. I would accept any other
nomination but that is probably unlikely.

4. Start voting on the PMC chair

5. Finalize (enhance, complete, ...) our Graduation Resolution [1]
This can be done in parallel if we think something important is missing
or should be added.

6. Continue with the graduation.

7. Keep it simply and don't make it to complicate.


Regarding 6.
I think we have successfully voted on the graduation already and I
believe that we should continue on this. We received feedback and
concerns from our mentors and are working on these stuff. But this is
ongoing and not really easy to measure because it was not really
detailed and more general. The best way to demonstrate that we are ready
is to continue and move forward things that we have to do anyway and
that will help us on different levels. And one of this is graduation!

If still anybody has serious concerns that we should not graduate I
would require that it is put on the table *NOW* and here on the public
list that everybody can see it. And we should require that potential
concerns are detailed enough that we can work on it. Everything else is
wasted time from my point of view.


So let us move forward together

Juergen



[1
https://cwiki.apache.org/confluence/display/OOOUSERS/Graduation+Resolution+%28draft%29


> 
> Sent from my tablet
> On Sep 19, 2012 12:00 AM, "Andrew Rist"  wrote:
> 
>> (top posting after private messages - I cannot describe the shame I
>> feel...  ;-)
>>
>> I have an option that I believe will handle Andrea's concerns.  I have
>> spoken with Ross and he is amenable to receiving Proposed PMC entries off
>> list.
>> If anyone is concerned about sending their list to ooo-dev, you can send
>> it to Ross ( rgardler at apache) instead, and at the end of the period
>> (next Sunday), he will send an anonymized summary of the votes he has
>> received, along with a breakdown of submissions by committers/PPMC vs other
>> community members.
>>
>> We have received lists from 10 people and have 25 nominees with multiple
>> votes.  It would be great to get even more feedback.
>>
>> A.
>>
>>
>>
>> On 9/18/2012 1:17 PM, Andrea Pescetti wrote:
>>
>>> On 17/09/2012 Andrew Rist wrote:
>>>
 * This is not a vote. This is a search for consensus. Please no '-1'
 replies. Let's see what this process produces, and then discuss
 from there.

>>>
>>> It seems that the process is working quite well, and that we are on the
>>> right way to bootstrap a PMC by consensus.
>>>
>>> I surely don't want to block the current process, but I wonder if
>>> allowing people to "vote" (actually, express preferences) anonymously would
>>> be better for some volunteers/cultures. Our mentors have often stated that
>>> we have secure voting solutions available, but maybe this is overkill and
>>> time-consuming, and it would be enough to allow people to send their lists
>>> to a mentor (if available), who would repost them here.
>>>
>>> It is not an issue that I feel personally: it's OK for me to continue
>>> with public messages on ooo-dev. But it could be that others have problems,
>>> and in that case I'd encourage them to speak up so that we can find a way
>>> to ensure that everyone can express their opinions.
>>>
>>> Regards,
>>>   Andrea.
>>>
>>
>>
> 

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Keith N. McKenna]

Rob Weir wrote:

On Mon, Sep 24, 2012 at 8:59 AM, Keith N. McKenna
 wrote:

Rob Weir wrote:


On Sun, Sep 23, 2012 at 10:13 AM, Shenfeng Liu  wrote:


Hi, all,
After 3.4.1, we are focusing on preparation of the community
graduation.
But I still want to remind us to take some time to think about our future
releases.

We have the discussion early about what 3.5 and 4.0 should look like.
If
I remember correctly:
(1) 3.5 should be more about fidelity, reliability, performance and
translation, new platform support...
(2) While 4.0, in addition to the same focuses as 3.5, should also add
significant UX enhancements (e.g. sidebar, modern UI) and new values
(e.g.
Accessibility, social integration capability, enhanced installer, new
features...). If we make good progress on those items at the same time,
we
may consider to skip 3.5.
(3) There are also more requirements (e.g. fixpack mechanism, simplifying
the build structure, OOMXL export, smartArt...) we need  to put into our
backlog and consider their priority.

Even we don't need to discuss the solid plan now, but there are
already a
lot of development activities on the trunk. So I think we need to keep
certain track on it. Though it may be too early to set a target date for
the next release, but it is important for us to tell more about what we
think the next release should contain.

So I'm suggesting the following:

1. Keep updating the current release planning wiki:
   -

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.5+Release+Planning
   -

https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning
 I know it is a little confusing for 2 places to input. But think
about
the scope we agreed above. You can input to the wiki that you think your
work belong to. I personally will monitor both wiki pages.

2. Figure out a better way to manage our release backlog. e.g. set Target
Milestone to 3.5 or 4.0 in Bugzilla for what we recommended.

3. Deliver milestone builds to harvest our development fruits. A
milestone
build is:
   (a) a development snapshot that contains the features/enhancements
that implemented till now;
   (b) passed regression test to ensure no severe defects;
   (c) announced on a development wiki;
   (d) with documents on the wiki for the list of features and bug
fixes
in this milestone build (like a release notes).
 Since whatever 3.5 or 4.0 sounds to me like some thing in next year
or
at least close to the end of this year, milestone builds can be light
weigh
on process to show our development progress, and give people a more clear
view on how far are we to the next release.

Looking forward every one's comments!



Maybe also start a "release notes" page on the wiki.  Whenever a new
feature or important bug fix is added to the trunk also add something
to the release notes.   If something can be show with a "before and
after" screen shot, include that.  This might be easier than waiting
until the end to prepare the release notes.

-Rob



- Simon




Rob;

A Release Notes page already exists or 3.5 and one or 4.0 can be easily
added. The complication I see here is since we have not decided whether the
next release will be 3.5 or 4.0 that would require adding it in two places.
I see that as a lot of overhead at this point.



IMHO, the name is not so important.  Everything in the trunk goes into
the next release.  Nothing not in the trunk goes into the next
release.  So if we want a wiki page that is called "Release notes for
AOO Target January 2013" then it would be sufficient.  Just describe
significant changes there made in the trunk.  Maybe in the end we call
it "Apache OpenOffice 2013", or "Apache OpenOffice Adventitious
Armadillo" or something like that.  That decision can come later.

-Rob



In that case lets use the existing 3.5 Release Notes as Armin has 
already put a number of entries in there the "name can be change to 
protect the innocent later".


Regards
Keith




I could create a separate page as a sandbox where what you suggest could be
input, then when the release comes it is just a matter of moving the data
from the sandbox into the formal Release Notes page.

Regards
Keith

can ooo's write export swf file?

[jianlizhao]

HI Dave Fisher：

I  know the  Java libraries.
How to combine it with ooo?
Or  How to use it with ooo?

Regards,



> HI Dave Fisher
> Could you tell me the  Java libraries.

They are here:

http://www.flagstonesoftware.com/transform/index.html

OpenSource and BSD licensed.

Regards,
Dave


> Regards
> 
> 
>> Hello my friend:
>> 
>> I ask you some question:
>> 
>> 1) Can ooo's write export swf file format?
>> 2) Can I use extension implement this feature?
> 
> Possibly, I know that there are Java libraries like itransform that can
> help.
> 
> Regards,
> Dave

Re: [PROPOSAL] Fund Allocation for ApacheCon EU 2012, Germany in Nov. 2012

[Louis Suárez-Potts]

Hi,
On 12-09-24, at 09:22 , Jürgen Schmidt  wrote:

>>> 
>> 
>> No objections are raised in the last days.
>> I will work on its realization.
>> 
>> We need a small group for the granting process.
>> Currently we have:
>> - Peter Junge
>> - Oliver-Rainer Wittmann
>> 
>> Who else want to join?
> 
> I can help but I would prefer if others would step forward to help here

Well, I've volunteered my services several times now. 

Louis
> 
> Juergen

Re: [PROPOSAL] Fund Allocation for ApacheCon EU 2012, Germany in Nov. 2012

[Jürgen Schmidt]

On 9/24/12 10:05 AM, Oliver-Rainer Wittmann wrote:
> Hi,
> 
> On 18.09.2012 13:57, Oliver-Rainer Wittmann wrote:
>> Hi,
>>
>> I have learned that the following discussion/proposal should to be on
>> ooo-dev
>> instead of ooo-private.
>>
>> A summary for the background:
>> AOO has some money from the pre-Apache time (the SPI fund) which we (AOO
>> community) can spend for our project. There was a discussion on
>> ooo-private to
>> use some of this money for the ApacheCon EU 2012, Germany in Nov. 2012.
>> A small discussion took place and more or less ended in the below
>> proposal which
>> I had made:
>>
>> Here is my proposal for fund allocation for ApacheCon EU 2012, Germany
>> in Nov.
>> 2012; more or less a summary of the former discussion of this topic.
>>
>> - 10 x 300 EUR flat subsidies for travel expenses; double the subsidy
>> for cases
>> of hardship, e.g. persons who need to take a long flight.
>> -- criteria for granting subsidy:
>> (a) preference order: invited speakers, committers, non-committers
>> (b) person lacks of corporate funding and TAC funding
>> (c) person needs to spend at least 300 EUR on travel
>> (d) person need accommodation for at least 2 nights
>>
>> - 30 x 100 EUR ticket discount for non-committers
>> -- criteria for granting discount:
>> (a) person lacks of corporate funding and TAC funding
>>
>> A small group of volunteers are needed to drive the granting process:
>> - define application form and deadlines
>> - run the application process
>> - accept/reject the applications
>>
>> I am volunteering to be part of this small group.
>> Who else is joining?
>>
>> If nobody objects in the next 72 hours, I will put the proposal into
>> practice.
>>
> 
> No objections are raised in the last days.
> I will work on its realization.
> 
> We need a small group for the granting process.
> Currently we have:
> - Peter Junge
> - Oliver-Rainer Wittmann
> 
> Who else want to join?

I can help but I would prefer if others would step forward to help here

Juergen


> From my point of view there should be at least 3 or 5 people.
> 
> I will start a corresponding thread to discuss the granting process. But
> do not wait for it, if you already have thoughts/ideas/... about it.
> 
> Best regards, Oliver.

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Rob Weir]

On Mon, Sep 24, 2012 at 8:59 AM, Keith N. McKenna
 wrote:
> Rob Weir wrote:
>>
>> On Sun, Sep 23, 2012 at 10:13 AM, Shenfeng Liu  wrote:
>>>
>>> Hi, all,
>>>After 3.4.1, we are focusing on preparation of the community
>>> graduation.
>>> But I still want to remind us to take some time to think about our future
>>> releases.
>>>
>>>We have the discussion early about what 3.5 and 4.0 should look like.
>>> If
>>> I remember correctly:
>>> (1) 3.5 should be more about fidelity, reliability, performance and
>>> translation, new platform support...
>>> (2) While 4.0, in addition to the same focuses as 3.5, should also add
>>> significant UX enhancements (e.g. sidebar, modern UI) and new values
>>> (e.g.
>>> Accessibility, social integration capability, enhanced installer, new
>>> features...). If we make good progress on those items at the same time,
>>> we
>>> may consider to skip 3.5.
>>> (3) There are also more requirements (e.g. fixpack mechanism, simplifying
>>> the build structure, OOMXL export, smartArt...) we need  to put into our
>>> backlog and consider their priority.
>>>
>>>Even we don't need to discuss the solid plan now, but there are
>>> already a
>>> lot of development activities on the trunk. So I think we need to keep
>>> certain track on it. Though it may be too early to set a target date for
>>> the next release, but it is important for us to tell more about what we
>>> think the next release should contain.
>>>
>>>So I'm suggesting the following:
>>>
>>> 1. Keep updating the current release planning wiki:
>>>   -
>>>
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.5+Release+Planning
>>>   -
>>>
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning
>>> I know it is a little confusing for 2 places to input. But think
>>> about
>>> the scope we agreed above. You can input to the wiki that you think your
>>> work belong to. I personally will monitor both wiki pages.
>>>
>>> 2. Figure out a better way to manage our release backlog. e.g. set Target
>>> Milestone to 3.5 or 4.0 in Bugzilla for what we recommended.
>>>
>>> 3. Deliver milestone builds to harvest our development fruits. A
>>> milestone
>>> build is:
>>>   (a) a development snapshot that contains the features/enhancements
>>> that implemented till now;
>>>   (b) passed regression test to ensure no severe defects;
>>>   (c) announced on a development wiki;
>>>   (d) with documents on the wiki for the list of features and bug
>>> fixes
>>> in this milestone build (like a release notes).
>>> Since whatever 3.5 or 4.0 sounds to me like some thing in next year
>>> or
>>> at least close to the end of this year, milestone builds can be light
>>> weigh
>>> on process to show our development progress, and give people a more clear
>>> view on how far are we to the next release.
>>>
>>>Looking forward every one's comments!
>>>
>>
>> Maybe also start a "release notes" page on the wiki.  Whenever a new
>> feature or important bug fix is added to the trunk also add something
>> to the release notes.   If something can be show with a "before and
>> after" screen shot, include that.  This might be easier than waiting
>> until the end to prepare the release notes.
>>
>> -Rob
>>
>>>
>>> - Simon
>>
>>
> Rob;
>
> A Release Notes page already exists or 3.5 and one or 4.0 can be easily
> added. The complication I see here is since we have not decided whether the
> next release will be 3.5 or 4.0 that would require adding it in two places.
> I see that as a lot of overhead at this point.
>

IMHO, the name is not so important.  Everything in the trunk goes into
the next release.  Nothing not in the trunk goes into the next
release.  So if we want a wiki page that is called "Release notes for
AOO Target January 2013" then it would be sufficient.  Just describe
significant changes there made in the trunk.  Maybe in the end we call
it "Apache OpenOffice 2013", or "Apache OpenOffice Adventitious
Armadillo" or something like that.  That decision can come later.

-Rob


> I could create a separate page as a sandbox where what you suggest could be
> input, then when the release comes it is just a matter of moving the data
> from the sandbox into the formal Release Notes page.
>
> Regards
> Keith
>

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Ariel Constenla-Haile]

On Mon, Sep 24, 2012 at 07:56:26AM -0400, Rob Weir wrote:
> Maybe also start a "release notes" page on the wiki.  Whenever a new
> feature or important bug fix is added to the trunk also add something
> to the release notes.   If something can be show with a "before and
> after" screen shot, include that.  This might be easier than waiting
> until the end to prepare the release notes.

We should come back to the old days, where there was a clear separation
between RC and Dev. Snapshot, see ooo-site/content/development/releases/
for example
http://www.openoffice.org/development/releases/DEV300m106_snapshot.html

I also think we should bring the Dev. Snapshot page back home, I'll try
to make a design with a left side bar, à la
http://www.openoffice.org/product/ and http://www.openoffice.org/why/
so that the download page (the forth, orange item) points to the same
site.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpos702ZYrj9.pgp
Description: PGP signature

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Keith N. McKenna]

Rob Weir wrote:

On Sun, Sep 23, 2012 at 10:13 AM, Shenfeng Liu  wrote:

Hi, all,
   After 3.4.1, we are focusing on preparation of the community graduation.
But I still want to remind us to take some time to think about our future
releases.

   We have the discussion early about what 3.5 and 4.0 should look like. If
I remember correctly:
(1) 3.5 should be more about fidelity, reliability, performance and
translation, new platform support...
(2) While 4.0, in addition to the same focuses as 3.5, should also add
significant UX enhancements (e.g. sidebar, modern UI) and new values (e.g.
Accessibility, social integration capability, enhanced installer, new
features...). If we make good progress on those items at the same time, we
may consider to skip 3.5.
(3) There are also more requirements (e.g. fixpack mechanism, simplifying
the build structure, OOMXL export, smartArt...) we need  to put into our
backlog and consider their priority.

   Even we don't need to discuss the solid plan now, but there are already a
lot of development activities on the trunk. So I think we need to keep
certain track on it. Though it may be too early to set a target date for
the next release, but it is important for us to tell more about what we
think the next release should contain.

   So I'm suggesting the following:

1. Keep updating the current release planning wiki:
  -
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.5+Release+Planning
  -
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning
I know it is a little confusing for 2 places to input. But think about
the scope we agreed above. You can input to the wiki that you think your
work belong to. I personally will monitor both wiki pages.

2. Figure out a better way to manage our release backlog. e.g. set Target
Milestone to 3.5 or 4.0 in Bugzilla for what we recommended.

3. Deliver milestone builds to harvest our development fruits. A milestone
build is:
  (a) a development snapshot that contains the features/enhancements
that implemented till now;
  (b) passed regression test to ensure no severe defects;
  (c) announced on a development wiki;
  (d) with documents on the wiki for the list of features and bug fixes
in this milestone build (like a release notes).
Since whatever 3.5 or 4.0 sounds to me like some thing in next year or
at least close to the end of this year, milestone builds can be light weigh
on process to show our development progress, and give people a more clear
view on how far are we to the next release.

   Looking forward every one's comments!



Maybe also start a "release notes" page on the wiki.  Whenever a new
feature or important bug fix is added to the trunk also add something
to the release notes.   If something can be show with a "before and
after" screen shot, include that.  This might be easier than waiting
until the end to prepare the release notes.

-Rob



- Simon



Rob;

A Release Notes page already exists or 3.5 and one or 4.0 can be easily 
added. The complication I see here is since we have not decided whether 
the next release will be 3.5 or 4.0 that would require adding it in two 
places. I see that as a lot of overhead at this point.


I could create a separate page as a sandbox where what you suggest could 
be input, then when the release comes it is just a matter of moving the 
data from the sandbox into the formal Release Notes page.


Regards
Keith

Re: [BUILD] atlthunk

[Ariel Constenla-Haile]

Hi Regina,

On Sun, Sep 23, 2012 at 04:36:42PM +0200, Regina Henschel wrote:
> Hi Ariel,
> 
> addition:
> I have set
>  --disable-activex \
> 
> Does that matter?

Since rev. 1389343 you can disable ActiveX while leaving ATL enabled
(the default if --disable-atl is not used).


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpBSuDH1dyda.pgp
Description: PGP signature

Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)

[Dave Fisher]

On Sep 24, 2012, at 4:34 AM, Rob Weir wrote:

> On Mon, Sep 24, 2012 at 5:37 AM, sebb  wrote:
>> On 24 September 2012 03:50, Rob Weir  wrote:
>>> On Sep 23, 2012, at 10:15 PM, "Dennis E. Hamilton"  
>>> wrote:
>>> 
 Rob,
 
 I recently took a look at 
  to see if I 
 could derive that list from the Roster.
 
 What gave me pause is that the list is apparently maintained in XML.  I 
 could not find anywhere that MarkDown is used.  Is that correct?
 
>>> 
>>> Correct.  It is XML. It used to require that I check out the whole
>>> directory, update the XML, run an ant script to generate the HTML and
>>> then check in both the XML and HTML.  This is much simplified by the
>>> CMS which does the template generation behind the scenes.
>>> 
>>> 
 I could still mechanically derive the XML elements that are used now, 
 although it is a bit more complicated than search and replace on a CSV of 
 an extract of the roster.  If I were to do that, I would also indicate who 
 is on the PPMC.
 
 Any suggestions?
>>> 
>>> I'm not sure we need to maintain that "status file" once we graduate.
>>> I think it is more of a podling tracking thing. So it might be
>> 
>> Yes, it is for active podlings only. No need to update it once
>> graduated, though it does need to be completed before graduation.
>> 
>> The other file that needs to be updated by podlings is podlings.xml.
>> 
>> Note that
>> 
>> http://people.apache.org/committers-by-project.html#ooo
>> 
>> is created automatically from the SVN authz file (where podling
>> committers are listed) plus LDAP groups.
>> 
>>> simplest if we just manually update it for now.  But longer term it
>>> would be good to be able to generate a page for the project website
>>> from the Roster.   The ODF Toolkit has an XSLTRunner component that
>>> could be used for this.
>> 
>> Not sure that's necessary. You could just link to the appropriate
>> sections in the above file.
>> 
> 
> Is there any easy way to track PMC membership?  Maybe that be derived
> from the authz for the eventual /pmc/openoffice tree?Eventually we
> want an easy way to generate a roster that lists committers but also
> identifies PMC members.

Sebb answered, but sometimes examples are needed. PMCs have authz as well. Here 
is the page for the POI PMC:

http://people.apache.org/committers-by-project.html#poi-pmc

Regards,
Dave

> 
> -Rob
> 
> 
>>> -Rob
>>> 
 
 - Dennis
 
 -Original Message-
 From: Rob Weir [mailto:robw...@apache.org]
 Sent: Sunday, September 23, 2012 17:41
 To: ooo-dev@incubator.apache.org
 Subject: Re: New committer: Chen ZuoJun
 
 On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton  
 wrote:
> The Apache OpenOffice PPMC announces the addition of committer
> Chen ZuoJun, zjchen@ apache.org
> 
> The list of all current podling committers is at:
> .
 
 And one other place:  
 http://incubator.apache.org/projects/openofficeorg.html
 
 That page is part of the IPMC's tracking of podling status and feeds
 into their "Status of the Clutch" report:
 http://incubator.apache.org/clutch.html
 
 Some may recall that we had a reporter use the "status of the clutch"
 report to claim that the project was not growing.  That was when we
 were not updating the report.  Since that is the official IPMC view of
 the podlings, it is important that we keep this information
 up-to-date, until the project graduates.
 
 I was updating this status page whenever a new committer was voted in.
 It would be great if someone else could take this over now.
 
 When a new committer is added, the status file needs to be updated in
 two places.
 
 1) Added as a News item.  Automation depends on the wording, so don't
 be clever.  Just follow the examples there.
 
 2) Added in the list of committers.
 
 This can most easily be edited via the Apache CMS.
 
 [ ... ]
 

Re: Missing Visual C++ Libraries in all recent versions of Open Office installer

[Ariel Constenla-Haile]

Hi Andrea,

On Sun, Sep 23, 2012 at 07:26:58PM +0200, Andrea Pescetti wrote:
> On 17/09/2012 Andrea Pescetti wrote:
> >On 16/09/2012 Ariel Constenla-Haile wrote:
> >>the fact is that
> >>there is a bug, that has to be closed as wontfix or left open depending
> >>on a *new* one: install the MSVCRedist (which IMO is no defect, but
> >>a request for enhancement).
> >For reference, I opened an enhancement request based on information in
> >this thread: https://issues.apache.org/ooo/show_bug.cgi?id=120979
> 
> And for those not following the issue: Ariel fixed it and provided a
> Windows build that includes the library. Please test it. As Ariel
> notes, it is a OOo-Dev build so it will not override your current
> installation.
> 
> The build can be found at
> http://people.apache.org/~arielch/packages/r1388877/win/Apache_OpenOffice_incubating-Dev_AOO350m1_Win_x86_install_en-US.exe

In the meantime I uploaded a new version, with language packs for all
supported languages:
http://people.apache.org/~arielch/packages/r1389156/win/


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgp4fTt2bKfuO.pgp
Description: PGP signature

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[RGB ES]

2012/9/24 Andrea Pescetti 

> On 23/09/2012 Shenfeng Liu wrote:
>
>> 3. Deliver milestone builds to harvest our development fruits. A milestone
>> build is:
>>   (a) a development snapshot that contains the features/enhancements
>> that implemented till now;
>>   (b) passed regression test to ensure no severe defects;
>>   (c) announced on a development wiki;
>>   (d) with documents on the wiki for the list of features and bug
>> fixes
>> in this milestone build (like a release notes).
>>
>
> Milestone builds are a good idea: they would not be the same as the daily
> snapshots (which by the way are not yet available for all platforms). I
> would add:
>
> (e) available in all official supported languages, at least as langpack;
>


+1. To give more time to volunteers for checking the translations will be
really important.

Regards
Ricardo



> and make the builds available on a monthly basis, so they can be easily
> identified and we can engage QA testers more effectively. This, of course,
> unless people who provide the builds find it too time-consuming to upload a
> build per month.
>
> Regards,
>   Andrea.
>

Re: OpenOffice Developer Room (devroom) at FOSDEM

[Jürgen Schmidt]

On 9/24/12 1:20 PM, Andrea Pescetti wrote:
> FOSDEM, one of the biggest Free and Open Source Software events in
> Europe, is coming again on 2-3 February 2013 in Brussels.
> 
> Attendance is free and, moreover, "Developer Rooms" can be made
> available upon request, but they must be requested before the end of
> September. See https://fosdem.org/2013/call_for_devrooms.html
> 
> I'm available to draft the application for an OpenOffice devroom and
> post it here on ooo-dev for lazy consensus, unless:
> - Someone has already done it (just let us know)
> - Apache manages applications in a centralized way
> - No OpenOffice developers can attend (I would appreciate to know that
> we will have some full-time developers there)
> - People believe it is useless (but FOSDEM is a big event and we
> shouldn't miss it, since by February we will probably have graduated and
> version 3.5 could be approaching release).
> 

OpenOffice was there present for many years and it can be of course an
opportunity to reach out to other open source developers there.

Depending on the feedback of the organizers I can also think about a
joined devroom with the LibreOffice folks. Space for devrooms is limited
and I can of course think about a joined effort here. I am at least open
for this if wanted.

I will support any activities and will probably join the conference.
FOSDEM is a nice event and it makes always fun to meet so many open
source freaks. I can only recommend it from this perspective and it is
always on a weekend.

Juergen

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Rob Weir]

On Sun, Sep 23, 2012 at 10:13 AM, Shenfeng Liu  wrote:
> Hi, all,
>   After 3.4.1, we are focusing on preparation of the community graduation.
> But I still want to remind us to take some time to think about our future
> releases.
>
>   We have the discussion early about what 3.5 and 4.0 should look like. If
> I remember correctly:
> (1) 3.5 should be more about fidelity, reliability, performance and
> translation, new platform support...
> (2) While 4.0, in addition to the same focuses as 3.5, should also add
> significant UX enhancements (e.g. sidebar, modern UI) and new values (e.g.
> Accessibility, social integration capability, enhanced installer, new
> features...). If we make good progress on those items at the same time, we
> may consider to skip 3.5.
> (3) There are also more requirements (e.g. fixpack mechanism, simplifying
> the build structure, OOMXL export, smartArt...) we need  to put into our
> backlog and consider their priority.
>
>   Even we don't need to discuss the solid plan now, but there are already a
> lot of development activities on the trunk. So I think we need to keep
> certain track on it. Though it may be too early to set a target date for
> the next release, but it is important for us to tell more about what we
> think the next release should contain.
>
>   So I'm suggesting the following:
>
> 1. Keep updating the current release planning wiki:
>  -
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.5+Release+Planning
>  -
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning
>I know it is a little confusing for 2 places to input. But think about
> the scope we agreed above. You can input to the wiki that you think your
> work belong to. I personally will monitor both wiki pages.
>
> 2. Figure out a better way to manage our release backlog. e.g. set Target
> Milestone to 3.5 or 4.0 in Bugzilla for what we recommended.
>
> 3. Deliver milestone builds to harvest our development fruits. A milestone
> build is:
>  (a) a development snapshot that contains the features/enhancements
> that implemented till now;
>  (b) passed regression test to ensure no severe defects;
>  (c) announced on a development wiki;
>  (d) with documents on the wiki for the list of features and bug fixes
> in this milestone build (like a release notes).
>Since whatever 3.5 or 4.0 sounds to me like some thing in next year or
> at least close to the end of this year, milestone builds can be light weigh
> on process to show our development progress, and give people a more clear
> view on how far are we to the next release.
>
>   Looking forward every one's comments!
>

Maybe also start a "release notes" page on the wiki.  Whenever a new
feature or important bug fix is added to the trunk also add something
to the release notes.   If something can be show with a "before and
after" screen shot, include that.  This might be easier than waiting
until the end to prepare the release notes.

-Rob

>
> - Simon

[REQUEST] Apache OpenOffice (incubating) - fund allocation for ACEU 2012

[Oliver-Rainer Wittmann]

Hi ASF treasurer,

[Apache OpenOffice (incubating) community and ACEU planners on CC]

the Apache OpenOffice (incubating) community wants to spend some of its fund for 
ApacheCon EU (ACEU) 2012 - see the corresponding thread on ooo-dev@i.a.o [1].


We are currently discussing the granting processes - see [2].

The purpose of this post is to assure ASF's charity status and to clarify the 
actual spending of the money regarding our planned fund allocation.
We want to spend the following money for ACEU 2012 participants from the Apache 
OpenOffice (incubating) community:

- 10 x 300/600 EUR for travel expense subsidy
- 30 x 100 EUR for ticket discounts for non-committers

Questions regarding assurence of charity status:
(1) Do the planned spendings violate our charity status?
(2) What do we need to consider in our planned granting processes to assure our 
charity status?


Questions regarding actual spending of the money:
(1) Is it possible to spend the "ticket discount" money via a special promotion 
code in the ACEU 2012 ticket system?

(1a) If not, do you have any recommendation how the money should be spent?

(2) What are the possibilities to spend the "travel expense subsidy" money?
(2a) Do you have a recommendation how the money should be spent?


[1] http://markmail.org/message/g6e5xqmkyq4elfqz
[2] http://markmail.org/message/k3yngrujqjgnnz4a


Thanks in advance for your support.

Best regards, Oliver.

Re: [RELEASE] 3.5, 4.0, fixpack, milestone build...

[Jürgen Schmidt]

On 9/24/12 8:01 AM, Andrea Pescetti wrote:
> On 23/09/2012 Shenfeng Liu wrote:
>> 3. Deliver milestone builds to harvest our development fruits. A
>> milestone
>> build is:
>>   (a) a development snapshot that contains the features/enhancements
>> that implemented till now;
>>   (b) passed regression test to ensure no severe defects;
>>   (c) announced on a development wiki;
>>   (d) with documents on the wiki for the list of features and bug
>> fixes
>> in this milestone build (like a release notes).
> 
> Milestone builds are a good idea: they would not be the same as the
> daily snapshots (which by the way are not yet available for all
> platforms). I would add:
> 
> (e) available in all official supported languages, at least as langpack;
> 
> and make the builds available on a monthly basis, so they can be easily
> identified and we can engage QA testers more effectively. This, of
> course, unless people who provide the builds find it too time-consuming
> to upload a build per month.

milestone builds are not only a good idea, they are overdue. We had
already agreed on milestones builds some weeks before and we lost focus
on this a little bit with other things :-(

I would suggest that we start this week with the first snapshot builds
and ideally based on a revision that our build bots have build
successful. Unfortunately I see only the 64 bit Linux build bot
reporting a successful build. We should analyzing these problems first.

Based on this I would suggest that we do official snapshots every 2 or 4
weeks besides our nightly build bot builds that can be used for testing
as well. Probably a 4 weeks cycle is good to report in more detail what
the snapshot contains and to focus more testing on it.

What do you think, is a 4 week cycle for official dev snapshots enough
together with working build bits supporting nightly builds?

Thanks Simon, for bringing this up again.

Juergen

Re: [CODE] gmake and AOO build system

[Andre]

On 09/19/2012 09:58 PM, Pedro Giffuni wrote:

Hi Andrew;


- Original Message -
...

I have been provided patches necessary to apply the following CWSes to AOO
trunk:

ause131
ause130
writerfilter10
gnumake4
sd2gbuild

As I understand it this is mostly gbuild stuff that we did not want to apply to
3.4.x as it might destabilize the build.
This was provided to me by Michael Stahl, and represents work done by Oracle
emps when OOo was still at Oracle.

Is there any resistance from checking in these patches?  If I don't hear any
opposition in 72 hours and the patches cleanly apply on my dev area, I will
check in these changes.
  

Not an objection at this point but this is likely to break transitorily
the FreeBSD port.

It would be helpful to see the patches before they are applied.


Any news?  (I just came back from my vacation)

Andre



Pedro.

Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)

[Rob Weir]

On Mon, Sep 24, 2012 at 5:37 AM, sebb  wrote:
> On 24 September 2012 03:50, Rob Weir  wrote:
>> On Sep 23, 2012, at 10:15 PM, "Dennis E. Hamilton"  wrote:
>>
>>> Rob,
>>>
>>> I recently took a look at 
>>>  to see if I could 
>>> derive that list from the Roster.
>>>
>>> What gave me pause is that the list is apparently maintained in XML.  I 
>>> could not find anywhere that MarkDown is used.  Is that correct?
>>>
>>
>> Correct.  It is XML. It used to require that I check out the whole
>> directory, update the XML, run an ant script to generate the HTML and
>> then check in both the XML and HTML.  This is much simplified by the
>> CMS which does the template generation behind the scenes.
>>
>>
>>> I could still mechanically derive the XML elements that are used now, 
>>> although it is a bit more complicated than search and replace on a CSV of 
>>> an extract of the roster.  If I were to do that, I would also indicate who 
>>> is on the PPMC.
>>>
>>> Any suggestions?
>>
>> I'm not sure we need to maintain that "status file" once we graduate.
>> I think it is more of a podling tracking thing. So it might be
>
> Yes, it is for active podlings only. No need to update it once
> graduated, though it does need to be completed before graduation.
>
> The other file that needs to be updated by podlings is podlings.xml.
>
> Note that
>
> http://people.apache.org/committers-by-project.html#ooo
>
> is created automatically from the SVN authz file (where podling
> committers are listed) plus LDAP groups.
>
>> simplest if we just manually update it for now.  But longer term it
>> would be good to be able to generate a page for the project website
>> from the Roster.   The ODF Toolkit has an XSLTRunner component that
>> could be used for this.
>
> Not sure that's necessary. You could just link to the appropriate
> sections in the above file.
>

Is there any easy way to track PMC membership?  Maybe that be derived
from the authz for the eventual /pmc/openoffice tree?Eventually we
want an easy way to generate a roster that lists committers but also
identifies PMC members.

-Rob


>> -Rob
>>
>>>
>>> - Dennis
>>>
>>> -Original Message-
>>> From: Rob Weir [mailto:robw...@apache.org]
>>> Sent: Sunday, September 23, 2012 17:41
>>> To: ooo-dev@incubator.apache.org
>>> Subject: Re: New committer: Chen ZuoJun
>>>
>>> On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton  
>>> wrote:
 The Apache OpenOffice PPMC announces the addition of committer
 Chen ZuoJun, zjchen@ apache.org

 The list of all current podling committers is at:
 .
>>>
>>> And one other place:  
>>> http://incubator.apache.org/projects/openofficeorg.html
>>>
>>> That page is part of the IPMC's tracking of podling status and feeds
>>> into their "Status of the Clutch" report:
>>> http://incubator.apache.org/clutch.html
>>>
>>> Some may recall that we had a reporter use the "status of the clutch"
>>> report to claim that the project was not growing.  That was when we
>>> were not updating the report.  Since that is the official IPMC view of
>>> the podlings, it is important that we keep this information
>>> up-to-date, until the project graduates.
>>>
>>> I was updating this status page whenever a new committer was voted in.
>>> It would be great if someone else could take this over now.
>>>
>>> When a new committer is added, the status file needs to be updated in
>>> two places.
>>>
>>> 1) Added as a News item.  Automation depends on the wording, so don't
>>> be clever.  Just follow the examples there.
>>>
>>> 2) Added in the list of committers.
>>>
>>> This can most easily be edited via the Apache CMS.
>>>
>>> [ ... ]
>>>

OpenOffice Developer Room (devroom) at FOSDEM

[Andrea Pescetti]

FOSDEM, one of the biggest Free and Open Source Software events in 
Europe, is coming again on 2-3 February 2013 in Brussels.


Attendance is free and, moreover, "Developer Rooms" can be made 
available upon request, but they must be requested before the end of 
September. See https://fosdem.org/2013/call_for_devrooms.html


I'm available to draft the application for an OpenOffice devroom and 
post it here on ooo-dev for lazy consensus, unless:

- Someone has already done it (just let us know)
- Apache manages applications in a centralized way
- No OpenOffice developers can attend (I would appreciate to know that 
we will have some full-time developers there)
- People believe it is useless (but FOSDEM is a big event and we 
shouldn't miss it, since by February we will probably have graduated and 
version 3.5 could be approaching release).


Regards,
  Andrea.

Re: Did we ever reach consensus on support for Windows 2000

[Stuart Swales]

On 23/09/2012 23:51, Kay Schenk wrote:
> 
> 
> On 09/16/2012 09:48 PM, Rob Weir wrote:
>> On Sep 16, 2012, at 11:38 PM, "Keith N. McKenna"
>>  wrote:
>>
>>> Rob Weir wrote:
 On Sun, Sep 16, 2012 at 4:26 PM, Keith N. McKenna
  wrote:
> Greetings All;
>
> I was going through FAQ's and other pages on the AOO (incubating)
> site and
> noticed that many still are showing that we support Windows 2000 as a
> baseline operating system. I though I remembered some discussions a
> while
> back on this list around that subject and thought we had decided
> that we
> would no longer do that due to lack of testing resources.
>

 IMHO, "support" is determined by what we do, not by what we say.  If
 no one is testing with Windows 2000, then it is hard to say we support
 it.  And if Microsoft does not make Windows 2000 CD's available to
 developers for testing, due to a lawsuit, then it is rather difficult
 for anyone who wants to test.  Not impossible, but they would need to
 get access to CD's or ISO images through unofficial means.
>>>
>>> The major disagreement I have with this Rob is that we publish FAQ's
>>> and installation documents on our official web site that lead people
>>> to believe that Windows 2000 is supported.
>>
>> Actually I don't think we disagree on this. At one point in time
>> (OpenOffice.org 3.3?) Windows 2000 was presumably tested and that is
>> why it is on the supported list. The fact that it remains on that list
>> is purely due to a kind of inertia: documentation in rest stays at
>> rest unless acted on by an outside force.
>>
>> So I agree that the website is out of synch with reality here and that
>> this is suboptimal. Two easy ways to fix: someone volunteers to do
>> some minimal testing with Windows 2000 to confirm basic operations, or
>> we remove it from the supported list.
>>
>> Of course even if removed it could come back once tested.
>>
>>> What does it say for us as a responsible project when we tell people
>>> that despite what we clearly show as a minimum requirement to use our
>>> software is really not what we meant. All that does is leave a bad
>>> taste in the consumers mouth that they most likely will tell there
>>> friends about. That to me is NOT the image we should project.
>>>
>>
>> If you feel strongly about this then you could propose to change the
>> website and if their are no objections after 72 hours assume lazy
>> consensus and go ahead and make the changes.
>>
 Of course, we could have a dozen people say we *should* support
 Windows 2000.  But should does not mean anything.  We really need to
 find even a single person who says they *will* test with Windows 2000
 and fix any problems that arise.  Until that happens we don't really
 support Windows 2000 in any meaningful way.
>>>
>>> That is all well and good Rob, but again that needs to be clear to
>>> people and not come as a surprise. I personally do not care one way
>>> or the other if 2000 is supported or not. My concern is with the
>>> image that we project to our user base. I am not a software engineer
>>> or coder so therefore not qualified to judge what is or is not
>>> supportable withing the code. That is why I brought this to the
>>> attention of the people that are qualified to get better information
>>> to present to our users.
>>>
 I went back through the archives and did find a number of threads
 but they
> never seemed to reach a definite conclusion. I we are going to
> continue to
> support it all well and good, but if we cannot then all FAQ's and
> other
> documentation on the site should change to reflect that.
>

 Support is not determined by consensus wishes.  It is determined by
 someone actually doing it.
>>>
>>> Again Rob that is all well and good, but why are we publishing to the
>>> world that Windows 2000 is the minimum Windows OS environment that
>>> our product can run in?
>>>
 Do we have any evidence that users have successfully installed and
 used AOO 3.4.x on Windows 2000?  If it works, we might just list it
 "not a tested configuration, but some users report success.".  In
 other words, between "tested and supported" and "known to be broken"
 is a middle territory where it is "use at your own risk".
>>>
>>> I really do not know if we do our not Rob. What I do know is that we
>>> are telling users on our official web site that Windows 2000 is the
>>> minimum Revision of the OS that our product will run on.
>>>
>>> Regards
>>> Keith
>>>
 -Rob

> Regards
> Keith
>

>>>
>>>
> 
> At least the following web pages need some attention:
> 
> * http://www.openoffice.org/dev_docs/source/sys_reqs.html
> (not sure of navigation to this one)
> * http://www.openoffice.org/dev_docs/source/sys_reqs_aoo34.html
> (linked from download)
> * http://www.openoffice.org/download/common/instructions.html
> (linked from mai

[DISCUSS] granting processes for fund allocation for ACEU 2012

[Oliver-Rainer Wittmann]

Hi,

I would like to discuss how the grainting processes for fund allocation for 
ApacheCon EU (ACEU) 2012 could work.
Two processes are needed. One for granting travel expense subsidy and one for 
ticket discount for non-committers of the OpenOffice community.


The goal is to reach (lazy) consensus on the granting processes in the next 72 
hours.


Here are my ideas regarding such processes:
(1) ticket discount for non-committers:
- 30 x 100 EUR ticket discount for non-committers can be granted.

- To apply for the ticket discount people should send post to ooo-private. The 
details should be:

-- subject = [ACEU 2012 - ticket discount] 
-- content:
--- full name
--- email address
--- affiliation to the OpenOffice community (something like: "user", 
"contributing X", "translator", ...)

--- description why applying for the ticket discount and why support is needed.
--- job or eduation status (something like: "student", "employee", 
"freeflancer", ...)


- Announce on our mailing lists and in our forum that application process is 
open until  -  should be at least 7 days ahead 
of the .


- The small group of volunteers collect the applications. The group selects not 
more than 30 and post the decision details on ooo-private. The selection process 
should not take more than 2 days.

The selection shall be based on the given description and the job/eduation 
status.

- Send out corresponding notifications and details how to get the ticket 
discount.

[Note: I will get in contact with ACEU 2012 planners, if it is possible to get a 
promotion code for our ticket discount.]
[Another note: I will get in contact with treasu...@apache.org to assure ASF's 
charity status and clarify the actual spending of the money]



(2) travel expense subsidy for OpenOffice community members:
- 10 x 300 resp. 600 EUR travel expense subsidy can be granted.

- To apply for the travel expense subsidy people should send a post to 
ooo-private. The details should be:

-- subject = [ACEU 2012 - travel subsidy] 
-- content:
--- full name
--- email address
--- affiliation to the OpenOffice community (something like: "committer", 
"user", "contributing X", "translator", ...)

--- Apache ID (if available)
--- accepted or stand-by speaker at ACEU?
--- description why applying for the travel expense subsidy and why support is 
needed.
--- job or eduation status (something like: "student", "employee", "freelancer", 
...)

--- estimated travel expense
--- estimated needed accommodation - # of nights
--- other available funding (something like: "corporate", "ACEU - TAC", ...)
--- applying for 300 EUR or 600 EUR?

- Announce on our mailing lists and in our forum that application process is 
open until  -  should be at least 7 days ahead 
of the .


- The small group of volunteers collect the applications. The group selects not 
more than 10 and post the decision details on ooo-private. The selection process 
should not take more than 3 days.

The selection should consider the following:
-- Application shall hold the following conditions, otherwise it is invalid
--- no corporate funding and no TAC funding
--- travel expense must be at least 300 EUR
--- accommodation needed for at least 2 nights
-- The selection shall be based on the given description and the job/eduation 
status.

-- Applications are selected in the following order:
--- invited (accepted or stand-by) speakers
--- committers
--- non-committers

- Send out corresponding notifications and details how to get the ticket 
discount.

[Note: I will get in contact with treasu...@apache.org to assure ASF's charity 
status and clarify the actual spending of the money.]



Please provide your input.


Best regards, Oliver.

Re: Updating Committers on Project Status Page (was RE: New committer: Chen ZuoJun)

[sebb]

On 24 September 2012 03:50, Rob Weir  wrote:
> On Sep 23, 2012, at 10:15 PM, "Dennis E. Hamilton"  wrote:
>
>> Rob,
>>
>> I recently took a look at 
>>  to see if I could 
>> derive that list from the Roster.
>>
>> What gave me pause is that the list is apparently maintained in XML.  I 
>> could not find anywhere that MarkDown is used.  Is that correct?
>>
>
> Correct.  It is XML. It used to require that I check out the whole
> directory, update the XML, run an ant script to generate the HTML and
> then check in both the XML and HTML.  This is much simplified by the
> CMS which does the template generation behind the scenes.
>
>
>> I could still mechanically derive the XML elements that are used now, 
>> although it is a bit more complicated than search and replace on a CSV of an 
>> extract of the roster.  If I were to do that, I would also indicate who is 
>> on the PPMC.
>>
>> Any suggestions?
>
> I'm not sure we need to maintain that "status file" once we graduate.
> I think it is more of a podling tracking thing. So it might be

Yes, it is for active podlings only. No need to update it once
graduated, though it does need to be completed before graduation.

The other file that needs to be updated by podlings is podlings.xml.

Note that

http://people.apache.org/committers-by-project.html#ooo

is created automatically from the SVN authz file (where podling
committers are listed) plus LDAP groups.

> simplest if we just manually update it for now.  But longer term it
> would be good to be able to generate a page for the project website
> from the Roster.   The ODF Toolkit has an XSLTRunner component that
> could be used for this.

Not sure that's necessary. You could just link to the appropriate
sections in the above file.

> -Rob
>
>>
>> - Dennis
>>
>> -Original Message-
>> From: Rob Weir [mailto:robw...@apache.org]
>> Sent: Sunday, September 23, 2012 17:41
>> To: ooo-dev@incubator.apache.org
>> Subject: Re: New committer: Chen ZuoJun
>>
>> On Sun, Sep 23, 2012 at 1:13 PM, Dennis E. Hamilton  
>> wrote:
>>> The Apache OpenOffice PPMC announces the addition of committer
>>> Chen ZuoJun, zjchen@ apache.org
>>>
>>> The list of all current podling committers is at:
>>> .
>>
>> And one other place:  http://incubator.apache.org/projects/openofficeorg.html
>>
>> That page is part of the IPMC's tracking of podling status and feeds
>> into their "Status of the Clutch" report:
>> http://incubator.apache.org/clutch.html
>>
>> Some may recall that we had a reporter use the "status of the clutch"
>> report to claim that the project was not growing.  That was when we
>> were not updating the report.  Since that is the official IPMC view of
>> the podlings, it is important that we keep this information
>> up-to-date, until the project graduates.
>>
>> I was updating this status page whenever a new committer was voted in.
>> It would be great if someone else could take this over now.
>>
>> When a new committer is added, the status file needs to be updated in
>> two places.
>>
>> 1) Added as a News item.  Automation depends on the wording, so don't
>> be clever.  Just follow the examples there.
>>
>> 2) Added in the list of committers.
>>
>> This can most easily be edited via the Apache CMS.
>>
>> [ ... ]
>>

Re: [code] building trunk, rev. 1386983 break in setup_native

[Oliver-Rainer Wittmann]

Hi,

On 23.09.2012 19:58, Regina Henschel wrote:

Hi Oliver,

Oliver-Rainer Wittmann schrieb:
[..]


Does the attached patch make sense in order to get rid of the problem by
removing the usage of boost::scoped_array?

Thx in advance for your feedback.


I have applied the patch before building with --enable-dbgutil and it builds
fine. I use MSVC 9.0 Express.

It would be nice to apply it generally, or does it harm a normal pro-build?



I will apply to patch on trunk.
The patch also affects the pro-build (build without configure option 
--enable-dbgutil).


Best regards, Oliver.

Re: [DISCUSS] [PMC] Proposed PMC List

[Ross Gardler]

Just to confirm that I have received no offline nominations.

Sent from my tablet
On Sep 19, 2012 12:00 AM, "Andrew Rist"  wrote:

> (top posting after private messages - I cannot describe the shame I
> feel...  ;-)
>
> I have an option that I believe will handle Andrea's concerns.  I have
> spoken with Ross and he is amenable to receiving Proposed PMC entries off
> list.
> If anyone is concerned about sending their list to ooo-dev, you can send
> it to Ross ( rgardler at apache) instead, and at the end of the period
> (next Sunday), he will send an anonymized summary of the votes he has
> received, along with a breakdown of submissions by committers/PPMC vs other
> community members.
>
> We have received lists from 10 people and have 25 nominees with multiple
> votes.  It would be great to get even more feedback.
>
> A.
>
>
>
> On 9/18/2012 1:17 PM, Andrea Pescetti wrote:
>
>> On 17/09/2012 Andrew Rist wrote:
>>
>>> * This is not a vote. This is a search for consensus. Please no '-1'
>>> replies. Let's see what this process produces, and then discuss
>>> from there.
>>>
>>
>> It seems that the process is working quite well, and that we are on the
>> right way to bootstrap a PMC by consensus.
>>
>> I surely don't want to block the current process, but I wonder if
>> allowing people to "vote" (actually, express preferences) anonymously would
>> be better for some volunteers/cultures. Our mentors have often stated that
>> we have secure voting solutions available, but maybe this is overkill and
>> time-consuming, and it would be enough to allow people to send their lists
>> to a mentor (if available), who would repost them here.
>>
>> It is not an issue that I feel personally: it's OK for me to continue
>> with public messages on ooo-dev. But it could be that others have problems,
>> and in that case I'd encourage them to speak up so that we can find a way
>> to ensure that everyone can express their opinions.
>>
>> Regards,
>>   Andrea.
>>
>
>

Re: [PROPOSAL] Fund Allocation for ApacheCon EU 2012, Germany in Nov. 2012

[Oliver-Rainer Wittmann]

Hi,

On 18.09.2012 13:57, Oliver-Rainer Wittmann wrote:

Hi,

I have learned that the following discussion/proposal should to be on ooo-dev
instead of ooo-private.

A summary for the background:
AOO has some money from the pre-Apache time (the SPI fund) which we (AOO
community) can spend for our project. There was a discussion on ooo-private to
use some of this money for the ApacheCon EU 2012, Germany in Nov. 2012.
A small discussion took place and more or less ended in the below proposal which
I had made:

Here is my proposal for fund allocation for ApacheCon EU 2012, Germany in Nov.
2012; more or less a summary of the former discussion of this topic.

- 10 x 300 EUR flat subsidies for travel expenses; double the subsidy for cases
of hardship, e.g. persons who need to take a long flight.
-- criteria for granting subsidy:
(a) preference order: invited speakers, committers, non-committers
(b) person lacks of corporate funding and TAC funding
(c) person needs to spend at least 300 EUR on travel
(d) person need accommodation for at least 2 nights

- 30 x 100 EUR ticket discount for non-committers
-- criteria for granting discount:
(a) person lacks of corporate funding and TAC funding

A small group of volunteers are needed to drive the granting process:
- define application form and deadlines
- run the application process
- accept/reject the applications

I am volunteering to be part of this small group.
Who else is joining?

If nobody objects in the next 72 hours, I will put the proposal into practice.



No objections are raised in the last days.
I will work on its realization.

We need a small group for the granting process.
Currently we have:
- Peter Junge
- Oliver-Rainer Wittmann

Who else want to join?
From my point of view there should be at least 3 or 5 people.

I will start a corresponding thread to discuss the granting process. But do not 
wait for it, if you already have thoughts/ideas/... about it.


Best regards, Oliver.