date:20120819

A quick reminder, also of benefit to new members of the project, and
all those observers/lurkers on the list.

A release for a podling at Apache has a two-stage voting process:

1) The release is first approved by the Podling Project Management
Committee, in a 72-hour vote.  This completed successfully on
Saturday.

2) An additional vote then occurs with the Incubator Project
Management Committee.  This vote is currently underway, ending Tuesday
afternoon (UTC).

If the IPMC vote is successful, then the release is approved.
However, we're not quite ready for a public announcement of the
availability of 3.4.1 at that point.  There are a number of additional
tasks that need to occur, related to uploading the files to release
servers, updating the website with new links, completing translations
of the release announcement, etc.   So there will be a short delay
between the release being approved and the release being announced.
This delay should be on the order of 24 hours.

I bring this up because with AOO 3.4.0 there was some premature press
coverage, confusing users who heard that we released 3.4.0, but then
came to the website and did not find it.

So how do you know when AOO 3.4.1 is really released?

1) A blog post announcing AOO 3.4.1 will be posted here:
http://blogs.apache.org/ooo/

2) A note will be sent to ooo-dev, ooo-users and ooo-announce

Regards,

-Rob

CMS diff: Why OpenOffice.org: Public administrations

Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/zh-cn%2Fwhy%2Fwhy_gov.mdtext

Shenfeng Liu

Index: trunk/content/zh-cn/why/why_gov.mdtext
===
--- trunk/content/zh-cn/why/why_gov.mdtext  (revision 1374681)
+++ trunk/content/zh-cn/why/why_gov.mdtext  (working copy)
@@ -1,4 +1,4 @@
-Title: Why OpenOffice.org: Public administrations
+Title: 为何选择Apache OpenOffice：公共管理
 Notice:Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
@@ -16,20 +16,20 @@
specific language governing permissions and limitations
under the License.
 
-![Why Apache OpenOffice: Public administrations](/why/images/why_gov.png) # 
{.rfloatimg}
+![为何选择Apache OpenOffice：公共管理](/why/images/why_gov.png) # {.rfloatimg}
 
-Public administrations and people working at **all levels of government** 
(local / federal / regional / national etc) find Apache OpenOffice is their 
ideal software solution. The combination of a **flexible word processor**, a 
**powerful spreadsheet**, **dynamic graphics**, **database access** and more 
meets all the everyday needs of a typical busy office worker.
+公共管理单位以及为**各级政府机关**工作的人（无论是地方的还是中央的，区域性的还是全国性的）都会发现Apache 
OpenOffice是他们理想的软件解决方案。它的组合中包含一个**灵活的文本编辑器**，一个**强大的电子表格**，**灵活的绘图**，**数据库访问**等等，可以满足一个忙碌的办公室工作人员的所有日常办公需求。
 
-Already available in a **wide range of languages**, OpenOffice can be freely 
translated by local teams.
+OpenOffice可以被本地团队自由地翻译，所以拥有**许多不同的语言包**。
 
-  - **Best value**
+  - **价值最大化**
 
-Using Apache OpenOffice demonstrates your commitment to deliver best value 
services. It is not owned by any commercial organisation. Its open source 
licence means there are no licence fees to pay, no expensive annual audits, and 
no worries about non-compliance with onerous and obscure licencing conditions. 
You may also distribute the software free to your employees, through the 
schools system, or any other channel of your choice.
+使用Apache 
OpenOffice可以帮助你实现服务价值最大化的承诺。它不被任何商业组织所拥有。它的开源许可协议意味着没有许可证费，没有昂贵的年审，并且不用担心违反那些繁琐而又模糊不清的许可协议条款。你还可以通过教育系统或任何你选择的途径将这个软件免费分发到你的员工手里。
 
-  - **Data is safe**
+  - **数据安全保证**
 
-Freedom of Information Acts require that the documents you create today 
will be accessible years in the future. Apache OpenOffice is the first software 
in the world to use ISO approved file formats as its default. It also has the 
ability to create PDF files if you need to publish information in a standard 
'read only' format. If you already have (possibly unlicenced) office software, 
Apache OpenOffice should be able to read your old files.
+信息自由法案要求你今天所创建的文档在未来几年内都可以被访问。Apache 
OpenOffice是世界上第一款使用ISO批准的标准文件格式作为缺省格式的软件。如果你需要通过标准的“只读”格式发布信息，它同样可以创建PDF文件来满足你的要求。如果你已经有了办公软件（也许不是正版的？），Apache
 OpenOffice可以读取你的那些旧文件。
 
-  - ** Open for all**
+  - **对所有人开放**
 
-There are no secrets in Apache OpenOffice - our open-source policy means 
anyone can inspect the code or even help us develop the software. We actively 
encourage local teams to produce versions for minority languages. OpenOffice is 
a leading international force in the movement for digital inclusion - making 
software of the highest quality available to all, regardless of income.
+在Apache 
OpenOffice中没有秘密——我们的开源政策意味着任何人都可以查看源代码或者甚至帮助我们开发这个软件。我们积极鼓励本地团队制作少数民族语言的版本。OpenOffice在数字化领域是一个国际化的领导力量——它汇集来源于各方的贡献集，为所有人制作最高质量的软件。

Re: CMS diff: Why OpenOffice.org: Public administrations

Let's be careful.  Don't we already have some announcement changes on
staging?  If so we can bring this change as well onto staging, but we
should avoid publishing, since that is all-or-nothing, and we don't
want to put the announcement changes out yet.

-Rob

On Sun, Aug 19, 2012 at 11:28 AM, Shenfeng Liu anonym...@apache.org wrote:
 Clone URL (Committers only):
 https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/zh-cn%2Fwhy%2Fwhy_gov.mdtext

 Shenfeng Liu

 Index: trunk/content/zh-cn/why/why_gov.mdtext
 ===
 --- trunk/content/zh-cn/why/why_gov.mdtext  (revision 1374681)
 +++ trunk/content/zh-cn/why/why_gov.mdtext  (working copy)
 @@ -1,4 +1,4 @@
 -Title: Why OpenOffice.org: Public administrations
 +Title: 为何选择Apache OpenOffice：公共管理
  Notice:Licensed to the Apache Software Foundation (ASF) under one
 or more contributor license agreements.  See the NOTICE file
 distributed with this work for additional information
 @@ -16,20 +16,20 @@
 specific language governing permissions and limitations
 under the License.

 -![Why Apache OpenOffice: Public administrations](/why/images/why_gov.png) # 
 {.rfloatimg}
 +![为何选择Apache OpenOffice：公共管理](/why/images/why_gov.png) # {.rfloatimg}

 -Public administrations and people working at **all levels of government** 
 (local / federal / regional / national etc) find Apache OpenOffice is their 
 ideal software solution. The combination of a **flexible word processor**, a 
 **powerful spreadsheet**, **dynamic graphics**, **database access** and more 
 meets all the everyday needs of a typical busy office worker.
 +公共管理单位以及为**各级政府机关**工作的人（无论是地方的还是中央的，区域性的还是全国性的）都会发现Apache 
 OpenOffice是他们理想的软件解决方案。它的组合中包含一个**灵活的文本编辑器**，一个**强大的电子表格**，**灵活的绘图**，**数据库访问**等等，可以满足一个忙碌的办公室工作人员的所有日常办公需求。

 -Already available in a **wide range of languages**, OpenOffice can be freely 
 translated by local teams.
 +OpenOffice可以被本地团队自由地翻译，所以拥有**许多不同的语言包**。

 -  - **Best value**
 +  - **价值最大化**

 -Using Apache OpenOffice demonstrates your commitment to deliver best 
 value services. It is not owned by any commercial organisation. Its open 
 source licence means there are no licence fees to pay, no expensive annual 
 audits, and no worries about non-compliance with onerous and obscure 
 licencing conditions. You may also distribute the software free to your 
 employees, through the schools system, or any other channel of your choice.
 +使用Apache 
 OpenOffice可以帮助你实现服务价值最大化的承诺。它不被任何商业组织所拥有。它的开源许可协议意味着没有许可证费，没有昂贵的年审，并且不用担心违反那些繁琐而又模糊不清的许可协议条款。你还可以通过教育系统或任何你选择的途径将这个软件免费分发到你的员工手里。

 -  - **Data is safe**
 +  - **数据安全保证**

 -Freedom of Information Acts require that the documents you create today 
 will be accessible years in the future. Apache OpenOffice is the first 
 software in the world to use ISO approved file formats as its default. It 
 also has the ability to create PDF files if you need to publish information 
 in a standard 'read only' format. If you already have (possibly unlicenced) 
 office software, Apache OpenOffice should be able to read your old files.
 +信息自由法案要求你今天所创建的文档在未来几年内都可以被访问。Apache 
 OpenOffice是世界上第一款使用ISO批准的标准文件格式作为缺省格式的软件。如果你需要通过标准的“只读”格式发布信息，它同样可以创建PDF文件来满足你的要求。如果你已经有了办公软件（也许不是正版的？），Apache
  OpenOffice可以读取你的那些旧文件。

 -  - ** Open for all**
 +  - **对所有人开放**

 -There are no secrets in Apache OpenOffice - our open-source policy means 
 anyone can inspect the code or even help us develop the software. We actively 
 encourage local teams to produce versions for minority languages. OpenOffice 
 is a leading international force in the movement for digital inclusion - 
 making software of the highest quality available to all, regardless of income.
 +在Apache 
 OpenOffice中没有秘密——我们的开源政策意味着任何人都可以查看源代码或者甚至帮助我们开发这个软件。我们积极鼓励本地团队制作少数民族语言的版本。OpenOffice在数字化领域是一个国际化的领导力量——它汇集来源于各方的贡献集，为所有人制作最高质量的软件。

Re: [DISCUSS] AOO Ready to Graduate

2012-08-19 Thread Donald Harbison

