Re: [VOTE] Accept Sqoop for Incubation
+1 (binding), Agreeing with Chris, looks awesome ! On Wed, Jun 8, 2011 at 5:39 AM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 (binding) Ralph On Jun 7, 2011, at 9:38 PM, Jonathan Hsieh wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to Cloudera
Introducing orcmid
Hi, My name is Dennis Hamilton. I am a semi-retired software system architect living in Seattle, Washington. My profile of profiles is already up at http://wiki.apache.org/incubator/orcmid. The orcmid handle goes back to DecWars on a PDP-10 and the early CompuServe CB chat rooms. My connection and interest in Apache OpenOffice.org is from my commitment to interoperable solutions in the management and processing of documents. A member of the OASIS OpenDocument Format TC, I was drawn to OASIS by the formation of the ODF Interoperability and Conformance (OIC) TC in late Summer 2008. Once in OASIS, it was a natural step to also join the ODF TC itself. I had submitted public comments before that, and I was around when David Wheeler kicked-off OpenFormula, originally on SourceForge. From a career perspective, I wrote my first line of code in the Spring of 1958 when I was an engineering aide at Boeing Company. The program (in Fortran, there not being any reason to call it Fortran I yet) crashed on being given the first test value. I graduated from Fortran to assembly language, and the last I wrote of that was for 8080/Z80 running CP/M-80. My career moved through Remington Rand Univac and Xerox Corporation, with occasional time-outs as an independent consultant. I don't write code that much anymore, although I am fascinated with coming up with C/C++ examples and tips for newcomers who struggle with tools like the Microsoft Visual C++ Express Editions. My hands-on work with OpenOffice, LibreOffice, and other instances of support for ODF is mainly in document forensics and QA work, in addition to continued participation in the development of the ODF standards. I'm allergic to GPL'd code, but not to permissive licenses, so I can see myself patching this 'n' that on Apache projects. I have an itch about development work for an ODF reference implementation with customizable/reusable components, as some of my comments on this list have already revealed. I think that will be very important for the long-term health of ODF-native software and the promise of interoperability (and substitutability) that users have been promised and that is not yet fulfilled. - Dennis - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 On Wed, Jun 8, 2011 at 10:08 AM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to Cloudera
Re: [VOTE] Flume to join the Incubator.
Here is my +1 (non binding) -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer *
Re: [VOTE] Accept Sqoop for Incubation
+1 (non binding) -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer *
Re: [VOTE] Accept Sqoop for Incubation
+1 -Nigel On Jun 7, 2011, at 8:39 PM, arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: Add incubator group to podling committers
Christian Grobmeier wrote on Tue, Jun 07, 2011 at 09:24:45 +0200:
Hello,
I sent this to infra, but I have been told the incubator chair should
handle this.
Can the people below be added to the incubator group so they can
update the ONGL website? I have hear our inc-chair is ooo (wow, that
acronym got somehow hijiacked in this list) - do we have a deputy
handling it?
Thirty-six other people on the Incubator PMC have sufficient karma:
[[[
% cat ./count-ipmc-chairs.zsh
#!/usr/bin/env zsh
f() {
ldapsearch -LLL cn=$1 member | grep ^member: | sort
}
comm -12 =(f incubator) =(f pmc-chairs) | wc -l
% ./count-ipmcchairs.zsh
37
]]]
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
+1 (binding) LieGrue, strub --- On Wed, 6/8/11, Julien Vermillard jvermill...@gmail.com wrote: From: Julien Vermillard jvermill...@gmail.com Subject: Re: [VOTE] Accept Sqoop for Incubation To: general@incubator.apache.org Date: Wednesday, June 8, 2011, 5:59 AM +1 (binding), Agreeing with Chris, looks awesome ! On Wed, Jun 8, 2011 at 5:39 AM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: Add incubator group to podling committers
Can the people below be added to the incubator group so they can
update the ONGL website? I have hear our inc-chair is ooo (wow, that
acronym got somehow hijiacked in this list) - do we have a deputy
handling it?
Thirty-six other people on the Incubator PMC have sufficient karma:
Thanks. But could you briefly explain how this knowledge can help me?
I mean, I am willing to do it myself, if I just know if I can or how.
[[[
% cat ./count-ipmc-chairs.zsh
#!/usr/bin/env zsh
f() {
ldapsearch -LLL cn=$1 member | grep ^member: | sort
}
comm -12 =(f incubator) =(f pmc-chairs) | wc -l
% ./count-ipmcchairs.zsh
37
]]]
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
http://www.grobmeier.de
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 (binding) Tommaso 2011/6/8 Jonathan Hsieh j...@cloudera.com Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to Cloudera provided feedback,
Re: [VOTE] Accept Sqoop for Incubation
+1 (binding) Tommaso 2011/6/8 arv...@cloudera.com arv...@cloudera.com As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
+1 (non-binding) On Wed, Jun 8, 2011 at 3:51 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: +1 (binding) Tommaso 2011/6/8 arv...@cloudera.com arv...@cloudera.com As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Upstream/Downstream (was OpenOffice LibreOffice)
On Wed, Jun 8, 2011 at 6:51 AM, Norbert Thiebaud nthieb...@gmail.com wrote: On Tue, Jun 7, 2011 at 9:43 PM, Noel J. Bergman n...@devtech.com wrote: [...] their downstream code cannot be used. Hence, the best outcome under the current licensing regime is for all core development to be done here, and for TDF to be a downstream consumer. Just because you choose a particular license that does not make you de-facto 'upstream'. Noel is describing a fact: It there is going to be something like upstream, it can only be an ASL licensed OO, not a LGPL'ed LO. What he misses (as quite a few others do, which is possibly why you are reacting angry) is a certain amount of sensibility that acknowledges that this fact is just as likely to cause a total split between LO and OO. Your reaction only goes to show that this sensibility is required: Such a split would be the worst thing to happen and it is something where LO would loose nothing (compared to the time before the proposal) but would have missed a chance to win. Jochen -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 and welcome on board. cheers, Leo On Wed, Jun 8, 2011 at 5:38 AM, Jonathan Hsieh j...@cloudera.com wrote: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation ... = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
+1! cheers, Leo On Wed, Jun 8, 2011 at 4:39 AM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation Pasting wiki page below for archival/reference: = Sqoop - A Data Transfer Tool for Hadoop = == Abstract == Sqoop is a tool designed for efficiently transferring bulk data between Apache Hadoop and structured datastores such as relational databases. You can use Sqoop to import data from external structured datastores into Hadoop Distributed File System or related systems like Hive and HBase. Conversely, Sqoop can be used to extract data from Hadoop and export it to external structured datastores such as relational databases and enterprise data warehouses. == Proposal == Hadoop and related systems operate on large volumes of data. Typically this data originates from outside of Hadoop infrastructure and must be provisioned for consumption by Hadoop and related systems for analysis and processing. Sqoop allows fast provisioning of data into Hadoop and related systems by providing a bulk import and export mechanism that enables consumers to effectively use Hadoop for data analysis and processing. == Background == Sqoop was initially developed by Cloudera to enable the import and export of data between various databases and Hadoop Distributed File System (HDFS). It was provided as a patch to Hadoop project via the issue [[https://issues.apache.org/jira/browse/HADOOP-5815|HADOOP-5815]] and was maintained as a contrib module to Hadoop between May 2009 to April 2010. In April 2010, Sqoop was removed from Hadoop contrib via [[https://issues.apache.org/jira/browse/MAPREDUCE-1644|MAPREDUCE-1644]] and was made available by Cloudera on [[http://github.com/cloudera/sqoop|GitHub]]. Since then Sqoop has been maintained by Cloudera as an open source project on GitHub. All code available in Sqoop is open source and made publicaly available under the Apache 2 license. During this time Sqoop has been formally released three times as versions 1.0, 1.1 and 1.2. == Rationale == Hadoop is often used to process data that originated or is later served by structured data stores such as relational databases, spreadsheets or enterprise data warehouses. Unfortunately, current methods of transferring data are inefficient and ad hoc, often consisting of manual steps specific to the external system. These steps are necessary to help provision this data for consumption by Map-Reduce jobs, or by systems that build on top of Hadoop such as Hive and Pig. The transfer of this data can take substantial amount of time depending upon its size. An optimal transfer approach that works well with one particular datastore will typically not work as optimally with another datastore due to inherent architectural differences between different datastore implementations. Sqoop addresses this problem by providing connectivity of Hadoop with external systems via pluggable connectors. Specialized connectors are developed for optimal performance for data transfer between Hadoop and target systems. Analyzed and processed data from Hadoop and related systems may also require to be provisioned outside of Hadoop for consumption by business applications. Sqoop allows the export of data from Hadoop to external systems to facilitate its use in other systems. This too, like the import scenario, is implemented via specialized connectors that are built for the purposes of optimal integration between Hadoop and external systems. Connectors can be built for systems that Sqoop does not yet integrate with and thus can be easily incorporated into Sqoop. Connectors allow Sqoop to interface with external systems of different types, ensuring that newer systems can integrate with Hadoop with relative ease and in a consistent manner. Besides allowing integration with other external systems, Sqoop provides tight integration with systems that build on to of Hadoop such as Hive, HBase etc - thus providing data integration between Hadoop based systems and external systems in a single step manner. == Initial Goals == Sqoop is currently in its first major release with a considerable number of enhancement requests, tasks, and issues logged towards its future development. The initial goal of this project will be to address the highly requested features and bug-fixes towards its next dot release. The key features of interest are the following: * Support for bulk import into Apache HBase. * Allow user to supply password in
Re: [VOTE] Accept Sqoop for Incubation
+1 (binding) cool project, if everything turns out well, I will surely need it in future. Go go go! ;-) On Wed, Jun 8, 2011 at 5:39 AM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
+1 and welcome ! 2011/6/8 arv...@cloudera.com arv...@cloudera.com: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
My name is Yegor Kozlov. I'm a Java developer, committer and a PMC in the Apache POI project. I've been hacking Microsoft Office formats since 2005 and got pretty solid knowledge of the internals of MS Excel and PowerPoint. I'm interested in bringing the ODF Toolkit to Apache and integrating this API with Apache POI. With ODF, POI will become a universal API for Office documents covering most of popular office formats. Apache POI is a conduit to other Apache products, in particular, to Apache Tika which uses POI for text extraction. Support for ODF is certainly a subject of interest here. Regards, Yegor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
Hi, Von: Yegor Kozlov ye...@apache.org I'm interested in bringing the ODF Toolkit to Apache and integrating this API with Apache POI. With ODF, POI will become a universal API for Office documents covering most of popular office formats. As I see this the second time in an introduction now - please be aware that the current project proposal is not about ODF toolkit. Although ODF toolkit once was a sub-project of OOo, it is now a seperate project (http://odftoolkit.org/) and (afaik) does not share code with OpenOffice.org. People from IBM might give more details, as they helped to create ODF-toolkit as independend project. regards, André PS.: the good thing for Apache is, that ODF toolit is under Apache License already. http://odftoolkit.org/docs/license.txt - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re : Request: Can proposed committers introduce themselves?
Hello, My name is Eric Bachard. In the real life, I'm Professor of Applied Physics at UTBM (see [1]). In my spare time, I'm contributing to free software, as core developer. Contributing to OpenOffice.org since 2004, my skills are C ++ / C, objective C, shell and Perl. I know well OpenOffice.org source tree, build system, code too, and can work for all major ports (Windows, Mac OS X , Linux), including on some precise parts like the framework, the abstraction layer, Impress too. Used to mentor students with EducOOo (more than 15), and with Google Summer of Code (mentored 4 students, in 2006, 2007 and 2010 for it), I am willing to contribute to the code and train students to OOo. My vision is to see the OpenOffice.org accepted, Education Project become sort of a Laboratory dedicated to OpenOffice.org, and see a day there is a real bridge between OpenOffice.org and the Educational world. Mostly : - sharing the knowledge, honestly ; - working with students, teachers and schools : hear them, and catch the Fun they can bring us ; - attracting new developers : critical for OOo ; - innovating : always ready to test a new idea in the code :-). Some of my roles and contributions : - Founding member of EducOOo [4] - OOo4Kids and OOoLight main developer [5] [6] - Education Project since 2007 (current Project Lead) [3] - Mac OS X native port of OpenOffice.org : was the Project Lead (2005 -2007) Last but not least, I'm not a native speaker, so please, be gentle, and apologies for my terrible english :) With best regards, Eric Bachard [1] UTBM : http://www.utbm.fr [2] OpenOffice.org Domain developers : http:// wiki.services.openoffice.org/wiki/DomainDeveloper [3] OpenOffice.org Education Project : http://education.openoffice.org [4] EducOOo : http://www.educoo.org [5] OOo4Kids : http://wiki.ooo4kids.org [6] OOoLight : http://wiki.ooolight.org Le 7 juin 11 à 19:12, robert_w...@us.ibm.com a écrit : By my count we have now have over 60 individuals listed on as proposed committers for the Apache OpenOffice project. I think this is a respectable start, though obviously the project will need to have a strong commitment to recruiting additional developers and growing the project further, On the list are many names on the list familiar to me, some from the OpenOffice.org community, some ODF experts, some involved in training and certification, some in globalization, some from downstream projects, commercial and open source, Symphony, RedOffice, EducOOo, even some TDF/LO names. There are also a lot of names that I do not recognize. This is good as well. I may have need of some new friends soon ;-) I think it would be good if the proposed committers who have not yet done so, could post a quick note to the list, to introduce yourself and your interest in this project. Think of this as an opportunity to introduce yourself to your future collaborators on Apache OpenOffice. Regards, -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- qɔᴉɹə Education Project: http://wiki.services.openoffice.org/wiki/Education_Project Projet OOo4Kids : http://wiki.ooo4kids.org/index.php/Main_Page L'association EducOOo : http://www.educoo.org Blog : http://eric.bachard.org/news
Re: Code covered by the Oracle grant
On 08.06.2011 00:37, robert_w...@us.ibm.com wrote: Greg Steingst...@gmail.com wrote on 06/07/2011 05:50:49 PM: Besides the content Oracle owns, it seems we could just ask the other owners to give the CWS's to the ASF. I mean, really... *somebody* out there holds the copyright. We just have to determine who, and then ask. Some definite legwork, but it seems doable. I was assuming that the CWS's contributed to OOo were already covered under the JCA, Sun Contributor Agreement or Oracle Contributor Agreement, depending on the date: http://wiki.services.openoffice.org/wiki/Joint_Copyright_Assignment Or is that note the case? Anyone know? With the usual reservation that you should not trust what people who arent't legal practitioners tell you about licenses or copyright, you are basically right. Regards, Mathias - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
On 06/08/2011 04:16 AM, Christian Lippka wrote: Moin Moin [1], my name is Christian Lippka and I work on the donnated code base since 1998 when I was hired by StarDivision which was then consumed by Sun and later bought by Oracle. Oracle is also my current employer. I am here as an individual, so everything I do and say is based on my own opinions and motivations. Please note that I can not and will not discuss decisions made by Sun/Oracle now or in the past. I also obviously do not speak for Oracle in any way and I'm not in any way involved in the donation process that is currently going on. That said, my past work was to lead the Sun/Oracle internal development of the Impress and Draw application. My work includes - the creation of the flash export - the down stripping of code to create the (discontinued before open sourcing) stand alone StarOffice Impress Player - the specification of the presentation and graphic parts of the OpenOffice.org xml format which later became the base for ODF - driving development of the UNO API for impress and draw so it is now possible to have an xml filter for impress that does not link to the application code - adding native table support to impress and draw - bootstrapping the graphics part of the native mac port by fixing open issues in the vcl sal layer for aqua (spare time project) - working on the renaissance project to modernize the overal UI experience of impress At heard I'm a C/C++ hacker but I nowadays often use Java for small private projects out of convenience and I started to get some experience in Objectice-c. I am not an idealist at all, I tend to use the tool that does the job at hand best. This makes me currently a desktop user of a windows pc, an ubuntu box and a lovely old mac pro. As someone coming originally from the hardware world I still have a huge interest in embedded and mobile and would love to see an OOo derivate on a tablet. My personal motivation to join this proposal as a committer is based on my bounding with the underlying source code and also the people involved. You can not work 12 years on the same thing without getting to either hate or love it. So for me it is obviously love and passion and it would make me sad to not even try to make this proposal a success. Now a valid question could be, why ASF and not TDF. For me, this is not a binary question. I have already contributed to OpenOffice.org in my spare time. I have also already (though small) contributed to LibreOffice in my spare time. While I have some different opinions, I do not oppose the TDF or LibreOffice. I am not here to make this project win and another project fail. I am not here to dishonor the good work that good people put into something that they think is the best way to go. But I hope that people will respect others for trying to do something different, even so we may share many of the same goals. I'm happy with healthy competition. Not competition in the sense that the same work needs to be done multiple times. But competition in the sense to try different things, provide diversity and something to choose from. At least this is my understanding of liberty, the freedom to be able to choose from different options. If there is only one option to choose from, even if this is the perfect option, this is still no longer freedom. My opinion on the split/unite community is very simple. For me, there is but one open office community. If you are working on any branch, fork, clone, sibling, successor,predecessor of what is OpenOffice.org, you are part of that community. If you are a teacher at a school and promote the use of any odf based office suite, you are part of this community. If you hate to see a world where there is only one vendor dominating something that is essential for everyone in the digital age, you are part of the community. And yet, inside this community there are other communities, formed around goals, opinions, motivations. And I think that is perfectly valid. I also think that while it is hard some times it is a good thing that this heats up so much emotions. This shows that OpenOffice.org did not just start something that is useful. It started something that people are passionate about. And this makes me so exited to be part of it. My technical vision (as in, not plans, no facts, no I tell you how to do it) for this particular project under the umbrella of the ASF is as follows. I see this as an opportunity to do some bold moves that will jumpstart the free office world to the next level. One such bold move in the past was the switch to XML. I think this changed everything, and I usually hate such marketing speech :) What I would love to see is a major rework concerning modularization and configurability. In the past I was part of many discussions on what would be the best UI framework for OpenOffice.org to solve all problems including world peace. Obviously there was no such thing. This is
Re: A little OOo history
On 07.06.2011 17:13, Danese Cooper wrote: It's a lot of code as well. When we launched it took a day (as in 24 hours) to build. I'd imagine that situation will have improved somewhat Indeed, fortunately. And before the 24 hours build is quoted out of the context that these number originates from builds back in 1999 with a somewhat strange build system, let met assure that with modern hardware a complete build will take not more than 2 hours, depending on the platform and the tools used. Regards, Mathias - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 Niall On Wed, Jun 8, 2011 at 5:38 AM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to Cloudera provided
Re: Request: Can proposed committers introduce themselves?
On Wed, Jun 8, 2011 at 12:40 PM, Andre Schnabel andre.schna...@gmx.net wrote: Hi, Von: Yegor Kozlov ye...@apache.org I'm interested in bringing the ODF Toolkit to Apache and integrating this API with Apache POI. With ODF, POI will become a universal API for Office documents covering most of popular office formats. As I see this the second time in an introduction now - please be aware that the current project proposal is not about ODF toolkit. Although ODF toolkit once was a sub-project of OOo, it is now a seperate project (http://odftoolkit.org/) and (afaik) does not share code with OpenOffice.org. People from IBM might give more details, as they helped to create ODF-toolkit as independend project. Apache POI is mentioned in the proposal, see Relationships With Other Apache Products. Rob mentioned the ODF toolkit too, so I thought it is relevant. PS.: the good thing for Apache is, that ODF toolit is under Apache License already. http://odftoolkit.org/docs/license.txt Not really, the source code goes under Oracle' Edition of ALv2 and all Java files include this header: / * * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER * * Copyright 2010 Oracle and/or its affiliates. All rights reserved.ed. * * Use is subject to license terms. * * Licensed under the Apache License, Version 2.0 (the License); you may not * use this file except in compliance with the License. You may obtain a copy * of the License at http://www.apache.org/licenses/LICENSE-2.0. You can also * obtain a copy of the License at http://odftoolkit.org/docs/license.txt * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an AS IS BASIS, WITHOUT * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * * See the License for the specific language governing permissions and * limitations under the License. * / - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Yegor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
+1 Niall On Wed, Jun 8, 2011 at 4:39 AM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Re : Request: Can proposed committers introduce themselves?
El 08/06/11 10:43, eric b escribió: Hello, My name is Eric Bachard. In the real life, I'm Professor of Applied Physics at UTBM (see [1]). In my spare time, I'm contributing to free software, as core developer. Contributing to OpenOffice.org since 2004, my skills are C++ / C, objective C, shell and Perl. I know well OpenOffice.org source tree, build system, code too, and can work for all major ports (Windows, Mac OS X , Linux), including on some precise parts like the framework, the abstraction layer, Impress too. Used to mentor students with EducOOo (more than 15), and with Google Summer of Code (mentored 4 students, in 2006, 2007 and 2010 for it), I am willing to contribute to the code and train students to OOo. My vision is to see the OpenOffice.org accepted, Education Project become sort of a Laboratory dedicated to OpenOffice.org, and see a day there is a real bridge between OpenOffice.org and the Educational world. Mostly : - sharing the knowledge, honestly ; - working with students, teachers and schools : hear them, and catch the Fun they can bring us ; - attracting new developers : critical for OOo ; - innovating : always ready to test a new idea in the code :-). +1 Some of my roles and contributions : - Founding member of EducOOo [4] - OOo4Kids and OOoLight main developer [5] [6] - Education Project since 2007 (current Project Lead) [3] - Mac OS X native port of OpenOffice.org : was the Project Lead (2005 -2007) Last but not least, I'm not a native speaker, so please, be gentle, and apologies for my terrible english :) With best regards, Eric Bachard [1] UTBM : http://www.utbm.fr [2] OpenOffice.org Domain developers : http://wiki.services.openoffice.org/wiki/DomainDeveloper [3] OpenOffice.org Education Project : http://education.openoffice.org [4] EducOOo : http://www.educoo.org [5] OOo4Kids : http://wiki.ooo4kids.org [6] OOoLight : http://wiki.ooolight.org Le 7 juin 11 à 19:12, robert_w...@us.ibm.com a écrit : By my count we have now have over 60 individuals listed on as proposed committers for the Apache OpenOffice project. I think this is a respectable start, though obviously the project will need to have a strong commitment to recruiting additional developers and growing the project further, On the list are many names on the list familiar to me, some from the OpenOffice.org community, some ODF experts, some involved in training and certification, some in globalization, some from downstream projects, commercial and open source, Symphony, RedOffice, EducOOo, even some TDF/LO names. There are also a lot of names that I do not recognize. This is good as well. I may have need of some new friends soon ;-) I think it would be good if the proposed committers who have not yet done so, could post a quick note to the list, to introduce yourself and your interest in this project. Think of this as an opportunity to introduce yourself to your future collaborators on Apache OpenOffice. Regards, -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- - // Marcelo Fortino www.estrategiasgnulinux.com //Servicios Informáticos //Formación·Software Libre AVISO: Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial y/o datos de carácter personal, cuya difusión está regulada por la Ley Orgánica de Protección de Datos y la Ley de Servicios de la Sociedad de la Información. De conformidad con la Ley 15/1999, de 13 de Diciembre de Protección de Datos, les informamos que sus datos personales, forman parte de nuestra base de datos, utilizándolos a efectos de gestión operativa. Pueden ejercer sus derechos de acceso, rectificación, cancelación y oposición, enviando un e-mail a servic...@estrategiasgnulinux.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Upstream/Downstream (was OpenOffice LibreOffice)
On 8 June 2011 08:43, Jochen Wiedmann jochen.wiedm...@gmail.com wrote: On Wed, Jun 8, 2011 at 6:51 AM, Norbert Thiebaud nthieb...@gmail.com wrote: On Tue, Jun 7, 2011 at 9:43 PM, Noel J. Bergman n...@devtech.com wrote: [...] their downstream code cannot be used. Hence, the best outcome under the current licensing regime is for all core development to be done here, and for TDF to be a downstream consumer. Just because you choose a particular license that does not make you de-facto 'upstream'. Noel is describing a fact: It there is going to be something like upstream, it can only be an ASL licensed OO, not a LGPL'ed LO. What he misses (as quite a few others do, which is possibly why you are reacting angry) is a certain amount of sensibility that acknowledges that this fact is just as likely to cause a total split between LO and OO. Your reaction only goes to show that this sensibility is required: Such a split would be the worst thing to happen and it is something where LO would loose nothing (compared to the time before the proposal) but would have missed a chance to win. This is really the crux of all the discussions. Is it better to maximise the development resource through cooperation or is it better to have two separate developments that end up incompatible with one another as far as code sharing is concerned? It's no good saying if this or if that because we are where we are. If my aunt had balls she'd be my uncle :-). So in the end it is really quite a simple choice, cooperation or separation. If it is cooperation and the licenses stay the same then to maximise resources, Noel's position is logical if not easy emotionally or philosophically for some. Jochen -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ian Ofqual Accredited IT Qualifications (The Schools ITQ) www.theINGOTs.org +44 (0)1827 305940 The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and Wales.
Re: Code covered by the Oracle grant
On 06/07/2011 06:08 PM, Andrew Rist wrote: It is Oracle's intent to provide to ASF the files needed to build OOo, taking into account licensing and ownership issues. This includes binary artifacts such as the OOo artwork and translation databases. I am following the discussions here closely, and I am collected all of the lists that are provided. In order to execute the standard ASF Software Grant we were required to come up with an initial list of files, and so the list, which has been distributed, is exactly that - an initial list. As previous stated [1][2], Oracle wants to provide what is needed for the continuity of the OOo project. In terms of svn history and such, that becomes more of an issue for the podling to decide, and is discussed in the podling documentation [3]. Now, the database with OOo is hsqldb, Java based, so assuming we want to run this on Apache Harmony, does the Java TCK becomes a test dependency of OOo? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
On 6/8/11 6:38 AM, Jonathan Hsieh wrote: [X] +1 Accept Flume for incubation (binding) -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
On 06/08/2011 04:39 AM, arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ +1 ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Code covered by the Oracle grant
On Wed, Jun 8, 2011 at 6:53 AM, Steve Loughran ste...@apache.org wrote: Now, the database with OOo is hsqldb, Java based, so assuming we want to run this on Apache Harmony, does the Java TCK becomes a test dependency of OOo? No - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
On 06/08/2011 05:38 AM, Jonathan Hsieh wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ +1 ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation (probably binding, I'm on incubator-pmc after all) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 (non-binding). On Wed, Jun 8, 2011 at 10:08 AM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to
Re: [VOTE] Flume to join the Incubator.
+1 (binding) and good luck :) On Wed, Jun 8, 2011 at 1:22 PM, Sanjiva Weerawarana sanj...@opensource.lk wrote: +1 (non-binding). On Wed, Jun 8, 2011 at 10:08 AM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was
Re: Happy happy joy joy
On Jun 7, 2011, at 2:43 PM, Simos Xenitellis wrote: On Thu, Jun 2, 2011 at 6:17 PM, Jim Jagielski j...@jagunet.com wrote: Guys, if we are going to argue over the mistakes of the pasts and the slights of the past, quite frankly, we aren't going to get very far. This is supposed to be a happy occasion; let's not bicker and argue about who-killed-who... :) If this is an attempt for reconciliation, it's somewhat poor ;-) And the last paragraph, quite ambiguous. You say 'bicker', which can be interpreted as a way to dissuade people from discussing. Do you feel people are bickering? The whole affair is a big issue, and what I detect is an attitude that it would better just not to discuss the touchy issues, as if they will go away. Monty Python and the Holy Grail. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Upstream/Downstream (was OpenOffice LibreOffice)
On Wed, Jun 08, 2011 at 09:43:45AM +0200, Jochen Wiedmann wrote: On Wed, Jun 8, 2011 at 6:51 AM, Norbert Thiebaud nthieb...@gmail.com wrote: On Tue, Jun 7, 2011 at 9:43 PM, Noel J. Bergman n...@devtech.com wrote: [...] their downstream code cannot be used. Hence, the best outcome under the current licensing regime is for all core development to be done here, and for TDF to be a downstream consumer. Just because you choose a particular license that does not make you de-facto 'upstream'. Noel is describing a fact: It there is going to be something like upstream, it can only be an ASL licensed OO, not a LGPL'ed LO. What he misses (as quite a few others do, which is possibly why you are reacting angry) is a certain amount of sensibility that acknowledges that this fact is just as likely to cause a total split between LO and OO. +1 The split between LO and OOo is reality. The code bases are already divergent and it would be very difficult to reconcile them. To make Apache OOo upstream from LO would mean one of two things: 1. The LO people throw out everything they've done and start over from scratch. 2. The LO people organize a large collective software grant to Apache for their work. Since there are a lot of people involved, this would be a daunting task even if it wasn't politically toxic. In both scenarios, TDF, after all they've gone through, after all the work they've done, takes on a reduced role: to use Norbert's analogy, they go from being the auto factory to being a custom shop. We're coming off like some know-it-all newbie manager waltzing in after a hostile takeover and imperiously informing the people closest to the project that they are being demoted and they should be happy about it 'cause our organization is so freakin' awesome. What we ought to be doing instead, if we really want to form good relationships with the LO community, is not continually repeating abrasive facts about licensing, but showing a modicum of *humility*. The reason I praised Sam is that he is clearly sensitive to all this. He has been an exemplary ambassador, and my hat is off to him. It is worth repeating his recommendations in their entirety: That indeed would be a wonderful place to end up. At the present time, there are people who would rather not participate in such an arrangement. They have something that works just fine for them. Many are skeptical that we can deliver. The most that we can do is (a) enable such collaboration, and (b) execute. If we do both well, we will achieve much more than we could by prior agreement. I think it is in our best interests to acknowledge that we don't yet have a track record or anything new to offer. And that in such a context it is rather presumptuous at this point for us proclaim that we are the core or even are relevant. I think that passage represents the best of Apache's inclusive traditions, and I hope we can live up to it -- both the sake of the project and for our own sake as human beings. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Upstream/Downstream (was OpenOffice LibreOffice)
Hello Marvin, Le Wed, 8 Jun 2011 06:04:42 -0700, Marvin Humphrey mar...@rectangular.com a écrit : On Wed, Jun 08, 2011 at 09:43:45AM +0200, Jochen Wiedmann wrote: On Wed, Jun 8, 2011 at 6:51 AM, Norbert Thiebaud nthieb...@gmail.com wrote: On Tue, Jun 7, 2011 at 9:43 PM, Noel J. Bergman n...@devtech.com wrote: [...] their downstream code cannot be used. Hence, the best outcome under the current licensing regime is for all core development to be done here, and for TDF to be a downstream consumer. Just because you choose a particular license that does not make you de-facto 'upstream'. Noel is describing a fact: It there is going to be something like upstream, it can only be an ASL licensed OO, not a LGPL'ed LO. What he misses (as quite a few others do, which is possibly why you are reacting angry) is a certain amount of sensibility that acknowledges that this fact is just as likely to cause a total split between LO and OO. +1 The split between LO and OOo is reality. The code bases are already divergent and it would be very difficult to reconcile them. To make Apache OOo upstream from LO would mean one of two things: 1. The LO people throw out everything they've done and start over from scratch. 2. The LO people organize a large collective software grant to Apache for their work. Since there are a lot of people involved, this would be a daunting task even if it wasn't politically toxic. In both scenarios, TDF, after all they've gone through, after all the work they've done, takes on a reduced role: to use Norbert's analogy, they go from being the auto factory to being a custom shop. We're coming off like some know-it-all newbie manager waltzing in after a hostile takeover and imperiously informing the people closest to the project that they are being demoted and they should be happy about it 'cause our organization is so freakin' awesome. What we ought to be doing instead, if we really want to form good relationships with the LO community, is not continually repeating abrasive facts about licensing, but showing a modicum of *humility*. The reason I praised Sam is that he is clearly sensitive to all this. He has been an exemplary ambassador, and my hat is off to him. It is worth repeating his recommendations in their entirety: That indeed would be a wonderful place to end up. At the present time, there are people who would rather not participate in such an arrangement. They have something that works just fine for them. Many are skeptical that we can deliver. The most that we can do is (a) enable such collaboration, and (b) execute. If we do both well, we will achieve much more than we could by prior agreement. I think it is in our best interests to acknowledge that we don't yet have a track record or anything new to offer. And that in such a context it is rather presumptuous at this point for us proclaim that we are the core or even are relevant. I think that passage represents the best of Apache's inclusive traditions, and I hope we can live up to it -- both the sake of the project and for our own sake as human beings. Well spoken; although I believe that humility has to be equally shared among every stakeholder :-) I think you have perfectly summarized the issue here, and I think it's perhaps time to consider this issue to be clearly stated in this way (at least the part related to TDF). Now if we could move forward I think that what could make sense would be to define or clarify what exact purpose would serve the OpenOffice code base at Apache and the Apache Openoffice project. I know that no codebase ever had any intent in itself and that people do whatever they want. That's true and by the way that's why software patents are dangerous, (but that's another discussion), but it does not preclude the project and its vision to be articulated in a different way than a general purpose office suite that's free, open source and uses ODF. In this case, LibreOffice fits the bill, but so does KOffice/Calligra (btw, nice examples to draw inspiration from), Abiword/Gnumeric, etc. My understanding is that the Apache OpenOffice codebase matters to IBM and anyone who would want to use the specificities of the Apache licensing, and I understand this as being a reality we can all agree on. Instead of spending hours and keystrokes pondering on the ability of the Apache OpenOffice project to execute or to become LibreOffice's upstream, I would like to rephrase or reframe Simon's proposal, esp. its points 2 and 3 (2: rename the project to Apache ODF suite 3. make this project not the office suite that competes with LibreOffice but make it the meeting point of development efforts for specific purposes and ODF). Basically this amounts to think about the current proposal based on two factors: 1. find a proper coherence and relevance between Apache OOo LibreOffice on a technological
Re: [VOTE] Accept Sqoop for Incubation
On Tue, Jun 7, 2011 at 11:39 PM, arv...@cloudera.com arv...@cloudera.comwrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation +1 (non-binding) Phil
Re: OpenOffice: Arguments and facts. Going ahead
300.000 downloads/day * 180 MB = 5400 MB / 1024 = roundabout 53.000 Gigs. Source: http://marketing.openoffice.org/marketing_bouncer.html Presumably we would distrubute through the usual *mirror* system - so the load should mostly by on other peoples hardware, no? Leo Simons explained that very well in another mail and confirms what you say. I asked at the infra channel and they confirmed this too. Its already Wednesday, I guess we can vote on Friday. Christian Niall Cheers agreed -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo mirroring (was: Re: A little OOo history)
Hello Leo, thanks for your interesting mail. It relaxes me and consider this one closed Cheers, Christian On Tue, Jun 7, 2011 at 8:22 PM, Leo Simons m...@leosimons.com wrote: On Tue, Jun 7, 2011 at 6:35 PM, Christian Grobmeier grobme...@gmail.com wrote: 30 downloads per day or per month? 52TB per month is still a lot... per day. Look at this chart: http://marketing.openoffice.org/marketing_bouncer.html TL;DR: these bandwidth numbers are not actually that scary or important -- the OOo infrastructure does not serve up all that traffic, the many mirrors do, and traffic from the OOo infrastructure to the mirrors is very efficient since it efficiently pushes out new releases (with rsync). The big work in mirroring is setting up the process and shepherding the mirroring community. OOo has 118 mirrors. Apache has 294 mirrors. There is significant overlap -- a lot of sites that mirror apache downloads already mirror OOo downloads and vice versa. http://download.services.openoffice.org/mirrors/all.html http://www.apache.org/mirrors/ Note that many of the mirrors of OOo and of apache also mirror large amounts of other open source software. OOo uses mirrorbrain [1]. Apache uses some CGI scripts to accomplish a lot but not all of the same functionality. The set of data ASF pushes to its mirrors is somewhere downwards of 50GB [4]. The set of data OOo pushes is somewhere downwards of 300 GB [2]. It doesn't seem like a good idea to push an additional 300GB to all existing apache mirrors: that isn't quite what they signed up for. As I understand it Oracle wants to transition out of maintaining the OOo infrastructure eventually. So if OOo gets accepted into the incubator, it seems like the smart approach would be to duplicate the existing OOo mirrorbrain installation onto some apache hardware, with the people that look after the OOo and apache mirrors figuring out the specific details. Will be a fair bit of work I imagine so definitely needs volunteers to step up and all that, but nothing particularly scary I think, assuming the existing OOo mirror maintainers [3] help out. Without their help it will be much harder to figure out how to do things! If most of the people that worked on mirroring at OOo are now at TDF (and looking at mail archives it seems that might be true [7]), better be extra nice to them TDF folks :-) Long term, if there's people to do the work, one could imagine updating the custom ASF mirror infrastructure to use mirrorbrain which seems like a cool tool...but that is a _lot_ of work because the existing CGI scripts integrate into the download pages of every apache project. cheers, Leo PS: LibreOffice also uses mirrorbrain [5], having about 65 mirrors. They required only 15GB for a mirror though [6], not the OOo footprint 200GB. Sounds much more reasonable... [1] http://mirrorbrain.org/ [2] http://wiki.services.openoffice.org/wiki/New_OOo_Mirror_Structure http://distribution.openoffice.org/files.html http://wiki.services.openoffice.org/wiki/Mirrors_Project [3] http://openoffice.org/projects/distribution/lists [4] http://www.apache.org/info/how-to-mirror.html [5] http://download.documentfoundation.org/mirrors/all.html http://wiki.documentfoundation.org/Mirrors [6] http://download.documentfoundation.org/mirroring.html [7] http://blog.gmane.org/gmane.comp.documentfoundation.mirrors - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
Andre Schnabel andre.schna...@gmx.net wrote on 06/08/2011 04:40:56 AM: Von: Yegor Kozlov ye...@apache.org I'm interested in bringing the ODF Toolkit to Apache and integrating this API with Apache POI. With ODF, POI will become a universal API for Office documents covering most of popular office formats. As I see this the second time in an introduction now - please be aware that the current project proposal is not about ODF toolkit. Although ODF toolkit once was a sub-project of OOo, it is now a seperate project (http://odftoolkit.org/) and (afaik) does not share code with OpenOffice.org. People from IBM might give more details, as they helped to create ODF-toolkit as independend project. This was in a previous discussion. I am interested in bringing the ODF Toolkit over to Apache. It is already 100% Apache 2.0 license. I'm a Steering Committee member on the ODF Toolkit Union, but obviously there are others, and we'll want to bring them and the developers in on this discussion. What is not resolved at this point is whether we target the ODF Toolkit as part of the OpenOffice, target it as a new TLP, or target it to POI. I think one could make a good argument for either one of these. My main recommendation was to defer this discussion and decision until after the debate on the OpenOffice proposal was done. Then we can engage the ODF Toolkit Union in this discussion. The connection of OOo and ODF Toolkit is like this, from app developer perspective: 1) If you want to do desktop client manipulation of documents, with a GUI and within the editors, then we have UNO-based scripting. This could include some kinds of batch processing. 2) If you want to do server side processing of documents, then you could run OOo on server as well, with the obvious performance constraints. Or you could use the ODF Toolkit, which is a lighter weight solution. POI developers would be familiar with this advantage, as well as the liabilities, e.g., who calculates/updates formulas, who creates/updates metafiles, etc. A sufficiently complex business application based on OpenOffice is going to involve document manipulations at both tiers. For example, we recently (at IBM) made an insurance solution that involved using Symphony, extended with a Plugin, submitting documents into a workflow, where they were introspected and validated using the ODF Toolkit. I'm sure many of us are familiar with the range of documents out there, from fully structured XML, forms, to semi-structured documents, to unstructured free-form documents. From what I've seen the sweet spot for ODF/OpenOffice automation is in the semi-structured area, where it is not quite structured enough to go with a form, but requires some free-form work by the user in a familiar word processor. So wherever the code goes, I think we'll want/need close technical coordination via a triangle of concerns: 1) The ODF editors, OpenOffice, LibreOffice, etc. 2) The ODF Toolkit 3) The ODF Standard, i.e., the Technical Committee at OASIS I intend to be involved across all three. I think that makes sense for anyone interested in the document automation scenarios, things that go beyond mere interactive editing. Regards, -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
Dear -Rob, all, 2011/6/7 robert_w...@us.ibm.com: [...] We should be able to check the math from another direction. Microsoft claims something like 400 million Office users. Studies looking at OOo install share show approximately 10%. Pick some random number between 6 and 12 months. Call it mean time to upgrade to a new OOo release. In my case the random number came out to be 10 months, fortunate for me for doing the math in my head. That gives 4 million users downloading/month. That gives 130,000 downloads/day. I know that is not the same number quoted, but it is in the ball park. Since this is a large download, I wonder whether the quoted numbers are impacted at all by timeouts, abandoned downloads attempts, etc. In other words, is it counting the HTTP GET's? Or the successful downloads? That may influence the load by quite a bit. It may even make it worse. And let's not even get started on the burst traffic when a major new release is announced. Of course, this is not necessarily a problem for Apache. Think of it this way. It would be perfectly possible, and actually quite easy for someone to host the files with a scalable cloud storage provider, e.g., Amazon, and charge $0.99 for the download, the cost of an iPhone app. That is over $30 million/year. Heck, I might just do that myself and retire! I only would like to know, whether this posting was really for the apache communtiy mailinglist or an IBM internal mailinglist to evolve a businessplan? cheers Manfred - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Request: Can proposed committers introduce themselves?
I am pleased that we have been asked to introduce ourselves. I am excited by what I have been reading this morning. I consider myself to be handicapped as an American native-language English speaker. It is very easy to say something in a very complex way and not notice. With so many participants from other language communities here, I want to communicate well. So your presence is an opportunity for my own training in having an international life. And, by the way. If you had not said you are not a native speaker, I could not determine that from your introduction statement. If I were to attempt to speak or write French, I think it would be a great embarrassment. I share your interest in education. For me it takes the form of ideas from CP4E (computer programming for everybody) and SE4E (software engineering ...). But also fluency with computing and information technology. I don't subscribe so much to the idea of computational thinking though. - Dennis PS: Someday, I would like to know what about the University of Pennsylvania inspired UTC, UTBM, and UTT, http://en.wikipedia.org/wiki/Universit%C3%A9_de_technologie_de_Belfort-Montb%C3%A9liard. -Original Message- From: eric b [mailto:eric.bach...@free.fr] Sent: Wednesday, June 08, 2011 01:44 To: general@incubator.apache.org Subject: Re : Request: Can proposed committers introduce themselves? Hello, My name is Eric Bachard. In the real life, I'm Professor of Applied Physics at UTBM (see [1]). [ ... ] Last but not least, I'm not a native speaker, so please, be gentle, and apologies for my terrible english :) With best regards, Eric Bachard [1] UTBM : http://www.utbm.fr [2] OpenOffice.org Domain developers : http:// wiki.services.openoffice.org/wiki/DomainDeveloper [3] OpenOffice.org Education Project : http://education.openoffice.org [4] EducOOo : http://www.educoo.org [5] OOo4Kids : http://wiki.ooo4kids.org [6] OOoLight : http://wiki.ooolight.org [ ... ] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Request: Can proposed committers introduce themselves?
Hi Christian. What a great positive attitude. I'm excited to see you here. And moin moin to you too (it is 06:56 here in Seattle). I did not know the relationship with moien auf Deutsch. Now I know why Svante Schubert says it. Ciao, - Dennis -Original Message- From: Christian Lippka [mailto:c...@lippka.com] Sent: Wednesday, June 08, 2011 01:17 To: general@incubator.apache.org Subject: Re: Request: Can proposed committers introduce themselves? [ ... ] So for me it is obviously love and passion and it would make me sad to not even try to make this proposal a success. Now a valid question could be, why ASF and not TDF. For me, this is not a binary question. I have already contributed to OpenOffice.org in my spare time. I have also already (though small) contributed to LibreOffice in my spare time. While I have some different opinions, I do not oppose the TDF or LibreOffice. I am not here to make this project win and another project fail. I am not here to dishonor the good work that good people put into something that they think is the best way to go. But I hope that people will respect others for trying to do something different, even so we may share many of the same goals. [ ... ] My technical vision (as in, not plans, no facts, no I tell you how to do it) for this particular project under the umbrella of the ASF is as follows. I see this as an opportunity to do some bold moves that will jumpstart the free office world to the next level. One such bold move in the past was the switch to XML. I think this changed everything, and I usually hate such marketing speech :) What I would love to see is a major rework concerning modularization and configurability. In the past I was part of many discussions on what would be the best UI framework for OpenOffice.org to solve all problems including world peace. Obviously there was no such thing. This is even more true in the world we live in now. There is not only the desktop any more, my smartphone is faster than my first development pc at StarDivision. My android tablet has a bigger screen resolution than my first VGA monitor. To serve this diverse market of target devices and different input idioms there can not only be one user interface, there must be many. Also it would be cool to target different groups of users by providing a user interface that is optimized for a special task or need. See OOo4Kids as a great example. I'm not a native speaker but I tried hard to look up every more complicated word in the dictionary to check for possible misreadings. If you still find something that you have a grudge with or find offensive, please just blame it on a communication issue. Best regards, Christian [1] http://moinmo.in/MoinMoinEtymology - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
Hi -Rob 2011/6/7 robert_w...@us.ibm.com: Danese Cooper dan...@gmail.com wrote on 06/07/2011 03:43:56 PM: robert_w...@us.ibm.com: Not surprisingly, you missed my point (or chose to ignore it). We at Honestly, your insult does surprise me. Apache don't think that money is evil, but we also believe that seeing our code in wide use is more important than money. OpenOffice.org is important to the Developing World, some of whom will pay for convenience. I would hate to see Apache enter that business, however. Apache doesn't think or believe. Wise guy Do you think that is an attitude in a mailinglist of volunteers? That is an illogical reification. once more wisenhimer or what? If I've learned anything from participating in this list is that Apache members of of different minds on many things. That is fine. I have learned a lot in the OOo community, esp. that working with volunteers differs a little bit from a tone in a big company like yours. cheers Manfred - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
On Wed, Jun 8, 2011 at 3:58 PM, robert_w...@us.ibm.com wrote: A sufficiently complex business application based on OpenOffice is going to involve document manipulations at both tiers. For example, we recently (at IBM) made an insurance solution that involved using Symphony, extended with a Plugin, submitting documents into a workflow, where they were introspected and validated using the ODF Toolkit. Of course the ODF Toolkit isn't a golden fleece for server side ODF processing. I would rather call it a good compromise offering some room for improvement. If we would have had a choice we would have preferred a headless OO runing on either AIX or z/OS ;) For instances you still have to code a comprehensive amount of XSL stylesheets if using the ODF toolkit. One drawback we faced was that customers created their ODF documents during design time using Symphony and during runtime while mass-producing business correspondence documents the ODF Toolkit generated documents which were not 100% formatted equal to what has been created in Symphony earlier on. Thus our preference to use the same formatting engine (i.e. Symphony/OO) during both design time and run time. Cheers Daniel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
Manfred A. Reiter ma.rei...@gmail.com wrote on 06/08/2011 10:17:02 AM: 2011/6/7 robert_w...@us.ibm.com: [...] We should be able to check the math from another direction. Microsoft claims something like 400 million Office users. Studies looking at OOo install share show approximately 10%. Pick some random number between 6 and 12 months. Call it mean time to upgrade to a new OOo release. In my case the random number came out to be 10 months, fortunate for me for doing the math in my head. That gives 4 million users downloading/month. That gives 130,000 downloads/day. I know that is not the same number quoted, but it is in the ball park. Since this is a large download, I wonder whether the quoted numbers are impacted at all by timeouts, abandoned downloads attempts, etc. In other words, is it counting the HTTP GET's? Or the successful downloads? That may influence the load by quite a bit. It may even make it worse. And let's not even get started on the burst traffic when a major new release is announced. Of course, this is not necessarily a problem for Apache. Think of it this way. It would be perfectly possible, and actually quite easy for someone to host the files with a scalable cloud storage provider, e.g., Amazon, and charge $0.99 for the download, the cost of an iPhone app. That is over $30 million/year. Heck, I might just do that myself and retire! I only would like to know, whether this posting was really for the apache communtiy mailinglist or an IBM internal mailinglist to evolve a businessplan? This was just a back of the envelope calculation, based on public information, intended for the list. The 300,000 downloads/day listed on the OOo did not sound plausible to me initially, so I wanted to see if I could confirm or contradict this number independently. -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Upstream/Downstream (was OpenOffice LibreOffice)
On 6/8/2011 10:06 AM, Ross Gardler wrote: On 08/06/2011 16:33, Charles-H. Schulz wrote: 1. find a proper coherence and relevance between Apache OOo LibreOffice on a technological level and on a distribution level 2. find a proper coherence with IBM's business requirements (Symphony). I hope we can move forward on this. If we are to call the vote on Friday as currently seems to be the target (which is in no way fixed) I wonder if the ASF representatives who engaged with the TDF lists can provide a little feedback. Specifically I'm interested to know if there was any discussion along the above lines. I'm hoping 'they' don't. E.g. that the ASF representatives who engage the TDF community are the Podling PMC members, old hats and newcomers alike, and that this communication and community bridge-building is delegated to that podling itself. But if there are new concerns raised at TDF that must be addressed before an acceptance vote, I hope any of the signed up committers already feel free to bring those concerns to this list. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: This list is for how not why?
Khirano, I just noticed your mail never received a response. Sorry for that, reply online... Sent from my mobile device (so please excuse typos) On 6 Jun 2011, at 18:02, Kazunari Hirano khir...@gmail.com wrote: It has been familiar with us to file issues and comment on them.in the bugzilla that we called IssueTracker. Will OpenOffice.org infrastructures like the bugzilla be also contributed to Apache Software Foundation? The proposal indicates that an instance of JIRA has been requested for issue tracking. The precise workflow adopted will be defined by the podling during incubation. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
I think it would be good if the proposed committers who have not yet done so, could post a quick note to the list, to introduce yourself and your interest in this project. Think of this as an opportunity to introduce yourself to your future collaborators on Apache OpenOffice. Ian Lynch, cut my coding teeth on Algol W (IBM 370). BBC BASIC, 6502, 6809 and ARM Assembler. Now I don't have time to hack, I run a UK government accredited Awarding Organisation and I'm trying to build a global service business that can support FOSS and liberally licensed content for education. We have 6 people working in the company based in the UK and we have active projects in Malaysia, Kenya, USA, Romania, Bulgaria, Czech Republic, Germany, Spain and Netherlands all at various stages. Something in South America in relation to OOo specifically seems imminent. I have been a member of the OOo marketing community since the early days leading education for a time and I was a co-founder of the Open Document Fellowship. I'm quite interested in developing businesses that can support FOSS development and obviate the need for closed software licenses. I think the most important aspect of all this is ISO26300 because it and its developments enable a rich range of FOSS implementations in the document space. I'm sure this will migrate to the cloud so current OOo/LO implementations are going to have to change. In terms of certification, we are product neutral. Most of our customers get their IT user certificates using MS products. There was not sufficient demand early on for an exclusive we only deal with FOSS products stance and getting to users of proprietary licensed software at least gives them the opportunity to see that there are alternatives. We use a Lamp stack and Drupal for our core business, Libre Office on Ubuntu. We only use Windows and IE for testing the web site - lots of schools still on IE6 unfortunately a real pain ;-) My main constraint is time as I am constantly needing to find ways of keeping everyone here employed while we develop the business. -- Ian Ofqual Accredited IT Qualifications (The Schools ITQ) www.theINGOTs.org +44 (0)1827 305940 The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and Wales.
Re: Upstream/Downstream (was OpenOffice LibreOffice)
On Wed, Jun 8, 2011 at 11:17 AM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 6/8/2011 10:06 AM, Ross Gardler wrote: On 08/06/2011 16:33, Charles-H. Schulz wrote: 1. find a proper coherence and relevance between Apache OOo LibreOffice on a technological level and on a distribution level 2. find a proper coherence with IBM's business requirements (Symphony). I hope we can move forward on this. If we are to call the vote on Friday as currently seems to be the target (which is in no way fixed) I wonder if the ASF representatives who engaged with the TDF lists can provide a little feedback. Specifically I'm interested to know if there was any discussion along the above lines. I'm hoping 'they' don't. E.g. that the ASF representatives who engage the TDF community are the Podling PMC members, old hats and newcomers alike, and that this communication and community bridge-building is delegated to that podling itself. +1 But if there are new concerns raised at TDF that must be addressed before an acceptance vote, I hope any of the signed up committers already feel free to bring those concerns to this list. +1 - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Happy happy joy joy
Is that a copyleft swallow or an ALv2 swallow? On Wed, Jun 8, 2011 at 8:38 AM, Jim Jagielski j...@jagunet.com wrote: On Jun 7, 2011, at 2:43 PM, Simos Xenitellis wrote: On Thu, Jun 2, 2011 at 6:17 PM, Jim Jagielski j...@jagunet.com wrote: Guys, if we are going to argue over the mistakes of the pasts and the slights of the past, quite frankly, we aren't going to get very far. This is supposed to be a happy occasion; let's not bicker and argue about who-killed-who... :) If this is an attempt for reconciliation, it's somewhat poor ;-) And the last paragraph, quite ambiguous. You say 'bicker', which can be interpreted as a way to dissuade people from discussing. Do you feel people are bickering? The whole affair is a big issue, and what I detect is an attitude that it would better just not to discuss the touchy issues, as if they will go away. Monty Python and the Holy Grail. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
dsh daniel.hais...@googlemail.com wrote on 06/08/2011 10:37:46 AM: On Wed, Jun 8, 2011 at 3:58 PM, robert_w...@us.ibm.com wrote: A sufficiently complex business application based on OpenOffice is going to involve document manipulations at both tiers. For example, we recently (at IBM) made an insurance solution that involved using Symphony, extended with a Plugin, submitting documents into a workflow, where they were introspected and validated using the ODF Toolkit. Of course the ODF Toolkit isn't a golden fleece for server side ODF processing. I would rather call it a good compromise offering some room for improvement. If we would have had a choice we would have preferred a headless OO runing on either AIX or z/OS ;) For instances you still have to code a comprehensive amount of XSL stylesheets if using the ODF toolkit. One drawback we faced was that customers created their ODF documents during design time using Symphony and during runtime while mass-producing business correspondence documents the ODF Toolkit generated documents which were not 100% formatted equal to what has been created in Symphony earlier on. Thus our preference to use the same formatting engine (i.e. Symphony/OO) during both design time and run time. The ODF Toolkit Union has several projects. It sounds like you have been using the XSLT Runner component? We also have ODFDOM. This is a Java API that uses a code generation approach, giving a typed DOM that is 1:1 with the ODF schema. So this can read and write documents and preserve 100% of the its contents, formatting, metadata, etc. On top of that (we all need layers, right?) we have the Simple Java API for ODF, which is a high level API for manipulating the document. So things that might be a complex operation touching many ODF elements, like deleting a column in a table, are done in a single function call in the Simple API. We also took a set of navigators to select interesting content in the document. So you can do a regular expression search and replace. But also search for all text with style = header 3 and then do something on it. You can extract the text of a document in one line of code. You can copy a presentation slide from one presentation and put it into a another in one line of code, etc. The cool thing, in my opinion, compared to other ODF API's, is because the Simple API is based on ODFDOM and ODFDOM is generated from the ODF schema directly, then the Simple API manipulations preserve all of the existing document content. You can see the details here: http://simple.odftoolkit.org/ We also have a validation component, with tools for validating conformance of ODF documents, And we have a C# ODF API, which I don't know so much about. Regards, -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Happy happy joy joy
On Wed, Jun 8, 2011 at 5:45 PM, Donald Whytock dwhyt...@gmail.com wrote: Is that a copyleft swallow or an ALv2 swallow? No definitive indicator for the latter, but if it consumes parts of the other, then it must be the former ... -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. John Maynard Keynes (http://en.wikiquote.org/wiki/Keynes) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Flume to join the Incubator.
+1 Tom On Tue, Jun 7, 2011 at 9:38 PM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to Cloudera provided
RE: Upstream/Downstream (was OpenOffice LibreOffice)
Ian Lynch wrote: It's no good saying if this or if that because we are where we are. If my aunt had balls she'd be my uncle :-). Exactly. This is really the crux of all the discussions. Is it better to maximise the development resource through cooperation or is it better to have two separate developments that end up incompatible with one another as far as code sharing is concerned? So in the end it is really quite a simple choice, cooperation or separation. If it is cooperation and the licenses stay the same then to maximise resources, Noel's position is logical if not easy emotionally or philosophically for some. Not mine. Perhaps stated more clearly and plainly, but others said the same before me. The issue is that there are players, IBM not being the only one, who require a permissive license. TDF's licensing does not satisfy that requirement. TDF could change, but I haven't seen any positive indication that it would. So we are where we are: - There is a codebase under a permissive license. - There are players -- large and small -- who want/need to work on it. - There is a large community actively engaged in working on the code under a non-permissive license. - Code can only flow from permissive to non-permissive. Alternative suggestions as to HOW to collaborate are welcomed. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Upstream/Downstream (was OpenOffice LibreOffice)
Marvin Humphrey wrote: The code bases are already divergent and it would be very difficult to reconcile them. To make Apache OOo upstream from LO would mean one of two things OK, let's clarify for sensibility: Apache would be upstream (licensing acting as a diode), but not THE upstream. As for how to do that, that's something that would have to be worked out between the project and other stakeholders, e.g., TDF. The greater the extent of the upstream work, the greater the code sharing. Charles Schulz wrote: Instead of spending hours and keystrokes pondering on the ability of the Apache OpenOffice project to execute or to become LibreOffice's upstream OK, can we put to rest the idea that code sharing only flows in one direction due to the licensing, and that is the sole implication of the word upstream? :-) I would like to rephrase or reframe Simon's proposal: - rename the project to Apache ODF suite That's up to the project. - this project not the office suite that competes with LibreOffice but make it the meeting point of development efforts for specific purposes and ODF). Again, this is up to the project and the needs of its participants. But you appear to be ignoring the need for a permissively licensed product codebase on behalf of some members of the proposed community. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Happy happy joy joy
On 6/8/2011 11:12 AM, Jochen Wiedmann wrote: On Wed, Jun 8, 2011 at 5:45 PM, Donald Whytock dwhyt...@gmail.com wrote: Is that a copyleft swallow or an ALv2 swallow? No definitive indicator for the latter, but if it consumes parts of the other, then it must be the former ... I believe the proper question is What is the airspeed velocity of an AL laden, GPL swallow? (seeing as an AL swallow can't lift GPL). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: This list is for how not why?
On Wed, Jun 8, 2011 at 11:27, Ross Gardler rgard...@apache.org wrote: Khirano, I just noticed your mail never received a response. Sorry for that, reply online... Sent from my mobile device (so please excuse typos) On 6 Jun 2011, at 18:02, Kazunari Hirano khir...@gmail.com wrote: It has been familiar with us to file issues and comment on them.in the bugzilla that we called IssueTracker. Will OpenOffice.org infrastructures like the bugzilla be also contributed to Apache Software Foundation? The proposal indicates that an instance of JIRA has been requested for issue tracking. The precise workflow adopted will be defined by the podling during incubation. I suspect that just came with the template, rather than any specific consideration. Once the podling is going, then I would suggest they figure out what to do. For example, they may want to transfer the OOo bugzilla content over here. Infra could set up a BZ instance for the podling and load it with the old content. That's probably some heavy lifting for a few people, but quite doable. It would provide some continuity for bug numbers, and the history. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Dcument automation with ODF (was Re: Request: Can proposed committers introduce themselves?)
dsh daniel.hais...@googlemail.com wrote on 06/08/2011 12:15:52 PM: Of course we had been using ODFDOM but the issue is how do you get ODF transformed accordingly to other formats such as RTF, AFP or PDF and make those formats look consistent with what you would get if doing the transformation natively during design time in OO or Symphony. I think your observation is correct. The ODF Toolkit does not currently have a good way of generating print or print equivalent output from an ODF document. The Toolkit had no layout or rendering support. But I wonder if this is something that Apache FOP could help solve? The styling vocabulary of ODF is loosely borrowed from XSL Formatting Objects (XSL:FO). It may be possible to generate XSL:FO from ODF much more easily than converting from ODF to PDF or Postscript directly. But once we have the XSL:FO intermediary, then the pipeline could continue with Apache FOP to target formats ranging from PDF to raster images. Does that sound plausible? Someone needs to do the layout and rendering. But I hate to see that code written more than once. The ODF-XSL:FO conversion would be a great toolkit enhancement. Has POI done this with the Microsoft formats? -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: Add incubator group to podling committers
On 8 June 2011 07:47, Christian Grobmeier grobme...@gmail.com wrote:
Can the people below be added to the incubator group so they can
update the ONGL website? I have hear our inc-chair is ooo (wow, that
acronym got somehow hijiacked in this list) - do we have a deputy
handling it?
Thirty-six other people on the Incubator PMC have sufficient karma:
Thanks. But could you briefly explain how this knowledge can help me?
I mean, I am willing to do it myself, if I just know if I can or how.
No, apart from infra, only pmc-chairs have the karma to update such LDAP groups
The full list of members is here:
http://people.apache.org/committers-by-project.html#pmc-chairs
[[[
% cat ./count-ipmc-chairs.zsh
#!/usr/bin/env zsh
f() {
ldapsearch -LLL cn=$1 member | grep ^member: | sort
}
comm -12 =(f incubator) =(f pmc-chairs) | wc -l
% ./count-ipmcchairs.zsh
37
]]]
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
http://www.grobmeier.de
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Upstream/Downstream (was OpenOffice LibreOffice)
Hi, can we please just end this futile discussion? I agree, that water flows one direction only. But there needs to be water first to flow in any direction. If there will be enough to establish a flow, can only be seen, once the podling is in place. The risk estimation (will the podling run dry?) is up to Apache. regards, André - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Dcument automation with ODF (was Re: Request: Can proposed committers introduce themselves?)
Actually I evaluated XSL-FO rendering engines quite excessively including Apache FOP. At that point in time (2009) Apache FOP still had performance issues in scenarios where you would generate thousands of business correspondence documents to be sent to clients on a daily basis. In the end we decided to go with a commercial XSL-FO rendering engine vendor where we had been using Apache FOP initially. Additionally at that point in time the most recent Apache FOP version did not have an open source approval which is of course an IBM-internal detail. The reason why we picked a commercial XSL-FO rendering engine was it's stability, some proof records such as clients already using this particular commercial XSL-FO rendering engine and it's feature richness such as AFP and 2D barcode (e.g. data matrix) support which is essential if you want to directly print to commercial printers. IIRC besides those issues one issue that probably applies to any XSL-FO rendering engine at least to a certain degree is that depending on how much time you spend on the XSL stylesheet it might be pretty expensive (in terms of man hours) to reassemble the layout of the original ODF document in the PDF document (e.g. the final document generated during runtime does not look the same to what has been defined by the business user during design time either using Symphony or OO). Hence my statement that it would have been nice if the core Symphony/OO ODF-PDF transformation would have been available as a separate library/module which could have been run on the server (AIX or z/OS). That way the business user would have been using the same transformation engine as the one used on the backend. These days, if I would be in a position to redo the design I would be tempted to figure out whether the whole transformation process could be off-loaded to a self-contained appliance such as datapower XA35 or even XI50. The datapower blade extension unit would even offer to off-load MIPS from the mainframe, something that illustrates that efficient ODF transformation is key in commercial environments where MIPS are expensive. But anyway I guess this scenario is a pretty advanced scenario cause it involves a distributed server infrastructure and a business application that generates large amounts of either PDF or AFP documents on a daily basis. Cheers Daniel On Wed, Jun 8, 2011 at 6:51 PM, robert_w...@us.ibm.com wrote: dsh daniel.hais...@googlemail.com wrote on 06/08/2011 12:15:52 PM: Of course we had been using ODFDOM but the issue is how do you get ODF transformed accordingly to other formats such as RTF, AFP or PDF and make those formats look consistent with what you would get if doing the transformation natively during design time in OO or Symphony. I think your observation is correct. The ODF Toolkit does not currently have a good way of generating print or print equivalent output from an ODF document. The Toolkit had no layout or rendering support. But I wonder if this is something that Apache FOP could help solve? The styling vocabulary of ODF is loosely borrowed from XSL Formatting Objects (XSL:FO). It may be possible to generate XSL:FO from ODF much more easily than converting from ODF to PDF or Postscript directly. But once we have the XSL:FO intermediary, then the pipeline could continue with Apache FOP to target formats ranging from PDF to raster images. Does that sound plausible? Someone needs to do the layout and rendering. But I hate to see that code written more than once. The ODF-XSL:FO conversion would be a great toolkit enhancement. Has POI done this with the Microsoft formats? -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Sqoop for Incubation
+1 On Wed, Jun 8, 2011 at 9:32 AM, Tom White tomwh...@apache.org wrote: +1 Tom On Tue, Jun 7, 2011 at 8:39 PM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Eric Sammer twitter: esammer data: www.cloudera.com
Re: [VOTE] Flume to join the Incubator.
+1 On Tue, Jun 7, 2011 at 9:38 PM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was initially developed by Jonathan Hsieh in July 2009 along with development team at Cloudera. Developers external to Cloudera provided
Re: Document automation with ODF (was Re: Request: Can proposed committers introduce themselves?)
Of course we had been using ODFDOM but the issue is how do you get ODF transformed accordingly to other formats such as RTF, AFP or PDF and make those formats look consistent with what you would get if doing the transformation natively during design time in OO or Symphony. I think your observation is correct. The ODF Toolkit does not currently have a good way of generating print or print equivalent output from an ODF document. The Toolkit had no layout or rendering support. But I wonder if this is something that Apache FOP could help solve? The styling vocabulary of ODF is loosely borrowed from XSL Formatting Objects (XSL:FO). It may be possible to generate XSL:FO from ODF much more easily than converting from ODF to PDF or Postscript directly. But once we have the XSL:FO intermediary, then the pipeline could continue with Apache FOP to target formats ranging from PDF to raster images. Does that sound plausible? Someone needs to do the layout and rendering. But I hate to see that code written more than once. The ODF-XSL:FO conversion would be a great toolkit enhancement. Has POI done this with the Microsoft formats? POI is more about reading, writing and calculating than it is about rendering. Users come to the list with questions about it, usually to HTML, and we help. In POI Excel is much better covered. Lately Word has finally been getting some attention. Yegor and I have experimented outside the POI project with PPT2PS (and PDF) conversion so that we can make use of slides in our postscript workflow. We have been using some EPS generated by OOo for this, but likely due to the font embedding issues that Robert referenced earlier these EPS have the text rendered as shapes which is awful looking because font anti-aliasing is gone ... big fat lowercase l etc for Arial of all things. One trouble with the FOP approach is that layout and rendering of tricky features is pushed even farther away from OOo. Not knowing the details, but knowing rendering and layout, there must certainly be code to do it in OOo. I would want to follow that - it is what the ODF toolkit ought to use from the core. Maybe the trouble with that approach is that the rendering there is too tied in with GUI considerations? IIRC - FOP like POI can suffer from the need to have the whole DOM in memory. If you have ever built a 6000 page PDF ... We have thought of using PDFBox... I think until we figure out where the rendering and layout should come from, the ODF Toolkit should be included as part of the Apache OOo podling. If the community decides it needs separate incubation that's fine. Exploring these trade-offs scientifically is what's needed - in the podling. I need to stop reading these emails and start reading the OOo site and looking at code. Now back to work... Best Regards, Dave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Add incubator group to podling committers
Christian Grobmeier wrote: I sent this to infra, but I have been told the incubator chair should handle this. I've made the changes via the command line interface. I wish there were some consistency on this when accounts are setup, but that's something we can discuss with infra. Oft-times when I have gone to change group membership, I have had the command line tool complain that the id is already in the group. And until it was fixed, that complaint caused the entire modification to fail for all ids. I have hear our inc-chair is ooo Out of Office? Naw. As long as I have decent Internet access (and no firewall keeping me from SSH), I'm in the office. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Add incubator group to podling committers
I sent this to infra, but I have been told the incubator chair should handle this. I've made the changes via the command line interface. Thank you very much Noel! I have hear our inc-chair is ooo Out of Office? Naw. As long as I have decent Internet access (and no firewall keeping me from SSH), I'm in the office. And I was even pretty sure somebody said you were on honeymoon - definitely too much e-mails the past days. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Re-Introduction
On Tue, Jun 7, 2011 at 4:49 PM, Volker Merschmann merschm...@gmail.com wrote: 2011/6/7 Ian Lynch ianrly...@gmail.com: On 7 June 2011 16:27, Volker Merschmann merschm...@gmail.com wrote: 2011/6/7 Ian Lynch ianrly...@gmail.com: On 7 June 2011 16:08, Volker Merschmann merschm...@gmail.com wrote: snip Apache is community centered with an open culture. Please encourage as many people as possible to come together to contribute their ideas into the mix. You shoul not expect too much, as all non-Oracle-employed council-members have left the council last year and the seats had not been re-elected... The Council wasn't the sum total of everyone, already a lot of non-Oracle people are on the commit list and people who were never on a Council no reason not to include TDF members too. Let's be inclusive and positive, this is new opportunities and new horizons :-) Oh, you shouldn't misinterpret me. Robert asked for this in connection with the mention of the OOo community council, which does not have community in it, nor can it fully represent it. That was my point. No negatives about the Apache thing here. Maybe you were misinterpreting Robert then :-) All he said was encourage as many people as possible. Certainly he didn't say *only* people at the meeting. They will have contacts. Touché ? ;-) That's it with the nonverbal communication, you can not never get the right meaning without hearing it. (my broad yorkshire might make you reconsider that ;-) I intended to aim my encouragement at the world I came up a little short Thanks to the community for jumping in and correcting my mistakes :-) Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A lot of bodies, a lot of money, and a source-dump release.
Hello, Niall, On Tue, Jun 07, 2011 at 10:11:02AM +0100, Niall Pemberton wrote: If you're right about the costs, they not going to hit from day one - as the initial effort will be in building the community and building something that can be released and very little needed in terms of end users - and the ASF has more than enough resources to cope with that. The ASF has IMO a great track record in fund raising and is not without resources (see the latest treasurers report[1]) and if this project succeeds here I wouldn't be surprised to see its success bring in an increase in ASF funding. If the project failed, then I also doubt that we would have incurred that much expenditure. Having read your reply, the other replies on this thread, the subsequent threads exploring impact on infrastructure and other ASF resources, and seeing the large ASF contingent signed up as both committers and Mentors, I'm persuaded that the resources are available, the problems are solvable, and that the podling can work out the details. Needing a large community, being able to cope with an IBM pullout releasing lots of binaries are all things this project would need to demonstrate they can deal with before graduating. If they can't then they wouldn't become an official ASF project. It's also been great to see so many people with deep knowledge of the project from diverse organizations introducing themselves -- including multiple employees of Oracle. Between all those developments and the clarifications from Andrew Rist regarding the software grant, I can't imagine opposing this proposal any longer. Looking forward to the vote thread... Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Add incubator group to podling committers
Christian Grobmeier wrote: Out of Office? Naw. As long as I have decent Internet access (and no firewall keeping me from SSH), I'm in the office. And I was even pretty sure somebody said you were on honeymoon - No, we actually haven't had time for other than a couple of get-away weekends, so far. definitely too much e-mails the past days. Yes. Lots of mail getting swamped by the OOo discussion. Even knowing that your e-mail was here, I had to do a search to find it. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [tdf-discuss] OpenOffice.org Summit Proposal
Hi, I almost forgot about that, as it is not a summit but may be the earliest date for a meeting. http://wiki.documentfoundation.org/DE/QAWochenende2011 So if some of you live rather close to Essen/Germany you may join us there. It would be helpfull to understand / speak German, as it is a meeting of the German community members. We used to have this as annual meeting with focus on QA and localization for some years now. But it is always a nice event to get to know each other, have barbecue, pizza and beer (or whatever you like ;) ) If you like to join, please notify Jacqueline and prefferable disc...@de.libreoffice.org. There are still some places left to stay overnight (but please be aware the we only have double rooms). regards, André PS.: - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice Proposal: Nominated Mentors
On Fri, Jun 3, 2011 at 9:49 PM, robert_w...@us.ibm.com wrote: This is for the proposal, the Nominated Mentors section. My observation, after seeing the topics that seem to be getting the most attention from the IPMC members on this list, is that in the the Podling we will want to pay special attention to: - IP review and remediation, due to the known presence of non-Apache code dependencies - Apache infrastructure, due to sheer size of the project, as well as the desire to have both project-facing and public facing web portals - Build management, due to the resources needed to build and the multiple platforms needed to build and test with - Community development, due to the need to develop and coordinate/collaborate with current and anticipated downstream consumers of the project, as well as potentially forging bi-directional collaborations. These, to me, seem to be areas we want to focus on. I apologize in advance if it is out of place for me to be asking this, but I think that with a project of this size, complexity, visibility, and shall we say drama, we would benefit from having incubation mentors with noted strength in these areas. I'd like to encourage everyone and anyone with opinions and ideas to post them - the world, or at least as much as can fit onto this list We currently are listing Jim and Sam as project mentors. This is an excellent start. But if say, another 2 or so IPMC members who have complementary strengths in one or more of the above areas, I'd welcome their assistance. That would allow us to work some of these areas in parallel with each other, and in parallel with other incubation tasks, without being too much of an imposition for any single mentor. Mentoring is a hands off, facilitation role IMO the downstream ecosystem and community needs to be sustained with continuity and speed in fixing the potential legal, infrastructure and build issues. This needs hands on help from developers with expertise from within the Apache community for a transitional sprint whilst the wider ecosystem and community is establishing itself. Does the IPMC need to consider calling for this? Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice - Wiki - Required Resources - Subversion vs. Mercurial vs. Git
On Sun, Jun 5, 2011 at 6:11 PM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I say that the sooner one can move to uni-directional flows with the bi-directionals out in customization and adoption layers, if anywhere, the better. It is difficult to conceive of any other way to get on top of the refactoring that is surely required as part of making a manageable, layered component structure. +1 Yes, I know this is simplistic in the face of the reality of OpenOffice.org. I maintain that such a separation of concerns should be sought. That to some degree the problem of multi-platform distribution, localization, etc., has already been taken on by at least one another provides some important breathing room. +1 Encouraging rich and diverse downstream ecology is essential. This means allowing space for downstream entities step into the supply chain. Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
On Tue, Jun 7, 2011 at 8:43 PM, Danese Cooper dan...@gmail.com wrote: We at Apache don't think that money is evil, but we also believe that seeing our code in wide use is more important than money. OpenOffice.org is important to the Developing World, some of whom will pay for convenience. I would hate to see Apache enter that business, however. +1 Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice Proposal: Nominated Mentors
Robert Weir wrote: - Community development, due to the need to develop and coordinate/collaborate with current and anticipated downstream consumers of the project, as well as potentially forging bi-directional collaborations. we would benefit from having incubation mentors with noted strength in these areas. if say, another 2 or so IPMC members who have complementary strengths in one or more of the above areas, I'd welcome their assistance. If she's amenable, perhaps Danese Cooper? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Res: Re: OpenOffice.org Summit Proposal
I finally had access to the edit function and updated the wiki. Thanks everyone for the support :) Best, Jomar -Original Message- From: Danese Cooper dan...@gmail.com Date: Tue, 7 Jun 2011 17:20:38 To: general@incubator.apache.orggeneral@incubator.apache.org Reply-To: general@incubator.apache.org Cc: general@incubator.apache.orggeneral@incubator.apache.org Subject: Re: OpenOffice.org Summit Proposal Jomar, I had to verify my email address, then log back in to activate the edit token. Gotta love them wikis ;-p. D On Jun 7, 2011, at 4:01 PM, Jomar Silva (Cuca) homem...@gmail.com wrote: Yep... but even logged in I couldn't edit it... I'm from the third world, you know :) Jomar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice Proposal: Nominated Mentors
On Jun 8, 2011, at 2:33 PM, Noel J. Bergman wrote: Robert Weir wrote: - Community development, due to the need to develop and coordinate/collaborate with current and anticipated downstream consumers of the project, as well as potentially forging bi-directional collaborations. we would benefit from having incubation mentors with noted strength in these areas. if say, another 2 or so IPMC members who have complementary strengths in one or more of the above areas, I'd welcome their assistance. If she's amenable, perhaps Danese Cooper? --- Noel The current list: • Jim Jagielski • Sam Ruby • Danese Cooper • Shane Curcuru • Nóirín Plunkett • Joe Schaefer • Christian Grobmeier • Ross Gardler - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
On Tue, Jun 7, 2011 at 10:45 AM, Christian Grobmeier grobme...@gmail.comwrote: Danese, 3) LOTS of people download OOo Like maybe 10% of the human population of the planet. And its a big file. Initially we engaged Akamai, but it quickly became too expensive. Serving up downloads of OOo was pretty intense. I know Apache has all that web server download traffic and all...but I'm telling you Sun.com quailed at the throughput, and we shouldn't assume our mileage will vary. There will be extraordinary infrastructure costs, because it is end-user software (and there are a LOT of users worldwide). Sun mitigated this problem with mirrors, but of course that screwed download stats. do you have any numbers? I am really curious - people are always saying that but I cannot get out numbers. I believe all you said, I just would like to know how much it is actually Thanks for the interesting read - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org OOo used brainstats, and you can get some numbers. There was 'some' number crunching but that project wasn't updated as usual: http://stats.openoffice.org/ We used bouncer also as a analytics type system here: http://marketing.openoffice.org/marketing_bouncer.html The Mirrobrain-OOo FAQ is also encourage to read. http://marketing.openoffice.org/marketing_bouncer_faq.html -- *Alexandro Colorado* *OpenOffice.org* Español http://es.openoffice.org
Openoffice.org
The expectation, assumption and intent behind the grant was that Openoffice.org would also be granted. In many, many ways, this trademark is just as important, if not more so, than the actual code for the success of the podling. Have we rec'd the updated grant yet? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openoffice.org
Nothing else has been received from Oracle. You will be the third person to know. ;-) Craig On Jun 8, 2011, at 12:58 PM, Jim Jagielski wrote: The expectation, assumption and intent behind the grant was that Openoffice.org would also be granted. In many, many ways, this trademark is just as important, if not more so, than the actual code for the success of the podling. Have we rec'd the updated grant yet? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Code covered by the Oracle grant
On 07/06/2011 Andrew Rist wrote: We are trying to provide all of the Oracle owned content in the OOo repositories. As a longtime OpenOffice.org volunteer (mini-introduction: involved with the OpenOffice.org project since 2003, main contributions in QA, Localization and QA Tools, Italian Project Lead since 2005) I'm happy to see Oracle finally answering questions on public lists. May I ask for a last clarification on the code covered by the Oracle grant? Some observers, like the Document Foundation [1] and Bradley Kuhn [2], seem to imply that the grant will also turn some proprietary software (components exclusive to StarOffice - Oracle Open Office perhaps? Or Oracle Cloud Office?) into free software: is this the case or, as it seems from the provided file list, all the code covered by the grant is already available as free (LGPL3) software? [1] http://blog.documentfoundation.org/2011/06/01/statement-about-oracles-move-to-donate-openoffice-org-assets-to-the-apache-foundation/ [2] http://ebb.org/bkuhn/blog/2011/06/01/open-office.html Regards, Andrea Pescetti. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A little OOo history
I just checked with my Brazilian friends involved with the BrOffice project in the past years, and it seems that all problems that we've had in the past with the OpenOffice.org trademark are now solved. Best, Jomar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
Richard S. Hall wrote (08-06-11 11:03) On 06/08/2011 04:16 AM, Christian Lippka wrote: Moin Moin [1], my name is Christian Lippka and I work on the donnated code base since 1998 [..] I just wanted to say that this is one of the best messages I've read throughout this entire ordeal. Thanks. Yip - thanks Christian :-) -- - Cor - http://nl.libreoffice.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Code covered by the Oracle grant
I'll quote my earlier answer [1] on that: Our approach is to start with the main open source code - stuff with clear provenance. The OOo extensions are more complex in terms of licensing and other issues, but this is certainly something to revisit at a later stage of the project. (acknowledged - that was several hundred messages ago) On 6/8/2011 1:41 PM, Andrea Pescetti wrote: May I ask for a last clarification on the code covered by the Oracle grant? Some observers, like the Document Foundation [1] and Bradley Kuhn [2], seem to imply that the grant will also turn some proprietary software (components exclusive to StarOffice - Oracle Open Office perhaps? Or Oracle Cloud Office?) into free software: is this the case or, as it seems from the provided file list, all the code covered by the grant is already available as free (LGPL3) software? [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3c4de9bd98.3050...@oracle.com%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Code covered by the Oracle grant
Andrew Rist wrote: I'll quote my earlier answer [1] on that: Our approach is to start with the main open source code - stuff with clear provenance. The OOo extensions are more complex in terms of licensing and other issues, but this is certainly something to revisit at a later stage of the project. (acknowledged - that was several hundred messages ago) Thanks for the confirmation. I had indeed read this message and all the several hundreds in between, but it seemed important enough to ask explicitly again, especially considering that those statements haven't been corrected and that the Oracle proprietary bits surely qualify for the clear provenance, so making them free software should not pose particular problems. Regards, Andrea. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
OOo Monetary Donations
I started looking around at the OOo website. I'm not sure if now is the time to bring this up, but at http://contributing.openoffice.org/donate.html there is a solicitation for funds via three processes. Here's what the page says: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Please discuss the tax benefits of donating with your accountant. You can make a donation to our primary treasury, Team OpenOffice.org, e.V. via PayPal or credit card or use bank transfer. Or, if you prefer to donate US dolars (USD) via credit card, cheque or money order, you can use use Software In the Public Interest, Inc. (SPI), and simply identify the recipient project, OpenOffice.org, where indicataed in the instructions SPI provides: SPI Donations for OpenOffice.org . (SPI does not accept PayPal or wire transfers.) Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... Regards, Dave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OOo Monetary Donations
Dave Fisher wrote: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... Well ... that's an interesting question. While hiring could happen outside of the ASF, AFAIK there is nothing to stop us from accepting funds and having a group (analogous to our Travel Assistance process) that offered payment, a la Google Code or other. I do agree that I'd like to see the Board and Membership weigh in on that discussion if/when it ever becomes one. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
On 8 June 2011 22:50, Noel J. Bergman n...@devtech.com wrote: Dave Fisher wrote: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... Well ... that's an interesting question. While hiring could happen outside of the ASF, AFAIK there is nothing to stop us from accepting funds and having a group (analogous to our Travel Assistance process) that offered payment, a la Google Code or other. I do agree that I'd like to see the Board and Membership weigh in on that discussion if/when it ever becomes one. Presumably it would also be possible to have a group outside ASF called eg Friends of Open Office ( FOO) that raised money and put it to code development or marketing or whatever. Not saying that is the best way just its a possibility. -- Ian Ofqual Accredited IT Qualifications (The Schools ITQ) www.theINGOTs.org +44 (0)1827 305940 The Learning Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79 8AQ. Reg No: 05560797, Registered in England and Wales.
RE: Add incubator group to podling committers
-Original Message- From: Noel J. Bergman [mailto:n...@devtech.com] Sent: Thursday, 9 June 2011 3:51 AM To: general@incubator.apache.org Subject: RE: Add incubator group to podling committers Christian Grobmeier wrote: I sent this to infra, but I have been told the incubator chair should handle this. I've made the changes via the command line interface. I wish there were some consistency on this when accounts are setup, but that's something we can discuss with infra. Oft-times when I have gone to change group membership, I have had the command line tool complain that the id is already in the group. And until it was fixed, that complaint caused the entire modification to fail for all ids. Hopefully you'll have noticed that was fixed couple of months ago. Gav... I have hear our inc-chair is ooo Out of Office? Naw. As long as I have decent Internet access (and no firewall keeping me from SSH), I'm in the office. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
On Wed, Jun 8, 2011 at 11:08 PM, Ian Lynch ianrly...@gmail.com wrote: On 8 June 2011 22:50, Noel J. Bergman n...@devtech.com wrote: Dave Fisher wrote: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... Well ... that's an interesting question. While hiring could happen outside of the ASF, AFAIK there is nothing to stop us from accepting funds and having a group (analogous to our Travel Assistance process) that offered payment, a la Google Code or other. I do agree that I'd like to see the Board and Membership weigh in on that discussion if/when it ever becomes one. Presumably it would also be possible to have a group outside ASF called eg Friends of Open Office ( FOO) that raised money and put it to code development or marketing or whatever. Not saying that is the best way just its a possibility. Doesn't one of those already exist? S.
Re: OOo Monetary Donations
Simon Phipps wrote: On Wed, Jun 8, 2011 at 11:08 PM, Ian Lynchianrly...@gmail.com wrote: On 8 June 2011 22:50, Noel J. Bergmann...@devtech.com wrote: Dave Fisher wrote: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... Well ... that's an interesting question. While hiring could happen outside of the ASF, AFAIK there is nothing to stop us from accepting funds and having a group (analogous to our Travel Assistance process) that offered payment, a la Google Code or other. I do agree that I'd like to see the Board and Membership weigh in on that discussion if/when it ever becomes one. Presumably it would also be possible to have a group outside ASF called eg Friends of Open Office ( FOO) that raised money and put it to code development or marketing or whatever. Not saying that is the best way just its a possibility. Doesn't one of those already exist? S. I think your referring to Friends of OpenDocument INC, based out of Queensland Australia. See http://www.friendsofopendocument.com/newsite/ . Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
Indeed, the ASF has been consistent that monetary donations be made to the ASF as a whole, and we have not accepted targeted cash donations for specific projects in the past. And as a Foundation, we have not paid directly for development on our projects (although obviously we have a paid sysadmin staff, as well as paying for our significant hardware and bandwidth needs, etc.) Guidelines for individual contributions: http://www.apache.org/foundation/contributing.html Guidelines for recurring larger contributions: http://www.apache.org/foundation/sponsorship.html - Shane Dave Fisher wrote: I started looking around at the OOo website. I'm not sure if now is the time to bring this up, but at http://contributing.openoffice.org/donate.html there is a solicitation for funds via three processes. Here's what the page says: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Please discuss the tax benefits of donating with your accountant. You can make a donation to our primary treasury, Team OpenOffice.org, e.V. via PayPal or credit card or use bank transfer. Or, if you prefer to donate US dolars (USD) via credit card, cheque or money order, you can use use Software In the Public Interest, Inc. (SPI), and simply identify the recipient project, OpenOffice.org, where indicataed in the instructions SPI provides: SPI Donations for OpenOffice.org . (SPI does not accept PayPal or wire transfers.) Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... Regards, Dave - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
On Jun 8, 2011, at 4:31 PM, Dave Fisher wrote: I started looking around at the OOo website. I'm not sure if now is the time to bring this up, but at http://contributing.openoffice.org/donate.html there is a solicitation for funds via three processes. Here's what the page says: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Please discuss the tax benefits of donating with your accountant. You can make a donation to our primary treasury, Team OpenOffice.org, e.V. via PayPal or credit card or use bank transfer. Or, if you prefer to donate US dolars (USD) via credit card, cheque or money order, you can use use Software In the Public Interest, Inc. (SPI), and simply identify the recipient project, OpenOffice.org, where indicataed in the instructions SPI provides: SPI Donations for OpenOffice.org . (SPI does not accept PayPal or wire transfers.) Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... btw, where do those funds go now?? I'm guessing some sort of escrow account held by Oracle? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
to a foundation independent of Oracle: Team OpenOffice.org e.V. searching for a more complete answer Oracle Email Signature Logo Andrew Rist | Interoperability Architect Oracle Corporate Architecture Group Redwood Shores, CA | 650.506.9847 On 6/8/2011 4:19 PM, Jim Jagielski wrote: On Jun 8, 2011, at 4:31 PM, Dave Fisher wrote: I started looking around at the OOo website. I'm not sure if now is the time to bring this up, but at http://contributing.openoffice.org/donate.html there is a solicitation for funds via three processes. Here's what the page says: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Please discuss the tax benefits of donating with your accountant. You can make a donation to our primary treasury, Team OpenOffice.org, e.V. via PayPal or credit card or use bank transfer. Or, if you prefer to donate US dolars (USD) via credit card, cheque or money order, you can use use Software In the Public Interest, Inc. (SPI), and simply identify the recipient project, OpenOffice.org, where indicataed in the instructions SPI provides: SPI Donations for OpenOffice.org . (SPI does not accept PayPal or wire transfers.) Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... btw, where do those funds go now?? I'm guessing some sort of escrow account held by Oracle? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
http://www.teamopenoffice.de/ I believe it is at the disposal of the Community Council, so probably Louis could give a more complete answer. S. On Thu, Jun 9, 2011 at 12:24 AM, Andrew Rist andrew.r...@oracle.com wrote: to a foundation independent of Oracle: Team OpenOffice.org e.V. searching for a more complete answer Oracle Email Signature Logo Andrew Rist | Interoperability Architect Oracle Corporate Architecture Group Redwood Shores, CA | 650.506.9847 On 6/8/2011 4:19 PM, Jim Jagielski wrote: On Jun 8, 2011, at 4:31 PM, Dave Fisher wrote: I started looking around at the OOo website. I'm not sure if now is the time to bring this up, but at http://contributing.openoffice.org/donate.html there is a solicitation for funds via three processes. Here's what the page says: Your donation will go directly towards helping this project. Some of the ways in which your funds might be used include: • Hiring independent developers to work with OpenOffice.org. • Paying for participation at trade shows and conferences. • Paying for organization and staff at annual OpenOffice.org Conference, OOoCon. • Marketing banners, collateral, CDs and brochures. Please discuss the tax benefits of donating with your accountant. You can make a donation to our primary treasury, Team OpenOffice.org, e.V. via PayPal or credit card or use bank transfer. Or, if you prefer to donate US dolars (USD) via credit card, cheque or money order, you can use use Software In the Public Interest, Inc. (SPI), and simply identify the recipient project, OpenOffice.org, where indicataed in the instructions SPI provides: SPI Donations for OpenOffice.org . (SPI does not accept PayPal or wire transfers.) Clearly there ought to be changes to the page and process when/if the podling happens. This is probably at the ASF Board level... certainly the hiring developers part doesn't fit... btw, where do those funds go now?? I'm guessing some sort of escrow account held by Oracle? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Simon Phipps +1 415 683 7660 : www.webmink.com
Re: OOo Monetary Donations
Andrew Rist wrote: to a foundation independent of Oracle: Team OpenOffice.org e.V. searching for a more complete answer It would be interesting to find out if all funds received for OOo were accounted for since the fork. The e.V changed names and collects donations for LibreOffice, http://www.documentfoundation.org/contribution/ . Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OOo Monetary Donations
Simon Phipps si...@webmink.com wrote on 06/08/2011 06:44:35 PM: I was actually thinking of Freies Office Deutschland e.V. primarily, http://www.frodev.org/ Interesting. That happens to also be where TDF donations go: http://www.documentfoundation.org/contribution/ -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
