On 3/19/2011 1:28 AM, Frans Meulenbroeks wrote:
2011/3/19 Richard Purdie<[email protected]>:
On Fri, 2011-03-18 at 10:15 +0000, Phil Blundell wrote:
On Fri, 2011-03-18 at 08:57 +0100, Frans Meulenbroeks wrote:
2011/3/17 Richard Purdie<[email protected]>:
On Thu, 2011-03-17 at 19:10 +0100, Michael 'Mickey' Lauer wrote:
I'm in favor of keeping it, cleaning it up, and improve
the integration with patchwork / git. Throwing it away
would be a very bad sign to all those countless people
who've gone through the pains of actually working with
the bugtracker.
The simple question is who is actually going to sort out the mess its
in?
Who is going to look after it on a continuing basis?
If there isn't ownership, nothing is going to change.
Actually I feel the real problem is that:
- people did not want to get bugs assigned to them (at least that was
what someone told me in the past)
- we're lacking a good notion of package or recipe ownership, so even
if we had someone acting as a bug manager, (s)he would have a hard
time to find out who to assign an issue to.
Yes, agreed. A few people have tried in the past to take responsibility
for bugzilla itself (in infrastructure terms) and I would be happy
enough to do that for the future. But it clearly is not reasonable to
expect the Bugzilla maintainer(s) to be personally responsible for
fixing every bug that gets reported.
This is the key question. Who is responsible for fixing bugs?
The recipe's original author?
The maintainer?
The reporter?
The bugzilla maintainer?
The TSC?
The answer in general is whoever has time and an interest in it and none
of the above.
Well, I do feel it is one of them, and that is the maintainer of the
package (who might be the original author).
To me being the maintainer of a recipe says that one cares about a
recipe and tries to maintain it (as the word says :-) )
Maintainership comes with responsibilities. If people do not want to
take these responsibilities then they should not list themselves as
maintainer.
I have seen too many incidents where someone does not care about a
package or bugs submitted to it, but if someone else steps in and
fixes things, then suddenly the original author or maintainer feels
they are stepped onto their toes, and react hostile.
Its always good to get reviews from people who have prior experience
even if it comes in ways you don't like since in the end it makes the
software better. A little attitude adjustment is however needed sometimes :)
Btw this is the main reason I stopped trying to fix bugs that do not
affect me (apart from the recipes I maintain).
Thats pretty selfish view of world I must say in a community of
volunteers :)
-Khem
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
