from:"Ali Lown"

Re: Wave build system updated to Gradle

2015-12-16 Thread Ali Lown

Thank you Evan for the huge amount of work involved in replacing the
old Ant system.

@Yuri: Are you on updating the Jenkins script to call the test suite
through gradle instead?

Ali

On 16 December 2015 at 15:44, Yuri Z  wrote:
> Hi
> I have just merged pulled request by Evan Hughes that replaced the old ANT
> based system with Gradle.
> I think it is a gig and important change.
> I want to use thus opportunity to thank Evan for his effort!

Re: Licensing issue

2015-11-22 Thread Ali Lown

Evan,

You are correct that the file header has been changed from the
original which looked like [0].

I am not aware of any reason that the Google agreement made with the
ASF during the migration would not cover this particular file under
it.
As such, my understanding is that the "licensed to the ASF under one
or more contributor license agreements" holds, and supersedes the
previous license (from google to the open-source world in general),
which would require maintaining the "Copyright Google Inc" part.

Replacing the file with a newer version would not fall under the
Google-ASF migration agreement though, so would be required to
maintain the "copyright Google" header instead (and update NOTICES as
well).

Ali

[0]: 
https://code.google.com/p/wave-protocol/source/browse/src/google/protobuf/descriptor.proto

On 21 November 2015 at 08:15, Evan Hughes  wrote:
> While working on moving us to gradle I decided to upgrade us to the 2.6
> version of the proto library and discovered that
> proto/google/protobuf/descriptor.proto is the original google owned code
> which has the license stripped.
>
> In order to upgrade I have had to import the 2.6 version of the file and it
> works but seeking advice on what I do with the license of the file.
>
> regards
> Evan Hughes

Re: [RESULT][VOTE] Wave 0.4.0-rc10

2015-11-14 Thread Ali Lown

I am trying to get enough votes from IPMC, we need 3 but only have 2
currently (Justin, Christian).

Ali

On 14 November 2015 at 00:25, Evan Hughes <ehu...@gmail.com> wrote:
> Is the release still stuck due to the issue the general member is having?
> On 06/11/2015 4:13 AM, "Upayavira" <u...@odoko.co.uk> wrote:
>
>> Ahh, got it. What you meant was:
>>   6 committer votes
>>   1 mentor vote
>>   4 non-binding
>>
>> I took it to mean 6 votes total, of which 1 mentor and 4 non-bonding.
>>
>> Clarity shines forth, thank you.
>>
>> Are you now in a position to forward this to general@incubator?
>>
>> Thx
>>
>> On Thu, Nov 5, 2015, at 05:10 PM, Ali Lown wrote:
>> > Upayavira,
>> >
>> > Am I overlooking something?
>> >
>> > I definitely wrote 6 committer votes (+1 mentor vote) in the email
>> > dated 3rd November.
>> >
>> >
>> https://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201511.mbox/%3CCABRGrVenajwQPBw98Zy99UqrMNNQMJ-X5tGcWWAMR3xNX%2Bnu7w%40mail.gmail.com%3E
>> >
>> > Ali
>> >
>> > On 3 November 2015 at 19:46, Upayavira <u...@odoko.co.uk> wrote:
>> > > Congrats Ali, and good luck with your future plans!
>> > >
>> > > Can I ask you to check those tallies? I'm sure there are more
>> > > committer/PPMC member votes than two.
>> > >
>> > > Upayavira
>> > >
>> > > On Tue, Nov 3, 2015, at 03:22 PM, Ali Lown wrote:
>> > >> Hi all,
>> > >>
>> > >> Thanks for taking part in verifying this release candidate, it is
>> > >> great to finally be able to take a potential release to the others in
>> > >> the incubator!
>> > >> (I apologize for not following up sooner, I have finally graduated
>> > >> from Uni, so am now sorting out what comes next...)
>> > >>
>> > >> These results supersede the email I sent dated 18th October, with the
>> > >> results now looking like:
>> > >>
>> > >> +1: 6 (+1 mentor, +4 non-binding)
>> > >> +0: 0
>> > >> -0:  0
>> > >> -1:  0
>> > >>
>> > >> Ali
>> > >>
>> > >> On 18 October 2015 at 02:48, Ali Lown <a...@lown.me.uk> wrote:
>> > >> > Hi all,
>> > >> >
>> > >> > Thanks to Yuri and Jeremy for downloading and trying out this RC.
>> > >> >
>> > >> > Well, I set a "deadline" around the 17th October which has now well
>> > >> > and truly passed.
>> > >> >
>> > >> > My vote on the matter was a +1 (though I realize that I failed to
>> put
>> > >> > this in my original email, so you are allowed to ignore this for
>> > >> > failing to meet my own deadline).
>> > >> >
>> > >> > The result looks something like (including mine):
>> > >> > +1: 3 (2 binding)
>> > >> > +0: 0
>> > >> > -0: 0
>> > >> > -1: 0
>> > >> >
>> > >> > Unfortunately we have had insufficient votes to meet the release
>> > >> > requirement (minimum of 3 +1 binding votes, more + than -) [0].
>> > >> > Binding votes as decided by people in [1].
>> > >> >
>> > >> > @Yuri/Jeremy: How do you feel now about us moving away from Apache,
>> as
>> > >> > this vote does seem to suggest that there is not enough interest
>> from
>> > >> > the currently defined committers to maintain this project here.
>> > >> >
>> > >> > I am not really sure why none of the other committers responded at
>> all
>> > >> > to the vote...
>> > >> >
>> > >> > Ali
>> > >> >
>> > >> > [0]:
>> https://www.apache.org/foundation/voting.html#votes-on-code-modification
>> > >> > [1]: https://people.apache.org/committers-by-project.html#wave
>> > >> >
>> > >> > On 14 October 2015 at 17:27, Jérémy Naegel <jeremy@gmail.com>
>> wrote:
>> > >> >> +1
>> > >> >>
>> > >> >> +Jérémy Naegel <http://google.com/+JérémyNaegel
>> <http://google.com/+J%C3%A9r%C3%A9myNaegel>>
>> > >> >> Public Information Offic

Re: [VOTE] Apache Wave Release 0.4.0-incubating (RC10)

2015-11-06 Thread Ali Lown

Hi Ian,

I am not sure about the best way to import this into eclipse, I have
always used the CLI tools directly. I have CC'd the dev-list in case
they have a better answer for you.

The inability to find  ${build.classpath.path}, ${build.macros.path}
suggests that you are missing/failed-to-import/failed-to-reference the
build.properties file which contains the values for these macros.

The follow-up problem about missing define-gxpc is to be expected
because of the above problem resulting in it not importing
build-macros.xml, which defines "define-gxpc" amongst other things.

Ali

On 6 November 2015 at 14:51, Ian Dunlop  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
>
> I'll give it at 0 the moment since I encountered a build issue. I
> downloaded the src zip and imported the code into Eclipse Mars (4.50)
> with jdk 1.7.0_79 & ANT 1.9.4 but found the following issues:
>
> 1)
> BUILD FAILED
> C:\Users\idunlop\workspace\waveinabox\build.xml:28: Cannot find
> C:\Users\idunlop\workspace\waveinabox\${build.classpath.path} imported
> from C:\Users\idunlop\workspace\waveinabox\build.xml
>
> Resolved by commenting out
>
>   
>
>   
>   
>
> and tried again
>
> 2)
>
> BUILD FAILED
> Target "define-gxpc" does not exist in the project "waveinabox". It is
> used from target "gen-gxp".
>
> Resolved by removing define-gxpc from
>
>  depends="init, define-gxpc, gen-gxp-dep" unless="skip.gen-gxp">
>  destdir="${gen.dir}/gxp"
> target="org.waveprotocol.box.server.gxp" />
> 
>   
>
> 3)
>
> BUILD FAILED
> C:\Users\idunlop\workspace\waveinabox\build.xml:120: Problem: failed
> to create task or type buildproto
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any / declarations have taken
> place.
>
> At that point I figured it best to report the issues here:
>
> Is there a procedure for building in eclipse, am I missing an ant
> setting somewhere?
>
> So, apart fromn the compile issue everything else looks good:
>
> signatures are good
> artifact/hashes good
> DISCLAIMER OK
> LICENCE OK
> NOTICE OK
>
> Cheers,
>
> Ian
>
>
>
> On 04/11/2015 07:14, Justin Mclean wrote:
>> Hi,
>>
>> +1 binding.
>>
>> Could you please fix the LICENCE Appendix in the next release. The
>> text should be "Copyright [] [name of copyright owner]” not
>> "Copyright 2013 The Apache Software Foundation”.
>>
>> I checked: - artefact has incubating in name - signatures and
>> hashes good - DISCLAIMER exists - LICENSE  has minor issue with the
>> copyright in the appendix. Not required but it could also use the
>> sort form in LICENSE [1] particularly as you bundle the software
>> LICENSE files. - NOTICE good. - All source files have Apache
>> headers - No unexpected binary file in source release (but see
>> below) - can compile from source - test pass
>>
>> I notice there’s a couple of photographs in the source release, I
>> assume you have permission from the person who took them to use
>> these? IF so you may want to put that in the LICENSE.
>>
>> There's a number of binary file without extensions in
>> /thumbnail_patterns/ but they all look to be PNGs is this the case?
>> Where did these images come from?
>>
>> I had a quick look at the binary release and the LICENCE and NOTICE
>> appear comprehensive. I didn;t do a though check. I did notice that
>> the year is incorrect in the NOTICE file and LICENSE appendix has
>> the same issue.  It’s actually wrong here as non ASF Apache
>> licensed software is mentioned. There no need to mean Apache
>> licensed software in the LICENCE but no harm is done by donning so.
>> [2]
>>
>> Thanks, Justin
>>
>> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> 2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
>>
>>
>>
>> -
>>
>>
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> - --
> Ian Dunlop, eScience Lab
> School of Computer Science
> The University of Manchester
> http://orcid.org/-0001-7066-3350
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJWPL6FAAoJEPK45GBX+Cy5agYH/3yPH2vLCltvOqIZlv70TJ9R
> EmdbRL6rvpJjcah+GH9BPpsYEeENXw5WTARH42RVZT4gFUz62GBIkZhhqFks0/qx
> ubL+bekcivMI2P/eZ3T6S/mKw52d8esRaDvrMKaUZ3Ax3tdkYt/dPaYoXGxAMNS4
> 5IolSgvMaTT2qKlcx0fmCh+gdfmxHFo0ZTvZ55V9ucnmsvQY8orGqZt7SJ+jdySz
> vp9AIvnxStMCorZ8tKSLDVo1H+ciQOXxCZWymFlAlm7nQAw5KoLQYMp/OBUrw6Lk
> urdolruKU7YGgdwh5uV8WHi+cCfpIyQIRaIz8nFlXYTFx/VL8Dm7vrgFpcH1jyw=
> =d5Aa
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [RESULT][VOTE] Wave 0.4.0-rc10

2015-11-05 Thread Ali Lown

Upayavira,

Am I overlooking something?

I definitely wrote 6 committer votes (+1 mentor vote) in the email
dated 3rd November.

https://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201511.mbox/%3CCABRGrVenajwQPBw98Zy99UqrMNNQMJ-X5tGcWWAMR3xNX%2Bnu7w%40mail.gmail.com%3E

Ali

On 3 November 2015 at 19:46, Upayavira <u...@odoko.co.uk> wrote:
> Congrats Ali, and good luck with your future plans!
>
> Can I ask you to check those tallies? I'm sure there are more
> committer/PPMC member votes than two.
>
> Upayavira
>
> On Tue, Nov 3, 2015, at 03:22 PM, Ali Lown wrote:
>> Hi all,
>>
>> Thanks for taking part in verifying this release candidate, it is
>> great to finally be able to take a potential release to the others in
>> the incubator!
>> (I apologize for not following up sooner, I have finally graduated
>> from Uni, so am now sorting out what comes next...)
>>
>> These results supersede the email I sent dated 18th October, with the
>> results now looking like:
>>
>> +1: 6 (+1 mentor, +4 non-binding)
>> +0: 0
>> -0:  0
>> -1:  0
>>
>> Ali
>>
>> On 18 October 2015 at 02:48, Ali Lown <a...@lown.me.uk> wrote:
>> > Hi all,
>> >
>> > Thanks to Yuri and Jeremy for downloading and trying out this RC.
>> >
>> > Well, I set a "deadline" around the 17th October which has now well
>> > and truly passed.
>> >
>> > My vote on the matter was a +1 (though I realize that I failed to put
>> > this in my original email, so you are allowed to ignore this for
>> > failing to meet my own deadline).
>> >
>> > The result looks something like (including mine):
>> > +1: 3 (2 binding)
>> > +0: 0
>> > -0: 0
>> > -1: 0
>> >
>> > Unfortunately we have had insufficient votes to meet the release
>> > requirement (minimum of 3 +1 binding votes, more + than -) [0].
>> > Binding votes as decided by people in [1].
>> >
>> > @Yuri/Jeremy: How do you feel now about us moving away from Apache, as
>> > this vote does seem to suggest that there is not enough interest from
>> > the currently defined committers to maintain this project here.
>> >
>> > I am not really sure why none of the other committers responded at all
>> > to the vote...
>> >
>> > Ali
>> >
>> > [0]: 
>> > https://www.apache.org/foundation/voting.html#votes-on-code-modification
>> > [1]: https://people.apache.org/committers-by-project.html#wave
>> >
>> > On 14 October 2015 at 17:27, Jérémy Naegel <jeremy@gmail.com> wrote:
>> >> +1
>> >>
>> >> +Jérémy Naegel <http://google.com/+JérémyNaegel>
>> >> Public Information Officer
>> >>
>> >> On Mon, Oct 12, 2015 at 9:24 PM, Yuri Z <vega...@gmail.com> wrote:
>> >>
>> >>> +1
>> >>> I did the following:
>> >>> - Checked signatures
>> >>> - Opened the binary and verified it works.
>> >>> - Opened the source and verified that it can be built and works.
>> >>> - Reviewed the changes for the rc 10.
>> >>>
>> >>> Ali - Thanks for making this RC!
>> >>>
>> >>> On Sat, Oct 10, 2015 at 9:59 AM Ali Lown <a...@lown.me.uk> wrote:
>> >>>
>> >>> > Hi all,
>> >>> >
>> >>> > RC10 is now available for review.
>> >>> > Artefacts can be found here:
>> >>> > https://people.apache.org/~al/wave_rc/0.4-rc10/
>> >>> > (Remember checksums are from 'gpg --print-md SHA512 $f > $f.sha')
>> >>> >
>> >>> > I have included both source and binary artefacts for convenience.
>> >>> >
>> >>> > The release version (if successful) will be 0.4.0-incubating
>> >>> >
>> >>> > This is taken from the branch 0.4.0-rc10 of the incubator-wave
>> >>> repository.
>> >>> >
>> >>> > Notable changes since earlier initial release attempts include:
>> >>> > - Use of typesafe config
>> >>> > - Bumped versions of Jetty, GWT, etc.
>> >>> > - Assorted tweaks to build system
>> >>> >
>> >>> > A summary of useful information can be found in RELEASE-NOTES, and a
>> >>> > list of changes in CHANGES in the source artefacts.
>> >>> >
>> >>> > Action Required:
>> >>> > Please go and test these packages (most importantly the source ones)
>> >>> > for any outstanding legal problems, or any runtime problems in a
>> >>> > 'standard' configuration.
>> >>> >
>> >>> > We are not looking for a perfect first release, as there is plenty of
>> >>> > time to fix outstanding bugs in future releases, but we do want to get
>> >>> > 0.4 out soon (at long last).
>> >>> >
>> >>> > This vote will close around  GMT 17th October 2015.
>> >>> >
>> >>> > [ ] +1 Release it!
>> >>> > [ ] +0 Ok, but...
>> >>> > [ ] -0  Ok, but you really should fix...
>> >>> > [ ] -1 Definitely do not release this because...
>> >>> >
>> >>> > Thanks,
>> >>> > Ali
>> >>> >
>> >>>

Re: [RESULT][VOTE] Wave 0.4.0-rc10

2015-11-03 Thread Ali Lown

Hi all,

Thanks for taking part in verifying this release candidate, it is
great to finally be able to take a potential release to the others in
the incubator!
(I apologize for not following up sooner, I have finally graduated
from Uni, so am now sorting out what comes next...)

These results supersede the email I sent dated 18th October, with the
results now looking like:

+1: 6 (+1 mentor, +4 non-binding)
+0: 0
-0:  0
-1:  0

Ali

On 18 October 2015 at 02:48, Ali Lown <a...@lown.me.uk> wrote:
> Hi all,
>
> Thanks to Yuri and Jeremy for downloading and trying out this RC.
>
> Well, I set a "deadline" around the 17th October which has now well
> and truly passed.
>
> My vote on the matter was a +1 (though I realize that I failed to put
> this in my original email, so you are allowed to ignore this for
> failing to meet my own deadline).
>
> The result looks something like (including mine):
> +1: 3 (2 binding)
> +0: 0
> -0: 0
> -1: 0
>
> Unfortunately we have had insufficient votes to meet the release
> requirement (minimum of 3 +1 binding votes, more + than -) [0].
> Binding votes as decided by people in [1].
>
> @Yuri/Jeremy: How do you feel now about us moving away from Apache, as
> this vote does seem to suggest that there is not enough interest from
> the currently defined committers to maintain this project here.
>
> I am not really sure why none of the other committers responded at all
> to the vote...
>
> Ali
>
> [0]: https://www.apache.org/foundation/voting.html#votes-on-code-modification
> [1]: https://people.apache.org/committers-by-project.html#wave
>
> On 14 October 2015 at 17:27, Jérémy Naegel <jeremy@gmail.com> wrote:
>> +1
>>
>> +Jérémy Naegel <http://google.com/+JérémyNaegel>
>> Public Information Officer
>>
>> On Mon, Oct 12, 2015 at 9:24 PM, Yuri Z <vega...@gmail.com> wrote:
>>
>>> +1
>>> I did the following:
>>> - Checked signatures
>>> - Opened the binary and verified it works.
>>> - Opened the source and verified that it can be built and works.
>>> - Reviewed the changes for the rc 10.
>>>
>>> Ali - Thanks for making this RC!
>>>
>>> On Sat, Oct 10, 2015 at 9:59 AM Ali Lown <a...@lown.me.uk> wrote:
>>>
>>> > Hi all,
>>> >
>>> > RC10 is now available for review.
>>> > Artefacts can be found here:
>>> > https://people.apache.org/~al/wave_rc/0.4-rc10/
>>> > (Remember checksums are from 'gpg --print-md SHA512 $f > $f.sha')
>>> >
>>> > I have included both source and binary artefacts for convenience.
>>> >
>>> > The release version (if successful) will be 0.4.0-incubating
>>> >
>>> > This is taken from the branch 0.4.0-rc10 of the incubator-wave
>>> repository.
>>> >
>>> > Notable changes since earlier initial release attempts include:
>>> > - Use of typesafe config
>>> > - Bumped versions of Jetty, GWT, etc.
>>> > - Assorted tweaks to build system
>>> >
>>> > A summary of useful information can be found in RELEASE-NOTES, and a
>>> > list of changes in CHANGES in the source artefacts.
>>> >
>>> > Action Required:
>>> > Please go and test these packages (most importantly the source ones)
>>> > for any outstanding legal problems, or any runtime problems in a
>>> > 'standard' configuration.
>>> >
>>> > We are not looking for a perfect first release, as there is plenty of
>>> > time to fix outstanding bugs in future releases, but we do want to get
>>> > 0.4 out soon (at long last).
>>> >
>>> > This vote will close around  GMT 17th October 2015.
>>> >
>>> > [ ] +1 Release it!
>>> > [ ] +0 Ok, but...
>>> > [ ] -0  Ok, but you really should fix...
>>> > [ ] -1 Definitely do not release this because...
>>> >
>>> > Thanks,
>>> > Ali
>>> >
>>>

[RESULT][VOTE] Wave 0.4.0-rc10

2015-10-17 Thread Ali Lown

Hi all,

Thanks to Yuri and Jeremy for downloading and trying out this RC.

Well, I set a "deadline" around the 17th October which has now well
and truly passed.

My vote on the matter was a +1 (though I realize that I failed to put
this in my original email, so you are allowed to ignore this for
failing to meet my own deadline).

The result looks something like (including mine):
+1: 3 (2 binding)
+0: 0
-0: 0
-1: 0

Unfortunately we have had insufficient votes to meet the release
requirement (minimum of 3 +1 binding votes, more + than -) [0].
Binding votes as decided by people in [1].

@Yuri/Jeremy: How do you feel now about us moving away from Apache, as
this vote does seem to suggest that there is not enough interest from
the currently defined committers to maintain this project here.

I am not really sure why none of the other committers responded at all
to the vote...

Ali

[0]: https://www.apache.org/foundation/voting.html#votes-on-code-modification
[1]: https://people.apache.org/committers-by-project.html#wave

On 14 October 2015 at 17:27, Jérémy Naegel <jeremy@gmail.com> wrote:
> +1
>
> +Jérémy Naegel <http://google.com/+JérémyNaegel>
> Public Information Officer
>
> On Mon, Oct 12, 2015 at 9:24 PM, Yuri Z <vega...@gmail.com> wrote:
>
>> +1
>> I did the following:
>> - Checked signatures
>> - Opened the binary and verified it works.
>> - Opened the source and verified that it can be built and works.
>> - Reviewed the changes for the rc 10.
>>
>> Ali - Thanks for making this RC!
>>
>> On Sat, Oct 10, 2015 at 9:59 AM Ali Lown <a...@lown.me.uk> wrote:
>>
>> > Hi all,
>> >
>> > RC10 is now available for review.
>> > Artefacts can be found here:
>> > https://people.apache.org/~al/wave_rc/0.4-rc10/
>> > (Remember checksums are from 'gpg --print-md SHA512 $f > $f.sha')
>> >
>> > I have included both source and binary artefacts for convenience.
>> >
>> > The release version (if successful) will be 0.4.0-incubating
>> >
>> > This is taken from the branch 0.4.0-rc10 of the incubator-wave
>> repository.
>> >
>> > Notable changes since earlier initial release attempts include:
>> > - Use of typesafe config
>> > - Bumped versions of Jetty, GWT, etc.
>> > - Assorted tweaks to build system
>> >
>> > A summary of useful information can be found in RELEASE-NOTES, and a
>> > list of changes in CHANGES in the source artefacts.
>> >
>> > Action Required:
>> > Please go and test these packages (most importantly the source ones)
>> > for any outstanding legal problems, or any runtime problems in a
>> > 'standard' configuration.
>> >
>> > We are not looking for a perfect first release, as there is plenty of
>> > time to fix outstanding bugs in future releases, but we do want to get
>> > 0.4 out soon (at long last).
>> >
>> > This vote will close around  GMT 17th October 2015.
>> >
>> > [ ] +1 Release it!
>> > [ ] +0 Ok, but...
>> > [ ] -0  Ok, but you really should fix...
>> > [ ] -1 Definitely do not release this because...
>> >
>> > Thanks,
>> > Ali
>> >
>>

[VOTE] Wave 0.4.0-rc10

2015-10-10 Thread Ali Lown

Hi all,

RC10 is now available for review.
Artefacts can be found here:
https://people.apache.org/~al/wave_rc/0.4-rc10/
(Remember checksums are from 'gpg --print-md SHA512 $f > $f.sha')

I have included both source and binary artefacts for convenience.

The release version (if successful) will be 0.4.0-incubating

This is taken from the branch 0.4.0-rc10 of the incubator-wave repository.

Notable changes since earlier initial release attempts include:
- Use of typesafe config
- Bumped versions of Jetty, GWT, etc.
- Assorted tweaks to build system

A summary of useful information can be found in RELEASE-NOTES, and a
list of changes in CHANGES in the source artefacts.

Action Required:
Please go and test these packages (most importantly the source ones)
for any outstanding legal problems, or any runtime problems in a
'standard' configuration.

We are not looking for a perfect first release, as there is plenty of
time to fix outstanding bugs in future releases, but we do want to get
0.4 out soon (at long last).

This vote will close around  GMT 17th October 2015.

[ ] +1 Release it!
[ ] +0 Ok, but...
[ ] -0  Ok, but you really should fix...
[ ] -1 Definitely do not release this because...

Thanks,
Ali

Re: New website design

2015-10-10 Thread Ali Lown

Hi Evan,

I have to admit that I am not a fan of those waves at the bottom of
the page, reminds me of a strange skirting board...

Not sure there is enough mocked-up to get a feel for the changes you
envision for the website?

I think the main problem with the current design is our rather
text-heavy (and very small print) approach, so any thoughts on how to
lessen this (without creating a site entirely made of icons) would be
good.
Could we reduce the number of pages we have usefully? Would something
more 'interactive' be better? Maybe changing the homepage into a
'quick-links' thing would be better (see git's front page?)

Ali


On 8 October 2015 at 17:34, Evan Hughes  wrote:
> Pablo if you check the link again, hopefully its something more to your
> liking, let us know how you feel about it, especially the waves at the
> bottom im 50/50 on them.
>
> On 9 October 2015 at 01:56, Evan Hughes  wrote:
>
>> I've worked with bootstrap before, and yes many of the Apache sites are
>> either default bootstrap or take designs from the popular bootstrap
>> templates. Sometimes though they are over kill, not to say i wont end up
>> using a bootstrap back end but I do like to dabble in refreshing my web
>> technologies now and then. So this is more enjoyment on my part ahah and
>> any opinion is always welcome with my work.
>>
>> On 9 October 2015 at 01:43, Pablo Ojanguren  wrote:
>>
>>> Excuse me for being candid. What do you think to choose one free HTML
>>> template and to change just colors and logo by CSS? Wouldn't be faster?
>>> There are a lot of sites with modern-hipster-cute-cool templates. e.g.
>>> this
>>> 
>>>
>>>
>>>
>>> 2015-10-08 17:09 GMT+02:00 Evan Hughes :
>>>
>>> > In our bid to attract new and old comitters back to wave Ive been
>>> thinking
>>> > about a new design for the website.
>>> >
>>> > Been trying different designs over the day but haven't found one that
>>> > sticks, if anyone has ideas or thoughts feel free to send them my way.
>>> >
>>> > Something I played with today
>>> > https://projects.invisionapp.com/share/UM4HAFWEH#/screens
>>> >
>>> > Evan Hughes
>>> >
>>>
>>
>>

Re: Incubation

2015-10-07 Thread Ali Lown

Upayavira,

I do concede that after watching over Wave here for the last 3 years
the project doesn't appear to have progress hugely far in terms of new
user-visible functionality, but I don't think that this means the end,
as there has been a slow-but-steady set of work on more underlying
things - I would argue that 'we' have a tendency to the first 90% of
the work, but then stop a bit short far too often.

Yuri and I have put together 9 release candidates for general review
under the name 0.4, which have received very varied quantities of
responses from the community at large, though all positive - but
ultimately all these RCs have had some form of bug we have
(previously) considered to be show-stopping, prior to reaching the
stage of sending the RC to the IPMC. I would say that this is due in
part to the large time scales between (later) attempts, and the
patches received in the interim time which caused a breakage, and more
generally due to a lack of usage outside of release testing, resulting
in these being the first time non-apparent bugs manifest themselves.

It would appear that the best way to progress forward from this
blocking point, is to simply cut RC10 from (roughly) where we
currently stand on master. Say "we know it has bugs, but it
sort-of-works if you do X and run only as Y, we will fix everything
else in future releases" - which would prevent us getting stuck again
at RC stage for anything short of "it doesn't work on any system
because the RC is missing the build scripts" - allowing the project to
meet the final criteria that has eluded this project for far too long
now.

Our next board report would be due in January, and assuming we would
agree to make our initial release under the limited statement above, I
think that making a release by then is perfectly achievable.

I would be happy to put together an RC10 tomorrow, as long as there
are still people on the Wave list interested in seeing its release?

Ali

On 7 October 2015 at 22:48, Upayavira  wrote:
> That is a reasonable response, Evan.
>
> So, let's look at what graduation might look like, then we can see about
> what goals might be reasonable:
>
> A podling must have:
> 1. proven its ability to produce legally correct releases
> 2. demonstrated its ability to vote in new committers and PPMC members
> 3. a diverse community
> 4. sufficient PPMC members to be able to command 3 or more votes on all
> important matters,
> notably new committers/PPMC members and on releases.
>
> So, the ONE thing this podling needs to do before our next board report
> is due is make a release.
>
> This involves these steps:
>  * prepare a tarball containing the source
>  * validate that it is (to the best of our knowledge) legally correct
>  * get at least 3 +1 votes from PPMC members
>  * submit it to the Incubator PMC for checking
>
> I personally am hesitant to vote on such things as I have limited
> experience of release vetting. My holding back should not be considered
> as a negative in any way.
>
> The PPMC needs to be able to demonstrate its ability to do this in a
> self managed way, i.e. without prodding from mentors.
>
> Note, I don't mention in that list "getting the Incubator PMC to accept
> the release". That can sometimes be challenging. But having shown that
> this PPMC can (a) produce a release tarball and (b) submit it to the
> Incubator PMC having acquired 3 or more +1 votes from PPMC members would
> make a big difference in terms of moving us closer to meeting graduation
> requirements.
>
> Reasonable?
>
> Upayavira
>
> On Wed, Oct 7, 2015, at 02:01 PM, Evan Hughes wrote:
>> maybe instead of deciding the end instead you and Christian set goals
>> that
>> must be completed by the next checkpoint aka have x amount of submits,
>> have
>> x more active contributors to help gain momentum. If the tasks are not
>> completed sufficiently or dismally fail then sure maybe its for the best.
>>
>> On 7 October 2015 at 22:44, Evan Hughes  wrote:
>>
>> > Well as the video discussion we had earlier this year, the main problem
>> > has been the complexity. We have been taking steps in this direction with;
>> >
>> > * reducing technical debt (removing updating dependencies), can bee seen
>> > from patches last week and there has been work in a gradle or sbt build
>> > system which allows people to understand how the project works together.
>> >
>> > I personally have been looking into giving the website a fresh coat of
>> > paint in the past couple of weeks (infrastructures docs on building locally
>> > are eh if not on a mac ;) but did get it working). We have also had the
>> > addition of the android project for wave.
>> >
>> > Progress might be slow but progress is still being made.
>> >
>> > On 7 October 2015 at 20:54, Upayavira  wrote:
>> >
>> >> Dear all,
>> >>
>> >> I need to sign off the Wave report, but find this difficult.
>> >>
>> >> The Apache Incubator exists to facilitate

Re: Incubator PMC/Board report for Oct 2015 ([ppmc])

2015-10-05 Thread Ali Lown

@Christian/Upayavira:
Please sign the report this month.

Let me know if you think we should add anything else to the report. Martin
thought it was a bit 'thin' last month...

Ali
On 5 Oct 2015 15:09, "Evan Hughes" <ehu...@gmail.com> wrote:

> hmm we still have not gotten a sign off yet.
>
> On 1 October 2015 at 08:28, Ali Lown <a...@lown.me.uk> wrote:
>
> > I have expanded upon the wave report a bit from last month.
> >
> > Looks like the mentors forgot to sign it
> >
> > Ali
> >
> > On 30 September 2015 at 02:58, Marvin Humphrey <mar...@apache.org>
> wrote:
> > > On Mon, Sep 28, 2015 at 02:15:05PM +, Marvin wrote:
> > >
> > >> The board meeting is scheduled for Wed, 14 October 2015, 10:30 am PST.
> > The
> > >> report for your podling will form a part of the Incubator PMC report.
> > The
> > >> Incubator PMC requires your report to be submitted 2 weeks before the
> > board
> > >> meeting, to allow sufficient time for review and submission (Wed, Sep
> > 30th).
> > >
> > > The dates in this autogenerated email (sent by the "Marvin" bot, not
> me)
> > were
> > > off by a week.  Your podling has more time to file.
> > >
> > > Here are the correct dates:
> > >
> > > *   Wed Oct 07 -- Podling reports due
> > > *   Wed Oct 14 -- Incubator report due (along with other TLP reports)
> > > *   Wed Oct 21 -- Monthly meeting of the Apache Board of Directors
> > >
> > > Marvin Humphrey
> > >
> > >
> >
>

Re: Review Request 38849: Create a pst-src.jar during the build

2015-10-01 Thread Ali Lown



> On Oct. 1, 2015, 2:42 p.m., Ali Lown wrote:
> > Ship It!

Committed as fdb393268f94986d7d8e31b5258149895efc15b3.


- Ali


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38849/#review101232
---


On Sept. 29, 2015, 11:56 a.m., Martin Letis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38849/
> ---
> 
> (Updated Sept. 29, 2015, 11:56 a.m.)
> 
> 
> Review request for wave and Ali Lown.
> 
> 
> Repository: wave
> 
> 
> Description
> ---
> 
> Create a pst-src.jar during 'dist-pst'
> 
> 
> Diffs
> -
> 
>   build.xml 893654a 
> 
> Diff: https://reviews.apache.org/r/38849/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Martin Letis
> 
>

Re: Review Request 38785: Remove dep on Impl::getNextHashId()

2015-09-30 Thread Ali Lown



> On Sept. 30, 2015, 10:11 p.m., Ali Lown wrote:
> > LGTM.

Committed as bdb8f24e1cbcb3e5b1c98199c86632cabd2c8d84.


- Ali


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38785/#review101168
---


On Sept. 29, 2015, 12:03 p.m., Martin Letis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38785/
> ---
> 
> (Updated Sept. 29, 2015, 12:03 p.m.)
> 
> 
> Review request for wave, Ali Lown and Yuri Zelikov.
> 
> 
> Repository: wave
> 
> 
> Description
> ---
> 
> As of 
> https://gwt.googlesource.com/gwt/+/6d27b4615004569c68c7bbf2b3d04a6c942cd493 
> the method is no longer available.
> 
> Calling Object#hashCode() should "Just Work (TM)" both for jso and java, as 
> the 'emul' implementation both before and after dankurka's change default to 
> the previous implementation in JsIdentity{Map,Set}.
> 
> 
> Diffs
> -
> 
>   src/org/waveprotocol/wave/client/common/util/JsIdentityMap.java d321b1e 
>   src/org/waveprotocol/wave/client/common/util/JsIdentitySet.java 9f7f6e1 
> 
> Diff: https://reviews.apache.org/r/38785/diff/
> 
> 
> Testing
> ---
> 
> ant compile compile-gwt works with latest GWT jars
> 
> 
> Thanks,
> 
> Martin Letis
> 
>

Re: Incubator PMC/Board report for Oct 2015 ([ppmc])

2015-09-30 Thread Ali Lown

I have expanded upon the wave report a bit from last month.

Looks like the mentors forgot to sign it

Ali

On 30 September 2015 at 02:58, Marvin Humphrey  wrote:
> On Mon, Sep 28, 2015 at 02:15:05PM +, Marvin wrote:
>
>> The board meeting is scheduled for Wed, 14 October 2015, 10:30 am PST. The
>> report for your podling will form a part of the Incubator PMC report. The
>> Incubator PMC requires your report to be submitted 2 weeks before the board
>> meeting, to allow sufficient time for review and submission (Wed, Sep 30th).
>
> The dates in this autogenerated email (sent by the "Marvin" bot, not me) were
> off by a week.  Your podling has more time to file.
>
> Here are the correct dates:
>
> *   Wed Oct 07 -- Podling reports due
> *   Wed Oct 14 -- Incubator report due (along with other TLP reports)
> *   Wed Oct 21 -- Monthly meeting of the Apache Board of Directors
>
> Marvin Humphrey
>
>

Re: Review Request 38831: Update GWT and ASM libraries in third_party

2015-09-30 Thread Ali Lown



> On Sept. 30, 2015, 10:18 p.m., Ali Lown wrote:
> > LGTM.
> > 
> > Thanks Martin.

Committed as fa9886b22dc0c801cad99c85135f5bc63becc4bc.


- Ali


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38831/#review101170
---


On Sept. 29, 2015, 12:02 p.m., Martin Letis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38831/
> ---
> 
> (Updated Sept. 29, 2015, 12:02 p.m.)
> 
> 
> Review request for wave and Ali Lown.
> 
> 
> Repository: wave
> 
> 
> Description
> ---
> 
> Update GWT libraries in third_party from 2.6.1 to 2.7.0.
> Also updates ASM from 3.3 to 5.0.4.
> 
> 
> Diffs
> -
> 
>   .classpath 88967fa 
>   build.xml 893654a 
> 
> Diff: https://reviews.apache.org/r/38831/diff/
> 
> 
> Testing
> ---
> 
> ant compile compile-gwt test dist
> 
> 
> Thanks,
> 
> Martin Letis
> 
>

Re: Review Request 38849: Create a pst-src.jar during the build

2015-09-30 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38849/#review101172
---


Patch LGTM.

What is the use case for this pst-src file? Why should we build it as well?

- Ali Lown


On Sept. 29, 2015, 11:56 a.m., Martin Letis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38849/
> ---
> 
> (Updated Sept. 29, 2015, 11:56 a.m.)
> 
> 
> Review request for wave and Ali Lown.
> 
> 
> Repository: wave
> 
> 
> Description
> ---
> 
> Create a pst-src.jar during 'dist-pst'
> 
> 
> Diffs
> -
> 
>   build.xml 893654a 
> 
> Diff: https://reviews.apache.org/r/38849/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Martin Letis
> 
>

Re: Review Request 38831: Update GWT and ASM libraries in third_party

2015-09-30 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38831/#review101170
---

Ship it!


LGTM.

Thanks Martin.

- Ali Lown


On Sept. 29, 2015, 12:02 p.m., Martin Letis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38831/
> ---
> 
> (Updated Sept. 29, 2015, 12:02 p.m.)
> 
> 
> Review request for wave and Ali Lown.
> 
> 
> Repository: wave
> 
> 
> Description
> ---
> 
> Update GWT libraries in third_party from 2.6.1 to 2.7.0.
> Also updates ASM from 3.3 to 5.0.4.
> 
> 
> Diffs
> -
> 
>   .classpath 88967fa 
>   build.xml 893654a 
> 
> Diff: https://reviews.apache.org/r/38831/diff/
> 
> 
> Testing
> ---
> 
> ant compile compile-gwt test dist
> 
> 
> Thanks,
> 
> Martin Letis
> 
>

Re: Review Request 38785: Remove dep on Impl::getNextHashId()

2015-09-26 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/38785/#review100748
---


Changes LGTM.

What do you mean by 'latest' GWT jars? Do you mean built from master (11a0d2e), 
or built from the 2.7.0 tag?
I think we should commit this change at the same time as updating the GWT jars 
stored in third_party/.

- Ali Lown


On Sept. 26, 2015, 9:17 a.m., Martin Letis wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/38785/
> ---
> 
> (Updated Sept. 26, 2015, 9:17 a.m.)
> 
> 
> Review request for wave and Yuri Zelikov.
> 
> 
> Repository: wave
> 
> 
> Description
> ---
> 
> As of 
> https://gwt.googlesource.com/gwt/+/6d27b4615004569c68c7bbf2b3d04a6c942cd493 
> the method is no longer available.
> 
> Calling Object#hashCode() should "Just Work (TM)" both for jso and java, as 
> the 'emul' implementation both before and after dankurka's change default to 
> the previous implementation in JsIdentity{Map,Set}.
> 
> 
> Diffs
> -
> 
>   src/org/waveprotocol/wave/client/common/util/JsIdentityMap.java d321b1e 
>   src/org/waveprotocol/wave/client/common/util/JsIdentitySet.java 9f7f6e1 
> 
> Diff: https://reviews.apache.org/r/38785/diff/
> 
> 
> Testing
> ---
> 
> ant compile compile-gwt works with latest GWT jars
> 
> 
> Thanks,
> 
> Martin Letis
> 
>

Re: Website repository

2015-08-22 Thread Ali Lown

Hi Evan,

Not entirely sure what this would constitute. Are you proposing
redesigning the website from scratch to not make use of the Apache
CMS?

Currently the reference version lives in the Wave subversion space (as
required for all the CMS scripts to work properly). This is already as
close to a separate repository as possible for the project.
(The staging and 'published' editions live in infra's space at
https://svn.apache.org/repos/infra/websites/)

If we made a github repository for the website, then the flow would
need to involve copying this in to the subversion space, then forcing
a rebuild, then publishing it from there if we wanted to use the CMS.

The alternative for a non-CMS site would look almost identical: as the
only alternate mechanism is via Infra's svnpubsub system, so the repo
gets copied to a designated space in svn, and then published by that
instead. (We just need to pre-build it first).

More information on the options can be found at:
https://www.apache.org/dev/project-site

Which of these options are you suggesting?

Ali

On 11 August 2015 at 11:39, Evan Hughes ehu...@gmail.com wrote:
 Making styling for the docs already, might as well chuck the website's css
 ontop.

 On 11 August 2015 at 20:37, Yuri Z vega...@gmail.com wrote:

 Fine with me, but I think that would require sufficient effort.

 On Tue, Aug 11, 2015 at 12:58 PM, Evan Hughes ehu...@gmail.com wrote:

  Does the mailing list think it would be beneficial for the Apache Wave
  website's design and content to be a separate repository if this is even
  possible?
 
  By making the change the layout of the design can be improved on (made to
  be more modern) and content more up to date taking away the
 responsibility
  from the commiters to only allow pull requests/patches.
 
  Also allows the docs in html form to be added to the website in a
  structured way as well with the pdf copies.
 
  ~ Evan

Re: Wave Android App Landing (GSoC)

2015-08-22 Thread Ali Lown

Hi all,

Thanks for the feedback.

We now have a new repository:
https://git-wip-us.apache.org/repos/asf?p=incubator-wave-android.git

Roshan is just tidying some things up at the moment, so I expect to
copy it into this repository at the end of next week.

Producing an apk seems possible alongside normal source releases for
this. (This reminds me we should really finish with releasing our main
code as well!)
@Yuri: Do you know if it is possible to add android app building to
the Apache jenkins server? If not, producing an apk manually every now
and then seems reasonable.

Ali

On 21 August 2015 at 12:39, Thomas Wrobel darkfl...@gmail.com wrote:
 1) Separate repository - keep it as clean as possible that way.
 2) Own versioning, as it should be able to be updated independently. The
 only question I guess is potential future breaks in compatibility? Might
 want a chart that says use this version sever with this version android
 client somewhere.
 3) Compiled apk, but no need to goto the play store. At this point it isnt
 for mass consumption and I would
 assume anyone interesting in Android development has already enabled 3rd
 party app installs.
 4) Whatevers needed to get them going, but again, I think aim for android
 developer skill level right now. Hopefully helps get more people
 interested in wave development.

 ~~~
 Thomas  Bertines online review show:
 http://randomreviewshow.com/index.html
 Try it! You might even feel ambivalent about it :)

 On 21 August 2015 at 08:53, Pablo Ojanguren pablo...@gmail.com wrote:

 Hi, good work

 1) and 2) Ok

 3) I would prefer to provide an .apk file somewhere.

 4) A miminim hacking guide to explain the basics. The user guide just
 explaining how to configure server connection. To consider configure the
 app with a default Wave that could be used immediatly.

 Regards,

 Pablo


 2015-08-21 1:29 GMT+02:00 Ali Lown a...@lown.me.uk:

  Hi all,
 
  As many of you know, Roshan has been working on developing an Android
  client for Wave, as part of GSoC '15. The code base can currently be
  found on his github account[0].
 
  I will let Roshan provide the full details of its functionality, but
  the core features are all there (signup, signin, search, new waves,
  wave rendering).
 
  Sadly, the end of GSoC is almost upon us and we should probably decide
  how best to fit this amongst the rest of our files, and what state
  Apache Wave should provide the client in.
 
  So, for handy reference when responding, here is my set of discussion
  points:
 
  1) Where should we store the android client code?
a) In a new repository? incubator-wave-android?
b) In our main repository incubator-wave, under a new top-level
  folder android/ ? Should this link in with our main build system then?
 
  My thoughts tend towards option (a), as it has very little in common
  with the main codebase - beyond pulling a 'core' library in as a jar.
 
  2) How to version the android client?
a) Should it follow the main client/server numbering (so we start it at
  0.4)?
b) Should it have its own versioning?
 
  I would again tend to option (b) here, which works particularly nicely
  if it is in its own repository.
 
  3) How should we distribute the client?
a) Should we provide a compiled apk for easy loading?
b) Should we publish on the Play Store?
c) Do we leave the client compilation up to Wave server operators,
  and simply provide the source code?
 
  I am leaning towards option (c) here, as I see the Apache Wave's code
  as mostly a 'reference implementation', but I know that others here
  might like a more turn-key solution. (Such as the binary releases
  alongside the normal source releases)
 
  4) I am imagining two sets of documentation for the client, a user
  guide, and a hacking guide, kept with the rest of the new
  documentation in the incubator-wave-docs repository. Do we need the
  user guide?
 
  Please do respond with your thoughts on any/all of these matters,
  (In the event of no responses, I will simply execute my thoughts as
  set out above ;) )
 
  Ali
 
  [0]: https://github.com/TinTin911/android-wave

Wave Android App Landing (GSoC)

2015-08-20 Thread Ali Lown

Hi all,

As many of you know, Roshan has been working on developing an Android
client for Wave, as part of GSoC '15. The code base can currently be
found on his github account[0].

I will let Roshan provide the full details of its functionality, but
the core features are all there (signup, signin, search, new waves,
wave rendering).

Sadly, the end of GSoC is almost upon us and we should probably decide
how best to fit this amongst the rest of our files, and what state
Apache Wave should provide the client in.

So, for handy reference when responding, here is my set of discussion points:

1) Where should we store the android client code?
  a) In a new repository? incubator-wave-android?
  b) In our main repository incubator-wave, under a new top-level
folder android/ ? Should this link in with our main build system then?

My thoughts tend towards option (a), as it has very little in common
with the main codebase - beyond pulling a 'core' library in as a jar.

2) How to version the android client?
  a) Should it follow the main client/server numbering (so we start it at 0.4)?
  b) Should it have its own versioning?

I would again tend to option (b) here, which works particularly nicely
if it is in its own repository.

3) How should we distribute the client?
  a) Should we provide a compiled apk for easy loading?
  b) Should we publish on the Play Store?
  c) Do we leave the client compilation up to Wave server operators,
and simply provide the source code?

I am leaning towards option (c) here, as I see the Apache Wave's code
as mostly a 'reference implementation', but I know that others here
might like a more turn-key solution. (Such as the binary releases
alongside the normal source releases)

4) I am imagining two sets of documentation for the client, a user
guide, and a hacking guide, kept with the rest of the new
documentation in the incubator-wave-docs repository. Do we need the
user guide?

Please do respond with your thoughts on any/all of these matters,
(In the event of no responses, I will simply execute my thoughts as
set out above ;) )

Ali

[0]: https://github.com/TinTin911/android-wave

Server Problems with Typesafe Config in Head (fc70bb9)

2015-07-09 Thread Ali Lown

Hi Yuri,

Evan was having a problem running the server using the run-server.sh
script, with the error below:
(Note that it works fine using ant run-server, due to that being
completely separate from the script)

Exception in thread main java.lang.NoClassDefFoundError:
com/typesafe/config/ConfigMergeable
at org.waveprotocol.box.server.ServerMain.main(ServerMain.java:113)
Caused by: java.lang.ClassNotFoundException: com.typesafe.config.ConfigMergeable
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 1 more

It seems that we forgot to add the new jar's namespace to the list of
ones to include in the final jar during the 'dist-server' build step.

The one-line patch below fixes this:

diff --git a/build.xml b/build.xml
index 1e721d4..d111325 100644
--- a/build.xml
+++ b/build.xml
@@ -686,6 +686,7 @@
 include name=com/mongodb/**/* /
 include name=org/slf4j/**/* /
  include name=org/atmosphere/**/* /
+include name=com/typesafe/**/* /
 include name=com/google/common/**/* /
 include name=com/google/gson/**/* /
 include name=com/google/gxp/**/* /

Are you happy for me to just commit this?
(Should probably also fix the whitespace issue on the line above about
atmosphere).

