+1.
Sanjiva.
On Thu, 2006-07-13 at 08:48 +0200, Jason van Zyl wrote:
Hi,
There has been plenty of discussion around the CeltiXfire proposal,
we feel that all the issues forwarded have been addressed, and we
would now like to officially propose CeltiXfire to the Incubator for
Alex Karasulu wrote:
...
I'm fine with this option as well. Let's give it a try. Do the rest of
you guys agree with this approach?
...
I think moving asyncweb within a Mina TLP would be very healty for the
project.
One thing I would like to discuss though is identity
AsyncWeb
Felix is using a Confluence wiki at SafeHaus. We have a dump which we
would like to import into the ASF Confluence. However, SafeHaus uses
2.2, ASF 2.1.5.
Would it be acceptable for Felix to consider graduation without having
migrated the wiki yet, on the basis that it will as soon as the ASF has
Hi,
So far we have 8 binding votes and I was wondering what the official
time period was for the voting window? Is it 72 hours as it is for
everything else? Just want to move on to the next phase of the
process if that is permissible at this point. Here are the votes that
have been cast
On 7/17/06, Jason van Zyl [EMAIL PROTECTED] wrote:
Hi,
So far we have 8 binding votes and I was wondering what the official
time period was for the voting window? Is it 72 hours as it is for
everything else?
AFAICT there is no official position or consensus on this. see this
thread:
On Jul 17, 2006, at 5:31 AM, Dave Irving wrote:
One thing I would like to discuss though is identity
AsyncWeb currently has some form of identity in its own right as a
project
(and is already bundled as a standalone http transport in a couple
of OSS
projects). Is this likely to be
peter royal wrote:
I was thinking of a similar relationship to MINA and Directory..
AsyncWeb would *not* be renamed MINA HTTP.
Sounds good to me :o)
Dave
--
View this message in context:
http://www.nabble.com/-pre-proposal--AsyncWeb-tf1931092.html#a5359859
Sent from the Apache
On 17 Jul 06, at 7:47 AM 17 Jul 06, robert burrell donkin wrote:
On 7/17/06, Jason van Zyl [EMAIL PROTECTED] wrote:
Hi,
So far we have 8 binding votes and I was wondering what the official
time period was for the voting window? Is it 72 hours as it is for
everything else?
AFAICT there is
On 7/17/06, peter royal [EMAIL PROTECTED] wrote:
On Jul 17, 2006, at 5:31 AM, Dave Irving wrote:
One thing I would like to discuss though is identity
AsyncWeb currently has some form of identity in its own right as a
project
(and is already bundled as a standalone http transport in a
Trustin Lee wrote:
One possibility though could be that MINA HTTP codec provides only encoder
and decoder implementation for HTTP messages and AsyncWeb is built on top
of
it to provide more tighter integration with existing webapp frameworks and
more HTTP-friently asynchronous APIs. Yep,
(resending since i think my first try didn't get noticed by the
httpclient-dev moderators)
howdy!
I'm writing to see if there is interest in collaborating in a larger
effort to develop HTTP code that utilizes NIO.
MINA http://directory.apache.org/subprojects/mina/ is a framework
here at
On 7/17/06, Dave Irving [EMAIL PROTECTED] wrote:
Trustin Lee wrote:
One possibility though could be that MINA HTTP codec provides only
encoder
and decoder implementation for HTTP messages and AsyncWeb is built on
top
of
it to provide more tighter integration with existing webapp
Trustin Lee wrote:
It makes total sense. I'd love to see everything becomes real, though we
need to draw a line between generalization and specialization when we
generalize AsyncWeb because MINA already has its role to provide a generic
network application framework.
Absolutely.
Attached is the Blaze project proposal for incubation consideration, we
welcomes your feedback. The
proposal has also been posted on the wiki at
http://wiki.apache.org/incubator/Blaze
Text copy of wiki.
= (Blaze Proposal) =
== RATIONALE ==
Blaze provides multiple language implementations of
As Noel enjoys belittling projects that don't have a 3 month collective
memory... I'm preempting his opportunity to bash your project and sending
you all a quick reminder of your status reports due this month;
http://wiki.apache.org/incubator/July2006
If your project is listed, ensure its
Hey Bill,
adffaces
I saw the project status list yesterday and added adffaces.
I didn't know that this list is only for projects that don't have a 3
month collective
memory..., since we posted last month a status report.
I think it is ok to add a status to that wiki, isn't it?
Or only for
Ah,
according to [1] the next report must be submitted in Sept.
:)
-Matthias
[1] http://wiki.apache.org/incubator/ReportingSchedule
On 7/17/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hey Bill,
adffaces
I saw the project status list yesterday and added adffaces.
I didn't know that
Matthias, I would think you can either move your reporting back one
cycle if you like, or simply See June report. Of course, if your
report was after the June reports were forwarded to the board (after
the deadline) then you better dup your last month status to July.
Bill
Matthias Wessendorf
Bill,
I already removed adffaces from that page :)
We'll wait for next cycle, which is in September.
Internally we track our status with the SVN based status file and
*move* it to the
homepage, when some *important* changes happened, so that it needs a
*public* reflection.
-Matthias
On
Matthias Wessendorf wrote:
I didn't know that this list is only for projects that don't have a 3
month collective memory...
I suspect that he was making a bit of a joke, along the lines of C'mon
folks, how hard is it to remember to get your [EMAIL PROTECTED] report in every
quarter?!
we
On 7/17/06, Noel J. Bergman [EMAIL PROTECTED] wrote:
Matthias Wessendorf wrote:
I didn't know that this list is only for projects that don't have a 3
month collective memory...
I suspect that he was making a bit of a joke, along the lines of C'mon
folks, how hard is it to remember to get
Roy,
Thanks. So let's clarify some of these issues (out of order from your
reply).
[The need for a Mentor to be an ASF Member was] imposed by
no other agency than the Incubator PMC, itself.
A need imposed by the board when it created the Incubator with a given
purpose that cannot be
For prior discussion, see the thread
[doc] Roles and Responsibilities Update Needed
in our archives.
Based upon various discussions we have had lately, I am putting for the
following as what I consider a reasonable attempt to build a consensus:
An Incubator Project SHOULD have at least
Dave,
Sending reminders to me for the Incubator PMC report isn't terribly helpful,
since we report every month. But what WOULD help would be if you could
generate reports for all of our projects.
See http://wiki.apache.org/incubator/ReportingSchedule, but it is just like
normal Board reports.
We have several projects that appear to be dormant, so let's discuss what
that means in terms of operational mechanics.
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.
On 7/17/06, Noel J. Bergman [EMAIL PROTECTED] wrote:
We have several projects that appear to be dormant, so let's discuss what
that means in terms of operational mechanics.
FWIW, It's merely the lack of a clue as to what needs to be changed
that's kept me from closing down lucene4c. Well,
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
On 7/17/06, Noel J. Bergman [EMAIL PROTECTED] wrote:
Or do we just turn
them off, with a bounce notice that people interested in resurrecting the
project contact us on [EMAIL PROTECTED]
That's probably the easiest thing to do. -- justin
Garrett Rooney wrote:
FWIW, It's merely the lack of a clue as to what needs to be changed
that's kept me from closing down lucene4c.
That, and Agila and a couple of others, prompted my e-mail.
I'd suggest that the PMC declare a project as dormant, with the effect
being
that we set the
On 7/17/06, Noel J. Bergman [EMAIL PROTECTED] wrote:
Garrett Rooney wrote:
FWIW, It's merely the lack of a clue as to what needs to be changed
that's kept me from closing down lucene4c.
That, and Agila and a couple of others, prompted my e-mail.
I'd suggest that the PMC declare a project
The interest around the BPEL implementation in Agila has mostly moved to Ode
and the workflow part isn't evolving so declaring the project as dormant
sounds fair enough. As for the policy, wouldn't it be possible to do a two
step thing? Like:
1. Make svn read-only and the mailing-list subscriber
Noel J. Bergman wrote:
We have several projects that appear to be dormant, so let's discuss what
that means in terms of operational mechanics.
Usually a project requests to change their status to abandoned/dormant,
but a gentle ping if we don't see two status reports over two months,
or any
32 matches
Mail list logo
