Nabble - Apache Incubator - General

Re: [Incubator Wiki] Update of "HeartProposal" by vaijanath

2008-07-24T00:16:24Z

Dear all, Sorry for mis-send.

- Edward

On Thu, Jul 24, 2008 at 4:12 PM, Edward J. Yoon <edwardyoon@...> wrote:

> Guys,
>
> Be careful when you edit the wiki. Wiki program will send a mail to
> all subscribers (e.g. IPMC, many committers, ..., etc) by trivial
> changes.
> So, we should collate all on our list.
>
> - Edward
>
> On Thu, Jul 24, 2008 at 3:37 PM, Apache Wiki <wikidiffs@...> wrote:
>
>
>> Dear Wiki user,
>>
>> You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.
>>
>> The following page has been changed by vaijanath:
>> http://wiki.apache.org/incubator/HeartProposal
>>
>> ------------------------------------------------------------------------------
>> * Inchul Song (icsong AT dbserver DOT kaist DOT ac DOT kr)
>> * Frederick Haebin Na (haebin.na AT gmail DOT com)
>> * http://groups.google.com/group/hrdfstore/members
>> + * Vaijanath Rao (vaiju1981 AT gmail DOT com)
>>
>> == Sponsors ==
>> === Nominated Mentors ===
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: cvs-unsubscribe@...
>> For additional commands, e-mail: cvs-help@...
>>
>>
>
>
>
> --
> Best regards, Edward J. Yoon
> edwardyoon@...
> http://blog.udanax.org
>

--
Best regards, Edward J. Yoon
edwardyoon@...
http://blog.udanax.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [Incubator Wiki] Update of "HeartProposal" by vaijanath

2008-07-24T00:12:08Z

Guys,

Be careful when you edit the wiki. Wiki program will send a mail to
all subscribers (e.g. IPMC, many committers, ..., etc) by trivial
changes.
So, we should collate all on our list.

- Edward

On Thu, Jul 24, 2008 at 3:37 PM, Apache Wiki <wikidiffs@...> wrote:

> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.
>
> The following page has been changed by vaijanath:
> http://wiki.apache.org/incubator/HeartProposal
>
> ------------------------------------------------------------------------------
> * Inchul Song (icsong AT dbserver DOT kaist DOT ac DOT kr)
> * Frederick Haebin Na (haebin.na AT gmail DOT com)
> * http://groups.google.com/group/hrdfstore/members
> + * Vaijanath Rao (vaiju1981 AT gmail DOT com)
>
> == Sponsors ==
> === Nominated Mentors ===
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cvs-unsubscribe@...
> For additional commands, e-mail: cvs-help@...
>
>

Re: [PROPOSAL] Tashi

2008-07-23T20:39:56Z

On 23-Jul-08, at 6:12 PM, Niall Pemberton wrote:

> I really don't see what the problem is here, there are two named
> committers in the proposal. Whatever the interests of the companies
> they work for, Tashi will have to create a healthy community to
> graduate and I don't think corporate backing should be used as a
> reason to deny entry in the first place. Also its a *good thing* IMO
> that the proposal is open about the three companies that are prepared
> to fund work and I would hate to see that rewarded with a -1, since it
> may prompt others to be less open in the future.
>

Right on. Why does it matter if it's committed individuals or
committed organizations? It will always be a mixture, and that's a
good thing. It's fallacy to think that every project can be the ideal
of a diverse set of committed individuals who will remain eternally
devoted to a project. Maybe that happens sometimes, but organizations
can also help make sustainable technologies as well, and is more
likely to be the case these days for better or worse. At least they
are honest, and that matters more then anything I think.

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
What matters is not ideas, but the people who have them. Good people
can fix bad ideas, but good ideas can't save bad people.

-- Paul Graham

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T20:35:25Z

+apache@...>
Subject: Re: [PROPOSAL] Tashi

Hi,

I've read the messages from Henning and William, and I'd like to address some of the concerns voiced by them. I'm Michael Stroucken, and I'm a senior systems programmer at CMU. That means I am staff, and my interests in the Tashi project are not driven by an interest to generate research from the project (which is a plus of course).

One of my tasks here is providing computing facilities to students, researchers and affiliates within the Parallel Data Laboratory. One of the facilities is a machine room designed from the bottom up to allow research on data center operations - the Data Center Observatory mentioned in the proposal.

When I was offered the opportunity to be part of this project, I gladly joined up because I'm feeling the pain of needing a means of fairly and equitably providing for the computing demands of our students, yet having average utilisation levels be rather low at the same time people are desperate for machines.

I have not been assigned to any part of this project as an employee of the university, and I am participating out of personal interest. I believe the project can improve services not just at our data centers, but at data centers in general.

While this project is likely to result in research publications, at the end of the day my rooms are still going to be there. For me, the fruits of the project will be a real asset in a production environment, benefitting from continued input and improvement. I believe that other adopters in industry or academia will regard it as such too.

Finally, as for the organisational vs. individual aspect, the project has large organisations behind it which provide an environment of communication and cooperation that would be difficult to replicate if we were just a few people at non-related and non-cooperating sites. I am aware that our responsibility towards an Apache project is as individuals, but I hope we can convince you that our corporate backing will be beneficial for the project.

Greetings,
Michael.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T20:11:39Z

On Wed, Jul 23, 2008 at 3:12 PM, Niall Pemberton
<niall.pemberton@...> wrote:
> I really don't see what the problem is here, there are two named
> committers in the proposal. Whatever the interests of the companies
> they work for, Tashi will have to create a healthy community to
> graduate and I don't think corporate backing should be used as a
> reason to deny entry in the first place. Also its a *good thing* IMO
> that the proposal is open about the three companies that are prepared
> to fund work and I would hate to see that rewarded with a -1, since it
> may prompt others to be less open in the future.

+1. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T19:04:51Z

