User talk:Qgil-WMF

Previous page history was archived for backup purposes at User talk:Qgil-WMF/LQT Archive 1 on 2015-06-10.

Hi

Hope you're the right person to contact. Found your info through these pages, suggested by somebody on phabricator.

I'm building a wiki on a shared webhost, who doesn't support node.js.

gunretort.xyz

Of course i love the new VisualEditor, but without node.js, we cannot use it.

Meantime, WikiEditor is really showing it's age. Other wysiwyg editors, like TinyMCE, CKEditor, etc are buggy or no longer supported (mostly the latter).

I strongly believe MediaWiki's social mission compels you to support low-budget wikis. But if WikiEditor continues to be lame and neglected, while VisualEditor gets all the attention, then you're being elitist, and neglecting MediaWiki's social mission.

Looking forward to your reply.

Thx,

Johny Why

Hi, I have been thinking about your question and what comes is my personal answer. I am not "the right person to contact" but maybe I can help you.

When it comes to low-budget projects, I think the question to be asked is not why depending on JavaScript or node.js to offer a good user experience, but why self-hosting. Running your own server is going to be resource intensive always (where resource includes not only money, also time). Meanwhile, MediaWiki's strength is to be run in a wiki farm (because Wikimedia is at the end a huge wiki farm).

There are wiki farms out there offering free wikis, also with VisualEditor and/or decent editors. Would this be an option for you?

If it's configurable as I need, and going to exist for years, then yes.

I tried the following for a while, and it wasn't bad.

https://meta.miraheze.org/wiki/Miraheze

But self-hosting offers more of the options I need, and I know it's not going anywhere.

Note, running a private server is resource intensive, as you mentioned. But shared hosting is less so.

Thx

With JavaScript spreading all over and with virtual hosting prices falling, I wonder whether using JavaScript is equivalent to "being elitist", and whether low-cost really is really equivalent to no JavaScript.

When it comes to the Wikimedia Foundation, the priority is to improve the user experience of editors, including those without the luxury of a desktop or high bandwidth. Plans go in the direction of offering a better mobile editing experience, because for millions of people low-cost really means regular access to mobile but less so to a desktop.

I guess this explains why the Foundation is investing in VisualEditor and mobile editing via web and native apps, and why there are no plans to develop the legacy editors further.

But anyway, as said all these are just my personal opinions. My talk page and myself are in fact not the best to provide the best informed answer. If you want to discuss this further, I recommend you to do it directly with the developers at the wikitech-l mailing list.

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:17, 4 January 2022 (UTC)

Latest news from the Wikimedia Global Collaboration team, about Notifications, Structured discussions, Edit Review Improvements and Content translation. Please tell other users about these changes. Not all changes will affect you.

What's new?

• The Global collaboration report for October is now available.
• All wikis now have the Filters for edit review as the default system on Recent Changes page.

Edit Review Improvements [More information • Help pages]

Most recent changes

• Filters for Watchlists are still on Beta. Please try them and give feedback before we release it for all users!
• Shortcuts to filter Namespaces and Tags are now more visible.
• Discovery of the search bar has been improved.
• If the Recent Changes page or the Watchlist fails to load or is time-outed, a message is now displayed.
• The bookmark icon for creating a "Saved filter" is now grayed when it is not possible to save. Before it was not visible. Bookmarking is unavailable when, for example, the current filter set is already saved.

Future changes

• Live updates on Recent changes will be moved out of beta and into the standard feature set by the end of the year.
• Extension:Translate filters for RecentChanges are going to be integrated to the new filters.
• Automatic edit summaries will be filtered as tags.

Content translation [More information • Help pages]

Recent changes

