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
[email protected] by emailing
[email protected]. I gather this list will receive
code reviews and commit notifications much like
[email protected] does now.

A.

On 7 December 2010 15:53, Dan Peterson <[email protected]> wrote:

> 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
> [email protected] and that will provision your email
> address as member of [email protected]
>
> -Dan
>
> ---------- Forwarded message ----------
> From: Alex North <[email protected]>
> Date: Mon, Dec 6, 2010 at 4:44 PM
> Subject: Re: Search wave design proposal
> To: [email protected]
>
>
> 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.
>
>
> On 7 December 2010 11:28, Dan Peterson <[email protected]> wrote:
>
>> Friendly suggestion -- shall we move this conversation over to
>> [email protected]?
>>
>> This means that we all need to sign up to that list. To sign up send an
>> email to [email protected]
>>
>>
>> On Mon, Dec 6, 2010 at 3:49 PM, Tad Glines <[email protected]> wrote:
>>
>>> 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
>>>
>>>
>>> On Mon, Dec 6, 2010 at 2:44 PM, Alex North <[email protected]> wrote:
>>>
>>>> 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 post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to
>>>> [email protected]<wave-protocol%[email protected]>
>>>> .
>>>> 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 [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected]<wave-protocol%[email protected]>
>>> .
>>> 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 [email protected].
>> To unsubscribe from this group, send email to
>> [email protected]<wave-protocol%[email protected]>
>> .
>> 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 [email protected].
> To unsubscribe from this group, send email to
> [email protected]<wave-protocol%[email protected]>
> .
> 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 [email protected].
> To unsubscribe from this group, send email to
> [email protected]<wave-protocol%[email protected]>
> .
> 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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en.

Reply via email to