[Aside: Why do we even have both the run-server.sh script and the
ability to run the server from the ant tool? Should we pick one and
stick to it? (My vote goes to the script, so that when distributed as
a binary the production server doesn't need to have ant on it).]

Ali

Re: Android Wave Interface

2015-06-29 Thread Ali Lown

Hi Roshan,

I have to admit that I am not entirely sure what I should be looking at here...
The current logic in the xActivity's seems fine to me, though it
doesn't do anything more than the mockups currently.

I think it worth correcting at this stage, but you have used sing
instead of sign as in sign up, sign in throughout the codebase.
:)

Could you provide a few instructions on how to build/run in the
emulator this codebase for those not familiar to Android development
on this list?

What is the next step? Performing login against a Wave server by
sending the relevant HTTP request?

Thanks,
Ali

On 25 June 2015 at 18:59, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
 Hi All
 I have made the loading, sing in, register interfaces in the android wave
 app.
 Can you all please look into these interfaces and give me your feedback.

 [1] https://github.com/TinTin911/android-wave.git
 Regards
 Roshan

Re: Documentation

2015-06-29 Thread Ali Lown

Hi Evan,

I have merged these into the (newly created) 0.4 branch in the docs repository.
Not sure how to close the pull requests though, as I didn't meet the
required criteria (different branch).

Should I clone these over to the master branch though? Is the master
branch even useful or should we always end up working on a
major-release-numbered branch?

The developer-docs and protocol-docs are now looking great! It would
be nice to get these on the website soon.

Ali

On 27 June 2015 at 11:32, Evan Hughes ehu...@gmail.com wrote:
 two pull requests on the documentation git repository, mostly just
 transferring from the confluence to the repository.

Re: Wave App mockups

2015-06-19 Thread Ali Lown

Hi Roshan,

These look great!

I am interested in seeing how blip editing translates to this UI. How
should we handle multiple user cursors on screen at the same time? How
do we render gadgets/attachments?

With regards to the sign up/login page, how does this work for
different wave servers? Does it auto-connect based upon the username?
Should we have some sort of drop-down to select which wave server we
which to connect to?

What sort of things would we have under the menu on the wave inbox screen?

Ali


On 19 June 2015 at 21:17, Zachary Yaro zmy...@gmail.com wrote:
 I like the overall idea, though there are a few ways you could better adhere
 to the Material Design guidelines that I think might improve the app's look
 and feel.  Namely:

 Make the user avatars (and avatar placeholders) circles instead of squares,
 or at least give them a little bit of padding so their visual weight is not
 so disproportionately high.  Also, Android in general has moved in the
 direction of circular cropping for profile pictures.
 Have the app bar and floating action button “float above” (have a higher
 z-value) than the other content so the FAB catches the user's eye.
 Use a more simple wave icon on the reply bar so it is less visually busy, or
 maybe swap it for a reply icon since that is really the function the user is
 going to perform there.

 You may also wish to make your back button and “Sign up” button more
 consistent 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 roshan.2013...@iit.ac.lk wrote:

 Hi All
 Here I have created the App mockups.
 Can you all please look into this App mockups and give me your feedback's.

  1. Loading screen
 [1]

 https://drive.google.com/file/d/0B_tP-jjki90QMzhpTVVFNTRVeWM/view?usp=sharing

 2. Sing In screen
 [2]

 https://drive.google.com/file/d/0B_tP-jjki90QaTVCaVVUaHUyWHM/view?usp=sharing

 3. Sing up screen
 [3]

 https://drive.google.com/file/d/0B_tP-jjki90QcV9Wb1FncmJoeE0/view?usp=sharing

 4. Wave Inbox screen
 [4]

 https://drive.google.com/file/d/0B_tP-jjki90QblBQSDFieGdvbW8/view?usp=sharing

 5. Chat page
 [5]

 https://drive.google.com/file/d/0B_tP-jjki90QMlNHTEd5Vmk2cXc/view?usp=sharing

 6. Create Wave page
 [6]

 https://drive.google.com/file/d/0B_tP-jjki90QdTZiVFpCRDdEYjA/view?usp=sharing

 Regards
 Roshan

Re: Proposal - Documentation storage

2015-05-16 Thread Ali Lown

Okay. I merged and pushed those changes.

Should I be squashing the commits into a single one before pushing?
Does anyone have any preferences on this/other parts of git -
branching and tagging documentation?

I was assuming we have something along the lines of a branch of docs
for each major release version, and we could potentially tag
documentation to match final releases including minor versions?

Ali

On 16 May 2015 at 11:49, Yuri Z vega...@gmail.com wrote:
 I think it is.

 On Sat, May 16, 2015 at 2:03 AM Ali Lown a...@lown.me.uk wrote:

 @Evan: Okay great.

 I have merged this PR into the incubator-wave-docs repo.

 For reference: as the github repo is a mirror, with the master being
 on git-wip-us.apache.org, I merged the PR by adding a new remote to my
 local repository which was Evan's repository, then merging the
 relevant commits locally and pushing it back upstream. Github can
 auto-detect this occurred and closed the PR for me.

 Does this seem a reasonable workflow?

 Ali

 On 15 May 2015 at 09:06, Evan Hughes ehu...@gmail.com wrote:
  @Ali, submitted today
 
  On 15 May 2015 at 05:12, Ali Lown a...@lown.me.uk wrote:
 
  @Evan: That PR looks fine to me.
  One thing: Have you submitted an ICLA to Apache? It seems like it
  would be a good idea to do at some point, as you are likely to
  continue making not-insignificant changes to this repo.
 
  @Yuri/Others: How do we want to handle PR reviews?
  I propose doing it the same way as on review-board, of leaving
  comments on the system as appropriate.
  Do we want to wait for multiple committers to say LGTM?
 
  I propose that at the moment, whilst the documentation repo is being
  built up, that we just commit the PRs after looking over them for
  sanity, and then lock it down a bit once stabilized to the current
  code base?
 
  To avoid stalling this progress any longer, I will commit Evans PR
  within the next 24hrs unless someone says otherwise.
 
  Ali
 
  On 9 May 2015 at 13:55, Evan Hughes ehu...@gmail.com wrote:
   For Pull request
  
   On 9 May 2015 at 17:12, Evan Hughes ehu...@gmail.com wrote:
  
   I believe we should split the docs into:
  
   Documentation  =  Documents how to build the documentation and how
 to
  use
   sphinx + ReST  (mostly just an example and to help ease the
 transition)
   manual  =  The user manual provided with the client
 (How to
   make a wave, .)
   developer  =  Everything a developer would need, how to
 start
  the
   server, how to build, how to contribute
   api =  How to build with the gadgets/robot api
   protocol =  All about the protocol specifications
  
   after the Documentation is built I will submit a pull request to
 the
   main so you guys can see if you like it.
  
   On 6 May 2015 at 00:41, Ali Lown a...@lown.me.uk wrote:
  
   The repository is at https://github.com/apache/incubator-wave-docs,
   and is rather empty at the moment.
   I see no reason we shouldn't accept pull requests to this repo, so I
   suggest you use that workflow...
  
   Sphinx sounds fine. Many people will be familiar with rest (it
 shares
   a lot with markdown but is more powerful) thanks to Python docs
 making
   use of it.
  
   Can we find any other volunteers for moving the docs out of
   confluence, as there is quite a lot to do?
  
   Ali
  
   On 1 May 2015 at 04:03, Evan Hughes ehu...@gmail.com wrote:
I think sphinx would be a better option than jekyll for the
documentation,
it does use restructured text instead of markdown but is more
extensible
and can easily produce a pdf format compared to markdown. Gonna
 spin
  up
my
own repo and see how it is, been looking at the syntax and it
 isn't
that
bad.
   
On 1 May 2015 at 01:53, Ali Lown a...@lown.me.uk wrote:
   
Okay. A new repository has been made:
   
 https://git-wip-us.apache.org/repos/asf?p=incubator-wave-docs.git
   
I have requested github integration for it, so we can use pull
requests if we would like to...
   
Ali
   
On 29 April 2015 at 00:53, Evan Hughes ehu...@gmail.com wrote:
 I like the idea of also moving the website off of the cms but
 not
 sure if
 it should be in same repository. Ill look into jekyll for the
documentation
 but theres also other build systems which might be better for
 us
  aka
 html
 and pdf export.

 Go ahead with the repository for the documentation and well go
  from
there.
 Well need to transfer any issues in jira or deal with them
 during
 the
 transition
  On 29/04/2015 1:20 AM, Pablo Ojanguren pablo...@gmail.com
 wrote:

 +1 Moving doc to git would be good, moreover if we update and
 improve
it a
 litlle bit along the migration process (at least the
  organization).

 2015-04-28 16:40 GMT+02:00 Ali Lown a...@lown.me.uk:

  Yuri,
 
  I think the main reason to move is to make it easier

Re: Proposal - Documentation storage

2015-05-15 Thread Ali Lown

@Evan: Okay great.

I have merged this PR into the incubator-wave-docs repo.

For reference: as the github repo is a mirror, with the master being
on git-wip-us.apache.org, I merged the PR by adding a new remote to my
local repository which was Evan's repository, then merging the
relevant commits locally and pushing it back upstream. Github can
auto-detect this occurred and closed the PR for me.

Does this seem a reasonable workflow?

Ali

On 15 May 2015 at 09:06, Evan Hughes ehu...@gmail.com wrote:
 @Ali, submitted today

 On 15 May 2015 at 05:12, Ali Lown a...@lown.me.uk wrote:

 @Evan: That PR looks fine to me.
 One thing: Have you submitted an ICLA to Apache? It seems like it
 would be a good idea to do at some point, as you are likely to
 continue making not-insignificant changes to this repo.

 @Yuri/Others: How do we want to handle PR reviews?
 I propose doing it the same way as on review-board, of leaving
 comments on the system as appropriate.
 Do we want to wait for multiple committers to say LGTM?

 I propose that at the moment, whilst the documentation repo is being
 built up, that we just commit the PRs after looking over them for
 sanity, and then lock it down a bit once stabilized to the current
 code base?

 To avoid stalling this progress any longer, I will commit Evans PR
 within the next 24hrs unless someone says otherwise.

 Ali

 On 9 May 2015 at 13:55, Evan Hughes ehu...@gmail.com wrote:
  For Pull request
 
  On 9 May 2015 at 17:12, Evan Hughes ehu...@gmail.com wrote:
 
  I believe we should split the docs into:
 
  Documentation  =  Documents how to build the documentation and how to
 use
  sphinx + ReST  (mostly just an example and to help ease the transition)
  manual  =  The user manual provided with the client (How to
  make a wave, .)
  developer  =  Everything a developer would need, how to start
 the
  server, how to build, how to contribute
  api =  How to build with the gadgets/robot api
  protocol =  All about the protocol specifications
 
  after the Documentation is built I will submit a pull request to the
  main so you guys can see if you like it.
 
  On 6 May 2015 at 00:41, Ali Lown a...@lown.me.uk wrote:
 
  The repository is at https://github.com/apache/incubator-wave-docs,
  and is rather empty at the moment.
  I see no reason we shouldn't accept pull requests to this repo, so I
  suggest you use that workflow...
 
  Sphinx sounds fine. Many people will be familiar with rest (it shares
  a lot with markdown but is more powerful) thanks to Python docs making
  use of it.
 
  Can we find any other volunteers for moving the docs out of
  confluence, as there is quite a lot to do?
 
  Ali
 
  On 1 May 2015 at 04:03, Evan Hughes ehu...@gmail.com wrote:
   I think sphinx would be a better option than jekyll for the
   documentation,
   it does use restructured text instead of markdown but is more
   extensible
   and can easily produce a pdf format compared to markdown. Gonna spin
 up
   my
   own repo and see how it is, been looking at the syntax and it isn't
   that
   bad.
  
   On 1 May 2015 at 01:53, Ali Lown a...@lown.me.uk wrote:
  
   Okay. A new repository has been made:
   https://git-wip-us.apache.org/repos/asf?p=incubator-wave-docs.git
  
   I have requested github integration for it, so we can use pull
   requests if we would like to...
  
   Ali
  
   On 29 April 2015 at 00:53, Evan Hughes ehu...@gmail.com wrote:
I like the idea of also moving the website off of the cms but not
sure if
it should be in same repository. Ill look into jekyll for the
   documentation
but theres also other build systems which might be better for us
 aka
html
and pdf export.
   
Go ahead with the repository for the documentation and well go
 from
   there.
Well need to transfer any issues in jira or deal with them during
the
transition
 On 29/04/2015 1:20 AM, Pablo Ojanguren pablo...@gmail.com
wrote:
   
+1 Moving doc to git would be good, moreover if we update and
improve
   it a
litlle bit along the migration process (at least the
 organization).
   
2015-04-28 16:40 GMT+02:00 Ali Lown a...@lown.me.uk:
   
 Yuri,

 I think the main reason to move is to make it easier for people
 to
 make changes, over the existing confluence system. So I would
 have
 though that improving the documentation is something people
 would
 be
 more likely to do afterwards.

 I agree that opening some tickets where the documentation could
 be
 improved does help highlight the problem, but it doesn't make
 it
 any
 easier for people to fix.

 Ali

 P.s. Do you want me to do anything for RC9, or are you happy to
 submit
 one? Are you waiting on me for anything still?

 On 28 April 2015 at 15:36, Yuri Z vega...@gmail.com wrote:
  Maybe it would be better to move in small steps. Like

Re: Proposal - Documentation storage

2015-05-14 Thread Ali Lown

@Evan: That PR looks fine to me.
One thing: Have you submitted an ICLA to Apache? It seems like it
would be a good idea to do at some point, as you are likely to
continue making not-insignificant changes to this repo.

@Yuri/Others: How do we want to handle PR reviews?
I propose doing it the same way as on review-board, of leaving
comments on the system as appropriate.
Do we want to wait for multiple committers to say LGTM?

I propose that at the moment, whilst the documentation repo is being
built up, that we just commit the PRs after looking over them for
sanity, and then lock it down a bit once stabilized to the current
code base?

To avoid stalling this progress any longer, I will commit Evans PR
within the next 24hrs unless someone says otherwise.

Ali

On 9 May 2015 at 13:55, Evan Hughes ehu...@gmail.com wrote:
 For Pull request

 On 9 May 2015 at 17:12, Evan Hughes ehu...@gmail.com wrote:

 I believe we should split the docs into:

 Documentation  =  Documents how to build the documentation and how to use
 sphinx + ReST  (mostly just an example and to help ease the transition)
 manual  =  The user manual provided with the client (How to
 make a wave, .)
 developer  =  Everything a developer would need, how to start the
 server, how to build, how to contribute
 api =  How to build with the gadgets/robot api
 protocol =  All about the protocol specifications

 after the Documentation is built I will submit a pull request to the
 main so you guys can see if you like it.

 On 6 May 2015 at 00:41, Ali Lown a...@lown.me.uk wrote:

 The repository is at https://github.com/apache/incubator-wave-docs,
 and is rather empty at the moment.
 I see no reason we shouldn't accept pull requests to this repo, so I
 suggest you use that workflow...

 Sphinx sounds fine. Many people will be familiar with rest (it shares
 a lot with markdown but is more powerful) thanks to Python docs making
 use of it.

 Can we find any other volunteers for moving the docs out of
 confluence, as there is quite a lot to do?

 Ali

 On 1 May 2015 at 04:03, Evan Hughes ehu...@gmail.com wrote:
  I think sphinx would be a better option than jekyll for the
  documentation,
  it does use restructured text instead of markdown but is more
  extensible
  and can easily produce a pdf format compared to markdown. Gonna spin up
  my
  own repo and see how it is, been looking at the syntax and it isn't
  that
  bad.
 
  On 1 May 2015 at 01:53, Ali Lown a...@lown.me.uk wrote:
 
  Okay. A new repository has been made:
  https://git-wip-us.apache.org/repos/asf?p=incubator-wave-docs.git
 
  I have requested github integration for it, so we can use pull
  requests if we would like to...
 
  Ali
 
  On 29 April 2015 at 00:53, Evan Hughes ehu...@gmail.com wrote:
   I like the idea of also moving the website off of the cms but not
   sure if
   it should be in same repository. Ill look into jekyll for the
  documentation
   but theres also other build systems which might be better for us aka
   html
   and pdf export.
  
   Go ahead with the repository for the documentation and well go from
  there.
   Well need to transfer any issues in jira or deal with them during
   the
   transition
On 29/04/2015 1:20 AM, Pablo Ojanguren pablo...@gmail.com
   wrote:
  
   +1 Moving doc to git would be good, moreover if we update and
   improve
  it a
   litlle bit along the migration process (at least the organization).
  
   2015-04-28 16:40 GMT+02:00 Ali Lown a...@lown.me.uk:
  
Yuri,
   
I think the main reason to move is to make it easier for people
to
make changes, over the existing confluence system. So I would
have
though that improving the documentation is something people would
be
more likely to do afterwards.
   
I agree that opening some tickets where the documentation could
be
improved does help highlight the problem, but it doesn't make it
any
easier for people to fix.
   
Ali
   
P.s. Do you want me to do anything for RC9, or are you happy to
submit
one? Are you waiting on me for anything still?
   
On 28 April 2015 at 15:36, Yuri Z vega...@gmail.com wrote:
 Maybe it would be better to move in small steps. Like to go
 over
   current
 documentation and open tickets with requests for improvements
  wherever
 something is missing or not clear.

 On Tue, Apr 28, 2015 at 5:33 PM Ali Lown a...@lown.me.uk
 wrote:

 Well, doesn't look like anybody else has much opinion.

 Shall I just raise a ticket for a new repo for this?

 It probably makes sense to put the whole website under it,
 rather
  than
 using the combination of Apache CMS website + Confluence that
 we do
 currently. We could just use Jekyll for both website and docs?

 Ali


 On 25 April 2015 at 02:52, Evan Hughes ehu...@gmail.com
 wrote:
  indeed and yea without a doubt

Re: [VOTE] Wave Release Candidate 9

2015-05-07 Thread Ali Lown

If you fetch the jars do you have the same error trying to start the server?

Ali
On 7 May 2015 07:46, Yuri Z vega...@gmail.com wrote:

I didn't fetched the jars - just copied them from existing folder.

On Thu, May 7, 2015 at 9:44 AM Yuri Z vega...@gmail.com wrote:

I see, what was the issue with federation?

On Thu, May 7, 2015 at 3:00 AM Ali Lown a...@lown.me.uk wrote:

-1 due to the inability to start the server with federation enabled.
(I will change this to +1 if this is me failing to build correctly).

Checked:
- SHA512 hashes and GPG signs
- Built using JDK7 and ran tests
- Checked README, CHANGES, KEYS, RELEASE-NOTES, build.properties
- Started server without federation using file backends. Tested wave
creation, simple editing, etc.
- Artifact naming seems good.
- Was unable to start server with federation (missing
org/xmpp/component/Log). Seems like a problem with the whack.jar file
that is fetched during build. This is making me wonder how it worked
in the RC8 binary package? @Yuri: Do you get the same error here, or
do you get something different when you build from the artifact in a
clean folder?

Ali

On 5 May 2015 at 18:23, Yuri Z vega...@gmail.com wrote:
Great, thanks Ali. I checked that the source compiles and runs.
On Tue 5 May 2015 at 17:39 Ali Lown a...@lown.me.uk wrote:

I think we may wish to extend the vote duration, as no-one seems to
have responded.

I have just gotten around to this email in my inbox, so hope to get
to
this this evening...

Ali

On 29 April 2015 at 20:44, Yuri Z vega...@gmail.com wrote:
RC9 is now available for review.
Artifacts can be found here:
https://dist.apache.org/repos/dist/dev/incubator/wave/0.4.0-rc9
(Remember checksums are from 'gpg --print-md SHA512 $f $f.sha')
This time I included only source artifacts.

The release version will be: 0.4.0-incubating

This is taken from branch

https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC9

Reminder on what included previous release candidates:
RC7 and RC8 included:
- Release related fixes.

RC6 included:
- Bug Fixes

RC5 included:
- Added MongoDB based deltas store and migration tool for deltas
migration
from file to mongo based store.

- Added client/server profiling.
- Added Atmosphere framework as replacement of Socket.IO.
- Added alternative - Gmail style initials avatars.
- Decreased number of permutations in dev compilation and added GWT
superdev mode.
- Upgraded the server to Jetty 9.1.1.
- Added JDK 7 compatibility.

RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

A summary of useful information can be found in RELEASE-NOTES, and
a
list
of changes in CHANGES at the above artifact distribution url, as
well as
being included in the tarballs/zips.(zipballs?)

Action Required:
Test the release and make it works on your environment - at least
standard
configurations. Please go over the source files and make sure they
don't
contain anything that cannot be released under Apache Wave due to
legal
issues.

This vote will close around GMT 5-th May 2015.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks

Re: [VOTE] Wave Release Candidate 9

2015-05-06 Thread Ali Lown

-1 due to the inability to start the server with federation enabled.
(I will change this to +1 if this is me failing to build correctly).

Ali

On 5 May 2015 at 18:23, Yuri Z vega...@gmail.com wrote:
Great, thanks Ali. I checked that the source compiles and runs.
On Tue 5 May 2015 at 17:39 Ali Lown a...@lown.me.uk wrote:

I think we may wish to extend the vote duration, as no-one seems to
have responded.

I have just gotten around to this email in my inbox, so hope to get to
this this evening...

Ali

The release version will be: 0.4.0-incubating

This is taken from branch

https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC9

Reminder on what included previous release candidates:
RC7 and RC8 included:
- Release related fixes.

RC6 included:
- Bug Fixes

RC5 included:
- Added MongoDB based deltas store and migration tool for deltas
migration
from file to mongo based store.

RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

A summary of useful information can be found in RELEASE-NOTES, and a list
of changes in CHANGES at the above artifact distribution url, as well as
being included in the tarballs/zips.(zipballs?)

Action Required:
Test the release and make it works on your environment - at least
standard
configurations. Please go over the source files and make sure they don't
contain anything that cannot be released under Apache Wave due to legal
issues.

This vote will close around GMT 5-th May 2015.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks

Re: [VOTE] Wave Release Candidate 9

2015-05-05 Thread Ali Lown

I think we may wish to extend the vote duration, as no-one seems to
have responded.

I have just gotten around to this email in my inbox, so hope to get to
this this evening...

Ali

The release version will be: 0.4.0-incubating

This is taken from branch
https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC9

Reminder on what included previous release candidates:
RC7 and RC8 included:
- Release related fixes.

RC6 included:
- Bug Fixes

RC5 included:
- Added MongoDB based deltas store and migration tool for deltas migration
from file to mongo based store.

RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

A summary of useful information can be found in RELEASE-NOTES, and a list
of changes in CHANGES at the above artifact distribution url, as well as
being included in the tarballs/zips.(zipballs?)

Action Required:
Test the release and make it works on your environment - at least standard
configurations. Please go over the source files and make sure they don't
contain anything that cannot be released under Apache Wave due to legal
issues.

This vote will close around GMT 5-th May 2015.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks

Re: Proposal - Documentation storage

2015-05-05 Thread Ali Lown

The repository is at https://github.com/apache/incubator-wave-docs,
and is rather empty at the moment.
I see no reason we shouldn't accept pull requests to this repo, so I
suggest you use that workflow...

Sphinx sounds fine. Many people will be familiar with rest (it shares
a lot with markdown but is more powerful) thanks to Python docs making
use of it.

Can we find any other volunteers for moving the docs out of
confluence, as there is quite a lot to do?

Ali

On 1 May 2015 at 04:03, Evan Hughes ehu...@gmail.com wrote:
 I think sphinx would be a better option than jekyll for the documentation,
 it does use restructured text instead of markdown but is more extensible
 and can easily produce a pdf format compared to markdown. Gonna spin up my
 own repo and see how it is, been looking at the syntax and it isn't that
 bad.

 On 1 May 2015 at 01:53, Ali Lown a...@lown.me.uk wrote:

 Okay. A new repository has been made:
 https://git-wip-us.apache.org/repos/asf?p=incubator-wave-docs.git

 I have requested github integration for it, so we can use pull
 requests if we would like to...

 Ali

 On 29 April 2015 at 00:53, Evan Hughes ehu...@gmail.com wrote:
  I like the idea of also moving the website off of the cms but not sure if
  it should be in same repository. Ill look into jekyll for the
 documentation
  but theres also other build systems which might be better for us aka html
  and pdf export.
 
  Go ahead with the repository for the documentation and well go from
 there.
  Well need to transfer any issues in jira or deal with them during the
  transition
   On 29/04/2015 1:20 AM, Pablo Ojanguren pablo...@gmail.com wrote:
 
  +1 Moving doc to git would be good, moreover if we update and improve
 it a
  litlle bit along the migration process (at least the organization).
 
  2015-04-28 16:40 GMT+02:00 Ali Lown a...@lown.me.uk:
 
   Yuri,
  
   I think the main reason to move is to make it easier for people to
   make changes, over the existing confluence system. So I would have
   though that improving the documentation is something people would be
   more likely to do afterwards.
  
   I agree that opening some tickets where the documentation could be
   improved does help highlight the problem, but it doesn't make it any
   easier for people to fix.
  
   Ali
  
   P.s. Do you want me to do anything for RC9, or are you happy to submit
   one? Are you waiting on me for anything still?
  
   On 28 April 2015 at 15:36, Yuri Z vega...@gmail.com wrote:
Maybe it would be better to move in small steps. Like to go over
  current
documentation and open tickets with requests for improvements
 wherever
something is missing or not clear.
   
On Tue, Apr 28, 2015 at 5:33 PM Ali Lown a...@lown.me.uk wrote:
   
Well, doesn't look like anybody else has much opinion.
   
Shall I just raise a ticket for a new repo for this?
   
It probably makes sense to put the whole website under it, rather
 than
using the combination of Apache CMS website + Confluence that we do
currently. We could just use Jekyll for both website and docs?
   
Ali
   
   
On 25 April 2015 at 02:52, Evan Hughes ehu...@gmail.com wrote:
 indeed and yea without a doubt

 On 25 April 2015 at 09:59, Ali Lown a...@lown.me.uk wrote:

 Hi Evan,

 +1

 After giving this some more thought post the Hangout, I do think
  that
 moving the docs to Git provides us with a measurable improvement
  over
 the current situation - particularly with the ability to keep
 docs
 synced with the releases via branches, and the reduced barrier
 to
 entry for changing them.

 Would you be interested in leading the migration effort?

 Ali

 On 24 April 2015 at 05:59, Evan Hughes ehu...@gmail.com
 wrote:
  woops, my bad
 
 
  This is a proposal for the storage of documentation to be
 moved
  to
   a
git
  repository instead of on confluence and leave confluence as a
  place
for
  other technical documents used by developers.
 
  *Confluence:*
  *The issues:*
  - contributors must ask for permission from the
 mailing
   list
to
 be
  given the privilege settings to edit/create pages
  - Simple revision history is kept but is more
 difficult
  to
easy
  transition documentation between wave release versions, more
 of a
running
  active document
  *The good:*
  *- *easily able to export to pdf and web formats
  - has an easy online rich editor
 
  *Git (markdown):*
  *The issues:*
  *- *setup as a new repository? a folder in current
   repository?
  apache will need to be involved if a new repository is to be
  setup
  - exporting the markdown files into a meaningful
representation
  (web, pdf), many build systems exist but custom system can
 also
  be
 written
  by our

Re: Proposal - Documentation storage

2015-04-30 Thread Ali Lown

Okay. A new repository has been made:
https://git-wip-us.apache.org/repos/asf?p=incubator-wave-docs.git

I have requested github integration for it, so we can use pull
requests if we would like to...

Ali

On 29 April 2015 at 00:53, Evan Hughes ehu...@gmail.com wrote:
 I like the idea of also moving the website off of the cms but not sure if
 it should be in same repository. Ill look into jekyll for the documentation
 but theres also other build systems which might be better for us aka html
 and pdf export.

 Go ahead with the repository for the documentation and well go from there.
 Well need to transfer any issues in jira or deal with them during the
 transition
  On 29/04/2015 1:20 AM, Pablo Ojanguren pablo...@gmail.com wrote:

 +1 Moving doc to git would be good, moreover if we update and improve it a
 litlle bit along the migration process (at least the organization).

 2015-04-28 16:40 GMT+02:00 Ali Lown a...@lown.me.uk:

  Yuri,
 
  I think the main reason to move is to make it easier for people to
  make changes, over the existing confluence system. So I would have
  though that improving the documentation is something people would be
  more likely to do afterwards.
 
  I agree that opening some tickets where the documentation could be
  improved does help highlight the problem, but it doesn't make it any
  easier for people to fix.
 
  Ali
 
  P.s. Do you want me to do anything for RC9, or are you happy to submit
  one? Are you waiting on me for anything still?
 
  On 28 April 2015 at 15:36, Yuri Z vega...@gmail.com wrote:
   Maybe it would be better to move in small steps. Like to go over
 current
   documentation and open tickets with requests for improvements wherever
   something is missing or not clear.
  
   On Tue, Apr 28, 2015 at 5:33 PM Ali Lown a...@lown.me.uk wrote:
  
   Well, doesn't look like anybody else has much opinion.
  
   Shall I just raise a ticket for a new repo for this?
  
   It probably makes sense to put the whole website under it, rather than
   using the combination of Apache CMS website + Confluence that we do
   currently. We could just use Jekyll for both website and docs?
  
   Ali
  
  
   On 25 April 2015 at 02:52, Evan Hughes ehu...@gmail.com wrote:
indeed and yea without a doubt
   
On 25 April 2015 at 09:59, Ali Lown a...@lown.me.uk wrote:
   
Hi Evan,
   
+1
   
After giving this some more thought post the Hangout, I do think
 that
moving the docs to Git provides us with a measurable improvement
 over
the current situation - particularly with the ability to keep docs
synced with the releases via branches, and the reduced barrier to
entry for changing them.
   
Would you be interested in leading the migration effort?
   
Ali
   
On 24 April 2015 at 05:59, Evan Hughes ehu...@gmail.com wrote:
 woops, my bad


 This is a proposal for the storage of documentation to be moved
 to
  a
   git
 repository instead of on confluence and leave confluence as a
 place
   for
 other technical documents used by developers.

 *Confluence:*
 *The issues:*
 - contributors must ask for permission from the mailing
  list
   to
be
 given the privilege settings to edit/create pages
 - Simple revision history is kept but is more difficult
 to
   easy
 transition documentation between wave release versions, more of a
   running
 active document
 *The good:*
 *- *easily able to export to pdf and web formats
 - has an easy online rich editor

 *Git (markdown):*
 *The issues:*
 *- *setup as a new repository? a folder in current
  repository?
 apache will need to be involved if a new repository is to be
 setup
 - exporting the markdown files into a meaningful
   representation
 (web, pdf), many build systems exist but custom system can also
 be
written
 by our committers
 *The good:*
 *- *less of a roadblock, allows users to contribute more,
  also
 allows new committers a trial at how to add commits using the
  apache
 procedures
 - Highly customisable
 - Revision history and versions easily achieved for
 example
   with
 branches (master, 0.4.x, 0.5.x, )

 *TL;DR*

 Confluence is a rich wiki but can limit the availability for
   committers
to
 publish updates (need to ask permission, which isn't that hard)
 and
   is a
 good place to store technical information for the project.
 A markdown written file structured documentation implementation
 is
   more
 accessible to developers, follows a more natural flow and can be
   highly
 customised and has great revision structure.

 *Relevant Jira Issues:*
 *- none*

 *Please express your opinions below and if enough feedback is
  present
   a
 vote from the mailing list should be called after

Re: Review Request 33237: Updates/fixes for release

2015-04-29 Thread Ali Lown

Sounds good.

Ali

On 29 April 2015 at 11:27, Yuri Zelikov vega...@gmail.com wrote:


 On April 20, 2015, 8:04 p.m., Ali Lown wrote:
  CHANGES, lines 65-69
  https://reviews.apache.org/r/33237/diff/1/?file=931060#file931060line65
 
  I take this to mean you want to put the release 0.4.0 after the custom 
  config changes.
 
  Do we want this? Is it going to annoy anybody?
  Perhaps this isn't really a problem, as it is our first release, but 
  shouldn't happen during RC'd phase of any subsuquent ones...

 Ok, I ll proceed with 0.4.0 version for release.


 - Yuri


 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/33237/#review80806
 ---


 On April 15, 2015, 8:09 p.m., Yuri Zelikov wrote:

 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/33237/
 ---

 (Updated April 15, 2015, 8:09 p.m.)


 Review request for wave and Ali Lown.


 Repository: wave


 Description
 ---

 The patch contains various updates/fixes related to release.


 Diffs
 -

   CHANGES cf47949
   README.md b227c16
   RELEASE-NOTES 916b0ce
   build.properties 86aad10
   build.xml 1e721d4

 Diff: https://reviews.apache.org/r/33237/diff/


 Testing
 ---


 Thanks,

 Yuri Zelikov

Re: Proposal - Documentation storage

2015-04-28 Thread Ali Lown

Well, doesn't look like anybody else has much opinion.

Shall I just raise a ticket for a new repo for this?

It probably makes sense to put the whole website under it, rather than
using the combination of Apache CMS website + Confluence that we do
currently. We could just use Jekyll for both website and docs?

Ali


On 25 April 2015 at 02:52, Evan Hughes ehu...@gmail.com wrote:
 indeed and yea without a doubt

 On 25 April 2015 at 09:59, Ali Lown a...@lown.me.uk wrote:

 Hi Evan,

 +1

 After giving this some more thought post the Hangout, I do think that
 moving the docs to Git provides us with a measurable improvement over
 the current situation - particularly with the ability to keep docs
 synced with the releases via branches, and the reduced barrier to
 entry for changing them.

 Would you be interested in leading the migration effort?

 Ali

 On 24 April 2015 at 05:59, Evan Hughes ehu...@gmail.com wrote:
  woops, my bad
 
 
  This is a proposal for the storage of documentation to be moved to a git
  repository instead of on confluence and leave confluence as a place for
  other technical documents used by developers.
 
  *Confluence:*
  *The issues:*
  - contributors must ask for permission from the mailing list to
 be
  given the privilege settings to edit/create pages
  - Simple revision history is kept but is more difficult to easy
  transition documentation between wave release versions, more of a running
  active document
  *The good:*
  *- *easily able to export to pdf and web formats
  - has an easy online rich editor
 
  *Git (markdown):*
  *The issues:*
  *- *setup as a new repository? a folder in current repository?
  apache will need to be involved if a new repository is to be setup
  - exporting the markdown files into a meaningful representation
  (web, pdf), many build systems exist but custom system can also be
 written
  by our committers
  *The good:*
  *- *less of a roadblock, allows users to contribute more, also
  allows new committers a trial at how to add commits using the apache
  procedures
  - Highly customisable
  - Revision history and versions easily achieved for example with
  branches (master, 0.4.x, 0.5.x, )
 
  *TL;DR*
 
  Confluence is a rich wiki but can limit the availability for committers
 to
  publish updates (need to ask permission, which isn't that hard) and is a
  good place to store technical information for the project.
  A markdown written file structured documentation implementation is more
  accessible to developers, follows a more natural flow and can be highly
  customised and has great revision structure.
 
  *Relevant Jira Issues:*
  *- none*
 
  *Please express your opinions below and if enough feedback is present a
  vote from the mailing list should be called after the discussion. *
 
 
  On 24 April 2015 at 14:28, Evan Hughes ehu...@gmail.com wrote:
 
  This is a proposal for 
 
 
  TL;DR

Re: Proposal - Documentation storage

2015-04-28 Thread Ali Lown

Yuri,

I think the main reason to move is to make it easier for people to
make changes, over the existing confluence system. So I would have
though that improving the documentation is something people would be
more likely to do afterwards.

I agree that opening some tickets where the documentation could be
improved does help highlight the problem, but it doesn't make it any
easier for people to fix.

Ali

P.s. Do you want me to do anything for RC9, or are you happy to submit
one? Are you waiting on me for anything still?

On 28 April 2015 at 15:36, Yuri Z vega...@gmail.com wrote:
 Maybe it would be better to move in small steps. Like to go over current
 documentation and open tickets with requests for improvements wherever
 something is missing or not clear.

 On Tue, Apr 28, 2015 at 5:33 PM Ali Lown a...@lown.me.uk wrote:

 Well, doesn't look like anybody else has much opinion.

 Shall I just raise a ticket for a new repo for this?

 It probably makes sense to put the whole website under it, rather than
 using the combination of Apache CMS website + Confluence that we do
 currently. We could just use Jekyll for both website and docs?

 Ali


 On 25 April 2015 at 02:52, Evan Hughes ehu...@gmail.com wrote:
  indeed and yea without a doubt
 
  On 25 April 2015 at 09:59, Ali Lown a...@lown.me.uk wrote:
 
  Hi Evan,
 
  +1
 
  After giving this some more thought post the Hangout, I do think that
  moving the docs to Git provides us with a measurable improvement over
  the current situation - particularly with the ability to keep docs
  synced with the releases via branches, and the reduced barrier to
  entry for changing them.
 
  Would you be interested in leading the migration effort?
 
  Ali
 
  On 24 April 2015 at 05:59, Evan Hughes ehu...@gmail.com wrote:
   woops, my bad
  
  
   This is a proposal for the storage of documentation to be moved to a
 git
   repository instead of on confluence and leave confluence as a place
 for
   other technical documents used by developers.
  
   *Confluence:*
   *The issues:*
   - contributors must ask for permission from the mailing list
 to
  be
   given the privilege settings to edit/create pages
   - Simple revision history is kept but is more difficult to
 easy
   transition documentation between wave release versions, more of a
 running
   active document
   *The good:*
   *- *easily able to export to pdf and web formats
   - has an easy online rich editor
  
   *Git (markdown):*
   *The issues:*
   *- *setup as a new repository? a folder in current repository?
   apache will need to be involved if a new repository is to be setup
   - exporting the markdown files into a meaningful
 representation
   (web, pdf), many build systems exist but custom system can also be
  written
   by our committers
   *The good:*
   *- *less of a roadblock, allows users to contribute more, also
   allows new committers a trial at how to add commits using the apache
   procedures
   - Highly customisable
   - Revision history and versions easily achieved for example
 with
   branches (master, 0.4.x, 0.5.x, )
  
   *TL;DR*
  
   Confluence is a rich wiki but can limit the availability for
 committers
  to
   publish updates (need to ask permission, which isn't that hard) and
 is a
   good place to store technical information for the project.
   A markdown written file structured documentation implementation is
 more
   accessible to developers, follows a more natural flow and can be
 highly
   customised and has great revision structure.
  
   *Relevant Jira Issues:*
   *- none*
  
   *Please express your opinions below and if enough feedback is present
 a
   vote from the mailing list should be called after the discussion. *
  
  
   On 24 April 2015 at 14:28, Evan Hughes ehu...@gmail.com wrote:
  
   This is a proposal for 
  
  
   TL;DR

Re: Proposal - Documentation storage

2015-04-24 Thread Ali Lown

Hi Evan,

+1

After giving this some more thought post the Hangout, I do think that
moving the docs to Git provides us with a measurable improvement over
the current situation - particularly with the ability to keep docs
synced with the releases via branches, and the reduced barrier to
entry for changing them.

Would you be interested in leading the migration effort?

Ali

On 24 April 2015 at 05:59, Evan Hughes ehu...@gmail.com wrote:
 woops, my bad


 This is a proposal for the storage of documentation to be moved to a git
 repository instead of on confluence and leave confluence as a place for
 other technical documents used by developers.

 *Confluence:*
 *The issues:*
 - contributors must ask for permission from the mailing list to be
 given the privilege settings to edit/create pages
 - Simple revision history is kept but is more difficult to easy
 transition documentation between wave release versions, more of a running
 active document
 *The good:*
 *- *easily able to export to pdf and web formats
 - has an easy online rich editor

 *Git (markdown):*
 *The issues:*
 *- *setup as a new repository? a folder in current repository?
 apache will need to be involved if a new repository is to be setup
 - exporting the markdown files into a meaningful representation
 (web, pdf), many build systems exist but custom system can also be written
 by our committers
 *The good:*
 *- *less of a roadblock, allows users to contribute more, also
 allows new committers a trial at how to add commits using the apache
 procedures
 - Highly customisable
 - Revision history and versions easily achieved for example with
 branches (master, 0.4.x, 0.5.x, )

 *TL;DR*

 Confluence is a rich wiki but can limit the availability for committers to
 publish updates (need to ask permission, which isn't that hard) and is a
 good place to store technical information for the project.
 A markdown written file structured documentation implementation is more
 accessible to developers, follows a more natural flow and can be highly
 customised and has great revision structure.

 *Relevant Jira Issues:*
 *- none*

 *Please express your opinions below and if enough feedback is present a
 vote from the mailing list should be called after the discussion. *


 On 24 April 2015 at 14:28, Evan Hughes ehu...@gmail.com wrote:

 This is a proposal for 


 TL;DR

Re: Review Request 31837: Fix for caret issues in Chrome+Linux with periods and apostrophes

2015-04-21 Thread Ali Lown



 On March 9, 2015, 6:15 a.m., Yuri Zelikov wrote:
 
 
 Vicente J. Ruiz Jurado wrote:
 Any other comment? @akaplanov?
 
 Andrew Kaplanov wrote:
 I can't reproduce this situation on Ubuntu with Chrome and Firefox.
 Try to input the same text in another application. Possibly the problem 
 is not caused by Wave.
 
 Vicente J. Ruiz Jurado wrote:
 It's strange that you cannot reproduce it. I have several users 
 complaining about this.
 
 I have just tested in Ubuntu:
 - Chromium 41.0.2272.76, richt click, new window with new temporal profile
 - I open: waveinabox.net
 - Click: New Wave
 - I type:
 abc.abc.abc.
 - What I get?
 abcabcabc.|..
 
 Doing the same test in wiab.pro I get:
 abc.abc.abc.|
 that is the correct behaviour.
 
 the | is the caret
 
 I've tested using both English and Spanish keyboard layout.

I was able to reproduce this in RC8 on Chromium 39 in Linux yesterday.


- Ali


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31837/#review75665
---


On March 9, 2015, 12:23 a.m., Vicente J. Ruiz Jurado wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/31837/
 ---
 
 (Updated March 9, 2015, 12:23 a.m.)
 
 
 Review request for wave, Andrew Kaplanov, Pablo Ojanguren, and Yuri Zelikov.
 
 
 Repository: wave
 
 
 Description
 ---
 
 This patch fix a issue in Chrome+Linux with periods and apostrophes. For 
 instance if you type:
 
 ...abc...
 
 the result must be
 
 ...abc...| 
 
 (where | is the caret/cursor), but instead you get:
 
 abc|..
 
 and the same whith apostrophes:
 
 abc|''
 
 It seems that this issue is not present in wiab.pro so maybe is interesting 
 the review of akaplanov.
 
 
 Diffs
 -
 
   src/org/waveprotocol/wave/client/common/util/SignalKeyLogic.java 5da169a 
 
 Diff: https://reviews.apache.org/r/31837/diff/
 
 
 Testing
 ---
 
 ant waveharness-superdev tested in FF and Chrome (Linux) and Chorme in Mac.
 
 
 Thanks,
 
 Vicente J. Ruiz Jurado

Re: Coming Months

2015-04-20 Thread Ali Lown

Is anyone else coming to this Hangout? If you still need an invite
just drop your G+ name here and I will add you.

Ali

On 20 April 2015 at 18:55, Christian Grobmeier grobme...@apache.org wrote:
Btw, this is me on G+:
https://plus.google.com/+ChristianGrobmeier/posts

On Sun, Apr 19, 2015, at 14:19, Evan Hughes wrote:
(1800 UTC / 6pm UTC) 20th April 2015

On 19 April 2015 at 21:41, Yuri Z vega...@gmail.com wrote:

Thanks, can you specify also the time?

On Sun, Apr 19, 2015 at 12:26 PM Evan Hughes ehu...@gmail.com wrote:

just a reminder that this is happening 20th April, 1800

On 13 April 2015 at 18:49, Christian Grobmeier grobme...@apache.org
wrote:

great, lets make it 20th april

On Sun, Apr 12, 2015, at 15:45, Ali Lown wrote:
I think tomorrow (13th) is a bit short-notice for people now - even
if
they may still be available.

I propose the next suitable time: 20th April, 1800 as the time for
the
hangout.

Ali

On 11 April 2015 at 17:49, Evan Hughes ehu...@gmail.com wrote:
looks like the 6pm UTC on the first day is pretty good for everyone
that
has filled in the doodle except ajr13 unfortunately. We just need
to
confirm the time so people can make plans to be available.
Unfortunately I
was not present during the last hangout so some information on how
the
calling process happened would be helpful.

@Grobmeier:
- Agreed
- Seems the 6pm (UTC) sessions early in the week are pretty common
- Sounds like a good idea, more information the better

On 11 April 2015 at 22:12, Christian Grobmeier
grobme...@apache.org

wrote:

Just checked the doodle and had this on mind:

- we should make sure that as many committers as possible are
there.
In
example. I consider Ali a very important person to participate

- from mentor perspective, I think it's ok if at least one of us
can
participate. I would be sad if I can't meet you all, but if there
is a
time when everybody except could make it, chose it.

- I would like to suggest a QA -after- the official Wave meeting
for
people, who are interested in working with Wave but are concerned
because they don't know what Apache is. What I want to say is: do
you
have any questions on the ASF, would like to learn how it works,
or
anything else, we could clarify this after the first part. That
said,
it
would interesting to know if there are any folks who would like to
see
there ASF related questions answered, even when they are not
related
to
Wave.

Cheers

On Tue, Apr 7, 2015, at 10:16, Upayavira wrote:
Thanks for this, Evan.

Given it was you that proposed the Hangout, it would seem
reasonable
that we try to accommodate you. Anyone here have any objections
to
an
earlier concall, say, 2pm UTC? Are there any Pacific time
participants?

Regarding the document, we need to keep it *really* simple. To
be
quite
frank, when you are trying to restart someone’s heart, you don’t
worry
much about a sore on their leg. We need to be looking for the
absolute
simplest things we can do that might make this project more
accessible.
They have to be small enough that someone here can undertake
them
with a
reasonable certainty of completion and success. The main
resource
we
lack at the moment is people to actually do the work, so we need
to
identify small, manageable tasks that will help draw in new
resources
which might, in turn, allow us to take on larger tasks.

Upayavira

On Tue, Apr 7, 2015, at 04:43 AM, Evan Hughes wrote:
Google Doc full of talking points, available for anyone to
edit
as they
see
fit. Its a combination of the summary Mr Grobmeier made from
the
other
thread and some person thoughts.

Talking points for hangout

https://docs.google.com/document/d/1_7wraANGg6XKfvENPwEgEn7_umlU0Y1eA5CjQcuvhxU/edit?usp=sharing

Need to make sure the hangout is recorded as for myself 12am
2am
4am
is
50/50 shot ill be able to stay awake to watch it live haha.

On 7 April 2015 at 05:26, Ali Lown a...@lown.me.uk wrote:

Times are whatever you set the doodle timezone to be (Top
right).

Ali
On 6 Apr 2015 20:17, Upayavira u...@odoko.co.uk wrote:

I presume times are UTC?

On Mon, Apr 6, 2015, at 02:39 AM, Ali Lown wrote:
Here is a fairly large Doodle poll to see see when may
work
as a
good
date/time for a hangout.

http

Re: Review Request 33237: Updates/fixes for release

2015-04-20 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33237/#review80806
---



CHANGES
https://reviews.apache.org/r/33237/#comment130920

I take this to mean you want to put the release 0.4.0 after the custom 
config changes.

Do we want this? Is it going to annoy anybody?
Perhaps this isn't really a problem, as it is our first release, but 
shouldn't happen during RC'd phase of any subsuquent ones...



build.properties
https://reviews.apache.org/r/33237/#comment130917

Err. When did we get to 0.6.0?

I thought we were handling 0.4.0-rcX


- Ali Lown


On April 15, 2015, 8:09 p.m., Yuri Zelikov wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/33237/
 ---
 
 (Updated April 15, 2015, 8:09 p.m.)
 
 
 Review request for wave and Ali Lown.
 
 
 Repository: wave
 
 
 Description
 ---
 
 The patch contains various updates/fixes related to release.
 
 
 Diffs
 -
 
   CHANGES cf47949 
   README.md b227c16 
   RELEASE-NOTES 916b0ce 
   build.properties 86aad10 
   build.xml 1e721d4 
 
 Diff: https://reviews.apache.org/r/33237/diff/
 
 
 Testing
 ---
 
 
 Thanks,
 
 Yuri Zelikov

Re: [VOTE] Wave Release candidate 8

2015-04-15 Thread Ali Lown

Yuri,

 1 - This one is nasty, forgot to remove the logs... We need to fix the
 release script to ignore logs...

Yes, this would be good to automate so it doesn't get missed in the future.

 2. Right, but this one is minor I think.

Yes, but just something we should probably do.

 3. So, what would be a better name for folder? 0.4.0-RC8? Regarding
 artifact name - I think incubating is actually part of the project name,
 not part of the version. The alpha was added following suggestions in the
 mail list.

Yes, I think as Dave says that 0.4.0-rc8 is a much clearer folder name.

Also, I would either drop the -alpha, or put it right at the end of the name.

Looking at the incubator-general list, the convention definitely seems
to be [name]-[version]-incubating.

http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3CCAMCtmeKen6FpxLL773krEA5xCdAn3ioy0wJdwHcnzkE5bgSCeQ%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3CCAPm%3DoFAFAbky0k1xwadvY1_M%3D9M%3DJkwgURdUJogP_CFmz9W47Q%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-general/201503.mbox/%3CD125F710.ACAA%25gsaha%40hortonworks.com%3E
etc.

I chose explicitly not to block the release, but if you agree also
then creating a new RC is probably best.

Ali

Re: [VOTE] Wave Release candidate 8

2015-04-15 Thread Ali Lown

You can do. Not sure if it is any more useful.

If your upload speed is the limit, you could always just do the
.tar.bz2 src variant, as the others are not the official release.

Ali

On 15 April 2015 at 15:43, Yuri Z vega...@gmail.com wrote:
Ok, I ll create a new RC then. Would you like me to send you a link before
posting a vote for preview?

On Wed, Apr 15, 2015 at 5:41 PM Ali Lown a...@lown.me.uk wrote:

Yuri,

1 - This one is nasty, forgot to remove the logs... We need to fix the
release script to ignore logs...

Yes, this would be good to automate so it doesn't get missed in the future.

2. Right, but this one is minor I think.

Yes, but just something we should probably do.

3. So, what would be a better name for folder? 0.4.0-RC8? Regarding
artifact name - I think incubating is actually part of the project
name,
not part of the version. The alpha was added following suggestions in
the
mail list.

Yes, I think as Dave says that 0.4.0-rc8 is a much clearer folder name.

Also, I would either drop the -alpha, or put it right at the end of the
name.

Looking at the incubator-general list, the convention definitely seems
to be [name]-[version]-incubating.

http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3CCAMCtmeKen6FpxLL773krEA5xCdAn3ioy0wJdwHcnzkE5bgSCeQ%40mail.gmail.com%3E

http://mail-archives.apache.org/mod_mbox/incubator-general/201504.mbox/%3CCAPm%3DoFAFAbky0k1xwadvY1_M%3D9M%3DJkwgURdUJogP_CFmz9W47Q%40mail.gmail.com%3E

http://mail-archives.apache.org/mod_mbox/incubator-general/201503.mbox/%3CD125F710.ACAA%25gsaha%40hortonworks.com%3E
etc.

I chose explicitly not to block the release, but if you agree also
then creating a new RC is probably best.

Ali

Re: [VOTE] Wave Release candidate 8

2015-04-14 Thread Ali Lown

Aah. The closing time for this has snuck up on me. I will test this
out in the morning.

Seems like we could do with a few other people checking it as well though...

Ali

On 11 April 2015 at 18:25, Yuri Z vega...@gmail.com wrote:
 But theactial release won't have the RC8, as it's will be
 incubating-0.4.0-alpha

 On Sat, Apr 11, 2015 at 3:04 PM Christian Grobmeier grobme...@apache.org
 wrote:

 I would name it like:

 0.4-incubating-RC8

 I think this is a more convenient pattern. However for this vote I think
 it's fine. This is more a suggestion for the future.
 however I would pass your information on the naming to the IPMC vote -
 I guess it might confuse people there too.

 On Thu, Apr 9, 2015, at 23:31, Yuri Z wrote:
  It's release candidate 8 for version 0.4.0 alpha. If you think we should
  name it something else - let me know.
 
  On Thu, Apr 9, 2015 at 11:35 PM Christian Grobmeier
  grobme...@apache.org
  wrote:
 
   +1
  
   However, I am still very confused by the link saying it's 0.8 and the
   artifacts saying it's 0.4.
   Are we sure this is what we want? It might pass the IPMC also because
   naming the release is not something which can/should be blocked, but it
   might confuse users.
  
   On Thu, Apr 9, 2015, at 21:49, Yuri Z wrote:
RC8 is now available for review.
It's basically RC7 with artifact names fixed to include incubating
Artifacts can be found here:
   
 https://dist.apache.org/repos/dist/dev/incubator/wave/0.8-incubating/
(Remember checksums are from 'gpg --print-md SHA512 $f  $f.sha')
   
The release version will be: 0.4.0-alpha
   
This is taken from branch (same as RC7)
https://git-wip-us.apache.org/repos/asf?p=incubator-wave.
   git;a=shortlog;h=refs/heads/0.4.0-RC7
   
Reminder on what included previous release candidates:
RC6 included:
- Bug Fixes
   
RC5 included:
- Added MongoDB based deltas store and migration tool for deltas
migration
from file to mongo based store.
   
- Added client/server profiling.
- Added Atmosphere framework as replacement of Socket.IO.
- Added alternative - Gmail style initials avatars.
- Decreased number of permutations in dev compilation and added GWT
superdev mode.
- Upgraded the server to Jetty 9.1.1.
- Added JDK 7 compatibility.
   
RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...
   
A summary of useful information can be found in RELEASE-NOTES, and a
 list
of changes in CHANGES at the above artifact distribution url, as
 well as
being included in the tarballs/zips.(zipballs?)
   
Action Required:
Test the release and make it works on your environment - at least
standard
configurations. Please go over the source files and make sure they
 don't
contain anything that cannot be released under Apache Wave due to
 legal
issues.
   
This vote will close around  GMT 16-th April 2015.
   
[ ] +1   Release it!
[ ] +0   OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...
   
Thanks

Re: TODO entries in the wave src

2015-04-14 Thread Ali Lown

Hi Roshan,

Yes, generally there should be a ticket in JIRA for each 'thing' that
needs doing - some of the TODO's may already have a ticket - but I
doubt most of them do as some are quite old.

We mention the process (in a _very_ brief form on the getting started
page[1]), but generally:

1) Create/assign/etc. a JIRA issue
2) Work on a patch
3) Create a single patch per logical item (might be one per issue -
but could be more for a complex problem)
4) Submit this to review board, with assigned to the wave project, and
mentioning the JIRA issue number it relates to.
5) Wait/pester us to get it reviewed
6) Fix patch as suggested at review
7) Push to git (if the person is a committer then they can do it
themselves, otherwise generally one of the reviewers will do it).

Someone should put the above paragraph in an expanded form on the wiki
contributing page...

Ali

[1]: https://incubator.apache.org/wave/get-involved.html

On 13 April 2015 at 15:40, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
 Hi,

 I have found lot of TODO entries in the wave src.
 If we completed a task.

 How can we submit the patch?
 Can you please tell me the procedure.

 Do we need to make a Jira issue and then submit the patch?
 There are some small TODO entries too.

 Cheers,

 Roshan

Re: Coming Months

2015-04-12 Thread Ali Lown

I think tomorrow (13th) is a bit short-notice for people now - even if
they may still be available.

I propose the next suitable time: 20th April, 1800 as the time for the hangout.

Ali

On 11 April 2015 at 17:49, Evan Hughes ehu...@gmail.com wrote:
looks like the 6pm UTC on the first day is pretty good for everyone that
has filled in the doodle except ajr13 unfortunately. We just need to
confirm the time so people can make plans to be available. Unfortunately I
was not present during the last hangout so some information on how the
calling process happened would be helpful.

@Grobmeier:
- Agreed
- Seems the 6pm (UTC) sessions early in the week are pretty common
- Sounds like a good idea, more information the better

On 11 April 2015 at 22:12, Christian Grobmeier grobme...@apache.org wrote:

Just checked the doodle and had this on mind:

- we should make sure that as many committers as possible are there. In
example. I consider Ali a very important person to participate

- from mentor perspective, I think it's ok if at least one of us can
participate. I would be sad if I can't meet you all, but if there is a
time when everybody except could make it, chose it.

- I would like to suggest a QA -after- the official Wave meeting for
people, who are interested in working with Wave but are concerned
because they don't know what Apache is. What I want to say is: do you
have any questions on the ASF, would like to learn how it works, or
anything else, we could clarify this after the first part. That said, it
would interesting to know if there are any folks who would like to see
there ASF related questions answered, even when they are not related to
Wave.

Cheers

On Tue, Apr 7, 2015, at 10:16, Upayavira wrote:
Thanks for this, Evan.

Given it was you that proposed the Hangout, it would seem reasonable
that we try to accommodate you. Anyone here have any objections to an
earlier concall, say, 2pm UTC? Are there any Pacific time participants?

Regarding the document, we need to keep it *really* simple. To be quite
frank, when you are trying to restart someone’s heart, you don’t worry
much about a sore on their leg. We need to be looking for the absolute
simplest things we can do that might make this project more accessible.
They have to be small enough that someone here can undertake them with a
reasonable certainty of completion and success. The main resource we
lack at the moment is people to actually do the work, so we need to
identify small, manageable tasks that will help draw in new resources
which might, in turn, allow us to take on larger tasks.

Upayavira

On Tue, Apr 7, 2015, at 04:43 AM, Evan Hughes wrote:
Google Doc full of talking points, available for anyone to edit as they
see
fit. Its a combination of the summary Mr Grobmeier made from the other
thread and some person thoughts.

Talking points for hangout

https://docs.google.com/document/d/1_7wraANGg6XKfvENPwEgEn7_umlU0Y1eA5CjQcuvhxU/edit?usp=sharing

Need to make sure the hangout is recorded as for myself 12am 2am 4am
is
50/50 shot ill be able to stay awake to watch it live haha.

On 7 April 2015 at 05:26, Ali Lown a...@lown.me.uk wrote:

Times are whatever you set the doodle timezone to be (Top right).

Ali
On 6 Apr 2015 20:17, Upayavira u...@odoko.co.uk wrote:

I presume times are UTC?

On Mon, Apr 6, 2015, at 02:39 AM, Ali Lown wrote:
Here is a fairly large Doodle poll to see see when may work as a
good
date/time for a hangout.

http://doodle.com/uz9vq9qiwyuqigsa

Let me know if you want more time options.

Ali

On 4 April 2015 at 07:28, Michael MacFadden
michael.macfad...@gmail.com

wrote:
I would be happy to participate. Perhaps the first thing to
know
is..
What time zones people are all in. I am in US Pacific Time Zone
(UTC
-7:00).

~Michael

On 4/2/15, 7:40 AM, Evan Hughes ehu...@gmail.com wrote:

sure, just need to know what time of day is suitable for the
speakers
as we
should keep a record of it for people to view whenever. Thanks
to the
other
threads there's plenty of stuff to compile a list of talking
points,
I'll
put something together over the next week.

On 2 April 2015 at 23:33, Ali Lown a...@lown.me.uk wrote:

I think another hangout would be a great thing to have.

@Evan: Are you happy to organise this?

Ali

On 1 April 2015 at 16:23, John Blossom jblos...@gmail.com
wrote:
Id be glad to listen in, but since I am not a technical
contributor, I
will
try mostly just to monitor.

All the best,

John Blossom

email: jblos...@gmail.com
phone: 203.293.8511
google

Re: WAVE-70

2015-04-09 Thread Ali Lown

Hi Ben,

 I think that you're right to include the wave in full for a first pass.. So
 the email would include three parts text/plain, text/html 
 application/wave

 The above thou may make the email huge in some cases where its a public
 wave or there are lots of participants, would it be better for the large
 change set just to include all blips since the persons last read blip? and
 possibly the last couple of read blips too for context on the wave?

Definitely only include the unread blips, otherwise this could get
huge as you say.
The only problem with just unread blips, is the lack of context -
which would be most noticeable with inline replies.

 I'm not sure how we'd test opening the application/wave part of the email
 thou as we don't have any clients beyond the web one and this can't
 currently interact with an email client :/

Indeed. There is no client with support for this currently, but this
argument could easily fall into the trap of circular reasoning.

No support because no specification, because no implementation,
because no major demand, because no support...

 So if we make the digest soution both instant and hourlydaily/weekly
 configurable, it'd be nice to make this user configurable, do we have any
 user setting anywhere? I don't remember seeing any.

The only user 'settings's currently are handled through the robots
(e.g. the passwordbot).

The client already has support for Popups, so creating a settings one
which talks over a new RPC channel could be done.

Ali

Re: RC7 Vote Release

2015-04-09 Thread Ali Lown

Are all 7 of those vores binding?

Do we really need a vote for fixing the name?

Ali
On 9 Apr 2015 08:02, Yuri Z vega...@gmail.com wrote:

 Hi
 The vote should be over with +7 votes. However it looks like I messed up
 artifacts names - they should include incubating according to
 https://incubator.apache.org/guides/releasemanagement.html#naming
 I guess I ll create new artifacts with fixed names and post a new release
 vote...

 On Wed, Apr 8, 2015 at 1:10 PM Pablo Ojanguren pablo...@gmail.com wrote:

  Hi,
 
  Installed RC7 on Ubuntu 14.04 LTS. Tested in Firefox and Chrome. Tested
  memory and MongoDb storage. It works as expected.
 
  +1
 
  2015-04-08 11:03 GMT+02:00 Roshan Lakmal roshan.2013...@iit.ac.lk:
 
   Hi,
  
   I installed the RC7 on Ubuntu 14.04.1 LTS and it working fine.
  
   +1
  
   Thanks,
  
   Roshan
  
  
  
   On Tue, Apr 7, 2015 at 6:48 PM, Ben Hegarty heg...@gmail.com wrote:
  
Hi,
I've downloaded and ran up an instance to test it's operational @
wiab.cloudapp.net feel free to test with it. :)
   
+1
   
On Tue, Apr 7, 2015 at 2:09 PM, Ali Lown a...@lown.me.uk wrote:
   
 Hi all,

 The end time for this is tomorrow, more votes = better!

 So, if you downloaded and tested this, but forgot to send an email,
 then this is your last chance.
 If you haven't downloaded and tested this yet, then please do so
  soon!

 Thanks,
 Ali

 On 5 April 2015 at 22:02, Michael MacFadden 
   michael.macfad...@gmail.com

 wrote:
  Ali,
 
  Adding them now.  First one is in.
 
 
 
 
  On 4/4/15, 12:30 PM, Ali Lown a...@lown.me.uk wrote:
 
 @Michael: What CSS type issues are these? Could you raise a JIRA
   issue
 for it?
 
 Ali
 
 On 4 April 2015 at 19:58, Michael MacFadden 
