Re: [Mesa-dev] docs: consistent language
On Mon, 15 Mar 2021 at 22:44, 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? All good, though I'm in the most likely to screw this up category, I'm never sure when to use s or z so it usually ends up being rather random, I think I've mostly got my outbreaks of colour under control. Dave. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] docs: consistent language
+1 to all of this. On Mon, Mar 15, 2021 at 1:54 PM 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. > > --Jason > > On Mon, Mar 15, 2021 at 12:59 PM Ian Romanick wrote: > > > > On 3/15/21 5:44 AM, 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. > > > > Over the years we've had quite a few contributions from folks in many > > different English spelling parts of the world where the UK spelling is > > the norm... though I don't think there have been that many from the UK > > itself. :) I suggested getting some group consensus because I didn't > > want any of those people to feel left out or undervalued. > > > > If anyone doesn't feel comfortable speaking out publicly about this, > > please feel free to contact Erik or me privately. > > > > > 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 > ___ > 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
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. --Jason On Mon, Mar 15, 2021 at 12:59 PM Ian Romanick wrote: > > On 3/15/21 5:44 AM, 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. > > Over the years we've had quite a few contributions from folks in many > different English spelling parts of the world where the UK spelling is > the norm... though I don't think there have been that many from the UK > itself. :) I suggested getting some group consensus because I didn't > want any of those people to feel left out or undervalued. > > If anyone doesn't feel comfortable speaking out publicly about this, > please feel free to contact Erik or me privately. > > > 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 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] 2021 X.Org Foundation Election Candidates
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 Variable Refresh rate kernel support for gaming and I have been already actively involved in IRC discussions with DRM and i915 maintainers to constantly provide any solution on display port questions and work on improving the kernel documentation and code quality. I have served on the X.org board of directors since 2019 helping in XDC 2019 and XDC 2020 organization and for ensuring the Code of Conduct on the X.org community and during XDC events. I have previously mentored for the KMS project in Outreachy 2018 winter program as well as administered the Google summer of code 2019 program and will continue to do so whenever I get an opportunity. I joined the Code of Conduct Freedesktop committee as well to ensure it is followed on all the Freedesktop projects and open source channels. I have recently stepped up to take over the treasurer responsibility as part of the X.org board and working with all our sponsors to get the invoicing for the X.org events. If I get elected I would like to continue being a treasurer managing the XDC sponsorship and invoicing responsibilities as well as continue serving on the Code of conduct committee for X.org and Freedesktop. In addition to this I would like to help out on XDC event website organization and promoti
Re: [Mesa-dev] docs: consistent language
On 3/15/21 5:44 AM, 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. Over the years we've had quite a few contributions from folks in many different English spelling parts of the world where the UK spelling is the norm... though I don't think there have been that many from the UK itself. :) I suggested getting some group consensus because I didn't want any of those people to feel left out or undervalued. If anyone doesn't feel comfortable speaking out publicly about this, please feel free to contact Erik or me privately. > 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
[Mesa-dev] docs: consistent language
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