On Thursday 24 July 2008 05:23, William A. Rowe, Jr. wrote:
> In other words, I'll vote -1 on any Proposal for non-person entities
> X, Y, and Z to form an incubator podling, and I know several other PMC
> members who will do likewise.

I disagree. IMHO, wording in the proposal is irrelevant. If they have known
this and written it differently, without any material change behind the
words, what is the difference?

Now, I think that Incubation is all about proving that there indeed is a
healthy community behind the project, and will be one of the major graduation
criteria, but I don't see why proposals with more experienced authors are
given green light and others are booted.

> This looks like a very interesting technology,

For me, this is an entry criteria,

> collaboration by actual persons A, B, and C (who happen to work for
> X, Y, and Z)

... and this would be the graduation criteria.

Cheers
--
Niclas Hedhman, Software Developer

I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T15:20:14Z

William A. Rowe, Jr. wrote:
> This looks like a very interesting technology, and when proposed as a
> collaboration by actual persons A, B, and C (who happen to work for
> X, Y, and Z) we will have something to discuss.

Great, because that's what I think we have. It so happens that persons
D, E and F also helped write up the proposal, but they won't be writing
the code, so they're not listed in the committer section.

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T15:12:10Z

On Wed, Jul 23, 2008 at 10:23 PM, William A. Rowe, Jr.
<wrowe@...> wrote:

> Doug Cutting wrote:
>>
>> There's no conspiracy here to steal Apacheness. Rather, Yahoo!, Intel and
>> CMU would like to collaborate on open source software. Intel and CMU have a
>> prototype, and Yahoo! is interested in helping to develop this further. All
>> three believe that other parties will also be interested in this software.
>> Apache is a good home for collaborative, open-source software projects, no?
>
> Here's the gist of the issue, and your email highlights it perfectly.
>
> Yahoo!, Intel, CMU etc have no standing at the ASF. The ASF does not
> recognize collaborative "corporate" development; the ASF recognizes
> collaborative development by physical persons, not other legal constructs
> or amalgamation.
>
> In other words, I'll vote -1 on any Proposal for non-person entities
> X, Y, and Z to form an incubator podling, and I know several other PMC
> members who will do likewise.
>
> This looks like a very interesting technology, and when proposed as a
> collaboration by actual persons A, B, and C (who happen to work for
> X, Y, and Z) we will have something to discuss.

I really don't see what the problem is here, there are two named
committers in the proposal. Whatever the interests of the companies
they work for, Tashi will have to create a healthy community to
graduate and I don't think corporate backing should be used as a
reason to deny entry in the first place. Also its a *good thing* IMO
that the proposal is open about the three companies that are prepared
to fund work and I would hate to see that rewarded with a -1, since it
may prompt others to be less open in the future.

Niall

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T14:23:12Z

Doug Cutting wrote:
>
> There's no conspiracy here to steal Apacheness. Rather, Yahoo!, Intel
> and CMU would like to collaborate on open source software. Intel and
> CMU have a prototype, and Yahoo! is interested in helping to develop
> this further. All three believe that other parties will also be
> interested in this software. Apache is a good home for collaborative,
> open-source software projects, no?

Here's the gist of the issue, and your email highlights it perfectly.

Yahoo!, Intel, CMU etc have no standing at the ASF. The ASF does not
recognize collaborative "corporate" development; the ASF recognizes
collaborative development by physical persons, not other legal constructs
or amalgamation.

In other words, I'll vote -1 on any Proposal for non-person entities
X, Y, and Z to form an incubator podling, and I know several other PMC
members who will do likewise.

This looks like a very interesting technology, and when proposed as a
collaboration by actual persons A, B, and C (who happen to work for
X, Y, and Z) we will have something to discuss.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T11:10:15Z

Henning Schmiedehausen wrote:
> - Are the proposed committers, people "assigned to work on the project"
> or are they genuinely interested in this software.

Those are not necessarily disjoint sets. Folks who are "assigned" are
frequently also "genuinely interested", and vice versa.

> IAW, will they stick around or leave as soon as they are reassigned to
> other projects or their grants run out?

Folks who are "genuinely interested" often lose interest over time, and
folks who are "assigned" are often long-term contributors who even
change employers and are "re-assigned" to work on the same project,
i.e., are hired for their familiarity and involvement with the project.
Nearly everyone on Hadoop from Y! was initially assigned. Most have
found it a plum assignment. A few have moved on, some to Hadoop-related
jobs at other companies.

> The wording for the Yahoo! "slot" sounded to me like there has been a
> decision at management level that CMU, Intel and Yahoo! want to do some
> work on that subject and they like to have the soft, warm glow of
> Apacheness on their effort for a (PR?) reason.

There's no conspiracy here to steal Apacheness. Rather, Yahoo!, Intel
and CMU would like to collaborate on open source software. Intel and
CMU have a prototype, and Yahoo! is interested in helping to develop
this further. All three believe that other parties will also be
interested in this software. Apache is a good home for collaborative,
open-source software projects, no?

Also, if Tashi doesn't garner a diverse, active set of contributors in
the incubator, it will die a slow death with little harm done.

> So there is an engineer
> from each group assigned to "work on this" until further notice. From
> thirteen names on the proposal, only two will be committers? I know
> about Doug, who are the other ten?

Several are managers that contributed to the proposal. They control
budgets that will pay contributors. Should they remove their names?

> That is not exactly the kind of project that we want. The whole Tashi
> proposal sounds to me like an abstract to a scientific paper, which has
> the tendency that as soon as the paper is done, the interest in the
> subject goes down.

That is certainly not my understanding. The intent as I understand it
is to build cluster management software that will actually be used to
manage clusters. Yahoo!, my employer, has many clusters and seeks
better software to manage them.

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T09:27:28Z

Hi,

a number of questions:

- Are the proposed committers, people "assigned to work on the project"
or are they genuinely interested in this software.

IAW, will they stick around or leave as soon as they are reassigned to
other projects or their grants run out?