michael.macfad...@gmail.com
 wrote:
  All,
 
  I installed the RC on OS X and on Windows 7.  Ran fine on both.
 Tested the UI out in Chrome, FF, and IE.  As usual a few CSS type
   issues,
 but no blockers.
 
  Again.. +1.
 
 
 
  On 4/4/15, 11:24 AM, Yuri Z vega...@gmail.com wrote:
 
 +1 I tested install and went over licenses in source files (we
   still
 have a
 lot of files with multiple license headers in them), checked
   NOTICE,
 DISCLAIMER, CHANGES, THANKS, LICENSE and RELEASE-NOTES files.
 
 On Sat, Apr 4, 2015 at 7:53 PM Ali Lown a...@lown.me.uk
 wrote:
 
  +1.
 
  Tested install, federation, memory and file backends.
 
  Ali
 
  On 2 April 2015 at 14:38, Ali Lown a...@lown.me.uk wrote:
   I have so far tested the SHA digest, GPG signature, and the
   KEYS/CHANGES/RELEASE-NOTE files, all are fine.
  
   I intend to test federation tomorrow to check it isn't
  broken.
  
   Has anyone checked the file copyright notices?
  
   Ali
  
   On 2 April 2015 at 00:31, Michael MacFadden 
 michael.macfad...@gmail.com
  wrote:
   +1
  
  
  
  
   On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk wrote:
  
  +1
  
  lgtm - tested simple install, user registration and local
   waves.
  
  Dave
  
  On 01/04/15 06:11, Yuri Z wrote:
   RC7 is now available for review.
  
   Artifacts can be found here:
   *https://dist.apache.org/repos/dist/dev/incubator/wave/
  0.7-incubating/
   https://dist.apache.org/repos/dist/dev/incubator/wave/
  0.7-incubating/*
   (Remember checksums are from 'gpg --print-md SHA512 $f 
 $f.sha')
  
   The release version will be: 0.4.0-alpha
  
   This is taken from branch
   *https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/0.4.0-RC7
   https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/0.4.0-RC7*
  
   Reminder on what included previous release candidates:
   RC6 included:
   - Bug Fixes
  
   RC5 included:
   - Added MongoDB based deltas store and migration tool
 for
deltas
  migration
   from file to mongo based store.
  
   - Added client/server profiling.
   - Added Atmosphere framework as replacement of
 Socket.IO.
   - Added alternative - Gmail style initials avatars.
   - Decreased number of permutations in dev compilation
 and
added
 GWT
   superdev mode.
   - Upgraded the server to Jetty 9.1.1.
   - Added JDK 7 compatibility.
  
   RC4 included:
   - More licensing fixes
   - Federation works
   - New and updated translations
   - And more...
  
   A summary of useful information can be found in
   RELEASE-NOTES,
 and a
  list
   of changes in CHANGES at the above artifact distribution
   url,
 as well
  as
   being included in the tarballs/zips.(zipballs?)
  
   *Action

Re: RC7 Vote Release

2015-04-09 Thread Ali Lown

I meant votes.
On 9 Apr 2015 10:49, Ali Lown a...@lown.me.uk wrote:

 Are all 7 of those vores binding?

 Do we really need a vote for fixing the name?

 Ali
 On 9 Apr 2015 08:02, Yuri Z vega...@gmail.com wrote:

 Hi
 The vote should be over with +7 votes. However it looks like I messed up
 artifacts names - they should include incubating according to
 https://incubator.apache.org/guides/releasemanagement.html#naming
 I guess I ll create new artifacts with fixed names and post a new release
 vote...

 On Wed, Apr 8, 2015 at 1:10 PM Pablo Ojanguren pablo...@gmail.com
 wrote:

  Hi,
 
  Installed RC7 on Ubuntu 14.04 LTS. Tested in Firefox and Chrome. Tested
  memory and MongoDb storage. It works as expected.
 
  +1
 
  2015-04-08 11:03 GMT+02:00 Roshan Lakmal roshan.2013...@iit.ac.lk:
 
   Hi,
  
   I installed the RC7 on Ubuntu 14.04.1 LTS and it working fine.
  
   +1
  
   Thanks,
  
   Roshan
  
  
  
   On Tue, Apr 7, 2015 at 6:48 PM, Ben Hegarty heg...@gmail.com wrote:
  
Hi,
I've downloaded and ran up an instance to test it's operational @
wiab.cloudapp.net feel free to test with it. :)
   
+1
   
On Tue, Apr 7, 2015 at 2:09 PM, Ali Lown a...@lown.me.uk wrote:
   
 Hi all,

 The end time for this is tomorrow, more votes = better!

 So, if you downloaded and tested this, but forgot to send an
 email,
 then this is your last chance.
 If you haven't downloaded and tested this yet, then please do so
  soon!

 Thanks,
 Ali

 On 5 April 2015 at 22:02, Michael MacFadden 
   michael.macfad...@gmail.com

 wrote:
  Ali,
 
  Adding them now.  First one is in.
 
 
 
 
  On 4/4/15, 12:30 PM, Ali Lown a...@lown.me.uk wrote:
 
 @Michael: What CSS type issues are these? Could you raise a JIRA
   issue
 for it?
 
 Ali
 
 On 4 April 2015 at 19:58, Michael MacFadden 
michael.macfad...@gmail.com
 wrote:
  All,
 
  I installed the RC on OS X and on Windows 7.  Ran fine on
 both.
 Tested the UI out in Chrome, FF, and IE.  As usual a few CSS type
   issues,
 but no blockers.
 
  Again.. +1.
 
 
 
  On 4/4/15, 11:24 AM, Yuri Z vega...@gmail.com wrote:
 
 +1 I tested install and went over licenses in source files (we
   still
 have a
 lot of files with multiple license headers in them), checked
   NOTICE,
 DISCLAIMER, CHANGES, THANKS, LICENSE and RELEASE-NOTES files.
 
 On Sat, Apr 4, 2015 at 7:53 PM Ali Lown a...@lown.me.uk
 wrote:
 
  +1.
 
  Tested install, federation, memory and file backends.
 
  Ali
 
  On 2 April 2015 at 14:38, Ali Lown a...@lown.me.uk wrote:
   I have so far tested the SHA digest, GPG signature, and
 the
   KEYS/CHANGES/RELEASE-NOTE files, all are fine.
  
   I intend to test federation tomorrow to check it isn't
  broken.
  
   Has anyone checked the file copyright notices?
  
   Ali
  
   On 2 April 2015 at 00:31, Michael MacFadden 
 michael.macfad...@gmail.com
  wrote:
   +1
  
  
  
  
   On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk
 wrote:
  
  +1
  
  lgtm - tested simple install, user registration and local
   waves.
  
  Dave
  
  On 01/04/15 06:11, Yuri Z wrote:
   RC7 is now available for review.
  
   Artifacts can be found here:
   *
 https://dist.apache.org/repos/dist/dev/incubator/wave/
  0.7-incubating/
   
 https://dist.apache.org/repos/dist/dev/incubator/wave/
  0.7-incubating/*
   (Remember checksums are from 'gpg --print-md SHA512 $f
 
 $f.sha')
  
   The release version will be: 0.4.0-alpha
  
   This is taken from branch
   *https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/0.4.0-RC7
   https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/0.4.0-RC7*
  
   Reminder on what included previous release candidates:
   RC6 included:
   - Bug Fixes
  
   RC5 included:
   - Added MongoDB based deltas store and migration tool
 for
deltas
  migration
   from file to mongo based store.
  
   - Added client/server profiling.
   - Added Atmosphere framework as replacement of
 Socket.IO.
   - Added alternative - Gmail style initials avatars.
   - Decreased number of permutations in dev compilation
 and
added
 GWT
   superdev mode.
   - Upgraded the server to Jetty 9.1.1.
   - Added JDK 7 compatibility.
  
   RC4 included:
   - More licensing fixes
   - Federation works
   - New and updated translations
   - And more...
  
   A summary of useful information can be found in
   RELEASE-NOTES,
 and a
  list
   of changes in CHANGES at the above artifact
 distribution
   url,
 as well

Re: Review Request 32893: Replaces custom config framework with typesafe config

2015-04-07 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32893/#review79166
---


Looks generally fine to me. You seem to have made other small changes to many 
of the files (tidying up imports, sanitizing parameters/exception, etc.) most 
of which are fine.

Eagerly sanitizing the file on startup is quite important, how best do we go 
about getting that?
Should we have some may of migrating the existing *.conf files for people, or 
do we just put that this has changed in big letters in RELEASE-NOTES?

I have highlighted a few things I spotted below:


server-config.xml
https://reviews.apache.org/r/32893/#comment128354

Why does this need to remain?

Actually, why does this file exist at all anymore? We could move the 
prosody-config section back into build.xml now.



server-config.xml
https://reviews.apache.org/r/32893/#comment128353

Can't we get rid of these, given the use of the federation.* config space.



test/org/waveprotocol/wave/federation/xmpp/XmppDiscoTest.java
https://reviews.apache.org/r/32893/#comment128352

This may prevent federation between older versions of the server and ones 
running with this change.

Whilst it should occur - as we really shouldn't have anything saying 
'google' left in here, I am not convinced this is the right patch...


- Ali Lown


On April 6, 2015, 7:23 p.m., Yuri Zelikov wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/32893/
 ---
 
 (Updated April 6, 2015, 7:23 p.m.)
 
 
 Review request for wave, Andrew Kaplanov and Ali Lown.
 
 
 Bugs: WAVE-423
 https://issues.apache.org/jira/browse/WAVE-423
 
 
 Repository: wave
 
 
 Description
 ---
 
 As of now Wiab uses a custom written configuration framework. The 
 configuration is defined in server.config and federation.server.config files. 
 In short - in order to add a new configuration property - one needs to edit 3 
 files in several locations. Also, it makes it really inconvenient to override 
 default settings with custom ones. The introduction of Typesafe Config solves 
 almost all these issues. Now, all default settings are defined in 
 reference.conf in HOCON format (typesafe config can also parse properties and 
 json formats). One can provide application.conf file with settings that will 
 override those in reference.conf. Or alternatively to pass them as JVM args 
 or environment variables - which will override both application.conf and 
 reference.conf.
 Currently the only disadvantage is that configuration is not validated 
 eagerly on startup, but only when accessed. This can be added later.
 
 
 Diffs
 -
 
   .classpath 824e720 
   .gitignore 42c8e03 
   build.xml 52000a0 
   run-server.bat 78c9fbf 
   run-server.sh 3ee3eb4 
   server-config.xml 30b33c2 
   server.config.example bc25193 
   server.federation.config de69730 
   server.federation.config.example f0c8d82 
   src/org/waveprotocol/box/server/CoreSettings.java 5fbd345 
   src/org/waveprotocol/box/server/DataMigrationTool.java 32e0d50 
   src/org/waveprotocol/box/server/SearchModule.java 9848a7f 
   src/org/waveprotocol/box/server/ServerMain.java 94ee5ae 
   src/org/waveprotocol/box/server/ServerModule.java 0266942 
   src/org/waveprotocol/box/server/StatModule.java 6c5af5e 
   src/org/waveprotocol/box/server/executor/ExecutorsModule.java ca0d365 
   src/org/waveprotocol/box/server/persistence/PersistenceModule.java 3016671 
   src/org/waveprotocol/box/server/persistence/file/FileAccountStore.java 
 d4608dc 
   src/org/waveprotocol/box/server/persistence/file/FileAttachmentStore.java 
 96b23a3 
   src/org/waveprotocol/box/server/persistence/file/FileDeltaStore.java 
 a615693 
   src/org/waveprotocol/box/server/persistence/file/FileSignerInfoStore.java 
 e8686f4 
   src/org/waveprotocol/box/server/persistence/lucene/FSIndexDirectory.java 
 4badd7c 
   src/org/waveprotocol/box/server/robots/ProfileFetcherModule.java be8f7ea 
   src/org/waveprotocol/box/server/robots/RobotApiModule.java 6bcaadb 
   src/org/waveprotocol/box/server/robots/RobotRegistrationServlet.java 
 b99d274 
   src/org/waveprotocol/box/server/robots/agent/AbstractBaseRobotAgent.java 
 a549cc0 
   src/org/waveprotocol/box/server/robots/agent/AbstractCliRobotAgent.java 
 dd878bc 
   src/org/waveprotocol/box/server/robots/agent/passwd/PasswordAdminRobot.java 
 49dbbf2 
   
 src/org/waveprotocol/box/server/robots/agent/registration/RegistrationRobot.java
  11fad95 
   src/org/waveprotocol/box/server/robots/agent/welcome/WelcomeRobot.java 
 ba041cd 
   
 src/org/waveprotocol/box/server/robots/operations/GravatarProfilesFetcher.java
  75501a7 
   src/org/waveprotocol/box/server/robots/operations/ImportDeltasService.java 
 c313f12

Re: RC7 Vote Release

2015-04-07 Thread Ali Lown

Hi all,

The end time for this is tomorrow, more votes = better!

So, if you downloaded and tested this, but forgot to send an email,
then this is your last chance.
If you haven't downloaded and tested this yet, then please do so soon!

Thanks,
Ali

On 5 April 2015 at 22:02, Michael MacFadden michael.macfad...@gmail.com wrote:
 Ali,

 Adding them now.  First one is in.




 On 4/4/15, 12:30 PM, Ali Lown a...@lown.me.uk wrote:

@Michael: What CSS type issues are these? Could you raise a JIRA issue for it?

Ali

On 4 April 2015 at 19:58, Michael MacFadden michael.macfad...@gmail.com 
wrote:
 All,

 I installed the RC on OS X and on Windows 7.  Ran fine on both.  Tested the 
 UI out in Chrome, FF, and IE.  As usual a few CSS type issues, but no 
 blockers.

 Again.. +1.



 On 4/4/15, 11:24 AM, Yuri Z vega...@gmail.com wrote:

+1 I tested install and went over licenses in source files (we still have a
lot of files with multiple license headers in them), checked NOTICE,
DISCLAIMER, CHANGES, THANKS, LICENSE and RELEASE-NOTES files.

On Sat, Apr 4, 2015 at 7:53 PM Ali Lown a...@lown.me.uk wrote:

 +1.

 Tested install, federation, memory and file backends.

 Ali

 On 2 April 2015 at 14:38, Ali Lown a...@lown.me.uk wrote:
  I have so far tested the SHA digest, GPG signature, and the
  KEYS/CHANGES/RELEASE-NOTE files, all are fine.
 
  I intend to test federation tomorrow to check it isn't broken.
 
  Has anyone checked the file copyright notices?
 
  Ali
 
  On 2 April 2015 at 00:31, Michael MacFadden 
  michael.macfad...@gmail.com
 wrote:
  +1
 
 
 
 
  On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk wrote:
 
 +1
 
 lgtm - tested simple install, user registration and local waves.
 
 Dave
 
 On 01/04/15 06:11, Yuri Z wrote:
  RC7 is now available for review.
 
  Artifacts can be found here:
  *https://dist.apache.org/repos/dist/dev/incubator/wave/
 0.7-incubating/
  https://dist.apache.org/repos/dist/dev/incubator/wave/
 0.7-incubating/*
  (Remember checksums are from 'gpg --print-md SHA512 $f  $f.sha')
 
  The release version will be: 0.4.0-alpha
 
  This is taken from branch
  *https://git-wip-us.apache.org/repos/asf?p=incubator-
 wave.git;a=shortlog;h=refs/heads/0.4.0-RC7
  https://git-wip-us.apache.org/repos/asf?p=incubator-
 wave.git;a=shortlog;h=refs/heads/0.4.0-RC7*
 
  Reminder on what included previous release candidates:
  RC6 included:
  - Bug Fixes
 
  RC5 included:
  - Added MongoDB based deltas store and migration tool for deltas
 migration
  from file to mongo based store.
 
  - Added client/server profiling.
  - Added Atmosphere framework as replacement of Socket.IO.
  - Added alternative - Gmail style initials avatars.
  - Decreased number of permutations in dev compilation and added GWT
  superdev mode.
  - Upgraded the server to Jetty 9.1.1.
  - Added JDK 7 compatibility.
 
  RC4 included:
  - More licensing fixes
  - Federation works
  - New and updated translations
  - And more...
 
  A summary of useful information can be found in RELEASE-NOTES, and a
 list
  of changes in CHANGES at the above artifact distribution url, as well
 as
  being included in the tarballs/zips.(zipballs?)
 
  *Action Required:*
  *Test the release and make it works on your environment - at least
 standard
  configurations. Please go over the source files and make sure they
 don't
  contain anything that cannot be released under Apache Wave due to
 legal
  issues.*
 
  This vote will close around  GMT 8-th April 2015.
 
  [ ] +1   Release it!
  [ ] +0   OK, but...
  [ ] -0OK, but you really should fix
  [ ] -1Definitely not because...
 
  Thanks

Re: Review Request 32893: Replaces custom config framework with typesafe config

2015-04-07 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32893/#review79247
---

Ship it!


LGTM.

- Ali Lown


On April 6, 2015, 7:23 p.m., Yuri Zelikov wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/32893/
 ---
 
 (Updated April 6, 2015, 7:23 p.m.)
 
 
 Review request for wave, Andrew Kaplanov and Ali Lown.
 
 
 Bugs: WAVE-423
 https://issues.apache.org/jira/browse/WAVE-423
 
 
 Repository: wave
 
 
 Description
 ---
 
 As of now Wiab uses a custom written configuration framework. The 
 configuration is defined in server.config and federation.server.config files. 
 In short - in order to add a new configuration property - one needs to edit 3 
 files in several locations. Also, it makes it really inconvenient to override 
 default settings with custom ones. The introduction of Typesafe Config solves 
 almost all these issues. Now, all default settings are defined in 
 reference.conf in HOCON format (typesafe config can also parse properties and 
 json formats). One can provide application.conf file with settings that will 
 override those in reference.conf. Or alternatively to pass them as JVM args 
 or environment variables - which will override both application.conf and 
 reference.conf.
 Currently the only disadvantage is that configuration is not validated 
 eagerly on startup, but only when accessed. This can be added later.
 
 
 Diffs
 -
 
   .classpath 824e720 
   .gitignore 42c8e03 
   build.xml 52000a0 
   run-server.bat 78c9fbf 
   run-server.sh 3ee3eb4 
   server-config.xml 30b33c2 
   server.config.example bc25193 
   server.federation.config de69730 
   server.federation.config.example f0c8d82 
   src/org/waveprotocol/box/server/CoreSettings.java 5fbd345 
   src/org/waveprotocol/box/server/DataMigrationTool.java 32e0d50 
   src/org/waveprotocol/box/server/SearchModule.java 9848a7f 
   src/org/waveprotocol/box/server/ServerMain.java 94ee5ae 
   src/org/waveprotocol/box/server/ServerModule.java 0266942 
   src/org/waveprotocol/box/server/StatModule.java 6c5af5e 
   src/org/waveprotocol/box/server/executor/ExecutorsModule.java ca0d365 
   src/org/waveprotocol/box/server/persistence/PersistenceModule.java 3016671 
   src/org/waveprotocol/box/server/persistence/file/FileAccountStore.java 
 d4608dc 
   src/org/waveprotocol/box/server/persistence/file/FileAttachmentStore.java 
 96b23a3 
   src/org/waveprotocol/box/server/persistence/file/FileDeltaStore.java 
 a615693 
   src/org/waveprotocol/box/server/persistence/file/FileSignerInfoStore.java 
 e8686f4 
   src/org/waveprotocol/box/server/persistence/lucene/FSIndexDirectory.java 
 4badd7c 
   src/org/waveprotocol/box/server/robots/ProfileFetcherModule.java be8f7ea 
   src/org/waveprotocol/box/server/robots/RobotApiModule.java 6bcaadb 
   src/org/waveprotocol/box/server/robots/RobotRegistrationServlet.java 
 b99d274 
   src/org/waveprotocol/box/server/robots/agent/AbstractBaseRobotAgent.java 
 a549cc0 
   src/org/waveprotocol/box/server/robots/agent/AbstractCliRobotAgent.java 
 dd878bc 
   src/org/waveprotocol/box/server/robots/agent/passwd/PasswordAdminRobot.java 
 49dbbf2 
   
 src/org/waveprotocol/box/server/robots/agent/registration/RegistrationRobot.java
  11fad95 
   src/org/waveprotocol/box/server/robots/agent/welcome/WelcomeRobot.java 
 ba041cd 
   
 src/org/waveprotocol/box/server/robots/operations/GravatarProfilesFetcher.java
  75501a7 
   src/org/waveprotocol/box/server/robots/operations/ImportDeltasService.java 
 c313f12 
   src/org/waveprotocol/box/server/rpc/AttachmentServlet.java ce30ac0 
   src/org/waveprotocol/box/server/rpc/AuthenticationServlet.java 49d5964 
   src/org/waveprotocol/box/server/rpc/ServerRpcProvider.java deaf01b 
   src/org/waveprotocol/box/server/rpc/UserRegistrationServlet.java 0b858a9 
   src/org/waveprotocol/box/server/rpc/WaveClientServlet.java 37bb8de 
   src/org/waveprotocol/box/server/waveserver/CertificateManagerImpl.java 
 75569bc 
   
 src/org/waveprotocol/box/server/waveserver/LucenePerUserWaveViewHandlerImpl.java
  02aa58b 
   src/org/waveprotocol/box/server/waveserver/NonSigningSignatureHandler.java 
 e87b6bf 
   src/org/waveprotocol/box/server/waveserver/SigningSignatureHandler.java 
 7133808 
   src/org/waveprotocol/box/server/waveserver/SimpleSearchProviderImpl.java 
 9884daf 
   src/org/waveprotocol/box/server/waveserver/SolrSearchProviderImpl.java 
 a46dc93 
   src/org/waveprotocol/box/server/waveserver/SolrWaveIndexerImpl.java 5403b5f 
   src/org/waveprotocol/box/server/waveserver/WaveMap.java 09ee788 
   src/org/waveprotocol/box/server/waveserver/WaveServerModule.java 5743594 
   src/org/waveprotocol/wave/federation/FederationSettings.java bad3199 
   src/org

Re: WAVE-70

2015-04-07 Thread Ali Lown

Hi Ben,

 Sending multiple versions of the email using the MIME implementation would
 be perfect, I have just a couple of questions...
 1. I would assume we should send text/plain and text/html, should we
 also send something like application/wave? What would application/wave
 look like? is there some data format I could use to build this out?

There is no precedent for this that I know of. application/wave
seems like a sensible type to go with for now.
As for the data format, you have a few options:
i) Just include a full wave snapshot base64'd
ii) Just include a URL to the wave on the hosting server, and include
the base64'd delta of what happened last (might not be human
presentable though...)
iii) Include a URL to the wave, and include the blip which 'changed'
in some format (could be base64'd, could be the html render of it,
etc.)

 2. What are we expecting in this email... is it just any new blips that are
 unread on my wave? When should it be sent if its a noisy wave? (should we
 include the last (parent) blips?)

Heh. Ties into above.

This is really the 'digest' question in disguise. Do we expect instant
notification mails, or hourly/daily/weekly digests with everything in?
(Or do we really want both!)

 3. Should emails be created for public waves?

At which stage of 'public'? Once a user contributes to a public wave,
they become an explicit participant, at which point I would expect
them to get emails. If they manually add themselves as an explicit
participant without changing anything, I would also expect emails.
Otherwise no.

*But* we could include it in a digest of some form. It really depends
on how busy that server is and what exactly the participants want.
(Think of a private server amongst a few friends vs a public server
run by a large company).

 The postfix solution sounds perfect :)
 4. I take it the autogenerated email address will just be the same as the
 wave id we use?

Yes, that is what I would use, and then bodge in an MTA. It may be
nice to offer the email 'domain' part as a configurable option for the
wave server though (not really any more work).

Ali

Re: Coming Months

2015-04-06 Thread Ali Lown

Times are whatever you set the doodle timezone to be (Top right).

Ali
On 6 Apr 2015 20:17, Upayavira u...@odoko.co.uk wrote:

 I presume times are UTC?

 On Mon, Apr 6, 2015, at 02:39 AM, Ali Lown wrote:
  Here is a fairly large Doodle poll to see see when may work as a good
  date/time for a hangout.
 
  http://doodle.com/uz9vq9qiwyuqigsa
 
  Let me know if you want more time options.
 
  Ali
 
  On 4 April 2015 at 07:28, Michael MacFadden michael.macfad...@gmail.com
 
  wrote:
   I would be happy to participate.  Perhaps the first thing to know is..
 What time zones people are all in.  I am in US Pacific Time Zone (UTC
 -7:00).
  
   ~Michael
  
  
  
  
   On 4/2/15, 7:40 AM, Evan Hughes ehu...@gmail.com wrote:
  
  sure, just need to know what time of day is suitable for the speakers
 as we
  should keep a record of it for people to view whenever. Thanks to the
 other
  threads there's plenty of stuff to compile a list of talking points,
 I'll
  put something together over the next week.
  
  On 2 April 2015 at 23:33, Ali Lown a...@lown.me.uk wrote:
  
   I think another hangout would be a great thing to have.
  
   @Evan: Are you happy to organise this?
  
   Ali
  
   On 1 April 2015 at 16:23, John Blossom jblos...@gmail.com wrote:
Id be glad to listen in, but since I am not a technical
 contributor, I
   will
try mostly just to monitor.
   
All the best,
   
John Blossom
   
email: jblos...@gmail.com
phone: 203.293.8511
google+: google.com/+JohnBlossom
   
On Mon, Mar 30, 2015 at 11:26 PM, Evan Hughes ehu...@gmail.com
 wrote:
   
Hey all,
   
could we get a Google hangout of the Mentors and contributors to
   solidify
the direction which wave will be heading and pointing out what
 needs to
   be
done other than just thoughts on the mailing list.

Re: Coming Months

2015-04-05 Thread Ali Lown

Here is a fairly large Doodle poll to see see when may work as a good
date/time for a hangout.

http://doodle.com/uz9vq9qiwyuqigsa

Let me know if you want more time options.

Ali

On 4 April 2015 at 07:28, Michael MacFadden michael.macfad...@gmail.com wrote:
 I would be happy to participate.  Perhaps the first thing to know is.. What 
 time zones people are all in.  I am in US Pacific Time Zone (UTC -7:00).

 ~Michael




 On 4/2/15, 7:40 AM, Evan Hughes ehu...@gmail.com wrote:

sure, just need to know what time of day is suitable for the speakers as we
should keep a record of it for people to view whenever. Thanks to the other
threads there's plenty of stuff to compile a list of talking points, I'll
put something together over the next week.

On 2 April 2015 at 23:33, Ali Lown a...@lown.me.uk wrote:

 I think another hangout would be a great thing to have.

 @Evan: Are you happy to organise this?

 Ali

 On 1 April 2015 at 16:23, John Blossom jblos...@gmail.com wrote:
  Id be glad to listen in, but since I am not a technical contributor, I
 will
  try mostly just to monitor.
 
  All the best,
 
  John Blossom
 
  email: jblos...@gmail.com
  phone: 203.293.8511
  google+: google.com/+JohnBlossom
 
  On Mon, Mar 30, 2015 at 11:26 PM, Evan Hughes ehu...@gmail.com wrote:
 
  Hey all,
 
  could we get a Google hangout of the Mentors and contributors to
 solidify
  the direction which wave will be heading and pointing out what needs to
 be
  done other than just thoughts on the mailing list.

Re: RC7 Vote Release

2015-04-04 Thread Ali Lown

+1.

Tested install, federation, memory and file backends.

Ali

On 2 April 2015 at 14:38, Ali Lown a...@lown.me.uk wrote:
I have so far tested the SHA digest, GPG signature, and the
KEYS/CHANGES/RELEASE-NOTE files, all are fine.

I intend to test federation tomorrow to check it isn't broken.

Has anyone checked the file copyright notices?

Ali

On 2 April 2015 at 00:31, Michael MacFadden michael.macfad...@gmail.com
wrote:
+1

On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk wrote:

lgtm - tested simple install, user registration and local waves.

Dave

On 01/04/15 06:11, Yuri Z wrote:
RC7 is now available for review.

Artifacts can be found here:
*https://dist.apache.org/repos/dist/dev/incubator/wave/0.7-incubating/
https://dist.apache.org/repos/dist/dev/incubator/wave/0.7-incubating/*
(Remember checksums are from 'gpg --print-md SHA512 $f $f.sha')

The release version will be: 0.4.0-alpha

This is taken from branch
*https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC7
https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC7*

Reminder on what included previous release candidates:
RC6 included:
- Bug Fixes

RC5 included:
- Added MongoDB based deltas store and migration tool for deltas migration
from file to mongo based store.

RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

A summary of useful information can be found in RELEASE-NOTES, and a list
of changes in CHANGES at the above artifact distribution url, as well as
being included in the tarballs/zips.(zipballs?)

*Action Required:*
*Test the release and make it works on your environment - at least standard
configurations. Please go over the source files and make sure they don't
contain anything that cannot be released under Apache Wave due to legal
issues.*

This vote will close around GMT 8-th April 2015.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks

Re: WAVE-70

2015-04-04 Thread Ali Lown

Hi Ben,

I remember Bruno doing some work on this a while back. You should be
able to find his patches in the list archives.

The issue seems to be currently assigned to Kasun, but I don't recall
anything coming of this, so you should be quite safe to have a go at
it.

Please re-assign it to yourself on JIRA.

What approach to this are you planning on taking?

Ali

On 4 April 2015 at 20:00, Ben Hegarty heg...@gmail.com wrote:
 apache secretary for commit privs..

 Regards Ben

 On Sat, Apr 4, 2015 at 7:59 PM, Ben Hegarty heg...@gmail.com wrote:

 Hi guys,

 Has anyone looked into this issue? if not I'd like to take ownership and
 start work on it, I've submitted the agreement to the

 --
 Regards
 Ben




 --
 Regards
 Ben

Re: RC7 Vote Release

2015-04-04 Thread Ali Lown

@Michael: What CSS type issues are these? Could you raise a JIRA issue for it?

Ali

On 4 April 2015 at 19:58, Michael MacFadden michael.macfad...@gmail.com wrote:
 All,

 I installed the RC on OS X and on Windows 7.  Ran fine on both.  Tested the 
 UI out in Chrome, FF, and IE.  As usual a few CSS type issues, but no 
 blockers.

 Again.. +1.



 On 4/4/15, 11:24 AM, Yuri Z vega...@gmail.com wrote:

+1 I tested install and went over licenses in source files (we still have a
lot of files with multiple license headers in them), checked NOTICE,
DISCLAIMER, CHANGES, THANKS, LICENSE and RELEASE-NOTES files.

On Sat, Apr 4, 2015 at 7:53 PM Ali Lown a...@lown.me.uk wrote:

 +1.

 Tested install, federation, memory and file backends.

 Ali

 On 2 April 2015 at 14:38, Ali Lown a...@lown.me.uk wrote:
  I have so far tested the SHA digest, GPG signature, and the
  KEYS/CHANGES/RELEASE-NOTE files, all are fine.
 
  I intend to test federation tomorrow to check it isn't broken.
 
  Has anyone checked the file copyright notices?
 
  Ali
 
  On 2 April 2015 at 00:31, Michael MacFadden michael.macfad...@gmail.com
 wrote:
  +1
 
 
 
 
  On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk wrote:
 
 +1
 
 lgtm - tested simple install, user registration and local waves.
 
 Dave
 
 On 01/04/15 06:11, Yuri Z wrote:
  RC7 is now available for review.
 
  Artifacts can be found here:
  *https://dist.apache.org/repos/dist/dev/incubator/wave/
 0.7-incubating/
  https://dist.apache.org/repos/dist/dev/incubator/wave/
 0.7-incubating/*
  (Remember checksums are from 'gpg --print-md SHA512 $f  $f.sha')
 
  The release version will be: 0.4.0-alpha
 
  This is taken from branch
  *https://git-wip-us.apache.org/repos/asf?p=incubator-
 wave.git;a=shortlog;h=refs/heads/0.4.0-RC7
  https://git-wip-us.apache.org/repos/asf?p=incubator-
 wave.git;a=shortlog;h=refs/heads/0.4.0-RC7*
 
  Reminder on what included previous release candidates:
  RC6 included:
  - Bug Fixes
 
  RC5 included:
  - Added MongoDB based deltas store and migration tool for deltas
 migration
  from file to mongo based store.
 
  - Added client/server profiling.
  - Added Atmosphere framework as replacement of Socket.IO.
  - Added alternative - Gmail style initials avatars.
  - Decreased number of permutations in dev compilation and added GWT
  superdev mode.
  - Upgraded the server to Jetty 9.1.1.
  - Added JDK 7 compatibility.
 
  RC4 included:
  - More licensing fixes
  - Federation works
  - New and updated translations
  - And more...
 
  A summary of useful information can be found in RELEASE-NOTES, and a
 list
  of changes in CHANGES at the above artifact distribution url, as well
 as
  being included in the tarballs/zips.(zipballs?)
 
  *Action Required:*
  *Test the release and make it works on your environment - at least
 standard
  configurations. Please go over the source files and make sure they
 don't
  contain anything that cannot be released under Apache Wave due to
 legal
  issues.*
 
  This vote will close around  GMT 8-th April 2015.
 
  [ ] +1   Release it!
  [ ] +0   OK, but...
  [ ] -0OK, but you really should fix
  [ ] -1Definitely not because...
 
  Thanks

Re: WAVE-70

2015-04-04 Thread Ali Lown

Hi Ben,

 I've read through the JIRA issue and it talks about having two messages
 being sent but one of those should just be the wave message being updated
 though the wave system, and a second email should be sent though the old
 school system using the update to the wave using just the unread blip(s).

I assume this is wrt the original description of
The system would basically send 2 version of the wave. A wave
version, and an email version. The same way we do plain text / html
currently for email. So we would add an email header including a reference
to the current wave, so if the recipient is using a wave-compatible
service, it would know to switch to wave. Otherwise, if it does not
understand the wave header, it would just ignore it and use regular email.
Something like that.

My reading of this is that we send a single email, but with multiple
contents (with different mime-types) in the way plain text/html email
messages work a la RFC 2110 (and friends).

 This will require that the wave system holds a record of the official email
 of the user that signed up to the wave system...
 [..]

Yes it will. Bruno's system involved giving any user signed up to a
wave domain an email automatically (powered by postfix o.e.), which
the user could then choose to have forwarded to wherever they would
prefer.
The advantage of this method over handling it internally, is it allows
whatever form of munging the Wave server admin prefers. It also gives
us the users's 'email' programatically, which works nicely when we
start having it federated, as we don't need to perform cross-server
lookup's of a 'true' email.

Thoughts?

Ali

Re: Coming Months

2015-04-02 Thread Ali Lown

I think another hangout would be a great thing to have.

@Evan: Are you happy to organise this?

Ali

On 1 April 2015 at 16:23, John Blossom jblos...@gmail.com wrote:
 Id be glad to listen in, but since I am not a technical contributor, I will
 try mostly just to monitor.

 All the best,

 John Blossom

 email: jblos...@gmail.com
 phone: 203.293.8511
 google+: google.com/+JohnBlossom

 On Mon, Mar 30, 2015 at 11:26 PM, Evan Hughes ehu...@gmail.com wrote:

 Hey all,

 could we get a Google hangout of the Mentors and contributors to solidify
 the direction which wave will be heading and pointing out what needs to be
 done other than just thoughts on the mailing list.

Re: RC7 Vote Release

2015-04-02 Thread Ali Lown

I have so far tested the SHA digest, GPG signature, and the
KEYS/CHANGES/RELEASE-NOTE files, all are fine.

I intend to test federation tomorrow to check it isn't broken.

Has anyone checked the file copyright notices?

Ali

On 2 April 2015 at 00:31, Michael MacFadden michael.macfad...@gmail.com wrote:
+1

On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk wrote:

lgtm - tested simple install, user registration and local waves.

Dave

On 01/04/15 06:11, Yuri Z wrote:
RC7 is now available for review.

The release version will be: 0.4.0-alpha

Reminder on what included previous release candidates:
RC6 included:
- Bug Fixes

RC5 included:
- Added MongoDB based deltas store and migration tool for deltas migration
from file to mongo based store.

RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

A summary of useful information can be found in RELEASE-NOTES, and a list
of changes in CHANGES at the above artifact distribution url, as well as
being included in the tarballs/zips.(zipballs?)

This vote will close around GMT 8-th April 2015.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks

Re: RC7 Vote Release

2015-04-02 Thread Ali Lown

I did not sign this? Are you verifying with gpg --verify?

Could you provide a snip of 'gpg -k' for what you believe to be myself and
Yuri - and check it against KEYS.

Ali
On 2 Apr 2015 19:27, Christian Grobmeier grobme...@apache.org wrote:

I am confused because Yuri was sending out the release,
but my shell tells me this release was signed by Ali.

Can you clarify who actually signed this?

Otherwise it looks as the sigs would be fine.

RAT brought me this:
http://creadur.apache.org/rat/apache-rat/index.html

*
Summary
---
Generated at: 2015-04-02T20:24:27+02:00
Notes: 5
Binaries: 342
Archives: 0
Standards: 2978

Apache Licensed: 2967
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

11 Unknown Licenses

***

Unapproved licenses:

wave/.classpath
wave/.project
wave/CHANGES
wave/NOTICE.bin
wave/NOTICE.src
wave/README.export-import
wave/README.md
wave/README.profiling
wave/THANKS
wave/jsongadgets.json
wave/tools/eclipse-formatter-style.xml

Except for the eclipse files I think it should be a non-blocker.

Is there a good reason we have the Eclipse files in the release?

Also one more question, why don't we have tag for this RC?

All after all, I think it should work out and give my +1.

I have not tested technically, just formally.

Regards

Christian

On Thu, Apr 2, 2015, at 15:38, Ali Lown wrote:
I have so far tested the SHA digest, GPG signature, and the
KEYS/CHANGES/RELEASE-NOTE files, all are fine.

I intend to test federation tomorrow to check it isn't broken.

Has anyone checked the file copyright notices?

Ali

On 2 April 2015 at 00:31, Michael MacFadden michael.macfad...@gmail.com

wrote:
+1

On 4/1/15, 3:04 PM, Dave Ball w...@glark.co.uk wrote:

lgtm - tested simple install, user registration and local waves.

Dave

On 01/04/15 06:11, Yuri Z wrote:
RC7 is now available for review.

Artifacts can be found here:
*
https://dist.apache.org/repos/dist/dev/incubator/wave/0.7-incubating/

https://dist.apache.org/repos/dist/dev/incubator/wave/0.7-incubating/*
(Remember checksums are from 'gpg --print-md SHA512 $f $f.sha')

The release version will be: 0.4.0-alpha

This is taken from branch
*
https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC7

https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/0.4.0-RC7
*

Reminder on what included previous release candidates:
RC6 included:
- Bug Fixes

RC5 included:
- Added MongoDB based deltas store and migration tool for deltas
migration
from file to mongo based store.

RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

A summary of useful information can be found in RELEASE-NOTES, and a
list
of changes in CHANGES at the above artifact distribution url, as
well as
being included in the tarballs/zips.(zipballs?)

*Action Required:*
*Test the release and make it works on your environment - at least
standard
configurations. Please go over the source files and make sure they
don't
contain anything that cannot be released under Apache Wave due to
legal
issues.*

This vote will close around GMT 8-th April 2015.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks

Re: GSoC 2015 with Apache Wave

2015-03-29 Thread Ali Lown

Hi Roshan,

Okay. I suggest 1700 BST (as GMT is no longer specific enough, due to
DST coming into effect).

Yes, I have access to your proposal on melange. Not sure what (if
anything) I am meant to do with it at the moment...

Ali

On 29 March 2015 at 06:09, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
Hi Ali,

Tomorrow is a bit busy for me, but Monday (30th) would work nicely.

What time would work best for you? Anything from 1100 GMT should work
okay for me.

I am little bit of busy between 1100 GMT to 1530 GMT. But after 1530 GMT
should work for me.

What are your term dates as an undergrad at IIT? Most of the
universities here are on holiday during April, does it work the same
for you?

Yes it is same here.

Do you have access to my proposal in GSOC site?

Cheers,

Roshan

[1] -
https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/roshanrox911/5639274879778816

Ali

On 28 March 2015 at 16:48, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
Yes
I have successfully submitted the proposal.
So can you please proved a subiable time to discuss about the next step
in
the IRC.

Regards
Roshan

On Sat, Mar 28, 2015 at 8:05 AM, Ali Lown a...@lown.me.uk wrote:

Hi Roshan,

The updated proposal document looks great.

I think we are now at the deadline for initial submission?

Ali
On 26 Mar 2015 12:31, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:

Hi Ali,

I submitted the proposal to GSoC website.
We can update it until the deadline.
Can you please provide a suitable time to discuss more about it on
irc.

cheers,

Roshan

On Tue, Mar 24, 2015 at 12:46 PM, Francesco Rossi
f...@schermaontc.com
wrote:

Hello all,
just FYI, our startup (in between italy and china) just got funded
and
we
are actively developing on wave (needless to say how much pressure
I'm
standing right now given the Architecture I've chosen).
while probably we cannot be of direct support to the GSoC, I think
it
might be useful to support the community if we are able to figure
out
an
interesting way to do it.

thank you,
francesco

On 3/23/2015 9:54 PM, Roshan Lakmal wrote:

Hi Ali,

I am free at anytime. If you are online please pork me.

We need to complete the proposal and it needs to be submitted to
the
GSoC
web site before the proposal deadline [1].

I have already register as a student and you also need to register
as
a
mentor [4] for GSoC and connect with Apache Software Foundation
[2]
[3]
before the deadline.

cheers,

Roshan

[1] - https://www.google-melange.com/gsoc/events/google/gsoc2015
[2] - https://community.apache.org/gsoc.html
[3] - https://community.apache.org/guide-to-being-a-mentor.html
[4] -
https://www.google-melange.com/gsoc/profile/register/org_
member/google/gsoc2015

On Tue, Mar 24, 2015 at 7:59 AM, Michael MacFadden
michael.macfad...@gmail.com wrote:

I have been traveling the last few days. I am also happy to help
out
on
this project.

~Michael

On 3/23/15, 5:53 PM, Ali Lown a...@lown.me.uk wrote:

Hi Roshan,

I work (loosely) under GMT - but tend to be more available later
in
the day here (looks like very early morning to you though...)

Deadline this Friday! Okay we need to get on this today/tomorrow
then...

If I suggest 1100-1200 GMT today to work out what we need for
Friday
would that work for you?

Ali

On 23 March 2015 at 16:46, Roshan Lakmal
roshan.2013...@iit.ac.lk

wrote:

Hi Ali,

Nice to here it,

I will catch you on #wiab freenode for further discussion about
the
proposal. My time zone is IST. Can you please suggest me a
suitable
time
for the discussion.

if you can give me a brief introduction about what we can do on
GSoC

then I

can start making my proposal because proposal deadline is Friday
(27th)
[1].

Cheers,

Roshan

[1] -
https://www.google-melange.com/gsoc/events/google/gsoc2015

On Sun, Mar 22, 2015 at 7:40 PM, Ali Lown a...@lown.me.uk
wrote:

Hi Roshan,

I would be happy to be your mentor through GSoC 2015 for Wave.

I think this would be a great opportunity to contribute some
major
work to the existing codebase, culminating in an Android App,
but
there is plenty to be done here to make it all work.

If you get some time, hop onto #wiab on freenode, and we could
discuss
exactly what the project proposal should look like - and how it
would
fit in with your interests.

Ali

On 20 March 2015 at 16:50, Roshan Lakmal
roshan.2013...@iit.ac.lk

wrote:

Hi all,

I stared to read about Wave architecture and protocol.

Can I still

Re: GSoC 2015 with Apache Wave

2015-03-28 Thread Ali Lown

Hi Roshan,

Tomorrow is a bit busy for me, but Monday (30th) would work nicely.

What time would work best for you? Anything from 1100 GMT should work
okay for me.

What are your term dates as an undergrad at IIT? Most of the
universities here are on holiday during April, does it work the same
for you?

Ali

On 28 March 2015 at 16:48, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
 Yes
 I have successfully submitted the proposal.
 So can you please proved a subiable time to discuss about the next step in
 the IRC.

 Regards
 Roshan


 On Sat, Mar 28, 2015 at 8:05 AM, Ali Lown a...@lown.me.uk wrote:

 Hi Roshan,

 The updated proposal document looks great.

 I think we are now at the deadline for initial submission?

 Ali
 On 26 Mar 2015 12:31, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:

  Hi Ali,
 
  I submitted the proposal to  GSoC website.
  We can update it until the deadline.
  Can you please provide a suitable time to discuss more about it on irc.
 
  cheers,
 
  Roshan
 
  On Tue, Mar 24, 2015 at 12:46 PM, Francesco Rossi f...@schermaontc.com
  wrote:
 
   Hello all,
   just FYI, our startup (in between italy and china) just got funded and
 we
   are actively developing on wave (needless to say how much pressure I'm
   standing right now given the Architecture I've chosen).
   while probably we cannot be of direct support to the GSoC, I think it
   might be useful to support the community if we are able to figure out
 an
   interesting way to do it.
  
   thank you,
   francesco
  
  
   On 3/23/2015 9:54 PM, Roshan Lakmal wrote:
  
   Hi Ali,
  
   I am free at anytime. If you are online please pork me.
  
   We need to complete the proposal and it needs to be submitted to the
  GSoC
   web site before the proposal deadline [1].
  
   I have already register as a student and you also need to register as
 a
   mentor [4] for GSoC  and connect with Apache Software Foundation [2]
 [3]
   before the deadline.
  
   cheers,
  
   Roshan
  
   [1] - https://www.google-melange.com/gsoc/events/google/gsoc2015
   [2] - https://community.apache.org/gsoc.html
   [3] - https://community.apache.org/guide-to-being-a-mentor.html
   [4] -
   https://www.google-melange.com/gsoc/profile/register/org_
   member/google/gsoc2015
  
   On Tue, Mar 24, 2015 at 7:59 AM, Michael MacFadden 
   michael.macfad...@gmail.com wrote:
  
I have been traveling the last few days.  I am also happy to help out
  on
   this project.
  
   ~Michael
  
  
  
  
   On 3/23/15, 5:53 PM, Ali Lown a...@lown.me.uk wrote:
  
Hi Roshan,
  
   I work (loosely) under GMT - but tend to be more available later in
   the day here (looks like very early morning to you though...)
  
   Deadline this Friday! Okay we need to get on this today/tomorrow
  then...
  
   If I suggest 1100-1200 GMT today to work out what we need for Friday
   would that work for you?
  
   Ali
  
   On 23 March 2015 at 16:46, Roshan Lakmal roshan.2013...@iit.ac.lk
  
   wrote:
  
   Hi Ali,
  
   Nice to here it,
  
   I will catch you on #wiab freenode for further discussion about the
   proposal. My time zone is IST. Can you please suggest me a suitable
   time
   for the discussion.
  
   if you can give me a brief introduction about what we can do on
 GSoC
  
   then I
  
   can start making my proposal because proposal deadline is Friday
  (27th)
   [1].
  
   Cheers,
  
   Roshan
  
   [1] - https://www.google-melange.com/gsoc/events/google/gsoc2015
  
  
  
   On Sun, Mar 22, 2015 at 7:40 PM, Ali Lown a...@lown.me.uk wrote:
  
Hi Roshan,
  
   I would be happy to be your mentor through GSoC 2015 for Wave.
  
   I think this would be a great opportunity to contribute some major
   work to the existing codebase, culminating in an Android App, but
   there is plenty to be done here to make it all work.
  
   If you get some time, hop onto #wiab on freenode, and we could
  discuss
   exactly what the project proposal should look like - and how it
  would
   fit in with your interests.
  
   Ali
  
   On 20 March 2015 at 16:50, Roshan Lakmal 
 roshan.2013...@iit.ac.lk
  
   wrote:
  
   Hi all,
  
   I stared to read about Wave architecture and protocol.
  
   Can I still continue this project for GSoC 2015 or Is there any
  other
  
   task
  
   that I can contribute.
   Is there anyone to mentor me for GSoC 2015?
  
   Cheers,
  
   Roshan.
  
  
   On Fri, Mar 20, 2015 at 2:54 PM, Pablo Ojanguren 
  pablo...@gmail.com
  
   wrote:
  
   Hi Roshan,
  
   I have re-engineered part of the original GWT webclient and port
  
   core
  
   code
  
   to Android [1]. With the app you can connect to a Wave server and
  
   operate
  
   at Wavelet-level with the original Java code.  A new UI for the
   conversational model could be added on top of it.
  
   As long as original code is Java it mostly works on Android,
  except
   specific GWT parts that have been replaced.
  
   Pablo
  
  
   [1] https://github.com/Zorbel/swell-android
   [2]
  
http

Re: Raise your hands if you would like to participate

2015-03-23 Thread Ali Lown

+1.

One of my main time-sink responsibilities is about to come to an end
(post an AGM later today).

Ali

On 23 March 2015 at 22:22, Vicente J. Ruiz Jurado v...@ourproject.org wrote:
 +0.5 (to be realistic)

Re: GSoC 2015 with Apache Wave

2015-03-23 Thread Ali Lown

Hi Roshan,

I work (loosely) under GMT - but tend to be more available later in
the day here (looks like very early morning to you though...)

Deadline this Friday! Okay we need to get on this today/tomorrow then...

If I suggest 1100-1200 GMT today to work out what we need for Friday
would that work for you?

Ali

On 23 March 2015 at 16:46, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
 Hi Ali,

 Nice to here it,

 I will catch you on #wiab freenode for further discussion about the
 proposal. My time zone is IST. Can you please suggest me a suitable time
 for the discussion.

 if you can give me a brief introduction about what we can do on GSoC then I
 can start making my proposal because proposal deadline is Friday (27th)
 [1].

 Cheers,

 Roshan

 [1] - https://www.google-melange.com/gsoc/events/google/gsoc2015



 On Sun, Mar 22, 2015 at 7:40 PM, Ali Lown a...@lown.me.uk wrote:

 Hi Roshan,

 I would be happy to be your mentor through GSoC 2015 for Wave.

 I think this would be a great opportunity to contribute some major
 work to the existing codebase, culminating in an Android App, but
 there is plenty to be done here to make it all work.

 If you get some time, hop onto #wiab on freenode, and we could discuss
 exactly what the project proposal should look like - and how it would
 fit in with your interests.

 Ali

 On 20 March 2015 at 16:50, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
  Hi all,
 
  I stared to read about Wave architecture and protocol.
 
  Can I still continue this project for GSoC 2015 or Is there any other
 task
  that I can contribute.
  Is there anyone to mentor me for GSoC 2015?
 
  Cheers,
 
  Roshan.
 
 
  On Fri, Mar 20, 2015 at 2:54 PM, Pablo Ojanguren pablo...@gmail.com
 wrote:
 
  Hi Roshan,
 
  I have re-engineered part of the original GWT webclient and port core
 code
  to Android [1]. With the app you can connect to a Wave server and
 operate
  at Wavelet-level with the original Java code.  A new UI for the
  conversational model could be added on top of it.
 
  As long as original code is Java it mostly works on Android, except
  specific GWT parts that have been replaced.
 
  Pablo
 
 
  [1] https://github.com/Zorbel/swell-android
  [2]
  http://p2pvalue.eu/blog/awakening-decentralised-real-time-collaboration
 
 
  2015-03-19 19:53 GMT+01:00 Ali Lown a...@lown.me.uk:
 
   Hi Roshan,
  
   You will probably be interested to read about the Client-Server
   Protocol[1], and its associated protobuf implementation[2], as this is
   what currently defines the 'split' between the WebClient and the
   Server parts of WIAB.
  
   As this protocol works entirely with deltas, you to retrieve the
   'content' for display in your client, you will need to understand the
   Conversation Model[3], which defines how create the familiar Wave
   structure on top of the underlying federateable delta-backed protocol.
   You should be able to re-use most of the model code[4] in your client.
  
   I hope these pointers give you somewhere to start from, feel free to
   ask me any further questions whilst navigating the wave codebase.
  
   Also, whilst not directly applicable - as I started at the federation
   end, you may find my 'rave'[5] codebase useful as a way of wrapping
   your head around the conversation model.
  
   Ali
  
   [1]:
  
 
 https://svn.apache.org/repos/asf/incubator/wave/whitepapers/client-server-protocol/
   [2]: src/org/waveprotocol/box/common/comms/waveclient-rpc.proto
   [3]:
  
 
 https://svn.apache.org/repos/asf/incubator/wave/whitepapers/conversation/
   [4]: src/org/waveprotocol/wave/model/*
   [5]: https://github.com/alown/rave
  
  
   On 19 March 2015 at 18:14, Roshan Lakmal roshan.2013...@iit.ac.lk
  wrote:
Hi Michael,
   
I'm interested to working on Native Android Client [1] because I
 think
  it
will help to boost the Wave project again. In my side this will be a
   great
opportunity understand about the Wave Protocol [2].
   
As a starting point I successfully build the project in my local
  machine
[3].
   
cheers,
   
[1] - https://issues.apache.org/jira/browse/WAVE-400
[2] - http://www.waveprotocol.org/protocol
[3] -
   
  
 
 https://drive.google.com/a/iit.ac.lk/file/d/0B_tP-jjki90QckNsUHBSbnZDaGs/view
   
On Thu, Mar 19, 2015 at 11:40 PM, Roshan Lakmal 
   roshan.2013...@iit.ac.lk
wrote:
   
Hi Michael,
   
I'm interested to working on Native Android Client [1] because I
 think
   it
will help to boost the Wave project again. In my side this will be
 a
   great
opportunity understand about the Wave Protocol [2].
   
As a starting point I successfully build the project in my local
  machine
[3].
   
cheers,
   
[1] - https://issues.apache.org/jira/browse/WAVE-400
[2] - http://www.waveprotocol.org/protocol
[3] -
   
[image: Inline image 1]
   
   
On Thu, Mar 19, 2015 at 9:48 PM, Michael MacFadden 
michael.macfad...@gmail.com wrote:
   
Roshan

Re: Review Request 31837: Fix for caret issues in Chrome+Linux with periods and apostrophes

2015-03-23 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31837/#review77503
---


Do we know where this problem has come from? Did webkit etc. change behaviour 
in an update - if so will this break older clients?


src/org/waveprotocol/wave/client/common/util/SignalKeyLogic.java
https://reviews.apache.org/r/31837/#comment125602

Could you fix the 2 typos in this line prior to commit?
Further, all previous comments in this file are above (and outside) the 
block they are commenting. Could you move this to there?


- Ali Lown


On March 9, 2015, 12:23 a.m., Vicente J. Ruiz Jurado wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/31837/
 ---
 
 (Updated March 9, 2015, 12:23 a.m.)
 
 
 Review request for wave, Andrew Kaplanov, Pablo Ojanguren, and Yuri Zelikov.
 
 
 Repository: wave
 
 
 Description
 ---
 
 This patch fix a issue in Chrome+Linux with periods and apostrophes. For 
 instance if you type:
 
 ...abc...
 
 the result must be
 
 ...abc...| 
 
 (where | is the caret/cursor), but instead you get:
 
 abc|..
 
 and the same whith apostrophes:
 
 abc|''
 
 It seems that this issue is not present in wiab.pro so maybe is interesting 
 the review of akaplanov.
 
 
 Diffs
 -
 
   src/org/waveprotocol/wave/client/common/util/SignalKeyLogic.java 5da169a 
 
 Diff: https://reviews.apache.org/r/31837/diff/
 
 
 Testing
 ---
 
 ant waveharness-superdev tested in FF and Chrome (Linux) and Chorme in Mac.
 
 
 Thanks,
 
 Vicente J. Ruiz Jurado

Re: Wave and Incubation

2015-03-23 Thread Ali Lown

Christian,

This seems to be the age-old Wave problem.

Regarding your last comment, is there any precedent for a project
leaving Apache and returning at future point - it does seem like a
strange set of circumstances would be needed to trigger it?

Ali

On 23 March 2015 at 14:06, Christian Grobmeier grobme...@apache.org wrote:
 Hi,

 if Wave moves out this list, Jira etc will be read only, but available.
 Same for the current source code.

 I agree with 1: in the end Apache is a strong brand and also shows that
 you can rely on a few things.

 However at this point we know the benefits of Apache, but can this
 project also fulfill the requirements of ever becoming a proper Apache
 project? Apache is not here to give protection or brand to a codebase or
 sell something. It's here to work with and help communities.

 The question to ask now is: can Wave have a community? I know the people
 here, and I agree here is a huge kindness around. I appreciate it. But
 what's needed is a community who is also willing to invest some amount
 of time to keep the ball rolling.

 I am fully aware some people here invested time. But a single person can
 not drive an Apache project forward.

 At Apache, everything is around community.

 I ask: can we ever build up a community around Wave which understands
 the principles of Apache, can release code and can keep the project
 alive?

 I am certain about the first two things; I am not so certain about the
 last thing. It's really not much activity here for a long time.

 As others mentioned: Github may lower the barrier. This might be a
 chance to ramp up a community, then return to Apache.

 Cheers

 Christian

 On Tue, Mar 17, 2015, at 18:41, Yuri Z wrote:
 I agree that from the point of view of adding to the source/experimenting
 -
 there's no advantage to staying with Apache. However, there are other
 reasons.
 1. Doing a release will signify that the code base is free of legal
 issues
 and thus encourage adoption of it by other parties, like wiab.pro,
 co-meeting, kune etc...
 2. The Apache Wave site and this mailing list had become a known place to
 look for the Wave related info. There's no other well established place
 like this. The wave-protocol at google code was such place before Apache,
 but it isn't now. Establishing a new home will confuse new and old Wave
 followers.
 3. Migrating issues from Jira and Wiki will take considerable effort,
 again... Probably a lot of info will be just lost.


 On Tue, Mar 17, 2015 at 4:03 PM Tobias Pfeiffer tgpfeif...@web.de
 wrote:

  Hi,
 
  I guess this is my first post to this list, even though I am subscribed
  for a year or so know and following the discussions here.
 
  The technology in Wave seems quite amazing to me (in particular the
  federation part, which hardly any commercial entity would add to their
  product out of a business interest) and I would love to see the project
  flourish, but – just judging from what I saw here on the mailing list –
  I was always wondering if this project is going anywhere from its
  current state. I don't know the project and its history very well, but
  it seems to me that even *if* it was possible to make a release or
  convince Apache that Wave should stay in the incubator, I don't see how
  overall progress should be made.
 
  My feeling is that moving out of Apache to, say, Github (not
  Sourceforge, though...) can't make anything worse, but it *might* lower
  the barrier to collaboration.
 
  Thanks
  Tobias

Re: GSoC 2015 with Apache Wave

2015-03-22 Thread Ali Lown

Hi Roshan,

I would be happy to be your mentor through GSoC 2015 for Wave.

I think this would be a great opportunity to contribute some major
work to the existing codebase, culminating in an Android App, but
there is plenty to be done here to make it all work.

If you get some time, hop onto #wiab on freenode, and we could discuss
exactly what the project proposal should look like - and how it would
fit in with your interests.

Ali

On 20 March 2015 at 16:50, Roshan Lakmal roshan.2013...@iit.ac.lk wrote:
Hi all,

I stared to read about Wave architecture and protocol.

Can I still continue this project for GSoC 2015 or Is there any other task
that I can contribute.
Is there anyone to mentor me for GSoC 2015?

Cheers,

Roshan.

On Fri, Mar 20, 2015 at 2:54 PM, Pablo Ojanguren pablo...@gmail.com wrote:

Hi Roshan,

I have re-engineered part of the original GWT webclient and port core code
to Android [1]. With the app you can connect to a Wave server and operate
at Wavelet-level with the original Java code. A new UI for the
conversational model could be added on top of it.

As long as original code is Java it mostly works on Android, except
specific GWT parts that have been replaced.

Pablo

[1] https://github.com/Zorbel/swell-android
[2]
http://p2pvalue.eu/blog/awakening-decentralised-real-time-collaboration

2015-03-19 19:53 GMT+01:00 Ali Lown a...@lown.me.uk:

Hi Roshan,

You will probably be interested to read about the Client-Server
Protocol[1], and its associated protobuf implementation[2], as this is
what currently defines the 'split' between the WebClient and the
Server parts of WIAB.

As this protocol works entirely with deltas, you to retrieve the
'content' for display in your client, you will need to understand the
Conversation Model[3], which defines how create the familiar Wave
structure on top of the underlying federateable delta-backed protocol.
You should be able to re-use most of the model code[4] in your client.

I hope these pointers give you somewhere to start from, feel free to
ask me any further questions whilst navigating the wave codebase.

Also, whilst not directly applicable - as I started at the federation
end, you may find my 'rave'[5] codebase useful as a way of wrapping
your head around the conversation model.

Ali

[1]:

https://svn.apache.org/repos/asf/incubator/wave/whitepapers/client-server-protocol/
[2]: src/org/waveprotocol/box/common/comms/waveclient-rpc.proto
[3]:

https://svn.apache.org/repos/asf/incubator/wave/whitepapers/conversation/
[4]: src/org/waveprotocol/wave/model/*
[5]: https://github.com/alown/rave

On 19 March 2015 at 18:14, Roshan Lakmal roshan.2013...@iit.ac.lk
wrote:
Hi Michael,

I'm interested to working on Native Android Client [1] because I think
it
will help to boost the Wave project again. In my side this will be a
great
opportunity understand about the Wave Protocol [2].

As a starting point I successfully build the project in my local
machine
[3].

cheers,

[1] - https://issues.apache.org/jira/browse/WAVE-400
[2] - http://www.waveprotocol.org/protocol
[3] -

https://drive.google.com/a/iit.ac.lk/file/d/0B_tP-jjki90QckNsUHBSbnZDaGs/view

On Thu, Mar 19, 2015 at 11:40 PM, Roshan Lakmal
roshan.2013...@iit.ac.lk
wrote:

Hi Michael,

As a starting point I successfully build the project in my local
machine
[3].

cheers,

[1] - https://issues.apache.org/jira/browse/WAVE-400
[2] - http://www.waveprotocol.org/protocol
[3] -

[image: Inline image 1]

On Thu, Mar 19, 2015 at 9:48 PM, Michael MacFadden
michael.macfad...@gmail.com wrote:

Roshan,

There are plenty of tasks within Wave that could be worked on. Do
you
have any particular interest? UI, Backend work, etc.? I am sure we
could
find you something.

~Michael

On 3/19/15, 5:33 AM, Roshan Lakmal roshan.2013...@iit.ac.lk
wrote:

Hi all,

I'm Roshan Lakmal, an Undergraduate student from Informatics
Institute of
Technology - Sri Lanka. Last year I participated Gsoc for Apache
Software
Foundation (Apache SIS) [1].

For this summer I would like to work with Apache Wave for GSoC 2015.
Is
there any suitable task available for me.

[1] -

http://www.google-melange.com/gsoc/project/details/google/gsoc2014/roshanrox911/5668600916475904

Cheers,

Roshan

Re: Incubator PMC/Board report for Dec 2014 ([ppmc])

2014-12-01 Thread Ali Lown

Yuri,

That sounds like a great plan.

I would love to help, but am swamped this week.

Thanks,
Ali

On 1 December 2014 at 14:32, Yuri Z vega...@gmail.com wrote:
 Hi
 There wasn't a lot of activity recently, but I think we still need to do
 the release. I ll merge some changes that were already approved in the
 Review Board and post a new release candidate for reviewing/voting.
 On Mon Dec 01 2014 at 4:15:29 PM Marvin no-re...@apache.org wrote:



 Dear podling,

 This email was sent by an automated system on behalf of the Apache
 Incubator PMC.
 It is an initial reminder to give you plenty of time to prepare your
 quarterly
 board report.

 The board meeting is scheduled for Wed, 17 December 2014, 10:30 am PST.
 The report
 for your podling will form a part of the Incubator PMC report. The
 Incubator PMC
 requires your report to be submitted 2 weeks before the board meeting, to
 allow
 sufficient time for review and submission (Wed, Dec 3rd).

 Please submit your report with sufficient time to allow the incubator PMC,
 and
 subsequently board members to review and digest. Again, the very latest you
 should submit your report is 2 weeks prior to the board meeting.

 Thanks,

 The Apache Incubator PMC

 Submitting your Report
 --

 Your report should contain the following:

  * Your project name
  * A brief description of your project, which assumes no knowledge of the
 project
or necessarily of its field
  * A list of the three most important issues to address in the move towards
graduation.
  * Any issues that the Incubator PMC or ASF Board might wish/need to be
 aware of
  * How has the community developed since the last report
  * How has the project developed since the last report.

 This should be appended to the Incubator Wiki page at:

   http://wiki.apache.org/incubator/December2014

 Note: This is manually populated. You may need to wait a little before
 this page
   is created from a template.

 Mentors
 ---
 Mentors should review reports for their project(s) and sign them off on the
 Incubator wiki page. Signing off reports shows that you are following the
 project - projects that are not signed may raise alarms for the Incubator
 PMC.

 Incubator PMC

Re: JSON editing and move conflicts

2014-10-18 Thread Ali Lown

Hi Joseph,

I think that the only sensible option is to delegate the resolution of
this action in the case of conflict back into the application, so some
sort of extension of (4) that allows some arbitrary lambda expression
to be passed as the onconflict method. (Depending on the situation,
they might want to 'merge' the two items (if possible), rather than
moving one into a 'backup' location).

This does complicate the OT type, and does make it more difficult to
analyse how long certain actions will take to resolve though...

How does this sound?

Ali

On 19 October 2014 00:33, Joseph Gentle jose...@gmail.com wrote:
 I'm (finally!) taking a serious look at making a better version of the
 JSON OT type. I'm cross-posting this here because it directly effects
 sharejs  derby users, and I think any serious rewrite of wave will
 use something like this at the top level to store waves.

 I have two questions that I would love some input on from the wider community.

 We want to add a 'move' action which will let you transplant arbitrary
 parts of the JSON structure to other places in the tree. This is
 really useful if, for example, you want a hierarchal to-do list, a
 tree of source files for your IDE or a tree of blips.

 But I can't figure out what should happen if two users move different
 objects to the same place in the tree at the same time.

 1. The simplest option is to simply delete one of them. This is really
 convenient from a programming pov, but I think that would be the worst
 kind of surprise. {x:1, y:2} - {z:2}
 2. We could try and make one of the moves fail - {x:1, y:2} - {x:1,
 z:2}. On the face of it this sounds great, but this is a cascading
 failure. If (locally) I move x-z then insert some new data at x, what
 happens to the new data? Does the new data get deleted? Does x get
 deleted? I can't think of a good answer here which isn't just
 dangerous in a more complicated way. Making both the moves fail has
 the same problem.
 3. We could pick a winner and then move the loser to some special
 lostfound bucket or something. So, {x:1, y:2} - {__recovered_z:1,
 z:2} But that could play havoc with data bindings, and we'd have to
 introduce some reserved keys. The other way to do this is to introduce
 a new top-level structure which contains the data, so it'd be
 {data:{x:1, y:2}} - {data:{z:2}, lost:[{z:1}]}.
 4. Or we could add the backup location into the move operation itself,
 so whoever's building on top of this API can make the choice. (They
 can make a better decision because they know what the data structure
 looks like). So instead of (move x-z) we'd have (move x-z,
 onconflict:(move x-__x)) or something.

 Are there any other choices I'm missing here? I'm edging toward option
 4, although it might increase the type's complexity by 50% unless I
 can think of a clean way to do it.

 Thanks
 -J

Re: Incubator PMC/Board report for Sep 2014 ([ppmc])

2014-08-29 Thread Ali Lown

I have extended the Wave report with a few more details.

Feel free to change/add more.

Ali

On 29 August 2014 11:16, Yuri Z vega...@gmail.com wrote:
 I updated the Wiki. Please feel free to update/add details.


 On Wed, Aug 27, 2014 at 5:20 PM, Christian Grobmeier grobme...@gmail.com
 wrote:

 Any takers?

 Regards,
 Christian

 --
   Christian Grobmeier
   grobme...@gmail.com

 On Wed, Aug 27, 2014, at 04:15 PM, Marvin wrote:
 
 
  Dear podling,
 
  This email was sent by an automated system on behalf of the Apache
  Incubator PMC.
  It is an initial reminder to give you plenty of time to prepare your
  quarterly
  board report.
 
  The board meeting is scheduled for Wed, 17 September 2014, 10:30:30:00
  PST. The report
  for your podling will form a part of the Incubator PMC report. The
  Incubator PMC
  requires your report to be submitted 2 weeks before the board meeting, to
  allow
  sufficient time for review and submission (Wed, Sep 3rd).
 
  Please submit your report with sufficient time to allow the incubator
  PMC, and
  subsequently board members to review and digest. Again, the very latest
  you
  should submit your report is 2 weeks prior to the board meeting.
 
  Thanks,
 
  The Apache Incubator PMC
 
  Submitting your Report
  --
 
  Your report should contain the following:
 
   * Your project name
   * A brief description of your project, which assumes no knowledge of the
   project
 or necessarily of its field
   * A list of the three most important issues to address in the move
   towards
 graduation.
   * Any issues that the Incubator PMC or ASF Board might wish/need to be
   aware of
   * How has the community developed since the last report
   * How has the project developed since the last report.
 
  This should be appended to the Incubator Wiki page at:
 
http://wiki.apache.org/incubator/September2014
 
  Note: This manually populated. You may need to wait a little before this
  page is
created from a template.
 
  Mentors
  ---
  Mentors should review reports for their project(s) and sign them off on
  the
  Incubator wiki page. Signing off reports shows that you are following the
  project - projects that are not signed may raise alarms for the Incubator
  PMC.
 
  Incubator PMC

Re: Review Request 20371: Deltas migration tool from file to mongodb store

2014-08-25 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20371/#review51393
---

Ship it!


LGTM.

- Ali Lown


On July 13, 2014, 9:43 a.m., Pablo Ojanguren wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/20371/
 ---
 
 (Updated July 13, 2014, 9:43 a.m.)
 
 
 Review request for wave, Ali Lown, Vicente J. Ruiz Jurado, and Yuri Zelikov.
 
 
 Bugs: WAVE-412
 https://issues.apache.org/jira/browse/WAVE-412
 
 
 Repository: wave
 
 
 Description
 ---
 
 Support to live installations of Wave (and its flavors) is needed if they 
 decide move from file to mongodb storage for deltas. So this is a tool to 
 move data from stores.
 
 Additionally, MongoDB configuration has been moved from the separated 
 property file (src/org/waveprotocol/box/server/persistence/mongodb) to the 
 server.config file. If no property is set, default values are taken. See 
 CoreSettings.java for more info.
 
 
 Diffs
 -
 
   run-data-migration.sh PRE-CREATION 
   server-config.xml 4f1d94fa7c5250aa8bc1e5bc471b0d12b3026697 
   server.config.example f3feba04a1e8a6cfa7a08911d1ddb94eedbcf98c 
   src/org/waveprotocol/box/server/CoreSettings.java 
 0a6f3fd50941a112acc50031c1220f3beb1dbca9 
   src/org/waveprotocol/box/server/DataMigrationTool.java PRE-CREATION 
   src/org/waveprotocol/box/server/persistence/PersistenceModule.java 
 14c645365604d75703dea781ad159132fcd3b45f 
   src/org/waveprotocol/box/server/persistence/migration/DeltaMigrator.java 
 PRE-CREATION 
   src/org/waveprotocol/box/server/persistence/mongodb/MongoDbProvider.java 
 4e290779444ac6d2a28e4573eef7fa0dd3895105 
   src/org/waveprotocol/box/server/persistence/mongodb/mongodb.properties 
 0f95fa4842cd726aca042366531c91aa0a651d47 
   test/org/waveprotocol/box/server/persistence/mongodb/AccountStoreTest.java 
 df79f791e7462c233af0edecd86d01457dbd6227 
   
 test/org/waveprotocol/box/server/persistence/mongodb/AttachmentStoreTest.java 
 46dd70b8aab90d90baa91c9643cbb4586051dc65 
   test/org/waveprotocol/box/server/persistence/mongodb/CertPathStoreTest.java 
 62bcd74478269983a639ce50121da7703f38c336 
 
 Diff: https://reviews.apache.org/r/20371/diff/
 
 
 Testing
 ---
 
 Basic manual test: all waves (12) in a local server initially stored in file 
 where migrated succesfully.
 
 
 Thanks,
 
 Pablo Ojanguren

Re: Review Request 25020: Gadget insertion position on cursor

2014-08-25 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25020/#review51394
---

Ship it!


LGTM.

- Ali Lown


On Aug. 25, 2014, 11:25 a.m., Antonio Tenorio-Fornés wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/25020/
 ---
 
 (Updated Aug. 25, 2014, 11:25 a.m.)
 
 
 Review request for wave and Pablo Ojanguren.
 
 
 Bugs: WAVE-269
 https://issues.apache.org/jira/browse/WAVE-269
 
 
 Repository: wave
 
 
 Description
 ---
 
 Resolves bug WAVE-269. Gadgets are now inserted in the position of the cursor
 
 
 Diffs
 -
 
   src/org/waveprotocol/wave/client/wavepanel/impl/toolbar/EditToolbar.java 
 7abe368ba5119f42491f147d8a18e5f32ea9d3df 
 
 Diff: https://reviews.apache.org/r/25020/diff/
 
 
 Testing
 ---
 
 - Write several lines text in a wave conversation.
 - move cursor to an intermediate character of an intermediate line of the 
 text.
 - The gadget is added at cursor position
 
 
 Thanks,
 
 Antonio Tenorio-Fornés

Re: Review Request 25021: Fixes Delta signature verification fail with wildcard certificates

2014-08-25 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/25021/#review51395
---

Ship it!


LGTM once you fix the trailing whitespace.

(I had been testing federation without setting up verification, so I hadn't 
spotted this issue).


src/org/waveprotocol/wave/crypto/WaveSignatureVerifier.java
https://reviews.apache.org/r/25021/#comment89708

Could we lose these trailing spaces?


- Ali Lown


On Aug. 25, 2014, 11:42 a.m., Pablo Ojanguren wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/25021/
 ---
 
 (Updated Aug. 25, 2014, 11:42 a.m.)
 
 
 Review request for wave, Ali Lown, Vicente J. Ruiz Jurado, and Yuri Zelikov.
 
 
 Bugs: WAVE-416
 https://issues.apache.org/jira/browse/WAVE-416
 
 
 Repository: wave
 
 
 Description
 ---
 
 
 In an federated environment, when a remote delta is received in A from host 
 B, signature verification fails if B cert is a wildcard certificate.
 
 
 Diffs
 -
 
   src/org/waveprotocol/wave/crypto/WaveSignatureVerifier.java 
 0b4238ec982484450d34fb54aeb0dce2c901289e 
 
 Diff: https://reviews.apache.org/r/25021/diff/
 
 
 Testing
 ---
 
 In our federation test environment both servers are in the same domain, so 
 the problem arose: federation-1.p2pvalue.eu and federation-2.p2pvalue.eu 
 After server patch was applied the federation works good.
 
 
 Thanks,
 
 Pablo Ojanguren

Re: Third party dependencies from http://wave.alown.co.uk fail the build

2014-08-25 Thread Ali Lown

Ah.

I deleted the DNS CNAME record for this domain, hence it fails. (I was
doing a clean out of my DNS records, and forgot that this one was
used.)

I have been able to source the tinder and whack jars from elsewhere,
and have pushed the fix in cab299e44b5a40498268ecae463f8e330fae6897

Not sure about the origins of websocket.jar (is this a really early
version of Java-Websocket?)

Maybe it would be easier if we just include the single source file in
the our repository? (MIT license, can we do that?)

Ali

On 24 August 2014 23:48, Ali Lown a...@lown.me.uk wrote:
 Sure.

 I am going to bed now (as it is about to hit midnight here), so I will
 take a look in the morning...

 Can we put them on an apache dist server somewhere?

 Ali

 On 24 August 2014 23:46, Yuri Z vega...@gmail.com wrote:
 It looks like we have some third party dependencies server from
 http://wave.alown.co.uk that are not reachable and fail the Jenkins build.
 @Ali, can you take a look? Ideally, would be to replace the links to use
 maven-central or some trusted third party...
 https://builds.apache.org/view/S-Z/view/Wave/job/wave-small_tests/2088/console

Re: Third party dependencies from http://wave.alown.co.uk fail the build

2014-08-25 Thread Ali Lown

I would expect LICENSE/NOTICE to need to be updated to include it.

@Christian: Can we do this for the single file that makes up websocket.jar?

Ali

On 25 August 2014 15:24, Yuri Z vega...@gmail.com wrote:
 I think we can, does it means we need to update LICENSE/NOTES?


 On Mon, Aug 25, 2014 at 4:52 PM, Ali Lown a...@lown.me.uk wrote:

 Not sure about the origins of websocket.jar (is this a really early
 version of Java-Websocket?)

 Maybe it would be easier if we just include the single source file in
 the our repository? (MIT license, can we do that?)

 Ali

 On 24 August 2014 23:48, Ali Lown a...@lown.me.uk wrote:
  Sure.
 
  I am going to bed now (as it is about to hit midnight here), so I will
  take a look in the morning...
 
  Can we put them on an apache dist server somewhere?
 
  Ali
 
  On 24 August 2014 23:46, Yuri Z vega...@gmail.com wrote:
  It looks like we have some third party dependencies server from
  http://wave.alown.co.uk that are not reachable and fail the Jenkins
  build.
  @Ali, can you take a look? Ideally, would be to replace the links to
  use
  maven-central or some trusted third party...
 
  https://builds.apache.org/view/S-Z/view/Wave/job/wave-small_tests/2088/console

Re: Third party dependencies from http://wave.alown.co.uk fail the build

2014-08-25 Thread Ali Lown

Done in 10db75a.

On 25 August 2014 18:54, Yuri Z vega...@gmail.com wrote:
 Looks like we actually don't use this dependency anymore. I removed the jar
 from Git.
 @Ali, can you please commit\push the updates for two other jars?


 On Mon, Aug 25, 2014 at 6:25 PM, Christian Grobmeier grobme...@gmail.com
 wrote:

 MIT should be no problem actually.

 You may want to check that page:
 http://www.apache.org/legal/resolved.html#category-a

 On Mon, Aug 25, 2014 at 5:05 PM, Yuri Z vega...@gmail.com wrote:
  I guess MIT license should allow this, right?
 
 
  On Mon, Aug 25, 2014 at 5:38 PM, Upayavira u...@odoko.co.uk wrote:
 
 
 
  On Mon, Aug 25, 2014, at 03:32 PM, Ali Lown wrote:
   I would expect LICENSE/NOTICE to need to be updated to include it.
  
   @Christian: Can we do this for the single file that makes up
   websocket.jar?
 
  We can place a source file into source control, so long as we can comply
  with the terms of its license (note, some licenses mandate inclusion in
  a binary form).
 
  Upayavira
 



 --
 http://www.grobmeier.de
 https://www.timeandbill.de

Re: Third party dependencies from http://wave.alown.co.uk fail the build

2014-08-25 Thread Ali Lown

I am looking in to it. The failure that can be seen there is from
tinder requiring stringprep which was not included.

I have upgraded to tinder 1.2.2 locally which uses libidn instead, and
am testing that.

On 25 August 2014 20:46, Yuri Z vega...@gmail.com wrote:
 The tests still fail -
 https://builds.apache.org/view/S-Z/view/Wave/job/wave-small_tests/2092/.
 Probably the jars are somewhat different from those that were on
 http://wave.alown.co.uk


 On Mon, Aug 25, 2014 at 9:34 PM, Yuri Z vega...@gmail.com wrote:

 Looks like we do need xmpp.jar at least for runtime, not sure about
 whack.jar
 The websocket.jar looks is not used as i was able to run the server and
 tests without it. I guess we need to return the dependency on xmpp and
 whack, but preferably to use public third party repositories.

 On Mon, Aug 25, 2014 at 8:59 PM, Ali Lown a...@lown.me.uk wrote:

 Done in 10db75a.

 On 25 August 2014 18:54, Yuri Z vega...@gmail.com wrote:
  Looks like we actually don't use this dependency anymore. I removed the
 jar
  from Git.
  @Ali, can you please commit\push the updates for two other jars?
 
 
  On Mon, Aug 25, 2014 at 6:25 PM, Christian Grobmeier 
 grobme...@gmail.com
  wrote:
 
  MIT should be no problem actually.
 
  You may want to check that page:
  http://www.apache.org/legal/resolved.html#category-a
 
  On Mon, Aug 25, 2014 at 5:05 PM, Yuri Z vega...@gmail.com wrote:
   I guess MIT license should allow this, right?
  
  
   On Mon, Aug 25, 2014 at 5:38 PM, Upayavira u...@odoko.co.uk wrote:
  
  
  
   On Mon, Aug 25, 2014, at 03:32 PM, Ali Lown wrote:
I would expect LICENSE/NOTICE to need to be updated to include it.
   
@Christian: Can we do this for the single file that makes up
websocket.jar?
  
   We can place a source file into source control, so long as we can
 comply
   with the terms of its license (note, some licenses mandate
 inclusion in
   a binary form).
  
   Upayavira
  
 
 
 
  --
  http://www.grobmeier.de
  https://www.timeandbill.de

Re: Fix to issue https://issues.apache.org/jira/browse/WAVE-413.

2014-08-24 Thread Ali Lown

Done.

Can we find some automated way to get pull requests emailed back to the list?

Ali

On 24 August 2014 23:30, Yuri Z vega...@gmail.com wrote:
 Please review https://github.com/apache/incubator-wave/pull/6

Re: Please review the Pull Request - Full text search

2014-08-21 Thread Ali Lown

Yuri,

I shall take a look at this tomorrow morning.

(We should probably decide whether we are going to use PR as the
review procedure instead of Review Board?)

Ali

On 21 August 2014 23:31, Yuri Z vega...@gmail.com wrote:
 Hi
 I made some changes to the original full text search with Solr patch by
 Frank Ren and created a pull request on GitHub -
 https://github.com/apache/incubator-wave/pull/4
 Please review.
 Hopefully we will be able to do it fast so the full text search will be
 included in the release.

Re: Please review the Pull Request - Full text search

2014-08-21 Thread Ali Lown

My concern with PRs, is that when it has lots of commits in, the
resultant merge destroys the history.

I tried to git-bisect the other day, and kept having to skip through
non-compiling commits that were doing partial work, that had been
pulled in from a PR.

Perhaps, PRs but only if the work has been pre-squashed for submission?

Ali

On 21 August 2014 23:38, Yuri Z vega...@gmail.com wrote:
 Unless there's an Apache policy against that, I think we should prefer
 GitHub pull requests.


 On Fri, Aug 22, 2014 at 1:34 AM, Ali Lown a...@lown.me.uk wrote:

 Yuri,

 I shall take a look at this tomorrow morning.

 (We should probably decide whether we are going to use PR as the
 review procedure instead of Review Board?)

 Ali

 On 21 August 2014 23:31, Yuri Z vega...@gmail.com wrote:
  Hi
  I made some changes to the original full text search with Solr patch by
  Frank Ren and created a pull request on GitHub -
  https://github.com/apache/incubator-wave/pull/4
  Please review.
  Hopefully we will be able to do it fast so the full text search will be
  included in the release.

Re: [VOTE] Release Wave 0.5 based on RC5

2014-08-12 Thread Ali Lown

http://www.apache.org/dev/licensing-howto.html

Seems to suggest extending both license and notice as required?

Ali
On 12 Aug 2014 05:38, Christian Grobmeier grobme...@gmail.com wrote:

 Hi

 sorry for the delay!

 I meant: the LICENSE file should only contain the Apache license
 used by this project. The NOTICE file can contain references to
 licenses of other libs used by the project.
 So far i haven't seen LICENSE files containing all licenses of
 all dependencies et al

 Kind regards,
 Christian

 On 8 Aug 2014, at 10:35, Yuri Z wrote:

  Hi Christian
  You mentioned that: The LICENSE file in the bin dist contains additional
  lines of text which should not be there. This is what belongs to a NOTICE
  file.
  Can you please explain?
 
 
  On Thu, Jul 24, 2014 at 1:03 PM, Christian Grobmeier 
 grobme...@gmail.com
  wrote:
 
  Thats good then, thanks for letting me know.
 
  On 23 Jul 2014, at 22:59, Ali Lown wrote:
 
  The thumnbail_patterns files were fixed by Vicente back in December.
  The curremt files are from the Humanity Project, a note was added to
  THANKS
  to Tango (who are behind them).
 
  The files themselves are public domain.
 
  Ali
  On 23 Jul 2014 21:37, Yuri Z vega...@gmail.com wrote:
 
  Thanks for pointing out these issues Christian.
  Basically, these files are generated, but since we dont want to make
 the
  project to depend on protobuff library, they are part of the source.
  Anyway, i think we can add the headers.
  Regarding images in thumbnail - i think we sorted out this issue.
  I ll make fixes and create rc6.
  On Jul 23, 2014 10:57 PM, Christian Grobmeier grobme...@gmail.com
  wrote:
 
  Unfortunately I found some issues which should be solved before we
 can
  release:
 
  I found these file without headers. Many of them are generated, but I
  found
  others in the same folders which were generated too and had a license
  header.
  So I think we can apply them here as well:
 
  WaveClientRpc.java
  ProfilesProto
  SearchProto
  ProtoDeltaStoreData
  Rpc
  Extensions
  ClientServer
  Diff
  FederationErrorProto
  Proto
 
  Others:
 
  artifact-sign.sh
  eclipse-formatter-style.xml
 
  What are these files in thumbnails_patterns? They look binary, do we
  have
  the permission to distribute them?
 
  The NOTICE file needs an update to the current year - speaking of the
  src
  dist, it looks correct (?) for the bin dist.
 
  The LICENSE file in the bin dist contains additional lines of text
  which
  should not be there. This is what belongs to a NOTICE file.
 
  Basically my main blocker is the header license.
 
  I don't know why files like LICENSE etc are different from the
  packages.
  They should be the same.
 
  I know its a lot of work, but can we fix these?
 
  Probably there are other issues, but I hope you'll see my point.
 
  Thanks!
  Christian
 
 
  On 19 Jul 2014, at 19:12, Yuri Z wrote:
 
  RC5 is now available for review.
 
  Major changes in RC5:
  - Added MongoDB based deltas store and migration tool for deltas
  migration
  from file to mongo based store.
 
  - Added client/server profiling.
  - Added Atmosphere framework as replacement of Socket.IO.
  - Added alternative - Gmail style initials avatars.
  - Decreased number of permutations in dev compilation and added GWT
  superdev mode.
  - Upgraded the server to Jetty 9.1.1.
  - Added JDK 7 compatibility.
 
  Reminder: Major changes in RC4 included:
  - More licensing fixes
  - Federation works
  - New and updated translations
  - And more...
 
  Artifacts can be found here:
  *
  https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
  
  https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
  *
  (Remember checksums are from 'gpg --print-md SHA512 $f  $f.sha')
 
  This is taken from branch
  *https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5
  https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5*
 
  A summary of useful information can be found in RELEASE-NOTES, and a
  list of changes in CHANGES at the above artifact distribution url,
 as
  well as being included in the tarballs/zips.(zipballs?)
 
  *Action Required:*
  *It is crucial to test these on some other machines and provide
  **feedback.*
 
  This vote will close around  GMT 26-th July 2014.
 
  [ ] +1   Release it!
  [ ] +0   OK, but...
  [ ] -0OK, but you really should fix
  [ ] -1Definitely not because...
 
  Thanks.
 
 
 
  ---
  http://www.grobmeier.de
  The Zen Programmer: http://bit.ly/12lC6DL
  @grobmeier
  GPG: 0xA5CC90DB
 
 
 
 
  ---
  http://www.grobmeier.de
  The Zen Programmer: http://bit.ly/12lC6DL
  @grobmeier
  GPG: 0xA5CC90DB
 


 ---
 http://www.grobmeier.de
 The Zen Programmer: http://bit.ly/12lC6DL
 @grobmeier
 GPG: 0xA5CC90DB

Re: [VOTE] Release Wave 0.5 based on RC5

2014-08-11 Thread Ali Lown

Yuri,

Because the two license files serve the same purpose for two different
artifacts.

The additional libraries listed in LICENSE.bin are only pulled in for
a binary release (they are the libraries in third_party/ that required
a mention in LICENSE).

For a true source artifact, only the libraries listed in LICENSE.src
are included as part of the distributed file.

Ali

P.S. Sorry about not responding sooner.

On 9 August 2014 12:59, Yuri Z vega...@gmail.com wrote:
 @Ali Why do we have additional third party libraries info in LICENSE.bin
 but not in LICENSE.src?


 On Fri, Aug 8, 2014 at 11:35 AM, Yuri Z vega...@gmail.com wrote:

 Hi Christian
 You mentioned that: The LICENSE file in the bin dist contains additional
 lines of text which should not be there. This is what belongs to a NOTICE
 file.
 Can you please explain?


 On Thu, Jul 24, 2014 at 1:03 PM, Christian Grobmeier grobme...@gmail.com
 wrote:

 Thats good then, thanks for letting me know.

 On 23 Jul 2014, at 22:59, Ali Lown wrote:

  The thumnbail_patterns files were fixed by Vicente back in December.
  The curremt files are from the Humanity Project, a note was added to
 THANKS
  to Tango (who are behind them).
 
  The files themselves are public domain.
 
  Ali
  On 23 Jul 2014 21:37, Yuri Z vega...@gmail.com wrote:
 
  Thanks for pointing out these issues Christian.
  Basically, these files are generated, but since we dont want to make
 the
  project to depend on protobuff library, they are part of the source.
  Anyway, i think we can add the headers.
  Regarding images in thumbnail - i think we sorted out this issue.
  I ll make fixes and create rc6.
  On Jul 23, 2014 10:57 PM, Christian Grobmeier grobme...@gmail.com
  wrote:
 
  Unfortunately I found some issues which should be solved before we can
  release:
 
  I found these file without headers. Many of them are generated, but I
  found
  others in the same folders which were generated too and had a license
  header.
  So I think we can apply them here as well:
 
  WaveClientRpc.java
  ProfilesProto
  SearchProto
  ProtoDeltaStoreData
  Rpc
  Extensions
  ClientServer
  Diff
  FederationErrorProto
  Proto
 
  Others:
 
  artifact-sign.sh
  eclipse-formatter-style.xml
 
  What are these files in thumbnails_patterns? They look binary, do we
 have
  the permission to distribute them?
 
  The NOTICE file needs an update to the current year - speaking of the
 src
  dist, it looks correct (?) for the bin dist.
 
  The LICENSE file in the bin dist contains additional lines of text
 which
  should not be there. This is what belongs to a NOTICE file.
 
  Basically my main blocker is the header license.
 
  I don't know why files like LICENSE etc are different from the
 packages.
  They should be the same.
 
  I know its a lot of work, but can we fix these?
 
  Probably there are other issues, but I hope you'll see my point.
 
  Thanks!
  Christian
 
 
  On 19 Jul 2014, at 19:12, Yuri Z wrote:
 
  RC5 is now available for review.
 
  Major changes in RC5:
  - Added MongoDB based deltas store and migration tool for deltas
  migration
  from file to mongo based store.
 
  - Added client/server profiling.
  - Added Atmosphere framework as replacement of Socket.IO.
  - Added alternative - Gmail style initials avatars.
  - Decreased number of permutations in dev compilation and added GWT
  superdev mode.
  - Upgraded the server to Jetty 9.1.1.
  - Added JDK 7 compatibility.
 
  Reminder: Major changes in RC4 included:
  - More licensing fixes
  - Federation works
  - New and updated translations
  - And more...
 
  Artifacts can be found here:
  *
 https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
  
 https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
  *
  (Remember checksums are from 'gpg --print-md SHA512 $f  $f.sha')
 
  This is taken from branch
  *https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5
  https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5*
 
  A summary of useful information can be found in RELEASE-NOTES, and a
  list of changes in CHANGES at the above artifact distribution url, as
  well as being included in the tarballs/zips.(zipballs?)
 
  *Action Required:*
  *It is crucial to test these on some other machines and provide
  **feedback.*
 
  This vote will close around  GMT 26-th July 2014.
 
  [ ] +1   Release it!
  [ ] +0   OK, but...
  [ ] -0OK, but you really should fix
  [ ] -1Definitely not because...
 
  Thanks.
 
 
 
  ---
  http://www.grobmeier.de
  The Zen Programmer: http://bit.ly/12lC6DL
  @grobmeier
  GPG: 0xA5CC90DB
 
 


 ---
 http://www.grobmeier.de
 The Zen Programmer: http://bit.ly/12lC6DL
 @grobmeier
 GPG: 0xA5CC90DB

Re: Potential Bugs and Release Date

2014-08-04 Thread Ali Lown

Hi Ronny,

Thanks for raising this again. I had lost your previous email in an inbox purge.
I have made a bug for this (WAVE-413), so that we can track progress
on this bug.

As for the data loss, could you raise this as a bug too. Is this only
on the windows server as well?

Thanks,
Ali

On 4 August 2014 18:21, Ronny Roscher ronny.rosc...@gmail.com wrote:
 Hey guys,

 I have a project where WIAB would be the perfect communication platform,
 but before I can actually use it, I have to wait till a few problems I have
 with RC4/RC5 are fixed. Therefore I would like to ask if those bugs are
 already knows or fixed and when the next version will be release.

 The issues I noticed are the following:


- The inability to access the RC5 server from outside localhost when it
running on a windows machine, which I detected last month, the discussion
on this issues stoped after someone had suggested where the bug may lie
- With RC4 I loose all data after every restart of the server (Alt+F4 in
the commandline or server restart, maybe I have to exit differntly?), I can
still see the waves in the list, but when I click on them the programm
crashes and I get the following error (1), the only thing I can do
afterwards is click refresh but its the same every time; to me it looks
like the deltas are not saved correctly to the hdd, even though I can see
them in the folder, maybe they can't be associated correctly with the links
in the list? anyways the config settings can be found here (2)

 Also I have some questions concerning usability and functionality compared
 to the original implementation of Google:

- One of the most useful features of GoogleWave was, that you could
start a subconversation at every place in the text, I think the shortcut
was Ctrl+Enter at the cursor position or something along those lines. I
didn't find such a shortcut with WIAB. When I click Reply on a wave the
first time such a subconversation is started behinf the title, and every
further try adds a new concersation at the end of the wave. Since you can
already create such subconversation at 2 different places, so I don't think
it would be hard to make it possible to do it everywhere, or am I wrong?
- The second issues is connected with the subconcersations as well. It
would be nice if the collapse status of each of them could be saved. The
reason for the most of the time is to discuss on the improvement of some
part of the main document, but when all are expanded each time you open the
wave, then you can't read the actual document but have to close all the
subconversations first which makes the feature very unconfortable.


 Anyways, thank you all for your effort to bringing GoogleWave back alive.
 It was a great communication platform and shame it was abandoned.

 Best regards,
 Ronny

 (1)
 Stack trace:
 Token: 1407169782249
 Class$Fif: [INVALID_OPERATION] Channel Exception
 Unknown.lI (Unknown source:0)
 Unknown.tI (Unknown source:0)
 Unknown.zI (Unknown source:0)
 Unknown.s_c (Unknown source:0)
 Unknown.qdf (Unknown source:0)
 Unknown.mdf (Unknown source:0)
 Unknown.Gdf (Unknown source:0)
 Caused by: Token: 1407169782250
 [INVALID_OPERATION] Channel Exception
 Unknown.lI (Unknown source:0)
 Unknown.Hif (Unknown source:0)
 Unknown.qdf (Unknown source:0)
 Unknown.mdf (Unknown source:0)
 Unknown.Gdf (Unknown source:0)
 Unknown.Lef (Unknown source:0)
 Unknown.Xef (Unknown source:0)
 Caused by: Token: 1407169782251
 Exception in view channel, state [ViewChannel id: ch3 waveId: [WaveId
 wiab.net/w+j0_BD8uz1_A] state: CONNECTED]
 Unknown.lI (Unknown source:0)
 Unknown.Bif (Unknown source:0)
 Unknown.Lef (Unknown source:0)
 Unknown.Xef (Unknown source:0)
 Unknown.Yef (Unknown source:0)
 Unknown.Gtc (Unknown source:0)
 Unknown.Jtc (Unknown source:0)
 Caused by: Token: 1407169782251
 Operation channel failed on ack: Operation Channel State = [state:
 CONNECTED], Delta Channel State = [state:CONNECTED] [connectionTag:1]
 [transmitDelta:null] [lastServerVersion:0] [lastTransmitDelta:delta
 version:
 0:d2F2ZTovL3dpYWIubmV0L3crajBfQkQ4dXoxX0EvdXNlcit3b2xrZUB3aWFiLm5ldA==,
 ops: 1, add participant wo...@wiab.net by wo...@wiab.net at Mon Aug 04
 18:29:42 GMT+200 2014 version null, ] [lastAckedVersion: 0:] [queue (0
 msgs):[]], Client CC State =
 [startSignature:0:d2F2ZTovL3dpYWIubmV0L3crajBfQkQ4dXoxX0EvdXNlcit3b2xrZUB3aWFiLm5ldA==]
 [endOfStartingDelta:null] [lastCommittedVersion: 0] [inferredServerPath:[]]
 [unacknowledged:CoreWaveletDelta(wo...@wiab.net,
 0:d2F2ZTovL3dpYWIubmV0L3crajBfQkQ4dXoxX0EvdXNlcit3b2xrZUB3aWFiLm5ldA==, 1
 ops: [add participant wo...@wiab.net by wo...@wiab.net at Mon Aug 04
 18:29:42 GMT+200 2014 version null])] [clientOperationQueue:Operation Queue
 = [deltas: 0] [queue: []] [tailCreator: null] ] [serverOperations:[]]
 Unknown.lI (Unknown source:0)
 Unknown.Bif (Unknown source:0)
 Unknown.icf (Unknown source:0)
 Unknown.ogf (Unknown

Re: Review Request 23682: Release candidate 5 for Wave

2014-07-25 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/23682/#review48749
---

Ship it!


LGTM.

Lets get this out of review board and into master.

(Not sure if this is really the best way to handle merging RC/release branches.)

- Ali Lown


On July 18, 2014, 3:53 p.m., Yuri Zelikov wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/23682/
 ---
 
 (Updated July 18, 2014, 3:53 p.m.)
 
 
 Review request for wave, Andrew Kaplanov, Ali Lown, Michael MacFadden, and 
 Vicente J. Ruiz Jurado.
 
 
 Repository: wave
 
 
 Description
 ---
 
 Changes for RC 5
 
 
 Diffs
 -
 
   CHANGES 725d5b6 
   CHANGES a9fd55d 
   KEYS 7b01194 
   NOTICE.bin f2b53ad 
   README 06cb590 
   README e8bec9d 
   artifact-sign.sh PRE-CREATION 
   artifact-sign.sh 2bb1b34 
   build.properties d995e46 
   build.properties 5f5b772 
   build.xml 73958a1 
   build.xml a5421f5 
   build.xml 8091c55 
   release/artifact-sign.sh PRE-CREATION 
   src/org/waveprotocol/box/stat/Stat.gwt.xml 300c8c7 
   src/org/waveprotocol/box/webclient/stat/Stat.gwt.xml be13f3a 
   src/org/waveprotocol/wave/client/widget/dialog/Dialog.gwt.xml 8dbf371 
 
 Diff: https://reviews.apache.org/r/23682/diff/
 
 
 Testing
 ---
 
 
 Thanks,
 
 Yuri Zelikov

Re: [VOTE] Release Wave 0.5 based on RC5

2014-07-23 Thread Ali Lown

The thumnbail_patterns files were fixed by Vicente back in December.
The curremt files are from the Humanity Project, a note was added to THANKS
to Tango (who are behind them).

The files themselves are public domain.

Ali
On 23 Jul 2014 21:37, Yuri Z vega...@gmail.com wrote:

 Thanks for pointing out these issues Christian.
 Basically, these files are generated, but since we dont want to make the
 project to depend on protobuff library, they are part of the source.
 Anyway, i think we can add the headers.
 Regarding images in thumbnail - i think we sorted out this issue.
 I ll make fixes and create rc6.
  On Jul 23, 2014 10:57 PM, Christian Grobmeier grobme...@gmail.com
 wrote:

  Unfortunately I found some issues which should be solved before we can
  release:
 
  I found these file without headers. Many of them are generated, but I
 found
  others in the same folders which were generated too and had a license
  header.
  So I think we can apply them here as well:
 
  WaveClientRpc.java
  ProfilesProto
  SearchProto
  ProtoDeltaStoreData
  Rpc
  Extensions
  ClientServer
  Diff
  FederationErrorProto
  Proto
 
  Others:
 
  artifact-sign.sh
  eclipse-formatter-style.xml
 
  What are these files in thumbnails_patterns? They look binary, do we have
  the permission to distribute them?
 
  The NOTICE file needs an update to the current year - speaking of the src
  dist, it looks correct (?) for the bin dist.
 
  The LICENSE file in the bin dist contains additional lines of text which
  should not be there. This is what belongs to a NOTICE file.
 
  Basically my main blocker is the header license.
 
  I don't know why files like LICENSE etc are different from the packages.
  They should be the same.
 
  I know its a lot of work, but can we fix these?
 
  Probably there are other issues, but I hope you'll see my point.
 
  Thanks!
  Christian
 
 
  On 19 Jul 2014, at 19:12, Yuri Z wrote:
 
   RC5 is now available for review.
 
  Major changes in RC5:
  - Added MongoDB based deltas store and migration tool for deltas
 migration
  from file to mongo based store.
 
  - Added client/server profiling.
  - Added Atmosphere framework as replacement of Socket.IO.
  - Added alternative - Gmail style initials avatars.
  - Decreased number of permutations in dev compilation and added GWT
  superdev mode.
  - Upgraded the server to Jetty 9.1.1.
  - Added JDK 7 compatibility.
 
  Reminder: Major changes in RC4 included:
  - More licensing fixes
  - Federation works
  - New and updated translations
  - And more...
 
  Artifacts can be found here:
  *https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
  https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
 *
  (Remember checksums are from 'gpg --print-md SHA512 $f  $f.sha')
 
  This is taken from branch
  *https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5
  https://git-wip-us.apache.org/repos/asf?p=incubator-
  wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5*
 
  A summary of useful information can be found in RELEASE-NOTES, and a
  list of changes in CHANGES at the above artifact distribution url, as
  well as being included in the tarballs/zips.(zipballs?)
 
  *Action Required:*
  *It is crucial to test these on some other machines and provide
  **feedback.*
 
  This vote will close around  GMT 26-th July 2014.
 
  [ ] +1   Release it!
  [ ] +0   OK, but...
  [ ] -0OK, but you really should fix
  [ ] -1Definitely not because...
 
  Thanks.
 
 
 
  ---
  http://www.grobmeier.de
  The Zen Programmer: http://bit.ly/12lC6DL
  @grobmeier
  GPG: 0xA5CC90DB

Re: [VOTE] Release Wave 0.5 based on RC5

2014-07-20 Thread Ali Lown

+1.

I have checked:
- CHANGES has the new information in it
- The signatures and sha sums for all 4 artifacts are valid
- Using a debian testing amd64 chroot, I tested that I could build and
run a working server from the source artifact. I tested that I could
run a working server from the binary artifact.
- I tested that text formatting, gadgets, urls all worked.
- I tested this on JDK7.
- I checked that all the required files (CHANGES, DISCLAIMER, LICENSE,
NOTICE, README, THANKS) could be found in both artifacts.

Thanks Yuri for handling this one. I hope to be able to start putting
some time back into Wave over the next few months.

Ali

On 19 July 2014 18:12, Yuri Z vega...@gmail.com wrote:
RC5 is now available for review.

Major changes in RC5:
- Added MongoDB based deltas store and migration tool for deltas migration
from file to mongo based store.

Reminder: Major changes in RC4 included:
- More licensing fixes
- Federation works
- New and updated translations
- And more...

Artifacts can be found here:
*https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/
https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/*
(Remember checksums are from 'gpg --print-md SHA512 $f $f.sha')

This is taken from branch
*https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5
https://git-wip-us.apache.org/repos/asf?p=incubator-wave.git;a=shortlog;h=refs/heads/wave-0.4-rc5*

A summary of useful information can be found in RELEASE-NOTES, and a
list of changes in CHANGES at the above artifact distribution url, as
well as being included in the tarballs/zips.(zipballs?)

*Action Required:*
*It is crucial to test these on some other machines and provide **feedback.*

This vote will close around GMT 26-th July 2014.

[ ] +1 Release it!
[ ] +0 OK, but...
[ ] -0OK, but you really should fix
[ ] -1Definitely not because...

Thanks.

Re: Can not connect from the outside, only localhost is working

2014-07-20 Thread Ali Lown

Ronny,

Could you list your full server.config.

I have just verified that RC5 works fine across a LAN using the exact
same combination of http_* options.

Regards,
Ali

On 20 July 2014 11:24, Ronny Roscher ronny.rosc...@gmail.com wrote:
 Hello guys,

 I seem to have a similar problem as this person here:

 http://mail-archives.apache.org/mod_mbox/incubator-wave-dev/201102.mbox/%3CAANLkTi=9UA7jxBQ2+D-jzsSwYPJ9yQEOLpnH85pebWZ=@mail.gmail.com%3E

 but the solution didn't work for me. I am currently have RC5 installed and
 tried different config settings, tried it without firewall (got an port
 9898 entry in the windows firewall as well as the router firewall
 anyways),... but still no success. The only thing that works is connecting
 via localhost:9898, and there I can register, login, write waves, ... , but
 I can't even connect via ip:9898 on the server machine, nor from another
 machine on the local network.

 I know that I got WIAB working with RC4 but then I decided waiting for a
 future version since the deltas didn't seem to be persistant yet. Later I
 tried compiling versions from git but since then I wan't able to connect
 anymore, but until then I thought it was due to a mistake on my side on
 cimpiling. But after testing it with the official RC5 binary and still not
 being able to connect, something else seems to be the problem. Maybe it is
 the server.config but since I tried so many variants which didn't solve the
 problem it may be something else.

 My current server.config:

 Dwave_server_domain=some.domain.net
 wave_server_domain = local.net
 http_frontend_public_address = 192.168.0.14:9898
 http_websocket_public_address = 192.168.0.14:9898
 http_websocket_presented_address = 192.168.0.14:9898
 http_frontend_addresses = localhost:9898,192.168.0.14:9898

 The rest I kept as it was.


 Finally here is the log when I start the server:

 D:\Programs\GoogleWaveServerjava
 -Djava.util.logging.config.file=wiab-logging.conf
 -Djava.security.auth.login.config=ja
 as.config -Dwave.server.config=server.config  -jar
 dist/wave-in-a-box-server-0.5-incubating.jar
 Jul 20, 2014 12:18:40 PM
 org.waveprotocol.box.server.waveserver.CertificateManagerImpl init
 WARNING: ** SIGNATURE VERIFICATION DISABLED ** see flag
 waveserver_disable_verification
 Jul 20, 2014 12:18:40 PM
 org.waveprotocol.box.server.waveserver.WaveServerImpl init
 INFO: Wave Server configured to host local domains: [local.net]
 Jul 20, 2014 12:18:40 PM org.waveprotocol.box.server.rpc.ServerRpcProvider
 parseAddressList
 WARNING: Ignoring duplicate address in http addresses list: Duplicate entry
 '192.168.0.14:9898' resolved to 192.168.0.14

 Jul 20, 2014 12:18:41 PM org.waveprotocol.box.server.ServerMain run
 INFO: Starting server
 1934 [main] INFO org.eclipse.jetty.server.Server - jetty-9.1.z-SNAPSHOT
 2379 [main] INFO org.eclipse.jetty.webapp.StandardDescriptorProcessor - NO
 JSP Support for /, did not find org.apache.ja
 sper.servlet.JspServlet
 Jul 20, 2014 12:18:42 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onUnregistrationSuccess
 INFO: Unregistered robot: welcome-...@local.net at
 http://192.168.0.14:9898/agent/welcome
 Jul 20, 2014 12:18:42 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onRegistrationSuccess
 INFO: Registered robot: welcome-...@local.net at
 http://localhost:9898/agent/welcome
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.ServerMain$GadgetProxyServlet init
 INFO: Starting GadgetProxyServlet for gmodules.com:80
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onUnregistrationSuccess
 INFO: Unregistered robot: passwd-...@local.net at
 http://192.168.0.14:9898/agent/passwd/user
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onRegistrationSuccess
 INFO: Registered robot: passwd-...@local.net at
 http://localhost:9898/agent/passwd/user
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onUnregistrationSuccess
 INFO: Unregistered robot: passwdadmin-...@local.net at
 http://192.168.0.14:9898/agent/passwd/admin
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onRegistrationSuccess
 INFO: Registered robot: passwdadmin-...@local.net at
 http://localhost:9898/agent/passwd/admin
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onUnregistrationSuccess
 INFO: Unregistered robot: registration-...@local.net at
 http://192.168.0.14:9898/agent/registration/admin
 Jul 20, 2014 12:18:43 PM
 org.waveprotocol.box.server.robots.register.RobotRegistrarImpl$1
 onRegistrationSuccess
 INFO: Registered robot: registration-...@local.net at
 http://localhost:9898/agent/registration/admin
 3052 [main] INFO org.atmosphere.cpr.AtmosphereFramework - Atmosphere is
 using org.atmosphere.cpr.DefaultAnnotationProces
 sor for processing annotation
 3056 [main] INFO

Re: Can not connect from the outside, only localhost is working

2014-07-20 Thread Ali Lown

Ronny,

Okay. I have setup a Server 2012 R2 machine to test this on, with JRE7.

Using the RC5 binary, setup as above with only the 4 http_* lines
adjusted to match my machine, I get 404's when attempting to access
from anywhere other than localhost.

So, this seems to be a Windows specific problem

@Anybody else: any thoughts?

Regards,
Ali

On 20 July 2014 19:18, Ronny Roscher ronny.rosc...@gmail.com wrote:
 Hey Ali,

 Yes it is a Windows Server 2012 R2.

 HomeServer.DreamScape.local, HomeServer is the name of the machine,
 DreamScape the name of the domain. I'm not too familiar with that concept
 tbh, I had to define one on installing the OS and so far it didn't
 interfere with much of my network usage.

 Concerning the the firewall, I only defined the Port for TCP.

 But as I said, with the same settings the RC4 binary of WIAB is working
 fine, I don't have to use any domain for reaching the webpage, just the ip
 or the internet domain + :9898 at the ned and its working.


 Best regards,
 Ronny

Re: Release

2014-07-17 Thread Ali Lown

RAT, but it can be a bit overly sensitive.

Ali
On 17 Jul 2014 17:37, Yuri Z vega...@gmail.com wrote:

 Is there some tool to verify that all files have the licences?


 On Sat, Jul 12, 2014 at 5:18 PM, Michael MacFadden 
 michael.macfad...@gmail.com wrote:

  All,
 
  Although I have been dormant.  I am willing to help out with the release
  in any way possible.  If you need some one to go through the release and
  test it.  Or post it up to he web site once we have it ready let me know.
  I haven¹t helped out in a while, so I would love to contribute.
 
  ~Michael
 
  On 7/12/14, 6:05 AM, Ali Lown a...@lown.me.uk wrote:
 
  Yuri,
  
  AFAIK both of these can be TODOs can be removed now.
  
  Thanks,
  Ali
  
  On 12 July 2014 14:01, Yuri Z vega...@gmail.com wrote:
   Ok, great. This is a great Wiki. I ll try to go the steps and later to
  add
   a release job to jenkins so the release process will be automated. Off
   course if someone want to help with release stuff - it would be great
 :)
   The wiki contains two todos:
   1. ODO: Do we need Extension-Name, Implementation-Vendor-Id as well?
   2. Check export status of any cryptographic dependencies. (Unknown
   currently whether we need an ECCN or not)
  
   Regarding the 2- I think we got rid of it, is it right?
   Regarding 1 - @Ali can you comment?
  
  
   On Sat, Jul 12, 2014 at 3:43 PM, Ali Lown a...@lown.me.uk wrote:
  
   Yuri,
  
   I started writing up the 'procedure' here:
   https://cwiki.apache.org/confluence/display/WAVE/Release+Procedure
 It
   needs updating now that we use git rather than svn.
  
   If we could get jenkins building the releases that would be great!
   (wave-artifacts doesn't seem to be generating the src releases?)
  
   Once the artifacts are made (ant release, or equivalent), then the
   next step is to manually verify the contents are as expected, and to
   sign it.
   I have a very small script to sign all the files using my key, and to
   generate the SHA512 sums for the files: http://pastebin.com/05wBkWd1
  
   Once that is done, send it to the wave list to vote upon...
   Once that is done, send it to the incubator list to vote upon...
   Once that is done, release! ;)
  
   Ali
  
   On 12 July 2014 13:21, Yuri Z vega...@gmail.com wrote:
Thanks for update Ali.
I think the release is important to show that we handled all the
   copyright
issues, so I would prefer just to release as is and then add the
  patch
later.
Anyway, let's try to do the release stuff for rc 05. Are there any
   scripts
that should be run? What is the procedure?
By the way, I already added a Jenkins job to create the release
  artifact
   -
https://builds.apache.org/view/S-Z/view/Wave/job/wave-artifacts/
So, if could to automate the licenses verification and signing we
  could
release just by running the job in Jenkins...
   
   
   
   
On Sat, Jul 12, 2014 at 2:56 PM, Ali Lown a...@lown.me.uk wrote:
   
RC4 was merged back in to master around January, and development
 has
continued in master from there..
   
I don't recall any major show stoppers with RC4. A look at the
 vote
thread suggests that the only problems left to discuss were the
  images
in thumbnail_patterns, for which we could find no copyright
assignment. But we fixed this problem in 48c3bc9, by changing the
thumbnails to some we could attribute.
   
On a meta level, the problem at the time was that RC4 had a very
  poor
vote turnout, disincentivizing further work.
(And on a personal level, I ran out of time I could put towards
  Wave)
   
I don't think there is anything stopping us putting together RC5
  over
this weekend.
(Since we would want to take from current master, a check of the
licenses will be required to be redone).
   
Is there interest in RC5?
(And do we want to put Frank's fulltextsearch patches in?)
   
Thanks,
Ali
   
On 12 July 2014 12:35, Yuri Z vega...@gmail.com wrote:
 I think I merged the rc 0.4 into master a while ago. But I don't
   remember
 what were the issues that prevented from us to release rc 0.4.
 @Ali, so you remember what were the issues?


 On Sat, Jul 12, 2014 at 2:27 PM, Christian Grobmeier 
grobme...@gmail.com
 wrote:

 Hi folks,

 before quite a while, we were discussing a release. It's still
  not
there,
 and I would like to know what the actual problem is.

 As you know, releases are considered a sign of a healthy
 project
  in
   the
 incubator.
 It's currently discussed within the IPMC why projects which
 don't
   manage
 to make a release
 after a year should stay in the incubator.

 Regards,
 Christian

 ---
 http://www.grobmeier.de
 The Zen Programmer: http://bit.ly/12lC6DL
 @grobmeier
 GPG: 0xA5CC90DB

Re: Release

2014-07-12 Thread Ali Lown

Yuri,

I started writing up the 'procedure' here:
https://cwiki.apache.org/confluence/display/WAVE/Release+Procedure It
needs updating now that we use git rather than svn.

If we could get jenkins building the releases that would be great!
(wave-artifacts doesn't seem to be generating the src releases?)

Once the artifacts are made (ant release, or equivalent), then the
next step is to manually verify the contents are as expected, and to
sign it.
I have a very small script to sign all the files using my key, and to
generate the SHA512 sums for the files: http://pastebin.com/05wBkWd1

Once that is done, send it to the wave list to vote upon...
Once that is done, send it to the incubator list to vote upon...
Once that is done, release! ;)

Ali

On 12 July 2014 13:21, Yuri Z vega...@gmail.com wrote:
 Thanks for update Ali.
 I think the release is important to show that we handled all the copyright
 issues, so I would prefer just to release as is and then add the patch
 later.
 Anyway, let's try to do the release stuff for rc 05. Are there any scripts
 that should be run? What is the procedure?
 By the way, I already added a Jenkins job to create the release artifact -
 https://builds.apache.org/view/S-Z/view/Wave/job/wave-artifacts/
 So, if could to automate the licenses verification and signing we could
 release just by running the job in Jenkins...




 On Sat, Jul 12, 2014 at 2:56 PM, Ali Lown a...@lown.me.uk wrote:

 RC4 was merged back in to master around January, and development has
 continued in master from there..

 I don't recall any major show stoppers with RC4. A look at the vote
 thread suggests that the only problems left to discuss were the images
 in thumbnail_patterns, for which we could find no copyright
 assignment. But we fixed this problem in 48c3bc9, by changing the
 thumbnails to some we could attribute.

 On a meta level, the problem at the time was that RC4 had a very poor
 vote turnout, disincentivizing further work.
 (And on a personal level, I ran out of time I could put towards Wave)

 I don't think there is anything stopping us putting together RC5 over
 this weekend.
 (Since we would want to take from current master, a check of the
 licenses will be required to be redone).

 Is there interest in RC5?
 (And do we want to put Frank's fulltextsearch patches in?)

 Thanks,
 Ali

 On 12 July 2014 12:35, Yuri Z vega...@gmail.com wrote:
  I think I merged the rc 0.4 into master a while ago. But I don't remember
  what were the issues that prevented from us to release rc 0.4.
  @Ali, so you remember what were the issues?
 
 
  On Sat, Jul 12, 2014 at 2:27 PM, Christian Grobmeier 
 grobme...@gmail.com
  wrote:
 
  Hi folks,
 
  before quite a while, we were discussing a release. It's still not
 there,
  and I would like to know what the actual problem is.
 
  As you know, releases are considered a sign of a healthy project in the
  incubator.
  It's currently discussed within the IPMC why projects which don't manage
  to make a release
  after a year should stay in the incubator.
 
  Regards,
  Christian
 
  ---
  http://www.grobmeier.de
  The Zen Programmer: http://bit.ly/12lC6DL
  @grobmeier
  GPG: 0xA5CC90DB

Re: Possible regression since wave-0.4-release and commit 47cd2e99. 404 errors generated unless the server is accessed through localhost

2014-05-21 Thread Ali Lown

Gareth,

Thanks for reporting this. Given the revisions you list, this sounds
like a problem caused by the atmosphere addition.

Have you tried not listing localhost in each of the http_*_address variables?

What resource is attempted to be accessed that causes a 404?

Thanks,
Ali

On 18 May 2014 23:55, Gareth gareth@gmail.com wrote:
 I don't know if this is the correct channel to post this, but this one had
 me scratching my head all day so I figured I should.

 My config file currently looks like this:

 # A comma separated list of address on which to listen for connections.
 # Each address is a comma separated host:port pair.
 # Default value: localhost:9898
 http_frontend_public_address = 192.168.0.10:9898,localhost:9898

 # A optional host:port address on which to listen for websocket connections.
 # If no value is set for http_websocket_public_address it defaults to the
 first address specified
 # by http_frontend_public_address.
 # Default value: localhost:9898
 http_websocket_public_address = 192.168.0.10:9898,localhost:9898

 # An optional host:port address for which the client is told to attempt
 websocket connections.
 # If no value is set for http_websocket_presented_address it defaults to
 http_websocket_public_address
 # Default value: localhost:9898
 http_websocket_presented_address = 192.168.0.10:9898,localhost:9898

 # Default value: values passed to http_frontend_public_address.
 http_frontend_addresses = 192.168.0.10:9898,localhost:9898.

 Where 192.168.0.10 is just my local box's ip address given by ifconfig:

 $ ifconfig

 eth0  Link encap:Ethernet  HWaddr 00:1f:d0:5f:6e:73
   inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
   inet6 addr: fe80::21f:d0ff:fe5f:6e73/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:2207164 errors:0 dropped:0 overruns:0 frame:0
   TX packets:1020261 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:2855724570 (2.8 GB)  TX bytes:132984003 (132.9 MB)

 loLink encap:Local Loopback
   inet addr:127.0.0.1  Mask:255.0.0.0
   inet6 addr: ::1/128 Scope:Host
   UP LOOPBACK RUNNING  MTU:65536  Metric:1
   RX packets:23626 errors:0 dropped:0 overruns:0 frame:0
   TX packets:23626 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:5654690 (5.6 MB)  TX bytes:5654690 (5.6 MB)


 If I access the server via http://localhost:9898 via a browser wave runs
 fine, but if I access it through http://192.168.0.10:9898 I get 404 errors
 no matter which page I visit. I'm on Ubuntu 12.04 LTS but I was also able
 to observe this behaviour on Amazon EC2 running Ubuntu 14.04 LTS where I
 had to verify http://localhost:9898 was working by using wget.

 I observed this behaviour in commit 47cd2e99 but happily it seems to be
 absent from wave-0.4-release.

Re: Review Request 20610: Removing old dependency with socketio-java

2014-04-26 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20610/#review41557
---

Ship it!


LGTM.

- Ali Lown


On April 23, 2014, 4:21 p.m., Vicente J. Ruiz Jurado wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/20610/
 ---
 
 (Updated April 23, 2014, 4:21 p.m.)
 
 
 Review request for wave, Ali Lown, Pablo Ojanguren, and Yuri Zelikov.
 
 
 Repository: wave
 
 
 Description
 ---
 
 Just removing the use of socketio-gwt.
 
 
 Diffs
 -
 
   .classpath ea8d06a 
   build.xml 8f1fc77 
   src/org/waveprotocol/box/server/CoreSettings.java 0a6f3fd 
   src/org/waveprotocol/box/server/rpc/AbstractWaveSocketIOServlet.java 
 be90642 
   src/org/waveprotocol/box/server/rpc/ServerRpcProvider.java ca2f6b8 
   src/org/waveprotocol/box/server/rpc/SocketIOServerChannel.java 2f8ec13 
   src/org/waveprotocol/box/webclient/client/WaveWebSocketClient.java 0b68d71 
   test/org/waveprotocol/box/server/rpc/RpcTest.java d86ddf8 
 
 Diff: https://reviews.apache.org/r/20610/diff/
 
 
 Testing
 ---
 
 gwt-compile and server basic tests
 
 
 Thanks,
 
 Vicente J. Ruiz Jurado

Re: Review Request 19355: Added Atmosphere framework as replacement of Socket.IO

2014-04-22 Thread Ali Lown



 On April 16, 2014, 6:59 a.m., Vicente J. Ruiz Jurado wrote:
  LGTM
  
  PS: Probably we have to use something like this in the future:
  http://www.eclipse.org/jetty/documentation/current/example-slf4j-multiple-loggers.html

@Vicente: Do you want to commit this then, as you have been reviewing it? 
Holding off any longer is causing issues with superdev mode.


- Ali


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19355/#review40508
---


On April 15, 2014, 6:47 p.m., Pablo Ojanguren wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/19355/
 ---
 
 (Updated April 15, 2014, 6:47 p.m.)
 
 
 Review request for wave, Andrew Kaplanov, Ali Lown, Vicente J. Ruiz Jurado, 
 and Yuri Zelikov.
 
 
 Bugs: WAVE-405
 https://issues.apache.org/jira/browse/WAVE-405
 
 
 Repository: wave
 
 
 Description
 ---
 
 This patch provides a full replacement of the Socket.IO as an alternative to 
 websockets when they are not available. Atmosphere framework is configured to 
 use long-polling protocol but additional are available.
 
 Server and GWT client has been affected. 
 
 NOT all references to Socket.IO has been removed from the source code yet.
 And .jar dependencies have been kept also. Is it safe to remove them?
 
 New dependencies has been included in build.xml, task get-third-party, so 
 none special process is needed to build this version.  
 The atmosphe.js client file is also handled as a third-party dep and it's 
 served from the class path
 
 
 Diffs
 -
 
   build.xml 0681b164cf580dd161d110dbf1032337243db79d 
   src/org/waveprotocol/box/server/rpc/ServerRpcProvider.java 
 9b0f2a927bf75b92fb708c3abfdb4666d9cd6e63 
   src/org/waveprotocol/box/server/rpc/atmosphere/AtmosphereChannel.java 
 PRE-CREATION 
   
 src/org/waveprotocol/box/server/rpc/atmosphere/AtmosphereClientInterceptor.java
  PRE-CREATION 
   src/org/waveprotocol/box/server/rpc/atmosphere/GuiceAtmosphereFactory.java 
 PRE-CREATION 
   src/org/waveprotocol/box/webclient/WebClient.gwt.xml 
 387d0c78206bfca61412f31bdac26ec9a67224c9 
   src/org/waveprotocol/box/webclient/client/WaveSocketFactory.java 
 4a1788fc6f89fa07cbc41ab99335b25861388d8a 
   src/org/waveprotocol/box/webclient/client/WaveWebSocketClient.java 
 65746d2348bf55a6c6f22b8b4404dfca6c8de302 
   
 src/org/waveprotocol/box/webclient/client/atmosphere/AtmosphereConnection.java
  PRE-CREATION 
   
 src/org/waveprotocol/box/webclient/client/atmosphere/AtmosphereConnectionImpl.java
  PRE-CREATION 
   
 src/org/waveprotocol/box/webclient/client/atmosphere/AtmosphereConnectionListener.java
  PRE-CREATION 
   
 src/org/waveprotocol/box/webclient/client/atmosphere/AtmosphereConnectionState.java
  PRE-CREATION 
 
 Diff: https://reviews.apache.org/r/19355/diff/
 
 
 Testing
 ---
 
 Only basic test has been performed so far: wiab server with two users 
 connected, all in the same dev computer. Using Firefoz 23 with websockets 
 disabled.
 
 More test and feedback is needed covering different browsers, work load and 
 network environments. All configuration values of the atmosphere framework 
 are set to default ones (thread pool size, buffers size...) so I think they 
 will need fine tuning.
 
 
 Thanks,
 
 Pablo Ojanguren

Re: Socket.IO script

2014-04-22 Thread Ali Lown

Ben,

This is a problem due to our enabling of superdev mode (which is a new
feature in gwt 2.5).

Sadly, 2.5 has deprecated support for cross-site-iframes which are in
use in the socketio package.

Workarounds:
1) Use the in-review patch to use atmosphere (avoids this issue)
2) Do as the error message says, and edit the xml build file to tell
gwt to ignore the message
3) Don't use superdev mode :p

Ali

On 22 April 2014 21:35, Ben Hegarty heg...@gmail.com wrote:
 Btw thanks for the tip, it looks like you're right, the gwt.xml that's
 causing it ,is buried there :)


 On Tue, Apr 22, 2014 at 9:32 PM, Ben Hegarty heg...@gmail.com wrote:

 Nope I'm seeing it as a build failure, when I try 'ant superdev-gwt' which
 I hope is a valid target?


 On Tuesday, April 22, 2014, Terry Hardin thardin...@gmail.com wrote:

 backwards compatibility. you should only see this as a warning, right? in
 chrome?


 On Tue, Apr 22, 2014 at 2:24 PM, Thomas Broyer t.bro...@gmail.com
 wrote:

  In the socketio-gwt JAR?
  Le 22 avr. 2014 22:03, Ben Hegarty heg...@gmail.com a écrit :
 
   Hi,
  
   I was wondering if anyone knows where in the wave codebase generates
 the
   following error?
  
[java]Invoking Linker Cross-Site-Iframe
[java] at
  
  
 
 com.google.gwt.core.ext.linker.impl.SelectionScriptLinker.generateSelectionScript(SelectionScriptLinker.java:422)
   [ERROR] The Cross-Site-Iframe linker does not support script tags in
  the
   gwt.xml files, but the gwt.xml file (or the gwt.xml files which it
   includes) contains the following script tags:
[java]
[java] /socket.io/socket.io.js
  
  
   I understand that its something do do with the import of socket.IO
 but I
   can't seem to find the code that imports Socket.IO to cause the error.
   Hopefully we'll have the atmosphere replacement soon :)
  
  
   --
   Regards
   Ben
  
 



 --
 Regards
 Ben




 --
 Regards
 Ben

Re: Review Request 17943: Inbox filter by date range

2014-04-21 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17943/#review40872
---

Ship it!


LGTM.

- Ali Lown


On April 16, 2014, 7:54 a.m., Pablo Ojanguren wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/17943/
 ---
 
 (Updated April 16, 2014, 7:54 a.m.)
 
 
 Review request for wave.
 
 
 Bugs: WAVE-408
 https://issues.apache.org/jira/browse/WAVE-408
 
 
 Repository: wave
 
 
 Description
 ---
 
 - Server part: added new operators to the search query string to indicate a 
 date range to filter a wave search.
 
From:MMdd Select wavelets with a later date value.
 
To:MMdd Select wavelets with an earlier or equal date 
 value.
 
Usedate:[createdate|lastmoddate]
Date field for filtering.
 
 
 - Client part: added a dialog box to select dates, participants and creator. 
 It's opened clicking a new buttom in the search panel.
 
 
 Diffs
 -
 
   src/org/waveprotocol/box/server/waveserver/QueryHelper.java 
 c108e5bf6ec31d69f229ddf0408f0ea405ed14bb 
   src/org/waveprotocol/box/server/waveserver/SimpleSearchProviderImpl.java 
 3c698164fa509b20d753934ed0d24ccd5595cbc1 
   src/org/waveprotocol/box/server/waveserver/TokenQueryType.java 
 654635041067339a09e695910778ad1444e43ce5 
   src/org/waveprotocol/box/webclient/search/Search.css 
 d0b0a94661d350b240f6bca37468cc84fcb98739 
   src/org/waveprotocol/box/webclient/search/SearchFilterDialog.css 
 PRE-CREATION 
   src/org/waveprotocol/box/webclient/search/SearchFilterDialogView.java 
 PRE-CREATION 
   src/org/waveprotocol/box/webclient/search/SearchFilterDialogWidget.java 
 PRE-CREATION 
   src/org/waveprotocol/box/webclient/search/SearchFilterDialogWidget.ui.xml 
 PRE-CREATION 
   src/org/waveprotocol/box/webclient/search/SearchPanelResourceLoader.java 
 178470832ba0246ed9c34892af615fb3d1c85d30 
   src/org/waveprotocol/box/webclient/search/SearchWidget.java 
 076aa4b571dedf86e93c190802c81359cba847b5 
   src/org/waveprotocol/box/webclient/search/SearchWidget.ui.xml 
 f929f709d618cf19d95a99a1d3c5961d984dc6ac 
   src/org/waveprotocol/box/webclient/search/i18n/SearchWidgetMessages.java 
 490b8397c2532b243a30e7277cf634c05fc8c7e6 
 
 Diff: https://reviews.apache.org/r/17943/diff/
 
 
 Testing
 ---
 
 Manual test: tested different ranges of dates ensuring that only right waves 
 were selected.
 
 
 Thanks,
 
 Pablo Ojanguren

Re: Review Request 20207: Fix for gadget proxy request URI

2014-04-10 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20207/#review40052
---

Ship it!


LGTM.
FYI: You need to put the bug id in as WAVE-411 for Reviewboard to link it up 
correctly...

PS. For fixes of this size, it really wasn't worth a 'review', just commit 
them...

- Ali Lown


On April 10, 2014, 12:46 p.m., Vicente J. Ruiz Jurado wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/20207/
 ---
 
 (Updated April 10, 2014, 12:46 p.m.)
 
 
 Review request for wave, Ali Lown, Pablo Ojanguren, and Yuri Zelikov.
 
 
 Bugs: 411
 https://issues.apache.org/jira/browse/411
 
 
 Repository: wave
 
 
 Description
 ---
 
 A fix for #411, so gadget transparent proxy works again with jetty 9.
 
 
 Diffs
 -
 
   src/org/waveprotocol/box/server/ServerMain.java 6887bcc 
 
 Diff: https://reviews.apache.org/r/20207/diff/
 
 
 Testing
 ---
 
 For instance, 
 ant run-server
 and try to open:
 http://localhost:9898/gadgets/js/core:rpc.js
 and not to get a 404.
 
 
 Thanks,
 
 Vicente J. Ruiz Jurado

Re: Review Request 20209: Fix for missing dependency in dist-server

2014-04-10 Thread Ali Lown


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/20209/#review40053
---

Ship it!


LGTM. Similarly, this stuff should just get committed.

- Ali Lown


On April 10, 2014, 1:35 p.m., Vicente J. Ruiz Jurado wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/20209/
 ---
 
 (Updated April 10, 2014, 1:35 p.m.)
 
 
 Review request for wave, Ali Lown and Yuri Zelikov.
 
 
 Repository: wave
 
 
 Description
 ---
 
 Fix for this missing servlet:
 
 ./run-server.sh 
 abr 10, 2014 3:22:08 PM 
 org.waveprotocol.box.server.waveserver.CertificateManagerImpl init
 Advertencia: ** SIGNATURE VERIFICATION DISABLED ** see flag 
 waveserver_disable_verification
 abr 10, 2014 3:22:08 PM org.waveprotocol.box.server.waveserver.WaveServerImpl 
 init
 Información: Wave Server configured to host local domains: [local.net]
 abr 10, 2014 3:22:08 PM org.waveprotocol.box.server.rpc.ServerRpcProvider 
 parseAddressList
 Advertencia: Ignoring duplicate address in http addresses list: Duplicate 
 entry 'localhost:9898' resolved to 127.0.0.1
 Exception in thread main java.lang.NoClassDefFoundError: 
 cc/kune/initials/InitialsAvatarsServlet
 at 
 org.waveprotocol.box.server.ServerMain.initializeServlets(ServerMain.java:252)
 at org.waveprotocol.box.server.ServerMain.run(ServerMain.java:192)
 at org.waveprotocol.box.server.ServerMain.main(ServerMain.java:138)
 Caused by: java.lang.ClassNotFoundException: 
 cc.kune.initials.InitialsAvatarsServlet
 at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
 
 
 Diffs
 -
 
   build.xml ae3ba88 
 
 Diff: https://reviews.apache.org/r/20209/diff/
 
 
 Testing
 ---
 
 
 Thanks,
 
 Vicente J. Ruiz Jurado

Re: How to migrate deltas from file to mongoDB storage

2014-04-10 Thread Ali Lown

Pablo,

There does not currently exist a method of exporting all waves from the server.

The import/export tool was written in mind for a particular user
moving from GWave-WIAB, so they would have only cared about waves
that a particular user was a participant in.

The export tool just uses the list of waves returned by the search api.

Feel free to improve on the export tool, so that it can interact
directly with the wave store, to allow it to read/write all waves.

Ali

On 9 April 2014 09:54, Pablo Ojanguren pablo...@gmail.com wrote:
 I have been playing with wave export/import tool and it works great and of
 course it allows to move then from disk to mongodb. But it only exports
 those waves of the user we use to execute the tool. So from an
 administration point of view I can't perform a full dump of waves.

 Does anybody know if there is a way to perform a full export of waves?


 Thank you!



 2014-03-03 19:09 GMT+01:00 Pablo Ojanguren pablo...@gmail.com:

 Yes, I was pending to check out your patch! Thank you very much!


 2014-03-03 18:57 GMT+01:00 Ben Hegarty heg...@gmail.com:

 just as an FYI there is a bug in the mongodb impl in the file
 MongoDbDeltaCollection.java here...

  129   @Override
 130   public WaveletDeltaRecord getDeltaByEndVersion(long version) throws
 IOException {
 131 DBObject query = createWaveletDBQuery();
 132

 query.put(MongoDbDeltaStoreUtil.FIELD_TRANSFORMED_RESULTINGVERSION_VERSION,
 version);
 133
 134 DBObject result = deltaDbCollection.findOne(query);
 135
 136 WaveletDeltaRecord waveletDelta = null;
 137
 138 if (result != null)
 139 try {
 *140   MongoDbDeltaStoreUtil.deserializeWaveletDeltaRecord(result);*
 141 } catch (PersistenceException e) {
 142   throw new IOException(e);
 143 }
 144 return waveletDelta;
 145   }

 that may cause issues, the deserialised record doesn't actually get
 returned.  Once I fixed the mongodb unit tests, I found it.

 Regards
 Ben


 On Mon, Mar 3, 2014 at 5:02 PM, Pablo Ojanguren pablo...@gmail.com
 wrote:

  Great whether import/export tools are realiable. I will perform test
 too.
 
  Thanks
 
 
  2014-03-03 17:59 GMT+01:00 Yuri Z vega...@gmail.com:
 
   I guess it might work. I ll try it out.
   On Mar 3, 2014 6:53 PM, Pablo Ojanguren pablo...@gmail.com wrote:
  
Hi,
   
I wonder if we could use existing delta export/import utilities to
   perform
such migration. These would be the steps to perform:
   
1) Run export utility and get a full backup of deltas
2) Change server configuration to use mongoDB for delta persistence
3) Run import utility with previous backup files
   
   
Does anyone see any pitfall or risk in this approach?
   
Thank you.
   
  
 



 --
 Regards
 Ben

Re: Sudden traffic on the demo servers

2014-04-08 Thread Ali Lown

If you haven't done so already, it is certainly worth a look through
the comments made by HNers:
https://news.ycombinator.com/item?id=7532059

Ali

On 8 April 2014 22:46, John Blossom jblos...@gmail.com wrote:
 Interesting.

 All the best,

 John Blossom
 On Fri, Apr 4, 2014 at 4:53 PM, Yuri Z vega...@gmail.com wrote:

 Thanks


 On Fri, Apr 4, 2014 at 11:37 PM, Ali Lown a...@lown.me.uk wrote:

  It was on hackernews.
  On 4 Apr 2014 21:36, Yuri Z vega...@gmail.com wrote:
 
   There's a sudden spike in traffic volume for the waveinabox.net -
 about
   2500 hits during the last few hours. The traffic comes from the Apache
  Wave
   demo servers page, so I guess someone put the link to Apache Wave
   incubation site. Did anyone mention a blog/article about Apache Wave
   lately?

1 2 3 4 5 >

1 - 100 of 415 matches

Mail list logo