Please subscribe to [e-mail]

[Dan Peterson]

Hi everyone,

As we prepare to move over to the Apache infrastructure, please go ahead and
sign up to the proper mailing list: send an email to
wave-dev-subscribe-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org and that will provision your email
address as member of wave-dev-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org

-Dan

---------- Forwarded message ----------
From: Alex North <anorth-hpIqsD4AKlfQT0dZR+***@public.gmane.org>
Date: Mon, Dec 6, 2010 at 4:44 PM
Subject: Re: Search wave design proposal
To: wave-protocol-/***@public.gmane.org


I think we should allow a small grace period for people to sign up to the
apache list. I only just did after processing an email back-log. Let's make
a loud announcement here that everyone should subscribe to the apache lists,
then make an atomic break where we lock out posting to this list and begin
posting on the apache one.

And let's further discuss this in some other thread.

Friendly suggestion -- shall we move this conversation over to
This means that we all need to sign up to that list. To sign up send an

I like the idea of managing indexes, search results, and folders in
wavelets.
I also like the idea of making the search request in a wavelet. Say,
placing the query in a document named "query" and the results would appear
in documents starting with "result+". If we added the concept of transient
wavelets (say all placed in a wave named "transient"), then it would be
easier for clients to know what wavelets should not be persisted locally.
-Tad

Hey all,
A few months ago Joseph and I worked on a design for using a wave as the
communication transport for search results, including your inbox. We then
decided that while this mechanism is good and wavey, Wave in a Box would be
better served by first taking advantage of the search Data API to get basic
inbox and search functionality without adding so much code.
I'm publishing the design now just because it's come up in a few
conversations. I don't think we should implement it (or something like it)
yet, but perhaps some time next year after basic WIAB is up and functional.
https://sites.google.com/a/waveprotocol.org/wave-protocol/protocol/design-proposals/search-wave-design-proposal
A.
--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To post to this group, send email to wave-protocol-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to
wave-protocol+unsubscribe-/***@public.gmane.org<wave-protocol%2Bunsubscribe-/***@public.gmane.org>
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

[Alex North]

In case you didn't gather from the forwarded text, we intend to turn off
this wave-protocol forum after allowing some time for you all to join the
incubator list. I propose doing so around the end of this week.

If you intend to write or review code you should also subscribe to
wave-commits-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org by emailing
wave-commits-subscribe-***@public.gmane.org I gather this list will receive
code reviews and commit notifications much like
wave-protocol-code-discuss-/***@public.gmane.org does now.

A.

Post by Dan Peterson
Hi everyone,
As we prepare to move over to the Apache infrastructure, please go ahead
and sign up to the proper mailing list: send an email to
-Dan
---------- Forwarded message ----------
Date: Mon, Dec 6, 2010 at 4:44 PM
Subject: Re: Search wave design proposal
I think we should allow a small grace period for people to sign up to the
apache list. I only just did after processing an email back-log. Let's make
a loud announcement here that everyone should subscribe to the apache lists,
then make an atomic break where we lock out posting to this list and begin
posting on the apache one.
And let's further discuss this in some other thread.

Friendly suggestion -- shall we move this conversation over to
This means that we all need to sign up to that list. To sign up send an

I like the idea of managing indexes, search results, and folders in
wavelets.
I also like the idea of making the search request in a wavelet. Say,
placing the query in a document named "query" and the results would appear
in documents starting with "result+". If we added the concept of transient
wavelets (say all placed in a wave named "transient"), then it would be
easier for clients to know what wavelets should not be persisted locally.
-Tad

Hey all,
A few months ago Joseph and I worked on a design for using a wave as the
communication transport for search results, including your inbox. We then
decided that while this mechanism is good and wavey, Wave in a Box would be
better served by first taking advantage of the search Data API to get basic
inbox and search functionality without adding so much code.
I'm publishing the design now just because it's come up in a few
conversations. I don't think we should implement it (or something like it)
yet, but perhaps some time next year after basic WIAB is up and functional.
https://sites.google.com/a/waveprotocol.org/wave-protocol/protocol/design-proposals/search-wave-design-proposal
A.
--
You received this message because you are subscribed to the Google
Groups "Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

[Jeremy NGL]

Hi guys,


Just wanted to let you know that for some readers (at least for me)
those mailing list adresses you're trying to promote appears truncated
on screen (and are not links)...
I'm also a member of the group, even if I've only posted once, so that
shouldn't be hidden to me I suppose.


Here's a screenshot :




I'm quite sure the second address is : wave-dev @
incubator.apache.org ;-) ...
But I can only make a guess about the first one (and most useful)
being : wave-dev-subscribe @ incubator.apache.org


Thanks for clarifying !

[Jon Spriggs]

Post by Jeremy NGL
Hi guys,
Just wanted to let you know that for some readers (at least for me)
those mailing list adresses you're trying to promote appears truncated
on screen (and are not links)...
I'm also a member of the group, even if I've only posted once, so that
shouldn't be hidden to me I suppose.
incubator.apache.org ;-) ...
But I can only make a guess about the first one (and most useful)
Thanks for clarifying !
--
You received this message because you are subscribed to the Google
Groups "Wave Protocol" group.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

This is usually where you need to enter a captcha to verify you're not a stinky address harvester.

Click on it to fix the issue :)

All the best,

[Jeremy NGL]

Nothing happens when I click on it...
Using Chrome 8.0.552.215 beta and Safari 5.0 leads to the same
results : those truncated addresses are not links for me !



Could this be because my membership is set on "no emails
notifications" ?
I'm reading and posting trough the new Google Groups interface :
https://groups.google.com/forum/?fromgroups#topic/wave-protocol/Vy_Om0FUwZk

[Tad Glines]

Post by Jeremy NGL
Nothing happens when I click on it...
those truncated addresses are not links for me !
Could this be because my membership is set on "no emails notifications" ?
https://groups.google.com/forum/?fromgroups#topic/wave-protocol/Vy_Om0FUwZk

It's because you are using the new Google Groups interface. That interface
is public (as in anyone, including nasty spammers) can read the posts. So,
the interface obfuscates e-mail addresses.

-Tad

[Jeremy NGL]

[jbills]

[Alex North]

Post by Alex North
In case you didn't gather from the forwarded text, we intend to turn off
this wave-protocol forum after allowing some time for you all to join the
incubator list. I propose doing so around the end of this week.

I'm just waiting for some of the committers to be given Apache accounts so
that we can moderate the wave-dev list before making the switch. It sounds
like this will be a couple of days away.

Alex

Post by Alex North
If you intend to write or review code you should also subscribe to
receive code reviews and commit notifications much like
A.

Post by Dan Peterson
Hi everyone,
As we prepare to move over to the Apache infrastructure, please go ahead
and sign up to the proper mailing list: send an email to
-Dan
---------- Forwarded message ----------
Date: Mon, Dec 6, 2010 at 4:44 PM
Subject: Re: Search wave design proposal
I think we should allow a small grace period for people to sign up to the
apache list. I only just did after processing an email back-log. Let's make
a loud announcement here that everyone should subscribe to the apache lists,
then make an atomic break where we lock out posting to this list and begin
posting on the apache one.
And let's further discuss this in some other thread.

Friendly suggestion -- shall we move this conversation over to
This means that we all need to sign up to that list. To sign up send an

I like the idea of managing indexes, search results, and folders in
wavelets.
I also like the idea of making the search request in a wavelet. Say,
placing the query in a document named "query" and the results would appear
in documents starting with "result+". If we added the concept of transient
wavelets (say all placed in a wave named "transient"), then it would be
easier for clients to know what wavelets should not be persisted locally.
-Tad

Hey all,
A few months ago Joseph and I worked on a design for using a wave as
the communication transport for search results, including your inbox. We
then decided that while this mechanism is good and wavey, Wave in a Box
would be better served by first taking advantage of the search Data API to
get basic inbox and search functionality without adding so much code.
I'm publishing the design now just because it's come up in a few
conversations. I don't think we should implement it (or something like it)
yet, but perhaps some time next year after basic WIAB is up and functional.
https://sites.google.com/a/waveprotocol.org/wave-protocol/protocol/design-proposals/search-wave-design-proposal
A.
--
You received this message because you are subscribed to the Google
Groups "Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google
Groups "Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

[vadbars]

Something has changed in these days? Does started work this mailing list?

[Alex North]

Committers are still waiting on Apache accounts.

Post by vadbars
Something has changed in these days? Does started work this mailing list?
And what will happen with this Google-group, will it be next?
--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.

[Alex North]

Alright, enough committers now have apache.org accounts and it's time to
move discussions entirely onto the wave-dev-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org list. The
same goes for the wave-protocol-code-discuss moving to wave-commits.

Please continue any future conversations from this list on the Apache one
instead. I will block posting to this group in a few days time. The archives
will remain accessible at http://groups.google.com/group/wave-protocol.

Reminder: subscribe to wave-dev-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org by sending mail to
wave-dev-subscribe-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org (and
wave-commits-subscribe-d1GL8uUpDdXTxqt0kkDzDmD2FQJk+8+***@public.gmane.org).

A.

Post by Alex North
Committers are still waiting on Apache accounts.

Post by vadbars
Something has changed in these days? Does started work this mailing list?
And what will happen with this Google-group, will it be next?
--
You received this message because you are subscribed to the Google Groups
"Wave Protocol" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.