The wording for the Yahoo! "slot" sounded to me like there has been a
decision at management level that CMU, Intel and Yahoo! want to do some
work on that subject and they like to have the soft, warm glow of
Apacheness on their effort for a (PR?) reason. So there is an engineer
from each group assigned to "work on this" until further notice. From
thirteen names on the proposal, only two will be committers? I know
about Doug, who are the other ten?

That is not exactly the kind of project that we want. The whole Tashi
proposal sounds to me like an abstract to a scientific paper, which has
the tendency that as soon as the paper is done, the interest in the
subject goes down.

- The sentence "A number of events at Yahoo, Carnegie Mellon, and Intel
Research Pittsburgh motivated the development of Tashi and convinced us
to work together in the context of an open-source community" makes me
wonder, what these events were and why specifically the Apache Incubator
was chosen.

- And finally: from your proposal and your concept, it is very clear to
me that you *will* be cutting very very close to proprietary open source
(i.e. GPL licensed) code and you will need to interface with such code.
Are you aware of our strict rules about non-Apache licensed code and how
will you amend this? Has your current code (which is not visible
anywhere) hard dependencies on Apache-incompatible software that you
will need to change/rewrite? XEN e.g. is GPLv2 licensed and you can not
host any code at Apache that needs to be linked with XEN.

Ciao
Henning

On Wed, 2008-07-23 at 10:36 -0400, David O'Hallaron wrote:

> No worries. I've removed the entry on the wiki version of the proposal
> at http://wiki.apache.org/incubator/TashiProposal. It now reads
> simply:
>
> Initially, there will be one committer each from Carnegie Mellon and
> Intel Research:
> * Michael Stroucken (mxs@...)
> * Michael Ryan (michael.p.ryan@...)
>
>
>
>
> Dave
>
>
> On Tue, Jul 22, 2008 at 8:36 PM, William A. Rowe, Jr.
> <wrowe@...> wrote:
> > Doug Cutting wrote:
> >>
> >> Noel J. Bergman wrote:
> >>>
> >>> With respect to "Initially, we plan to start with one committer each from
> >>> Carnegie Mellon and Intel Research, with a Yahoo committer to be
> >>> determined
> >>> later", that's awkwardly phrased. It appears to imply a corporate
> >>> representative doing commits for "hidden" people, something that we
> >>> consider
> >>> to be an anti-pattern.
> >>
> >> That is not the intent. The intent is for Yahoo! to assign someone to
> >> work on this project as a direct contributor. But that person has not yet
> >> been identified.
> >>
> >>> Whomever is to be actively involved in development
> >>> should be on the committer list. If it is just a community of just The
> >>> Two
> >>> Michaels, fine, but the wording should be rephrased.
> >>
> >> +1 If Y! does not name someone soon, then that entry should be removed. A
> >> committer from Y! can always be added later, based on merit.
> >
> > No; the entry should be removed now.
> >
> > Yahoo the Company cannot place a reservation on a place at the table for
> > an unnamed body. This is not how the ASF works. Nor are committers
> > expressed as delegates of the institutions the work for/study at.
> > This places a cloud over the acceptance of this particular project, and
> > I would encourage everyone to be sure their mentors/champions review the
> > text before posting a proposal for incubation..
> >
> > Bill
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@...
> > For additional commands, e-mail: general-help@...
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-23T07:36:49Z

No worries. I've removed the entry on the wiki version of the proposal
at http://wiki.apache.org/incubator/TashiProposal. It now reads
simply:

Initially, there will be one committer each from Carnegie Mellon and
Intel Research:
* Michael Stroucken (mxs@...)
* Michael Ryan (michael.p.ryan@...)

Dave

On Tue, Jul 22, 2008 at 8:36 PM, William A. Rowe, Jr.
<wrowe@...> wrote:

> Doug Cutting wrote:
>>
>> Noel J. Bergman wrote:
>>>
>>> With respect to "Initially, we plan to start with one committer each from
>>> Carnegie Mellon and Intel Research, with a Yahoo committer to be
>>> determined
>>> later", that's awkwardly phrased. It appears to imply a corporate
>>> representative doing commits for "hidden" people, something that we
>>> consider
>>> to be an anti-pattern.
>>
>> That is not the intent. The intent is for Yahoo! to assign someone to
>> work on this project as a direct contributor. But that person has not yet
>> been identified.
>>
>>> Whomever is to be actively involved in development
>>> should be on the committer list. If it is just a community of just The
>>> Two
>>> Michaels, fine, but the wording should be rephrased.
>>
>> +1 If Y! does not name someone soon, then that entry should be removed. A
>> committer from Y! can always be added later, based on merit.
>
> No; the entry should be removed now.
>
> Yahoo the Company cannot place a reservation on a place at the table for
> an unnamed body. This is not how the ASF works. Nor are committers
> expressed as delegates of the institutions the work for/study at.
> This places a cloud over the acceptance of this particular project, and
> I would encourage everyone to be sure their mentors/champions review the
> text before posting a proposal for incubation..
>
> Bill
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

--
-- David O'Hallaron
-- Director, Intel Research Pittsburgh
-- Assoc Prof of CS and ECE, Carnegie Mellon University
-- http://www.cs.cmu.edu/~droh

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [VOTE]: Buildr 1.3.2 release

2008-07-23T00:31:37Z

On Wed, Jul 23, 2008 at 8:14 AM, Assaf Arkin <arkin@...> wrote:

> On Tue, Jul 22, 2008 at 6:18 AM, ant elder <ant.elder@...> wrote:
> > Looks ok to me so +1.
> >
> > Would be helpful to include a RAT report with the request, but I ran it
> > myself and it didn't highlight any issues.
> >
> > If the doc pdf is going to be distributed separately it should probably
> > include the Incubator disclaimer text, maybe on the page which already
> has
> > the Apache License text.
>
> Welcome/Notices, on page 7.
>
> It's generated from the same source as the web site, so we only have
> to edit one file to include all the proper notices.
>
> Assaf
>
>