• List items (suggested items and in-progress/published translations) layout restyled to prevent overflows on small screen sizes.
• Search results for new translation dialog are now embedded, instead of being displayed in floating menu. Search results remain displayed when tabbed out and can be closed using ESC key.
• Missing pages are no longer shown when there is no match for search query. Message informing that there are no results is displayed instead.
• Embedded search results enabled to provide users with more translation opportunities. Articles user recently edited (in currently selected source language wiki) are surfaced when there is no input in search bar, with additional info if article is missing in user's currently selected target language.
• Long suggestion descriptions are limited to three lines, and the rest is truncated, which is indicated by ellipsis.
• Chart data representing user translation statistics in now showing all the months since user's first published translation. Months that went without translation are now displayed in chart as well.
• A loading indicator is shown while suggestions are loading.
• Button to discard dialog is now shown through the whole process of selecting article to translate.

Notifications [More information • Help pages]

Recent changes

• Edit-user-talk notifications are now expandable.

Structured Discussions [More information • Help pages]

Future changes

• Some work is ongoing to store Structured Discussions contents from HTML to wikitext. That change will allow some specific templates and magic words to work properly on Structured Discussions.
• Some tests are conducted in order to prepare the rewriting of Structured Discussions' interface. That rewriting will have no visible impact on users but it will ease future changes.

Other projects

• Compact Language Links has been deployed on German Wikipedia.

Collaboration team's newsletter prepared by the Global Collaboration team and posted by bot • Give feedback • Subscribe or unsubscribe.

15:36, 21 November 2017 (UTC)

Hello

Sorry to use English if that's not your favorite language.

You are receiving this message because you were reading the Collaboration team newsletter.

The Collaboration team doesn't longer exists. That team was working on building features that encourage collaboration. This is the latest message for that newsletter.

The Growth Team, formed in July 2018, supports some former Collaboration projects. The Growth Team's main objective is to ease new editors' first steps on wikis, through software changes. You can discover all objectives and missions of the Growth team on its page.

If you wish to be informed about Growth team's updates about easing new users first steps, you can subscribe to the new list to get updates. The first message from Growth –with a call for feedback on a new project– will be posted in a few days!

If you have questions or you want to share experiences made on your wiki about new users' first steps, please post them on the team talk page, in any language.

On behalf of the Growth team, Trizek (WMF) (talk) 10:29, 22 August 2018 (UTC)

Bom dia amigos.

Preciso saber quantos acessos foram realizados por página. Existem alguma extensão que faça isso?

Hi, this is just my personal Talk page. If you have more questions, please ask in Project:Support desk, where others will be able to help as well. Thank you.

Olá amigos,

Preciso alterar a página principal utilizada pelo sistema, ao abrir preciso que chame uma página especifica e não a página principal.

Também gostaria de saber se há a possibilidade de alteração do nome de uma página já criada.

Hi, see

• Manual:Main Page
• Help:Moving_a_page/pt-br

I solved the problem with your tip. Thank you very much.

Hi Qgil! I've been working on my Summer of Code/OPW proposal and was hoping to get some feedback on it before I got too far along. It's not on the list of recommended project ideas, so I wanted to make sure you thought it was feasible and that it had some chance of receiving broader support. Thanks! (talk) 12:49, 11 April 2013 (UTC)

Interesting idea, and very good project proposal structure overall. You have clearly invested a lot of thought and time already. Congratulations?

Have you found a mentor? In any case, the next steps recommended are:

• Creating a new enhancement request in Bugzilla, unless there is already an open report about this.
• Sending an email to wikitech-l pointing to the wiki page of your proposal and the bug report.

Good luck! And see you there.

I have not found a mentor yet, no. I sent an email yesterday to User:Raylton P. Sousa, who maintains the BookManager extension and was on the mentors list for GSoC 2012, but I've not heard back as of yet. Do you have any suggestions for people who might have relevant knowledge and would be willing to mentor?

As for Bugzilla, there are quite a few bugs that are somewhat related. The issue of having a way to represent books is namely mentioned in bug 15071. There are also a number of bugs specifically related to the BookManager extension here. Do you think I need to create a new request, or are these close enough?

