Request ASF assistance to reform XALAN PMC
To The Incubator: Bertrand Delacretaz has indicated that XALAN_C is a candidate for moving to the attic. I would like to see XALAN moved to the Incubator instead of the attic. I will help reinstate the XALAN PMC but need some ASF assistance. I am not currently an ASF member, but I am willing to become a member and a contributor for the purpose of advancing the XALAN projects. I am willing to mentor the XALAN-C project and prepare project releases. I am willing to help reform the XALAN PMC and report to the ASF and appropriate PMCs on XALAN project status. You already have my ASF committer's license agreement on file, but there are insufficient active members in the XALAN PMC to nominate or approve of new membership. I have extensive background in technical writing and publishing. I also have significant expertise in systems programming and network communications programming (over 40 years). If you need my resume information, just ask! The following persons have submitted information to the xalan-...@apache.org mail list in the last few months. There may be enough persons available to reform the XALAN PMC if membership and committer credentials can be authorized. I hope the ASF board can help with this. I monitor the mail lists: xalan-...@xml.apache.org and xalan-c-us...@xml.apache.org. Sincerely, Steven J. Hathaway shath...@e-z.net steven.j.hatha...@state.or.us --- Bertrand Delacretaz bdelacre...@apache.org Incubator PMC David Bertoni dbert...@apache.org XALAN PMC Chair Steven J Hathaway steven.j.hatha...@state.or.us Steven J Hathaway shath...@e-z.net Oregon State Police - Systems Analyst Former: Tektronix, Inc - Technical Writer Consultant - to Unisys Corp. Michael Glavassevich mrgla...@apache.org Michael Glavassevich mrgla...@ca.ibm.com XML Parser Development IBM Toronto Lab Harsh Gupta har...@adobe.com XALAN User Victor Wang wangqu.aguai.2...@gmail.com Google Summer of Code project - XSLT 2.0 and XPath 2.0 for Xalan http://www.google.melange.com/gsoc/project/google/gsoc2011/aguai/9003 Xun Long Gui ustbco...@gmail.com Mentor for GSoC project - XSLT 2.0 and XPath 2.0 for Xalan Jesper Steen Maller jes...@selskabet.org PsychoPath code tree information Mark Thomas markt jira-users Resolving XALAN-C issues Apache Tomcat project - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Bluesky status and plans (was: Monthly reports missing)
On Tue, Jun 14, 2011 at 1:48 PM, Sam Ruby ru...@intertwingly.net wrote: On Tue, Jun 14, 2011 at 12:58 AM, Noel J. Bergman n...@devtech.com wrote: I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. Bluesky entered incubation nearly three and half years ago. It is time to decide that incubation is not going to succeed for this podling? I think so: no commits, almost no relevant discussion on the dev list, and mentors don't seem to be really active. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
On Mon, Jun 13, 2011 at 9:26 PM, Tom White tomwh...@apache.org wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. I'd like to join as a committer and mentor. -- Owen
[CANCELED] Re: [VOTE] Release Droids 0.1-incubating RC2
On 06/11/2011 10:43 PM, Richard Frovarp wrote: Please vote on the release cndidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 2 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201106.mbox/%3c4de7d6cc.8080...@apache.org%3E Source files: http://people.apache.org/~rfrovarp/droids/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachedroids-011/ SVN source tag (r1127762): https://svn.apache.org/repos/asf/incubator/droids/tags/0.1-incubating/ PGP release keys (signed using 3698A2B1): https://svn.apache.org/repos/asf/incubator/droids/KEYS [ ] +1 [ ] +0 [ ] -1 Thanks, Richard This vote has been canceled due to identification of blocking issues. They will be fixed and a new build will be made shortly. Thanks to those that helped. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On 06/15/2011 04:39 PM, Marvin Humphrey wrote: On Tue, Jun 14, 2011 at 09:35:05PM -0500, Richard Frovarp wrote: There should be archived VOTE threads on the droids-private list, which were cc'd to private@incubator.a.o. Hopefully they were for PPMC membership. If not, there will be some cleanup work to do. The votes were handled on the droids-dev list (like they should) and were committer votes. So Bertil and I aren't on the PPMC. OK... In my opinion, the intent of the community to make this release is perfectly clear. None of the people who are officially on the PPMC objected to it, nor did anyone raise any concerns about the validity of votes from Committers who aren't on the PPMC. In general, votes can come from anyone, so votes from people that aren't on the PMC shouldn't be discouraged. In a previous vote, Ross did tell me if I needed more binding votes, to come here. However, it looks as though Droids isn't *bundling* either JUnit or javax.servlet, in either in source or binary form -- you're expecting Maven to resolve and install the dependency. Therefore, I don't believe it's required to include the license texts which apply to those components. I'm not even sure whether you even need attributions in NOTICE.txt for components you aren't bundling. As best I can tell, the Droids distro archive does not contain either source or binary materials belonging to or derived from either JUnit or javax.servlet IP. In summary, unless someone corrects my interpretation, LICENSE.txt is fine and NOTICE.txt has some info which is arguably superfluous, but the presence of that extra info does not block the release. I consider the matter provisionally resolved. Sebb seems to agree with your interpretation. I have fixed the files to remove any notices to anything, except for the standard ASF notice. License only include AL2. I was unclear on this, as you can't have runtime required dependencies on category X items. A project can't require Hibernate (LGPL) and claim that it is okay because Apache Maven is bringing in the dependency. It was not clear to me how category-B should be handled. Consensus is to say nothing if it isn't being bundled, so everything has been removed. OK. In my rush, I hadn't noticed that the Maven-generated NOTICE file was just a stub rather than a substantially different version of NOTICE.txt. It's still inaccurate because it's incomplete, though: Droids Copyright 2007-2011 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). I've renamed NOTICE.txt to NOTICE and have updated all the references in the poms to Apache Droids, instead of just Droids. This should insure that future packages have the correct information. Yep. I double checked and RAT only flags that silly DEPENDENCIES file. License headers look good! Excellent. Thanks. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On 06/15/2011 08:47 PM, sebb wrote: On 12 June 2011 04:43, Richard Frovarprfrov...@apache.org wrote: Please vote on the release cndidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 2 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201106.mbox/%3c4de7d6cc.8080...@apache.org%3E Source files: http://people.apache.org/~rfrovarp/droids/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachedroids-011/ SVN source tag (r1127762): https://svn.apache.org/repos/asf/incubator/droids/tags/0.1-incubating/ PGP release keys (signed using 3698A2B1): https://svn.apache.org/repos/asf/incubator/droids/KEYS [ ] +1 [ ] +0 [ ] -1 There must be a disclaimer saying that the project is undergoing Incubation. This is normally in a DISCLAIMER file, which should be in SVN, source and binary archives. Added. The website should also carry a prominent disclaimer, nromally at the start of the index page. Will have someone work on that. The NOTICE file must only contain required notices, and only for items that are actually included in the release, not run-time dependencies that are downloaded by Maven. E.g. is JUnit included in the release? If not, remove the reference. Do not add any extraneous text to the Notice file - e.g explanations and headings - it should be as short as possible (but no shorter). Done. The project name should be shown as Apache Droids in the Notice file(s). Fixed as well. I think the above all need to be fixed before release. The source archive contents agree with SVN (apart from extra files generated by Maven). Sigs and hashes are OK; key is in public PGP repo. Contents of jar files look good; there are NL files in the META-INF dir. The source and javadoc jar manifests could include the Specification entries. I don't know that I completely understand this. I'm not too familiar with the manifest files, and adding specification into a search returns back the specs on the file format. It would be useful to include the Java source and target versions in the binary jar manifests. Will do. The SVN properties don't appear to have been set on many of the source files, which suggests that some committers have not set up their SVN defaults correctly. (I'll raise a JIRA for correcting the properties) Applied / fixed. Thanks. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
Owen, Thanks for offering to help out. Cheers, Tom On Thu, Jun 16, 2011 at 7:13 AM, Owen O'Malley omal...@apache.org wrote: On Mon, Jun 13, 2011 at 9:26 PM, Tom White tomwh...@apache.org wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. I'd like to join as a committer and mentor. -- Owen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
Tom, Looking through the proposal with a bit more attention I've noticed that initial source code linked in here https://github.com/cloudera/bigtop refers to iTest framework as the foundation of BigTop testing. However, iTest repository at github.com/cloudera/iTest isn't available? Will it be available along with the rest of the code or it isn't opened to the public? A error in the document? What's the deal there? I believe it'd be beneficial for the community to be able to see the source code of the testing engine. Please correct me if I'm wrong though ;) -- ═ Thanks, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 ═6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Tue, Jun 14, 2011 at 11:43, Konstantin Boudnik c...@apache.org wrote: On 14/06/11 05:26, Tom White wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. Here's a link to the proposal on the wiki http://wiki.apache.org/incubator/BigtopProposal I've also included the initial contents below. Cheers, Tom I've added my name to the committer list, I won't be working on this in much/any of work time, and am fairly overcommitted, so don't expect that much. I can contribute some of my experience in VM setup/teardown for testing RPM installations, and how to do functional testing of dynamically created Hadoop clusters. I am going to add my name to the list of the committers too. Considering my other commitments I might not be able to work much on this project, but I guess the fact that I have wrote like 50% of the underlying system framework might count for something. Cos - 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: [PROPOSAL] Bigtop for the Apache Incubator
Hi Cos, On Thu, Jun 16, 2011 at 5:21 PM, Konstantin Boudnik c...@apache.org wrote: However, iTest repository at github.com/cloudera/iTest isn't available? Will it be available along with the rest of the code or it isn't opened to the public? A error in the document? What's the deal there? I believe it'd be beneficial for the community to be able to see the source code of the testing engine. Please correct me if I'm wrong though ;) iTest is now part of bigtop and resides under test/src/itest-common: https://github.com/cloudera/bigtop/tree/master/test/src/itest-common So in that sense it is there, but not as a separate project. The original documentation for iTest is available under this link: http://cloudera.github.com/bigtop/iTest/ And it looks like there are could be a couple of dangling links there still pointing to where iTest used to be on GitHub as a separate repository. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
Oh, I see. Looks like a dangling links indeed... Thanks for pointing out. Cos On Thu, Jun 16, 2011 at 05:32PM, Roman Shaposhnik wrote: Hi Cos, On Thu, Jun 16, 2011 at 5:21 PM, Konstantin Boudnik c...@apache.org wrote: However, iTest repository at github.com/cloudera/iTest isn't available? Will it be available along with the rest of the code or it isn't opened to the public? A error in the document? What's the deal there? I believe it'd be beneficial for the community to be able to see the source code of the testing engine. Please correct me if I'm wrong though ;) iTest is now part of bigtop and resides under test/src/itest-common: https://github.com/cloudera/bigtop/tree/master/test/src/itest-common So in that sense it is there, but not as a separate project. The original documentation for iTest is available under this link: http://cloudera.github.com/bigtop/iTest/ And it looks like there are could be a couple of dangling links there still pointing to where iTest used to be on GitHub as a separate repository. Thanks, Roman. - 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: [PROPOSAL] Bigtop for the Apache Incubator
Alan Gates has volunteered to be a committer and mentor, so I added
him to the proposal. (For some reason his email to this list didn't
come through.)
Thanks Alan!
Tom
On Mon, Jun 13, 2011 at 9:26 PM, Tom White tomwh...@apache.org wrote:
Hi,
I would like to propose Bigtop to be an Apache Incubator project.
Bigtop is a project for the development of packaging and tests of the
Hadoop ecosystem. The goal is to do testing at various levels
(packaging, platform, runtime, upgrade, etc...) developed by a
community with a focus on the system as a whole, rather than
individual projects.
Here's a link to the proposal on the wiki
http://wiki.apache.org/incubator/BigtopProposal
I've also included the initial contents below.
Cheers,
Tom
= Bigtop - Apache Hadoop Ecosystem Packaging and Test =
== Abstract ==
Bigtop - a project for the development of packaging and tests of the
Hadoop ecosystem.
== Proposal ==
The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects.
This includes testing at various levels (packaging, platform, runtime,
upgrade, etc...) developed by a community with a focus on the system
as a whole, rather than individual projects.
Build, packaging and integration test code that depends upon official
releases of the Apache Hadoop-related projects (HDFS, MapReduce,
HBase, Hive, Pig, ZooKeeper, etc...) will be developed and released by
this project. As bugs and other issues are found we expect these to be
fixed upstream.
== Background ==
The initial packaging and test code for Bigtop was developed by
Cloudera to package projects from the Apache Hadoop ecosystem and
provide a consistent, inter-operable framework.
== Rationale ==
Hadoop defines itself as:
{{{
The Apache Hadoop project develops open-source software for reliable,
scalable, distributed computing. Hadoop includes these subprojects:
* Hadoop Common: The common utilities that support the other Hadoop
subprojects.
* HDFS: A distributed file system that provides high throughput access
to application data.
* MapReduce: A software framework for distributed processing of large
data sets on compute clusters.
}}}
There are also several other Hadoop-related projects at Apache. Some
TLP examples include HBase, Hive, Mahout, ZooKeeper, and Pig. There
are also several new projects in the Incubator such as HCatalog and
Sqoop.
There is limited interoperability testing done the projects
themselves. The intent of this project is to build a community where
the projects are brought together, packaged, and tested for
interoperability.
Projects such as Apache Whirr (incubating), which deploy and use a
collection of Hadoop-related projects, would benefit from the
interoperability testing done by Bigtop, rather than picking and
testing project combinations themselves.
== Initial Goals ==
Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.
Some current goals include:
* create a set of packages for the Hadoop ecosystem, over a wide
range of platforms
* interoperability test these projects
* document project sets that are known to work well together
Bigtop’s release artifact would consist of a single tarball of
packaging and test code that, when built, would produce source and
binary Linux packages for the upstream projects.
= Current Status =
== Meritocracy ==
Bigtop was originally developed and released as an open source
packaging infrastructure, CDH, by Cloudera.
== Community ==
The community is primarily the original developers at Cloudera,
however a number of contributions to the packaging specifications have
been accepted from outside contributors. Growing a diverse community
is the main reason to bring Bigtop to the Apache Incubator.
== Core Developers ==
The core developers for Bigtop project are:
* Andrew Bayer has extensive expertise with build tools, specifically
Jenkins continuous integration and Maven.
* Peter Linnell has contributed to the RPM packaging.
* Bruno Mahé has overseen much of the development of the RPM and
Debian packaging system.
* Roman Shaposhnik designed and implemented the system testing framework.
Many of the committers to the Bigtop project have contributed towards
Hadoop or related Apache projects (Alejandro Abdelnur, Eli Collins,
Patrick Hunt, John Sichi, Michael Stack, Tom White) and are familiar
with Apache principals and philosophy for community driven software
development.
== Alignment ==
We expect projects in Bigtop to be drawn from Hadoop and related
projects at Apache. Bigtop will complement these projects (Hadoop,
Pig, Hive, HBase, etc...) by providing an environment for contributors
interested in building more complex data processing pipelines to work
together integrating more than a single project into a well tested
whole.
= Known Risks =
== Orphaned Products ==