Ah ha so it is. All looks fine to me then.

...ant

Re: [VOTE]: Buildr 1.3.2 release

2008-07-23T00:14:55Z

On Tue, Jul 22, 2008 at 6:18 AM, ant elder <ant.elder@...> wrote:
> Looks ok to me so +1.
>
> Would be helpful to include a RAT report with the request, but I ran it
> myself and it didn't highlight any issues.
>
> If the doc pdf is going to be distributed separately it should probably
> include the Incubator disclaimer text, maybe on the page which already has
> the Apache License text.

Welcome/Notices, on page 7.

It's generated from the same source as the web site, so we only have
to edit one file to include all the proper notices.

Assaf

>
> ...ant
>
> On Mon, Jul 21, 2008 at 9:36 PM, Assaf Arkin <arkin@...> wrote:
>
>> Up for vote, the Buildr 1.3.2 release. The release vote passed within
>> the PPMC with +3 (+5 including non-binding votes) and no -1:
>>
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/%3C3de5d7d20807211224x2d649c3i4f6a1c871343f610@...%3E
>>
>>
>> We're voting on the source distributions available here:
>> http://people.apache.org/~assaf/buildr/1.3.2/distro/<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/>
>>
>> Specifically:
>>
>> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz>
>>
>> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip>
>>
>> The documentation generated for this release is available here:
>> http://people.apache.org/~assaf/buildr/1.3.2/site/<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/>
>> http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdf<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/buildr.pdf>
>>
>> The official specification against which this release was tested:
>> http://people.apache.org/~assaf/buildr/1.3.2/site/specs.html<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/specs.html>
>>
>>
>> Changes since 1.3.1:
>> * Added: --prereqs command line argument to show all tasks and their
>> dependencies. You can also follow with regular expression to narrow down
>> the
>> list of tasks.
>> * Changed: Upgraded to Rubyforge 1.0.0.
>> * Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems.
>> * Changed: BUILDR-88 Test classes/resources should come before compile
>> classes/resources so they load up earlier in java classpath.
>> * Changed: BUILDR-102 Update JUnit Version to 4.4.
>> * Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the
>> sources
>> paths.
>> * Fixed: BUILDR-76 Added more specs and fixes to compile task.
>> * Fixed: BUILDR-77 Layout feature not working.
>> * Fixed: BUILDR-79 Remove :source option for Scala compiler
>> * Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon.
>> * Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to
>> load Pageant DLLs when running on JRuby/Windows.
>> * Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include
>> abstract classes.
>> * Fixed: BUILDR-90 Installing from source doesn't work with JRuby.
>> * Fixed: BUILDR-91 When doing a release, buildr should spawn the same
>> version of buildr
>> * Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath.
>> * Fixed: BUILDR-95: Only download Scala test framework artifacts when
>> required
>> * Fixed: BUILDR-100 Directory structure documentation needs updating.
>> * Fixed: Installation instructions updated for RubyGems 1.2.0.
>>
>> Assaf
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: Jt Pattern Oriented Framework (looking for champion/mentors)

2008-07-22T19:44:48Z

I'll update the project proposal with names as soon as I get the chance. As explained in the proposal, we plan to move the project to a central location. Some of the internal project
info/documentation (email, etc) is scattered around. The main focus/goal has been completing the core functionality of the pattern oriented framework.

Regards,

Ed

--- On Tue, 7/22/08, Roland Weber <ossfwot@...> wrote:
From: Roland Weber <ossfwot@...>
Subject: Re: Jt Pattern Oriented Framework (looking for champion/mentors)
To: general@...
Date: Tuesday, July 22, 2008, 4:22 AM

David S (or rather Ed) wrote:
>
> Community
>
> One of the next objectives is to continue growing an active community of
> users and contributors. It is expected that community will continue to
grow.

So you already have an active community of users and contributors?
Any public record of that? Names and/or numbers?

[jira] Commented: (INCUBATOR-77) [IP-GRANT] Local Lucene/Solr Code Dump

2008-07-22T17:53:31Z