On Fri, Aug 17, 2012 at 11:55 AM, Rob Weir robw...@apache.org wrote:

 We've had several prods from our mentors suggesting that we are ready
 to graduate.  But I think there was general recognition that with
 graduation comes a little hump in extra work, both for the project as
 well as the IPMC and Infra, especially related to mailing list and
 website changes [1].  We wanted to avoid piling that on top of the
 already considerable work required to get AOO 3.4.1 released.

 The AOO 3.4.1 release is now being voted on.  So I think it is a good
 time for us to start this process.

 I'd recommend everyone take a look at this timeline [2] for what the
 graduation process looks like.  You can see it is three steps:

 1) Optional Community vote [3]

 2) Preparation of a Charter and Resolution [4]

 3) Vote by the IPMC to recommend the Charter/Resolution to the ASF Board.

 4) Approval by the ASF Board.

 As I understand it the ASF Board meeting on the 3rd Wednesday of each
 month.  So the next meeting should be September 19th.  If we start
 now, we should have plenty of time to work through this process in
 time for that meeting.

 I'd like to start the first step, with the optional, but highly
 recommended, community vote, stating our belief that we are ready to
 graduate.


+1 Let's get this started this week.



 Regards,

 -Rob


 [1]
 http://incubator.apache.org/guides/graduation.html#project-first-steps

 [2] http://incubator.apache.org/guides/graduation.html#process

 [3] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

 [4] http://incubator.apache.org/guides/graduation.html#tlp-resolution

CMS diff: Why Apache OpenOffice: Education

Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/zh-cn%2Fwhy%2Fwhy_edu.mdtext

Shenfeng Liu

Index: trunk/content/zh-cn/why/why_edu.mdtext
===
--- trunk/content/zh-cn/why/why_edu.mdtext  (revision 1374681)
+++ trunk/content/zh-cn/why/why_edu.mdtext  (working copy)
@@ -1,4 +1,4 @@
-Title: Why Apache OpenOffice: Education
+Title: 为何选择Apache OpenOffice：教育
 Notice:Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
@@ -16,20 +16,20 @@
specific language governing permissions and limitations
under the License.
 
-![Why Apache OpenOffice: Education](/why/images/why_edu.png) # {.rfloatimg}
+![为何选择Apache OpenOffice：教育](/why/images/why_edu.png) # {.rfloatimg}
 
-Education establishments of all levels (primary, secondary, college, 
university...) find Apache OpenOffice meets the needs of both teachers and 
students. The **flexible word processor**, **powerful spreadsheet**, **dynamic 
graphics**, **database access** and more meet all requirements for an office 
software package.
+各级教育机构（小学，中学，大学和各级学院……）都发现Apache 
OpenOffice完全可以满足师生的要求。**灵活的文本编辑器**，**强大的电子表格**，**灵活的绘图**，**数据库访问**等等，可以满足大家对一个办公软件包的所有需求。
 
-With an **open-source licence**, OpenOffice can be freely used and distributed 
with no licence worries.
+因为使用了**开源许可协议**，OpenOffice可以被自由地免费使用和分发，而不存在许可协议上的顾虑。
 
-  - **For pupils and students**
+  - **为学生和学者**
 
-Apache OpenOffice forms an ideal teaching platform for core computer 
literacy skills, without tying students to commercial products. The free 
software licence means students can be given copies of software to use at home 
- perfectly legally - a useful 'added value'. For IT students, OpenOffice's 
component based software is also an ideal platform for developing IT skills and 
understanding real-life software engineering.
+Apache 
OpenOffice构造了一个理想的核心计算机文化技能教育平台，而不必将学生们绑定到商业产品上。免费软件许可协议意味着学生们可以将软件拷贝回家使用——完全合法——这对他们是非常有价值和有意义的。对以信息技术专业的学生，OpenOffice这款高度模块化的软件是一个理想的平台，让学生们练习和拓展IT技能并了解现实中的软件工程。
 
-  - **For teachers and academics**
+  - **为老师和学院**
 
-Apache OpenOffice is also an ideal platform for creating teaching 
materials and managing administrative tasks. For example, the *Writer* word 
processor is easy to use for simple memos, but also powerful enough to cope 
with complex dissertations. For IT staff, the open-source software licence 
means an end to licence compliance worries and the threat of software audits. 
OpenOffice is developed, translated, and supported by an international 
community linked by the internet, opening exciting possibilities for school 
projects. 
+Apache 
OpenOffice同样是一个开发教学资料和进行教学管理的理想平台。比如，Writer文本编辑器可以轻松处理简单的备忘录，或者提供丰富强大的功能来编撰复杂的学术论文。对于IT员工，开源软件许可协议意味着不再需要担心是否遵守了许可证协议，或者如何通过软件审查。OpenOffice是由一个通过互联网链接起来的国际化社区来开发、翻译和支持的，对学校项目来说，它有很多开放和令人兴奋的参与机会。
 
-  - **Open for all**
+  - **对所有人开放**
 
-Apache OpenOffice is a leading international force in the movement for 
digital inclusion - making software of the highest quality available to all, 
regardless of income. OpenOffice is available in a wide variety of languages, 
and we actively encourage local teams to produce versions for local languages. 
We develop software on an open-source process - the computing equivalent of 
peer-reviewed publishing - creating software of the highest quality.
+Apache 
OpenOffice在数字化领域是一个国际化的领导力量——它汇集来源于各方的贡献集，为所有人制作最高质量的软件。OpenOffice拥有许多不同的语言版本，而且我们积极鼓励本地团队来参与制作本地语言的版本。我们在一个开源流程下进行软件开发——在发布过程中进行平等的结对审查——以创造更高的质量。

CMS diff: Why Apache OpenOffice

Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/zh-cn%2Fwhy%2Findex.mdtext

Shenfeng Liu

Index: trunk/content/zh-cn/why/index.mdtext
===
--- trunk/content/zh-cn/why/index.mdtext(revision 1374681)
+++ trunk/content/zh-cn/why/index.mdtext(working copy)
@@ -24,7 +24,7 @@
 
   - [杰出的软件](why_great.html)
 
-Apache 
OpenOffice凝聚了二十多年软件工程的结晶。它从最初的单一功能软件开始，秉承一致，专注发展，是其它许多产品所不能比拟的。它采用完全开放的开发流程，这意味着每个人都可以报告产品缺陷，或对这个软件提出新功能或功能增强的需求。其结果就是：
 Apache OpenOffice能够如你所愿做到你期望一个办公软件为你做到的任何事。
+Apache 
OpenOffice凝聚了二十多年软件工程的结晶。它从最初的一体软件开始，秉承一致，专注发展，是其它许多产品所不能比拟的。它采用完全开放的开发流程，这意味着每个人都可以报告产品缺陷，或对这个软件提出新功能或功能增强的需求。其结果就是：
 Apache OpenOffice能够如你所愿做到你期望一个办公软件为你做到的任何事。
 
   - [易于使用](why_easy.html)

Re: [DISCUSS] AOO Ready to Graduate

On Sat, Aug 18, 2012 at 2:43 AM, Andrea Pescetti pesce...@apache.org wrote:
 On 17/08/2012 Rob Weir wrote:

 We've had several prods from our mentors suggesting that we are ready
 to graduate.


 I agree it would be good to do so, since it will automatically reduce
 complex and unclear terminology (incubator, podling) that has been
 misused outside the project and it will make governance easier.


 I'd recommend everyone take a look at this timeline [2] for what the
 graduation process looks like.  You can see it is three steps:
 1) Optional Community vote [3]
 2) Preparation of a Charter and Resolution [4]
 3) Vote by the IPMC to recommend the Charter/Resolution to the ASF Board.
 4) Approval by the ASF Board.


 If the Charter needs to contain complex statements about scope and mission
 of the project, it will take some time (but this is not the case, if I
 understand the the examples correctly).


It is not clear to me what the charter actually does.  What does it
mean organizationally?  Does it obligate or constrain the project in
any formal way?  Or is it just a convenient summary of the project's
focus?  For example, has anything bad ever happened to any Apache
project because their charter was too narrow (or too broad)?  If not I
would not worry too much about it.

 It also seems, from the links, that the project will need to elect a chair,
 and this would be quite time-consuming too.


If there is just a single nominee then this is easy.  If we have 2
nominees, we could have a 72-hour vote.  But if have more than two,
then we need to think about either a multi-stage voting process (run
off elections), or a transferable vote system.   But I don't this will
 take much time.  And it could be done in parallel with drafting the
charter.

Of course, if no one wants to be Chair, then this can take longer ;-)

 So I wouldn't be sure that we can have everything ready by the September
 Board meeting.


If we make it by then, great.  If not, then October is a fine month as well.

Another thing we need to do is determine the membership of the PMC.
This would likely be the current PPMC, minus those who signed up when
the podling started but then never actually got involved with the
project.   I assume we would also want to extend an invitation to any
Mentors who wish to continue with the project as PMC members.  But
that can be done in parallel as well.  This all gets wrapped into one
proposed Resolution: charter, PMC members and PMC Chair.

-Rob


 I'd like to start the first step, with the optional, but highly
 recommended, community vote, stating our belief that we are ready to
 graduate.


 I agree. If we have consensus that we are ready to graduate, let's start
 with a formal vote about it, and then proceed step by step with the process.

 Regards,
   Andrea.

[VOTE] Apache OpenOffice Community Graduation Vote

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

[VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

Please vote in the main [VOTE] thread, and have discussion in this thread.

Thanks!

-Rob

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread RGB ES

2012/8/19 Rob Weir robw...@apache.org:
 Per the IPMC's Guide to Successful Graduation [1] this is the
 optional, but recommended, community vote for us to express our
 willingness/readiness to govern ourselves.  If this vote passes then
 we continue by drafting a charter, submitting it for IPMC endorsement,
 and then to the ASF Board for final approval.   Details can be found
 in the Guide to Successful Graduation.

 Everyone in the community is encouraged to vote.  Votes from PPMC
 members and Mentors are binding.  This vote will run 72-hours.


 [ ] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1  Apache OpenOffice community is not ready to graduate from the
 Apache Incubator because...


 Regards,

 -Rob

 [1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

+1  Apache OpenOffice community is ready to graduate from the Apache Incubator.

Regards
Ricardo

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Rory O'Farrell

On Sun, 19 Aug 2012 11:52:33 -0400
Rob Weir robw...@apache.org wrote:

 Per the IPMC's Guide to Successful Graduation [1] this is the
 optional, but recommended, community vote for us to express our
 willingness/readiness to govern ourselves.  If this vote passes then
 we continue by drafting a charter, submitting it for IPMC endorsement,
 and then to the ASF Board for final approval.   Details can be found
 in the Guide to Successful Graduation.
 
 Everyone in the community is encouraged to vote.  Votes from PPMC
 members and Mentors are binding.  This vote will run 72-hours.
 
 
 [ ] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1  Apache OpenOffice community is not ready to graduate from the
 Apache Incubator because...

+1  Apache OpenOffice community is ready to graduate from the Apache Incubator.


-- 
Rory O'Farrell ofarr...@iol.ie

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Carl Marcum

+1  Apache OpenOffice community is ready to graduate from the Apache 
Incubator.


Best regards,
Carl

On 08/19/2012 11:52 AM, Rob Weir wrote:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Reizinger Zoltán


2012.08.19. 17:52 keltezéssel, Rob Weir írta:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote


+1  Apache OpenOffice community is ready to graduate from the Apache Incubator.

Zoltan

Re: [DISCUSS] AOO Ready to Graduate


On Aug 19, 2012, at 8:48 AM, Rob Weir wrote:

 On Sat, Aug 18, 2012 at 2:43 AM, Andrea Pescetti pesce...@apache.org wrote:
 On 17/08/2012 Rob Weir wrote:
 
 We've had several prods from our mentors suggesting that we are ready
 to graduate.
 
 
 I agree it would be good to do so, since it will automatically reduce
 complex and unclear terminology (incubator, podling) that has been
 misused outside the project and it will make governance easier.
 
 
 I'd recommend everyone take a look at this timeline [2] for what the
 graduation process looks like.  You can see it is three steps:
 1) Optional Community vote [3]

1.5) Make sure that everything on the status page is checked off.

Someone needs to enter the date of the trademark transfer and the mentors have 
some check-offs.

 2) Preparation of a Charter and Resolution [4]
 3) Vote by the IPMC to recommend the Charter/Resolution to the ASF Board.
 4) Approval by the ASF Board.
 
 
 If the Charter needs to contain complex statements about scope and mission
 of the project, it will take some time (but this is not the case, if I
 understand the the examples correctly).
 
 
 It is not clear to me what the charter actually does.  What does it
 mean organizationally?  Does it obligate or constrain the project in
 any formal way?  Or is it just a convenient summary of the project's
 focus?  For example, has anything bad ever happened to any Apache
 project because their charter was too narrow (or too broad)?  If not I
 would not worry too much about it.

The Charter / Board Resolution establishes the PMC.

Here is a recent example from general@i.a.o for Lucene.Net - just now passed by 
the Board:

 X. Establish the Apache Lucene.Net Project
 
 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software related to maintaining a .NET platform
 version of the Lucene Indexing Engine for distribution at
 no charge to the public.
 
 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Lucene.Net Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further
 
 RESOLVED, that the Apache Lucene.Net
 Project be and hereby is responsible for the creation and 
 maintenance of software related to maintaining a .NET 
 platform version of the Lucene Indexing Engine and be 
 it further
 


I purposefully used another project as an example. There are two phrases that 
are important.

(1) Lucene.Net - in our case this is OpenOffice

(2) related to maintaining a .NET platform version of the Lucene Indexing 
Engine and this is the phrase that will describe the scope of the project and 
should be carefully considered and likely not too narrow.

... likely this should be another thread.

 
 It also seems, from the links, that the project will need to elect a chair,
 and this would be quite time-consuming too.
 
 
 If there is just a single nominee then this is easy.  If we have 2
 nominees, we could have a 72-hour vote.  But if have more than two,
 then we need to think about either a multi-stage voting process (run
 off elections), or a transferable vote system.   But I don't this will
 take much time.  And it could be done in parallel with drafting the
 charter.
 
 Of course, if no one wants to be Chair, then this can take longer ;-)
 
 So I wouldn't be sure that we can have everything ready by the September
 Board meeting.
 
 
 If we make it by then, great.  If not, then October is a fine month as well.
 
 Another thing we need to do is determine the membership of the PMC.
 This would likely be the current PPMC, minus those who signed up when
 the podling started but then never actually got involved with the
 project.   I assume we would also want to extend an invitation to any
 Mentors who wish to continue with the project as PMC members.  But
 that can be done in parallel as well.  This all gets wrapped into one
 proposed Resolution: charter, PMC members and PMC Chair.

I think we should decide on the PMC before we decide on the Chair.

Regards,
Dave


 
 -Rob
 
 
 I'd like to start the first step, with the optional, but highly
 recommended, community vote, stating our belief that we are ready to
 graduate.
 
 
 I agree. If we have consensus that we are ready to graduate, let's start
 with a formal vote about it, and then proceed step by step with the process.
 
 Regards,
  Andrea.

Re: [DISCUSS] AOO Ready to Graduate

2012-08-19 Thread Roberto Salomon

Agreed..

--
Roberto Salomon

Enviado do meu celular Android
Em 18/08/2012 13:27, Jürgen Lange j...@juergen-lange.de escreveu:

I think its time to start the process
+1

Jürgen

Am 17.08.2012 17:55, schrieb Rob Weir:

We've had several prods from our mentors suggesting that we are ready
to graduate. But I think there was general recognition that with
graduation comes a little hump in extra work, both for the project as
well as the IPMC and Infra, especially related to mailing list and
website changes [1]. We wanted to avoid piling that on top of the
already considerable work required to get AOO 3.4.1 released.

The AOO 3.4.1 release is now being voted on. So I think it is a good
time for us to start this process.

I'd recommend everyone take a look at this timeline [2] for what the
graduation process looks like. You can see it is three steps:

1) Optional Community vote [3]

2) Preparation of a Charter and Resolution [4]

3) Vote by the IPMC to recommend the Charter/Resolution to the ASF Board.

4) Approval by the ASF Board.

As I understand it the ASF Board meeting on the 3rd Wednesday of each
month. So the next meeting should be September 19th. If we start
now, we should have plenty of time to work through this process in
time for that meeting.

I'd like to start the first step, with the optional, but highly
recommended, community vote, stating our belief that we are ready to
graduate.

Regards,

-Rob

[1] http://incubator.apache.org/**guides/graduation.html#**
project-first-stepshttp://incubator.apache.org/guides/graduation.html#project-first-steps

[2]
http://incubator.apache.org/**guides/graduation.html#processhttp://incubator.apache.org/guides/graduation.html#process

[3] http://incubator.apache.org/**guides/graduation.html#tlp-**
community-votehttp://incubator.apache.org/guides/graduation.html#tlp-community-vote

[4]
http://incubator.apache.org/**guides/graduation.html#tlp-**resolutionhttp://incubator.apache.org/guides/graduation.html#tlp-resolution

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Keith N. McKenna


Rob Weir wrote:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote



+1 Apache OpenOffice community is ready to graduate from the Apache 
Incubator.


Keith N. McKenna

Something wrong on SF download statistics

2012-08-19 Thread Reizinger Zoltán


Hi all,

I looked around of SF download site, to write Hungarian download 
statistics in a blog post.


I checked the AOO 3.4.0 data from here:

http://sourceforge.net/projects/openofficeorg.mirror/files/stats/map?dates=2012-05-08+to+2012-08-19

Hungary in the 28th place. If I sum up all platform download numbers, I 
get 44786, the Total is 57,235.


The difference is 12 499.

Maybe some bug in creation of this statistics?

Regards,
Zoltan

Re: svn commit: r829379 - in /websites/production/ooo-site: cgi-bin/ content/

We were supposed to wait to publish.

Regards,
Dave

On Aug 19, 2012, at 8:08 AM, pesce...@apache.org wrote:

 Author: pescetti
 Date: Sun Aug 19 15:08:26 2012
 New Revision: 829379
 
 Log:
 Publishing svnmucc operation to ooo-site site by pescetti
 
 Added:
websites/production/ooo-site/cgi-bin/
  - copied from r829378, websites/staging/ooo-site/trunk/cgi-bin/
websites/production/ooo-site/content/
  - copied from r829378, websites/staging/ooo-site/trunk/content/

Re: 3.4.1 release notes now on the web server

On 08/18/2012 05:05 PM, Keith N. McKenna wrote:

Kay Schenk wrote:

On Sat, Aug 18, 2012 at 12:36 PM, Keith N. McKenna
keith.mcke...@comcast.net wrote:

Kay Schenk wrote:

... at

http://www.openoffice.org/**development/releases/3.4.1.**htmlhttp://www.openoffice.org/development/releases/3.4.1.html

Please make any further changes to web document and not the
cwiki doc. Thanks.

This is not linked from:

http://www.openoffice.org/**development/releases/http://www.openoffice.org/development/releases/

yet, until we're ready to do the announcement.

Kay;

I was just starting on making a change to the Release Notes on
the wiki when I saw your post. The change was to be a link to the
porting page for FreeBSD, etc.

I admit to being a total novice when it comes to HTML editing,
but if there is a way to easily make the change without a high
probability of screwing something else up I would be happy to try
and do it.

Regards Keith

Well, you could supply what you want to say here and I'll be happy
to take care of it if you're nto comfortable with this.

And, Thank You, Andrea for supplying the warning about making
changes to the cwiki version -- why didn't I think of that? :/

Kay;

Than you very much or the offer to make the change. This close to a
release I would hate to have my novice ineptitude screw anything up.

Well I doubt you could do much harm.

The text I was going to add was. A number of community members are
working on ports or Solaris, FreeBSD, and OS/2. You can learn more
rom our Porting page at: http://www.openoffice.org/porting/

Super -- yes, I was just thinking of doing something similar, and
actually expanding the list of what we do have as official platform
releases. So, will do!

I there is documentation on an easy way to make these kind of changes
that you can point me to it would be greatly appreciated. Hopefully
I can learn enough to be at least quasi-comfortable in the future.

see the CMS Reference page: http://www.apache.org/dev/cmsref.html

You can watch Rob's videos! :)

It's pretty easy but you do need to know html.

Regards Keith

MzK

Never express yourself more clearly than you are able to think.
-- Niels Bohr

Re: [VOTE] Apache OpenOffice Community Graduation Vote




