Package: wnpp
Severity: wishlist
Owner: Stéphane Glondu
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ocaml-ma...@lists.debian.org
* Package name: ocaml-zarith-stubs-js
Version : 0.17.0
Upstream Contact: Jane Street
* URL : https://github.com/janestreet/zarith_st
> "Charles" == Charles Plessy writes:
Charles> Hi all, we are so diverse, that when the possibility of a
Charles> conflict of interest arises in a situation, it is too late,
Charles> because we are not even going to agree on what a conflict
Charles> of interest is, and how to
On Fri, 07 Feb 2025 17:08:44 +0100, Pierre-Elliott Bécue
wrote:
>I'd not, eg, expect some Canonical employee to refrain voting a GR
>because they might be biased. We all are biased.
Some call it bias, others call it opinion. It's fine.
Greetings
Marc
--
-
Package: wnpp
Severity: wishlist
Owner: Christopher Obbard
X-Debbugs-Cc: debian-devel@lists.debian.org, obba...@debian.org,
dmitry.barysh...@linaro.org, anders...@kernel.org
Package name: debugcc
Version : 0.0~git20240907.6444cf9-1
Upstream Contact: Bjorn Andersson
URL
Hi,
Le 2025-02-07 17:08, Pierre-Elliott Bécue a écrit :
I'd not, eg, expect some Canonical employee to refrain voting a GR
because they might be biased. We all are biased.
Another reason why it is a good practice to not take part in votes when
in a potential or actual conflict of interests s
[M-F-T set to -project; see https://cr.yp.to/proto/replyto.html ]
At 2025-02-07T17:08:44+0100, Pierre-Elliott Bécue wrote:
> I'm not sure I'd expect more from people than them saying who they
> work for or defend.
>
> I'd not, eg, expect some Canonical employee to refrain voting a GR
> because th
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: lomiri-location-service
Version : 3.3.0
Upstream Contact: UBports developers
* URL :
https://gitlab.com/ubports/development/core/lomiri-location-service
*
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: lomiri-indicator-location
Version : 25.2.7
Upstream Contact: UBports developers
* URL :
https://gitlab.com/ubports/development/core/lomiri-indicator-locat
Hey,
Charles Plessy wrote on 07/02/2025 at 10:10:20+0100:
> Hi all,
>
> we are so diverse, that when the possibility of a conflict of interest
> arises in a situation, it is too late, because we are not even going to
> agree on what a conflict of interest is, and how to handle the
> situation, b
Hi all and Jeremy,
first, I would like to apologise for sending my original email to the
wrong list,
Le Fri, Feb 07, 2025 at 07:47:35AM -0500, Jeremy Bícha a écrit :
>
> I interpret your explicit mention of Canonical in your original email
> as an attack
I am really sorry if my email sounded li
On Fri, Feb 7, 2025 at 4:10 AM Charles Plessy wrote:
> - Consider potential conflicts and be transparent when a decision might
>intersect with their employer’s, sponsor’s, or other affiliations'
>interests.
I don't see why this is needed. I am privileged to be paid by
Canonical to packag
> Thank you. I am unable to duplicate these issues with the information
> provided. Please report these as Debian bugs instead of on this
> mailing list.
I am planning to do more systematic and reproducible tests on a
dedicated system. I can file Debian bug reports if necessary, after
checking wit
* Andrew M.A. Cater [2025-02-07 12:27]:
[And it is somewhat ironic that this email contains
output from an AI while your signature requests that this
email not be used to train one :) ]
I for one applaud his attempt to protect our AI overlords from model
collapse [1] ;)
Cheers
Timo
[1] http
On Fri, Feb 7, 2025 at 6:08 AM Stephan Verbücheln
wrote:
> It was not distribution-level breakage but upstream bugs. I immediately
> observed multiple bugs in evolution:
> - Evolution started to forget various UI settings
> - icons were mixed up (showing incorrect icons in various places)
Thank y
On Fri, Feb 07, 2025 at 06:10:20PM +0900, Charles Plessy wrote:
> Hi all,
>
> we are so diverse, that when the possibility of a conflict of interest
> arises in a situation, it is too late, because we are not even going to
> agree on what a conflict of interest is, and how to handle the
> situatio
On Thu, 2025-02-06 at 14:48 -0500, Jeremy Bícha wrote:
> Please be specific about the breakage you are seeing. The best way to
> do this is to file bugs against affected packages instead of emailing
> this list.
It was not distribution-level breakage but upstream bugs. I immediately
observed multi
At 2025-02-07T09:32:35-, Sune Vuorela wrote:
> On 2025-02-07, Charles Plessy wrote:
> > Does that mean we should equip ourselves with a Conflict of Interest
> > Policy? Here is a suggestion drafted by ChatGPT.
>
> I'm not sure why I should spend time reading something you didn't
> bother wri
On 2025-02-07, Charles Plessy wrote:
> Does that mean we should equip ourselves with a Conflict of Interest
> Policy? Here is a suggestion drafted by ChatGPT.
I'm not sure why I should spend time reading something you didn't bother
write ?
/Sune
Hi all,
we are so diverse, that when the possibility of a conflict of interest
arises in a situation, it is too late, because we are not even going to
agree on what a conflict of interest is, and how to handle the
situation, before one could conclude if there is really a conflict of
interest. The
19 matches
Mail list logo