[ https://issues.apache.org/jira/browse/INCUBATOR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615846#action_12615846 ]

Ian Holsman commented on INCUBATOR-77:
--------------------------------------

http://people.apache.org/~ianh/locallucene-ASF.tgz
GPG sig: http://people.apache.org/~ianh/locallucene.tgz.sig

$ md5 locallucene-ASF.tgz
MD5 (locallucene-ASF.tgz) = 0eaf4dfab591e8fba997d10916049e81

headers for 99% were converted to standard ASL header.
1 file was not modified LonLatTrig.java in com.traversetechnologies.fulcrum.math
as it is LGPL

my understanding is that this code is being replaced with the code in the mqspatialbase directory, so will not be there in the medium term.

> [IP-GRANT] Local Lucene/Solr Code Dump
> --------------------------------------
>
> Key: INCUBATOR-77
> URL: https://issues.apache.org/jira/browse/INCUBATOR-77
> Project: Incubator
> Issue Type: New Feature
> Environment: lucene.apache.org
> Reporter: Ian Holsman
> Attachments: locallucene.tgz.asc
>
>
> $ rpm -qf $(which md5sum)
> coreutils-5.97-12.1.el5
> $ md5sum locallucene.tgz
> e470f7dfd963994eebb6c5002f810549 locallucene.tgz

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-22T17:36:01Z

Doug Cutting wrote:

> Noel J. Bergman wrote:
>> With respect to "Initially, we plan to start with one committer each from
>> Carnegie Mellon and Intel Research, with a Yahoo committer to be
>> determined
>> later", that's awkwardly phrased. It appears to imply a corporate
>> representative doing commits for "hidden" people, something that we
>> consider
>> to be an anti-pattern.
>
> That is not the intent. The intent is for Yahoo! to assign someone to
> work on this project as a direct contributor. But that person has not
> yet been identified.
>
>> Whomever is to be actively involved in development
>> should be on the committer list. If it is just a community of just
>> The Two
>> Michaels, fine, but the wording should be rephrased.
>
> +1 If Y! does not name someone soon, then that entry should be removed.
> A committer from Y! can always be added later, based on merit.

No; the entry should be removed now.

Yahoo the Company cannot place a reservation on a place at the table for
an unnamed body. This is not how the ASF works. Nor are committers
expressed as delegates of the institutions the work for/study at.
This places a cloud over the acceptance of this particular project, and
I would encourage everyone to be sure their mentors/champions review the
text before posting a proposal for incubation..

Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [PROPOSAL] Tashi

2008-07-22T13:27:40Z

Noel J. Bergman wrote:
> With respect to "Initially, we plan to start with one committer each from
> Carnegie Mellon and Intel Research, with a Yahoo committer to be determined
> later", that's awkwardly phrased. It appears to imply a corporate
> representative doing commits for "hidden" people, something that we consider
> to be an anti-pattern.

That is not the intent. The intent is for Yahoo! to assign someone to
work on this project as a direct contributor. But that person has not
yet been identified.

> Whomever is to be actively involved in development
> should be on the committer list. If it is just a community of just The Two
> Michaels, fine, but the wording should be rephrased.

+1 If Y! does not name someone soon, then that entry should be removed.
A committer from Y! can always be added later, based on merit.

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[VOTE] Release Apache UIMA CasEditor-2.2.2-incubating

2008-07-22T12:55:44Z

Hello,

please vote again to release the Cas Editor. The first vote was
rejected, because the ICU license and notice was
missing, this is now fixed, see UIMA-1115.

On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to
release it.
The vote thread can be found here:

http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg07741.html

The release artifacts and the rat reports can be found at:
http://people.apache.org/~joern/CasEditor-2.2.2-04/

The Cas Editor originally came to Apache under a software grant.

Thanks,
Jörn

[jira] Updated: (INCUBATOR-79) Update guide: releasing-eclipse-update-site to correct some inaccuracies

2008-07-22T11:27:31Z

[ https://issues.apache.org/jira/browse/INCUBATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor updated INCUBATOR-79:
------------------------------------

Attachment: patch.txt

> Update guide: releasing-eclipse-update-site to correct some inaccuracies
> ------------------------------------------------------------------------
>
> Key: INCUBATOR-79
> URL: https://issues.apache.org/jira/browse/INCUBATOR-79
> Project: Incubator
> Issue Type: Improvement
> Reporter: Marshall Schor
> Priority: Minor
> Attachments: patch.txt
>
>
> Found some inaccuracies in the guide while building an eclipse update site: the location of the urlDigest needs to point to the directory containing the digest.zip, not the digest.zip itself. Add info on using relative urls, as well.

[jira] Created: (INCUBATOR-79) Update guide: releasing-eclipse-update-site to correct some inaccuracies

2008-07-22T11:23:31Z

Update guide: releasing-eclipse-update-site to correct some inaccuracies
------------------------------------------------------------------------

Key: INCUBATOR-79
URL: https://issues.apache.org/jira/browse/INCUBATOR-79
Project: Incubator
Issue Type: Improvement
Reporter: Marshall Schor
Priority: Minor

Found some inaccuracies in the guide while building an eclipse update site: the location of the urlDigest needs to point to the directory containing the digest.zip, not the digest.zip itself. Add info on using relative urls, as well.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [VOTE]: Buildr 1.3.2 release

2008-07-22T08:05:06Z

On Mon, Jul 21, 2008 at 1:36 PM, Assaf Arkin <arkin@...> wrote:

> Up for vote, the Buildr 1.3.2 release.

The source package and the gem both look good to me. As Ant mentioned, the
disclaimer in the pdf would be nice to have.

+1

Matthieu

> The release vote passed within
> the PPMC with +3 (+5 including non-binding votes) and no -1:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/%3C3de5d7d20807211224x2d649c3i4f6a1c871343f610@...%3E
>
>
> We're voting on the source distributions available here:
> http://people.apache.org/~assaf/buildr/1.3.2/distro/<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/>
>
> Specifically:
>
> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz>
>
> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip>
>
> The documentation generated for this release is available here:
> http://people.apache.org/~assaf/buildr/1.3.2/site/<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/>
> http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdf<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/buildr.pdf>
>
> The official specification against which this release was tested:
> http://people.apache.org/~assaf/buildr/1.3.2/site/specs.html<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/specs.html>
>
>
> Changes since 1.3.1:
> * Added: --prereqs command line argument to show all tasks and their
> dependencies. You can also follow with regular expression to narrow down
> the
> list of tasks.
> * Changed: Upgraded to Rubyforge 1.0.0.
> * Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems.
> * Changed: BUILDR-88 Test classes/resources should come before compile
> classes/resources so they load up earlier in java classpath.
> * Changed: BUILDR-102 Update JUnit Version to 4.4.
> * Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the
> sources
> paths.
> * Fixed: BUILDR-76 Added more specs and fixes to compile task.
> * Fixed: BUILDR-77 Layout feature not working.
> * Fixed: BUILDR-79 Remove :source option for Scala compiler
> * Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon.
> * Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to
> load Pageant DLLs when running on JRuby/Windows.
> * Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include
> abstract classes.
> * Fixed: BUILDR-90 Installing from source doesn't work with JRuby.
> * Fixed: BUILDR-91 When doing a release, buildr should spawn the same
> version of buildr
> * Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath.
> * Fixed: BUILDR-95: Only download Scala test framework artifacts when
> required
> * Fixed: BUILDR-100 Directory structure documentation needs updating.
> * Fixed: Installation instructions updated for RubyGems 1.2.0.
>
> Assaf
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

Re: [VOTE]: Buildr 1.3.2 release

2008-07-22T06:18:05Z

Looks ok to me so +1.

Would be helpful to include a RAT report with the request, but I ran it
myself and it didn't highlight any issues.

If the doc pdf is going to be distributed separately it should probably
include the Incubator disclaimer text, maybe on the page which already has
the Apache License text.

...ant

On Mon, Jul 21, 2008 at 9:36 PM, Assaf Arkin <arkin@...> wrote:

> Up for vote, the Buildr 1.3.2 release. The release vote passed within
> the PPMC with +3 (+5 including non-binding votes) and no -1:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/%3C3de5d7d20807211224x2d649c3i4f6a1c871343f610@...%3E
>
>
> We're voting on the source distributions available here:
> http://people.apache.org/~assaf/buildr/1.3.2/distro/<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/>
>
> Specifically:
>
> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz>
>
> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip<http://people.apache.org/%7Eassaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip>
>
> The documentation generated for this release is available here:
> http://people.apache.org/~assaf/buildr/1.3.2/site/<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/>
> http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdf<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/buildr.pdf>
>
> The official specification against which this release was tested:
> http://people.apache.org/~assaf/buildr/1.3.2/site/specs.html<http://people.apache.org/%7Eassaf/buildr/1.3.2/site/specs.html>
>
>
> Changes since 1.3.1:
> * Added: --prereqs command line argument to show all tasks and their
> dependencies. You can also follow with regular expression to narrow down
> the
> list of tasks.
> * Changed: Upgraded to Rubyforge 1.0.0.
> * Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems.
> * Changed: BUILDR-88 Test classes/resources should come before compile
> classes/resources so they load up earlier in java classpath.
> * Changed: BUILDR-102 Update JUnit Version to 4.4.
> * Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the
> sources
> paths.
> * Fixed: BUILDR-76 Added more specs and fixes to compile task.
> * Fixed: BUILDR-77 Layout feature not working.
> * Fixed: BUILDR-79 Remove :source option for Scala compiler
> * Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon.
> * Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to
> load Pageant DLLs when running on JRuby/Windows.
> * Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include
> abstract classes.
> * Fixed: BUILDR-90 Installing from source doesn't work with JRuby.
> * Fixed: BUILDR-91 When doing a release, buildr should spawn the same
> version of buildr
> * Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath.
> * Fixed: BUILDR-95: Only download Scala test framework artifacts when
> required
> * Fixed: BUILDR-100 Directory structure documentation needs updating.
> * Fixed: Installation instructions updated for RubyGems 1.2.0.
>
> Assaf
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>
>

Re: Jt Pattern Oriented Framework (looking for champion/mentors)

2008-07-21T21:18:56Z

David S (or rather Ed) wrote:
>
> Community
>
> One of the next objectives is to continue growing an active community of
> users and contributors. It is expected that community will continue to grow.

So you already have an active community of users and contributors?
Any public record of that? Names and/or numbers?

> Orphaned products: The projects has been growing as an open source project
> for several years. The team is committed to continue this work therefore
> the risk is fairly small.

Names or numbers on "the team"? Public records of the growing?
The CVS mails show no relevant activity before October 2007,
nor afterwards.

> Homogenous developers: The people involved with the project work for
> several organizations who are geographically distributed across the world.

The only account used on the project site is "wwwfswcom",
an obvious reference to a website that seems to belong to
a software consulting company.
Can you give some details on "distributed across the world"?
Number of people by country or continent, for example?

> Reliance on salaried developers: This project does not rely
> on salaried contributors. They work on a volunteer basis.

Is the above mentioned software consulting company aware of
the fact that a diverse team of volunteers is indirectly
referencing its website when releasing open source software?

> Project information and complete documentation/sources can be downloaded from
> http://jt.dev.java.net/. java.net forums and mailings lists are not used.

So which forums and/or mailing lists do you use?
As far as I can see you didn't use the CVS repo either,
except for index.html and one drop of code in October 2007.

cheers,
Roland

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

RE: Jt Pattern Oriented Framework (looking for champion/mentors)

2008-07-21T17:23:24Z

Hi folks,

We've put together a draft proposal for the Jt pattern Oriented Framework. I hope it
answers some of the questions regarding project status, community, licensing, etc.

Regards,

Ed

Jt Pattern Oriented Framework

Introduction

This proposal describes a Pattern Oriented Framework for the rapid implementation
of Java applications. This integrated framework is based on a messaging architecture
which provides strong encapsulation and loose coupling; framework components can be
interchangeably plugged into complex framework applications using a “Lego" approach.
This framework provides capabilities for the implementation of applications
based on design patterns. The framework itself is conceived, from the ground up,
based on design patterns. Jt is probably one of the first Pattern Oriented Frameworks
(open source).

Goals

The framework addresses the following goals:

A) The pattern oriented framework implements and/or facilitates the implementation of
well-known design patterns like Gang Of Four design patterns (GoF) and J2EE Design patterns. The framework itself is conceived and implemented based on design patterns (from the ground up). The framework also facilitates and accelerates the implementation of applications based on design patterns.

B) The framework architecture is based on a messaging design pattern: framework objects
are able to interchange information and perform computations by sending, receiving and
processing messages. A messaging API provides strong encapsulation and loose coupling;
framework components can be interchangeably plugged into complex framework applications using a “lego/messaging” architecture. The framework takes full advantage of the power and simplicity of the messaging design pattern/API.