On 08/19/2012 08:52 AM, Rob Weir wrote:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote



+1 Apache OpenOffice community is ready to graduate from the Apache 
Incubator

--

MzK

Never express yourself more clearly than you are able to think.
   -- Niels Bohr

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Roberto Galoppini

On Sun, Aug 19, 2012 at 5:52 PM, Rob Weir robw...@apache.org wrote:

 Per the IPMC's Guide to Successful Graduation [1] this is the
 optional, but recommended, community vote for us to express our
 willingness/readiness to govern ourselves.  If this vote passes then
 we continue by drafting a charter, submitting it for IPMC endorsement,
 and then to the ASF Board for final approval.   Details can be found
 in the Guide to Successful Graduation.

 Everyone in the community is encouraged to vote.  Votes from PPMC
 members and Mentors are binding.  This vote will run 72-hours.


 [ ] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1  Apache OpenOffice community is not ready to graduate from the
 Apache Incubator because...



+1  Apache OpenOffice community is ready to graduate from the Apache
Incubator.

Roberto



 Regards,

 -Rob

 [1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote


-- 

This e- mail message is intended only for the named recipient(s) above. It 
may contain confidential and privileged information. If you are not the 
intended recipient you are hereby notified that any dissemination, 
distribution or copying of this e-mail and any attachment(s) is strictly 
prohibited. If you have received this e-mail in error, please immediately 
notify the sender by replying to this e-mail and delete the message and any 
attachment(s) from your system. Thank you.

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread imacat

On 2012/08/19 23:52, Rob Weir said:
 Per the IPMC's Guide to Successful Graduation [1] this is the
 optional, but recommended, community vote for us to express our
 willingness/readiness to govern ourselves.  If this vote passes then
 we continue by drafting a charter, submitting it for IPMC endorsement,
 and then to the ASF Board for final approval.   Details can be found
 in the Guide to Successful Graduation.
 
 Everyone in the community is encouraged to vote.  Votes from PPMC
 members and Mentors are binding.  This vote will run 72-hours.
 
 
 [ ] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1  Apache OpenOffice community is not ready to graduate from the
 Apache Incubator because...

+1 from me.

 
 
 Regards,
 
 -Rob
 
 [1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote


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

Woman's Voice 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/



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Andrea Pescetti


Rob Weir wrote:

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.
[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


+1  Apache OpenOffice community is ready to graduate from the Apache 
Incubator.


Andrea

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Regina Henschel


Hi,

Rob Weir schrieb:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.




 +1  Apache OpenOffice community is ready to graduate from the Apache 
Incubator.


Kind regard
Regina

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Ross Gardler

I'm unable to vote either way until:

A) a PMC chair has been identified by the community

B) a resolution for the TLP is prepared which will define what we are
voting on

Note, I'm generally in favour of the proposal but I do want to be sure that
the community has the resources it needs to continue to build and maintain
a healthy,vibrant and inclusive community. There are some candidates for
PMC chair that I can think of, but I don't know if they want the role.

In a healthy community the PMC role is just taking responsibility for board
reports (not necessarily writing them, just making sure they get written)
and any community actions requested by the board. It shouldn't be a time
consuming role, but it can become so on occasion.

This query should not prevent the community expressing their opinion in the
vote. I just wanted to let you know why I will be abstaining. You only need
my vote when it comes to the actual graduation vote.

Ross
 On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:

 Please vote in the main [VOTE] thread, and have discussion in this thread.

 Thanks!

 -Rob

Re: svn commit: r829379 - in /websites/production/ooo-site: cgi-bin/ content/

2012-08-19 Thread Andrea Pescetti


Dave Fisher wrote:

We were supposed to wait to publish.

Author: pescetti
Date: Sun Aug 19 15:08:26 2012
New Revision: 829379


What did I publish? If it was only (like the diff showed)
http://www.openoffice.org/it/stampa/comunicati/aoo341.html
then it's OK to have it online. It's not linked and I prefer to prepare 
pages online in advance and only link them at the last minute.


If I accidentally published something else, just let me know, but from 
the diff it seemed I was only going to publish the page above and that 
was intentional... Unless we want to keep the pages offline (on staging) 
until the announcement, but then there's the risk that we cannot catch 
errors in internal links.


Regards,
  Andrea.

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote


On Aug 19, 2012, at 1:43 PM, Ross Gardler wrote:

 I'm unable to vote either way until:
 
 A) a PMC chair has been identified by the community
 
 B) a resolution for the TLP is prepared which will define what we are
 voting on
 
 Note, I'm generally in favour of the proposal but I do want to be sure that
 the community has the resources it needs to continue to build and maintain
 a healthy,vibrant and inclusive community. There are some candidates for
 PMC chair that I can think of, but I don't know if they want the role.
 
 In a healthy community the PMC role is just taking responsibility for board
 reports (not necessarily writing them, just making sure they get written)
 and any community actions requested by the board. It shouldn't be a time
 consuming role, but it can become so on occasion.
 
 This query should not prevent the community expressing their opinion in the
 vote. I just wanted to let you know why I will be abstaining. You only need
 my vote when it comes to the actual graduation vote.

I understand.

BTW - There are some Mentor related status items on [1] that need action. Would 
you be able to take care of those items?

Thanks  Regards,
Dave

[1] http://incubator.apache.org/projects/openofficeorg.html

 
 Ross
 On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:
 
 Please vote in the main [VOTE] thread, and have discussion in this thread.
 
 Thanks!
 
 -Rob

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Graham Lauder

 Per the IPMC's Guide to Successful Graduation [1] this is the
 optional, but recommended, community vote for us to express our
 willingness/readiness to govern ourselves.  If this vote passes then
 we continue by drafting a charter, submitting it for IPMC endorsement,
 and then to the ASF Board for final approval.   Details can be found
 in the Guide to Successful Graduation.
 
 Everyone in the community is encouraged to vote.  Votes from PPMC
 members and Mentors are binding.  This vote will run 72-hours.
 
 
 [ ] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1  Apache OpenOffice community is not ready to graduate from the
 Apache Incubator because...
 
 
 Regards,
 
 -Rob



+1 Let's get this party started

Cheers
GL

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Ross Gardler

Regarding finishing my duties as a mentor - yes I'll certainly help. I seem
to have hit an extremely busy period that doesn't seem to be ending, but I
intend to finish things off here. As I am sure other mentors are.

Ross
On Aug 19, 2012 10:08 PM, Dave Fisher dave2w...@comcast.net wrote:


 On Aug 19, 2012, at 1:43 PM, Ross Gardler wrote:

  I'm unable to vote either way until:
 
  A) a PMC chair has been identified by the community
 
  B) a resolution for the TLP is prepared which will define what we are
  voting on
 
  Note, I'm generally in favour of the proposal but I do want to be sure
 that
  the community has the resources it needs to continue to build and
 maintain
  a healthy,vibrant and inclusive community. There are some candidates for
  PMC chair that I can think of, but I don't know if they want the role.
 
  In a healthy community the PMC role is just taking responsibility for
 board
  reports (not necessarily writing them, just making sure they get written)
  and any community actions requested by the board. It shouldn't be a time
  consuming role, but it can become so on occasion.
 
  This query should not prevent the community expressing their opinion in
 the
  vote. I just wanted to let you know why I will be abstaining. You only
 need
  my vote when it comes to the actual graduation vote.

 I understand.

 BTW - There are some Mentor related status items on [1] that need action.
 Would you be able to take care of those items?

 Thanks  Regards,
 Dave

 [1] http://incubator.apache.org/projects/openofficeorg.html

 
  Ross
  On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:
 
  Please vote in the main [VOTE] thread, and have discussion in this
 thread.
 
  Thanks!
 
  -Rob

Re: svn commit: r829379 - in /websites/production/ooo-site: cgi-bin/ content/

On Sun, Aug 19, 2012 at 1:45 PM, Andrea Pescetti pesce...@apache.orgwrote:

 Dave Fisher wrote:

 We were supposed to wait to publish.

 Author: pescetti
 Date: Sun Aug 19 15:08:26 2012
 New Revision: 829379


 What did I publish? If it was only (like the diff showed)
 http://www.openoffice.org/it/**stampa/comunicati/aoo341.htmlhttp://www.openoffice.org/it/stampa/comunicati/aoo341.html
 then it's OK to have it online. It's not linked and I prefer to prepare
 pages online in advance and only link them at the last minute.

 If I accidentally published something else, just let me know, but from the
 diff it seemed I was only going to publish the page above and that was
 intentional... Unless we want to keep the pages offline (on staging) until
 the announcement, but then there's the risk that we cannot catch errors in
 internal links.

 Regards,
   Andrea.


Andrea (and Dave), as an FYI...I basically did the same thing with the
writeup for the 3.4.1 release notes. It's not linked in to anything, it's
just out there, and announced here for folks to make further modifications
if necessary.
Since it takes a little bit of futzing to convert from cwiki to html, I
didn't want to leave this until the last minute.



-- 

MzK

Never express yourself more clearly than you are able to think.
--
Niels Bohr

RE: [DISCUSS] AOO Ready to Graduate

2012-08-19 Thread Dennis E. Hamilton

+1 on prerequisites.  

-Original Message-
From: Dave Fisher [mailto:dave2w...@comcast.net] 
Sent: Sunday, August 19, 2012 09:40
To: ooo-dev@incubator.apache.org
Subject: Re: [DISCUSS] AOO Ready to Graduate

On Aug 19, 2012, at 8:48 AM, Rob Weir wrote:

 On Sat, Aug 18, 2012 at 2:43 AM, Andrea Pescetti pesce...@apache.org wrote:
 On 17/08/2012 Rob Weir wrote:

 We've had several prods from our mentors suggesting that we are ready
 to graduate.

 I agree it would be good to do so, since it will automatically reduce
 complex and unclear terminology (incubator, podling) that has been
 misused outside the project and it will make governance easier.

 I'd recommend everyone take a look at this timeline [2] for what the
 graduation process looks like.  You can see it is three steps:
 1) Optional Community vote [3]

1.5) Make sure that everything on the status page is checked off.

Someone needs to enter the date of the trademark transfer and the mentors have 
some check-offs.

 2) Preparation of a Charter and Resolution [4]
 3) Vote by the IPMC to recommend the Charter/Resolution to the ASF Board.
 4) Approval by the ASF Board.

 If the Charter needs to contain complex statements about scope and mission
 of the project, it will take some time (but this is not the case, if I
 understand the the examples correctly).

 It is not clear to me what the charter actually does.  What does it
 mean organizationally?  Does it obligate or constrain the project in
 any formal way?  Or is it just a convenient summary of the project's
 focus?  For example, has anything bad ever happened to any Apache
 project because their charter was too narrow (or too broad)?  If not I
 would not worry too much about it.

The Charter / Board Resolution establishes the PMC.

Here is a recent example from general@i.a.o for Lucene.Net - just now passed by 
the Board:

 X. Establish the Apache Lucene.Net Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software related to maintaining a .NET platform
 version of the Lucene Indexing Engine for distribution at
 no charge to the public.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Lucene.Net Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Lucene.Net
 Project be and hereby is responsible for the creation and 
 maintenance of software related to maintaining a .NET 
 platform version of the Lucene Indexing Engine and be 
 it further

I purposefully used another project as an example. There are two phrases that 
are important.

(1) Lucene.Net - in our case this is OpenOffice

(2) related to maintaining a .NET platform version of the Lucene Indexing 
Engine and this is the phrase that will describe the scope of the project and 
should be carefully considered and likely not too narrow.

... likely this should be another thread.

 It also seems, from the links, that the project will need to elect a chair,
 and this would be quite time-consuming too.

 If there is just a single nominee then this is easy.  If we have 2
 nominees, we could have a 72-hour vote.  But if have more than two,
 then we need to think about either a multi-stage voting process (run
 off elections), or a transferable vote system.   But I don't this will
 take much time.  And it could be done in parallel with drafting the
 charter.

 Of course, if no one wants to be Chair, then this can take longer ;-)

 So I wouldn't be sure that we can have everything ready by the September
 Board meeting.

 If we make it by then, great.  If not, then October is a fine month as well.

 Another thing we need to do is determine the membership of the PMC.
 This would likely be the current PPMC, minus those who signed up when
 the podling started but then never actually got involved with the
 project.   I assume we would also want to extend an invitation to any
 Mentors who wish to continue with the project as PMC members.  But
 that can be done in parallel as well.  This all gets wrapped into one
 proposed Resolution: charter, PMC members and PMC Chair.

I think we should decide on the PMC before we decide on the Chair.

Regards,
Dave

 -Rob

 I'd like to start the first step, with the optional, but highly
 recommended, community vote, stating our belief that we are ready to
 graduate.

 I agree. If we have consensus that we are ready to graduate, let's start
 with a formal vote about it, and then proceed step by step with the process.

 Regards,
  Andrea.

RE: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Dennis E. Hamilton

+0 Abstain (binding)

-Original Message-
From: Rob Weir [mailto:robw...@apache.org] 
Sent: Sunday, August 19, 2012 08:53
To: ooo-dev@incubator.apache.org
Subject: [VOTE] Apache OpenOffice Community Graduation Vote

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.

[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...

Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Jürgen Lange


[x] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.

Jürgen

Am 19.08.2012 17:52, schrieb Rob Weir:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread tj


On 8/19/2012 11:52, Rob Weir wrote:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


 [x] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.

The real test will be the process (not the result, the process) of 
picking the PMC and the Chair. Should be interesting.


/tj/

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

On Sun, Aug 19, 2012 at 4:43 PM, Ross Gardler
rgard...@opendirective.com wrote:
 I'm unable to vote either way until:

 A) a PMC chair has been identified by the community

 B) a resolution for the TLP is prepared which will define what we are
 voting on


Those points will be addressed in the proposed Resolution we send to
the IPMC.  What we're having right now is the preliminary community
graduation vote, which according this diagram from the IPMC's Guide
to Successful Graduation occurs *before* the charter is created:

http://incubator.apache.org/guides/graduation.html#toplevel

Not that this same guide says of this community vote, It is unlikely
that IPMC members will vote to approve graduation unless the Mentors
and community positively express their readiness for graduation.   So
I am slightly concerned that you do not feel able to vote in this
ballot, which merely expresses (per the graduation guidelines) our
readiness for graduation.

-Rob

 Note, I'm generally in favour of the proposal but I do want to be sure that
 the community has the resources it needs to continue to build and maintain
 a healthy,vibrant and inclusive community. There are some candidates for
 PMC chair that I can think of, but I don't know if they want the role.

 In a healthy community the PMC role is just taking responsibility for board
 reports (not necessarily writing them, just making sure they get written)
 and any community actions requested by the board. It shouldn't be a time
 consuming role, but it can become so on occasion.

 This query should not prevent the community expressing their opinion in the
 vote. I just wanted to let you know why I will be abstaining. You only need
 my vote when it comes to the actual graduation vote.

 Ross
  On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:

 Please vote in the main [VOTE] thread, and have discussion in this thread.

 Thanks!

 -Rob

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

On Sun, Aug 19, 2012 at 5:07 PM, Dave Fisher dave2w...@comcast.net wrote:

 On Aug 19, 2012, at 1:43 PM, Ross Gardler wrote:

 I'm unable to vote either way until:

 A) a PMC chair has been identified by the community

 B) a resolution for the TLP is prepared which will define what we are
 voting on

 Note, I'm generally in favour of the proposal but I do want to be sure that
 the community has the resources it needs to continue to build and maintain
 a healthy,vibrant and inclusive community. There are some candidates for
 PMC chair that I can think of, but I don't know if they want the role.

 In a healthy community the PMC role is just taking responsibility for board
 reports (not necessarily writing them, just making sure they get written)
 and any community actions requested by the board. It shouldn't be a time
 consuming role, but it can become so on occasion.

 This query should not prevent the community expressing their opinion in the
 vote. I just wanted to let you know why I will be abstaining. You only need
 my vote when it comes to the actual graduation vote.

 I understand.

 BTW - There are some Mentor related status items on [1] that need action. 
 Would you be able to take care of those items?


So the items I see as not marked as done are:

1. Make sure that the requested project name does not already exist
and check www.nameprotect.com to be sure that the name is not already
trademarked for an existing software product.

2. Subscribe all Mentors on the pmc and general lists.

3. Give all Mentors access to the incubator SVN repository. (to be
done by the Incubator PMC chair or an Incubator PMC Member wih karma
for the authorizations file)

4. Tell Mentors to track progress in the file
'incubator/projects/{project.name}.html'

For 1, we came with a transferred trademark, from Oracle.  I think
that can be considered an alternative way of demonstrating uniqueness,
since that was required in the first instance to acquire the
registered trademark,  So maybe we just put down the date of the
transfer?

For 2, that is obviously done.  I assume it was done within hours of
the podling being created.

Ditto for 3.

For 4, this sounds incorrect.  It has been podling members, not
mentors, who have been maintaining the status file.  But for
completeness can we assume that the mentors were implicitly told to do
this when the IPMC approved the podling initially?

So is there anything on that list that you think needs Mentor
attention?  Anything else in the status file?

-Rob

 Thanks  Regards,
 Dave

 [1] http://incubator.apache.org/projects/openofficeorg.html


 Ross
 On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:

 Please vote in the main [VOTE] thread, and have discussion in this thread.

 Thanks!

 -Rob

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote


On Aug 19, 2012, at 3:58 PM, Rob Weir wrote:

 On Sun, Aug 19, 2012 at 4:43 PM, Ross Gardler
 rgard...@opendirective.com wrote:
 I'm unable to vote either way until:
 
 A) a PMC chair has been identified by the community
 
 B) a resolution for the TLP is prepared which will define what we are
 voting on
 
 
 Those points will be addressed in the proposed Resolution we send to
 the IPMC.  What we're having right now is the preliminary community
 graduation vote, which according this diagram from the IPMC's Guide
 to Successful Graduation occurs *before* the charter is created:
 
 http://incubator.apache.org/guides/graduation.html#toplevel
 
 Not that this same guide says of this community vote, It is unlikely
 that IPMC members will vote to approve graduation unless the Mentors
 and community positively express their readiness for graduation.   So
 I am slightly concerned that you do not feel able to vote in this
 ballot, which merely expresses (per the graduation guidelines) our
 readiness for graduation.

Community Graduation Vote

A community needs to be willing to govern itself before it can become a top 
level project. A good way to demonstrate this is through a free VOTE (by the 
community) on the graduation proposal.

This VOTE is not a requirement but is recommended. It is unlikely that IPMC 
members will vote to approve graduation unless the Mentors and community 
positively express their readiness for graduation. It is wise to copy the 
incubator general list when the vote is proposed.

I think that the graduation proposal is often understood to be the Charter 
and therefore (1) and (2) are swapped in current, undocumented process, but I 
could be wrong.

Regards,
Dave




 
 -Rob
 
 Note, I'm generally in favour of the proposal but I do want to be sure that
 the community has the resources it needs to continue to build and maintain
 a healthy,vibrant and inclusive community. There are some candidates for
 PMC chair that I can think of, but I don't know if they want the role.
 
 In a healthy community the PMC role is just taking responsibility for board
 reports (not necessarily writing them, just making sure they get written)
 and any community actions requested by the board. It shouldn't be a time
 consuming role, but it can become so on occasion.
 
 This query should not prevent the community expressing their opinion in the
 vote. I just wanted to let you know why I will be abstaining. You only need
 my vote when it comes to the actual graduation vote.
 
 Ross
 On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:
 
 Please vote in the main [VOTE] thread, and have discussion in this thread.
 
 Thanks!
 
 -Rob

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote


On Aug 19, 2012, at 4:09 PM, Rob Weir wrote:

 On Sun, Aug 19, 2012 at 5:07 PM, Dave Fisher dave2w...@comcast.net wrote:
 
 On Aug 19, 2012, at 1:43 PM, Ross Gardler wrote:
 
 I'm unable to vote either way until:
 
 A) a PMC chair has been identified by the community
 
 B) a resolution for the TLP is prepared which will define what we are
 voting on
 
 Note, I'm generally in favour of the proposal but I do want to be sure that
 the community has the resources it needs to continue to build and maintain
 a healthy,vibrant and inclusive community. There are some candidates for
 PMC chair that I can think of, but I don't know if they want the role.
 
 In a healthy community the PMC role is just taking responsibility for board
 reports (not necessarily writing them, just making sure they get written)
 and any community actions requested by the board. It shouldn't be a time
 consuming role, but it can become so on occasion.
 
 This query should not prevent the community expressing their opinion in the
 vote. I just wanted to let you know why I will be abstaining. You only need
 my vote when it comes to the actual graduation vote.
 
 I understand.
 
 BTW - There are some Mentor related status items on [1] that need action. 
 Would you be able to take care of those items?
 
 
 So the items I see as not marked as done are:
 
 1. Make sure that the requested project name does not already exist
 and check www.nameprotect.com to be sure that the name is not already
 trademarked for an existing software product.
 
 2. Subscribe all Mentors on the pmc and general lists.
 
 3. Give all Mentors access to the incubator SVN repository. (to be
 done by the Incubator PMC chair or an Incubator PMC Member wih karma
 for the authorizations file)
 
 4. Tell Mentors to track progress in the file
 'incubator/projects/{project.name}.html'
 
 For 1, we came with a transferred trademark, from Oracle.  I think
 that can be considered an alternative way of demonstrating uniqueness,
 since that was required in the first instance to acquire the
 registered trademark,  So maybe we just put down the date of the
 transfer?
 
 For 2, that is obviously done.  I assume it was done within hours of
 the podling being created.
 
 Ditto for 3.
 
 For 4, this sounds incorrect.  It has been podling members, not
 mentors, who have been maintaining the status file.  But for
 completeness can we assume that the mentors were implicitly told to do
 this when the IPMC approved the podling initially?

I agree with your interpretation on all points.

 
 So is there anything on that list that you think needs Mentor
 attention?  Anything else in the status file?

Not that I know of.

Regards,
Dave

 
 -Rob
 
 Thanks  Regards,
 Dave
 
 [1] http://incubator.apache.org/projects/openofficeorg.html
 
 
 Ross
 On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:
 
 Please vote in the main [VOTE] thread, and have discussion in this thread.
 
 Thanks!
 
 -Rob

Re: What to say in AOO 3.4.1 release announcement about the ports? (BSD, Solaris, OS/2)?

So it looks like we're ending up with two related pages, both now in staging:

This page describes the porting work in the project, including
work-in-progress as well as work that has already lead to a release:

http://ooo-site.staging.apache.org/porting/index.html

And this page lists only ports that are actually available for download:

http://ooo-site.staging.apache.org/download/non_ASF.html

So in terms of the release announcement, I assume we mention the first
page, the one for the ports-in-progress, since we are not releasing
concurrently with any other ports.  Does that sound right?  The
mention of ports in the announcement is a statement about the breadth
of the ecosystem.  It is not a statement about immediately
availability of downloads.

Regards,

-Rob

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

On Sun, Aug 19, 2012 at 7:11 PM, Dave Fisher dave2w...@comcast.net wrote:

 On Aug 19, 2012, at 3:58 PM, Rob Weir wrote:

 On Sun, Aug 19, 2012 at 4:43 PM, Ross Gardler
 rgard...@opendirective.com wrote:
 I'm unable to vote either way until:

 A) a PMC chair has been identified by the community

 B) a resolution for the TLP is prepared which will define what we are
 voting on


 Those points will be addressed in the proposed Resolution we send to
 the IPMC.  What we're having right now is the preliminary community
 graduation vote, which according this diagram from the IPMC's Guide
 to Successful Graduation occurs *before* the charter is created:

 http://incubator.apache.org/guides/graduation.html#toplevel

 Not that this same guide says of this community vote, It is unlikely
 that IPMC members will vote to approve graduation unless the Mentors
 and community positively express their readiness for graduation.   So
 I am slightly concerned that you do not feel able to vote in this
 ballot, which merely expresses (per the graduation guidelines) our
 readiness for graduation.

 Community Graduation Vote

 A community needs to be willing to govern itself before it can become a top 
 level project. A good way to demonstrate this is through a free VOTE (by the 
 community) on the graduation proposal.

 This VOTE is not a requirement but is recommended. It is unlikely that IPMC 
 members will vote to approve graduation unless the Mentors and community 
 positively express their readiness for graduation. It is wise to copy the 
 incubator general list when the vote is proposed.

 I think that the graduation proposal is often understood to be the Charter 
 and therefore (1) and (2) are swapped in current, undocumented process, but I 
 could be wrong.


Look at the diagram:
http://incubator.apache.org/guides/graduation.html#toplevel

Do you see any way to read it consistent with your interpretation?

-Rob

 Regards,
 Dave





 -Rob

 Note, I'm generally in favour of the proposal but I do want to be sure that
 the community has the resources it needs to continue to build and maintain
 a healthy,vibrant and inclusive community. There are some candidates for
 PMC chair that I can think of, but I don't know if they want the role.

 In a healthy community the PMC role is just taking responsibility for board
 reports (not necessarily writing them, just making sure they get written)
 and any community actions requested by the board. It shouldn't be a time
 consuming role, but it can become so on occasion.

 This query should not prevent the community expressing their opinion in the
 vote. I just wanted to let you know why I will be abstaining. You only need
 my vote when it comes to the actual graduation vote.

 Ross
 On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:

 Please vote in the main [VOTE] thread, and have discussion in this thread.

 Thanks!

 -Rob

Re: [VOTE][DISCUSS] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Ross Gardler

I only wanted to indicate why I was abstaining. This need not be a concern.
I could have made no comment but that might have been interpreted as an
absent mentor by some.

I'm happy to explain my reasons further if anything is not clear, but
without understanding what part you don't understand its hard to expand on
my points. Instead I'll just try and reassure you.

The timeline graphic you point to is new to me. It looks really useful.
You'll note that I said I will abstain until I see the resolution
(including the PMC chair). You'll also note I said my abstention should not
affect the community vote. I believe my position is consistent with the
chart, which shows the community vote prior to the charter andthe IPMC (of
which I am a member) vote after the charter.

Ross
On Aug 19, 2012 11:59 PM, Rob Weir robw...@apache.org wrote:

 On Sun, Aug 19, 2012 at 4:43 PM, Ross Gardler
 rgard...@opendirective.com wrote:
  I'm unable to vote either way until:
 
  A) a PMC chair has been identified by the community
 
  B) a resolution for the TLP is prepared which will define what we are
  voting on
 

 Those points will be addressed in the proposed Resolution we send to
 the IPMC.  What we're having right now is the preliminary community
 graduation vote, which according this diagram from the IPMC's Guide
 to Successful Graduation occurs *before* the charter is created:

 http://incubator.apache.org/guides/graduation.html#toplevel

 Not that this same guide says of this community vote, It is unlikely
 that IPMC members will vote to approve graduation unless the Mentors
 and community positively express their readiness for graduation.   So
 I am slightly concerned that you do not feel able to vote in this
 ballot, which merely expresses (per the graduation guidelines) our
 readiness for graduation.

 -Rob

  Note, I'm generally in favour of the proposal but I do want to be sure
 that
  the community has the resources it needs to continue to build and
 maintain
  a healthy,vibrant and inclusive community. There are some candidates for
  PMC chair that I can think of, but I don't know if they want the role.
 
  In a healthy community the PMC role is just taking responsibility for
 board
  reports (not necessarily writing them, just making sure they get written)
  and any community actions requested by the board. It shouldn't be a time
  consuming role, but it can become so on occasion.
 
  This query should not prevent the community expressing their opinion in
 the
  vote. I just wanted to let you know why I will be abstaining. You only
 need
  my vote when it comes to the actual graduation vote.
 
  Ross
   On Aug 19, 2012 4:53 PM, Rob Weir robw...@apache.org wrote:
 
  Please vote in the main [VOTE] thread, and have discussion in this
 thread.
 
  Thanks!
 
  -Rob

Re: What to say in AOO 3.4.1 release announcement about the ports? (BSD, Solaris, OS/2)?

On Sun, Aug 19, 2012 at 4:17 PM, Rob Weir robw...@apache.org wrote:

 So it looks like we're ending up with two related pages, both now in
 staging:

 This page describes the porting work in the project, including
 work-in-progress as well as work that has already lead to a release:

 http://ooo-site.staging.apache.org/porting/index.html

 And this page lists only ports that are actually available for download:

 http://ooo-site.staging.apache.org/download/non_ASF.html

 So in terms of the release announcement, I assume we mention the first
 page, the one for the ports-in-progress, since we are not releasing
 concurrently with any other ports.  Does that sound right?  The
 mention of ports in the announcement is a statement about the breadth
 of the ecosystem.  It is not a statement about immediately
 availability of downloads.

 Regards,

 -Rob



Actually, they're both in production now.

h...I didn't realize that the winPenPack port is also listed on the
first page, the porting page. I don't remember seeing this earlier today.
Do we really want to do this? Is this really a port or a distribution?
I think the latter.

-- 

MzK

Never express yourself more clearly than you are able to think.
--
Niels Bohr

Re: [VOTE] Apache OpenOffice Community Graduation Vote

On Sun, Aug 19, 2012 at 11:52 AM, Rob Weir robw...@apache.org wrote:
 Per the IPMC's Guide to Successful Graduation [1] this is the
 optional, but recommended, community vote for us to express our
 willingness/readiness to govern ourselves.  If this vote passes then
 we continue by drafting a charter, submitting it for IPMC endorsement,
 and then to the ASF Board for final approval.   Details can be found
 in the Guide to Successful Graduation.

 Everyone in the community is encouraged to vote.  Votes from PPMC
 members and Mentors are binding.  This vote will run 72-hours.


 [ ] +1  Apache OpenOffice community is ready to graduate from the
 Apache Incubator.
 [ ] +0 Don't care.
 [ ] -1  Apache OpenOffice community is not ready to graduate from the
 Apache Incubator because...


+1 from me.

