Hi,

As for introduction, I'm David Bruant, Mozilla contributor for a couple of years now, mostly on JavaScript docs, occasional bug triaging and commenting. I'm currently contracting for Mozilla to document WebAPIs and I've decided to focus first on APIs available to non-certified app developers.

Before anything else, I'm cross-posting on both dev-b2g and dev-gaia because I'm not sure which of both is the relevant mailing-list. Feel free to drop the one that is not relevant from CCs if applicable. Apologies for the noise.

I've discovered on the devengage mailing list [1] that as of January 10th, remote debugging for FirefoxOS has been disabled. This is quite unfortunate, because remote debugging makes a tremendous difference in my work studying and documenting the APIs. It's also obviously a much needed feature for app developers.
A couple of questions remain unanswered:
* Why has this been decided?
* Is it planned to re-enable it in its previous form? a new form?
* Has a date or milestone been decided to fix this issue?
* If it takes too long to fix, what are the other ways to debug apps on an actual device?


Besides these questions to understand the current situation, I'd like to discuss a trend I'm noticing. I am under the impression that app developers are becoming a growing population of the FirefoxOS ecosystem especially with Mozilla increasingly reaching out to potential such developers (app days all over the globe in the upcoming weeks). I feel it will become increasingly important for this population to have a stable development environment and if for good reasons the environment can't be kept stable, alert this population of the upcoming change that may affect it.

Thank you very much,

David

[1] https://groups.google.com/d/msg/mozilla.engagement.developers/DuoPbjXqK48/EONYxwGrFQsJ
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to