It is neither a question of overblowing or "paranoia", (thanks for the
gratuitous comment by the way, in tdf#147130), but I raised the issue as
to where bugs for Collabora should be reported when it was first
released via the AppStore and was told, multiple times, and no less by
Michael Meeks himself, to report them in the LO BZ.
Seemingly, and without any other form of policy discussion, that has now
changed.
Where is the due process in that decision ?
This is the problem I'm pointing out.
Secondarily, accusing people of abusing TDF resources in bug reports
(whether they take it personally, or whether it is directed more
generally at Collabora) doesn't help the situation IMHO.
Alex
Le 15/06/2022 à 09:56, Adolfo Jayme Barrientos a écrit :
It is sad how you're willing to misinterpret and overblow it, Alex.
Collabora Office is a downstream (i.e. derived) project of
LibreOffice, and although it is based on the same codebase, it may
have its own bugs.
It is not fair for unpaid, volunteer triagers to spend time triaging
their software's bugs in a bug tracking system pertaining to a
different project, that is all. The NOTOURBUG status is meant to
indicate that the bug simply needs to be moved to a more appropriate
instance, as we do with e.g. snapcraft-related issues, which I triage
on Launchpad.net. NOTOUTBUG does *not* mean that your bug is invalid.
I am sorry because I am terse in my non-native languages, but really,
there is no conspiracy behind it. I translate Collabora's software for
free, but as you may note, they host their Weblate platform
independently from TDF's -- their Jenkins is similarly separately
hosted; their online help site is, too. For GOOD REASON.
Adolfo
--
To unsubscribe e-mail to: [email protected]
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy
