https://bugs.documentfoundation.org/show_bug.cgi?id=159766
--- Comment #12 from `{third: "Beedell", first: "Roke"}`{.JSON5}
<[email protected]> ---
(In reply to Buovjaga from comment #11)
> (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #10)
> > (In reply to Buovjaga from comment #9)
> > > (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #8)
> > > > Why *not* have work tracked? Your opinions appear contradictory to
> > > > themselves, and certainly at odds with how the rest of not merely this
> > > > Bugzilla instance (see my other filed bugs and their discussions) but
> > > > all
> > > > other Bugzilla instances I've used operate.
> > >
> > > Because tracking adds overhead, not everything needs to be tracked. If you
> > > want to influence TDF staff management, contact the board of directors and
> > > give feedback.
> >
> > How is that a better method than a bug? Regardless, I consider this worth
> > tracking, so if it's just your versus my personal opinions rather than an
> > organizational policy, I don't see why it should be considered
> > authorititive.
>
> It is how infra team is handling things so far and the directors have never
> seen it necessary to change it. Of course you are free to exceptionally open
> a ticket and I can take it for my own task to update it to avoid infra team
> having to spend time on it. But if you want to expand this to a new policy
> requiring the infra team to ticket any and all web app updates, then you
> have to prepare for a wider discussion.
I do believe that what you describe would be best, at least for significant
changes obviously worth tracking, but that wouldn't be within the perview of
this. If ever I were to decide to take it upon myself to create an issue to
discuss that, I would consider my reasoning very carefully, so its description
would be more verbose than this issue's is.
Regardless, would you consider taking this issue, as you describe? I would be
incredibly thankful.
--
You are receiving this mail because:
You are the assignee for the bug.
