Project:Village Pump/Flow/2020/07
| This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
This page is only for discussing issues related to MediaWiki.org website.
Feedback on movement names
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello. Apologies if you are not reading this message in your native language. Please help translate to your language if necessary. Thank you!
There are a lot of conversations happening about the future of our movement names. We hope that you are part of these discussions and that your community is represented.
Since 16 June, the Foundation Brand Team has been running a survey in 7 languages about 3 naming options. There are also community members sharing concerns about renaming in a Community Open Letter.
Our goal in this call for feedback is to hear from across the community, so we encourage you to participate in the survey, the open letter, or both. The survey will go through 7 July in all timezones. Input from the survey and discussions will be analyzed and published on Meta-Wiki.
Thanks for thinking about the future of the movement, --The Brand Project team, 20:33, 2 July 2020 (UTC)
Note: The survey is conducted via a third-party service, which may subject it to additional terms. For more information on privacy and data-handling, see the survey privacy statement.
MediaWiki message delivery (talk) 20:33, 2 July 2020 (UTC)
Module documentation translation
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Can we mark module documentation pages (Module:*/doc) for translation? (They have never been marked.)
Sophivorus wants to prepare Module:Transcluder/doc for translation. Shirayuki (talk) 02:24, 5 July 2020 (UTC)
- Page names will be inconsistent with template documentation pages:
| source page | translation pages | |
|---|---|---|
| Template documentation (without Translate) | Template:(name)/doc
|
Template:(name)/(language)/doc
|
| Template documentation (with Translate) | Template:(name)
|
Template:(name)/(language)
|
| Module documentation | Module:(name)/doc
|
Module:(name)/doc/(language)
|
- I don't see why module documentation pages shouldn't be translatable. * Pppery * it has begun 02:10, 17 July 2020 (UTC)
- So, can we give it a try? Sophivorus (talk) 16:07, 19 July 2020 (UTC)
- My only other comment is that they have to be treated as templates (given the
#switch:<translate></translate>wrapper), because they are implicitly transcluded by the module they are documenting. * Pppery * it has begun 16:56, 19 July 2020 (UTC) - Hi! I just did another attempt to mark the module documentation for translation. Unlike my first attempts, I think I did quite a detailed markup this time. However, I couldn't quite understand the
#switch:<translate></translate>wrapper and I couldn't find documentation about it either, so I would really appreciate if someone more familiar with it could tweak my markup to comply with that, or give me some hint so I can do it myself. Thanks!!! Sophivorus (talk) 16:00, 21 July 2020 (UTC) - See Module:Transcluder. There are many
<translate>tags. Shirayuki (talk) 21:04, 21 July 2020 (UTC) - Hence my previous comment about treating it as a template, doing something like Special:Diff/3976778 (see the edit summary of that edit, I'm aware that Module:Transcluder is currently erroring with a template loop). * Pppery * it has begun 21:16, 21 July 2020 (UTC)
- Unable to create Module:Transcluder/doc/ja by translating. Shirayuki (talk) 21:30, 21 July 2020 (UTC)
- And FuzzyBot failed to create Module:Transcluder/doc/en as well. I think you've run into a software bug that should be reported on phabricator.
- You might be able to work around the problem (if my hunch as to what caused it is correct) by unmarking the page for translation, creating Module:Transcluder/doc/en and Module:Transcluder/doc/ja with the
wikitextcontent model using Special:ChangeContentModel, and then marking the page for translation again (but of course that dance will need to be repeated the first time the page is translated into a new language, which kind of defeats the point) * Pppery * it has begun 21:38, 21 July 2020 (UTC) - Maybe we can move the documentation to Help:Module:Transcluder and then transclude it at Module:Transcluder/doc using:
{{#invoke:Template translation|renderTranslatedTemplate|template=Help:Module:Transcluder|noshift=1|uselang={{int:lang}}}}? Thanks for all the help and sorry for the trouble! Sophivorus (talk) 22:07, 21 July 2020 (UTC) - In any case, Shirayuki did my dance and made things work. * Pppery * it has begun 00:56, 22 July 2020 (UTC)
- Thanks guys! I just did a full translation of the documentation to Spanish and also a minor tweak to the source text. This may help to fully test the translation process. Sophivorus (talk) 12:37, 22 July 2020 (UTC)
- Making a change to the source text appears to have worked. Translating the page into a Spanish seems to have run into the same problem as the initial marking for translation and Shirayuki's translation into Japanese: Module:Transcluder/doc/es needs to be created manually by an admin doing the dance I described a few comments ago. * Pppery * it has begun 03:15, 23 July 2020 (UTC)
- Awesome, thanks! I'm a bit concerned that the dance may slow the translation process, so I went ahead and created Module:Test to try out the strategy I outlined above. Module:Template translation wouldn't transclude the languages header, so I added Template:Languages to compensate. Other than that, I think this approach is simpler and more reliable, unless I'm missing something. What do you think? (If you agree, could you move Module:Transcluder/doc and subpages to Help:Module:Transcluder?) Cheers! Sophivorus (talk) 13:48, 23 July 2020 (UTC)
- Be careful of moving things to the help namespace, due to Project:PD help. Otherwise, I like neither the current situation nor your proposed solution, but of course one of them will have to do. * Pppery * it has begun 15:07, 23 July 2020 (UTC)
- I agree neither is perfect, but I think I prefer using Help:Module:Transcluder to avoid issues like this one that are bound to happen again and again. Noted Project:PD help, but I think for now moving to Help namespace should be fine since so many extensions have their user documentation under a similar format (like Help:Extension:Translate). That being said, I cannot move the module documentation myself since I need to be a translator admin to do so. What do you think, Shirayuki? If you agree, would you do the move? Thanks! Sophivorus (talk) 22:00, 23 July 2020 (UTC)
- I was also concerned for FR page => Module talk:Transcluder/doc#h-french_translated_pages_exist_but_language_is_not_in_the_selector-2020-07-23T19:04:00.000Z
- Christian 🇫🇷 FR (talk) 10:06, 24 July 2020 (UTC)
My page not published (LBSCST)
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I have already created a draft for LBS Center for Science Technology. The main aim to educate the people about the institution and its service to the public. I have tried two mre methods to contribute to the wikipage but it couldn't have any success. Still my first document (about the LBS) is shown as draft. I can't visible this by search engine or any other way other my contributions page. Please help met o solve the issue. 157.46.217.164 (talk) 12:28, 8 July 2020 (UTC)
- You are very likely in the wrong place. This page is for discussing issues related to documentation for the MediaWiki software. If your question is about the English Wikipedia, I'd recommend asking at their teahouse. Taavi (talk!) 12:30, 8 July 2020 (UTC)
Announcing a new wiki project! Welcome, Abstract Wikipedia
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi all,
It is my honor to introduce Abstract Wikipedia, a new project that has been unanimously approved by the Wikimedia Foundation Board of Trustees. Abstract Wikipedia proposes a new way to generate baseline encyclopedic content in a multilingual fashion, allowing more contributors and more readers to share more knowledge in more languages. It is an approach that aims to make cross-lingual cooperation easier on our projects, increase the sustainability of our movement through expanding access to participation, improve the user experience for readers of all languages, and innovate in free knowledge by connecting some of the strengths of our movement to create something new.
This is our first new project in over seven years. Abstract Wikipedia was submitted as a project proposal by Denny Vrandečić in May 2020 [1] after years of preparation and research, leading to a detailed plan and lively discussions in the Wikimedia communities. We know that the energy and the creativity of the community often runs up against language barriers, and information that is available in one language may not make it to other language Wikipedias. Abstract Wikipedia intends to look and feel like a Wikipedia, but build on the powerful, language-independent conceptual models of Wikidata, with the goal of letting volunteers create and maintain Wikipedia articles across our polyglot Wikimedia world.
The project will allow volunteers to assemble the fundamentals of an article using words and entities from Wikidata. Because Wikidata uses conceptual models that are meant to be universal across languages, it should be possible to use and extend these building blocks of knowledge to create models for articles that also have universal value. Using code, volunteers will be able to translate these abstract “articles” into their own languages. If successful, this could eventually allow everyone to read about any topic in Wikidata in their own language.
As you can imagine, this work will require a lot of software development, and a lot of cooperation among Wikimedians. In order to make this effort possible, Denny will join the Foundation as a staff member in July and lead this initiative. You may know Denny as the creator of Wikidata, a long-time community member, a former staff member at Wikimedia Deutschland, and a former Trustee at the Wikimedia Foundation [2]. We are very excited that Denny will bring his skills and expertise to work on this project alongside the Foundation’s product, technology, and community liaison teams.
It is important to acknowledge that this is an experimental project, and that every Wikipedia community has different needs. This project may offer some communities great advantages. Other communities may engage less. Every language Wikipedia community will be free to choose and moderate whether or how they would use content from this project.
We are excited that this new wiki-project has the possibility to advance knowledge equity through increased access to knowledge. It also invites us to consider and engage with critical questions about how and by whom knowledge is constructed. We look forward to working in cooperation with the communities to think through these important questions.
There is much to do as we begin designing a plan for Abstract Wikipedia in close collaboration with our communities. I encourage you to get involved by going to the project page and joining the new mailing list [3]. We recognize that Abstract Wikipedia is ambitious, but we also recognize its potential. We invite you all to join us on a new, unexplored path.
Yours,
Katherine Maher (Executive Director, Wikimedia Foundation)
MediaWiki message delivery (talk) 19:56, 9 July 2020 (UTC)
Can't log in
[edit]Hi, I can't log in using my old password or the new, temporary password emailed to me. Please help, as I'd like to reopen my wiki. 2401:4900:3A1E:B500:1DE8:FCBD:806D:F141 (talk) 13:45, 10 July 2020 (UTC)
- Which account on which wiki do you mean? MGChecker (talk) 13:50, 10 July 2020 (UTC)
Permissions to add external links?
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hello! I work on the Wikipedia iOS app, and am trying to update a couple outdated links to the GitHub repo on the iOS app page. It seems like I don't have permissions to update external links on MediaWiki, and am being redirected here. Is it possible to either grant me permissions, or update the two README links to this updated link? Thank you. MCleinman (WMF) (talk) 19:19, 13 July 2020 (UTC)
- Hi, I adjusted your user rights to exempt you from the filter. You should be all set now - let me know if you run into any other problems. Legoktm (talk) 20:02, 13 July 2020 (UTC)
Extract Data out of an iFrame
[edit]Hello forum
in short, I try to read data from an iFrame query, but I can't.
The situation is as follows: There is a query from a wiki that reads and displays a data record from a Lotus Notes application.
Lotus Notes provides this data on an html page which is then displayed in the wiki using iFrame.
I would now like to assign various variables with data from this iframe query.
Could someone give me a hint how to go about it?
greetings ede Ede1103 (talk) 11:46, 14 July 2020 (UTC)
- You probably won't be able to do this without additional work (like accessing a web API for Lotus Notes). See this SO question about cross-domain scripting for more information. ☠MarkAHershberger☢(talk)☣ 15:29, 14 July 2020 (UTC)
Adding External Link with procedure to install Mediawiki
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi,
I've received a warning while adding the external link:
https://peppe8o.com/personal-mediawiki-with-raspberry-pi-and-docker/
to following mediawiki page:
https://www.mediawiki.org/wiki/Installing_MediaWiki_on_a_Raspberry_Pi
My link refers a procedure to install Mediwiki in Raspberry PI using Docker and docker-compose.
Please let me know if it is possible.
Many thanks,
Giuseppe 93.48.188.214 (talk) 08:16, 15 July 2020 (UTC)
Unprotect Template:Pp
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Template is unused (except in a topic on a deleted Flow board), so does not need to be protected as "highly visible". * Pppery * it has begun 15:34, 18 July 2020 (UTC)
Extension QrCode
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Is it possible to move the page Extension:BlueSpiceQrCode to the archived page Extension:QrCode since most users might look for a current extension there? MLRodrigue (talk) 13:41, 20 July 2020 (UTC)
- I added a reference to the BlueSpice extension there. As pages in extension namespace should mirror the extension's internal name, the extension page itself should not be moved. MGChecker (talk) 14:08, 20 July 2020 (UTC)
I am trying to create a new page. The site will not allow it.
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Sean Hancock (born 29 May 1977) is a American professional arm wrestler. He is a five-time international champion arm wrestler and is a former champion triathlete. Hancock is sponsored by Mazurenko arm wrestling equipment and Frog Fuel liquid protein supplements. PALBOOM (talk) 18:15, 22 July 2020 (UTC)
Proposal: Template "Used by"
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
A good suggestion for improvement has developed from the deletion discussion of a template: At least in my reading there are several users who find it helpful to provide extension pages with an additional "used by" template.
What's this about? Similar to the already existing WMF template "OnWikimedia" the goal is to give extension pages a marker that this extension is also used in bundles, distributions, maybe even in larger websites or wiki farms. This way visitors of the page will see an information that the extension is "mission critical" or "best breed" in certain contexts. Especially since there is no real other way to know which extensions are widely used and which are not. This would hopefully also help us all to better understand which extensions need to be considered when technological structures change or which extensions need continuous maintainers. And, of course, in general, it is also positive feedback for the developers.
The deletion discussion made clear that such a template must be designed in a way that it does not promote a single project, but leaves room for as many projects as possible to be displayed in the template. And it could or should of course tend to bring together non-Wikimedia projects and Wikimedia projects, point to these projects, but must not overload the screen. It must also be clearly recognizable (in the documentation) that the template can be removed from the corresponding page at any time if the maintainer does not want the template there.
I have here a link for a first suggestion with three variants how this could look like, to give a visual impression of what we are talking about. First you see a variant with icons, a variant with text only and a variant with logo and text.
Now I would be interested in a first feedback, whether this intiative should be pursued at all and what advice and concerns there are about it. Then there is the question of whether the decision-making process should go through an RfC or whether we can already clarify this here, because everyone is for or against it anyway. I am looking forward to your opinions and help in order to move the issue forward in a timely manner. RichardHeigl (talk) 07:58, 23 July 2020 (UTC)
- > there is no real other way to know which extensions are widely used and which are not
- That's not true. There's a "Check usage and version matrix" link in the extension infobox that tells you exactly that, and you can also look in which MediaWiki versions are being used.
- If we're including such bundles or wiki farms, I guess we should also come with a policy about which bundles or wiki farms are considered relevant enough to grant them appearing on that template. Ciencia Al Poder (talk) 09:35, 23 July 2020 (UTC)
- I like the idea of somehow providing a meaningful indicator of extension quality and support. Currently extension "status" is just up to the editor of the Extension page.
- Also (a related tangential topic), the installer links to Category:Extensions by category - which has no filter capability (on quality or any other basis) and was first generated in 2007. The installer should be updated to direct users to a more meaningful directory of Extensions (and it would be nice if it had search / filtering capabilities). Greg Rundlett (talk) 20:24, 23 July 2020 (UTC)
- @Ciencia Al Poder - I had seen that "Check usage and version matrix" link a thousand times but never thought to click on it! (Maybe because it's a boring name for a link.) I was surprised to see that it links to WikiApiary. It's certainly a useful link, and I'm glad it exists, but I think a "Used by" template would still be useful as a way to see additional information about usage.
- The policy question is an interesting one, though. Even if there is a policy in place, the "Used by" template could still get overwhelmed by names (at least for certain extensions), if various consulting companies and/or hosting providers start to see this template as a way to advertise their services. If there's no policy, it could be worse - although then again, I can't imagine what such a policy would be. What could a consulting company provide to prove that they are legitimate, or large enough - a bank statement?
- Any thoughts on this? Yaron Koren (talk) 03:30, 24 July 2020 (UTC)
- Thanks again for the reference to the link to WikiApiary. It is true that it gives you a first estimation about the distribution of extensions. But only via wikis that are accessible via the web. But not about systems that live behind firewalls. That's what I meant when I wrote that we only have limited possibilities so far. The extension bundles for public wikis and internal wikis are very different. And we have a view that takes both worlds into account. RichardHeigl (talk) 14:49, 24 July 2020 (UTC)
- @RichardHeigl - what do you think about the danger of this template getting overloaded? Perhaps it's not that big a fear; I don't know. One option is to have the template "collapse" if it has more than some number of values, like 20 values - if it does, it can say something like "This extension is used in many bundles and wiki farms; click here to see the full list."
- As for the mockups you created - I think I prefer the 2nd one, which is just a list of text terms. The 1st one, with the logos, is nicer-looking, but it can be unclear: first because most people won't recognize the logos, and second because a single logo might not communicate enough. What if a company produces more than one bundle? (Hallo Welt might be in that situation, actually.) If you want to clarify which bundle(s) this extension is part of, that would be difficult to accomplish with just a logo.
- The 3rd option I don't understand. What does "as needed" mean, and what would the other options be? Yaron Koren (talk) 16:05, 24 July 2020 (UTC)
- WikiApiary gives you an unsorted list of random wikis, I don't think it's sensible to expect people to glean any useful information from that. Although the same can be true for "used by" templates - the extension is part of MyMediaWikiBundle, so what? Does that imply some level of support? Does it imply some level of testing? Does it mean someone evaluated it? How long ago, against what criteria? UsedByWikimedia is not super helpful but at least tries to characterize what can be inferred from the presence of the template. Tgr (talk) 00:10, 25 July 2020 (UTC)
- @Yaron_Koren: A good developer's question: What happens when there are a large number of entries? It can be done the way you suggest: So open a complete list at the push of a button. But at the moment I think this is still a luxury problem. And I also don't see the template as an instrument that should represent "completeness". I would be glad if five / six projects would voluntarily start to enrich extension entries with this additional information. "As needed" is only a placeholder for more entries.
- Which brings me to the objection of @Tgr. What does it mean that an extension is part of a bundle or a project? For me it is the statement that the function is operational and its basic function is tested ("runs for me"), that its functionality is at least probably, if not guaranteed with other extensions and that through these projects people can be found who can remove incompatibilities, contribute patches or function extensions if necessary.
- This has pretty much the same function for me as the hint that extension XY runs on Wikipedia. That means for me: It is tested and maybe even maintained there.
- But there are many extensions that Wikipedia does not use or that only work on Wikimedia servers. In this respect, I see the added value of such a template in the possibility of being able to research whether an extension is also used in others and in which contexts. Unfortunately, Mediawiki.org does not offer any further possibilities to store and evaluate corresponding metadata.
- Actually the problem is, I can see that, that the entries have to be kept up-to-date. That would be a showstopper. RichardHeigl (talk) 08:49, 27 July 2020 (UTC)
- Rereading Tgr's post again: Do I understand you correctly that such a template like the Wikimedia template should include a hint, which is implied? e.g. "This probably means that the extension is stable and works well enough to be used in <context>". RichardHeigl (talk) 08:57, 27 July 2020 (UTC)
- A template mentioning multiple "used by" entries should show those entries in random order.
- I see the risk (as with any other human maintained list) that over time a lot of orphaned entries will render the list useless. Planetenxin (talk) 08:14, 31 July 2020 (UTC)
- @Planentenxin: I disagree - I think the list should always be in alphabetical order, to make it easier to see if some specific company/package/farm supports this extension. If "Acme Consulting", or whoever it is, benefits by always being first, so be it - I don't think being first is that important.
- I also have to disagree with, I guess, both Planetenxin and RichardHeigl that out-of-date entries would ruin this whole feature. There's a lot that's out of date on mediawiki.org in general, but that doesn't make the site useless. People who use "Used by" to find a package to download, a wiki farm to use, etc. will quickly discover if they were given bad information. And of course, it's a wiki, so it's easy to update things.
- But I'm curious now about the fact that the proposer of this idea, RichardHeigl, now thinks that there's a big flaw in the plan. Does that mean that this idea is dead? Yaron Koren (talk) 18:29, 31 July 2020 (UTC)
- Hello, Yaron. The idea isn't dead and I don't think it has a fundamental flaw. We now have a number of good suggestions and advice, so I would make a revised draft (I think until next week). I personally prefer a text/picture version with notes and documentation as requested above. But these are then design issues.
- The only problem I find so far is that I don't know how we should or can introduce this. It doesn't make much sense if we now put the new template on extension pages. That would then lead to further discussions. We would need the approval or commitment of some stakeholders in this process. So do we have to do an RfC after all? What is the best way forward here? RichardHeigl (talk) 10:37, 3 August 2020 (UTC)
- Okay, great. I'm looking forward to seeing the demo! After that, yes, an RfC might make sense. Yaron Koren (talk) 12:59, 3 August 2020 (UTC)
- @Yaron: position matters, see Serial-position effect. So the only fair way would be a changing random order. Planetenxin (talk) 11:59, 7 August 2020 (UTC)
- I know that position matters (that's why there are so many companies in the English-speaking world named "Ace, "Acme" or "AAA", not to mention "Zenith"), but I think the benefits of having a consistent alphabetical order outweigh the drawbacks. Yaron Koren (talk) 13:05, 7 August 2020 (UTC)
- Reminder: This new template is all about making projects visible and bringing people together. And I'm largely there with all the proposals. To be honest, I don't like the random order, and not because I care that BlueSpice comes before Fandom. I really don't care about that at all. We can also put BlueSpice somewhere in the middle. But there should be a consistent, easy to follow order that doesn't produce arguments and long discussions. Except alphabetical order I can't think of anything else. Is random distribution technically possible? Relevance criteria are completely out of scope, that's causing a lot of trouble. But as I said, the order is not that important to me. I consider that at the moment a secondary topic. Let us focus on the main challenges. One of them: Who will actively support this template?
- And I also think that it can be designed in such a way that nobody feels cut off here, especially because I assume that only a small number of projects will be shown, at least for the foreseeable future, because the main effort is to enter them and that has to be done first. This will surely remain rather clear at the beginning. The luxury problem of too many entries I would like to have first.
- As I said, I hope that next week I will be able to deliver another draft and then we will see if the existing reservations can be removed. Personally, I would like to see a variant that offers colored pictures/logos and text. This makes recognition much easier and projects do not disappear in a text landscape. But let us see.
- And then we will hopefully create a small contribution through which the sub-projects will become more integrated and refer more to each other. In no other community this seems to me to be as difficult as with MediaWiki. But we should overcome this quickly if MediaWiki is not to disappear outside of Wikimedia. RichardHeigl (talk) 13:03, 8 August 2020 (UTC)
- Well, no need to be dramatic. :) But I'm looking forward to the next drafts. Yaron Koren (talk) 22:04, 9 August 2020 (UTC)
- Here are now the other mockups, which meet different requirements: https://en.wiki.bluespice.com/wiki/MediaWiki-usedby#/media/File:UsedBy-option1.png
- First a completely unobtrusive text variant, then a text variant with a pop-up mechanism and reference to different editions, then different variants with a logo/text combination and once again variants with "buttons".
- We have added a sentence that should make it clear why this template exists and what the referencing of the projects should say. We have also tried to use a different sort logic (alphabetical, but starting in the middle and then "rotating").
- The relevance criteria question (inclusion of a project) should still be difficult. I still consider this a luxury problem, but I imagine that in the template documentation there are minimum criteria such as installation numbers, download and visitor numbers that have to be met. And there are still discussion sites where you can negotiate borderline cases.
- What do you think?
- I now see an RfC as the next step. I have never done this on mediawiki.org before. Can anyone support me there? RichardHeigl (talk) 11:20, 12 August 2020 (UTC)
- Overall these look pretty good, I think. I don't think it makes sense to include "large websites" as an option, unless you have a precise metric for that (I guess that's what you were getting at in the end). I also don't think it makes sense to include that second sentence ("This means that this extension seems to be stable, the basic function is tested and running and the extension is or should be maintained") - people can judge for themselves what it means that extension X is used by Y and Z. As for the different layouts - they all seem fine to me. I'm glad that the name, not just the logo, is visible in all of them.
- As for an RfC: just create a draft RfC page, and I think other people will be able to help at that point. Yaron Koren (talk) 13:26, 13 August 2020 (UTC)
- After some research I came to the conclusion, that an RfC does not seem to be the right way (as the procedure is reserved for technical issues). The discussion will now be continued in this ticket: https://phabricator.wikimedia.org/T260998 RichardHeigl (talk) 17:45, 21 August 2020 (UTC)
Not able to add information
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Trying to create a page for Founder of One Stage but not able publish. It says new user. BahetiP (talk) 12:27, 23 July 2020 (UTC)
- MediaWiki.org is not Wikipedia to create articles. Even on Wikipedia, the subject must meet the notability criteria for biographies. Ainz Ooal Gown (talk) 12:44, 23 July 2020 (UTC)
- Thanks for the information. The person is Vice President (MH) of Human Rights Council of India and Journalist.
- How can I progress on that? BahetiP (talk) 13:01, 23 July 2020 (UTC)
- You need to cite enough secondary reliable sources (minimum three that discuss the subject in great detail, not passing mentions) to prove that a subject is notable. Anyway this isn't the forum to discuss this. You might want to ask your question on English Wikipedia TeaHouse. If you prefer a live conversation, join w:en:WP:DISCORD to chat with me live. Ainz Ooal Gown (talk) 13:10, 23 July 2020 (UTC)
- Thank You for the help & knowledge BahetiP (talk) 05:14, 25 July 2020 (UTC)
Edit request at Template:Top icon
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Change the top-right area of [[Wikipedia:User pages|user pages]] or articles to the top-right area of a page; Top icons are in fact used on pages that are not user pages or "articles" (does that last term even mean anything on MediaWiki.org?) * Pppery * it has begun 14:26, 27 July 2020 (UTC)
- I think "articles" on mediawiki.org would be documentation pages of the software. Changed the wording accordingly. Ainz Ooal Gown (talk) 14:30, 27 July 2020 (UTC)
Translate : is it worth to use the suggestions frame ?
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Hi all, when I translate Mediawiki pages into FR, sometimes in the suggestion frame, an Apertium proposal appears. I rarely use that because it is often far from the usual use and make me smile although I recognize it holds the idea of the text.
To make things in an intelligent way I wonder if it is not worth clicking on this text to bring it back in the main frame and then correct/adapt it. Is there a learning process behind that ? I mean receiving the translated text and returning it corrected can feed a function of amelioration for further translations.
...or is that only a one way mechanism ? and in this case it is worth to translate directly on the flow without referring to the suggestion.
Thanks.
Christian 🇫🇷 FR (talk) 10:33, 30 July 2020 (UTC)
- I don’t think it would send back any data to Apertium, but Nikerabbit should know it better. Tacsipacsi (talk) 19:56, 30 July 2020 (UTC)
- Apertium developers can use Content Translation dumps. We do not track or store the machine translation output in Translate which makes it impossible to produce similar dumps. One reason behind poor quality Apertium translations is that Translate is configured to allow to do translation through an intermediate language. Nikerabbit (talk) 19:03, 4 August 2020 (UTC)