Re: [Mesa-dev] libGL not build but opengl=true option is set
You are right, building with -Dx11=disabled don't require any X11 dependency. Thanks a lot !On Mar 13, 2021 2:52 PM, Michel Dänzer wrote: > > On 2021-03-12 7:46 p.m., Quentin SCHIBLER wrote: > > GLVND depends on several X librairies. > > Even if you build libglvnd with -Dx11=disabled ? > > > -- > Earthling Michel Dänzer | https://redhat.com > Libre software enthusiast | Mesa and X developer ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote: > TLDR; I'm proposing to standardize on US English in our public-facing > documentation. +1 J.A. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand wrote: > Three comments: > > 1. +1 > 2. Khronos has generally standardized on American English in their > specs so I guess that provides some sort of prior art or something. > 3. I'd generally be a fan of encouraging American spellings in common > code as well. As someone who doesn't use auto-complete, having to > remember which variable is named "color" and which is "colour" would > get painful. Fortunately, we don't have a whole lot of variation here > but it'd be good to keep consistency. 4. UK English is unarguably correct and better. 5. That doesn't change point #3 in particular; just like coding style, one 'bad' choice is better than no choice at all. Cheers, Daniel ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
On Tue, 2021-03-16 at 10:06 +, Daniel Stone wrote: > On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand > wrote: > > Three comments: > > > > 1. +1 > > 2. Khronos has generally standardized on American English in their > > specs so I guess that provides some sort of prior art or something. > > 3. I'd generally be a fan of encouraging American spellings in > > common > > code as well. As someone who doesn't use auto-complete, having to > > remember which variable is named "color" and which is "colour" > > would > > get painful. Fortunately, we don't have a whole lot of variation > > here > > but it'd be good to keep consistency. > > > > 4. UK English is unarguably correct and better. Actually, strike all of the above, and let's write all docs in Norwegian Bokmål instead. Or even better, Esperanto! > 5. That doesn't change point #3 in particular; just like coding > style, one 'bad' choice is better than no choice at all. Yeah, so I don't oppose consistent language in code and comments either, but I suspect that's a bit harder to change or get agreement on. For instance, it seems both Panfrost and Nouveau use quite a bit of UK English, whereas AFAICT most other drivers use mostly US English (mostly based on grepping for "color" vs "colour", so a very flawed metric indeed, but whatever). I simply don't want to hold back a decision about the docs due to something that might be harder to agree about. Color me self-serving here, I guess ;) ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
Just one detail to fill in: I just got a question on #dri-devel if this suggestion would place an additional burden on most developers to additionally look up every word of new documentation to see if it's US or UK English. I'm not proposing to place any additional burden on people writing docs. I think it's fine if people do a best-effort (which arguably can be low; this isn't a very important detail), and then we'll either catch things during reviews or fix it up afterwards. It's not like the Mesa docs are perfect in terms of spelling or grammar anyway, I just want to resolve which of the forks in the road we follow trying to clean things up ;) On Mon, 2021-03-15 at 13:44 +0100, Erik Faye-Lund wrote: > TLDR; I'm proposing to standardize on US English in our public-facing > documentation. > > I proposed an MR a while back that changed the only occurrence of the > UK English spelling "optimisation" for the US English spelling > "optimization", which is already used 34 times in the docs. I've done > similar changes in the past. > > But this time Ian brought up the good point that picking a preferred > language should probably be done using group consensus on the mailing > list than just picking what's currently most popular. > > So, I hereby propose to pick US English as our default language for > user-facing documentation. > > I'm not proposing to force anyone to use a particular English variant > for things like comments, commit messages or variable names. I don't > think there's much value in enforcing that, and I think it'd be > perfectly fine if any particular driver wanted to pick a particular > variant of English. > > The main reason I want to standardize on an English variant is that > I'm > trying create a word-list for domain-specific/technical language to > detect spelling mistakes in the docs more easily. And not having to > add > both US and UK English words makes this list easier to maintain. I'm > not planning on going 100% systematically though the dictionary to > detect UK English words that might be in my system dictionary, just > to > fix the words that currently cause me (a tiny amount of) pain ;) > > The main reason why I'm proposing US English over for instance UK > English is that this seems to be the dominant variant currently in > the > documentation. So it seems like the pragmatic choice to me. > > Thoughts? Any objections to sticking to US English in the docs? > > The MR in question: > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8572 > > Ian's response: > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8572#note_808593 > > Previous changes: > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6864 > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6894 > > > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
On March 16, 2021 05:06:53 Daniel Stone wrote: On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand wrote: Three comments: 1. +1 2. Khronos has generally standardized on American English in their specs so I guess that provides some sort of prior art or something. 3. I'd generally be a fan of encouraging American spellings in common code as well. As someone who doesn't use auto-complete, having to remember which variable is named "color" and which is "colour" would get painful. Fortunately, we don't have a whole lot of variation here but it'd be good to keep consistency. 4. UK English is unarguably correct and better. 😝 5. That doesn't change point #3 in particular; just like coding style, one 'bad' choice is better than no choice at all. I have three words for you: three space tabs. Yeah... It may be a good style but consistency is good. 🤪 --Jason ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
On Tue, 16 Mar 2021 at 13:08, Jason Ekstrand wrote: > On March 16, 2021 05:06:53 Daniel Stone wrote: > >> On Mon, 15 Mar 2021 at 20:54, Jason Ekstrand >> wrote: >> >>> Three comments: >>> >>> 1. +1 >>> 2. Khronos has generally standardized on American English in their >>> specs so I guess that provides some sort of prior art or something. >>> 3. I'd generally be a fan of encouraging American spellings in common >>> code as well. As someone who doesn't use auto-complete, having to >>> remember which variable is named "color" and which is "colour" would >>> get painful. Fortunately, we don't have a whole lot of variation here >>> but it'd be good to keep consistency. >> >> >> 4. UK English is unarguably correct and better. >> > > 😝 > > 5. That doesn't change point #3 in particular; just like coding style, one >> 'bad' choice is better than no choice at all. >> > > I have three words for you: three space tabs. Yeah... It may be a good > style but consistency is good. 🤪 > Absolutely. Apparently I forgot to write the final line which is that I think standardising on US English across the board is a good thing, even though I personally like it about as much as three-space tabs. As you can see from the previous sentence. ;) So, +1 from me too. Cheers, Daniel ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] 2021 X.Org Foundation Election Candidates
Correction, we have 7 candidates for 4 positions. I seem to have overlooked Walter Harms's nomination email. My sincerest apologies. His personal affiliation, statement of contribution, and personal statement are below. The full slate of candidates can be found at https://wiki.freedesktop.org/xorg/BoardOfDirectors/Elections/2021/ ## Walter Harms __Current Affiliation:__ Scientist @ Bundesamt für Strahlenschutz __Statement of Contribution:__ I am involved into the open source since studying physics several years ago. I am also certified trainer for programmers. I contributed in the last years to projects like linux kernel, man pages, etc. Since a few years i have commit rights for X11 and did some work on libX11 and libXt. __Personal Statement:__ Since i started to become a trainer i have a predilection for documentation. Xorg has a lot good documentation but today is it less. NTL what is important is the application. I would like to see more training material and more X11 applications especially for remote access. But i was never involved in the xorg organisation. So i see myself more as an apprentice. We will see if i can help. Thanks, Harry Wentland, on behalf of the X.Org elections committee On 2021-03-15 2:47 p.m., Harry Wentland wrote: To all X.Org Foundation Members: The election for the X.Org Foundation Board of Directors will begin on 22 March 2021. We have 6 candidates who are running for 4 seats. They are (in alphabetical order): Samuel Iglesias Gonsálvez Manasi Navare Lyude Paul Rodrigo Siqueira Lucas Stach Daniel Vetter Attached below are the Personal Statements each candidate submitted for your consideration along with their Statements of Contribution that they submitted with the membership application. Please review each of the candidates' statements to help you decide whom to vote for during the upcoming election. If you have questions of the candidates, you should feel free to ask them here on the mailing list. The election committee will provide detailed instructions on how the voting system will work when the voting period begins. ** Election Schedule ** Nomination period Start: Mon 22nd February Nomination period End: Sun 7th March Publication of Candidates & start of Candidate QA: Mon 15th March Deadline of X.Org membership application or renewal: Thu 18th March Election Planned Start: Mon 22nd March anywhere on earth Election Planned End: Sun 4th April anywhere on earth ** Election Committee ** * Eric Anholt * Mark Filion * Keith Packard * Harry Wentland Thanks, Harry Wentland, on behalf of the X.Org elections committee ** Nominees ** ## Samuel Iglesias Gonsálvez __Current Affiliation:__ Igalia __Personal Statement:__ I have been contributing to Mesa and piglit for 7 years improving open-source drivers for both OpenGL and Vulkan. During my time on the board, I have become the XDC organization coordinator and the XDC CFP committee chair, due to my experience organizing the XDC 2018 in A Coruña, Spain. Thanks to these experiences, I have been deeply involved in the XDC organization process, where I have helped make a great and welcoming conference every year. If I am elected, I plan to continue leading both the XDC organization process and the XDC CFP committee. ## Manasi Navare __Current Affiliation:__ Intel __Statement of contribution:__ I am a lead contributor to Intel’s Open source graphics kernel driver i915 as well as to the Linux Kernel DRM subsystem. One of my most widely used contributions is the Display Port Compliance code in i915, DRM as well as in Xserver and IGT to make the entire graphics stack Display Port compliant and reward the end users with black screen free displays. I have also enabled features like Display stream compression across DRM and i915 as per VESA’s DSC specification for Display Port. Most recently I have been working with both the DRM and i915 community as well as the AMD developers to implement and enable adaptive sync feature for variable refresh rate on display drivers for enhanced gaming experience. I also have commit rights to several upstream projects like drm-intel, drm-misc and Intel GPU Tools. I have served on X.org board of directors for last 2 years organizing XDC conferences, being on Code of Conduct committee for X.org and Freedesktop and taking over the treasurer responsibility since September 2020. __Personal Statement:__ I have been a Linux Open Source contributor for last 7 years since I joined Intel's Open source technology center. My major contributions are in enabling display interfaces and develop display features in upcoming display specifications in i915 and Linux DRM subsystem. I have presented several talks at Linux Graphics conferences like Embedded Linux Conference, XDC and FOSDEM on several graphics display features like Display Port compliance and Display Stream Compression, Tiled display support, Adaptive Sync or Va
Re: [Mesa-dev] docs: consistent language
Hi, On Mon, Mar 15, 2021 at 01:44:18PM +0100, Erik Faye-Lund wrote: > The main reason I want to standardize on an English variant is that I'm > trying create a word-list for domain-specific/technical language to > detect spelling mistakes in the docs more easily. Are you aware of codespell[1]? It already contains a list of common spelling mistakes, and supports an exclusion list for domain-specific words we want to keep, for instance we don’t want to “fix” LOD → LOAD so we can write LOD in a file and pass --ignore-words=that-file when running it in CI. [1] https://pypi.org/project/codespell/ -- Emmanuel Gil Peyrot signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
