Re: [PROPOSAL] Accept Wave for incubation
On Tue, Nov 23, 2010 at 12:16 PM, Dan Peterson dpeter...@google.com wrote: Hello all, We'd like to propose Wave for entry into the ASF incubator. The draft proposal is available at: http://wiki.apache.org/incubator/WaveProposal (for your convenience, a snapshot is also copied below) +1 (a bit biased as I was a fan of wave) -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL][VOTE] Subversion
On Wed 04 Nov 2009 12:12, Greg Stein gst...@gmail.com wrote: Initial Committers The list of initial committers is at http://svn.collab.net/repos/svn/trunk/COMMITTERS. The initial PMC members are those listed as full committers in that file (lines 1-74). Sponsors * Champion: Greg Stein * Nominated Mentors: Justin Erenkrantz, Greg Stein, Sander Striker, Daniel Rall * Sponsor: Quite a collection of shady characters, but... +1 :-) -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Libcloud proposal for incubation
On Wed 28 Oct 2009 14:39, Paul Querna p...@querna.org wrote: Libcloud proposal thread went well, and we added several mentors. I would like to start the vote to incubate Libcloud into the ASF. The proposal is included below and is also at: http://wiki.apache.org/incubator/LibcloudProposal Please cast your votes: [ ] +1 Accept Libcloud for incubation [ ] +0 Indifferent to Libcloud incubation [ ] -1 Reject Libcloud for incubation +1 -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Changing poddling release voting process
On Fri 21 Aug 2009 14:58, ant elder ant.el...@gmail.com wrote: What do people think about changing the poddling release voting process so that there is just a single vote which is held on the poddlings dev list instead of the dual voting we have now with a poddling dev list vote followed by an general@ vote? My only concern is that we have some very great volunteers here on the general@ list who check release compliance and I doubt they want to deal with the traffic of every podling dev list. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Thrift release legal issues
On Mon 17 Aug 2009 10:20, Niclas Hedhman nic...@hedhman.org wrote: On Mon, Aug 17, 2009 at 10:04 AM, David Crossleycross...@apache.org wrote: The NOTICE file is not for that purpose. Did you mean to say that you have seen LICENSE files containing pointers? No, I don't mean LICENSE... IIRC (it was not yesterday), the NOTICE file would contain something like; Portions of this software contains Foo from Bar Foundation, which is under the Abc license. See licenses/license.foo That's only necessary if the ABC license requires attribution similar to the Apache license. The NOTICE file is *not* for notifications about other licenses. The NOTICE file is for required attributions as specified in the Apache license. You can put all the licenses or references to the licences in the LICENSE file. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Does an incubation proposal require a codebase?
On Tue 11 Aug 2009 04:06, Upayavira u...@odoko.co.uk wrote: There are two reasons why it is more heavyweight: because we haven't spent huge amounts of time/money automating our infrastructure and putting it behind a pretty web UI, but more importantly because we pay more attention to the legals, ensuring we have grants, CLAs etc, and that we know precicely what piece of code came from where. The infrastructure costs shouldn't dictate policy though. Not to put any more stress on infra, but in an ideal setting, infra wouldn't be an issue. The paperwork is an important feature, but the paperwork also doesn't require an existing codebase. If a group of people want to start a new incubator project and we have sufficient suitable mentors and champions, then I say go for it. Certainly a project without any code deserves a bit more scrutiny, such as have the proposed committers worked on open source previously? but again, I think that's a case by case decision. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: incorrect terminology: lead developers
On Tue 11 Aug 2009 11:28, Greg Brown gkbr...@mac.com wrote: Thanks, Niclas. Very appropriate material. This very clearly draws a distinction between the terms leader (as I have been attempting to use it) and manager (by which I would never describe myself). IMO, successful projects (including those at ASF) need leadership, not management. So describing myself, or any other committer, as a leader is not an attempt to assert authority or otherwise. It is simply a means of describing a level of committment. +1 Projects need people who make decisions and push the code forward, these people are leaders. But that forward direction needs to be done with the awareness, consent and respect by the rest of the committers. We don't want to discourage the energy of someone's vision and volunteer work. At the same time, we need to balance the goal of having many contributors peer review the work and collaborate so that in the long run, the success of the project is not dictacted by any one person. If anything, we can say, projects need leaders, they don't need a project management position. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Mothball/Pause Lokahi
On Wed 12 Aug 2009 12:50, Niclas Hedhman nic...@hedhman.org wrote: PMC and others, Lokahi's community has collapsed long time ago and albeit Noel's repeated efforts to create interest around the project, there is no signs of any improvement. I am therefor calling a vote to mothball/pause the project. Please place your votes. [ ] +1, go ahead and mothball/pause Lokahi, [ ] -1, don't mothball/pause Lokahi, because... (reason is optional, but appreciated) -1 Can we at least ping the lokahi-dev list to let them know the vote is taking place. I know the last time there was any activity on the list was February (and that message was about retiring the project), but still, can one of the mentors at least ping them? Otherwise, I'm fine with retiring the project. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Does an incubation proposal require a codebase?
On Fri 07 Aug 2009 23:52, Bertrand Delacretaz bdelacre...@apache.org wrote: I was imagining a bunch of unknown people coming up with a vague idea for a project, and no code...to that would seem too risky to warrant dedicating resources to a podling. Now, if mentors were enthusiastic about that podling, why not...that's kind of a rethorical question anyway, as in the present case Noah indicates that there is a group of experienced people. Let's see their proposal then, but from what I've seen in this thread I'm positive about it. Exactly, we need a concrete proposal to vote on anything. But to answer the original question: no codebase is initially needed. The incubator is bureaucratic enough as it is, no need to make up new requirements. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incorrect use of Sponsor.
On Sun 05 Jul 2009 02:36, Gavin ga...@16degrees.com.au wrote: -Original Message- From: Bob Schellink [mailto:sab...@gmail.com] Sent: Sunday, 5 July 2009 12:13 AM To: general@incubator.apache.org Subject: Re: Incorrect use of Sponsor. Thanks for the clarification Niclas. I'll update the site. However, you are allowed to have them on the page, just with a 'thanks to ...' , be sure that any external links like these use the 'nofollow' attribute as specified by the PRC (so as to not water down the value of the main ASF thanks page.) We put `nofollow` on the Bronze level sponsors and that was to stop the sponsorship program from turning into a spam-ridden link farm. I don't recall the PRC requiring other links to use nofollow, but perhaps I missed it. Lots of projects have lists of companies which provide commercial support or powered by sites. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Mentors role after Graduation?
On Thu 02 Jul 2009 16:39, Upayavira u...@odoko.co.uk wrote: I would like to clarify whether Mentors are expected to be on the PMC of a TLP graduating project or not. Someone told me that some podling in the past was requested to do so, while I personally have declined to be on any PMC I have mentored so far, although I have stayed on as an ASF Member observer at an arm's length to step in with advice, assistance and help if needed, for a 6-12 month period. I think it is important to have some representation of the ASF membership on a PMC. Perhaps the gauge is to stay on, as a member of the PMC, until the PMC starts to breed its own ASF members. +1 Podlings should be able to choose their own PMC and do not need an ASF member on that PMC. However, it's useful to have at least one member, such as a former mentor, around on the private@ list to answer questions. New TLPs have a VP who can go directly to the board, so it's not like they're completely on their own, but at least having someone subscribed to the private@ list can help. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal][Vote] Traffic Server
On Fri 03 Jul 2009 07:03, Leif Hedstrom l...@yahoo-inc.com wrote: Good evening, As you know, we've been preparing our proposal to submit Traffic Server to the Incubator for a few weeks now. With the help from our champion (thanks Doug!), and the entire Incubator community, it's my pleasure to submit a request for Traffic Server to be accepted into the Incubator. The proposal is attached below, and is also available on the Wiki: http://wiki.apache.org/incubator/TrafficServerProposal Since our first draft, we've added a number of mentors and contributors, and also added and improved on the proposal. I would like this to be considered our official application, and that the Incubator votes (+ or -) on our acceptance as a podling. +1 -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Community readiness-when does it show?
On Wed 24 Jun 2009 06:08, Martijn Dashorst martijn.dasho...@gmail.com wrote: My current issue is with the definition of open. Not necessarily as documented (haven't looked at the text lately), but as a gut feeling: when is a community open? - all (technical) discussions happen on publicly archived lists - conflicts are resolved in a civil and respectful manner But also: - the podling is able to identify new, valuable contributors and add them to the project From http://incubator.apache.org/guides/graduation.html: Apache projects are self-sustaining and self-governing communities. Long term success and health requires that these communities understand how to: - recruit users, developers, committers and PMCers - take responsible collective action - disagree in public on technical matters without destroying personal relationships - create an open, positive and inclusive atmosphere on the mailing lists Often podlings have to add at least one new committer just to meet the diversity requirement of at least 3 'independent' committers. Adding at least one committer has always been a litmus test for any podling I've worked with. As of a year or two ago when I last looked at the statistics, most podlings only ever add one committer during incubation. If a community meets all the criteria, but hasn't discovered a new committer (or two) by itself, is the community ready for graduation? If not, how can we—mentors— nudge the community to focus on this thing, without it becoming an exercise in checking the check marks? There are at least two scenarios: - The podling has attracted new contributors, but not made them committers - The podling has not attracted any new contributors since starting incubation In the first case, it's simply a matter of helping the podling committers be comfortable giving out commit bits. Sometimes the barrier to becoming a committer has been made too high. The second case is much more difficult. It might involve working with PRC to get a bit of press or marketing. It might involve making sure one or more of the committers go to ApacheCon to meet other ASF committers and potential users. If there's a user community, but no contributors, then the committers have to learn how to better engadge the community: asking for bug fixes, encouraging users to work out a patch themselves rather than just fixing it, putting together better documentation, etc. In either case, it *is* important for the project to learn how to add committers. If the podling leaves the incubator with the commit bit barrier too high, they'll have problems down the road. If they leave the incubator with users but no contributors, they're also going to have trouble. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MISSING REPORTS] Droids Lokahi SocialSite WSRP4J
On Mon 18 May 2009 14:56, Bertrand Delacretaz bdelacre...@apache.org wrote: See http://wiki.apache.org/incubator/May2009 - those reports are overdue. WSRP4J missed the report completely this month. They should include a report next month. -- J. Aaron Farr 馮傑仁 www.cubiclemuses.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: New Incubator Proposal: Null - A cloud-aware Web 3.0 Container
On Wed 01 Apr 2009 14:02, Upayavira u...@odoko.co.uk wrote: On Wed, 2009-04-01 at 07:23 +0200, Felix Meschberger wrote: You'll find all the details here: http://wiki.apache.org/incubator/NullProposal Now, currently we are looking for interested parties. So if you are interested in this proposal, please add your name to the wiki page. If anything is missing/unclear etc. let's discuss it :) My wholehearted +1. I'll mentor it. +null This could be the next big thing at Apache after: http://markmail.org/message/iz6ejtre3dwtfgdo You know, the subversion classloader was a *great* idea. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: UIMA [WAS Re: Suspending Projects]
On Fri 20 Feb 2009 17:23, Thilo Goetz twgo...@gmx.de wrote: Can you perhaps contact these individuals one-by-one and get their view on how they see it. Perhaps ask them to publish their work in parallel, and perhaps the 'OSS bug' will bite a couple of them?? I have talked to quite a few of them, and I'll keep hitting on them :-) Keep in mind that it's up to the project to define what warrants becoming a committer and that doesn't necessarily have to be due to significant code contributions. It can also include documentation, handling releases, and so on. Generally, someone who is willing to regularly help, review and commit to the project can be brought on. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Could someone create the JIRA project for ESME?
On Fri 05 Dec 2008 15:26, Bertrand Delacretaz [EMAIL PROTECTED] wrote: Hi, I don't think I have karma to do that, could someone create an ESME project in JIRA? Please also add me as an admin of that project, username bdelacretaz I've created it and added you and the mentors. We need the new committers to create accounts: https://issues.apache.org/jira/browse/ESME -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept ESME into the Apache Incubator
On Wed 26 Nov 2008 11:10, Darren Hague [EMAIL PROTECTED] wrote: Hi Aaron, Are we ready for the next steps of accepting ESME into the Incubator? The Apache Incubator general mailing list seems to have been quiet since Saturday 21st November, so I'm not sure if there's a problem with the mailserver somewhere or if people are just getting ready for Thanksgiving in the USA. Probably Thanksgiving. I can help close up the vote. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept ESME into the Apache Incubator
On Sun 16 Nov 2008 14:12, Darren Hague [EMAIL PROTECTED] wrote: Having proposed ESME for inclusion in the Apache Incubator two weeks ago (http://wiki.apache.org/incubator/ESMEProposal), comments have now died down. The feedback we have had has been constructive and positive, we have a Champion in J. Aaron Farr, and five mentors have signed up: + J. Aaron Farr + Bertrand Delacretaz + Daniel Kulp + Gianugo Rabellino + Sylvain Wallez I think that now is the right time for a vote, so please vote +1 to accept ESME into the Apache Incubator, or -1 (with comments) if you think ESME should not be in the Apache Incubator in its present form. +1 let's keep the vote open for another day or so, so that more incubator pmc members can vote. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] ESME - The Enterprise Social Messaging Experiment
Darren Hague [EMAIL PROTECTED] writes: I would like to propose ESME as a project for the Apache Incubator. Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME is written in Scala and uses the Lift web framework. Please see http://wiki.apache.org/incubator/ESMEProposal for details. Since this is my first Apache project, any and all feedback is welcome Welcome! Just want to add that I've volunteered to Champion and mentor this project. We're still looking for other mentors. I will call for a vote a few days after relevant messages on the list reduce to a trickle and people seem happy with the proposal. With ApacheCon this week, we'll want to give this a little extra time. I'd wait to hold a vote until next week at the earliest. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL - OpenWebBeans Project Proposal]
Gurkan Erdogdu [EMAIL PROTECTED] writes: Hi to all; I have posted a proposal about the project, named OpenWebBeans. It is in the WIKI, its address is http://wiki.apache.org/incubator/OpenWebBeansProposal I have a number of questions before I can support the proposal: Where do you expect this code / community to end up after the incubator? Will it be part of Geronimo? Part of MySpaces? It's own TLP? I can say now that if the project is to stand on its own, then there's a lot of work to do. It seems as though there are 2 or 3 other Apache licensed efforts in creating a RI for JSR-299: Gavin King's work, JBoss's work and the rumored Guice work. What makes this RI effort any different? Why should the ASF support this project instead of one of the others? I'm concerned that there's only one listed committer. Getting to at least 3 committers is going to have to be the first order of business for this podling. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Allow incubator releases?
William A. Rowe, Jr. [EMAIL PROTECTED] writes: Niclas Hedhman wrote: I will support the initial intent of no releases out of Incubator. Which would work, except for the fact that the incubator decided it's a good idea to have podlings demonstrate how releases work in a meritocracy. Sure they've grokked vetoes over code, but the majority-vote release schema is nearly at odds with that. It's good that they demonstrate the entire cycle of envisioning ... creating ... collecting ... releasing code as a community. +1 So this is a better schema. Drop any pretense that the incubator has a say over the already-done code releases, and we can seriously start the real discussion, which would have been motivating projects to graduate if we hadn't wasted several hundred posts on a silly topic. This is simple, people. This is what mentors are for. When the PMC submits the board report, someone should mark the ones that need motivating and task the mentors with doing so. If the mentors can't (which is fine, we're all volunteers here), then delegate to someone who can. As for motivation, escaping the neverending threads on this mailing list should be encouragement enough. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] accept Droids into incubation
Thorsten Scherler [EMAIL PROTECTED] writes: Please vote on accepting Droids into incubation. +1 -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Putting a visitor tracker on incubator project web site.
Edward J. Yoon [EMAIL PROTECTED] writes: Hello community, We'd like to put a google analytics visitor tracker on our (Hama) web site. Is there a limit to put a visitor tracker on incubator project web site? A similar request was just discussed at the board meeting today. We need to review the google analytics terms of use and also the matter of who has access to the analytic data (is is public? restricted to PMCs? and so on.) There should be a discussion starting on the site-dev list today or tomorrow to figure this out. So, short answer is: not yet, but a lot of people like the idea and we just have to work out the details. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept CouchDB for incubation
Sam Ruby [EMAIL PROTECTED] writes: We've had an initial discussion, which attracted a number of messages of encouragement, and identified no issues or concerns. Then we proceeded onto a proposal, which attracted three excellent mentors. Now it is time to vote on the proposal which can be found on the Apache Wiki, and reproduced below. I would like to proudly start this off with my +1. - Sam Ruby http://wiki.apache.org/incubator/CouchDBProposal +1 Very excited to see CouchDB here. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] as to Thrift Proposal
On Jan 23, 2008 9:07 PM, Mark Slee [EMAIL PROTECTED] wrote: Hi all, We've just posted the Apache Incubator proposal for Thrift onto the Wiki: http://wiki.apache.org/incubator/ThriftProposal +1 -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Thrift
David Reiss [EMAIL PROTECTED] writes: J Aaron Farr wrote: git could be an issue. Can you explain what the issue is with Git? Leo already gave a decent explanation. Basically, it comes down to two aspects: 1) infrastructure support 2) cultural bias There's no No git rule that I know of, so in theory, it could be possible. In practice, you'll get some resistance. One aspect of resistance will be from the infrastructure team. SVN is basically the standard here, we have experience with it and we can support it well. Due to painfully learned lessons, our infra team (mostly volunteer) tends to be very conservative about adding new tools to our stack. That said, no one wants to arbitrarily stand in the way of a project, so there's some give and take, some flexibility. The point is, this is something the Thrift committers would have to work out with the infra team. I don't see it as a show stopper from this respect, but I hope you understand why this could cause some friction. The second issue is cultural. One concern we've had about distributed version control is the lack of a central repository which _requires_ committers to cooperate and communicate. This deficiency is seen as a feature by many in the Apache community because it encourages people to work closely together and it also makes clear which bits of code are blessed by the community at large. That said, the workflow you describe sounds great. Many of us have used distributed version control systems and there's been idle talk about it now and then, so this attitude could change, particularly if a project could demonstrate how to avoid the potential pitfalls. Hope that clears things up a bit. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept PDFBox for incubation
Jukka Zitting [EMAIL PROTECTED] writes: Incubator PMC, Please vote on accepting the PDFBox project for incubation. The full PDFBox proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/PDFBoxProposal. We ask the Incubator PMC to sponsor the PDFBox podling, with myself, Jeremias Maerki, and Niall Pemberton as the mentors. The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. [ ] +1 Accept PDFBox as a new podling [ ] -1 Do not accept the new podling (provide reason, please) [X] +1 Accept PDFBox as a new podling -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] CouchDB incubator project
Sam Ruby [EMAIL PROTECTED] writes: The original source for this proposal can be found at http://www.couchdbwiki.com/index.php?title=Apache_Incubator_Proposal and a current snapshot is attached below. Once we have established that there is interest, my plan is to move this content over to wiki.apache.org/incubator as a [PROPOSAL]. I've been watching CouchDB since September, and believe that it would fit well in the ASF. My preference is that it exits as a top level project, mainly due to my experience with umbrella PMCs, but I would otherwise not be adverse to it joining the DB project. We certainly do not need to decide this now. +1 I really wish I had the time to help mentor this directly, but instead I'll probably have to lurk on the list. CouchDB caught my eye back in March of last year, but Damien had just joined MySQL at the time and wasn't interested in changing the license from GPL. Glad to see it make it to the incubator. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Thrift
Mark Slee [EMAIL PROTECTED] writes: Anyone have feedback? If no objections are voiced, when would it be appropriate for us to move forward with a VOTE thread on this? Sorry for not responding. I flagged the email when I first saw it but didn't have time to respond. Overall the proposal is solid and I think Thrift would be a great Apache project. The issues of committer diversity should be handled during incubation. I also agree with others that you'll find there's really no need to introduce internal commit barriers. This sort of problem tends to work out on its own. However, if there are real concerns about this, it can done. git could be an issue. Finally, I'd love to help mentor this, but I'm already mentoring two other projects. I would like to at least lurk on the mailing lists. I'm doing some Facebook app development now and I'd like to better understand some of the code that's running behind those servers. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving a failed incubation project
Noel J. Bergman [EMAIL PROTECTED] writes: When forking Apache licensed code, one does _not_ need to change the package name, or anything else in the source code. One arguably shouldn't then re-publish the binaries or source as Apache Foo [1], but the code itself can use the same namespace. there is no legal requirement to [rename the package space] Again, unless you've a law degree that I missed recently and are ASF counsel of record, I would suggest that no one attempt to dispense legal advice. Didn't get the law degree yet. :-) Sorry if I came across short to anyone. I _did_ read the whole thread before responding and I have forwarded a note to legal-discuss and prc. The legal committee has previously been tasked with a fork FAQ that would cover this and the PRC team is currently working on a trademarks FAQ that should also cover this. I agree that the proper thing for forks to do is change the namespace and it's reasonable to (politely) request this. However, beyond a request we're on shaky grounds. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving a failed incubation project
Assaf Arkin [EMAIL PROTECTED] writes: On 1/22/08, Craig L Russell [EMAIL PROTECTED] wrote: I think the terminology in the subject is wrong. You are not moving a failed incubation project. That project is dead. What you can do is to use the code in another project, and assume all responsibility to verify that the license in the code is correct. What you can't do is to use the Apache brand for another project, meaning to use the package names including apache if it's not an Apache project. If I were to fork an Apache project, at what point would I have to rename packages? I can't find anything that says so in the license. I'm ignoring the trademark use because a) the license gives permission to reference Apache in my source files, b) which is not by itself branding, and c) and there's nothing explicit about package names. Assaf is correct. Moving a failed incubation project = fork. When forking Apache licensed code, one does _not_ need to change the package name, or anything else in the source code. One arguably shouldn't then re-publish the binaries or source as Apache Foo [1], but the code itself can use the same namespace. If the fork wishes to do more than patch up the original or wishes to create its own identity unique from the Apache original, then it would be wise to rename the packages, but there is no legal requirement to do so. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 [1] this is trademark, not copyright issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Business Framework Project
Ahmad Khalifa [EMAIL PROTECTED] writes: Ultimately, what this would be good for, is to offer several pre-built applications along the lines of CRM, ERP, Accounting, POS, etc... just like some already available applications, but the extra customization features would make it much more adaptable/extendable to organizations, and much easier to extend to more business domains. I understand it's technically different from OFBiz, but have you looked at Apache OFBiz? Would it be something that team could use? http://ofbiz.apache.org/ -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Synchronizing PMC Membership rosters
sebb [EMAIL PROTECTED] writes: Just wondering whether Labs would be a suitable place to collaborate on scripts for cross-checking/reformatting the meta data? Also to document the current meta data. Technically the incubator PMC should be free to create a new subdirectory under /incubator in svn. But if you don't want to do that, then, yeah, a lab is fine. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Bluesky Project into the Incubator
Bill Stoddard [EMAIL PROTECTED] writes: Thanks to everyone who made contributions to this proposal and special thanks to Niclas and Aaron for stepping up as mentors. The project is documented here: http://wiki.apache.org/incubator/BlueSky Please vote on accepting Bluesky into the Apache Incubator. The vote will run 1 week, beginning now, and will conclude Saturday, January 12, 2008. [X] +1 Accept BlueSky for incubation -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept project Buildr for incubation
Jim Jagielski [EMAIL PROTECTED] writes: On Oct 29, 2007, at 5:29 PM, Matthieu Riou wrote: Also we're missing one more mentor so if someone could volunteer, that would really be great. Count me in. Jim beat me to it. :-) I'll be keeping an eye on the project as well though. Please vote on accepting Buildr into the Apache Incubator. This vote will run until Thursday November 1st at 3pm PST. [X] +1 Accept Buildr project for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason : +1 Good to see some Ruby code coming into the foundation, even if it is for compiling Java. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [apachecon eu'08] Guide to successful incubation at the ASF
Martijn Dashorst [EMAIL PROTECTED] writes: I just sent a proposal to the apache con CFP for a presentation on successful incubation. Unfortunately the title was submitted wrongly, and the apache con site doesn't allow editing of the title of a submitted proposal. Cool. I did a couple of talks on open source communities and the incubator at OSCON and ApacheCon. You can find the slides at: http://www.cubiclemuses.com/cm/files/incubating_communities.pdf http://www.cubiclemuses.com/cm/files/incubator.ppt Feel free to use anything that might help. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Java Jabber Server
Petar Tahchiev [EMAIL PROTECTED] writes: Hi guys, today I was looking for a Jabber server implemented entirely in Java, and the only results that I got was this: ---(free)--- http://www.codecobra.com/chime/ http://www.open-im.net/ OpenIM was originally developed using Apache Avalon containers and now uses Plexus (which is entering incubation). The developer, alag, was a regular on the mailing lists at the time. I'm not sure how active the project is today (looks like it's moved to Codehaus). It's under the MIT license. And while I haven't used this particular feature of ActiveMQ, it does advertise XMPP support: http://activemq.apache.org/xmpp.html -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request to accept the Sling project for Incubation
Jukka Zitting [EMAIL PROTECTED] writes: As described in [1], please acknowledge this request to enter the Sling project into incubation. The Jackrabbit PMC has voted (see the vote request [2] and results [3]) to approve the Sling project (see the proposal [4]) for incubation. +1 -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Sling
Jukka Zitting [EMAIL PROTECTED] writes: Hi, On 8/17/07, Jukka Zitting [EMAIL PROTECTED] wrote: Anyone interested in mentoring Sling? Still looking for a third mentor, preferably from outside Day. I guess we could also go forward with just two mentors for now, given that we have two other IPMC members (Carsten and Bertrand, both from Day) as initial committers, so release votes and other such stuff shouldn't suffer from lack of IPMC interest. I'll help. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator new committer redux
Craig L Russell [EMAIL PROTECTED] writes: The thread has died down with no consensus, so I'm going to try again. I apologize for being absent from these threads for the last month. Life got busy and one of the things that got dropped was the incubator general list. I don't want to rehash everything that's been discussed before, but here's my opinions as an IPMC member: I'd prefer that the decision making stays close to the PPMC. If we need the IPMC to check off on PPMC decisions, fine. That should be possible via the mentors. But let's not make this any more bureaucratic than necessary. Thus I'm in favor of only ONE vote. Furthermore, I'm not completely convinced by Noel's argument that the PPMC is a figment of our imagination. Sorry, Noel, don't mean to pick on you here. :-) My point is, if the IPMC choses to delegate committer voting responsibilities to PPMCs, then the PPMC votes are just as 'binding' as IPMC votes. AFAIK, there's no legal barrier for this to happen, only procedural ones. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Graduation Apparel] Logo
robert burrell donkin [EMAIL PROTECTED] writes: On 5/14/07, Noel J. Bergman [EMAIL PROTECTED] wrote: Jim Jagielski wrote: robert burrell donkin wrote: we could do a cracked-eggshell motif as logo With a feather peaking out :) Cool idea! :-) sounds good to me 1 anyone have any alternative/improvements? 2 any volunteers for the creation of the logo art? Something like this? http://people.apache.org/~farra/graduated.png I can do a few other variations. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] Retire Heraldy from Incubator
The vote to retire Heraldry from the Incubator as PASSED. Voting +1: 16 (14 binding) J Aaron Farr Matt Pelletier Davanum Sirnivas Robert Burrell Donkin Justin Erenkratz Niclas Hedhman Alex Karasulu Bertrand Delacretaz Dan Quellhorst Ted Leung William Rowe Noel J Bergman Leo Simons Brian McCallister Jean T Anderson Craig Russell Voting -1: 0 Again, thanks to all who participated! -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Retire Heraldry from incubation
J Aaron Farr [EMAIL PROTECTED] writes: This is a vote to move the Heraldry project from active incubation to 'retired' status. Earlier this year the Heraldry project was reorganized in order to make another attempt at incubating an OpenID project. Unfortunately, the reconstituted podling has been unable to reboot and the remaining committers agree that termination at this time is in the best interest of all involved. Details of these matters can be found on the public Heraldry dev list, in particular the Recharter and SVN thread in May [1]. I want to thank all the committers and mentors, both past and present, for their efforts in the Heraldry project and I especially wish the committers success in their furture efforts. As with any retired or domant open source project here at Apache, should a future team of developers be interested in picking where others left off, they may do so by forming a proposal and emailing the Incubator PMC. Please vote for the Heraldry Podling Termination: [ ] +1, terminate the Heraldry podling and move to 'retired' [ ] -1, do not terminate the podling at this time +1 -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Retire Heraldry from incubation
This is a vote to move the Heraldry project from active incubation to 'retired' status. Earlier this year the Heraldry project was reorganized in order to make another attempt at incubating an OpenID project. Unfortunately, the reconstituted podling has been unable to reboot and the remaining committers agree that termination at this time is in the best interest of all involved. Details of these matters can be found on the public Heraldry dev list, in particular the Recharter and SVN thread in May [1]. I want to thank all the committers and mentors, both past and present, for their efforts in the Heraldry project and I especially wish the committers success in their furture efforts. As with any retired or domant open source project here at Apache, should a future team of developers be interested in picking where others left off, they may do so by forming a proposal and emailing the Incubator PMC. Please vote for the Heraldry Podling Termination: [ ] +1, terminate the Heraldry podling and move to 'retired' [ ] -1, do not terminate the podling at this time -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 [1] http://mail-archives.apache.org/mod_mbox/incubator-heraldry-dev/200705.mbox/thread - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Request for Comments - Pnuts as Incubator Project?!]
Hello Siegfried! Siegfried Goeschl [EMAIL PROTECTED] writes: since I'm basically an ASF newbie I would like to ask for some feedback if you would think pnuts as suitable candidate for an incubator project. Your feedback would help me a lot convincing the pnuts community to move over to Apache. Has the community expressed any interest already? And how much community is there beyond Tomatsu? While a existing, active community isn't a requirement to enter incubation, it is a requirement to exit. So my concern is that pnuts has been around for a while, yet not attracted much of a community (at least that's my perception and it could be wrong). Again, that alone isn't enough to stop a proposal, just something to consider. It's possible that pnuts is more suited for a place like codehaus than Apache. On a related note, there are a ton of JVM languages now. I wouldn't want to give the impression that a specific one is sanctioned by the ASF. In fact, I think it would be cool to see several JVM languages and related research in Apache. I mean, we have a VM now (almost). That could foster some really interesting harmony. :) -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: housekeeping ( was Re: [Vote] Graduate Trinidad (to an Apache MyFaces subproject))
Matthias Wessendorf [EMAIL PROTECTED] writes: So, I'll provide a larger patch next days. Clean up: -adffaces/trinidad -felix (have the graduated?) -roller -kabuki More ? :) I just commited a change to the source file that updates all the missing start/end dates for graduated projects. In case anyone is interested, incubation averages just under 10 months with a floor of 4 months and a ceiling of 18. What I'm trying to gather next is an averge number of committers added during incubation. Since some projects incubated before or during the SVN switch, I haven't completed this. Many projects add no new committers beyond the proposed original. Those that do add committers only add 1 or 2. The major expection to this was Heraldry which added 10 committers. I thought it would be interesting to see if the actual metrics live up to what we perceive the incubator as doing. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Missing update for site-publish?
Craig L Russell [EMAIL PROTECTED] writes: When I updated my incubator trunk repository, I noticed [1] that there is an update for site-author/projects/index.html without a corresponding update for site-publish/projects/index.html. I can fix this by committing the site-publish/projects/index.html change, but I thought I'd ask if there is a reason for the inconsistency... That was me. I just updated the dates on index.xml without publishing it yet. I noticed the 'housekeeping' thread and figured I'd wait to publish until other changes were in. Sorry for the confusion. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Approve changing escalation to graduation in Incubator Policy
+1 Craig L Russell [EMAIL PROTECTED] writes: [ ] +1 approve the patch to change escalation to graduation in Incubator Policy [ ] -1 don't approve the patch I've attached the JIRA reference [1] and formatted html page [2] so you don't need to apply the patch to see what it will do. There are broken links because the page is not in its preferred location but the text is complete. [1] https://issues.apache.org/jira/browse/INCUBATOR-53 [2] https://issues.apache.org/jira/secure/attachment/12355574/ Incubation_Policy.html Craig Russell DB PMC, OpenJPA PPMC [EMAIL PROTECTED] http://db.apache.org/jdo -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ApacheCon - session] Incubating Open Source Communities
Matthias Wessendorf [EMAIL PROTECTED] writes: there is a session, called Incubating Open Source Communities by J. Aaron Farr. Is this a similar session, like we did in Austin? Or a *general* session on the Apache Incubator? (there is no link available on the website, therefore the mail...) It's a general session, similar to one I gave at OSCON last year. The intention is to share lessons learned from the Incubator as well as introduce the general policies of ASF Incubation. I did like the Incubator Lightening Talks at Austin though. It'd be nice to see them again. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Revised Heraldry ACL
Ted Leung [EMAIL PROTECTED] writes: [ ] +1 accept the new Heraldry ACL and PPMC [ ] +0 no opinion [ ] -1 do not accept the new Heraldry ACL (thereby terminating the Heraldry podling) +1 -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Revised Heraldry commit ACL
Ted Leung [EMAIL PROTECTED] writes: I would also point out that I am currently the only mentor for Heraldry, and I'm not willing to continue without some other people jumping in to help. When I originally agreed to mentor Heraldry, I did it thinking that I was one of three mentors. I'm willing to mentor if you still need an extra set of eyeballs. However, outside of what has leaked onto general@ and private@, I haven't followed Heraldry. I'm not sure if that counts as a pro or con. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: March Board reports due
Noel J. Bergman [EMAIL PROTECTED] writes: Has anyone other than me reviewed these reports? We had gotten extra time due to the Board rescheduling its meeting, which is why I haven't been pushing, but I'd like to post the report by Sunday, preferably on Friday (I'll do another pass through of my own on Friday, and mark them off). I've read through them all. Woden's is a little brief, the rest seem fine. And if the ReportingSchedule is accruate, we're missing: * mod_ftp * log4net * log4php * OpenJPA -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Killing the incubator m2 repository
Noel J. Bergman [EMAIL PROTECTED] writes: Jukka Zitting wrote: Agreed. Once a release is out the only restrictions we place on it's use and distribution should be the ASLv2. The Apache License does not give ASF projects carte blanche to ignore ASF policy. But Jukka is right in that we, the ASF, can only restrict the redistribution by third parties of an incubator release to those stated in the ASL. In other words, if someone other than an Apache project were to load the incubator releases into a maven repository, I'm not sure what the ASF Incubator could do about it (other than express disagreement). -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Killing the incubator m2 repository
Davanum Srinivas [EMAIL PROTECTED] writes: #1) End user using an Incubator podling m2 artifact directly: End users need to specify our repo in their pom.xml explicity. this is a conscious decision. #2) End user using a regular Apache project that depends on incubator podling artifact: End users won't have to touch their pom.xml and the podling jars are automatically downloaded. So we lose the benefit here. *BUT* here's what we can do to make #2 a conscious decision. Say Axis2...we depend on woden. If we mark woden jar with scope=provided [1], then the end user has to do a conscious import just like they did in #1. So there is a way to enforce the policy if we wish. The end user in situation #2 is trusting the Apache project (ie- Axis) and shouldn't have to care whether it includes incubating code. Just as the user shouldn't have to deal with separate downloads if, say, Axis includes MPL licensed code as per the legal guidelines. The PMC made the decision to trust the incubating code and released it. If the PMC feels it needs to warn it's users, it should include something in it's release documentation. (Axis PMC here just being an example of _any_ TPL PMC). -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incentive for Graduation
Davanum Srinivas [EMAIL PROTECTED] writes: Niclas, Here the scenario is a project with all committers from one employer and regular releases. Then they shouldn't have regular releases. I think Niclas's suggestions on community requirements for releases are fine, particularly for podlings that have been incubating for some time. The incubator, as it stands, is a big stick. Getting out (as Bill points out) is a carrot all of its own. If the mentors think a project has lost it's incentive, then they need to discuss the issue with the committers and put together a solution or look at termination. It's not that hard of a problem. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Difference between Maven repository and dist directory
Craig McClanahan [EMAIL PROTECTED] writes: Is everyone in ASF willing to be comfortable with the ASF stamp of approval on a project that might still be in the process of vetting code provenance, or still checking licenses, but chooses to do an incubating release anyway? No, of course not. But that shouldn't be happening anyway. It is the responsibility of the Incubator PMC that all podling releases meet requirements for an ASF release. If they don't then the release should not be allowed. The release ritual is an important one for Apache projects, incubating or otherwise. IMHO no podling should graduate without going through that process -- it's part of learning about how the ASF operates. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Should we treat incubator releases differently to normal releases
Henri Yandell [EMAIL PROTECTED] writes:
Two parts to the vote:
ONE: Should Incubator tarballs go in the normal place (and thus mirrors).
YES (+1)
Assuming normal place means something like dist/incubator not /dist/{podling}
TWO: Should there be an Incubator maven repository.
+0
--
jaaron
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: New project by committer...
Noel J. Bergman [EMAIL PROTECTED] writes: Davanum Srinivas wrote: Niclas Hedhman [EMAIL PROTECTED] wrote: I would like to start a new project in the incubator. It will be a from scratch effort, and I have some friends who are eager to help out. please see http://labs.apache.org/ Apache Labs isn't appropriate for his effort, since it seems that he wants to build a new community, which will not be exclusively existing Committers. Funny, because I would still recommend labs, at least for a from-scratch effort. New committers can submit patches and as soon as Niclas shows he as a decent following, it should be straight forward to bump it out of labs and into the incubator. This was partly the whole point of labs... to cut the red tape necessary for these sorts of things. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Tika - a content analysis toolkit
Jukka Zitting [EMAIL PROTECTED] writes: Please vote on the proposal that follows. The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. [X] +1 Accept Tika as a new podling Good luck! -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Tika, a content analysis toolkit
This is a proposal to start a content analysis toolkit project in the Apache Incubator. The live version of the proposal is available at http://wiki.apache.org/incubator/TikaProposal. +1 Looks like a good fit. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: March Board reports due
Noel J. Bergman [EMAIL PROTECTED] writes: This month's ASF Board reports should be written up on the wiki at http://wiki.apache.org/incubator/March2007 River and Woden are not nearly detailed enough. We need status, issues required for graduation, etc. Not just the project description. The other reports can be viewed for examples. And Triple Soup is missing, but nothing has happened with that podling yet. Also, do we want PMC members to sign off on the reports like last month? -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] TripleSoup - a SPARQL endpoint for httpd
Garrett Rooney [EMAIL PROTECTED] writes: I would avoid creating a -user list until it's actually proven necessary. In the beginning keeping user questions on the dev list makes sense to me. Me too. One less mailing list to deal with is always a good thing. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Felix Graduation
On 1/17/07, Richard S. Hall [EMAIL PROTECTED] wrote: The Felix community feels that we are ready for graduation, as indicated by the following community vote to request graduation: +1 -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] graduate Solr to Lucene
Yonik Seeley [EMAIL PROTECTED] writes: The Solr community has voted and believes Solr is ready for graduation from the Incubator and has met all incubation requirements, and the Lucene PMC has voted to accept Solr. The Solr podling is therefore requesting to graduate from the Incubator to become an Apache Lucene subproject. +1 -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Making a non ASF project, ASF friendly
On 1/6/07, Chris Howe [EMAIL PROTECTED] wrote: Scenario: A project (Project A) is set up on Source Forge by individuals as the only legal entities. Project A is setup under the Apache License V2. What would Project A need to do beforehand to ensure that all code committed to Project A's SVN is available for an existing ASF project to incorporate into it's code base in the following scenarios: From a purely legal and policy standpoint, any AL2 licensed work can be included in an ASF work. So all your situations should be fine just by having the sf.net project use the Apache License. The only tricky part is if a contribution is significant and that's only because of policy not license restrictions. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Making a non ASF project, ASF friendly
On 1/7/07, Henri Yandell [EMAIL PROTECTED] wrote: I don't agree. Any AL2 licensed work can be included in an ASF distribution, as a dependency. In terms of committing a piece of work that is not under our IP (and is not covered by a CLA), the Apache license doesn't make it a given. You would still need to submit a grant or be covered by a CLA, and you would have to be responsible for the IP of the work. (I think... :) ). From a purely licensing point of view (independent of the ASF) you can take two AL2 works and combine them and get an AL2 licensable work as a result without having to get anyone's permission. We may not always do this in the ASF but that's a result of policy not licensing. If something is small enough to submit via JIRA and it's already AL2, then I don't think it would be a problem. Our JIRA process already covers this anyway. As a pure dependency, it's also not an issue. Our third-party licensing guidelines make this clear. So is the only situation that I see as tricky is taking say a handful of source code from sf.net and dropping it directly into the main trunk of an ASF project. This would be a fork but it wouldn't create a licensing issue as long as the code were clearly identified and any attached copyright statements maintained. I can understand some could feel uneasy about the forked result, but the only legal concern I can detect would be if someone doubted whether the original sf.net work had been properly put under the AL2 in the first place. If the original work were encumbered in some way, then that could put the ASF fork in a bind. So in the end it's a question of if we trust the original work is what it says it is -- a legally licensed AL2 work. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] - Restarting the vote to --- Ratify Tuscany PPMC vote to release SDO for Java M2 artifacts
On 11/6/06, kelvin goodson [EMAIL PROTECTED] wrote: I understand it is good practice to restart a vote if the vote thread becomes heavy with discussion. This is the case with the vote that was begun at http://www.mail-archive.com/general@incubator.apache.org/msg11201.html which contains some issues raised and comments to address each of those issues. So please vote to ratify the Tuscany PPMC vote to release SDO for Java M2 artifacts at http://people.apache.org/~kelvingoodson/sdo_java/RC5a/ which have been voted for by the Tuscany PPMC. +1 Though I agree with the earlier sentiment expressed by Bill Dudney [1] that the LICENSE and/or NOTICE file should explicitly state which jars are under which licenses. This is at least not the case for the RC5a binary. Otherwise, good job! -- jaaron [1] http://www.mail-archive.com/general@incubator.apache.org/msg11273.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Retire AltRMI
On 11/6/06, peter royal [EMAIL PROTECTED] wrote: The AltRMI podling, http://incubator.apache.org/projects/ altrmi.html has become stagnant. Here is a vote to move it into retirement. [ ] -1 : It lives on, you someone missed my recent commits on it last week [ ] 0 : I don't do fall cleansing [ ] +1 : Move to retirement +1 Poor altrmi... I really liked that code... :-) And stagnant is putting it nicely. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Retiring a project [Was: Retiring Agila?]
On 11/6/06, Henri Yandell [EMAIL PROTECTED] wrote: So how do we retire a project? My checklist so far is: * move Agila to the Retired section of the Incubator site, * inform -dev/-user mailing lists (earlier than the rest) * ask that the mailing lists be shutdown, * update the wiki, * update the website, * move the JIRA project to a Retired category(?), (what if Bugzilla?) * make the SVN read-only, * what else? That's essentially how it worked for Avalon too. Though in that case, some of the code was also transferred to Excalibur first. The only issue I have with retired projects is that it's not the code that is retired, it's the community. The message we should be sending is Hey, we don't have any active committers on this project. You're still free to use it, but you're on your own. Anyone who really wants to revive the project can fork it or drum up support through the incubator again. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Anyone up for a docathon at ApacheCon Austin?
On 10/2/06, Jean T. Anderson [EMAIL PROTECTED] wrote: I've been holding onto posts with good fodder for the incubator site, but haven't had time to incorporate them yet. I'll be at the hackathon on Tuesday Oct 10. Is anyone else up for a docathon? (Or did I miss a post already suggesting one? *chagrin*) Count me in. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Policy on Initial Committership
On 10/1/06, Martin Cooper [EMAIL PROTECTED] wrote: I do too. And with the number of projects coming in with sizeable numbers of committers these days, I wonder how long it will be before the committers coming in this way will outnumber those whose committership is based on (ASF earned) merit. It seems to me that this could change the fundamental nature of the ASF. This has also been one of my concerns. But then it's only an issue if individuals on the proposal have not earned the necessary merit in the original project. I sense some of us suspect this to be the case. However, I agree with Roy's approach -- let the podling deal with the committer issue during incubation. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Podling Release Requirement (WAS: Re: [VOTE] Graduate Felix to TLP status)
On 9/13/06, Justin Erenkrantz [EMAIL PROTECTED] wrote: On 9/12/06, Niclas Hedhman [EMAIL PROTECTED] wrote: As Leo pointed out, 'codebase quality' is not a graduation criteria. And (hopefully) with Upayvira as the initial PMC Chair, I am not worried that the PMC will overlook release requirements. If ASF Members feel that to be a concern, they are both free to monitor and participate in the PMC work. My concern has nothing to do with 'codebase quality', but asking for a demonstration that the Felix community understands how to conduct a release that meets the ASF's criteria. If the community produces a release that is perfect on first shot, great - they're truly ready to graduate. If not, well, then, they'll learn from those mistakes and once they can produce a release that meets our criteria, then they'll be ready to graduate. Remember that a major task for a TLP is conducting a release. Therefore, it's reasonable for the Incubator PMC to ask for proof that they will execute that task successfully rather than taking it on blind faith. -- justin And I'm fine with that. I think it's a good idea for Incubating projects to do at least one release before graduating. My concerns are: 1) The policy regarding podling releases has never been explicit and always been conflicting 2) Let's not (again) fall into the trap of changing the requirements of graduation (or entry for that matter) on a vote thread So could we move these discussions to a new thread? -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [rant] seperate policy change from proposal discussion
On 8/8/06, Leo Simons [EMAIL PROTECTED] wrote: Perhaps we should try and seperate this somewhat more rigidly. Eg we could have a released version of all the things we want a project to do and/or comply with (this is our website) and we could have an in progress version of the same thing (this is what changes more rapidly). And *new proposals should be evaluated against the released one*. +1 This is one of my biggest concerns -- the rapidly changing requirements. This is easy enough to do as well. The released version (with a release number) is on the public website and the in progress version could be on the wiki. Proposals should include the version number they were written against. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Glasgow into Incubator
On 8/3/06, Mads Toftum [EMAIL PROTECTED] wrote: On Thu, Aug 03, 2006 at 05:54:14PM -0400, Garrett Rooney wrote: I'm sorry, but I have to vote -1 (binding). I very much agree with Garretts concerns - and would be much in favor of not bringing the project into incubation before they have proven an actual community and that they can work the standard the apache way. I feel it would look very much as an ASF endorsement of a standard that we may not have any influence on at all - maybe things will look different in a few months time, but right now I'm far from convinced. I understand that there are some specific circumstances in this case, but in general I believe this sort of criteria is why we get complaints that it's impossible to innovate at Apache any more. We require all the grunt work of innovation to occur outside of Apache. The issues of an open specification is one thing. But aren't proven an actual community and work the standard 'apache way' graduation requirements, not entry requirements? If we expect something coming into the incubator to already have a fully functioning, health Apache-style community, then the only point of the Incubator is for handling licensing issues. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Glasgow into Incubator
+1 -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Proposal] Blaze
On 7/18/06, Brian McCallister [EMAIL PROTECTED] wrote: Comments in line: On Jul 17, 2006, at 12:10 PM, Carl Trieloff wrote: == Interactions with the specifications == The specification is being developed by group of companies, under a contract that requires the resulting work to be published to a standards body. Which standards body? What licensing terms apply to the spec? Google brought me back this article which cleared a few things up for me: http://www.infoq.com/news/amq -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dormancy
On 7/17/06, Noel J. Bergman [EMAIL PROTECTED] wrote: I'd suggest that the PMC declare a project as dormant, with the effect being that we set the SVN ACL to read-only. If people want to wake the project up, we can change the ACL. +1 I'm not sure what would be best for the mailing list. If we make make them subscriber only, we would need people watching the lists, anyway. Leave them ostensibly place, but forward them to [EMAIL PROTECTED] Or do we just turn them off, with a bounce notice that people interested in resurrecting the project contact us on [EMAIL PROTECTED] Can we have the messages both forward to general@ and send the poster a notice message? This allows an email to get through but also makes it very clear to the sender the state of the project. If not, I would prefer the bounced message to simply forwarding the email along. And we can add a dormant section to the project index. And include info on how to re-activate a project for those brave enough. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Thoughts on Umbrellas, Federations, and Communication
On 3/9/06, Matthieu Riou [EMAIL PROTECTED] wrote: I know that mailing-lists are part of the foundation of the ASF and are a really useful way to communicate effectively. However my feeling is that we don't have the right tools or policies to use them as effectively as could be. For example, as a commiter, I find it extremely annoying that I have to subscribe to a mailing-list just to post a message on it. Also most archives aren't really user-friendly. Not being able to do a simple search on ALL mailing lists is for me a major drawback. So I'd suggest (if possible) the following ideas: * Give any commiter the necessary rights to send an e-mail on any mailing list without having to subscribe. * Provide fully searchable mailing-list archives. That's perhaps part of the solution. Really we have two problems: 1. Managing information 2. Providing suitable forums for cross-project collaboration In the first case, it's a matter of filtering the massive amount of information that goes through the mailing lists. I can't subscribe to them all. I'm over-subscribed as it is. So while I want to know about other conversations, I need a filtering mechanism. One solution that I really liked were the Apache newsletters we had going on a little while ago. It was a nice way to know about what was going on in each project's little corner of the ASF. If we could extract similar information from the mailing lists and create smart digests that would perhaps suffice. Another matter is providing spaces for cross-project collaboration. In this matter, I'm not sure I have any solution, though I'm not sure additional mailing lists are really the best idea. That might only add to the email overload. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz - next steps
On 2/13/06, Jacopo Cappellato [EMAIL PROTECTED] wrote: Hi all, here at OFBiz we'd like to go on with the IP-clearance effort but, since we are going to contact *many* developers, we would like to be sure that the steps we'll perform are the correct ones. Anyone here could help us to answer these questions? If not, could you please post a message to the legal-discuss list (it is only open to ASF committers) to see if we can get some feedback from them? Go ahead and use the iCLA as is. While the iCLA covers everything, you should clearly explain the license change in your notice to contributors in order to reduce any confusion. If anyone else has specific questions, they can send them our way. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz - next steps
On 2/13/06, Jacopo Cappellato [EMAIL PROTECTED] wrote: J Aaron, thanks for your feedback. Sorry but I still have some doubts about this: if a guy signs an iCLA in which he states that he agrees to release under the ASL all the work (present and future) that he sends to the ASF (thru mailing lists, Jira, SVN etc...), in which way this agreement will address the work that the guy did and donated in the past under a different licence and to a different project/community? Incubating OFBiz = present contribution. For former contributors, the purpose of the iCLA is to cover this current contribution to the Incubator. While the contribution may be in the past as far as OFBiz is concerned, it's in the present as far as the ASF is concerned. In other words, the contributor is re-contributing the code as part of the incubation grant. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz - next steps
On 2/8/06, David E. Jones [EMAIL PROTECTED] wrote: Under the MIT license we have been using there is no assignment or granting of copyright. All of the code is licensed under the MIT license, and the copyright everywhere is listed under The Open For Business Project. I don't know if this is an issue or not as the Apache license doesn't involve ownership of copyright, just a use license grant and such. Do we need to get any sort of license grant from other contributors? Under the MIT license terms we can add a license to it, but not remove that license, but if read literally the license comes from The Open For Business Project. So, I guess I'm not sure what we really need in this area... There are a number of ways in which we can handle this, but the first step is to get a list of all those who have had direct commit access to Open For Business. The next list you'll want are contributors whose code is in Open For Business but who never had commit rights. As Justin explain, this can be the most difficult part, but it's not only necessary, it's worth it because it ensures the code is free and clear to be used properly. I'll help with this item in any way I can. And no, we don't need ip-clearance files, we need CLAs. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Roles (was OFBiz proposal)
On 1/26/06, Noel J. Bergman [EMAIL PROTECTED] wrote: David N. Welton wrote: Roy T. Fielding wrote: Where are the mentors? Are the champions also going to mentor the project? According to the docs I read, the incubator PMC is supposed to assign them. The docs still need revising. Yep. Though I am interested in one more clarification: number of mentors. According to the current docs, there's only one mentor. However, in practice, they are sometimes several. Is this an issue? Is it better to have one person have the final responsibility or to spread it out? If the project is sponsored by another PMC, they must line up Mentors first, or we are going to bounce the project as being out of conformance with Incubation requirements. If the Incubator PMC sponsors the project, there must be Mentors lined up before we vote for it. We are not in the business of providing or assigning Mentors. Having Mentors serves a number of legal and structural purposes, and effectively limits the Incubator. If there isn't sufficient interest that we have active Mentors participating, we cannot incubate the project. Simple as that. Can I just change the docs to reflect this or do we need a formal vote for changing official policy documents? And as for OFBiz itself, both David and I are willing to mentor and others have said they'll step up to the role if necessary. Do you want me to update the proposal or is it fine as it is? -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RANT] Mission of the incubator
On 1/27/06, Sam Ruby [EMAIL PROTECTED] wrote: What I DO care more about is communities and the people that make them up. As I have come to believe that tasks assigned to many are effectively assigned to nobody, I would prefer that there be either a single or primary mentor for Kabuki. And frankly, I believe that Andy is the best person for that job. I don't want to distract to any of the other content in Sam's rant, which is great by the way, but I want to revisit this idea of the role of a mentor. There's been one or two other threads on this [1] and it's something I want to clarify. The current docs refer to a single mentor. The current practice is to have several. Even the Kabuki proposal as written has 4 mentors listed. There was a vote recently in which many people supported the notion that there should be 3 mentors for any proposal. Now I agree with Sam that having more than one mentor can easily mean having no mentor. This is why I think there's some confusion around the role of mentor and the intent of having more than one. My impression is that the intent is to show that there is reasonable support from ASF membership, ie- three members have volunteered their support. Whereas the actual role of mentor is not about showing support but about oversight and guidance. My point is, I think we need to clarify the role of mentor and perhaps champion. I really have no strong feeling about how many we should have or any hard requirements. I'd rather just see clarification so that the incubation process is less confusing. -- jaaron [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] OFBiz Proposal
On 1/25/06, David N. Welton [EMAIL PROTECTED] wrote: Roy T. Fielding wrote: * David N. Welton [EMAIL PROTECTED] * Yoav Shapira [EMAIL PROTECTED] * J Aaron Farr [EMAIL PROTECTED] Where are the mentors? Are the champions also going to mentor the project? According to the docs I read, the incubator PMC is supposed to assign them. I'd planned to help out where possible in that role. Exactly. According to the *current* Incubator policies, a proposal only starts with champions. The sponsor, in this case the Incubator PMC, is supposed to assign a mentor upon acceptance of the proposal. Technically, the policies only refer to a single champion and single mentor. There's nothing to suggest there cannot be more than one champion, but the documentation does suggest that the mentor role is fulfilled by a single individual who has specific oversight responsibilities. In practice, the roles of champion and mentor have been reversed and confused. In particular there was a recent vote on changing some of these requirements and policies. In any case, both David and I have expressed a willingness to mentor and I believe Yoav may be as well, though I don't recall him specifically saying so. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
On 1/22/06, Noel J. Bergman [EMAIL PROTECTED] wrote: It is also good to try to ensure that discussion has settled down, and that there is a consensus before calling for the vote. I generally believe that a good ASF vote isn't called to make a decision; it is called to ratify one. Exactly. A very important principle. So, regarding this proposal, does anyone else have any other concerns? Any other questions from or for the OFBiz team? Otherwise, I can prepare the vote later today. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] OFBiz Proposal
The Open For Business Project and has no ownership or other legal relationship to it, as was planned from the beginning). * Hans Bakker is from the Netherlands but now lives in Thailand and runs consulting and services companies in both countries. * Al Byers is from Utah and is an independent consultant. * Jacopo Cappellato is from Italy and works on manufacturing management and related software for his company, TAU Informatica SrL. * Si Chen is from Los Angeles and is both an OFBiz user at his company Gracious Style, Inc. and service provider at Open Source Strategies, Inc. In addition, there are other contributors from France, Germany, Portugal, the UK, US, Canada, Australia, India, Japan, China, and various other countries. Many contributors come from a software background, but OFBiz has also attracted many people from business and other backgrounds that are somewhat technical and have learned enough of the technology to contribute significantly to the project. === Reliance on Salaried Developers: === There is a good balance of developers in the OFBiz community today. Many of the developers are independents who rely on OFBiz for their consulting work, while others work at end user organizations for whom OFBiz is a core part of the technology mix. === No Ties to other Apache Products: === Many Apache products are used within OFBiz, including Tomcat, Derby, Xerces, Jakarta commons, Lucene, Xalan, ORO, Log4j. Also, the proprietary bug tracking tool used at the ASF, JIRA, is based on technology from OFBiz. === A Fascination with the Apache Brand: === The developers of OFBiz have been quite successful on their own and could continue on that path with no problems at all. They are interested in joining the ASF in order to increase their contacts and visibility in the open source world. == Committers == * David E. Jones * Andy Zeneski * Si Chen * Al Byers * Jacopo Cappellato * Hans Bakker == Proposed Apache Sponsor == Incubator PMC == Champions == * David N. Welton [EMAIL PROTECTED] * Yoav Shapira [EMAIL PROTECTED] * J Aaron Farr [EMAIL PROTECTED] -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT] Kabuki Proposal -- Eclipse Plugins
Since I don't really know my way around the Eclipse community very well, I thought I might ask the question here. I was really interested in the Eclipse portion of the original Kabuki proposal but that's now been kicked over to the Eclipse foundation. So, does anyone know where I can join in on the discussion on that proposal and perhaps get involved? Thanks. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OFBiz Marketing and Services
On 1/19/06, Al Byers [EMAIL PROTECTED] wrote: J Aaron, As one of the committers, I would have no problem have any reference to my company removed, if that is necessary for the process to continue. Well, the references don't necessarily have to be removed. Other ASF projects provide links to companies providing support and services. For example: Struts: http://wiki.apache.org/struts/StrutsResources http://wiki.apache.org/struts/StrutsConsultants Geronimo: http://geronimo.apache.org/powered_by.html It's more a matter of how the references are handled. For example, Apache has not required fees in order for these links to be provided. Also, when looking at an Apache project website, there's a fairly clear distinction between the open source project and any commercial entities which might be offering services. Not that such a distinction is absent at OFBiz.org, but my impression is the seperation is wider for ASF projects. These issues can be sorted out during incubation (that's what it's for). I'm bringing it up now to get a better understanding of what the team's plan is and to see if there's an understanding that incubation might require some changes in approach. But I wonder if there is not a bigger aspect to this whole thing. I see your remarks about ASF encouraging commercial efforts, but OFBiz is significantly different in this regard. As has been mentioned earlier, up until this time ASF products have mostly been tool oriented. With OFBiz, ASF will be offering a product that is ready for businesses to plug in with very little effort - adding a huge new market for its services. No longer need its client-base be programmers only. Of course, I want to also restate that OFBiz is both a programming framework and set of end-user modules. Perhaps the closest existing analogy is Apache Lenya which can be installed as a more end-user application. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mentor v Champion (WAS: Re: [VOTE] Changes to Incubator process(es))
I know the vote is essentially over, but the following thought occurred to me this morning as I volunteered to support the OfBiz proposal. On 1/11/06, Davanum Srinivas [EMAIL PROTECTED] wrote: [ ] - Any new proposal should have 3 ASF Members / Officers as mentors (without regard to affiliation) Currently there's only one mentor, but there can be several champions. The mentor has specific oversight responsibilities. The champions are also expected to be involved but their specific role is to demonstrate that the proposal has support within the ASF. Did we really want to distribute the mentor responsibilities to three people? Or was the intent to increase the required show of support? My impression was that the intent was to show that there is a minimal level of support among ASF members, not to dilute responsibility. In this case, a more accurate process change would be to require (or recommend) that proposals have three champions, not three mentors. If so, we may also need to better define the role of champion. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [doc] Getting Started in the Incubator topic
On 1/17/06, Jean T. Anderson [EMAIL PROTECTED] wrote: It shouldn't be buried deep in a subpage, nor should it be on a page that is already busy. http://incubator.apache.org/howtoparticipate.html is borderline too busy and covers more than this one role. comments? feedback? Looks good. I think a checklist approach is useful. A while back I worked on some documentation that Ted Husted had started. I'll see if I can dig that up. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OFBiz Marketing and Services
Hello all. The current OFBiz project has a lot of material on marketing and services. I'm wondering how the team anticipates they'll handle this material during the incubation transition. We encourage commercial use of ASF products and we support efforts to build companies around them. So there's no problem with that. But at the same time, there's a precedent to remain fairly neutral when it comes to promoting one service provider over another on ASF sites. Has the OFBiz team thought of how they want to handle this? -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
On 1/18/06, Justin Erenkrantz [EMAIL PROTECTED] wrote: On Mon, Jan 16, 2006 at 10:45:49PM +0100, David N. Welton wrote: David N. Welton wrote: I guess it should be placed on the wiki? I'll do that later today if no one else beats me to it. Here we go: http://wiki.apache.org/incubator/OFBizProposal I changed the proposed sponsor to the Incubator PMC, as that's apparently the done thing. I believe J. Aaron said he'd be willing to mentor too[1]. -- justin Certainly willing if they'll have me! :-) -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
On 1/10/06, David E. Jones [EMAIL PROTECTED] wrote: We are all looking forward to your comments and desire to express in advance appreciation for all that you have done and are doing for the open source world and the software world in general through your efforts in the Apache Software Foundation. This proposal has caught my interest. I'd be willing to help mentor. A couple of points: The proposal says that this project is to be sponsored by the ASF Board. Is that correct? Did the Board already +1 on or are we still searching for a sponsoring entity? Apache has generally stayed away from end user applications and instead focuses on infrastructure and middleware. That's not completey true, but is a good rule of thumb. For example, a lot of contributors and supporters of the ASF use our code to create ecommerce products. I'm a little worried that some may view this proposal as the ASF attempting to compete with these contributors. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for OFBiz to Join the ASF
On 1/12/06, David N. Welton [EMAIL PROTECTED] wrote: I think we should look at whether this project is a good fit for the ASF (I think so, or I wouldn't have mentioned the idea to them) rather than if we are stepping on someone's toes. Geronimo steps on toes. Harmony does to some degree, as well. Once upon a time, people sold web servers, and httpd stepped on their toes. On 1/12/06, Ross Gardler [EMAIL PROTECTED] wrote: Many ASF projects compete with many other products. As far as I understand things the ASF prides itself on not allowing any commercial entities or individuals to dictate what the ASF does and how it does it. Certainly. My point was that we should be prepared for such concerns. For example, I imagine an announcement that Apache is producing a full ecommerce stack would create some buzz and questions. As for being a good fit, on the surface it seems like it would be. I don't know anything other than what was in the proposal about how OFBiz has worked internally as a community. But then, figuring out those sorts of things is exactly what the incubation process is about. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there a no graduate option?
On 12/22/05, Rich Bowen [EMAIL PROTECTED] wrote: Davanum Srinivas wrote: I'd say after X months (6? 12?), there should be a VOTE on incubator PMC whether to continue that project or not. Ok, so say we went with X=12. There are 13 projects that fit that description. Of those, 3 have status updates that date within that X month timeframe, leaving 10 that, at least to me, appear to be inactive for more than X months. I can speak a little for AltRMI and the FtpServer projects which were spun out of Avalon oh so long ago. This was early in the Incubator's history before we had the guidelines and procedures we do today. The FtpServer has seen more recent activity, but those who have expressed interested in AltRMI (myself included) simply haven't invested in building a community around it (it was mostly stable code even when it was in Avalon). I believe a similar situation may be true of other dormant incubator projects. And dormant might be better than failed. If someone wants to come along a pick up these projects and re-activate them, they are more than welcome. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FAQ for Apache Harmony
First off, Harmony sounds like a great project. A truly compliant open source JVM would be wonderful. Greir, one question... On 5/6/05, Geir Magnusson Jr. [EMAIL PROTECTED] wrote: FAQ : Frequently Asked Questions = ... 11) Will you accept SWT if IBM offers it? Apache is always grateful for contributions from wherever they come, and IBM has a record of contributions to open source, but it would up to the project community to decide whether any particular contribution was used in the project. How does SWT relate? -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal for a centralized Eclipse update manager site for Apache projects/software
On 5/3/05, Dion Gillard [EMAIL PROTECTED] wrote: Is there a reason we can't reuse the existing repository at http://www.apache.org/dist/java-repository/ ? In your example, Eclipse could be configured to check http://www.apache.org/dist/java-repository/axis/jars/ for an update? Something like that might work. Eclipse checks for a 'site.xml' file that references one or more plugins to download and install. The update site URL needs to be stable, so if a user picks a particular mirror initially that user will always use that mirror for future updates. Also the plugins are more than just a jar and minimally require a plugin.xml file zipped together into a single archive. Currently, Derby is the only ASF project I know of which distributes its releases in Eclipse plugin format [1] in addition to traditional binary and source releases. So it's slightly more than just making ASF jars available on the repository and pointing Eclipse to them. There's also the question of having a single site.xml file for all ASF Eclipse plugins versus a separate one for each PMC or even subproject. A single site would be far easier for users but more complicated for ASF developers. While we could reuse the java-repository location for Eclipse updates, I would prefer to see a new separate location such as: http://www.apache.org/dist/updates or something like that. Finally, unless we wanted all those Eclipse clients hitting our main distribution site, we would have to instruct users to pick a mirror. It's all feasible and I would love to see more Eclipse plugins for ASF projects. An update site would definitely help. -- jaaron [1] http://incubator.apache.org/derby/integrate/derby_plugin.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Volunteer Documentation
On Thu, 17 Mar 2005 09:17:25 +0530, Vikas Singhal [EMAIL PROTECTED] wrote: Hi List, I am a technical writer with an experience of more than three years. I want to contribute to the foundation in terms of documentation. I am willing to work on projects that either have no documentation or minimal documentation. Can anyone help me in identifying such projects? Thanks, -Vikas The Agila project is a new workflow engine that could use documentation (currently none). See: http://incubator.apache.org/projects/agila.html I'm working on new documentation for the Excalibur project (http;//excalibur.apache.org) and we would always love more help. The process of contributing documentation will be slightly different for each project. In general you'll have to check out the site source documents (generally XML) and then submit patches to the developer team. Alternatively, most projects have a wiki site (http://wiki.apache.org) to which you can contribute directly without having an Apache account. -- jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: New Incubator Site branch - sources in html
-Original Message- From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED] I've created a branch [1] for the Incubator website, a rendered version of which is visible here [2], with the following modifications: ... Comments? The menu looks a lot better, but I think the banner space is still really busy. What if we went with a simpler Incubator logo that blended with the background like the ASF logo: http://www.jadetower.org/muses/images/apache-incubator-logo.png jaaron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