C) The framework lego/messaging architecture provides transparent access to remote components: remote framework objects are treated as local objects. Design patterns implemented by the framework (adapters, remote proxies and facades) make this possible by hiding the complexities associated with remote APIs.

D) The framework provides transparent integration with other technologies via framework
adapters, proxies and the implementation of related design patterns. These technologies include BPM, Data Access Object implementations (DAO), Model View Controller implementations (MVC), EJBs, AJAX, JMS, XML and Web Services.

E) The framework is designed to be lightweight and fast (low overhead/small footprint).

F) The framework messaging/lego architecture should improve and simplify design/development efforts. There should be a tight correspondence between UML design diagrams and the framework messaging based applications and components needed for the implementation. The framework should provide wizards and automated capabilities for generating framework applications. Framework components should be easily added to BPM process diagrams. In future versions of the framework, it should
be possible for application modules to be generated directly from the UML design diagrams.
This goal is still work in progress. There is an early version of the Jt Wizard.

G) The framework messaging architecture facilitates testing and debugging efforts.
It provides capabilities for testing components as independent units by
sending messages to the component and verifying the expected reply messages..

H) In order to provide additional productivity, the framework has been integrated
with open source IDEs.

Criteria

Current Status

The current release of the framework (2.6) meets most of the goals outlined above.
Item F is still work in progress. The software base is very stable (production quality).
Several production applications have been built based on the Jt framework.
Documentation, reference framework applications and examples are available.