-Rob



 Regards,

 -Rob

 [1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-19 Thread Peter Junge


On 8/19/2012 11:52 PM, Rob Weir wrote:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Although I have been mostly limiting my participation to reading and 
moderating, I'm convinced that AOO is ready to move ahead.


+1  from my side.

Peter

Re: [UX] DISCUSS - Survey Tool Recommendation

2012-08-19 Thread Kevin Grignon

KG01 - see comments inline

On Aug 18, 2012, at 9:34 AM, Graham Lauder y...@apache.org wrote:

 On 16/08/2012 Rob Weir wrote:
 On Thu, Aug 16, 2012 at 12:47 AM, Kevin Grignon wrote:
 I've been looking at various survey tools and would like to recommend
 that we deploy the open source survey tool, *LimeSurvey.*
 
 Perfect. It is a good tool and it is in continuity with what the project
 used to use, see my old e-mail at
 http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201206.mbox/%3
 C4 feecc9a.3020...@apache.org%3E

KG01 - Great news. Most gracious. 

 
 1) A volunteer hosts the survey outside of Apache at their existing
 domain name
 
 2) A volunteer hosts the survey outside of Apache and some pays $15 or
 so to get a better domain name for it, like www.oosurvey.net
 
 3) A volunteer hosts the survey outside of Apache but we redirect the
 subdomain survey.openoffice.org to point to the external server
 
 As I wrote in the same e-mail, Graham had written he had a working
 LimeSurvey installation that he could make available to the project:
 http://s.apache.org/wZ . So I'd try with that first, and I'd probably
 prefer option 3 to keep all services under one namespace.

KG01 - yes, a natural language oriented name such as survey.openoffice.org 
would be great. 

 
 Regards,
 
   Andrea.
 
 Just having long loud discussions with the host at the moment because the
 site is broken, looks like an update has gone bad.  As soon as it's sorted
 we can be in to it.
 
 We should probably still do the survey design on the wiki however.

KG01 - Indeed, I have been capturing the survey questions on the wiki. I will 
also start to build the survey groups (question collections) in LimeSurvey to 
be ready to import into our hosted instance, when available.

 
 Cheers
 G
 
 Good grief, server meltdown and they're talking about 72 hours before it's up 
 again. 

KG01 - No worries, as long as we can get cracking by the end of the week. 

KG01 - Please share server details and user credentials when available.

Re: [DISCUSS] AOO Ready to Graduate

2012-08-19 Thread Zhe Liu

+1.  Let's move forward.

2012/8/17 Rob Weir robw...@apache.org:
 We've had several prods from our mentors suggesting that we are ready
 to graduate.  But I think there was general recognition that with
 graduation comes a little hump in extra work, both for the project as
 well as the IPMC and Infra, especially related to mailing list and
 website changes [1].  We wanted to avoid piling that on top of the
 already considerable work required to get AOO 3.4.1 released.

 The AOO 3.4.1 release is now being voted on.  So I think it is a good
 time for us to start this process.

 I'd recommend everyone take a look at this timeline [2] for what the
 graduation process looks like.  You can see it is three steps:

 1) Optional Community vote [3]

 2) Preparation of a Charter and Resolution [4]

 3) Vote by the IPMC to recommend the Charter/Resolution to the ASF Board.

 4) Approval by the ASF Board.

 As I understand it the ASF Board meeting on the 3rd Wednesday of each
 month.  So the next meeting should be September 19th.  If we start
 now, we should have plenty of time to work through this process in
 time for that meeting.

 I'd like to start the first step, with the optional, but highly
 recommended, community vote, stating our belief that we are ready to
 graduate.

 Regards,

 -Rob


 [1]  http://incubator.apache.org/guides/graduation.html#project-first-steps

 [2] http://incubator.apache.org/guides/graduation.html#process

 [3] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

 [4] http://incubator.apache.org/guides/graduation.html#tlp-resolution



-- 
Best Regards
From aliu...@gmail.com

Re: CMS diff: Why OpenOffice.org: Public administrations

Rob,
  That's my translations to the existing website materials. So it is no
problem to wait to publish together with our announcement.

- Shenfeng


2012/8/19 Rob Weir robw...@apache.org

 Let's be careful.  Don't we already have some announcement changes on
 staging?  If so we can bring this change as well onto staging, but we
 should avoid publishing, since that is all-or-nothing, and we don't
 want to put the announcement changes out yet.

 -Rob

 On Sun, Aug 19, 2012 at 11:28 AM, Shenfeng Liu anonym...@apache.org
 wrote:
  Clone URL (Committers only):
 
 https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/zh-cn%2Fwhy%2Fwhy_gov.mdtext
 
  Shenfeng Liu
 
  Index: trunk/content/zh-cn/why/why_gov.mdtext
  ===
  --- trunk/content/zh-cn/why/why_gov.mdtext  (revision 1374681)
  +++ trunk/content/zh-cn/why/why_gov.mdtext  (working copy)
  @@ -1,4 +1,4 @@
  -Title: Why OpenOffice.org: Public administrations
  +Title: 为何选择Apache OpenOffice：公共管理
   Notice:Licensed to the Apache Software Foundation (ASF) under one
  or more contributor license agreements.  See the NOTICE file
  distributed with this work for additional information
  @@ -16,20 +16,20 @@
  specific language governing permissions and limitations
  under the License.
 
  -![Why Apache OpenOffice: Public
 administrations](/why/images/why_gov.png) # {.rfloatimg}
  +![为何选择Apache OpenOffice：公共管理](/why/images/why_gov.png) # {.rfloatimg}
 
  -Public administrations and people working at **all levels of
 government** (local / federal / regional / national etc) find Apache
 OpenOffice is their ideal software solution. The combination of a
 **flexible word processor**, a **powerful spreadsheet**, **dynamic
 graphics**, **database access** and more meets all the everyday needs of a
 typical busy office worker.
  +公共管理单位以及为**各级政府机关**工作的人（无论是地方的还是中央的，区域性的还是全国性的）都会发现Apache
 OpenOffice是他们理想的软件解决方案。它的组合中包含一个**灵活的文本编辑器**，一个**强大的电子表格**，**灵活的绘图**，**数据库访问**等等，可以满足一个忙碌的办公室工作人员的所有日常办公需求。
 
  -Already available in a **wide range of languages**, OpenOffice can be
 freely translated by local teams.
  +OpenOffice可以被本地团队自由地翻译，所以拥有**许多不同的语言包**。
 
  -  - **Best value**
  +  - **价值最大化**
 
  -Using Apache OpenOffice demonstrates your commitment to deliver
 best value services. It is not owned by any commercial organisation. Its
 open source licence means there are no licence fees to pay, no expensive
 annual audits, and no worries about non-compliance with onerous and obscure
 licencing conditions. You may also distribute the software free to your
 employees, through the schools system, or any other channel of your choice.
  +使用Apache
 OpenOffice可以帮助你实现服务价值最大化的承诺。它不被任何商业组织所拥有。它的开源许可协议意味着没有许可证费，没有昂贵的年审，并且不用担心违反那些繁琐而又模糊不清的许可协议条款。你还可以通过教育系统或任何你选择的途径将这个软件免费分发到你的员工手里。
 
  -  - **Data is safe**
  +  - **数据安全保证**
 
  -Freedom of Information Acts require that the documents you create
 today will be accessible years in the future. Apache OpenOffice is the
 first software in the world to use ISO approved file formats as its
 default. It also has the ability to create PDF files if you need to publish
 information in a standard 'read only' format. If you already have (possibly
 unlicenced) office software, Apache OpenOffice should be able to read your
 old files.
  +信息自由法案要求你今天所创建的文档在未来几年内都可以被访问。Apache
 OpenOffice是世界上第一款使用ISO批准的标准文件格式作为缺省格式的软件。如果你需要通过标准的“只读”格式发布信息，它同样可以创建PDF文件来满足你的要求。如果你已经有了办公软件（也许不是正版的？），Apache
 OpenOffice可以读取你的那些旧文件。
 
  -  - ** Open for all**
  +  - **对所有人开放**
 
  -There are no secrets in Apache OpenOffice - our open-source policy
 means anyone can inspect the code or even help us develop the software. We
 actively encourage local teams to produce versions for minority languages.
 OpenOffice is a leading international force in the movement for digital
 inclusion - making software of the highest quality available to all,
 regardless of income.
  +在Apache
 OpenOffice中没有秘密――我们的开源政策意味着任何人都可以查看源代码或者甚至帮助我们开发这个软件。我们积极鼓励本地团队制作少数民族语言的版本。OpenOffice在数字化领域是一个国际化的领导力量――它汇集来源于各方的贡献集，为所有人制作最高质量的软件。

Re: CMS diff: Why OpenOffice.org: Public administrations

On Sun, Aug 19, 2012 at 9:58 PM, Shenfeng Liu liush...@gmail.com wrote:
 Rob,
   That's my translations to the existing website materials. So it is no
 problem to wait to publish together with our announcement.


When using the CMS a publish operation is all or nothing.  So if we
publish your changes then we also need to publish any other changes
that are pending on the staging server.  Since we are preparing to
announce the 3.4.1 release we are starting to load
announcement-related changes onto the staging server.  But we're not
ready to publish them yet.

So my note was just to remind other committers that it is OK to commit
your changes and get them onto the staging server, but to wait for
publishing them.

