jtojnar has quit [Read error: Connection reset by peer]
jtojnar_ is now known as jtojnar
lassulus has quit [Quit: WeeChat 2.0]
lassulus has joined #nixos-wiki
<makefu>
fadenb: again, i think these letters will primarily come for websites without any notice. nobody will go through the lenghts of court if there are still low hanging fruits
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-wiki
jtojnar has quit [Remote host closed the connection]
jtojnar has joined #nixos-wiki
balsoft has joined #nixos-wiki
lassulus has quit [Quit: WeeChat 2.0]
lassulus has joined #nixos-wiki
balsoft has quit [Remote host closed the connection]
balsoft has joined #nixos-wiki
<Mic92>
makefu: sounds like a lot of FUD to me
<Mic92>
Since there are so many affected by this law, there will be a solution soon.
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-wiki
<makefu>
I already prepared two letters. one for my employer and one for the caterer
<makefu>
best day
<fadenb>
Caterer? As in company preparing food?
<makefu>
yes
<makefu>
we have personalized cards for paying for the food. i want to know if they store personal data and if they do something with it
<fadenb>
Ah, at the customer site I am currently working one can use their access card to pay
<fadenb>
but you have to initialize it in the payment system first, I believe initializing means it reads the ID from the card and adds it to the credit database
<fadenb>
AFAIK our cards do not contain anything but an ID
<makefu>
well, if an ip address can be personally identifiable i guess that id can be as well
<fadenb>
not to our caterer, only security department can do the mapping
<joepie91>
fadenb: pseudonymous data is still covered under the GDPR, you just need to take measures to clearly define who can resolve it back to personally identifiable data, why they need to do so, and document all that
<joepie91>
so if it's "only the security department can map it back to persons, and that's necessary to detect fraud" and that's documented, then you're basically done
<joepie91>
(assuming you've taken the appropriate technical measures to make that statement true ofc)
<fadenb>
As the caterer and the company are different legal entities and the caterer has no access to any data I believe it is not categorized as personal data
<fadenb>
If they were the same company or would allow access to the data it would be pseudonymous data
balsoft has quit [Quit: balsoft]
<makefu>
fadenb: a personal identifier is still counted as indirect personal data
<nixoswikibot>
[[Workgroup:DataScience]] N https://nixos.wiki/index.php?oldid=2395&rcid=2418 * Ixxie * (+276) Created page with " This workgroup is dedicated towards improving the state of the data science stack in Nixpkgs. This includes work on packages and modules for scientific computation, artificia..."
<ixxie>
samueldr: maybe its time for another sprint on the wiki's core articles
<ixxie>
specifically tutorials
<samueldr>
ixxie: definitely would help, though such a sprint shouldn't be left open-ended, I think it should be planified with subjects pre-selected, and even lead-authors for sections of subjects
<samueldr>
I know that the install guide has to be written
<samueldr>
I still have the notes from the last sprint
<samueldr>
then I know that "what do I do after installing?" needs to exist, with use cases and known good setups for most cases
<ixxie>
exactly
<samueldr>
e.g. setting up a fully configured plasma, a fully configured gnome, xmonad, i3, awesome (select a few)
<samueldr>
then for common software
<ixxie>
first tutorials would be nice for that
<samueldr>
firefox/chrome, especially wrt chrome vs. chromium, then maybe something about firefox from mozilla's overlay
<ixxie>
so the NixOS tutorial could cover 'setting up a basic desktop environment'
<ixxie>
although maybe it fits better in the guide? I donno
<ixxie>
if the guides get you from "I read the article and understand the theory" to "I have set up some basic stuff with this tool" I think we did our job correctly
<ixxie>
and I guess the tutorials are more pedagogic in that they should be teaching you something theoretical by doing some practical excercise
<ixxie>
regarding to logistics I thought we could:
<ixxie>
1. craft the article outlines ourselves
<ixxie>
2. then create a sign up sheet somewhere (discourse?) for an 'adopt an article' program
<samueldr>
I definitely think configuring the system should be split from installation, while configuring follows installation, installation in itself is full of questions and different solutions :/
<samueldr>
(e.g. the installation guide should clearly explain the differences between installing on efi and legacy systems, as it is a recurring class of questions)
<samueldr>
Guide != first time users resources as far as I understand it
<samueldr>
or is it what's intended?
<ixxie>
but didn't we have the plan that the guides - say the NixOS guide - would have sections on installation, configuration and so on which summarize the main approach and link to full blow articles with more info?
<ixxie>
well I agree
<ixxie>
hmmm
<ixxie>
well I am not sure xD
<samueldr>
ixxie: in that specific case (nixos) the guide may need to be on multiple pages, but have the "NixOS Guide" page be the overview
<samueldr>
I mean, some of those sections are huuuge
<ixxie>
exactly
<ixxie>
but that is actually imo a nicer way to start than the manual
<ixxie>
A. read the Ecosystem overview article, decide what to start with;
<ixxie>
B. read the guide to get you started with installing and initial configuration
<ixxie>
C. read some tutorials to get deeper
<ixxie>
D. dig into the reference / cookbooks to get even deeper
<ixxie>
oh between A and B is reading the article of the component you picked
<ixxie>
samueldr: in a way it seems our existing main discussion articles are a lot like what I want guides to be
<ixxie>
which in a sense kinda what I wish the documentation was more like
<ixxie>
if we call the main articles the <guides> and these are just special discussion articles that provide a launchpad to other stuff then maybe its like: