Noel J. Bergman wrote:
Craig.Russell wrote:
It would appear then that the "Apache Jini" podling would be the
[spec project], and the "to be named" podling the [implementation
project]. Fortunately, the incubator should be warmed up for a
naming discussion.
Apache JINI and Apache JINN?
Craig L Russell wrote:
>
> On Aug 13, 2006, at 7:05 PM, Geir Magnusson Jr wrote:
>
>> As the champion for JINI, I suppose it behooves me to try and get this
>> untangled.
>>
>> I'm not a Jini expert, but my understanding is that it is it's own spec
>> ecosystem. Therefore, I'm against having o
Craig.Russell wrote:
> It would appear then that the "Apache Jini" podling would be the
> [spec project], and the "to be named" podling the [implementation
> project]. Fortunately, the incubator should be warmed up for a
> naming discussion.
Apache JINI and Apache JINN? Deliberate play on words,
On 8/14/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
Noel J. Bergman wrote:
> Steve Toback wrote:
>
>> The Lokahi community voted on and has approved a proposal to release
>> Lokahi M01.
>
> I see that Yoav voted +1, but neither Bill Stoddard nor William Rowe. Were
> there reasons for tho
Noel J. Bergman wrote:
> Steve Toback wrote:
>
>> The Lokahi community voted on and has approved a proposal to release
>> Lokahi M01.
>
> I see that Yoav voted +1, but neither Bill Stoddard nor William Rowe. Were
> there reasons for those non-votes?
Travel and work commitments, nothing more ama
Steve Toback wrote:
> The Lokahi community voted on and has approved a proposal to release
> Lokahi M01. Pursuant to the Releases section of the Incubation Policy
> we would now like to request the permission of the Incubator PMC to
> publish the tarball on the Lokahi Download page.
+1
Bill
On Aug 13, 2006, at 7:05 PM, Geir Magnusson Jr wrote:
As the champion for JINI, I suppose it behooves me to try and get this
untangled.
I'm not a Jini expert, but my understanding is that it is it's own
spec
ecosystem. Therefore, I'm against having one project doing software
implementation
Geir Magnusson Jr wrote:
> I'd like to propose that we create two podlings, one for JINI
> governance, and one for building the implementation and
> community around the working code that has been proposed.
> Comments?
None of an objecting nature. Would this satisfy the desires of the JINI
comm
Geir,
>> If Sun is going to do the trademark assignment, there is no difference.
>> We would have the trademark for the technology domain. And if you take
>> into consideration the concurrent talk about specifications coming under
>> ASF practices, that would dovetail nicely.
> Sorry, I think it
Geir Magnusson Jr wrote:
> Noel J. Bergman wrote:
>> Geir Magnusson Jr wrote:
>>> Noel J. Bergman wrote:
Wait ... why can't a specification be a releasable, just like a
codebase? The only issue, as I see it, would be enforcement of
compliance. And Roy even put forward a proposed li
As the champion for JINI, I suppose it behooves me to try and get this
untangled.
I'm not a Jini expert, but my understanding is that it is it's own spec
ecosystem. Therefore, I'm against having one project doing software
implementation that is called "Jini", just as I'd be against projects
like
Geir Magnusson Jr wrote:
>
> It's an implementation of a spec. A single spec that is part of an
> external spec-governing ecosystem, the JCP. "Jini" isn't a spec, it's
> it's own spec ecosystem. It's not part of the JCP, for example.
>
> So Apache Jini is like saying Apache JCP (I'm stretching
Noel J. Bergman wrote:
> Geir Magnusson Jr wrote:
>> Noel J. Bergman wrote:
>>> I don't know that the name is an issue at all, if Sun is willing to
> transfer
>>> the trademark to the ASF, as was done with SpamAssassin. The impression
>>> that I have from Craig and others is that this is do-able
Noel J. Bergman wrote:
> Geir Magnusson Jr wrote:
>> Noel J. Bergman wrote:
>>> Wait ... why can't a specification be a releasable, just like a
>>> codebase? The only issue, as I see it, would be enforcement of
>>> compliance. And Roy even put forward a proposed license amendment
>>> for such t
Geir Magnusson Jr wrote:
> Noel J. Bergman wrote:
> > I don't know that the name is an issue at all, if Sun is willing to
transfer
> > the trademark to the ASF, as was done with SpamAssassin. The impression
> > that I have from Craig and others is that this is do-able. According to
> > Simon, thi
Craig.Russell wrote:
> Noel J. Bergman wrote:
>> Cliff Schmidt wrote:
>>> Just as I was posting the vote thread for the Glasgow project, I saw
>>> Noel had updated the new wiki page with a concern about the name
>>> collision with the old Sun codename
>> Only because I hadn't seen Craig's e-mail fi
Geir Magnusson Jr wrote:
> Noel J. Bergman wrote:
>> Wait ... why can't a specification be a releasable, just like a
>> codebase? The only issue, as I see it, would be enforcement of
>> compliance. And Roy even put forward a proposed license amendment
>> for such things.
> Which license amendment
What broken mail client are you using?
inline...
Noel J. Bergman wrote:
> Carl Trieloff wrote:
>
>> -> Is Apache in the business of writing and publishing specifications? <-
>
>> As long as Apache is not in the business of also creating
>> specifications, there will be by definition some separ
Noel J. Bergman wrote:
> Geir Magnusson Jr wrote:
>
>> I think that instead of spinning on this lock, we should move forward
>> with some other name to get things booted, and then resolve the Jini
>> name issue in parallel.
>
> I don't know that the name is an issue at all, if Sun is willing to
Noel J. Bergman wrote:
> david reid wrote:
>
>> Where is the information you maintain presently?
>
> The site is built from
> https://svn.apache.org/repos/asf/incubator/public/trunk/, and the specific
> stuff that you'd be looking for is in multiple locations:
>
> Projects (one file per):
>
On Aug 13, 2006, at 11:50 AM, Noel J. Bergman wrote:
Cliff Schmidt wrote:
Just as I was posting the vote thread for the Glasgow project, I saw
Noel had updated the new wiki page with a concern about the name
collision with the old Sun codename
Only because I hadn't seen Craig's e-mail first
Steve Toback wrote:
> The Lokahi community voted on and has approved a proposal to release
> Lokahi M01.
I see that Yoav voted +1, but neither Bill Stoddard nor William Rowe. Were
there reasons for those non-votes?
> http://people.apache.org/~toback/lokahi-incubating-M01.tar.gz
The Incubator d
The Lokahi community voted on and has approved a proposal to release
Lokahi M01. Pursuant to the Releases section of the Incubation Policy
we would now like to request the permission of the Incubator PMC to
publish the tarball on the Lokahi Download page.
Thanks
Steve
Proposal:
http://mail-arch
One option in AMQP would be to write a custom exchange to handle the
concept of delivery at a scheduled time. Exchanges are effectively an
extension point in the protocol so that you can customise delivery
algorithms.
The Glasgow broker currently doesn't have a well defined API to allow the
averag
In the thread titled "RE: [Proposal] Blaze", James Strachan wrote:
> Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > Totally unrelated ... JMS has the ability to create a message filter,
but
> > one of the limitations is that the filter is applied when the receiver
is
> > created, rather than when
Cliff Schmidt wrote:
> Just as I was posting the vote thread for the Glasgow project, I saw
> Noel had updated the new wiki page with a concern about the name
> collision with the old Sun codename
Only because I hadn't seen Craig's e-mail first. :-) But I believe that we
have ended up with a be
Eelco Hillenius wrote:
> On 8/4/06, J Aaron Farr <[EMAIL PROTECTED]> wrote:
> > 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
Alex Karasulu wrote:
> You cannot put a time on how long the incubation will actually take
> because things change and you never know if the podling is actually
> meeting up to the requirements.
Readers should keep in mind that Alex also brought an existing Open Source
project, with community, to
On Aug 13, 2006, at 10:49 AM, Noel J. Bergman wrote:
Carl Trieloff wrote:
-> Is Apache in the business of writing and publishing
specifications? <-
As long as Apache is not in the business of also creating
specifications, there will be by definition some separation
between code and spec p
Carl Trieloff wrote:
> -> Is Apache in the business of writing and publishing specifications? <-
> As long as Apache is not in the business of also creating
> specifications, there will be by definition some separation
> between code and spec processes, and I would like to work
> with the ASF to
Cliff,
> The Glasgow proposal vote has passed with:
> 6 binding +1s, 2 binding 0s, and 2 binding -1s.
> There were also 5 non-binding +1s and 2 non-binding -1s.
So 11 +1 and 4 -1. That passes by a fairly large majority, BUT the concerns
of the dissenters should be addressed. The major one app
Geir Magnusson Jr wrote:
> I think that instead of spinning on this lock, we should move forward
> with some other name to get things booted, and then resolve the Jini
> name issue in parallel.
I don't know that the name is an issue at all, if Sun is willing to transfer
the trademark to the ASF,
I'm going to reply to this as I found no good point in the thread.
I think that instead of spinning on this lock, we should move forward
with some other name to get things booted, and then resolve the Jini
name issue in parallel.
Clearly there's sufficient interest to see this become an Apache
co
david reid wrote:
> Where is the information you maintain presently?
The site is built from
https://svn.apache.org/repos/asf/incubator/public/trunk/, and the specific
stuff that you'd be looking for is in multiple locations:
Projects (one file per):
https://svn.apache.org/repos/asf/incubat
Noel J. Bergman wrote:
> david reid wrote:
>> Noel J. Bergman wrote:
>>> david reid wrote:
All I need is a list of when the project should report and the email
address to send the reminder to. If you can provide those in an
accessible format then I'll send out reminders without a pro
35 matches
Mail list logo
