User Details
- User Since
- Sep 13 2022, 9:16 AM (28 w, 1 d)
- Availability
- Available
- LDAP User
- Hasan Akgün (WMDE)
- MediaWiki User
- Unknown
Today
Mon, Mar 20
Thu, Mar 16
Mon, Mar 13
Thu, Mar 9
Tue, Mar 7
Wed, Mar 1
We can only use overflow-wrap: anywhere; on item links and it solves wrapping problem without breaking table layout.
Tue, Feb 28
Feb 27 2023
When value input removed it gives another error as well.
Feb 23 2023
Feb 20 2023
Feb 14 2023
Jan 31 2023
I think everything is merged now.
Jan 5 2023
It seems like difference between desktop and mobile was because of the order and content of language codes array sent to Termbox renderer and right now it's already solved. Editing workflow on mobile can be changed within a day, IMO.
Dec 21 2022
I couldn't reproduce the order in "In more languages" section (desktop and mobile has the same order of items, both logged out). After talking with @ItamarWMDE, we decided to take a deeper look into fallback algorithm and terms. Then we can talk about edit mechanism in mobile termbox.
Dec 5 2022
Nov 23 2022
There is no need to add additional documentation, we have both of them in both example CSV file and the documentations.
Nov 21 2022
Nov 10 2022
Oh, that's great! I'll proceed like you said then, thanks a lot!
Nov 9 2022
We should allow CSV files without meta_wikidata_value column because we are adding it as optional and it's not good for backward compatibility. However, we have another optional column in our CSV files, external_url and unlike meta_wikidata_value, the CSV file should have that column even there is no value for the external_url field. I think we should treat there columns same because they have similar attributes: we should allow CSV files without external_url column just like with meta_wikidata_value. Otherwise we have two optional columns but one is not so optional compared to the other one. I wonder if you agree @Lydia_Pintscher?
Oct 31 2022
Oct 25 2022
Oct 10 2022
Oct 7 2022
Here is the final form of the merged ontology file @Lydia_Pintscher @danshick-wmde, I don't know how to update current one that's why I'm adding it to here.
Sep 30 2022
@Lucas_Werkmeister_WMDE I think we can add problematic part of a property as a parameter to the API response? UI can also highlight the issue with the input as well. I don't know if it's a good idea to add it as a parameter though.
Sep 28 2022
Sep 26 2022
As discussed on gerrit, there is an uncertainty about lexemes having languages and the way we define them, or should we define them at all.
I have added the final form of ontology file as attachment, I don't know where to add it tbh :)
We have talked about "Lexemes having spelling variant" with @Lucas_Werkmeister_WMDE and I suppose forms have spelling variants instead of lexemes and I'm not sure if it's relatable anymore. Other than that, it should be ready for review.
Sep 19 2022
When I checked the escapeHtmlAllowEntities and the signature of htmlspecialchars function, it seems like it doesn't matter if you put or remove ENT_QUOTES | ENT_SUBSTITUTE as flags, because it's the default value anyway.
Sep 16 2022
Sep 15 2022
@Dzahn no I realize that it's way more complicated than I think, so let's cancel the task and pretend like it never happened?
Hello, I just signed the agreement.
Sep 14 2022
@WMDE-leszek @Dzahn Actually the problem with creating new user process was kernel username, I couldn't remove that from the old user so I couldn't add it to the new one. If you can provide a proper way to make this happen, I can create the new user for sure.
Sep 13 2022
As the WMF-Legal project tag was added to this task, some general information to avoid wrong expectations:
Please note that public tasks in Wikimedia Phabricator are in general not a place where to expect feedback from the Legal Team of the Wikimedia Foundation due to the scope of the team and/or nature of legal topics. See the project tag description.
Please see https://meta.wikimedia.org/wiki/Legal for when and how to contact the Legal Team. Thanks!