On 2/20/14 9:52 AM, nperria...@mozilla.com wrote:
On Thursday, February 20, 2014 12:31:53 AM UTC+1, Adam Roach wrote:
* L: *Nicolas* to examine use of client libraries (jQuery, Backbone)
to determine how much effort we're likely to save versus the effort
of ensuring we can run the
Looking at database backends for the data we’re talking about storing, these
are the ranked concerns that I have heard:
1. availability
2. performance
3. consistency and partition tolerance
Basically, if the service is up, that’s good. The data that we are hold here
is either very short lived
On 2/20/14 12:08, Dan Mosedale wrote:
On Thu Feb 20 09:15:15 2014, Adam Roach wrote:
Keep in mind that the nominal user experience for this, once we get to
MVP, will be rooted in an address book. I'll have my list of contacts,
which includes phone numbers and email addresses. When an address bo
On Thu Feb 20 09:15:15 2014, Adam Roach wrote:
Keep in mind that the nominal user experience for this, once we get to
MVP, will be rooted in an address book. I'll have my list of contacts,
which includes phone numbers and email addresses. When an address book
user is activated by a user, we'll c
You know, we might be able to have our cake and eat it too. Just
call it PTS, and pretend it is an acronym.
Byron
On 2/20/14 9:55 AM, Christopher Lee wrote:
Hi all,
I would say that *if* the majority of the team agreed to this, let's move
forward with this name.
I know it's unlikely we'
Hi all,
I would say that *if* the majority of the team agreed to this, let's move
forward with this name.
I know it's unlikely we're going to have everyone happy with a project name.
The point of 'it could be a product name' is very subjective given some very
strange startup product names o
On Thursday, February 20, 2014 12:31:53 AM UTC+1, Adam Roach wrote:
> * L: *Nicolas* to examine use of client libraries (jQuery, Backbone)
> to determine how much effort we're likely to save versus the effort
> of ensuring we can run the libraries safely in the context of
> elevated
I think that this fails one of the basic criterion that Andreas laid out.
Namely, that it can very easily be mistaken for a product name. I can imagine
taking this to a public announcement.
On 2014-02-20, at 00:57, Romain Testard wrote:
> Hi all,
>
> Thanks for your input regarding re-namin
On 2/20/14 04:54, Alexis Métaireau wrote:
Adam, thanks for starting this discussion,
Le 20/02/2014 04:52, Adam Roach a écrit :
Putting this together, what we want is something that semantically
evaluates to:
http://authority/action/url-format-version/{serial
#,caller,callee,expiration,hmac}
A
On 19/02/2014 23:48, Eric Rescorla wrote:
> On Wed, Feb 19, 2014 at 3:31 PM, Adam Roach wrote:
>> * We will use github pull requests to ensure that patches are reviewed
>>prior to landing.
>>
>
> I missed this decision, but it's not really matching what I would have
> expected.
>
> Rather,
Any progress on bandwidth/webrtc constraints control in firefox yet?
On Thursday, July 4, 2013 1:48:12 AM UTC+2, bryand...@gmail.com wrote:
> FF 22 does not seem to honor the video constraints passed to getUserMedia:
>
>
>
> getUserMedia(
>
> {audio:true,video:{mandatory:{maxWidth:320,maxHe
As of this morning, the "Talkilla"* product now has the User Stories
extension added to it in Bugzilla.
The extension provides:
* A User Story field just under the attachments box
* The User story field can be updated by anyone
* History is kept for the user story field
The intention is th
Adam, thanks for starting this discussion,
Le 20/02/2014 04:52, Adam Roach a écrit :
> Putting this together, what we want is something that semantically
> evaluates to:
>
> http://authority/action/url-format-version/{serial
> #,caller,callee,expiration,hmac}
As Martin points out, URLs should not
Hi all,
Thanks for your input regarding re-naming the project.
This came to a draw between Loop and Archway and we decided that Loop is
a good name for the WebRTC application project (the product name will be
different).
Loop is concise, fits all of Andreas requirements and can be turned into
14 matches
Mail list logo