-Rob

 - Shenfeng


 2012/8/19 Rob Weir robw...@apache.org

 Let's be careful.  Don't we already have some announcement changes on
 staging?  If so we can bring this change as well onto staging, but we
 should avoid publishing, since that is all-or-nothing, and we don't
 want to put the announcement changes out yet.

 -Rob

 On Sun, Aug 19, 2012 at 11:28 AM, Shenfeng Liu anonym...@apache.org
 wrote:
  Clone URL (Committers only):
 
 https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://ooo-site.apache.org/zh-cn%2Fwhy%2Fwhy_gov.mdtext
 
  Shenfeng Liu
 
  Index: trunk/content/zh-cn/why/why_gov.mdtext
  ===
  --- trunk/content/zh-cn/why/why_gov.mdtext  (revision 1374681)
  +++ trunk/content/zh-cn/why/why_gov.mdtext  (working copy)
  @@ -1,4 +1,4 @@
  -Title: Why OpenOffice.org: Public administrations
  +Title: 为何选择Apache OpenOffice：公共管理
   Notice:Licensed to the Apache Software Foundation (ASF) under one
  or more contributor license agreements.  See the NOTICE file
  distributed with this work for additional information
  @@ -16,20 +16,20 @@
  specific language governing permissions and limitations
  under the License.
 
  -![Why Apache OpenOffice: Public
 administrations](/why/images/why_gov.png) # {.rfloatimg}
  +![为何选择Apache OpenOffice：公共管理](/why/images/why_gov.png) # {.rfloatimg}
 
  -Public administrations and people working at **all levels of
 government** (local / federal / regional / national etc) find Apache
 OpenOffice is their ideal software solution. The combination of a
 **flexible word processor**, a **powerful spreadsheet**, **dynamic
 graphics**, **database access** and more meets all the everyday needs of a
 typical busy office worker.
  +公共管理单位以及为**各级政府机关**工作的人（无论是地方的还是中央的，区域性的还是全国性的）都会发现Apache
 OpenOffice是他们理想的软件解决方案。它的组合中包含一个**灵活的文本编辑器**，一个**强大的电子表格**，**灵活的绘图**，**数据库访问**等等，可以满足一个忙碌的办公室工作人员的所有日常办公需求。
 
  -Already available in a **wide range of languages**, OpenOffice can be
 freely translated by local teams.
  +OpenOffice可以被本地团队自由地翻译，所以拥有**许多不同的语言包**。
 
  -  - **Best value**
  +  - **价值最大化**
 
  -Using Apache OpenOffice demonstrates your commitment to deliver
 best value services. It is not owned by any commercial organisation. Its
 open source licence means there are no licence fees to pay, no expensive
 annual audits, and no worries about non-compliance with onerous and obscure
 licencing conditions. You may also distribute the software free to your
 employees, through the schools system, or any other channel of your choice.
  +使用Apache
 OpenOffice可以帮助你实现服务价值最大化的承诺。它不被任何商业组织所拥有。它的开源许可协议意味着没有许可证费，没有昂贵的年审，并且不用担心违反那些繁琐而又模糊不清的许可协议条款。你还可以通过教育系统或任何你选择的途径将这个软件免费分发到你的员工手里。
 
  -  - **Data is safe**
  +  - **数据安全保证**
 
  -Freedom of Information Acts require that the documents you create
 today will be accessible years in the future. Apache OpenOffice is the
 first software in the world to use ISO approved file formats as its
 default. It also has the ability to create PDF files if you need to publish
 information in a standard 'read only' format. If you already have (possibly
 unlicenced) office software, Apache OpenOffice should be able to read your
 old files.
  +信息自由法案要求你今天所创建的文档在未来几年内都可以被访问。Apache
 OpenOffice是世界上第一款使用ISO批准的标准文件格式作为缺省格式的软件。如果你需要通过标准的“只读”格式发布信息，它同样可以创建PDF文件来满足你的要求。如果你已经有了办公软件（也许不是正版的？），Apache
 OpenOffice可以读取你的那些旧文件。
 
  -  - ** Open for all**
  +  - **对所有人开放**
 
  -There are no secrets in Apache OpenOffice - our open-source policy
 means anyone can inspect the code or even help us develop the software. We
 actively encourage local teams to produce versions for minority languages.
 OpenOffice is a leading international force in the movement for digital
 inclusion - making software of the highest quality available to all,
 regardless of income.
  +在Apache
 OpenOffice中没有秘密——我们的开源政策意味着任何人都可以查看源代码或者甚至帮助我们开发这个软件。我们积极鼓励本地团队制作少数民族语言的版本。OpenOffice在数字化领域是一个国际化的领导力量——它汇集来源于各方的贡献集，为所有人制作最高质量的软件。

Re: [QA] TestLink Usage Guide

2012-08-19 Thread Li Feng Wang

Thank you Andrea Pescetti 's remarks.

Pls see my reply below every remark.
2012/8/18 Andrea Pescetti pesce...@apache.org

 Li Feng Wang wrote:

I wrote a Wiki about TestLink Usage Guide,
 http://wiki.openoffice.org/**wiki/QA/TestLinkhttp://wiki.openoffice.org/wiki/QA/TestLink
Hope to help you use TestLink.


 Thanks, very good information. A couple of remarks:

 1) Can testcases be translated? Of course one can create a scenario where,
 say, all tests are translated into Italian; but maintaining and updating
 translations will be much easier if TestLink supports translations out of
 the box.


From I know that TestLink not support translate.


 2) Can we establish a policy to use the Export function to archive
 testcases in the OpenOffice SVN repository at regular intervals? This will
 clarify any intellectual property issues and it will avoid disasters
 similar to what happened with TCM, where we had hundreds of testcases
 (translated into multiple languages) that were lost when Oracle turned off
 TCM (or the server hosting it, or the DNS record for it).


The second is Testlink backup. Testlink provide method to backup testlink
database and attachments.
Backup exported xml on SVN is a good idea. But as I know, the attachment in
testcase can't export with xml.



 Regards,
   Andrea.




-- 
Best Wishes, LiFeng Wang

Re: Request to Create a Branch for the Implement the Loading of TOC and Improve TOC Fidelity with MS Word Binary Document

2012-08-19 Thread chengjh

Hi Oliver,

As I know,the first stage's code changes of implementing the TOC Load and
improving TOC fidelity with MS Word binary have been reviewed  by
you..Could you please apply the patch to the branch
https://svn.apache.org/repos/asf/incubator/ooo/branches/writer001/?, and
then we will ask Simon to help the branch build for us.Thanks.

On Mon, Jul 2, 2012 at 1:24 PM, chengjh chen...@apache.org wrote:

 Branch https://svn.apache.org/repos/asf/incubator/ooo/branches/writer001/
 has been created for the TOC Enhancement.Let's exchange code changes in
 this branch for the followed improvements and bugfixes of TOC. Thanks.


 On Mon, Jul 2, 2012 at 9:06 AM, chengjh chen...@apache.org wrote:

 Oliver, Very good suggestion.That's also one of my goals.Let's take it as
 a pilot to practise the way of branch development in community. After the
 TOC improvement done,the actual usage of this branch will pop up to focus
 on the Study and POC of Writer's Track Changes..Thanks.


 On Fri, Jun 29, 2012 at 5:57 PM, Oliver-Rainer Wittmann 
 orwittm...@googlemail.com wrote:

 Hi,


 On 29.06.2012 10:37, chengjh wrote:

 Thanks to Juergen and Oliver's comments..I got points as followed:
 a)If the code changes of an improvement are too many,effort is also big
 and
 development has to be went on for long,moreover,special testing work
 will
 be taken to cover the given function areas and impacted areas, that's
 ok to
 create a branch for the improvement..It is better to do so.
 b)If the risk and impact areas are under control,and we are confident to
 ensure the quality along with that the finished scenarios are clear and
 expected, it is better for us to deliver the code changes to main
 stream( trunk )
 directly even the deliverable is not complete.Thus QE volunteers can
 help
 us to find out regression defects as early as possible,and also,better
 feedback can be got in time.

 So,the selection can be decided according to the actual project's
 situation
 and evaluation.To the TOC Loading,we are able to deliver the code
 changes
 to main and finish the development work stage by stage in main
 directly..Any misunderstanding,please correct me.


 Yes.
 The team that is working on a feature can decide what is better -
 working on trunk or working on a branch.

 May be we can use the TOC enhancements as an opportunity to figure out
 a good and accepted way to work on branches.
 Thus, I am fine with both ways for the TOC enhancements.

 Best regards, Oliver.

 P.S.: I have just finished my review on the recent patch for issue 119963

  On Fri, Jun 29, 2012 at 3:49 PM, Oliver-Rainer Wittmann 
 orwittm...@googlemail.com wrote:

  Hi,


 On 29.06.2012 03:59, chengjh wrote:

  Hi,

 We have proposed to implement the loading of TOC and improve TOC
 fidelity
 with MS Word binary document..And now,we have finished the loading
 implementation part and delivered patch for review in
 https://issues.apache.org/ooo/show_bug.cgi?id=119963https://issues.apache.org/ooo/**show_bug.cgi?id=119963
 https**://issues.apache.org/ooo/show_**bug.cgi?id=119963https://issues.apache.org/ooo/show_bug.cgi?id=119963
 .

 Because this is just
 the stage I code implementation, and more improvements within stage
 II/III/
 code implementation will be followed,moreover,special qe efforts are
 needed
 to cover the whole TOC function area and the impact areas,in order to
 decrease the negative impacts on the main stream,we request to create
 a
 branch and deliver our code implementation to the branch first, and
 then
 integrate the final qualified code to main..How about your
 comments?Thanks.

 Reference:
 [1]Candidate Proposal:
 https://cwiki.apache.org/confluence/display/OOOUSERS/**https://cwiki.apache.org/**confluence/display/OOOUSERS/**
 AOO+4.0+Feature+Planninghttps**://cwiki.apache.org/**
 confluence/display/OOOUSERS/**AOO+4.0+Feature+Planninghttps://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Feature+Planning
 
 [2]Wiki with FS and SDD:  http://wiki.services.openoff**
 ice.org/wiki/Writer/ 
 http://openoffice.org/wiki/**Writer/http://openoffice.org/wiki/Writer/
 
 TOC 
 http://wiki.services.**openof**fice.org/wiki/Writer/TOChttp://openoffice.org/wiki/Writer/TOC
 http:**//wiki.services.openoffice.**org/wiki/Writer/TOChttp://wiki.services.openoffice.org/wiki/Writer/TOC
 
 **


  In general I think it makes completely sense to work on a branch for
 a
 certain feature which takes more implementation, testing etc. efforts.

 In this special case I am not sure, if it is needed.
 I am currently reviewing the patch for issue 119963. It works fine
 from my
 point of view. There are no open ends, it is complete and does not
 cause
 any problems as far as I can see. Thus, I am planning to apply this
 patch
 to trunk today or on Monday.
 Thus, from my point of view this feature milestone and the following
 ones
 are still small enough to handle them without an additional branch.


 Best regards, Oliver.








 --

 Best Regards,Jianhong Cheng

Re: [VOTE][preliminary RESULT] Release Apache OpenOffice 3.4.1 (incubating), RC2