13:00:05 <evilaliv3> #startmeeting
13:00:05 <MeetBot> Meeting started Fri May 15 13:00:05 2015 UTC.  The chair is evilaliv3. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:05 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:15 <evilaliv3> halo! :)
13:00:37 <evilaliv3> here is the pad for the scrum activity of today!
13:00:38 <evilaliv3> http://piratepad.net/zMKNNa74iU
13:00:55 <evilaliv3> i've already filled mine, let me know if you have some comment
13:06:44 <elv> "i promise" ahah lol
13:07:28 <elv> seems a very good schedule
13:07:40 <elv> to match our goal for end2end release
13:10:03 <evilaliv3> ehehe
13:28:43 <evilaliv3> ok thanks elv
13:29:15 <evilaliv3> i'm ok with the schedule as the work on this task is still not started
13:30:17 <evilaliv3> for the future when you will have analyzed the problem try to divide the task in objectives and to assign you clear task days by days
13:30:51 <evilaliv3> just to self asses yourself on daily targets
13:44:39 <elv> yep
13:45:01 <elv> to clear things out
13:45:14 <elv> it's not just "crypto yes or no?"
13:45:15 <elv> right?
13:49:24 <evilaliv3> in general no, as we need to test various capabilities like: cookies enabled, localstorage, compatibility with angularjs
13:49:45 <elv> ok so i start with these four
13:49:58 <elv> cookies, localstorage, angularjs, crypto
13:50:18 <evilaliv3> in practice as window.crypto is only suppoterd in recent browser that support all the other capabilities windows.crypto could be evaulated as the simple test to do
13:51:01 <evilaliv3> for the moment you could start analyzing deeply the requirements of globaleaks around topics like: cookies, crypto, localstorage, angularjs
13:51:19 <evilaliv3> then when analyzed the requirements identify wich browsers support the various things
13:52:03 <evilaliv3> and then try to design this simple detector() and the relevant situations in which notify the user meaningful information
13:53:09 <evilaliv3> by the way naif already described it all on the ticket. and addressing the ticket would be probably more easy of what i'm discribing here, 'cause as i've said it's also possible that the only simple thing to test is "window.crypto" and that if the browser has that it already has all the other things
13:53:14 <evilaliv3> got the point ?
13:53:21 <evilaliv3> naif anything to add ?
13:54:35 <naif> i got to go in few minutes
13:54:47 <naif> yesterday we agreed what to do
13:55:04 <naif> - write in the ticket the list of methods that shall be checked
13:55:10 <naif> have we done that?
13:55:45 <naif> i don't think that we need more than 20-30 minutes
14:16:40 <evilaliv3> i written mine current analysis here: https://github.com/globaleaks/GlobaLeaks/issues/137#issuecomment-102410937
14:38:30 <from-freenode> [gitter]  Authentication failed. Get a valid token from https://irc.gitter.im
14:38:33 <from-freenode> [gitter]  Authentication failed. Get a valid token from https://irc.gitter.im
14:55:10 <evilaliv3> #endmeeting