Meritocracy

Meritocracy will be fostered and encouraged within the project. We will follow the guidelines of the Apache Software Foundation. Community contributions and feedback are always welcome.We also plan to actively encourage individuals to get involved in the project and be
recognized based on Merit.

Community

One of the next objectives is to continue growing an active community of users and contributors. It is expected that community will continue to grow. So far the main focus has been the completion of the core framework functionality. We see Jt becoming an ASF incubator project as a next step in its evolution. We plan to open the project to a wider audience in order to achieve a larger and more diverse community.

Alignment

Jt is aligned well with existing Apache projects and technologies. The framework
has been integrated with several Apache technologies including Struts (MVC design pattern) and Axis (Web Services Adapter). The Jt automated Wizard capabilities has also been built based on Apache products.

Known Risks

Orphaned products: The projects has been growing as an open source project for several years.The team is committed to continue this work therefore the risk is fairly small.
A preliminary Java Specification Request (JSR) is being worked on.

Inexperience with open source: Some of the current contributors have experience working with open sourceprojects and communities. The team expects to gain additional experience via the ASF incubator community.

Homogenous developers: The people involved with the project work for several organizations who are geographically distributed across the world.

Reliance on salaried developers: This project does not rely on salaried contributors. They work on a volunteer basis.

No ties to other Apache products: As described in the alignment section, this framework has been integrated with many Apache products. The project expects to adopt the Apache License 2.0

An excessive fascination with the Apache brand: This project started outside the Apache Software Foundation. It has been evolving for several years. Hopefully other Apache projects and initiatives will benefit from the capabilities provided by Pattern oriented framework.

Documentation and sources

Project information and complete documentation/sources can be downloaded from
http://jt.dev.java.net/. java.net forums and mailings lists are not used.
We plan to move to a new location which should serve as a central location
for the project.

Apache sponsor

TBD.

ASF resources to be created

- Mailing lists
- A subversion repository
- A JIRA issue tracker

Getting involved

Please send a message to the list if you are interested in joining this project
or using the framework for your particular application.

[VOTE]: Buildr 1.3.2 release

2008-07-21T13:36:33Z

Up for vote, the Buildr 1.3.2 release. The release vote passed within
the PPMC with +3 (+5 including non-binding votes) and no -1:

http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/%3C3de5d7d20807211224x2d649c3i4f6a1c871343f610@...%3E

We're voting on the source distributions available here:
http://people.apache.org/~assaf/buildr/1.3.2/distro/

Specifically:
http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz
http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip

The documentation generated for this release is available here:
http://people.apache.org/~assaf/buildr/1.3.2/site/
http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdf

The official specification against which this release was tested:
http://people.apache.org/~assaf/buildr/1.3.2/site/specs.html

Changes since 1.3.1:
* Added: --prereqs command line argument to show all tasks and their
dependencies. You can also follow with regular expression to narrow down the
list of tasks.
* Changed: Upgraded to Rubyforge 1.0.0.
* Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems.
* Changed: BUILDR-88 Test classes/resources should come before compile
classes/resources so they load up earlier in java classpath.
* Changed: BUILDR-102 Update JUnit Version to 4.4.
* Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the sources
paths.
* Fixed: BUILDR-76 Added more specs and fixes to compile task.
* Fixed: BUILDR-77 Layout feature not working.
* Fixed: BUILDR-79 Remove :source option for Scala compiler
* Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon.
* Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to
load Pageant DLLs when running on JRuby/Windows.
* Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include
abstract classes.
* Fixed: BUILDR-90 Installing from source doesn't work with JRuby.
* Fixed: BUILDR-91 When doing a release, buildr should spawn the same
version of buildr
* Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath.
* Fixed: BUILDR-95: Only download Scala test framework artifacts when required
* Fixed: BUILDR-100 Directory structure documentation needs updating.
* Fixed: Installation instructions updated for RubyGems 1.2.0.

Assaf

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [VOTE] Accept Click for Incubation

2008-07-21T06:45:16Z

+1

Craig

On Jul 14, 2008, at 4:14 AM, Henning Schmiedehausen wrote:

> This vote will run until Monday, July 21st, 2008.
>
> [ ] +1 Accept Click for incubation
> [ ] 0 Don't care
> [ ] -1 Reject for the following reason:
>
> ------------
> = Click Proposal =

Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@...
P.S. A good JDO? O, Gasp!

smime.p7s (3K) Download Attachment

Re: [RESULT] Re: [VOTE] Accept Click for Incubation

2008-07-21T03:12:06Z

On Jul 21, 2008, at 12:42 PM, Henning Schmiedehausen wrote:

> Note: Andrus and Will have requested to join the Incubator PMC but
> were
> no IPMC members at the time when they voted.

I can vote one more time with my IPMC member hat on ;-) Not that we
don't have enough votes.

Andrus

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

Re: [RESULT] Re: [VOTE] Accept Click for Incubation

2008-07-21T03:04:08Z

That is great news, thanks for your support.

regards Malcolm Edgar

On Mon, Jul 21, 2008 at 7:42 PM, Henning Schmiedehausen
<henning@...> wrote:

> And the results are in:
>
> +1
>
> Alan D. Cabrera (*)
> Andrus Adamchik
> Bertrand Delacretaz (*)
> Davanum Srinivas (*)
> Eelco Hillenius
> Henning Schmiedehausen (*)
> Jim Jagielski (*)
> Les Hazlewood
> Martijn Dashorst (*)
> Niall Pemberton (*)
> Niklas Gustavsson
> Siegfried Goeschl
> Ted Husted (*)
> Will Glass-Husain
> William A. Rowe (*)
>
> (* == Incubator PMC)
>
> Note: Andrus and Will have requested to join the Incubator PMC but were
> no IPMC members at the time when they voted.
>
> 0:
>
> none
>
> -1:
>
> none
>
> Congratulations to the Click team, you have been accepted to the
> Incubator as a podling.
>
> Ciao
> Henning
>
>
>
> On Mon, 2008-07-14 at 13:14 +0200, Henning Schmiedehausen wrote:
>> This vote will run until Monday, July 21st, 2008.
>>
>> [ ] +1 Accept Click for incubation
>> [ ] 0 Don't care
>> [ ] -1 Reject for the following reason:
>>
>> ------------
>> = Click Proposal =
>>
>> This proposal specifies the migration of Click web application framework
>> to the Apache Software Foundation as a Top Level Project.
>>
>> http://click.sourceforge.net/
>>
>> == Rationale ==
>>
>> Click is a modern J2EE web application framework released under the
>> Apache License 2.0. It takes a component and page orientated approach to
>> web applications with its main goals being ease of use and low barrier
>> to entry. A major difference between Click and other component oriented
>> frameworks, is that Click is stateless by design, although stateful
>> pages are supported. It is an optimal framework, always trading off
>> bloating features to its main goals of simplicity. Another important
>> focus of the project has been to provide high quality documentation and
>> examples to get people started as quickly as possible.
>>
>> We see Click becoming an Apache project as a logical step in its
>> evolution. Becoming part of the Apache community will increase
>> visibility and expose the framework to a larger community of developers.
>>
>> === Current Status ===
>>
>> == Meritocracy ==
>>
>> Click was developed by Malcolm Edgar in 2003 publicly released in March
>> 2005. Since then there have been contributions from a number of
>> developers across the world. New contributors are encouraged to provide
>> patches, and later commit privileges are assigned to them. In 2008 Bob
>> Schellink joined Malcolm Edgar as a joint lead on the project after
>> contributing to the project for a number of years.
>>
>> == Community ==
>>
>> Click is a small but growing community of users and developers. Its two
>> mailing lists receive around 200 messages per month.
>>
>> == Core Developers ==
>>
>> * Malcolm Edgar
>> * Bob Schellink
>> * Naoki Takezoe
>> * Ahmed Mohombe
>>
>> == Alignment ==
>>
>> Click has already built up relationships with existing Apache projects
>> especially Velocity and Cayenne. Using Velocity as its default rendering
>> engine, Click has formed a close relationship with the Velocity
>> community. Click also supports good integration with the Apache Cayenne
>> ORM framework.
>>
>> == Known Risks ==
>>
>> * Orphaned Software: Click has a healthy community of users and
>> developers and has a very low risk of becoming orphaned. Experience With
>> Open Source: Click was started as an open source project in 2005 and has
>> remained so for 3 years.
>> * Homogeneous Developers: The community is very diverse with users
>> and developers from all over the world.
>> * Reliance on salaried developers: None of the Click developers are
>> compensated for their contributions. It is a complete voluntary project.
>> * Relationships with Other Apache Products: As mentioned in the
>> Alignment section, Click has formed close relationships with Velocity
>> and Cayenne. Other Apache products used include commons-* and log4j.
>> * An Excessive Fascination with the Apache Brand: Although it is
>> true that the Apache Brand will increase visibility of the framework, we
>> are more interested in building stronger relationships and influence
>> Apache projects such as Velocity.
>>
>>
>> == Scope of the project ==
>>
>> Currently Click consists of the following parts: the core framework, an
>> extras package for non core controls, an examples project and a quick
>> start project. There is also an Eclipse plugin called ClickIDE.
>>
>> == Initial Source ==
>>
>> Click sources is available from http://sourceforge.net/projects/click
>>
>> == External Dependencies ==
>>
>> There are some concerns over incompatible licensed libraries Click
>> depends on.
>>
>> * calendar.js is released under a LGPL licensed library from
>> http://www.dynarch.com/projects/calendar/
>> * Hibernate is released under a LGPL licensed library from
>> http://www.hibernate.org/
>> * HSQLDB is released under the license specified here:
>> http://hsqldb.org/web/hsqlLicense.html
>>
>>
>> == Required Resources ==
>>
>> == Mailing lists ==
>>
>> Create new mailing lists
>>
>> * click-dev
>> * click-private
>>
>>
>> == Subversion Directory ==
>>
>> Migrate the current subversion code from sourceforge to Apache
>>
>> * https://svn.apache.org/repos/asf/incubator/click
>>
>>
>> == Issue Tracking ==
>>
>> * Need to create a new JIRA project called CLICK for the Click
>> framework
>> * Migrate the current JIRA issue tracker from
>> http://www.avoka.com/jira/
>>
>>
>> == Other Resources ==
>>
>> Need to create a new Confluence Wiki
>>
>> * CLICK
>>
>>
>> == Initial Committers ==
>>
>> The initial committers for the project should include:
>>
>> * Malcolm Edgar
>> * Bob Schellink
>> * Naoki Takezoe
>> * Ahmed Mohombe
>> * Henning Schmiedehausen
>> * Will Glass-Husain
>> * Ted Husted
>> * Andrus Adamchik
>>
>>
>> == Sponsors ==
>>
>> === Champion ===
>>
>> * Henning Schmiedehausen
>>
>>
>> === Nominated Mentors ===
>>
>> * Will Glass-Husain
>> * Ted Husted
>> * Andrus Adamchik
>>
>>
>> === Sponsoring Entity ===
>>
>> * Velocity
>> ----------------
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@...
>> For additional commands, e-mail: general-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...