Re: [Wikitech-l] Logo of mediawiki
Hello everyone, I just wanted to remind you that only one week left from the voting period of the first round (general design and look of proposals). Best On Mon, Aug 10, 2020 at 2:42 PM Amir Sarabadani wrote: > Hey again. > I just wanted to remind people that the first round of voting has started, > you can vote on the general look and design of the proposals (but you can't > add more anymore). This will continue for a month and after that there will > be another round of voting for variants of the top designs (like different > wordmarks, different colors, etc.) > > Thank you for your contributions on this project. > > Best > > On Sun, Jul 19, 2020 at 3:44 PM Amir Sarabadani > wrote: > >> Hello everyone, >> Thank you for your enthusiasm around the logo. It made me so happy, and >> also thank you for all of the feedback around the process, I'm certainly >> learning. >> Based on the feedback I want to say some notes: >> >> With all other discussions happening at the same time this can be >> draining and having a global pandemic going on is not going to help either. >> So the deadlines are pretty relaxed. >> >> It's already been a month (almost) and let's add three weeks for adding >> and discussing proposals, meaning until 10th of August you can add and >> discuss proposals. After that, we will have a month for the first round of >> voting, In this round, you can vote on the logo designs in general, meaning >> until 10th of September you can vote on logos general look and design (not >> the colors, wordmark, number of pedals, etc). The second round of voting >> will be a month afterwards (meaning until 10th of October) which you can >> vote on different variants of the top logos of the first round (like >> different wordmarks, different colors, and so on) and after that we will >> move forward with implementing the top logo and variant. >> >> In short, there will be three phases: >> - Current phase (until 10th of August): Suggest proposal and discuss >> proposals. >> - Second phase (until 10th of September): Vote on general design of all >> proposals >> - Third phase (until 10th of October): Vote on different variants of the >> top proposals. >> >> If anyone wants to help with facilitating discussions, I'd be more than >> happy to have some help. Send me a private message and we can form a group. >> >> Also, I would like to humbly ask everyone to be more mindful in their >> comments, each proposal is a product of someone's creative thinking and >> work. Especially avoid criticizing people. In other words, please be >> kinder, we all can use a little bit of kindness these days. >> >> Thank you. >> >> On Mon, Jun 22, 2020 at 2:39 AM Amir Sarabadani >> wrote: >> >>> Hello, >>> The current logo of MediaWiki was adapted slightly more than fifteen >>> years ago and hasn’t changed since. This logo despite having the nice >>> concept of sunflower, is old. The sunflower represents the diversity, the >>> constant growth and also the wildness. >>> >>> Among its biggest issues I can point out that it’s a bitmap picture so >>> it’s unusable in large sizes (like large posters) and it’s too realistic >>> making it unusable in small sizes. >>> >>> Most, virtually all, software products use a simpler and more abstract >>> form. For example, docker, kubernetes, Ubuntu, VueJs, React, Apache Kafka, >>> and many more. It’s a good time for MediaWiki to follow suit. >>> >>> My request is for changing the logo of MediaWiki and I have no plans or >>> interest in changing logo of any other project. >>> >>> Please show your support, oppose or your comments in the discussion >>> page. You can also add more suggestions. >>> >>> The discussion page: >>> https://www.mediawiki.org/wiki/Project:Proposal_for_changing_logo_of_mediawiki,_2020 >>> >>> Best >>> -- >>> Amir (he/him) >>> >>> >> >> -- >> Amir (he/him) >> >> > > -- > Amir (he/him) > > -- Amir (he/him) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Scrum of scrums/2020-09-02
Hello, This email contains updates for September 2, 2020. For the HTML version, see: https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-09-02 Cheers, Deb *= 2020-09-02 =* == Callouts == * Datacenter switchover completed. All wikis are being served from codfw. Switchback in 1 month from now. Many thanks to everyone who contributed to this! * [[GitLab_consultation|GitLab consultation]] is now open! Please comment on the talk page. == Product == === iOS native app === * Blocked by: * Blocking: * Updates: ** Development of our 6.7 release - [[phab:project/view/4661]] *** Article as a living document feature *** New iOS14 widgets (Top Read, Picture of the Day, On This Day) === Web === * Updates: ** '''Summary''': Vue.js search performance tests, IE11 support, and instrumentation. ** [[Reading/Web/Desktop Improvements|Desktop Improvements Project (Vector / DIP)]]: *** [[phab:T261686|Search bar should shift to right edge of container at low resolutions]] *** [[phab:T261523|Revisit client exclusion rules for errors where file uri matches URL or no URL]] *** [[phab:T260867|PrefUpdate captures user preference modifications at registration]] *** [[phab:T256897|Decide on and clean up naming of CSS classes identifying menus in toolbars and the sidebar.]] *** [[phab:T250968|[ShoutWikiAds] Replace use of deprecated hook VectorBeforeFooter]] *** [[phab:T260412|[Spike 10hrs] Determine steps necessary for switch to header-first DOM]] *** [[phab:T258552|Add wordmarks and taglines for 26 more Wikipedias]] *** [[phab:T258493|[Spike 8hrs] "Use Legacy Vector" is not working as a global preference]] *** [[phab:T256100|Add skin version and search version fields to search satisfaction schema]] *** [[phab:T254695|Build a pre-library loading indicator for Vue.js search]] *** [[phab:T249363|Move the existing search to the header in preparation for Vue.js search development]] *** [[phab:T252774|Checkbox and mediawiki.toc.styles styles should be merged into a single ResourceLoader module]] *** [[phab:T251544|Add user journey performance tests for Vector's Legacy and Vue.js search]] *** [[phab:T213845|Change link colors in Vector]] *** [[phab:T213778|Update link colors in Vector for improved UX (and consistency)]] *** [[phab:T244392|Vue.js search case study]]: See [[Reading/Web/Desktop Improvements/Vue.js case study/Status log|weekly status updates]]. ** Mobile website (MinervaNeue / MobileFrontend): *** [[phab:T258096|Regression: Nested references do not open if user clicks on [ or ] (which are wrapped in span)]] *** [[phab:T240622|[Technical debt payoff] Remove InlineDiffFormatter and InlineDifferenceEngine from MobileFrontend]] ** Standardization *** [[phab:T261391|Use standard external link icon for external links]] ** Miscellaneous *** [[phab:T261378|Remove IE8 CSS hacks and fallbacks in Vector]] *** [[phab:T259630|TypeError: results.error is undefined]] *** [[phab:T259400|Drop MonoBookAfterContent hook]] *** [[phab:T203023|skins.monobook.mobile.uls dependency doesn't do mobile?]] *** [[phab:T253938|Future proof addPortletLink]] == Technology == === Site Reliability Engineering === * Blocked by: ** None * Blocking: ** None * Updates: ** Datacenter switchover successfully completed. All wikis are now being served by codfw. Many thanks to everyone who contributed to this! -- deb tankersley (she/her) sr program manager, engineering Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Public API for Wikimedia map tiles to be discontinued in 45 days
> > > [crosspost from Maps-l] > Hi everyone, here are a few clarifications about our prior announcement re: Maps API deprecation for 3rd parties [1]. As stated, our plan is *not* going to have any impact on any Wikimedia-hosted wikis. This means that nothing will change for maps, in any namespace, on Wikipedia and any sister projects. Tools that are hosted on Wikimedia services are also not going to be affected (i.e., Kartographer). This said, we are aware that there may be map usage beyond such venues where deprecation would still affect our community members and their activities - for instance, the Wiki Loves Monuments website, and the Wikimedia Poland chapter website both rely on our maps API. Hence, over the 45 day deprecation period which ends in mid October: *if you represent an affiliated free knowledge group that does regular work with our maps (any Wikimedia affiliates, or established wikiprojects), or if you are closely partnering with other entities who do, we welcome you to reach out, either here on this announcement thread or on the dedicated Phabricator ticket [2].* We will work with you to understand your needs, and what alternatives exist. For further questions, I encourage you to contact me off-list to reduce noise. Thank you. [1] https://lists.wikimedia.org/pipermail/maps-l/2020-August/001729.html [2] https://phabricator.wikimedia.org/T261694 -- Erica Litrenta Manager, Community Relations Specialists https://meta.wikimedia.org/wiki/User:Elitre_(WMF) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Making breaking changes without deprecation?
Hi! For the BlueSpice distribution ... * we have got ~90 active repos hosted on WMF Gerrit and another ~10 in our internal Gitlab * we want to develop as much as possible on the public infrastructure of the WMF, so the remaining internal repos will (hopefully) be published in the future * we have hundreds of installations and a lot of them have a custom extension/skin maintained by us, that can not be published * we mainly target MediaWiki core LTS branches with our code, therefore deprecations and breaking changes introduced by a non-LTS usually are no problem. But ... * we try to keep up with the changes in the core `master` branch mainly for two reasons: 1) CI tests of our codes `master` branch will fail whenever we cherry-pick a change from the LTS branch 2) There is less work left for the time when a new LTS is about to be released (just happening with 1.35) I believe the proposed process change will not affect us much. We will benefit more from a cleaner/modernized MediaWiki core codebase more than we will suffer from breaking changes. Especially as a lot of our code will be in the public available locations and therefore be visible for the WMF anyways. As long as we have a way to know about such breaking changes (mailin-list, mw.org pages, release notes, ...) - and how to handle them - we should be good. -- Robert Vogel ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
