On 7/6/23 12:10, Aoife Moloney wrote:
> That said, Fedora Legal has determined that if we collect any
> personally-identifiable data, the entire metrics system must be
> opt-in. Since we are only interested in opt-out metrics due to the low
> value of opt-in metrics, we must accordingly never colle
On 7/7/23 21:14, Naheem Zaffar wrote:
> On Sat, 8 Jul 2023, 01:08 Randy Barlow via devel, <
> devel@lists.fedoraproject.org> wrote:
>
>> On 7/7/23 19:59, Demi Marie Obenour wrote:
>>> That is not consent. The GDPR explicitly states that consent must
>>> be opt-IN.
>>
>> I agree.
>>
>> I think it
On Sat, 8 Jul 2023, 01:08 Randy Barlow via devel, <
devel@lists.fedoraproject.org> wrote:
> On 7/7/23 19:59, Demi Marie Obenour wrote:
> > That is not consent. The GDPR explicitly states that consent must
> > be opt-IN.
>
> I agree.
>
> I think it is important to make it possible for a user to as
On 7/7/23 19:59, Demi Marie Obenour wrote:
That is not consent. The GDPR explicitly states that consent must
be opt-IN.
I agree.
I think it is important to make it possible for a user to ask for the
data collected from their machine to be deleted in the event they
mistakenly submitted data,
On 7/6/23 21:17, Michael Catanzaro wrote:
> On Thu, Jul 6 2023 at 07:42:47 PM -0400, Demi Marie Obenour
> wrote:
>> Then make the metrics be neither opt-in nor opt-out. Have
>> “Enable telemetry (y/n)?” be a mandatory question in the
>> installer,
>> which the user must answer.
>
> The problem
On Thu, Jul 06, 2023 at 08:08:05PM -0500, Michael Catanzaro wrote:
> ... that would be sad since it would mean more work for me, but
> we're still at the point where that's possible. (I'd *much* rather make
> changes to the existing system to adapt it to our needs, though. :)
Oh, and I didn't mean
On Fri, Jul 07, 2023 at 16:15:14 -0500,
Michael Catanzaro wrote:
The local collection is a bit of a hole, but I like your suggestion to
put a short time limit on that. Perhaps we can collect for something
like one hour locally, then delete if the user has not consented to
upload before then
On Thu, Jul 06, 2023 at 08:08:05PM -0500, Michael Catanzaro wrote:
> But remember we do not want to keep information about individuals in the
> data set in the first place. It's easier to dodge privacy concerns if we
> just don't store such associations at all.
Sure, but the data still needs to le
Looking at the screenshot, I wonder what percentage of users will read
"Privacy", see that all the switches are on, and click "Next" in the
belief that all the privacy features are on.
Björn Persson
pgp2ZQzLUmMNa.pgp
Description: OpenPGP digital signatur
_
Michael Catanzaro wrote:
> The problem is if users are expected to answer, they are going to
> probably answer No and it's effectively the same as an opt-in. But if
> we have a default value, users will be inclined to leave the default
> value.
[...]
> Remember, for avoidance of doubt, we will N
Michael Catanzaro wrote:
> I would envision installing
> eos-event-recorder-daemon via a Recommends: from the
> gnome-control-center and gnome-initial-setup packages (and probably
> also by adding it to the workstation-product comps group), so if you
> don't have gnome-initial-setup or gnome-co
On Fri, Jul 7 2023 at 12:25:12 PM -0500, Bruno Wolff III
wrote:
Is there going to be a recommended way to not accidentally install
this stuff? I'm guessing the least work (for Fedora) would be to
black list the key packages in the repo files. Making available a
package that conflicts with them
On Fri, Jul 7 2023 at 12:03:14 PM -0500, Bruno Wolff III
wrote:
Note that collecting the data by default increases the harm if
someone accidentally enables telemetry and then notices the issue
after data is reported.
Is there going to be some time limit on the data that is stored and
not upl
Hello,
The license tag in the mirmon package (https://src.fedoraproject.org/rpms/
mirmon) was corrected from BSD to MIT in rawhide.
Regards,
Robby
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@list
On 7/6/23 10:14, Alessandro Astone wrote:
Is there any interest in providing the full older clang binary instead of just
compat libraries?
In my case, I'm working on an LLVM pass currently targeting LLVM15, and i can
use the llvm15 rpm to build it. But then I don't have a way to compile a C
so
On Thu, Jul 06, 2023 at 08:17:27PM -0500, Michael Catanzaro wrote:
On Thu, Jul 6 2023 at 07:42:47 PM -0400, Demi Marie Obenour
wrote:
Then make the metrics be neither opt-in nor opt-out. Have
“Enable telemetry (y/n)?” be a mandatory question in the installer,
which the user must answer.
The
>From what I read, the metrics accumulation has an option to turn off the
>collection, as well as the transmission
Sent from Yahoo Mail on Android
On Thu, Jul 6, 2023 at 8:53 p.m., Michael Catanzaro
wrote:
On Thu, Jul 6 2023 at 11:08:15 PM +0200, Björn Persson
wrote:
> As a non-user
Hi all
In some days, i will update SuperLU to the release 6.0.0
All related dependent packages will be rebuilt in a side-tag:
$ repoquery --whatrequires 'libsuperlu.so.5()(64bit)'
SuperLU-devel-0:5.3.0-4.fc38.x86_64
amg4psblas-serial-0:1.1.0-5.fc38.x86_64
armadillo-0:10.8.2-3.fc38.x86_64
freefe
On Thu, Jul 06, 2023 at 19:53:12 -0500,
Michael Catanzaro wrote:
Well this change proposal is for Fedora Workstation specifically.
That's in the title. :) I would envision installing
eos-event-recorder-daemon via a Recommends: from the
gnome-control-center and gnome-initial-setup packages (
On Thu, Jul 06, 2023 at 14:32:04 -0500,
Michael Catanzaro wrote:
On Thu, Jul 6 2023 at 08:19:07 PM +0200, Vitaly Zaitsev via devel
wrote:
All telemetry collection MUST be an opt-in feature (disabled by
default). I'm strongly against enabling it by default.
As explained in the proposal doc
On Thu, Jul 06, 2023 at 20:17:27 -0500,
Michael Catanzaro wrote:
Remember, for avoidance of doubt, we will NEVER enable telemetry
upload without the user's consent, which is indicated by either (a)
not flipping the telemetry switch in gnome-initial-setup to the off
position, or (b) flipping
On Fri Jul 7, 2023 at 15:56 +, Maxwell G wrote:
> Hi,
>
> Can the configured 5 minute delay between forum posting and email
> notifications going out be turned off?
> It disadvantages users who participate via email and is an unwelcome
> diversion from the way the mailing lists work.
s/diversi
Hi,
Can the configured 5 minute delay between forum posting and email
notifications going out be turned off?
It disadvantages users who participate via email and is an unwelcome
diversion from the way the mailing lists work.
--
Best,
Maxwell G (@gotmax23)
Pronouns: He/They
+1
Am 07.07.23 um 13:05 schrieb Kevin Kofler via devel:
"Privacy-preserving Telemetry" is an oxymoron. No such thing exists.
Telemetry is always an invasion of privacy, and as such, completely
unacceptable in a Free Software operating system. All the more if it is
mandatory or opt-out rather tha
Hi,
Since pkgconf is use by half Fedora , I'm sending this information to
devel mailing list , I hope not have any disturbance.
Best regards,
--
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel
On Thu, Jul 6 2023 at 09:27:47 PM +0200, Florian Weimer
wrote:
What about packages which already collect metrics and report them
somewhere (not necessarily to Red Hat)? Would these packages need to
change under this proposal? If not, how do we explain this to our
users?
No, packages that are
I actually copy-paste the Debian prompt since Debian Jessie on my systems.
Even though it uses blue-green colors, I can see it very well on both
white and black background.
I think it would be nicer if we played around with several options and
have the user have a simple way of choosing. There
I agree that blue is not good. It was impossible to read the welcome
messages during boot and startup. The cyan/teal is much better.
I typically use amber on black but sometimes use green on black so I'm
not sure that green would help those who also use green font color. For
me, on a black backgr
Hi,
I went through the thread and there are good points that I was not aware
of. But libuser is now pulled into every installation and considering the
state of the library (not being developed) I still think we should do
something about it. The benefit is small for tools like passwd.
The passwd u
Once upon a time, Vít Ondruch said:
> Shouldn't blue be the default for Fedora?
Blue is probably a bad idea in a prompt, as the human eye doesn't
perceive blue as strongly as green. The prompt isn't about art/style,
it's purely about functionality.
--
Chris Adams
__
* Florian Weimer:
> * Tulio Magno Quites Machado Filho:
>
>> Florian Weimer writes:
>>
>>> Today, I pushed a redhat-rpm-config update to rawhide,
>>> redhat-rpm-config-260-1.fc39. The only expected change is that
>>> -Wno-complain-wrong-lang now shows up in %optflags (but not
>>> %build_cflags e
Richard Shaw wrote:
> So it looks like upstream has no intention of supporting Python 3.12 in
> Pyside2 (5.15.x series), only in Pyside6 which AFAIK requires Qt6.
>
> https://bugreports.qt.io/browse/PYSIDE-2388
>
> Porting is non-trivial and Python upstream does not provide a porting
> guide.
>
On Fri, Jul 07, 2023 at 01:38:08PM +0200, Vít Ondruch wrote:
> >
> > There seems to be a general desire to have a colored prompt like other
> > popular distros, which commonly use green
>
>
> Shouldn't blue be the default for Fedora?
>
> And I think that dark as well as light color schemes shou
Dne 05. 07. 23 v 11:25 Aoife Moloney napsal(a):
https://fedoraproject.org/wiki/Changes/Color_Bash_Prompt
== Summary ==
Introduce a default colored prompt for Fedora's default shell bash.
== Owner ==
* Name: [[User:Petersen| Jens Petersen]]
* Email:
== Detailed Description ==
For a long ti
So it looks like upstream has no intention of supporting Python 3.12 in
Pyside2 (5.15.x series), only in Pyside6 which AFAIK requires Qt6.
https://bugreports.qt.io/browse/PYSIDE-2388
Porting is non-trivial and Python upstream does not provide a porting guide.
https://docs.python.org/3/c-api/unic
"Privacy-preserving Telemetry" is an oxymoron. No such thing exists.
Telemetry is always an invasion of privacy, and as such, completely
unacceptable in a Free Software operating system. All the more if it is
mandatory or opt-out rather than opt-in (but I also consider all those
obnoxious "plea
On Fri, Jul 07, 2023 at 12:41:00PM +0200, Leon Fauster via devel wrote:
> Am 07.07.23 um 12:19 schrieb Richard W.M. Jones:
> > On Thu, Jul 06, 2023 at 05:10:24PM +0100, Aoife Moloney wrote:
> > > Important process note: we are experimenting with using Fedora
> > > Discussion as part of the Changes
Am 07.07.23 um 12:19 schrieb Richard W.M. Jones:
On Thu, Jul 06, 2023 at 05:10:24PM +0100, Aoife Moloney wrote:
Important process note: we are experimenting with using Fedora
Discussion as part of the Changes process. Change announcements (like
the one you are reading right now) will still be se
On Thu, Jul 06, 2023 at 10:26:17PM +0200, Frantisek Zatloukal wrote:
>
>
> On Thu, Jul 6, 2023 at 9:58 PM Vitaly Zaitsev via devel <
> devel@lists.fedoraproject.org> wrote:
>
> On 06/07/2023 21:32, Michael Catanzaro wrote:
> > As explained in the proposal document, we know that opt-in me
On Thu, Jul 06, 2023 at 05:10:24PM +0100, Aoife Moloney wrote:
> Important process note: we are experimenting with using Fedora
> Discussion as part of the Changes process. Change announcements (like
> the one you are reading right now) will still be sent to the
> devel-announce mailing list, but t
Announcing the creation of a new nightly release validation test event
for Fedora-IoT 39 RC 20230707.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_pl
Assuming the goal is to improve fedora, that would be pointless as
telemetry rarely produces useful results as opt-in. It makes sense to have
it opt-out, but I'd expect the telemetry output and inputs to be open and
available for fedora developers.
Regards,
Nikos
On Thu, Jul 6, 2023 at 8:19 PM V
OLD: Fedora-Rawhide-20230706.n.0
NEW: Fedora-Rawhide-20230707.n.0
= SUMMARY =
Added images:1
Dropped images: 1
Added packages: 4
Dropped packages:0
Upgraded packages: 152
Downgraded packages: 1
Size of added packages: 2.35 MiB
Size of dropped packages:0 B
* Aoife Moloney:
> == Dependencies ==
>
> Any package that wishes to collect a metric would need to depend on
> eos-metrics. For example, if we were to collect statistics on which
> system settings panels are used most frequently, then the
> gnome-control-center package would need to depend on eos
Hi,
I have updated the license on the "lazpaint" package. [0]
LazPaint is an image editor, and a leaf package with no dependents.
a) LGPLv2 -> LGPL-3.0-only
I missed upstream switching from v2 to v3 at some point.
b) Dropping Boost
The Boost license is only relevant to some test files,
No files
* Tulio Magno Quites Machado Filho:
> Florian Weimer writes:
>
>> Today, I pushed a redhat-rpm-config update to rawhide,
>> redhat-rpm-config-260-1.fc39. The only expected change is that
>> -Wno-complain-wrong-lang now shows up in %optflags (but not
>> %build_cflags etc.). It should prevent For
46 matches
Mail list logo
