Kall good, that file is auto-generated
Kjust got included in your MR by accident
Kthe README stuff is still there as it should be
CAlso, it says that my build is behind some commits, but my pull request has been merged 
Kyeah you'll just want to hit the sync button
Kyours is behind because I just merged your changes, and others
CGotcha
CBy the way, is there a way I don't spam you guys? I think I have sent too many messages that may derail the chat group, sorry!
KYou're in the project chat and as far as I'm concerned that's project chat
KFine by me
KYou're welcome to make a thread if you prefer, but I don't mind
Jmake a thread if you want something indexed in google
COh well, I'll continue posting here :), I'm having some difficulties translating some terms, I'll try to use my best of judgment and select which terms should be translated and then add a context or don't translate them at all, like "rebase"
CThankfully, some of this terms come in the github docs which contains the correct way of translating them into Spanish
K
YouTubeawe
Curtis Mayfield - Move On Up
Original extended LP version from the album "Curtis" produced in 1970.
All rights reserved © Warner Bros. Records
Original extended LP version from the album "Curtis" produced in 1970.
All rights reserved © Warner Bros. Records
M2k by the end of the weekend at this rate
CHow funny, you can't translate this as is from GitHub, you'll have to change the language of GitHub for it to say Importante
CWho would have known that translating something made you research and learn so many things
KThat read me is orchestrated chaos
CFor example, I just added context about wtf is Compatdata
CI know I may be shooting myself in the foot, but maybe once there's an organized wiki, a glossary will be really helpful
MExtremely helpful. Lexicon is the first portion of understanding and giving people a common language.
Ti could probably do this actually
Tdefining some of the words the README says?
Tyeah i guess that isn't a bad idea
CYes
COverclocking, poll rate, compat data, rebase, those are the terms at the top of my head
CShaders too for example
CI have always believed that the main issue for the adoption of linux by the masses, is that we nerds overestimate how much common people know about the system
Toh, well some of those terms are not really specific to the project. overclocking and poll rate are very much general computer terms. compatdata is the WINE prefix which i try to explain poorly here: https://universal-blue.discourse.group/docs?topic=31#what-is-a-protonwine-prefix-11
now rebase should be defined sure
now rebase should be defined sure
Tyeah i get that
C...I believe theres a XKCD for that
Tthe never ending desktop linux hurdles
CYeah I get it, but nevertheless is mentioned in the readme and some people may be like "Huh?"
KAt some point I'm going to do a very nice looking website (I am biased)
KWhen that happens we'll have a much friendlier frontend
KWithout all the nerd shit
KLikely right after we get the installer sorted
Thonestly we need the attention of the nerds right now for the project to help on some other fronts too
KSince that's kind of a requirement for normal users
Tuniversal blue has grown significantly over the last 4 months, but even in linux circles, it's kind of unknown. but i sometimes think the linux circles are worried about other stuff
Tthat is fine however. the project will continue to grow and i think eventually once a lot of things get fixed upstream and we are in a good spot, things will change
Jonce people realize that you'll be able to switch between nvk and nvidia with a reboot via a single
justcheck the ISO thread for installer progress, we're close now. 
Toh is that in the works? that would be extremely convenient with the rapid progress of nvk recently
KWe get it for free
KNext Kernel release all non-nvidia builds will support NVK
Kswitching between it and proprietary is a rebase away
KAll the kargs are handled for you by our setup stuff
Jpeople still arguing about packages
