[MeeGo-dev] [MeeGo-touch-dev] libmeegotouch 0.20.44-1 has been tagged.
viroteck at viroteck.net
Fri Sep 24 03:53:34 PDT 2010
[moving this discussion back to meego-dev as well, as I know there
were a number of people following the discussion there]
Thanks for your perspective. Replies inline.
On Fri, Sep 24, 2010 at 12:51 PM, Eero Tamminen <eero.tamminen at nokia.com> wrote:
> 1) Nokia developers have to track the internal bug tracker anyway.
> (With this argument you're actually saying they shouldn't participate
> in public one...)
The closed application developers, sure.
People who are working on open components should *not* need to know
about bugs in closed applications. They should be worrying about their
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
- 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
- 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.
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.
I'll repeat what I've said earlier in that yes, this will make life
slightly more difficult for developers on closed Nokia projects in
terms of dependencies between bugs and so on, but this is *already*
going to be the case for other open components, so it should not be
(Just finally, this is all hypothetical: excuse my repetition, but if
I don't keep emphasising this, someone might misinterpret what I'm
> I've participated on this stuff in the bugs.maemo.org and I don't see
> this as major obstacle because reported public bugs are so few compared
> to what we handle internally.
Consider, that this might at least be partially be a case of cause and
effect. After a while, the novelty of filing bugs who go through a
third party (and in a lot of cases, still don't get a reply even with
that bridge) probably starts to wear a bit thin.
> 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.
> - Eero
> (Note: I'm not involved in MTF development.)
More information about the MeeGo-dev