Hi,
ext Robin Burchell wrote:
On Fri, Sep 24, 2010 at 12:51 PM, Eero Tamminen <[email protected]> wrote:
Let's take a small hypothetical example and say that Nokia have a
hypothetical web browser using Webkit with a hypothetical closed UI,
and it occasionally crashes when scrolling, due to a hypothetical bug
in webkit.
- The bug is reported internally at a Nokia tracker
- The Nokians responsible for the browser triage the bug, come to the
conclusion that the bug isn't in their closed UI code
- The Nokians create a test case, and open a bug at webkit.org
Note that:
- Webkit people do not need the logs, core dump, or any information
about the closed browser code
- They do need a way to reproduce the bug in *their* code, or, even
better: a patch fixing it.
What was the issue in that process?
This is hardly rocket science. I suspect that the only reason why it
isn't working this way is the developers are in the same company, and
have been using closed channels through inertia. Now, if for no other
reason than MeeGo trying to encourage other companies like Intel to
work in a partnership, open channels *should* be used.
Uh, I though things work like you described for components that
aren't maintained by Nokia?
(With the Webkit the problem is more that a lot of development is done
by Apple behind closed doors, I don't think they have open repos
for that development, just occasional code dumps. Correct me
if I'm mistaken.)
It just needs a "bug master" like on Maemo who makes sure that appropriate
triaging is done,
keeps these two things in sync as needed and prods internal people when needed.
Sounds sensible. Let's say that you're right about this: why not do it
the _other_ way around?
Report what can be publically reported in the open, and have someone
syncing the _public_ reports back to the _private_ tracker. I suspect
that this is probably the way it probably already is for every
component not controlled by Nokia.
And how do you differentiate which of the bugs are specific for
Harmattan[1] and which are for MeeGo? I think currently more of
the Nokia (MeegoTouch) development & testing effort happens for
Harmattan than MeeGo and I doubt MeeGo people would be very happy
if MeeGo bug tracker would be flooded by a huge amount of bugs that
may be specific to Harmattan and nobody's tested how much they
apply to MeeGo releases...
- Eero
[1] I.e. the Maemo based & MeeGo API compatible distribution that
uses Debian packaging and Busybox instead of GNU tools (among
other differences).
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
