nion on the UX...
—Zachary Yaro
On 13 September 2013 14:00, Upayavira wrote:
> Bruno,
>
> You are kinda right, and kinda not :-)
>
> I guess the thing is, it is perhaps best to say that this release
> *ISN'T* about code, it is about everything else.
>
> And that
Yes, thank you, I really appreciate the additional clarification. Should I
send such a vote to the RC4 vote thread, or is there going to be a later
RC5 thread I should wait for?
—Zachary Yaro
On 14 September 2013 04:26, Ali Lown wrote:
> > > Also, don't assume you need to be
on the main
WIAB project. I continue to work on gadgets, the
WEG<http://waveextensions.org>,
and wave-related Chrome extensions.
—Zachary Yaro
On 28 November 2013 11:36, Thomas Wrobel wrote:
> On 28 November 2013 15:41, Frank R. wrote:
>
> > Hi Ewan
> >
> >
FWIW, I agree with Fleeky. Most of the extensions I have developed for
Rizzoma have been because a bug or missing feature annoys me regularly. If
people used WIAB regularly, I think they would start to notice glaring and
subtle usability problems and be more inclined to fix them.
—Zachary Yaro
is a
great idea because it gives those of us who do *not* prefer Java a bigger
way to contribute to the wave ecosystem.
—Zachary Yaro
On 1 December 2013 06:47, Thomas Wrobel wrote:
> " I still want a web client, but it should be
> written in pure javascript."
>
> GWT
from forking the GitHub mirror (or, for
that matter, creating a separate GitHub project for their own wave
implementation).
—Zachary Yaro
On 10 December 2013 15:10, Upayavira wrote:
> As I'm sure you can imagine, I've been thinking about this quite a bit
> recently. If a project sti
Move to git at Apache.
—Zachary Yaro
On 14 December 2013 01:37, Basavaraj K N [MaGE] <
basavaraj...@manipalglobal.com> wrote:
> Mov to git
>
> -Original Message-
> From: Angus Turner [mailto:ad...@theangus.org]
> Sent: Saturday, December 14, 2013 6:56 AM
> To
I honestly thought he was already, but welcome, Andrew! I am a big fan of
the work you have done over on wiab.pro and look forward to all the ways I
am sure you will improve WIAB :D
Zachary Yaro
On 19 July 2014 17:57, Yuri Z wrote:
> Wavers,
>
> Please join me in welcoming Andrew Ka
collaboration, and I really want to see that kept alive.
Zachary Yaro
On 15 March 2015 at 11:46, Thomas Wrobel wrote:
> Thanks for that I'll look into both your Javascript API and your Android
> one.
>
> Is your communication between client and server just between your forked
>
with other Material apps, but that is just nitpicking. Overall
these seem like pretty good designs, and I look forward to seeing them
implemented in an app :)
Zachary Yaro
On 19 June 2015 at 16:06, Roshan Lakmal wrote:
> Hi All
> Here I have created the App mockups.
> Can you all please
I doubt that can be copyrighted. Plenty of other apps—including Rizzoma—do
that. I think some apps even did that before Google did.
Zachary Yaro
On Jun 21, 2015 19:10, "John Blossom" wrote:
> This looks very, very nice so far. Are there any copyright issues with the
> use of t
I would have cast a vote, but I read non-binding votes were discouraged.
To clarify, what are the criteria for being able to cast a binding vote for
this project?
Zachary Yaro
On 17 October 2015 at 21:48, Ali Lown wrote:
> Hi all,
>
> Thanks to Yuri and Jeremy for downloading and t
I am interested in helping with this. What are the associated deadlines?
Zachary Yaro
On Jan 30, 2016 11:17, "Michael MacFadden"
wrote:
> I agree. I did the initial design of the site we have many years ago, and
> we really haven’t done much with it since than. Should w
I am inclined to agree with Yuri—if the alternative implementation can be
developed in parallel around the same protocol, that would seem to be the
best scenario, but the existing codebase should be kept because it is
(AFAIK) the most functional implementation of the protocol.
Zachary Yaro
On Mar
Congratulations! Welcome, Evan, and thank you for contributing your time
and skills to Apache Wave!
Zachary Yaro
On May 11, 2016 11:59, "Yuri Z" wrote:
> The Project Management Committee (PMC) for Apache Wave
> has asked Evan Hughes to become a committer and we are pleased
&g
I am in a similar boat. I have front-end development skills, but I
struggle to fully understand the back-end functionality or begin separating
the client from the server.
Zachary Yaro
On Aug 30, 2016 11:51 AM, "Thomas Wrobel" wrote:
> I have tried on 3 separate occasions to u
).
That said, the original Google Wave took two years to develop with a full
dev team and support from a large corporation. I am concerned restarting
from zero might not be as feasible with the small team we have here.
Zachary Yaro
On Aug 31, 2016 09:47, "Thomas Wrobel" wrote:
>
I am excited to see all this. It is unlikely I can join the call during
work hours—is there any chance it could be recorded (e.g., done as a
Hangout On Air) so I can catch up later?
Thank you,
Zachary Yaro
On Sep 5, 2016 11:16, "Adam John" wrote:
> @pablo that is great that yo
I do not mean to upend plans you might already have in place, but is there
a reason not to use a Hangout or Hangout On Air? That would allow people
like Thomas and myself to join in the text chat even though we cannot join
via voice/video.
Zachary Yaro
On Wednesday, 28 September 2016, Adam John
WaveInABox.net used to host an Apache Wave demo instance, but presumably
the domain expired and someone else bought it up. Those links were correct
at the time they were added, but they should probably be removed now.
Zachary Yaro
On Tuesday, 4 October 2016, Philip McGrath wrote:
> I&#x
Welcome! Thank you for helping move Wave forward!
Zachary Yaro
On Thursday, 12 January 2017, Yuri Z wrote:
> The Project Management Committee (PMC) for Apache Wave has invited Pablo
> Ojanguren to become a committer and we are pleased to announce that he has
> accepted.
> Pablo
+1; I think a lot of us have voiced support over the years for decoupling
the Wave server from its current GUI, and it sounds like this approach
would be a great shift in that direction.
Zachary Yaro
On Tuesday, 21 March 2017, Michael MacFadden
wrote:
> Pablo,
>
> +1 on this approach
documentation and mailing list archives from Apache, and would anything be
done to help migrate that elsewhere?
(On a related note, do we still have access to waveprotocol.org and the
related mailing list? That would seem to be the logical place to migrate
to.)
Zachary Yaro
On 27 November 2017 at 14
If possible, I think it would be better to hold off on the vote until we
know what the new homes for the mailing list, code repo, and documentation
will be, and ensure we can update waveprotocol.org with those details.
Zachary Yaro
On 29 November 2017 at 04:41, Yuri Z wrote:
> So, if we hav
I do not recall getting an answer to this before: do we still have access
to the old (pre-Apache) mailing list?
Zachary Yaro
On Jan 27, 2018 10:53, "Upayavira" wrote:
On Sat, 27 Jan 2018, at 2:34 PM, John D. Ament wrote:
> Hi all,
>
> I missed sending the notice to this li
25 matches
Mail list logo
