On Friday, June 14, 2013 9:20:31 AM UTC-7, Eric Shepherd wrote:
> On 2013-06-14 15:51:14 +, Gabriele Svelto said:
>
>
>
> > Will this documentation be oriented towards developers who might
>
> > actually want to work on the B2G core (gecko, gonk, platform stuff,
>
> > porting, etc...)?
>
On 2013-06-14 15:51:14 +, Gabriele Svelto said:
Will this documentation be oriented towards developers who might
actually want to work on the B2G core (gecko, gonk, platform stuff,
porting, etc...)?
Yes, some of it. This documentation is for people that want to work on
B2G core, porting,
> The biggest problem with this kind of documentation is that it always risks
> ending up outdated; how do we encourage developers to keep it up to date
> once it's done?
My response to this has been to put such documentation in the code
itself. As developers, our responsibility is to the code, a
On 06/14/2013 04:10 PM, Eric Shepherd wrote:
We may be contracting out to help get the core B2G docs up to date. By
that, I mean, things other than Web-facing stuff. Things like core
libraries, architecture, that kind of thing.
Will this documentation be oriented towards developers who might
a
We may be contracting out to help get the core B2G docs up to date. By
that, I mean, things other than Web-facing stuff. Things like core
libraries, architecture, that kind of thing.
Anyone aware of things that need documenting or their docs updated? I'm
building a list for the statement of wo
