Hi Tom,
On 2016-10-10 03:00, Tom Farrow wrote:
I'd like to remind that this is a governance mailing list. Participatory
challenges and issues are better suited to the relevant teams, and Mozilla's
participation team, especially while it's unclear whether there is a wider
governance issue here
I'd propose that if you really want to tackle your difficulties, you discuss
them with both the bugzilla team and the participation team.
This thread is become quite large and the discussion isn't the style people
typically associate with this list.
I do understand fully your difficulties, and hope that you find a solution for
them, just, (correct me if I'm wrong), this probably isn't the ideal place.
Maybe a more clarified issue will come back to this list if it's actionable by
governance.
I have not yet had the chance to consult an ITS over a long period of time without noticing reports of persisting issues being closed (without due diligence). Although BMO does not allow contributors to manipulate reports other than their own by default, Mozilla is understandably not an exception to that unfortunate rule. I would hope that all of the BMO governance issues I exposed could indeed have been solved without having to report to this list. But the fact that a volunteer who does not directly contribute to Mozilla on a regular basis like myself could notice that many issue tracking issues can also be considered as a meta-meta-issue. Mozilla is a mature project; such issues should be rare. Considering that Mozilla has a net income of several millions of USD-s, this might be an occasion for management to re-evaluate whether enough of these funds are allocated to issue tracking. A burnt out workforce could raise the rate of inappropriate ticket treatments, in particular
if there is no process to identify such victims.
And even if all of the BMO issues could have been fixed, some of the items are
not caused by BMO governance. Item 2 (and perhaps 1) has nothing to do with ITS
management, but with development processes and/or quality assurance. A
volunteer like myself should never experience 6 unreported bugs in the same
product in less than one month, when Mozilla has been marketing that product as
stable for more than a decade. I know that was triggered by item 1, and I was
cleaning up for a period of time during which I used Thunderbird
professionally, but still. By the way, I have heard of plans to move
Thunderbird away from Mozilla's umbrella. I find this unfortunate, but if
Mozilla is confident that Thunderbird's situation cannot improve promptly, part
of my report can be considered as support for that plan.
Thank you, I do not remember hearing about the Participation team, and this
discussion is related to the team's declared mission and principles. After
looking at the team's activities and goals, I am under the impression that the
team is mainly focused on recruitment, and less on retention and management,
but I agree it would be good to at least inform the team about this discussion.
Feel free to do that. For my part, since it appears to be impossible to do that
via email, and since I have never contributed to the Discourse site used by the
team, I will refrain from doing so at this point (I am not a fan of mailing
lists, but this discussion was already started on one, and while I am curious
about Discourse, I am reluctant to invest time discovering a system which is
not clearly powered by free software).
I am not sure why your reply comes in this sub-thread, but my original message
was sent to both bugmast...@lists.mozilla.org and this list (although it still
doesn't show on the former, which - I'm afraid - may be more evidence that
addressing the governance list was not superfluous). I would probably have gone
to the participation team before reaching the governance list had that been
suggested. If you think the participation team can help with such issues,
please either:
1. Ensure that affected contributors are notified when their BMO account is
disabled, and that the notice points to the participation team.
2. Point to the participation team in the message displayed when trying to
connect to BMO using a disabled account.
Any of these would be a huge progress on the issue I reported in item 10.
By the way, your team's strategic plan is currently confidential. I hope a team
which promotes openness does not voluntarily hide that document, but if so, it
would be good to make that clear on the wiki page which links to it (
https://wiki.mozilla.org/Participation ).
I appreciate your constructive intervention. If the participation team can help
with BMO accounts, that would be a great start.
On Sunday, October 9, 2016, Filipus Klutiero <chea...@gmail.com
<mailto:chea...@gmail.com>> wrote:
Hi Svetlana,
On 2016-10-09 05:33, Svetlana Tkachenko wrote:
Good day,
When someone disagrees, pace down and come back to it later; don't keep
working on them (or the issue) in frustration. From my observation
failing to do this has contributed to a majority of bans on the
Internet.
I agree that waiting can help, but could you clarify which person you are
talking about, and how long you think is optimal to wait before coming back?
Since Mozilla software is free, you are not obligated to stay on
bugzilla.mozilla.org <http://bugzilla.mozilla.org> -- you still can fix
these bugs within the
infrastructure of a new or existing fork.
Mozilla is one of the main projects which brought me to free software. I
have used Mozilla software for most of the 13 years since I switched to the
good old Mozilla Suite. In any case, forking an organization as known as
Mozilla should not be done lightly.
While the issues I exposed may be grave, the number of persons involved is
small relative to the number of contributors, and some of the meta-issues are
trivial to solve. I am far from thinking that the situation is hopeless.
However, I am not particularly aware of the project's status. If you think
this situation may carry on, would you recommend switching to a particular fork?
--
Filipus Klutiero
http://www.philippecloutier.com <http://www.philippecloutier.com>
_______________________________________________
governance mailing list
governance@lists.mozilla.org
https://lists.mozilla.org/listinfo/governance
<https://lists.mozilla.org/listinfo/governance>
--
--
*Tom Farrow*/
Participation Volunteer/
Mozilla
--
Filipus Klutiero
http://www.philippecloutier.com
_______________________________________________
governance mailing list
governance@lists.mozilla.org
https://lists.mozilla.org/listinfo/governance
