On Fri, Jun 6, 2014 at 5:31 PM, Julien Wajsberg wrote:
> If I can summarize your thoughts, in my decreasing order of importance :
>
> 1. when I report bug, they basically get ignored
> -> this is the #1 issue to have a sane community.
>
> The owners or peers of components should definitely triage
On 8/6/2014, 17:37, Johannes Bauer wrote:
On 03.06.2014 16:52, Kartikaya Gupta wrote:
In general the proprietary files are stored in a backup-* folder inside
the B2G source folder. (For the Alcatel it's probably called
backup-hamachi or backup-buri). You should be able to back this folder
up as
On 08/06/2014 23.54, Johannes Bauer wrote:
Hm yes the Alcatel is quite a tortoise speed-wise and unresponsive at
times. I also blame the hardware for that.
The hardware is not stellar but we could also do better in certain respects.
Is the difference between the Alcatel One Touch Fire and the
On 05.06.2014 21:33, Chris Mills wrote:
>> Thinking about it, maybe I'll write a wrapper script that does exactly
>> what I propose. That will clone the different repos, have some
>> rudimentary i18n support (will create these json files for instance) and
>> will be able to extract and re-feed tha
Hey Natalia,
On 04.06.2014 18:46, Natalia Martinez-Winter wrote:
> After using 1.4 for a while (and was really satisfied with it, although
> I could report some minor bugs...), I'm currently on 2.0 on my Alcatel
> One Touch Fire and I wouldn't recommend it right now. There are still
> many bugs wh
Hey Julien,
yes you paraphrased my points nicely and the proposed solutions (i.e.
having different "channels" to upgrade to) would be absolutely wonderful.
About the browser crashes, I didn't know that the Alcatel was so poorly
equipped with hardware. But that would certainly explain things. Than
On 03.06.2014 16:52, Kartikaya Gupta wrote:
> In general the proprietary files are stored in a backup-* folder inside
> the B2G source folder. (For the Alcatel it's probably called
> backup-hamachi or backup-buri). You should be able to back this folder
> up as you describe and then put it back in
Hey Johannes,
If I can summarize your thoughts, in my decreasing order of importance :
1. when I report bug, they basically get ignored
-> this is the #1 issue to have a sane community.
The owners or peers of components should definitely triage their coming
bugs at least once a week. Maybe dif
Bit more of a complete reply - sorry for the delay!
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills
On 3 Jun 2014, at 13:18, Johannes Bauer wrote:
> Hey Chris,
>
> On 03.06.2014 13:00, Chris Mills wrote:
>> One thing I will
After using 1.4 for a while (and was really satisfied with it, although
I could report some minor bugs...), I'm currently on 2.0 on my Alcatel
One Touch Fire and I wouldn't recommend it right now. There are still
many bugs which prevents from using it as a phone (you would probably
miss calls,
On Tue, 03 Jun 2014 11:48:08 +0200, Johannes Bauer wrote:
> Ironically the worst thing about the phone is the browser. Wow, that
> browser sucks so much it's hard to put in words. It feels like Netscape
> Navigator again. Don't know why something with a "Firefox" label can
> have such a horrible b
On 06/03/2014 04:48 AM, Johannes Bauer wrote:
> About the usage: One of the very very first things I noticed was that
> the phone had a irritating, annoyning and most of all completely useless
> vibration effect when pressing the home button. It's one of the first
> tickets I commented on and it wa
On 3/6/2014, 8:18, Johannes Bauer wrote:
One problem for me is that I cannot tell which components are
proprietary (vendor-specific) and which aren't. During the build process
the phone has to be hooked up so it can fetch these proprietary files.
It's not transparent to me where these files end u
If it's any consolation I'm a staff member and my dogfooding bugs get
ignored, too :)
I recall that dialing bug - I am pretty sure we fixed that. It
definitely doesn't exist in 2.0.
As Chris said, v2.0 is light years ahead of v1.2.
Thanks for giving it a go anyway, you've given it far more p
On 6/3/2014 8:18 AM, Johannes Bauer wrote:
Reading through my message again, it's clear that I really hit the wrong
tone. I sound all bitchy and pissed which is not what I wanted to come
across as. Thanks for ignoring that attitude and focusing on the content.
FWIW, brutally honest feedback is
Hey Chris,
On 03.06.2014 13:00, Chris Mills wrote:
> This is really interesting feedback; thanks Johannes! I can only really speak
> for the documentation aspect of the project, so the comments below will only
> focus on those. I’ll let other better qualified team members comment on the
> dev p
This is really interesting feedback; thanks Johannes! I can only really speak
for the documentation aspect of the project, so the comments below will only
focus on those. I’ll let other better qualified team members comment on the dev
process issues, etc.
One thing I will say is that the OS is
Hey list,
so I've been using Firefox OS on my Alcatel One Touch Fire since Nov
2013 as my only phone on a day-to-day basis. I'd like to share my
feedback to give you an impression about what I like and dislike about
it. I've been on branch 1.2 for pretty much the whole trip.
Gernerally when I bou
18 matches
Mail list logo