I will send an email to wikitech-l shortly.

Thank you!

Bug 15071 is blocking several others and it's followed already by 12 people, including some maintainers that have commented. So yes, it's a good destination to announce your project proposal.

Raylton was indeed interested in mentoring. Being a maintainer of the BookManager extension and a pt.wikibooks.org admin he seems to be the ideal mentor for your project, yes. But you don't need to wait for his answer to announce your project idea at Bugzilla and wikitech-l.

But before I would still try to polish your project summary a bit. Are you able to summarize in one sentence the solution your project aims to deliver? If you can, use it as opening of the summary. It's amazing how impatient readers are nowadays...  :)

Alright, I will announce the project there and on wikitech-l after I put a little more work into the proposal! Thanks for the feedback.

Latest news from the Wikimedia Collaboration team, about Map improvements 2018, Notifications, Structured discussions and Edit Review Improvements. Please tell other users about these changes. Not all changes will affect you.

What's new?

The Collaboration team has announced the start of a new project: In-Context Help and Onboarding. The idea is to improve retention of new wiki editors by giving them short tutorials and other training experiences related to, and triggered by, their current activities on the wikis (that’s the “in context” part). The project follows from the conclusions of the New Editor Experiences research. The work is in its very early stages, but we’d like to hear from people with ideas on the subject—particularly if you have experience supporting or training new contributors.

Map improvements 2018 [More information]

• Maps using Maplink and Mapframe functions now include an extra zoom level (level 19). This is part of the Kartographer Improvements, the number one request of the 2017 Community Wishlist survey.

Edit Review Improvements [More information • Help pages]

• Number of edit to show in recent changes information text was incorrect in Special:Preferences. It has been rephrased.

Notifications [More information • Help pages]

Recent changes

• You can notify users in edit summaries. They will get a ping just as if they had been mentioned on a wiki page. That new feature has been documented.
• Preferences panel on Special:Notifications was overlapping other elements. This has been fixed.

Future changes

• An important work is under progress to allow thanks of log entry. This is done by the Community Tech team.

Structured discussions [More information • Help pages]

Recent changes

• Structured Discussions extension has been uninstalled from wikis not using it. However, it is still possible for a community to request a trial of Structured discussions.

Problems

• It was not possible to opt-in and opt-out Structured discussions on wikis using it as a Beta feature. It is now fixed.

Future changes

• The visual editor and 2017 wikitext editor interface is going to change for consistency. The toolbar, dialogs and menus will appear slightly bigger; some icons will look different. Content or functionality will not change. That change will apply to Structured Discussions as well.

Collaboration team's newsletter prepared by the Global Collaboration team and posted by bot • Give feedback • Subscribe or unsubscribe.

12:25, 26 March 2018 (UTC)

Latest news from the Wikimedia Global Collaboration team, about Map improvements 2018, Notifications, Structured discussions and Edit Review Improvements. Please tell other users about these changes. Not all changes will affect you.

What's new?

• Collaboration and Language are now going their way separately. Updates about Content Translation are not included in this newsletter anymore. Please refer to the Language report.
• Collaboration has a new project: Map improvements 2018.
  • The team’s engagement with maps is based on 2017 Community Wishlist proposal Kartographer Improvements, though the work won’t be restricted to items named there.
  • The project is currently in its very early research and planning stages.
  • It has a limited term that’s scheduled to conclude at the end of June 2018.

Edit Review Improvements [More information • Help pages]

Recent changes

• es.wikipedia, es.wikibooks, sv.wikipedia, and simple.wikipedia get ORES predictions on Recent Changes (and on Watchlist through "New filters for edit review" Beta feature).

Problems

• The explanation of the abbreviations on the recent changes page could overlap with the list of changes. This has been fixed.
• On Related changes it was not possible to use Saved filters for several articles. It has been fixed.
• Transclude special:relatedchanges on a subpage removed #contentSub. This is now fixed.

