User Details
- User Since
- Nov 18 2014, 11:57 PM (488 w, 2 d)
- Availability
- Available
- IRC Nick
- mooeypoo
- LDAP User
- Mooeypoo
- MediaWiki User
- Mooeypoo [ Global Accounts ]
Wed, Mar 6
Feb 23 2024
Feb 21 2024
Summary from the MW Engineering Group after some discussion about this: As far as the MediaWiki Engineering side of things, this is done.
Jan 26 2024
This is an interesting question. I think that what will help think through this would be listing our the implication and impact of either option.
Jan 4 2024
This error looked extremely familiar to me, I believe this happens when OOUI isn't setup correctly.
Jan 3 2024
Nov 28 2023
Oct 30 2023
This is a really interesting feature!
Oct 10 2023
Sep 13 2023
This looks promising! And.... honestly, anything would have outlier issues in RTL. There will be cases you'll have to run around fixing no matter what you do (OOUI had that too) so you might as well start from something solid that gives you 90% of the functionality. In that aspect, I'd just verify it allows you to tweak / extend properly because you likely will have to with specific edge cases.
Aug 23 2023
Aug 22 2023
Jun 20 2023
Jun 15 2023
There is a theoretically conceptual way to fix this but I think it's too convoluted to be worth it.
Jun 14 2023
It all looks good to me (for some definition of good ;) -- the only thing I'd like to discuss and think about is the Artifact page. That page still has relevant documents, and some folks are adding to it. It could still be a good repository of analysis documents regardless of the existence of the team.
Jun 7 2023
Jun 1 2023
May 23 2023
May 19 2023
Okay, I have to admit, I completely didn't think about the option of only triggering the "save preference" when the user manually clicks the checkbox; I think in my mind I thought that the distinction (between explicitly clicking vs the programmatic change of state) wouldn't be as clear to users as to when the state is saved or not.
May 17 2023
This looks done to me, from 2018. Closing.
May 16 2023
It is never good to see a frustrated @Whatamidoing-WMF, and so in my explorations of RCFilters (in preparation for a planned hackathon project) I have decided to don my cape and try to help.
May 2 2023
Apr 25 2023
Mar 30 2023
Mar 27 2023
Mar 20 2023
Nov 2 2022
Oct 19 2022
Tracking ticket from Security: https://phabricator.wikimedia.org/T297791
Oct 10 2022
Oct 5 2022
Yeah, I think that's a good resolution.
I might need guidance as to what to do to make this happen...
Sep 9 2022
Aug 30 2022
I was thinking a lot about this ever since we talked about this problem, and so I would like to offer a slight point here about being careful of over-optimizing for this problem.
Jul 20 2022
Unfortunately, I'm in the same boat; I've never actually been directly involved in the project. I had a very passing general interest in it while working on another GraphQL project -- and I worked with the original maintainer! -- but I don't think I can serve as a maintainer on this (or even fix bugs...)
Apr 1 2022
Mar 14 2022
Feel free to share those wherever you deem fit :)
Mar 10 2022
Mar 9 2022
Another example for what I was trying to demonstrate is the "flipping" of the expected location of the negative sign
This figma file is absolutely incredible. For years we've been working on RTL support on the Wikimedia projects with some learnings and insights that were very rarely properly coalesced into a proper document with guidance and decisions, so having one being worked on not only as decisions for the specific Codex library, but as more widespread visual guidance is extremely helpful!
Feb 16 2022
Icons and RTL are one of my favorite topics of philosophical musings that lead to practical visual decisions -- but they're usually really complicated, as the discussion here demonstrates.
Jan 9 2022
Jan 8 2022
I'd love to try, but this is an interesting problem... I admittedly did not have a chance to go over any of the code yet, so I'm mostly offering some guesses here for now based on previous experience.
Dec 15 2021
Not only is netlify self hostable, it directly connects to a github repository and gives you a myriad of deploy tools, including an automatic pull request preview, A/B testing with two or more branches, deploy out of a specific branch, etc.
Dec 2 2021
Ah, localizing filenames on wiki, yes. One of the toughy questions, honestly.
Nov 15 2021
(Add) -- also, you'll need to take into account the ability to let component users (implementers?) force directionality for content (so, input direction regardless of interface) and also force and set based on interface. I know we all know this, I'm just pointing it out because it might get a bit more complex with the prefix selectors.
This sounds generally good plan, I'm slightly worried about how exceptions may work with logical properties, but I think they should work in general.
Sep 13 2021
Sep 3 2021
There's a lot of really good questions in this thread that are more about the general knowledge store than they are specifically about the data model (so just pointing out potential scope creep of the ticket specifically regarding the DSO) *but* I have some general points that I thought would be useful to raise in this context too.
Aug 11 2021
Another clarifying point is that this isn't about changing our internal nomenclature "deep inside our stack" - this is a solution that's meant for clients like Wikimedia Enterprise and a distribution method to provide a layer between the information we have in our databases that uses terms and nomenclature that are very specific to the Mediawiki operations, and translate that to consumers who want to digest pieces of the data using as much commonly "human digestible" terminology and structure as possible.
Jul 7 2021
Jun 30 2021
Yes to all of the above -- we definitely want to make sure we're iterating on a data model, and it's definitely important to decide on the standard. We do have a couple of artifacts touching on this and we'd love to share those.
We should make sure we choose a library that properly supports RTL. It seems Tailwind has support, but potentially a bit over complicated, see: https://github.com/tailwindlabs/tailwindcss/discussions/1492#discussioncomment-6061
Jun 14 2021
To be honest, my main pet peeve is that mediawiki is taking a choice that the user usually thinks is private (preferences), that is then used to show things differently only for them in their context - and then turning around and using it publicly.
Gender, sex, and language pronouns are three distinct notions. The article discusses some application of this, but the first sentence can't be clearer:
A gender symbol is a pictogram or glyph used to represent biological sex and gender in biology or medicine"
Jun 13 2021
Jun 11 2021
Jun 10 2021
Jun 9 2021
This is a fascinating discussion and I actually am not entirely sure I have a good answer to this. As a woman who speaks gendered language, this touches all my pet peeves at once, which would have been helpful to formulate an opinion, except some of those pet peeves are from one side and the others on the other.
May 26 2021
Correct. My "concern" is simply about the added abstraction of a compiler in javascript.
May 14 2021
From my personal perspective, and my experience with OOUI that was meant to be a shared library used by teams to create components, I am extremely intrigued by the potential benefits that TypeScript can offer with the IDE hints and developer-help that you've mentioned above. I think it might be worth exploring whether it's worth using TypeScript if not in the entire wvui library, then even only on the "lower/common" underlying code that others will rely on -- llike mixins and base components.
Jan 7 2021
I am not sure if you've done anything in the past couple of days, but I haven't encountered this issue anymore.
Jan 3 2021
Dec 7 2020
Re your notes, in reverse order:
Oct 28 2020
Oct 25 2020
Chrome and FF seem to be somewhat smart about the date and are rendering it properly in RTL