RE: Need some help to bring ambari into incubator again
Since you need a community to work on it, I'd suggest that you ask in the Hadoop project to see if there are interested parties. --- Noel -Original Message- From: 吴治国 Sent: Monday, April 11, 2022 4:36 To: general@incubator.apache.org Subject: Need some help to bring ambari into incubator again Hello community, Our company is considering to restart the ambari project and help it leave the attic. But I don’t know how to do it, I heard I need 3 incubator PMC to approve this, But I really don’t know who is interesting about this, and what’s next step. So I came here asking for help, if someone is interesting about this, please contact me. Thanks very much. Best regards, Zhiguo Wu. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Apache Guacamole Incubator Proposal
I've been aware of Guacamole for several years. Definitely keen to see it join the ASF. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Jukka Zitting for PMC Chair
I believe that we can call this vote, now, and request that the Board install Jukka as the new PMC Chair. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report, February 2012
Over the past month, there has been a lot of discussion within the Incubator. We have voted in a new PMC Chair, Jukka Zitting, who will be rotating out of the PMC Chair position of JackRabbit. There has been a lot of discussion over the future of the Incubator. Under one proposal, the Board would establish new TLPs whose PMC chair is an ASF Member and initial PMC has at least 3 ASF Members. Such a TLP would be under incubation, but not under an Incubator. Under such a plan, ComDev would be given responsibility for much of the Incubator's Policy Procedure documentation, and similar Community Development related content. Other proposals are less radical, and focus on doing something to ensure more active and involved Mentors. More immediately, some of Jukka's thoughts on the Board's hot topic of pushing projects out of the Incubator are presented in the following exchange: Jukka Zitting wrote: Sam Ruby wrote: What I would like to see is the Incubator start identifying PPMCs that are stalled, and to consider what information they need (in future reports) to help them (us) make such a determination. I am not suggesting that this be made retroactive. Or that it be done immediately. A plan would be fine: i.e., setting a date by which the IPMC will have decided what information needs to be in such reports, and a schedule by which the PPMCs need to start providing said information. My suggestion is to ask the podlings now in category 2 to report again in May on their progress on the identified blockers. If there's been no measurable progress by then, we'll dig deeper to see what we can do. Podlings reporting in other months can be picked up for a similar oversight cycle over the coming months. By July we should then have a pretty accurate record of progress throughout the entire Incubator, including a clear list of podlings that are stuck and need help. Before the next quarterly report I'd rely on mentors to help the podlings identify and implement ways to move forward. And of course, if a podling or its mentors feel that more help is needed, asking on general@ or submitting an extra report is always a good idea. On a related topic, the Incubator PMC voted to reite the HISE podling. BVal has voted to seek TLP status. Syncope, intended to be a reference implementation for Open Source Identity Management, was voted to begin Incubation. The podling reports are below. Sam suggested including podling reports as a link to a frozen wiki page. The Incubator PMC requests feedback from the Board as a whole as to whether an in-line summary and URL to is satisfactory for future reports. Summary of podling reports We reviewed all podlings reporting in this quarter and categorized them according to their progress through the Incubator and the most pressing issues that are currently blocking progress. Still getting started at the Incubator (7 podlings) Any23, Bloodhound, Cordova, DeltaSpike, DeviceMap, Flex, Openmeetings These projects are still getting started, so no immediate progress towards graduation is yet expected. Not yet ready to graduate (13 podlings) IP clearance: Amber Release trouble: Clerezza, Stanbol Low activity: Ambari, Nuvem, PhotArk, SIS, Wink, Zeta Components Low diversity: Airavata, Droids, VCL, Wookie We expect the next quarterly report of projects in this category to include a summary of their actions and progress in solving these issues. Ready to graduate (4 podlings) Jena, Lucene.NET, NPanday, OpenNLP We expect these projects to graduate within the next quarter. Detailed Reports Airavata Airavata is a software toolkit which provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. Airavata is incubating since May 2011. A list of the three most important issues to address in the move towards graduation 1. The barrier of entry in contributing to Airavata seems to be high. The code, documentation and JIRA issues have to be efficiently organized and managed to appeal to wider developer community. 2. Develop a strong community with organizational diversity and well aligned with existing ASF projects as outlined here: http://wiki.apache.org/incubator/AiravataProposal#Alignment 3. Create a regular and predictable release process and schedule Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Whilst our community is reasonably large and active we do not, at present, have significant diversity, but are working on it. Right now most of the contributors that are active are from Indiana University. Chris from JPL is involved very closely from a mentoring perspective and will try and get involved code wise. The 0.2 release candidate is currently VOTE'ing
RE: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)
+1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Re: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)
Ross Gardler wrote: I'm ready to vote, but Chris said it looks like the remaining folks (including me) that were in the running have aligned beyond the following nominee: Where is the mail from Noel saying he is no longer standing? Have I missed something? There wasn't one. I was traveling when the vote started. No worries. I have no issue with standing down after 8 years, and Jukka is an excellent and active successor. I was exceedingly pleased to see his message that he had reconsidered, was willing to stand as Incubator PMC Chair, and would rotate out of the JackRabbit VP position. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: NOMINATIONS for Incubator PMC Chair
I intend to nominate Noel J. Bergman I will leave my hat in the ring, but also note that a number of people have expressed that not only is it time to vote for the Incubator PMC Chair, but also that it is time for new, different, energy and ideas in that role. So those people would certainly prefer to see someone other than me in the role. In my view, the Incubator PMC Chair is a largely administrative role, but also charged with protecting the ASF and the Incubator as the ultimate oversight. If I am not re-elected, I will not reminisce about the days of having to do the monthly reports. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: NOMINATIONS for Incubator PMC Chair
Based on the current discussions for radically redefining the Incubator, I propose William A Rowe, Jr. for the new Incubator PMC Chair. Between Bill and Chris Mattman, they are the leading forces behind the proposed re-org, and I feel that, Bill would be the more experienced choice, and hope that he he would take the role at least long enough to see the new re-org structure put into place and up-and-running. Bill, what say you? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: NOMINATIONS for Incubator PMC Chair
Noel J. Bergman wrote: I intend to nominate Noel J. Bergman I will leave my hat in the ring ... But as others will have noted, if the proposed re-organization is to move forward, I personally recommend Bill Rowe for the role, or Chris Mattman if Bill won't take it. That new Incubator will be different from the one we have known, and those two are the driving forces behind its new structure. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Nomination of Chris Mattman for the IPMC Chair (was: Re: NOMINATIONS for Incubator PMC Chair)
Chris, I will note that should I be elected into this role, I will state that I don't intend to be in it very long as I don't intend for it to exist much longer. I spoke with Bill this evening, and have indicated to him that I'd like for you and he to already start working on the re-org proposal. We'll need to vote on it, but there seems to be interest in that direction. However, please note that the re-org still has a position that is at least analogous. You would not be getting off so easily. ;-) --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Questions for projects
I need to say that your [Jukka] work here is great. Thanks. +1 one doesn't need to be a PMC chair to invest some time in podling review and followup. :-) :-) --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: NOMINATIONS for Incubator PMC Chair
When did you resign? I didn't. As intimated by Benson, and mentioned in a prior Board report, there has been discussion on the private list of rotating the PMC Chair. I've had it for many years, and a number of people expressed the view that a shot of new blood might be beneficial. The call for nominations came up on the private list while I was on vacation, so upon returning, I forwarded it to the community, where it belongs. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Discuss] Qualifications for Incubator PMC Chair
Robert Burrell Donkin asked: Noel J. Bergman wrote: A call for nominations for Incubator PMC Chair was started on the private@ list. The nomination process should be open to the Incubator community. What qualities does a good Incubator Chair need? - Robert IMO: - Ability and willingness to do the administrative work required - Consistent and proper focus on protecting the integrity of the ASF and Incubator - Remembers why we are here - Ability to help guide the PMC when/as necessary towards workable solutions - Ability to delegate I'm sure that there are others, and encourage folks to add their views to the list. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSSION] Regular rotation PMC chair
Should the current chair be forced to resign I'm not going to make an issue of it. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
NOMINATIONS for Incubator PMC Chair
This belongs on general@ ... A call for nominations for Incubator PMC Chair was started on the private@ list. The nomination process should be open to the Incubator community. --- Noel -Original Message- Sent: Thursday, January 26, 2012 11:30 To: priv...@incubator.apache.org Subject: NOMINATIONS for IPMC Chair I nominate __, assuming he is willing and able to handle the workload - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: -1 on this months board report (was: Small but otherwise happy podlings)
Apparently Benson feels that it is unreasonable to expect at least one Incubator PMC member to actually read the one report that this PMC sends on. Yes, I'm irritated. To be clear, *I* read every word of every Board report that we send on. I don't take issue with whatever else you wrote. I even accept that I might well be the only person who reads the whole report. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Q. Forks without concensus?; A. anytime / depends / never without agreement
Roy T. Fielding wrote: Noel J. Bergman wrote: The ASF is not about code; it is about community. If a community forks, or otherwise emerges around a codebase, we are not accepting the CODE: we are accepting the COMMUNITY. One company is not a community. As you've otherwise acknowledged, I was talking in the general case, and you're addressing a specific instance. And it seems to me that if we are to say that a COMMUNITZY is not permitted to participate despite use of code that is perfectly proper according to the license, then we are beggaring out own license, the whole point of which is to permit forks, and to prevent a sole copyright holder from assuming control over the community. If there is no community for the original codebase, yes. Agreed. If there is a community and that community doesn't want Apache to fork the code that they created, then we will not fork that code at Apache. Why not, *IF* there is an active second community that wants to fork? Again, in the hypothetical, not in the specific, case, which you say is a single vendor, not a community. If the original developers of the code do not want their license changed, then we will not fork the code at Apache. I kind of take that as a given, since how could we fork it if we can't relicense it? We only accept voluntary contributions The presence of a community that wants to work here implies voluntary, and not everyone has to agree with the fork. Don't you remember the origins of Apache Felix? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Improviing quarterly reports
Joe Schaefer wrote: Let's stop discussing this issue in the abstract Good idea. Lets be more specific, and put together something actionable. Now lets look at the remainder- several projects with no report whatsoever This has been an issue. Perhaps we need to put some teeth in the requirement, such as closing down commit access until reports are posted? I don't have an issue with saying that a project that does not report by the assigned cut-off date has its commit access turned off until the report is posted. Or, perhaps to give weight to your view that Mentors need to be more involved, until after it is signed off by a Mentor? Tashi, which has been incubating since 2008, writes exclusively about technical issues and really says zilch about their progress towards graduation. We've repeatedly asked projects to focus on their graduation requirements. What can we do to help push them in the right direction? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
January 2012 Incubator Board Report
A number of substantive issues came up during the past month. First, and although it was raised on the private list and therefore details won't be part of the public report, we advise the Board that there is substantial discussion regarding changing the Incubator VP, which has been held for almost 8 years by the current VP. Second, there is a dispute, both in the abstract and concretely, regarding whether or not the ASF, via the Incubator, may play host to a community that has forked a compatibly licensed codebase. Roy suggested that, in the specific case: The VOTE was based on misleading information. The Incubator PMC should declare it void and request a new proposal. The existing Bloodhound podling should be placed on hold until this is sorted out. Greg has said, more recently, that the Bloodhound and Trac communities already have a new non-fork plan and are executing on that now, on the bloodhound-dev mailing list. If that comes to pass, perhaps no further attention from the PMC and Board will be required on this issue. If not, we'll have to revisit the specific case. However, Bill Rowe has requested that the Incubator PMC formally put the general matter to the Board: what policy do or should we have regarding a community that wishes to fork a suitably licensed codebase and come to the ASF? If so, what is that policy? Or is that decision still a matter to be determined situationally by the Incubator PMC? For whatever it is worth, the latter is the opinion of the Incubator VP, who recalls that more than one successful ASF project started elsewhere and came to the ASF as a fork, and not without some complaint from members of the outside community (e.g., Apache Felix). Third, there was a lot of discussion surrounding a couple of Incubator issues: 1) podlings being comfortably settled in the Incubator, and not being focused enough on graduation; 2) Mentors being insufficiently active, and thus not providing either proper guidance or oversight. We definitely need to address these issues, promoting both Mentor involvement and graduation from the Incubator. And, finally, Jukka spent time reviewing the status of many of the older podlings, and recommending an action. Perhaps not coincidentally, ACE, Gora and Bean Validation Framework are all in graduation mode. But, meanwhile, Bloodhound (the podling previously mentioned), DeviceMap and Flex have joined. Below are podling reports. Sam Ruby has already reviewed the original list prior to posting, and requested that specific posts not be provided to the Board, as he was unhappy with their status: Kato: has been in limbo for years due to Oracle. The podling needs to decide what to do, or terminate Bloodhound, HISE, JSPWiki and Openmeetings: missing VXQuery: not signed off by a Mentor Although initially requested to be excluded, the Celix and Tashi reports were revised to provide at least some graduation guidance, and so their reports are included, below. - Any23 Any23 is defined as a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats. Any23 is what it is informally named an RDF Distiller. A list of the three most important issues to address in the move towards graduation 1. Port Any23 code to ASF infrastructure and update license headers 2. Develop a strong community with organizational diversity and with strong connections to other relevant ASF communities. 3. At least one Any23 incubating release Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need to be aware of? Yes, all of the code has been ported from Google Code to the ASF. Thanks to Daniel Shahaf and Michele Mostarda for leading the charge here. How has the community developed since the last report? All ASF karma has been granted on the repository, and we've received a few JIRA issues, but not from outside the core set of PPMC members as of yet. The team needs to respond to Paolo Castagna's points regarding RDF frameworks and collaboration, and will hopefully do so this month. How has the project developed since the last report? Any23 was voted into the Incubator by the IPMC on October 1, 2011. We have Jenkins CI builds going thanks to Lewis John McGibbney, code up and running at the ASF thanks to Michele and to Daniel, so we're all set to really get kicking! Celix Celix is an implementation of the OSGi Specification in C. Celix entered incubation on November 2, 2010. Over the last few months lots of work has been put into integrating APR and updating the Celix code base to the proposed code style. This code style has partially been documented on [1]. Also some effort has been put into updating the source for Visual Studio, even though not yet finished some interesting and helpful patches where submitted and applied. In Oktober an
RE: Q. Forks without concensus?; A. anytime / depends / never without agreement
The ASF is not about code; it is about community. If a community forks, or otherwise emerges around a codebase, we are not accepting the CODE: we are accepting the COMMUNITY. And it seems to me that if we are to say that a COMMUNITZY is not permitted to participate despite use of code that is perfectly proper according to the license, then we are beggaring out own license, the whole point of which is to permit forks, and to prevent a sole copyright holder from assuming control over the community. If a corporation were to create an ASF-licensed codebase, and later decide to take back control, would we refuse a COMMUNITY-based project based on that codebase? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Actively retiring projects
Sam, My personal perspective is that incubation shouldn't generally take more than a year. The problem is with small communities. What do you suggest with projects that are functional, but just barely have a critical mass, or not quite even? my feeling is that there needs to be an expectation that a podling produces AT THE VERY MINIMUM a credible plan that they are executing on which will lead to graduation at some point. Many of them say that they need to grow their community. What do you suggest they do while trying? Do we simply call them done after 365 days? Meanwhile, I will personally focus on JSPWiki. I would have expected that one done long ago. And some of the ones on your list are actually dead. Perhaps just not yet buried, which I would agree falls under the term of garbage collection. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
December 2011 Incubator Board Report
We've all been aware that the Incubator has been growing more than graduating, over the years. Last month, Sam started a discussion regarding being more proactive and pushing projects out of the nest, basically one way or another, after a year. A real issue is pushing out those really ready to graduate, and doing the garbage collection on those that are already dead (and may have even voted to terminate). In-between are those projects that are struggling to achieve critical mass, but are active with who they do have involved. The response from mentors of various projects was quite encouraging, both in specifics and in concept, and hopefully we'll start to see a wave of TLP requests, following ACE, Bean Validation, and Empire-DB. Meanwhile, Apache DeltaSpike -- a collection of JSR-299 (CDI) Extensions for building applications on the Java SE and EE platforms -- was voted for Incubation. There has also been excellent discussion about pruning and clarifying Incubation rules and process, to be more streamlined and minimal. With respect to the monthly board report, since the last report (and since the schedule change), we've changed how reminders are processed, and hope to be well on the way to cleaning up the problem where the wrong projects were listed and reminded. There were still a few glitches for this month, but hopefully they're resolved for next. Brett Porter, Dave Crossley, Upayavira, Jim, and others have contributed to the efforts, and are well deserving of continued thanks. Even so, and despite an extra day and reminder, neither HISE nor KATA reported. Wave did take advantage of the time to report. Accumulo Accumulo is a sorted, distributed key/value store based on BigTable's design. Accumulo entered incubation in September 2011. In the move towards graduation, we must address: 1. Learning Apache procedures 2. Creating releases 3. Building a community Community Development: * active discussion on mailing lists and on JIRA tickets * three new contributors have submitted patches this month * logo voted upon Project Development: * made progress towards releasing 1.3.5 (now on candidate 10) * incorporated lessons from failed release candidates into redesign of release process for trunk * fixed bugs / tested code / added documentation Ambari Ambari is monitoring, administration and lifecycle management project for Apache Hadoop clusters. * Incubating since 30 August 2011. * Picked CTR instead of RTC. * Development proceeding actively. (129 jiras fixed so far, 15k of java) * Should have first end to end test working soon. Issues that must be addressed before graduation are: * Making a release * Attracting users and developers * Increase diversity of developers outside of Hortonworks Amber Amber has been incubating since July 2010. Amber is a project to develop a Java library which provides an API specification for, and an unconditionally compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications. OAuth is a mechanism that allows users to authenticate and authorise access by another party to resources they control while avoiding the need to share their username and password credentials. The most important issues that must be addressed before graduation are: - Clarify status of code grant - Attract users and developers - Generate a release The Incubator PMC / ASF Board should be aware that: - Community activity is relatively low - We need copyright signoff from University of Newcastle How has the community developed since the last report - New users / devs show up on the mailing lists both contributing patches and asking for guidance/release How has the project developed since the last report - The old trunk has been moved to a branch amber-0.10 which reflects OAuth 0.10 spec - The new trunk is being updated to latest 0.22 spec version - Versions of artifacts have been aligned to the supported OAuth specification supported - Discussion about preparing for an initial release is ongoing Any23 Any23 is defined as a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats. Any23 is what it is informally named an RDF Distiller. A list of the three most important issues to address in the move towards graduation 1. Port Any23 code to ASF infrastructure and update license headers 2. Develop a strong community with organizational diversity and with strong connections to other relevant ASF communities. 3. At least one Any23 incubating release Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need to be aware of? Yes, there has been ongoing work to bring the Any23 codebase to Apache SVN. The final stages include loading the code dump to the Apache test repos, there will then be a short time for the dev/committer team to review
RE: October 2011 Incubator Board Report
Our next report is due in December, not October. Nu? So where is it? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: so the deadline for podling reports has passed, now what?
Some reports missing: HISE, Kato, Wave. If they are not posted by tomorrow AM, the report is going in without them. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Change in Due Dates for Board reports
PLEASE NOTE! From the ASF Board: For now on, all reports to the board for review/inclusion at the board meetings will now be due 1 WEEK before the meeting. Reports submitted late will be declined and you'll need to resubmit the next month. This means that Incubator reports really need to be finished by the end of the FIRST week of the month. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report November 2011
Notwithstanding the fact that members of the Board are active within the Incubator, there are no issues requiring Board attention or intervention. We are, however, recognizing that we've had growth issues of our own. As David Crossley pointed out, he made mistakes last month related to the Reporting Schedule, and we continue to have issues. The Incubator is almost as big as the rest of the ASF combined. David posted a plot chart reflecting our growth: http://incubator.apache.org/history/ Roy proposed one change to help cut down on some commit karma logistics. Sebb and David have been discussing some changes to help manage the meta-data, e.g., reporting schedule. Nothing is concrete, yet, but clearly we need to make some changes to make things easier. OpenMeetings -- project to provide video conferencing, instant messaging, white board, collaborative document editing and other groupware tools using API functions of the Red5 Streaming Server for Remoting and Streaming -- has been accepted for Incubation. Accumulo Accumulo is a sorted, distributed key/value store based on BigTable's design. Accumulo entered incubation in September 2011. In the move towards graduation, we must address: 1. Learning Apache procedures 2. Creating releases 3. Building a community Community Development: * active discussion on mailing lists and on JIRA tickets * two new contributors have submitted patches * web site created * procedures and decision processes beginning to take form Project Development: * podling voted on release candidate for 1.3.5 (soon to be submitted to incubator PMC) * documented release process * applied formatting and licenses * fixed bugs / tested code / added documentation Airavata Airavata is a software toolkit which provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. Airavata is incubating since May 2011. A list of the three most important issues to address in the move towards graduation 1. The barrier of entry in contributing to Airavata seems to be high. The code, documentation and JIRA issues have to be efficiently organized and managed to appeal to wider developer community. 2. Test coverage of the code has to be increased significantly. 3. Develop a strong community with organizational diversity and well aligned with existing ASF projects as outlined here: http://wiki.apache.org/incubator/AiravataProposal#Alignment Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Patanachai Tangchaisin, Heshan Suriyarachchi and Saminda Wijeratne were VOTEd in as committers and PPMC members on the project. Chris, Ross, Ate, Suresh, Marlon, Raminder met at ApacheCon NA and had a great time! Suresh's Fast Feather talk introducing Airavata went great. How has the project developed since the last report? * Community is efficient being engaged through maling list and JIRA. * The code is significantly improved with proper modular organization and packaging since entering incubation. * Documentation and website have also been improved. * All data base required components are integrated with Derby. * The XRegistry component is deprecated in favor of synergizing with other Apache repository projects like Jack Rabbit through the JCR API. * Jenkins continuos integration and sonar code analysis dashboard are setup and actively used by the community. * The project is preparing its initial 0.1-incubating release, currently VOTE'ing on the 2nd release candidate. Amber DID NOT REPORT Any23 Anything To Triples (shortly Any23) defined as a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats. Any23 is what it is informally named an RDF Distiller. A list of the three most important issues to address in the move towards graduation 1. Port Any23 code to ASF infrastructure and update license headers 2. Develop a strong community with organizational diversity and with strong connections to other relevant ASF communities. 3. At least one Any23 incubating release Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Paolo Castagna came onto list and filed some issues ANY23-18, and ANY23-19 suggesting to abstract away the interfaces in Any23 and make it easier to plug in other RDF technologies, and to support RDF-A. Giovanni Tumarello now has his account. How has the project developed since the last report? Any23 was voted into the Incubator by the IPMC on October 1, 2011. All infrastructure has been moved over to Apache. Michele
October 2011 Incubator Board Report revised (missed removing WAVE, too)
Most of the general discussion on the Incubator list over the past month was how to improve the usability of the Incubator web-site. S4 (Simple Scalable Streaming System) -- a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data -- was voted to begin Incubation. Any23 (Anything To Triples) -- a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats -- was voted to begin Incubation. Apache DirectMemory -- a multi-layered cache implementation featuring off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java objects without degrading JVM performance -- was voted to begin Incubation. Apache Callback (derived from PhonaGap) -- a platform for building native (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS and JavaScript -- was voted to begin Incubation. DeltaCloud is currently voting on graduation from the Incubator. ACE is also discussing graduation. With respect ot an early version of the report, there was confusion as to which podlings needed to report this month, but we appear to have it straightened out. The Wiki page had a few too many projects loaded onto it. -- Accumulo Accumulo is a sorted, distributed key/value store based on BigTable's design. Accumulo entered incubation in September 2011. In the move towards graduation, we must address: 1. Learning Apache procedures 2. Creating releases 3. Building a community Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: Discussion is ongoing as to whether agreements other than ICLAs are needed or desirable for people employed by the US government to make contributions to Apache (see LEGAL-100). Developments since entering incubation: * mailing lists created * JIRA created * SVN directory and git mirror created * accounts for initial committers created * ICLAs and Software Grant filed * CMS-ready site begun * initial code uploaded * Jenkins build created * ReviewBoard group created --- ACE Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. ACE started incubation on April 24th 2009. There are currently no issues requiring board or Incubator PMC attention. Community: * We've got a lot of great feedback and patches from the community. * There have been talks with the jclouds (we use them) as well as the Amdatu (they use us) open source projects. Software: * We now have a REST client API. * The management agent has been extended. * Karaf features were added. * We have a server side resolver based on Apache Felix. Licensing and other issues: * None at the moment. Things to resolve prior to graduation: * We hope this is our very last board report as we think we're ready for graduation now! Ambari Ambari is monitoring, administration and lifecycle management project for Apache Hadoop clusters. * Incubating since 30 August 2011. * Mailing lists created and mentors subscribed. * Confluence created. * Initial code committed. * Site created. * Code grant received. * Development proceeding actively. * RAT added to pom and report is clean. Any23 Anything To Triples (shortly Any23) defined as a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats. Any23 is what it is informally named an RDF Distiller. A list of the three most important issues to address in the move towards graduation 1. Port Any23 code to ASF infrastructure and update license headers 2. Develop a strong community with organizational diversity and with strong connections to other relevant ASF communities. 3. At least one Any23 incubating release Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA filed and Chris working on getting account set up). We've already moved our discussions onto the public mailing lists now that they are set up. How has the project developed since the last report? Any23 was voted into the Incubator by the IPMC on October 1, 2011. Software grants from DERI and from FBK have been filed and accepted thanks to Michele Mostarda. There has already been discussion of how to move over JIRA issues and Wiki issues from the Google Code site and the full issues transition was completed on 12/10/2011. Code
RE: October 2011 Incubator Board Report revised (missed removing WAVE, too)
Weird ... that was posted to my output queue on Monday. :-( No big deal. Just a clarification that Wave wasn't missing. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
October 2011 Incubator Board Report
Most of the general discussion on the Incubator list over the past month was how to improve the usability of the Incubator web-site. S4 (Simple Scalable Streaming System) -- a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data -- was voted to begin Incubation. Any23 (Anything To Triples) -- a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats -- was voted to begin Incubation. Apache DirectMemory -- a multi-layered cache implementation featuring off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java objects without degrading JVM performance -- was voted to begin Incubation. Apache Callback (derived from PhonaGap) -- a platform for building native (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS and JavaScript -- was voted to begin Incubation. DeltaCloud is currently voting on graduation from the Incubator. ACE is also discussing graduation. With respect ot an early version of the report, there was confusion as to which podlings needed to report this month, but we appear to have it straightened out. The Wiki page had a few too many projects loaded onto it. -- Accumulo Accumulo is a sorted, distributed key/value store based on BigTable's design. Accumulo entered incubation in September 2011. In the move towards graduation, we must address: 1. Learning Apache procedures 2. Creating releases 3. Building a community Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: Discussion is ongoing as to whether agreements other than ICLAs are needed or desirable for people employed by the US government to make contributions to Apache (see LEGAL-100). Developments since entering incubation: * mailing lists created * JIRA created * SVN directory and git mirror created * accounts for initial committers created * ICLAs and Software Grant filed * CMS-ready site begun * initial code uploaded * Jenkins build created * ReviewBoard group created --- ACE Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. ACE started incubation on April 24th 2009. There are currently no issues requiring board or Incubator PMC attention. Community: * We've got a lot of great feedback and patches from the community. * There have been talks with the jclouds (we use them) as well as the Amdatu (they use us) open source projects. Software: * We now have a REST client API. * The management agent has been extended. * Karaf features were added. * We have a server side resolver based on Apache Felix. Licensing and other issues: * None at the moment. Things to resolve prior to graduation: * We hope this is our very last board report as we think we're ready for graduation now! Ambari Ambari is monitoring, administration and lifecycle management project for Apache Hadoop clusters. * Incubating since 30 August 2011. * Mailing lists created and mentors subscribed. * Confluence created. * Initial code committed. * Site created. * Code grant received. * Development proceeding actively. * RAT added to pom and report is clean. Any23 Anything To Triples (shortly Any23) defined as a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats. Any23 is what it is informally named an RDF Distiller. A list of the three most important issues to address in the move towards graduation 1. Port Any23 code to ASF infrastructure and update license headers 2. Develop a strong community with organizational diversity and with strong connections to other relevant ASF communities. 3. At least one Any23 incubating release Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA filed and Chris working on getting account set up). We've already moved our discussions onto the public mailing lists now that they are set up. How has the project developed since the last report? Any23 was voted into the Incubator by the IPMC on October 1, 2011. Software grants from DERI and from FBK have been filed and accepted thanks to Michele Mostarda. There has already been discussion of how to move over JIRA issues and Wiki issues from the Google Code site and the full issues transition was completed on 12/10/2011. Code
October 2011 Incubator Board Report
Most of the general discussion on the Incubator list over the past month was how to improve the usability of the Incubator web-site. S4 (Simple Scalable Streaming System) -- a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data -- was voted to begin Incubation. Any23 (Anything To Triples) -- a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats -- was voted to begin Incubation. Apache DirectMemory -- a multi-layered cache implementation featuring off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java objects without degrading JVM performance -- was voted to begin Incubation. Apache Callback (derived from PhonaGap) -- a platform for building native (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS and JavaScript -- was voted to begin Incubation. DeltaCloud is currently voting on graduation from the Incubator. ACE is also discussing graduation. ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF (also managed to do a release, though), RAT and WAVE all failed to report this month. The Chair is raising the issue of what to do with these projects. -- Accumulo Accumulo is a sorted, distributed key/value store based on BigTable's design. Accumulo entered incubation in September 2011. In the move towards graduation, we must address: 1. Learning Apache procedures 2. Creating releases 3. Building a community Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: Discussion is ongoing as to whether agreements other than ICLAs are needed or desirable for people employed by the US government to make contributions to Apache (see LEGAL-100). Developments since entering incubation: * mailing lists created * JIRA created * SVN directory and git mirror created * accounts for initial committers created * ICLAs and Software Grant filed * CMS-ready site begun * initial code uploaded * Jenkins build created * ReviewBoard group created --- ACE Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. ACE started incubation on April 24th 2009. There are currently no issues requiring board or Incubator PMC attention. Community: * We've got a lot of great feedback and patches from the community. * There have been talks with the jclouds (we use them) as well as the Amdatu (they use us) open source projects. Software: * We now have a REST client API. * The management agent has been extended. * Karaf features were added. * We have a server side resolver based on Apache Felix. Licensing and other issues: * None at the moment. Things to resolve prior to graduation: * We hope this is our very last board report as we think we're ready for graduation now! Ambari Ambari is monitoring, administration and lifecycle management project for Apache Hadoop clusters. * Incubating since 30 August 2011. * Mailing lists created and mentors subscribed. * Confluence created. * Initial code committed. * Site created. * Code grant received. * Development proceeding actively. * RAT added to pom and report is clean. Any23 Anything To Triples (shortly Any23) defined as a Java library, a Web service and a set of command line tools to extract and validate structured data in RDF format from a variety of Web documents and markup formats. Any23 is what it is informally named an RDF Distiller. A list of the three most important issues to address in the move towards graduation 1. Port Any23 code to ASF infrastructure and update license headers 2. Develop a strong community with organizational diversity and with strong connections to other relevant ASF communities. 3. At least one Any23 incubating release Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA filed and Chris working on getting account set up). We've already moved our discussions onto the public mailing lists now that they are set up. How has the project developed since the last report? Any23 was voted into the Incubator by the IPMC on October 1, 2011. Software grants from DERI and from FBK have been filed and accepted thanks to Michele Mostarda. There has already been discussion of how to move over JIRA issues and Wiki issues from the Google Code site and the full issues transition was completed on 12/10/2011.
Projects failing to repoirt for October - appropriate actions?
On most months, I have to chase down missing reports. ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF (also managed to do a release, though), RAT and WAVE all failed to report this month. RAT was discussing graduation, but still needs to report. Two others were active enough to put out releases, but failed to report. Wave has been active enough to discuss their next steps, but failed to report. What should be done with these projects? Which one(s) should be retired? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
September 2011 Incubator Board
The flood of Hadoop related projects continues with new Incubator projects: * HMS (now Ambari), a monitoring, administration and lifecycle management project for Apache Hadoop clusters * Accumulo, a sorted, distributed key/value store based on Google's BigTable design, and built on top of Hadoop, Zookeeper, and Thrift were voted to start Incubation, along with: * Kalumet, a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. Other projects under discussion: * S4 (Simple Scalable Streaming System), a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. OGNL should be moving to Apache Commons. --- Ambari (was HMS) Ambari is monitoring, administration and lifecycle management project for Apache Hadoop clusters. * Incubating since 30 August 2011. * Changed name to Ambari over trademark concerns. * In process of moving onto Apache infrastructure: * Jira and subversion created. * Mailing lists requested (6 Sep), but not created. * Confluence requested (6 Sep), but not created * Committer accounts created. * Working on initial code import and code grant. BeanValidation Bean Validation was accepted into Incubator on 1 March 2010. The Bean Validation project is an implementation of the Java EE Bean Validation JSR303 specification. There are no other important issues open before a possible graduation. Actually the project is discussing its graduation as TLP or into Apache Commons, as natural successor of Commons Validator. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * none How has the community developed since the last report * Users community activity is stable, users slightly decreased the activity of filling issues on JIRA and asking questions, we suppose codebase/provided documentation start being mature enough to satisfy users needs. How has the project developed since the last report. * Started a 'extras' module development where putting validators not included in the JSR303 spec. * planning the development for implementing next JSR330 spec version. Bigtop Bigtop is a project for the development of native packaging and stack tests of the Hadoop ecosystem. Bigtop entered incubation on June 20, 2011. Primary issues blocking graduation: * Need for increased diversity and additional committers. * Incubating release including testing framework. * Incorporation of functional stack testing. Issues which Incubator PMC and/or ASF Board might need/wish to be aware of: * Due to limitations in available platforms on Apache Jenkins infrastructure and need for VM spin-up/spin-down for tests, we are working directly with OSUOSL on build/test setup. Community development since last report: * Community meetup held August 18th, with mentors and committers alike. Project development since last report: * 0.1.0-incubating released. * Website created. * Additional component project (Mahout) added. * Supported platforms voted on. * Initial implementation of package validation tests implemented and live. Deft Deft is a non-blocking, asynchronous, event driven high performance web framework running on the JVM. Issues before graduation * Project rename (Deft seems to be trademarked) * Put together a first incubation release * Find new committers The PPMC has discussed that we probably need to rename Deft. The reason for this is to avoid future complication because of trademarks associated with Deft. No significant change has been noticed regarding the Apache Deft community. The Apache Deft web page is up and running (still a lot of documentation to be done). Etch Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. - Etch binding-cpp is currently in development and some parts of the basic framework (OS abstraction layer, collection types, basic Etch components) are already implemented and available in the trunk - A new developer Martin Veith from the BMW Car IT provided a lot of patches and some documentation stuff - Fixed some smaller bugs in the C, Java and C# bindings - The new Apache Etch website is nearly complete http://etch.staging.apache.org/etch/ and will be migrated to the public area while the next weeks. A detailed Etch documentation will be converted afterwards (Docbook PDF and HTML) - Community ramp up a little bit and we hope to get a better grounding future tasks: - Prepare next release and publish it - Migrate to new Apache Etch CMS - Further development of the
RE: Accumulo incubator proposal: Statement of Concern
No... Knowing Noel, he was not opening anything. He was speaking to general principles about how the Incubator works. +1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Suggested tweak to proposal template
I'd like to add a note to the template asking the initial contributors to note their favorite email address. Or at least the one they intend to use/expose. when the inevitable 'subscribe' requests for the private list come along, the mentor moderating the private list can identify the addresses as legitimate. Or we could preload the mailing list. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Accumulo incubator proposal: Statement of Concern
Doug Meil wrote: I think that the ASF and ASF incubator leadership should consider it a priority to foster such communication. We do. I, in particular, tend to do it --- and have on occassion been criticized for trying to foster project collaboration and/or merger. BUT ... The Incubator does not pick winners, exclude projects based on overlap with others, or deny a community a chance just because some other project (ASF or otherwise) feels that their turf is being infringed. We have been very consistent on this issue. Your best move is to open talks with the Accumulo community, and see what options for collaboration and/or merger exist as it proceeds. As for some of the other comments, Accumulo will be held to the same standards as every other project, and will be required to exhibit The Apache Way. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Retire Olio?
I don't see anything that suggests the community is viable. No response to Hen's ping, for example. Should we move ahead with moving the project to dormant status? Do we have provenance such that we can leave a read-only SVN? --- Noel -Original Message- From: Henri Yandell [mailto:flame...@gmail.com] Sent: Wednesday, August 03, 2011 4:00 To: general@incubator.apache.org Subject: Re: Retire Olio? Pinging on this thread. Are there alternatives other than retiring? ie) Things that could be done to bring it to life? Other communities it could join? Hen On Tue, Jul 19, 2011 at 11:07 PM, Henri Yandell flame...@gmail.com wrote: +1 (non-binding). Note that they've not signed off on their copyright item, so we should delete the svn tree or get that signed off before hand. Hen On Mon, Jul 18, 2011 at 11:31 AM, Noel J. Bergman n...@devtech.com wrote: I see no development in 18 months. Is it time to terminate? --- 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report August 2011
Bluesky was retired by vote of the Incubator PMC. The project just never managed to adjust to the ASF's community-orientation. Olio likewise seems prime for retirement. HISE (Human Tasks for WS-BPEL) again failed to report (that was an issue in February as well). Activity has picked up aomewhat being mostly dead, but the Incubator will inquire into the viability of the project. Oozie failed to report, but is just getting started. There are no archives for the -dev list. ODF Toolkit, a set of Java modules that allow programmatic creation, scanning and manipulation of OpenDocument Format documents, was voted to begin Incubation, and has filed its first report. Giraph, a large-scale, fault-tolerant, Bulk Synchronous Parallel (BSP)-based graph processing framework that runs on Hadoop, was voted to begin Incubation. The Incubator PMC voted to submit Whirr for TLP status to the Board. Richard Provarp joined the Incubator PMC. -- Airavata Airavata is a software toolkit which provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. Airavata is incubating since May 2011. A list of the three most important issues to address in the move towards graduation 1. Update web service implementations from XSUL to Axis2. Update security libraries and simplify the build process and provide sample use cases. 2. Package, document and release at least one Apache Incubator release. 3. Develop a strong community with organizational diversity and well aligned with existing ASF projects as outlined here: http://wiki.apache.org/incubator/AiravataProposal#Alignment Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Web designer Barbara Hallock was voted in a commiter and PPMC member for her contributions to the website design, logo and CSS contributions. The website is now live with her contributions. Lahiru Gunathilake an existing apache commiter from Axis2 QPID projects has made significant contributions and provided 25+ patches to Airavata. He is voted in as a commiter and PPMC member. A new volunteer Patanachai Tangchaisin has been contributing to the various components of the project. How has the project developed since the last report? * Significant progress has been made towards a release. All components are organized within the svn adding project level and module level maven build profiles. * Website is updated with documentation for build and eclipse development instructions. * The default database in WS-Messenger and XRegistry is changed from mysql to Apache Derby. Derby is integrated as an embedded database to build and deploy as a maven profile. This porting has removed the incompatible license dependency on mysql-connector jar. * WS-Messenger module is re-factored, packaged and tested. The messaging system clients are being worked on, this component needs to integrated with rest of the modules. * XBaya module is cleaned up of unused legacy code, improved dependency management and simple test cases are tested through. Amber Amber has been incubating since July 2010. Amber is a project to develop a Java library which provides an API specification for, and an unconditionally compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications. OAuth is a mechanism that allows users to authenticate and authorise access by another party to resources they control while avoiding the need to share their username and password credentials. The most important issues that must be addressed before graduation are: - Clarify status of code grant - Attract users and developers - Generate a release The Incubator PMC / ASF Board should be aware that: - Community activity is relatively low How has the community developed since the last report - Some users have started asking for help or getting started guides on the mailing list How has the project developed since the last report - Work has begun on updating the OAuth implementation - Discussion about preparing for an initial release is ongoing Bigtop Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. Bigtop entered incubation on June 20 2011 A list of the three most important issues to address in the move towards graduation: * Create Bigtop web site. Item in progress. See ticket BIGTOP-9 * Make an incubating release. * Grow the community size and diversity. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: * No issues How has the community developed since the last report: * Discussions have been started about how to organize the development (RTC vs CTR) How has the project developed since the last report. *
RE: OGNL missing reports
I have added it now for OGNL. it was a mentor failure - the project has written its report and ask mentors to sign it and add it to the wiki. And we mentors all forgot. Too late for this month. Please add it to the August wiki page, and update date it as necessary. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: *** Missing reports - POST IMMEDIATELY!
OGNL, Olio (2 cycles in a row), Rave, VXQuery (also two cycles in a row) are all missing. We (Rave) completed three monthly reports (April, May, June) and were moved to the March, June, September, December reporting schedule. Is there another list we need to update? I went by the roster on the Wiki page, which had you listed for July. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Bluesky cleanup? (was: [RESULT][VOTE] Retire Bluesky Podling)
Er, have you explicitly told the Bluesky lists that the repo is about to be deleted? Alternatively, we can simply turn off write access [to] ensure it's not actively developed, but that it's available. Are we deleting or moving to an attic-type section? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
*** Missing reports - POST IMMEDIATELY!
OGNL, Olio (2 cycles in a row), Rave, VXQuery (also two cycles in a row) are all missing. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Retire Olio?
I see no development in 18 months. Is it time to terminate? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Retire Bluesky Podling
Bill Stoddard wrote: I would like to see this vote suspended until we can get some feedback from Jack Cai re whether he is willing to be a mentor. I concur that we should suspend this vote pending the outcome of the project's attempt to reboot. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Bluesky calls for a new mentor!
Samuel Kevin wrote: Most of the developers of BlueSky project are students. As you all know, students come when they join in school and go after they graduate. So the active developers are around 10. Like we used to have 5 committers, but now we only have 2 committers in active. As others have pointed out, and I believe you acknowledge (q.v., I am not avoiding the truth that we suck during the last three years), there are better and necessary ways to address this issue. And we've worked with Google every year during the Summer of Code, so we're not exactly inexperienced working with students. According to what you've listed, i would forward your suggestion to bluesky dev list and wish we could make a quick response after discussion. Incorporate all of the feedback you're getting from folks. It is urgent that you take the advice, get all of the current code into source control ASAP, get students onto the mailing list now, start doing discussion and coding in public, and submit changes on a regular basis via SVN and/or JIRA. These are the same things you've also read from Christian and Upayavira. You don't need a new Mentor to do those things. Demonstrate change and we'll try to help you succeed. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Bluesky calls for a new mentor!
Joe Schaefer wrote: Chen Liu wrote: We propose to move future development of BlueSky to the Apache Software Foundation in order to build a broader user and developer community. You are supposed to be doing your development work in the ASF subversion repository, using ASF mailing lists, as peers. Chen, as Joe points out, these are what BlueSky should have been doing for the past three (3) years, and yet we still here a proposal for the future. Looking at the (limited) commit history, there is a total imbalance between the number of people associated with the development work (20+) and the number of people with Apache accounts here (2). Again, as Joe points out, ALL of BlueSky development should been done via the ASF infrastructure, not periodically synchronized. We are a development community, not a remote archive. What we really need you to discuss are *plans*, how you will implement them, who will implement them, and how you will collaborate in the codebase as peers. Joe, again, has this on the money. The BlueSky project must immediately make significant strides to rectify these issues. Now, not later. We should see: 1) All current code in the ASF repository. 2) All development via ASF accounts (get the rest of the people signed up). 3) Ddevelopment discussion on the mailing list. 4) All licensing issues cleaned up. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Retire Bluesky Podling
I don't have Internet access right now, except for ssh to my mail server. Has anyone told the BlueSky project about this vote, yet? I'm +1 for retirement, but feel that part of the process for retiring a project should be notice to the project that retirement is being considered and acted upon. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: KEYS and releases
Chris, This is related to why it also matters how you get and verify your browser. If someone were to successfully distribute a build of Firefox or Chrome with bogus root certs, they could potentially do a lot of damage. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Retire ALOIS podling
+1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Retire Stonehenge
+1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: KEYS and releases
It seems to me to be a bad idea to distribute keys with releases. And don't we already have some ASF-wide policy for managing keys? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [alois] Incubation failed?
If that is the recommendation, check with the community to see if there is any pushback, and depending on result we'll vote on it. Thanks for taking the time to get this going. :-) --- Noel -Original Message- From: Christian Grobmeier [mailto:grobme...@gmail.com] Sent: Tuesday, June 14, 2011 4:18 To: general@incubator.apache.org Subject: [alois] Incubation failed? Hi all, shortly after the last report in March one of the Alois-Devs contacted me and told me, that there will be no further development on the project because of some personal trouble and changes to the company IMSEC (inventor of alois). Even prior march there were only slow steps to observe - website has been established, code has been made accessible via svn (but no more commits) and a few talks has been given. We waited for three more months and there is still no interest in the project: no mailinglist activity, no commits, no new issues. I do not expect any changes to the current situation. I would like to propose Dormant or Retired status for the alois project - not sure what is more matching or what the difference between these two is. Unfortunately I have not found any docs about this process. Any comments to this? Thanks, Christian - 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: Bluesky status and plans (was: Monthly reports missing)
We can take that up with the community. They've certainly had their struggles, but seem to come back sporadically. --- Noel -Original Message- From: sa3r...@gmail.com [mailto:sa3r...@gmail.com]On Behalf Of Sam Ruby Sent: Tuesday, June 14, 2011 6:49 To: general@incubator.apache.org Subject: Bluesky status and plans (was: Monthly reports missing) 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? --- Noel - Sam Ruby - 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)
Sam Ruby wrote: All past struggles aside, if there are no credible plans to produce an ASF project after 2.5 years, then IMHO it is time to begin the process of terminating the incubation of this podling. I'm not arguing that point. As I had replied, we can start the dormancy discussion with them. Do you wish to do that, or ask Bill? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Etch Status?
What is preventing Etch from graduating? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
June 2011 Incubator Board Report
The Incubator PMC now totals 143 members, with some additional requests (joining and a resignation) pending. Recent changes include Peter Royal and Phil Steitz (pending) dropping off; and Shane Curcuru, Srinath Perera, Nicolas Lalevee, Marvin Humphrey, Michael McCandless, Nigel Daley, Tommaso Teofili, Yegor Kozlov, Leif Hedstrom and Steve Loughran joining the PMC. Certainly the biggest thing in the Incubator this month is the arrival of OpenOffice.org for Incubation. OpenOffice.org is going to need significant help and guidance, with an emphasis on liasoning with other, external, projects such as LibreOffice. There is very significant concern regarding how this project will relate to the rest of the Openoffice.org ecosystem, and those will need to be carefully addressed. One of the first challenges for the project will be deciding its scope. If it is going to try to be the old OpenOffice.org, essentially an Apache Licensed coopetitor to the downstream forks; or if it is going to focus on common technologies, release vanilla binaries for key platforms, and let the downstreams take the primary role in delivering end-user binaries. Other issues with respect to OpenOffice.org may challenge our infrastructure. There may also be IP (patent and trademark) issues to address. But the lengthy and diverse list of Mentors should be aware of and preparing to address all of the issues. Despite OpenOffice.org's arrival, and its well than 1000 messages swamping the mailing list, there was more activity than just that one topic. BigTop, a project for the development of packaging and tests of the Hadoop ecosystem, is proposed for Incubation. Flume -- 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 -- was voted to enter Incubation. Sqoop -- a tool designed for efficiently transferring bulk data between Apache Hadoop and structured datastores such as relational databases -- was voted to enter Incubation. There is nascent discussion regarding moving Alois and BlueSky to dormant status. Airavata Airavata is a software toolkit currently used to build science gateways but that has a much wider potential use. It provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. A list of the three most important issues to address in the move towards graduation 1. Finish the security paper work needed to import donated code with cryptographic dependencies. 2. Engage the community by document existing design, drafting detailed JIRA tasks defining smaller goals. 3. Remove incompatible license dependencies and implement over ALV2 compatible libraries. 4. Simplify the build process and provide simple to use cases. 5. At least one Apache Incubator release. 6. Develop a strong community with organizational diversity and well aligned with existing ASF projects as outlined here: http://wiki.apache.org/incubator/AiravataProposal#Alignment Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? The interactions to date have been focused on development, and getting the project started. How has the project developed since the last report? Airavata was voted into the Incubator by the IPMC on May 7, 2011. Suresh Marru is pushing forward on the Airavata website. There is also work going on related to this to define a new Apache Airavata logo. In addition, Suresh led a development roadmap discussion. ALOIS The ALOIS project team wrote an private e-mail to it's mentors shortly after the last report. They have told us that due to personal reasons they cannot keep this project alive and there will be no project activity in near future. We have agreed to wait until the June 2011 comes up. So far there is no change in project activity or interest, no e-mails and even no more private messages. After this report the Incubator-PMC needs to discuss about moving this podling to attic. (Christian Grobmeier) In addition to Christian's report, I'd like to mention that we didn't find any interest in the project outside of our small group, although we did quite a lot requests off list. If there would be someone to take over the project, we would be happy to give a helping hand at the start. (Urs Lerch) BeanValidation Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * Perform successful Releases - Done * Grow the community and committer base - stale at a medium level * Decide on graduation target of TLP or
Hadoop related Incubator projects
There are some which indicate that their sole impediment to graduation is community size. Has there been any consideration of the Hadoop TLP picking them up as sub-projects? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
*** Monthly reports missing ...
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. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept OpenOffice.org for incubation
+1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: FSF Statement on OpenOffice.org's move to Apache
Andrew Rist wrote: I would also point out that this is not a case of moving from Copy Left to Permissive licensing. In this case, the code base is moving from dual-licensing (Copy Left and Proprietary) to Permissive. I made the same point elsewhere. Also, while I appreciate clarification of licensing, the actual removal of non-freely licensed plug-ins hardly increases the freedom of the end-user. It is like banning the use of nvidia drivers for licensing purity. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Vote plans for OOo proposal
Sam Ruby wrote: Unless I see pushback that merits waiting further, I plan to call for a vote approximately 24 hours from now (noon EDT). Please count my +1 vote. I will be traveling, and I don't know what my Internet access will be during the voting timeframe. There are a lot of issues to resolve, but from what I have heard on- and off-line, they can be worked out on the project's own mailing lists. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Remediation ...
Michael Meeks wrote: Robert Weir wrote: But I know with certainty that we've fixed things that LO has missed. (I'm talking patents, not the MPL/LGPL dependency issues). You seem to assert that you have patent remediation patches for problems that others are unaware of, that you can provide, but you are choosing not to (yet) ? There is a nasty nucleus of potential future FUD here, so it would be interesting to firm this perennial rumour up. I heard about this, myself, in some specific detail very recently. I will leave disclosure to the relevant parties, but while it may or may not be an issue for you, IBM did not consider it FUD on their end, and invested in addressing it to their satisfaction. So let's at least, taking a line from one of Simon's recent messages, assume they are a wise and honest conclusion to an earlier conversation until we discover otherwise. Can you comment on your plans, and/or can others comment on ASF policies in this regard ? how are such issues worked through ? Rob has already stated, as quoted by you, that Symphony has done IP remediation at many levels. Where we've worked around things, WE WILL BE ABLE TO CONTRIBUTE OUR FIXES BACK. [Emphasis mine] ASF policy is that our code must be unconstrained, in order to be available for all purposes to all parties. So, yes, we should expect (and require) that IP remediation will happnen in our codebase. * As a European, I rather resent the ethnocentric imperialism implied by trying to export the (terminally broken) US patent system As an American, I wish that you lot would simply up and pass legislation to reject all US Patents on software so that we can get rid of our broken US patent system. Please stop using the meme that software patents make Americans happy. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Remediation ...
Joe Schaefer wrote: I don't see how this has any bearing on the vote. The ASF doesn't require entities to disclose whether or not any particular contribution includes a patent license. We do, however, have the patent clause to ensure that contributed code comes with license for any necessary and owned IP. What would not be covered would be any hypothetical 3rd party patent(s) that might potentially be infringed by a contribution. If at some point there needs to be a discussion about outstanding patent claims regarding the code grant to the ASF, that is best done in the confines of a podling, on the podling's public dev list. Well, started perhaps with ASF Legal, and then discussed as determined appropriate by our lawyers. Which suggests to me that Sam ought to quietly take the lead on this issue, and we should put it aside for the moment. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Remediation ...
Michael Meeks wrote: I rest my case about FUD. It seems hard for me to reconcile your statement with the emphasis around things happening transparently Then let me be equally clear. I've learned not to discuss *potential* legal issues on public lists before first consulting counsel. Akin to the idea that you don't post security vulnerabilities on a public forum before you have a chance to address them. Which is why the rest of my response may have come across as vague. Personally, I'd prefer that we weren't discussing it until it can be investigated. What I can say is that if we (which hopefully will include you), have done everything right in our code base, then everything you take downstream will be clean, as I previously mentioned and you liked. I'd like to say that any remediation would be flagged as such, but I don't know how to make it an iron-clad guarantee. As an American, I wish that you lot would simply up and pass legislation to reject all US Patents on software so that we can get rid of our broken US patent system. As I understand it US patents are not enforceable in Europe and many other jurisdictions anyway That's unclear to me. My hope is that if everyone outside of the US were to outright ban software patents and completely ignore American IP claims on such, that it would remove their value and lead to our abandonment of this dysfunctional system. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Remediation ...
Michael Meeks wrote: It still leaves something you can't answer though: whether it is Rob's understanding of IBM's intention to camouflage such changes or to flag them all openly and clearly. Separating the above from what seems to be the underlying concern. Ultimately with a suite of 8+ million lines, packed with obscure features, and thousands of lines of change a day it is fairly easy to slip things in, to the potential detriment of other users of the code. Wait. How is an IP remediation of potential detriment of other users of the code? I can appreciate your concern over potential submarine patents -- we do have a clause to address that -- but how is REMOVAL of a problem a potential detriment? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Remediation ...
Michael, I agree that the ethical thing to do is to inform partners of such matters, although I still don't know how to guarantee it. And generally speaking, you might want to treat the specifics of such matters in similarly sensitive manner as to how you would carefully handle any potential security related matters that might exist. --- 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)
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: 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
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: 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
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: OpenOffice LibreOffice
Simon Phipps wrote: unless either the Apache project or the LibreOffice project do extremely substantial refactoring very fast, both projects will be using the same code for a long time. If we all do things right, this will be in the context of actual shared repositories. That sounds like a fine scenario. The ASF is good at providing Open Source to be reused downstream. And hopefully (from my perspective, at least) there will be refactoring, or even rearchitecting/rewriting, to enable OOo to better participate in the mobile/cloud arena, with that forming the basis for downstream builds. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: A little OOo history
It seems Apache will have a destination of value in OpenOffice.org. There should be a way to monetize this, similar to how Mozilla monetized their default search engine choice with Google. That'll spawn a whole other set of debates. For example, ASF could take bids and award a contracts to providers who want to serve up OOo code. No, I do not believe that we can, given both our fundemental beliefs in Open Source and our tax status. ANYONE can take the code for ANY PURPOSE, including distribution. But at least part of that question can be run by the lawyers. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice LibreOffice
Simon Phipps wrote: I agree on both counts. My sense continues to be that the best outcome would be close to my original proposal[1], although that got substantial push-back from some quarters. So let's address the push-back. The proposal, as I understand it, is for OpenOffice to exist at the ASF. Push-back that it should move to TDF is just a non-starter, as far as I can see, for those interested in doing OpenOffice under a permissive license. The licensing issue does not go away, so let's move on with the assumption that OpenOffice will happen here. Once we establish that predicate, the question is what happens with collaboration. You and I agree that core development would happen at the ASF. TDF would be a downstream consumer of the core code, and able to incorporate incompatibly licensed code into its unique distribution. Everyone, IBMer, TDFer, and other alike would be welcomed to contribute to the core code, under our license, and to incorporate their own downstream changes under their own license. From that perspective, TDF and IBM are equal players, each with their own enhancements: one set LGPL/MPL, the other closed source. Let us not conflate trademark issues with collaboration on the code. That just defocuses attention from the necessary issues, IMO. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice LibreOffice
Sam Ruby wrote: my suggestion is that we not focus on the differences we have. Let's instead focus on how we can maximize the areas we have in common. Isn't that what: Core development would happen at the ASF. Everyone: IBMer, TDFer, and other alike would be welcomed to contribute to the core code, under our license, and to incorporate their own downstream changes under their own license. From that perspective, TDF and IBM would be equal players, each with their own enhancements. does? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice LibreOffice
Keith Curtis wrote: This AL2 is not within the spirit of the tradition of this codebase because it is invoking a proprietary clause. The Apache License is a fully permissive, inclusive, non-viral, Open Source license. You are entirely incorrect. AL2 will make ongoing code sharing with LO impossible. No, again, you are wildly incorrect. Under the Apache License, TDF has full ability to use all code. The reverse, however, is not true, as 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. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice LibreOffice
Sam Ruby wrote: Noel J. Bergman wrote: Core development would happen at the ASF. Everyone: IBMer, TDFer, and other alike would be welcomed to contribute to the core code, under our license, and to incorporate their own downstream changes under their own license. From that perspective, TDF and IBM would be equal players, each with their own enhancements. 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. You can only lead a horse to water. 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. Perhaps. Prior agreement wouldn't suck, though. :-) Existing developers need to know that they are absolutely welcomed here. I think it is in our best interests to acknowledge that we don't yet have a track record or anything new to offer. In what sense? What track record did we have developing LDAP until the people who wanted to built the Apache Directory Server here arrived? What track record did we have with databases before Derby arrived? The people currently working on the codebase at IBM clearly have a track record delivering their derived product. We've seen other people indicate that they want to join. And the more people with experience on the codebase who join, the more track record we have. The whole point is to build the Community. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Apache Incubator Proposal: Splitting^H^H^H^H^H^H^H^H^HREUNITING the Community?
Volker Merschmann wrote: I've been told that Oracle and TDF *were* in discussions but that the demands by TDF were sufficiently unpalatable to Oracle as to prevent any sort of agreement... IBM may have strongly suggested the ASF as a backup, but we were the runner-up in a sense. Taxes were not an issue... I do not see where the demands were unpalatable: Well, We believe that the MPL (over say an Apache license) as a copy-left license, is crucial to community growth and acceptance, and has proved itself with Mozilla may not have been palatable. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Question to TDF and its community
Niclas Hedhman wrote: For the record; I am opposing this contribution and will vote -1, unless there is a clear indication that TDF/LO is behind it 100% and the two projects are on a trajectory of a merge. I urge TDF to participate, but their participation should not be a prerequisite for us to Incubate a project. I hope I am not alone in thinking that bringing this to Apache without TDF/LO on-board is really BAD for Apache's reputation in the larger software community. We didn't balk when Geronimo was proposed, despite complaints from JBoss. We didn't balk when Felix (nee Oscar) was proposed. We didn't balk in other cases. We have never picked winners, we have incubated projects and let the community pick the winners. I don't see a reason to change our philosophy now. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Summit Proposal - Budget Concerns
Drew, Quick note: I'll be staffing the TDF/LibreOffice table at SELF (Southeast Linux Fest) in Spartanburg, South Carolina this coming weekend. I can't make it for this weekend, but keep me in mind for future, local, activities. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OOo - Lines in the sand and pre-determined conclusions...
Michael, Conclusion: I do not believe the ASF is likely to provide a good home for the OO.o project in the long run. Supporting statements: They are sufficiently confident and comfortable with their model that attempting to negotiate over changing any core aspect of it (such as the non-copy-left stance) is unlikely to be fruitful work. The ASF has a very well designed governance, and a very experienced team, and some excellent licensing for specific situations. I believe that the Apache licensing and policies are for the most part extremely mature, very applicable and effective in certain projects, and fundamentally non-negotiable. I fail to see how you draw the conclusion from the supporting arguments. One can infer from your supporting statements that you see licensing as the issue. But you've failed to draw the connection between the license and your conclusion. As an Epistemologist, I'm kind of interested in such nits. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OOo - Lines in the sand and pre-determined conclusions...
Cor Nouws wrote: Noel J. Bergman wrote (06-06-11 23:51) Conclusion: I do not believe the ASF is likely to provide a good home for the OO.o project in the long run. Supporting statements: [...] Supporting explanation ;-) http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3c4de97e04.20...@nouenoff.nl%3E So, For me it is obvious that this statement is because there is strong involvement in LibreOffice from people that do not want to work with non-copyleft and Apache licence. I agree; you draw the same inference that I do: he means that a non-copyleft license is the reason for (predicted eventual) failure. That attitude is most likely why (IMO) the obvious candidate wasn't used when Oracle decided to transfer OpenOffice. Licensing matters. IBM and others prefer an Open Source license, which allows a level playing field, rather than the inequity of GPL+proprietary, but they are not interested sharing everything. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OOo - Lines in the sand and pre-determined conclusions...
Allen Pulsifer wrote: I think your labels Conclusion and Supporting statements are incorrect To the contrary, Cor indicates that I nailed the matter quite squarely. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Apache Incubator Proposal: Splitting the Community?
Sam Ruby wrote: From my perspective, I think the license discussion is the essential one. TDF is now in the position where it has a historic opportunity to change their license to the Apache License. As I understand it, TDF should certainly be able to replace their original LGPL license from Oracle with the Apache License. But I have questions about their ability to relicense new contributions, based on what I read at http://www.libreoffice.org/get-involved/developers/ and the licensing policy linked from there. It does not seem clear to me that TDF can unilaterally relicense all contributions. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Apache Incubator Proposal: Splitting the Community?
Ian Lynch wrote: Noel J. Bergman: Sam Ruby wrote: From my perspective, I think the license discussion is the essential one. TDF is now in the position where it has a historic opportunity to change their license to the Apache License. As I understand it, TDF should certainly be able to replace their original LGPL license from Oracle with the Apache License. But I have questions about their ability to relicense new contributions, based on what I read at http://www.libreoffice.org/get-involved/developers/ and the licensing policy linked from there. It does not seem clear to me that TDF can unilaterally relicense all contributions. At least to start with they don't need to change anything. No, they don't. But, to re-quote Sam, they now have the historic opportunity to change their license to the Apache License, which makes it much easier to (quoting you, now), cooperate with ASF to make the two projects work as harmoniously as possible. At least some folks at TDF seem to feel slighted by recent developments. I understand, but they should not, at least from the ASF's perspective. TDF did nothing wrong, and there is nothing wrong with TDF. They did the best that they could with the licensing cards dealt to them. That situation has now changed, with the software grant to the ASF and resulting change in licensing. That change is essential to various parties, and while it should not be taken to reflect negatively on TDF, nor can it be ignored. The license is, as Sam said, essential. As Sam said, if TDF is willing and able to relicense, all sorts of frictionless exchange would be possible, and all sorts of divisions of labor could be contemplated. In fact, the division of labor could be dynamic in that we could experiment with all sorts of different arrangements and find out what works best. Which is why I raised the question regarding TDF's ability to relicense all of the contributions it has received. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Apache Incubator Proposal: Splitting^H^H^H^H^H^H^H^H^HREUNITING the Community?
First off, as we've seen with other projects that have gone through Incubation, we have not chosen to avoid areas where others have projects. Simply put, if there is interest from a community, we seek to be supportive. If this proposal goes through, and the ASF chooses to incubate OO.o, everyone will be welcomed. The TDF, individually or en masse, can consider whether or not to join the project. If there is a community split, that decision will rest solely on those who choose not to join our all-inclusive environment. Personally, I would wholeheartedly welcome the TDF joining in on the project. This need not be a miss opportunity to re-unite; it is STILL an opportunity to reunite. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Apache Incubator Proposal: Splitting^H^H^H^H^H^H^H^H^HREUNITING the Community?
Florian Effenberger wrote: Noel J. Bergman wrote: If there is a community split, that decision will rest solely on those who choose not to join our all-inclusive environment. So, if TDF does not join the Apache OOo project, a community split is our (=TDF) fault. However, if the people proposing the Apache incubator project do not join TDF, a community split is not their fault. This looks like a rather one-sided view to me. Look on the positive side, and realize that this is a huge opportunity to reunite the community. That's how *I* choose to view it. That is how Jim, Jukka and Andreas also appear to view it. Charles Schulz also seems to concur that were OO.o's transfer to the ASF have happened right off the bat, we wouldn't be debating the point. I'm sure that we're not alone, despite the fact that we all might wish that this had happened long ago. Charles says that he doesn't want to enter a debate on licensing. But licensing is an elephant in the room. Oracle's move with OO.o will fully open the project to all participants and use-cases, including those who might previously have had to enter into alternate, paid, licensing arrangements with the copyright holder. --- Noel - 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
We already had subversion for some time as the repository for the main code and it didn't work well for a project this size. Tangential to the responses you've already received, I'm curious as to the problems you experienced with Subversion. Our infrastructure team, working closely over the years with the Subversion team, has done wonders to get Subversion working for the ASF. We've often been their canary in the coal mine. :-) --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice.org Apache Incubator Proposal: Splitting^H^H^H^H^H^H^H^H^HREUNITING the Community?
Charles H. Schulz wrote: Noel J. Bergman wrote: Oracle's move with OO.o will fully open the project to all participants and use-cases, including those who might previously have had to enter into alternate, paid, licensing arrangements with the copyright holder. And it comes with arrangements that create issues. Elaborate, please. :-) --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: OpenOffice Apache Incubator Proposal and uniting The Community
Jim Jagielski wrote: Allen Pulsifer wrote: As a long time member of the OpenOffice.org community, I would like to offer my thoughts on the Oracle/IBM proposal. Thanks for the very well-written and well-reasoned post. +1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Board Reports Due -- and missing
Alex, Celix is due in July according to http://wiki.apache.org/incubator/ReportingSchedule Is the automated system supposed to email every month? Or does it follow the schedule and is there something wrong? I was going by what was on the May Wiki page. I just checked the reporting schedule, and also the April report, and see that Celix did report in April, as scheduled. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report May 2011
Incubator Report May 2011 The Incubator continues to accept and graduate projects a pace. This month we have two new projects, one retirement (with two more likely), and one graduation. Imperius has voted to retire. Others are likely to follow (see below). LibCloud is proposed for graduation to TLP status, and presenting to the Board as such. OGNL, a Java development framework for Object-Graph Navigation Language, was accepted for Incubation. Airavata, a project that provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds, has been accepted for Incubation. Bluesky did not report, but did report last month and may not realize it is still on a monthly reporting schedule. DeltaCloud did not report, and is active so they should have reported. HISE and Stonehenge did not report, and both look ripe for retirement. The latter community is actively discussing that this month, but simply failed to report that discussion, and the former appears mostly dead already. --- Incubator Project reports --- Amber Amber has been incubating since July 2010. Amber is a project to develop a Java library which provides an API specification for, and an unconditionally compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications. OAuth is a mechanism that allows users to authenticate and authorise access by another party to resources they control while avoiding the need to share their username and password credentials. The most important issues that must be addressed before graduation are: - Attract users and developers - Generate a release The Incubator PMC / ASF Board should be aware that: - Community activity is relatively low How has the community developed since the last report - Some users have started asking for help or getting started guides on the mailing list How has the project developed since the last report - Fixed some bugs - Removed LGPL licensed files from website Bluesky Did not report (currently on monthly schedule), but did report in April. Clerezza (incubating since November 27th, 2009) is an OSGi-based modular application and set of components (bundles) for building RESTFul Semantic Web applications and services. There are currently no issues requiring board attention. Recent activity: - Added WebId test suite - Added Clerezza-UIMA CAS Consumer - Released a new website version with much more documentation Next steps: - First release - Improve documentation and tutorial to website Top 2/3 Issues before graduation: - Prepare some easy-to-run demos to get people interested in Clerezza Deltacloud Did not report. Is active, and simply failed to report. Droids Droids is an Incubator project arrived from Apache Labs. Droids entered incubation on October, 2008. It's an intelligent standalone robot framework that allows one to create and extend existing web robots. The last three months have been very productive for the project since mailing and issue tracking activity have been very good. Our two new committer have driven our first release which is planed for this month. More people appeared on the mailing list and especially one dev is driving constantly enhancement in our issue tracker. Issues before graduation : * IP clearance HCatalog HCatalog is a table and storage management service for data created using Apache Hadoop. The most important issues in moving the project to graduation are expanding the community of developers and producing a release of the software. Since the last report we have: * got the initial code drop checked in * got the build working for building, testing, and the documents * branched in preparation for a 0.1 release * started development on new features for 0.2 Currently there are 29 subscribers to the user list and 27 on the dev list. There were 14 and 15 respectively last month. HISE Did not report. Appears largely inactive, and perhaps should be retired. Jena Jena was accepted into the Apache Incubator November 2010. It is an existing project migrating to ASF. It has a large codebase that provides a semantic web framework in Java that implements the key W3C recommendations for the core semantic web technologies of RDF and SPARQL. Three most important issues to address for graduation: * Create a code base in Apache with legal clearance. * Establish the Apache-based community for developers, contributors and users * Create and communicate open project processes aligned to Apache Issues for the Incubator PMC or ASF Board: None. Community development: We have started to
Board Reports Due -- and missing
I will be doing it tonight for Thursday's meeting. Missing: Bluesky, Celix, Delta Cloud, HCatalog, HISE, LibCloud (up for a TLP vote, but we still need a report), and SIS. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Retire the Imperius Podling
+1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
JSPWiki, Olio and VXQuery missing
Please submit ASAP. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report April 2011
A remarkably quiet month in general, with no Board level issues. One project, Apache OGNL (http://wiki.apache.org/incubator/OGNLProposal) is under consideration. JSPWiki, Olio and VXQuery did not report. Neither did SocialSite, but that was previously voted into dormant status. --- April 2011 podling reports Apache ACE is a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. ACE started incubation on April 24th 2009. There are currently no issues requiring board or Incubator PMC attention. Community: Angelo gave a talk about massive device deployment and Karl and Marcel did a tutorial about ACE in the Cloud at EclipseCon / OSGi DevCon. We're gathering EclipseCon / OSGi DevCon feedback to populate the roadmap and raise the corresponding Jira issues. Software: A lot of work has been done on the build to fully support Maven 3. We started to work on the documentation also. Use of Apache Karaf as default runtime is in progress. Cloud extensions based on jclouds have been added, including a new launcher. Licensing and other issues: None at the moment. Things to resolve prior to graduation: We created a SVN maven repo waiting for some Felix dependencies release. Make a release. Grow the community some more. BlueSky BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. The following items have been performed since the last reporting period: * test the stability of system on a certain scale. * add the fuanction of recording vedio in the teacher part. The following items are planned for the next reporting period: * go on testing the stability of system Celix Celix is an implementation of the OSGi Specification in C. Celix entered incubation on November 2, 2010. During the EclipseCon a talk was given over Celix, also spoke with several OSGi people who are interested in the progress, especially related to Universal OSGi (which details specification and requirements for OSGi in other languages). During the last few weeks work has been done to get rid of memory leaks and null pointers. Currently we are looking at the requirements/details for bundle deployment and updating, possibly in combination with Apache Ace. Most important issues are: - Define a status overview of what is and isn't working. - Move all sub project to the new structure. - Use APR for all file handling, threading etc. - Generate awareness and grow a community Chukwa Chukwa is a distributed log collection and processing system built on top of Hadoop and HBase. Chukwa is waiting for a official working release of Hadoop 0.2x and HBase 0.9x. There are certain API incompatibility in metrics collection system to prevent them working together. This is a blocker for Chukwa 0.5 release. Chukwa entered incubation on August 5th, 2010. EasyAnt EasyAnt is a tool built on top of Ant and Ivy providing a standard approach to building java projects without locking the users in. Incubating since January 31st 2011 issues/agenda: - 1 ICLA missing. The person does not answer since Feb 4th 2011, when he indicated he was working on getting the ICLA. The svn logs have been gathered and shared between the PPMC members in preparation for a possible cleanup of the svn tree of that person's contribution. activity since last report: - the web site http://incubator.apache.org/easyant/ is published via svnpubsub - while reviewing the licences of the software included in the svn tree of Easyant, some dependency on external LGPL library was found. There are somehow optional to EasyAnt core, but not for the plugin dedicated to the integration of that third library. A consensus was found by the developer community to not release such software under the ASF. Empire-db Apache Empire-db is a relational database abstraction layer that allows developers to take a more SQL-centric approach in application development than traditional ORM frameworks. Its focus is to allow highly efficient database operations in combination with a maximum of compile-time-safety and DBMS independence. Empire-db has entered Incubation in August 2008. Activity since last report: - We have successfully completed and published our 2.1.0 release with few but major improvements. - We have increased your community by taking on a new long-time contributor as a new committer. Important issues to address for graduation: We still need more contributors and more attention in the Java community. Recently we experience increased traffic on the user lists and there are plenty of plans on the development side. The challenge will be
RE: Releases and IPMC votes
ant elder wrote: As long as general@ is included i don't see that any oversight is lost Please note that the original poster's comment was: I was under the impression that *any* mentor is an IPMC member, has a binding +1 vote for releases and could therefore approve of releases WITHOUT HAVING TO GO THROUGH general@ [emphasis mine] We (you and I) both agree on the neccessity of involving general@ to maintain proper oversight. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report - March 2011 [REVISED WITH GORA]
[REVISED TO INCLUDE GORA. I saw that it was already picked up from the mailing list, but wanted to get it into the archives in one place. Thanks to Chris for posting, and Doug for including.] Nigel Daly, Tommaso Teofili, and Alan Gates have joined the PMC since the last report. Howl -- a table and storage management service for data created using Apache Hadoop -- has been accepted for Incubation. It will be renamed first, given that there is an ObjectWeb project also called HOWL. MRUnit -- a library to support unit testing of Hadoop MapReduce jobs -- has been accepted for Incubation. Rave -- a web And social Mashup Engine -- has been accepted for Incubation. BeanValidation and Gora failed to report this period. ALOIS ALOIS stands for Advanced Log Data Insight System and is meant to be a fully implemented open source SIEM security information and event management system. ALOIS is incubating since 22nd October 2010. The following items have been performed since the last reporting period: * Launch of the project website * Code review * Lightning Talk at the CCC Conference in Berlin * Promoting the project on different plaforms * Preparing several talks and booths (Chemnitz, Berlin, CeBIT, ...) Three most important issues to address in the move towards graduation: * Releasing Version 1 * Enlarge the developer base * Creating more use cases How has the community developed since the last report: * Despite the activities no real community so far How has the project developed since the last report: * The code is stable and accessable * The website is online and managed BeanValidation Failed to report. There is some degree of activity on its mailing lists, and addition of new Committers. Bluesky BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. The following items have been performed since the last reporting period: * Now improving the statbility of system * Resolving the problems of having no Screen images * Resolving unstability of the 2nd focus student's data transportation. The following items are planned for the next reporting period: * Improving the stability of the system * add the fuanction of recording vedio in the teacher part. EasyAnt EasyAnt is a tool built on top of Ant and Ivy providing a standard approach to building java projects without locking the users in. Incubating since January 31st 2011 issues/agenda - 1 ICLA missing. The person does not answer since Feb 4th 2011, when he indicated he was working on getting the ICLA. - the code base has been migrated in SVN - the issues are in JIRA with component EASYANT Etch Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. For the last 3 months the main effort has been by Holger Grandy and Michael Fitzner, who contributed some bug fixes and have been converting documentation. The transition of current Etch Website to the new Apache CMS is in progress. Major parts of the sides are already available inside the CMS repository and can be seen at the staging area. The Spawn Labs team (Comer, Dixson) is working to integrate the c-binding into their product. They've been very quiet lately. We miss them. Comer wrote up something about his service cloud and is waiting for permission to publish it. Although progress is now visible, we still need to get more user and development activity on our lists. Top issues currently are: - plan features and dates for release 1.2 / 1.1.1 - work on further language bindings - website transition to Apache CMS - documentation Note by Martijn Dashorst: I met with Holger Grandy and Michael Fitzner at FOSDEM'11 and we spoke about lots of stuff concerning Etch. I think the future for the podling is bright, but we need to get more people involved by publishing articles. The biggest problem is finding the right venues for publishing the articles. I'll bring Etch under the attention of PR to see if they have any good ideas. Gora Gora is an ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop. A list of the three most important issues to address in the move towards graduation 1. Port Gora code and license headers into ASF license headers 2. Develop a strong community with organizational diversity and with infection into existing ASF projects like Nutch and Hadoop 3. At least one Gora incubating release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
RE: Releases and IPMC votes
I was under the impression that *any* mentor is an IPMC member, has a binding +1 vote for releases and could therefore approve of releases without having to go through general@ The issue is allowing proper oversight, and we've felt that it was important to give the PMC as a whole the opportunity to vet the release package(s). Given the frequency with which we have found issues, that seems warranted. Hence ... Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report - March 2011
Nigel Daly, Tommaso Teofili, and Alan Gates have joined the PMC since the last report. Howl -- a table and storage management service for data created using Apache Hadoop -- has been accepted for Incubation. It will be renamed first, given that there is an ObjectWeb project also called HOWL. MRUnit -- a library to support unit testing of Hadoop MapReduce jobs -- has been accepted for Incubation. Rave -- a web And social Mashup Engine -- has been accepted for Incubation. BeanValidation and Gora failed to report this period. ALOIS ALOIS stands for Advanced Log Data Insight System and is meant to be a fully implemented open source SIEM security information and event management system. ALOIS is incubating since 22nd October 2010. The following items have been performed since the last reporting period: * Launch of the project website * Code review * Lightning Talk at the CCC Conference in Berlin * Promoting the project on different plaforms * Preparing several talks and booths (Chemnitz, Berlin, CeBIT, ...) Three most important issues to address in the move towards graduation: * Releasing Version 1 * Enlarge the developer base * Creating more use cases How has the community developed since the last report: * Despite the activities no real community so far How has the project developed since the last report: * The code is stable and accessable * The website is online and managed BeanValidation Failed to report. There is some degree of activity on its mailing lists, and addition of new Committers. Bluesky BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. The following items have been performed since the last reporting period: * Now improving the statbility of system * Resolving the problems of having no Screen images * Resolving unstability of the 2nd focus student's data transportation. The following items are planned for the next reporting period: * Improving the stability of the system * add the fuanction of recording vedio in the teacher part. EasyAnt EasyAnt is a tool built on top of Ant and Ivy providing a standard approach to building java projects without locking the users in. Incubating since January 31st 2011 issues/agenda - 1 ICLA missing. The person does not answer since Feb 4th 2011, when he indicated he was working on getting the ICLA. - the code base has been migrated in SVN - the issues are in JIRA with component EASYANT Etch Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. For the last 3 months the main effort has been by Holger Grandy and Michael Fitzner, who contributed some bug fixes and have been converting documentation. The transition of current Etch Website to the new Apache CMS is in progress. Major parts of the sides are already available inside the CMS repository and can be seen at the staging area. The Spawn Labs team (Comer, Dixson) is working to integrate the c-binding into their product. They've been very quiet lately. We miss them. Comer wrote up something about his service cloud and is waiting for permission to publish it. Although progress is now visible, we still need to get more user and development activity on our lists. Top issues currently are: - plan features and dates for release 1.2 / 1.1.1 - work on further language bindings - website transition to Apache CMS - documentation Note by Martijn Dashorst: I met with Holger Grandy and Michael Fitzner at FOSDEM'11 and we spoke about lots of stuff concerning Etch. I think the future for the podling is bright, but we need to get more people involved by publishing articles. The biggest problem is finding the right venues for publishing the articles. I'll bring Etch under the attention of PR to see if they have any good ideas. Gora Gora is Gora is an ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop. Did not report. Has voted in new Committers. Appears quite active. Hama Hama was accepted into Incubator on 20 May 2008. Hama is a distributed computing framework based on BSP (Bulk Synchronous Parallel) computing techniques for massive scientific computations. == Top 2 or 3 things to resolve prior to graduation == * Complete first release * Invite new active committers == Issues for the Incubator PMC or ASF Board == None. == Community development == * Mailing list shows increased usage from previous report * Chia-Hung Lin has contributed a part
