On 12/11/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Hen
I'm just following what I considered was the procedure. I'm happy to
take your advice, but I would have thought that the incubator list
needed the opportunity to vote.
They just need the opportunity to -1. It's more efficient to just
n
+1 from me as well .. my vote wasn't going thru because I was traveling
and I had my smtp going out on port 25 and the damned hotel ISP was
trying to be too smart. I used to use smtp over ssl (465) and had to
turn that off somewhere else because it wasn't working. Anyway now I'm
back in action and
Thanks for the links
Having read the chain, I can see that putting incubating in the
version helps maintain continuity as we graduate. But in our case it
breaks continuity with our previous releases and format.
Given that we meet the requirements of the incubator (having the
artefacts clearly ma
On Monday 11 December 2006 03:43, Paul Fremantle wrote:
> Dan
>
> Thanks for noting the lack of an incubator disclaimer in the META-INF.
> I hadn't seen this requirement in the docs, but it makes sense to me.
>
> As for the naming convention, we used the current convention in our
> previous releas
Hen
I'm just following what I considered was the procedure. I'm happy to
take your advice, but I would have thought that the incubator list
needed the opportunity to vote.
Sanjiva has voted. He had some problems with the list, but his vote
got through eventually.
I think Glen should be on the I
Dan
Thanks for noting the lack of an incubator disclaimer in the META-INF.
I hadn't seen this requirement in the docs, but it makes sense to me.
As for the naming convention, we used the current convention in our
previous release and I'd rather leave it alone if its just a
preference. For my own
On 7/7/06, Justin Erenkrantz <[EMAIL PROTECTED]> wrote:
On 7/6/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
> A project graduates from the incubator when the incubator PMC comes to
> a consensus that the project has resolved any existing legal issues,
> has built a sustainable community around i
Apache Synapse has an unusual history for an incubated project. While
there was a contributed codebase from Infravio, we looked at this
codebase (which was built on Axis1) and decided to re-write completely
based on Axis2. So the code we have built, the community and users we
have created have fun
On 7/6/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
A project graduates from the incubator when the incubator PMC comes to
a consensus that the project has resolved any existing legal issues,
has built a sustainable community around itself, and is operating in a
way that is consistent with how s
Garrett,
This is great to hear, one of the mails in the thread was getting me
concerned.
Thanks for the reply.
Carl.
Garrett Rooney wrote:
On 7/6/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
I am spending many hours working through Apache processes so do you mind
if I ask a few questions
Matthias
We did the original check on Synapse when we started the project.
nameprotect.com seems quite different since then and I couldn't simply
find the same page that I used last year, but there is an online
trademark search here:
http://tess2.uspto.gov/bin/gate.exe?f=searchss&state=b3bfcn.1.1
Hey Paul-
I just looked at your page [1] and saw a "DONE" before the task
If applicable, make sure that any associated name does not already
exist and check www.nameprotect.com to be sure that the name is not
already trademarked for an existing software product.
I'd like to do the same for th
On 7/6/06, Carl Trieloff <[EMAIL PROTECTED]> wrote:
I am spending many hours working through Apache processes so do you mind
if I ask a few questions:
For the graduation,
a.) what are the demographics of the commiters added to the project
in the community building and how/is this considered in
I am spending many hours working through Apache processes so do you mind
if I ask a few questions:
For the graduation,
a.) what are the demographics of the commiters added to the project
in the community building and how/is this considered in graduation?
b.) if there are committers on the pro
Well, not to chime in "me too" but in order to get up-to-speed
enough to cast a vote, I also looked over the archives, and
I saw a lot of code commits but little "online" development
as well... so it was hard to trace the commits to actual
community discussion and debate.
So I share Noel's concer
Noel
Firstly thanks for the scrutiny.
I agree that we've perhaps become a little quiet on the dev list. We
had some very intense discussions earlier this year and having got
over those and worked out a way forward we've just had plenty of
coding to do to implement the changes. I also agree that
Paul,
Before I vote, I'd like to ask you a community related question.
Looking at the June mail archives for Synapse (actually, I looked at other
months as well), I see a lot of commits but very little discussion. Yes,
some, but not much. More in May than in June, but a downtrend in mailing
lis
+1 for graduation and +1 for closing the vote. The normal period is 72
hours, so 10 days is within the margin of error.
Sanjiva.
On Thu, 2006-07-06 at 10:13 +0100, Paul Fremantle wrote:
> This vote has now been running for 10 days. We have 4 +1s of which 3
> are binding:
>
> Roy Fielding +1
> Da
This vote has now been running for 10 days. We have 4 +1s of which 3
are binding:
Roy Fielding +1
Davanum Srinivas +1
Ant Elder (non-binding) +1
Paul Fremantle +1
I am happy for this vote to continue - as long as the time is actually
being used productively.
If everyone has had enough time to s
The page is now updated and seems to have made it through to the website.
Paul
On 7/3/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Thanks for pointing that out. The PMC vote has now completed. I'll
update right now.
Paul
On 7/3/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> The referenced web
Thanks for pointing that out. The PMC vote has now completed. I'll
update right now.
Paul
On 7/3/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
The referenced web site has the following:
"Organizational acceptance of responsibility for the project
* Has the receiving PMC voted to accept it?
The referenced web site has the following:
"Organizational acceptance of responsibility for the project
* Has the receiving PMC voted to accept it? In Progress
"
Is this up to date?
On 7/4/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Someone pointed out to me that the original $subject mi
Someone pointed out to me that the original $subject might be confusing.
Paul
On 7/3/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
+1 from me.
Paul
On 6/30/06, ant elder <[EMAIL PROTECTED]> wrote:
> +1 (non-binding)
>
>...ant
>
> On 6/27/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> >
+1 from me.
Paul
On 6/30/06, ant elder <[EMAIL PROTECTED]> wrote:
+1 (non-binding)
...ant
On 6/27/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
>
> +1 from me.
>
> On 6/26/06, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
> > > The Synapse incubator would like to ask the Incubator PMC to
>
+1 (non-binding)
...ant
On 6/27/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
+1 from me.
On 6/26/06, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
> > The Synapse incubator would like to ask the Incubator PMC to
> > release the
> > Synapse project into the Apache Web Services PMC. Synapse h
+1 from me.
On 6/26/06, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
> The Synapse incubator would like to ask the Incubator PMC to
> release the
> Synapse project into the Apache Web Services PMC. Synapse heavily
> integrates with other WS projects including Axis2, Axiom, Sandesha,
> Rampart.
>
>
The Synapse incubator would like to ask the Incubator PMC to
release the
Synapse project into the Apache Web Services PMC. Synapse heavily
integrates with other WS projects including Axis2, Axiom, Sandesha,
Rampart.
The Synapse status page is here:
http://incubator.apache.org/projects/synapse.h
27 matches
Mail list logo
