Sorry, I'll answer only part of your mail, as I don't see myself wise
enough to comment everything you've written. That does not mean I
disregard the part I deleted.

Le 12/02/2014 16:12, Adrian Custer a écrit :
>
>
> A primary need, from my point of view, is taking the B2G project from
> the current, fragile, undocumented, sloppily structured system to an
> industrially robust, modular, fully documented build tool for all
> users: mozilla developers, telephony partners, community hackers, and
> web app developers who just need a latest build. 
> I spent December working on a bash script infrastructure for such a
> project and then got bogged down for the nth time in the mess and
> stopped, discouraged. 

Have you filed a bug for your work? Would be nice to post your current
work somewhere so that you or someone else can pick it up later...

> I gave up when I discovered that my manifest was downloading the
> gigabytes of Linux kernel and associated libraries but was then
> silently skipping the compile.

have you filed a bug about this?

> Eventually, I'll work up the energy again to delve into the mess and
> maybe make progress; however, I suspect that I will never actually
> successfully build FxOS for the OneTouch Fire. It's too bad because it
> is a decent developer phone.
>
> A secondary need will be to resolve the GPL violations. My current
> plan on that is to write the board of the Mozilla Foundation asking
> for advice. I presume they would rather resolve this themselves
> through back channels in a friendly supportive process since keeping
> the telephony partners happy is critical to the ongoing success of
> FxOS. However, I also suspect they will fail to assign anyone to work
> on it or fail to sustain the effort necessary to make it happen.
> (After all, technically this is not their problem.) That will mean we
> are left to work through other means, probably contacting the Linux
> Foundation, FSF, and SFLC, and possibly eventually end up in court. If
> I have the energy for it, I guess that I'll learn how the court system
> works in this country. (A minor hiccup in this plan is that Mozilla
> does not actually offer any contact point for the Board of Directors
> that I have yet been able to find, a lovely testimony to how little
> they look at themselves from the point of view of the outside community.)

I don't know for this, but I found a legal contact point specifically
about copyright on the legal page:
http://www.mozilla.org/en-US/about/legal.html

>
>
>
> In the mean time, I would actually encourage you to not file any
> bugs---it will end up being stressful without helping anyone. If you
> have a 1.2 device and the developers have all moved on to 1.4, we
> really can't help each other. 

1.2 is actually kinda old now, but if you find bugs on 1.3 it's actually
helpful to file bugs now.
(I know you don't have a 1.3 device, I'm just saying)
1.2 is also much closer to 1.3 than 1.1 was to 1.2, so it might still be
useful to file bugs about 1.2.

> At best, they might eventually tell you 'works on newer xxx' which
> will be of no utility to you and you won't be able to know if they
> even understood your bug to begin with and if it has indeed been fixed.

I don't know if that's the same for other components, but for the
Messages app I always try to find the duplicated bug that fixed the
issue, if any.

> So save yourself the effort and grief, and save the work on bug
> triage. Bugs are now features.

I don't understand this. We use bugzilla for everything: features,
little bugs, big bugs, uploading a SSH public key, opening accesses to
some servers, etc.


Regards,
-- 
Julien

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to