Notifications [More information • Help pages]

Recent changes

• The wording when you send a thanks message has changed. Instead of Yes or No it says Thank and Cancel. It is also now easier to understand that all thanks are public.
• A notification is now sent to account owner on multiple unsuccessful login attempts.

Problems

• Between week 7 and 20 February, when you thanked someone for an edit, the thank went to the latest unthanked edit to that page. It didn't matter which edit you tried to give thanks for. This has been fixed.
• Long page titles on Special:Notifications were not truncated. This is now fixed.

Structured discussions [More information • Help pages]

Recent changes

• You can now press CTRL + ENTER to post a new message.
• It wasn't possible to create a description of a Structured discussions board. This has been fixed.

Problems

• On wikis using the Beta feature, it is not possible to enable or disable Structured discussion from the Beta page. However, admins can create and move the pages.

Collaboration team's newsletter prepared by the Collaboration team and posted by bot • Give feedback • Subscribe or unsubscribe.

11:29, 5 March 2018 (UTC)

Latest news from the Wikimedia Global Collaboration team, about Notifications, Structured discussions, Edit Review Improvements and Content translation. Please tell other users about these changes. Not all changes will affect you.

What's new?

• The Global Collaboration report for December is now available (in English).
• Filters are better integrated on Related Changes (see below).
• Structured discussions now use the 2017 wikitext editor (see below).

Edit Review Improvements [More information • Help pages]

Bug fixes

• When searching, a click on a filter capsule moved the list of filters.
• On Related Changes page, the page name entry box didn't show the entirety of long page names.
• Transcludeing Special:RelatedChanges on a page added unexpected parameters to the URL.
• Filter menu was opening upwards.
• ORES preferences on Recent Changes and Watchlist preferences pages have been rationalized.
• Users are now prevented from clicking on a link when they click outside of the dropdown menu to close it.

Work in progress

• Filters on Related Changes page are better integrated and get new features, for instance:
  • The standard auto-completion mechanism is available when you search for a page to look at.
  • It is more clear if you are looking to pages linked from the target page or to the target page.
  • You no longer need to click the "Show" button; the page updates automatically when a page is positively identified via autocompletion.

Content translation [More information • Help pages]

Recent changes

• Further enhancement are made for list (Suggestions/In-progress/Published) items on mobile screens. Long titles no longer overflow or overlap with other interface elements.
• Various changes to the "New translation" dialog and the selected page for translation have been made:
  • Longer titles of selected pages are displayed in smaller. Some space has been added around to increase readability.
  • Language codes are not truncated by ellipsis anymore. Only full, autonym language names are subject to truncation.
  • Minimal screen sizes and selected suggestion dialog have been revisited. They are more consistent in responding to screen size changes.
  • Discard button is no longer shown on small screen sizes.
• Language filters no longer render wrong or non-existent language codes.
• The "New translation" dialog now shows a loading indicator and doesn't display an error when you change the source language after an unsuccessful research.

Structured discussions [More information • Help pages]

Recent changes

• Structured discussions now uses the 2017 wikitext editor instead of its old custom one. This works with your preference for wikitext or visual editor.
  • The documentation has been updated and needs translations updates.
• Prométhée, from French Wikipedia, has created some gadgets to customise Structured discussions interface.
  • The documentation is ready to be translated.

Future changes

• Structured discussions does not always follow wiki's configurations concerning talk pages indexation. This will be fixed.
• Hidden topics will not be indexed by search engines anymore.

Notifications [More information • Help pages]

Bug fixes

• User rights change notifications were displaying a broken link. This is now fixed.
• "Mark as read" buttons had a bad appearance for users who don't have JavaScript activated.

Collaboration team's newsletter prepared by the Global Collaboration team and posted by bot • Give feedback • Subscribe or unsubscribe.

00:56, 25 January 2018 (UTC)