User talk:Quiddity

Hi, you're welcome to leave a message for me here,
or at w:User talk:Quiddity on the English Wikipedia. Thanks!

JS

Did it work or not? (Please don't use the CSS, it's borked. The JS works for me, but not the CSS.) PiRSquared17 (talk) 00:05, 15 September 2013 (UTC)

@PiRSquared17: It worked so well, that I have 15 tabs open (starting from w:WP:User scripts), and I was looking to see (a) what else I want to experiment with, and (b) whether your script was already included in there, or if I needed to suggest that you add it! (w:Wikipedia:WikiProject User scripts/Scripts#Watchlist is where it belongs ;)

I assume the JS code works identically at En.wiki? (no cleanchanges there, so nope). How would I/we achieve the same thing at En.wiki?

The CSS does work for me, and whilst I do not forsee myself ever needing to collapse the individual items, I guess there might be a heavy-activity day at some forum/rfc/etc, so I'll reset to just using the JS.

[Also, I'm not familiar with JS, so I wasn't sure how to interpret your "eval is evil" comment - is that like "tables are evil (html layout wise)" or more like "This is madness (and could make my processor lose it's magic smoke)" ? (I assume the former, and am mostly joking with the latter ;) ]

Maybe I can finally start using "expand my watchlist" on En.Wiki, after 8 years of avoiding it! Thank you! Quiddity (talk) 00:25, 15 September 2013 (UTC)

@PiRSquared17: Oh, I've found w:user:js/watchlist which claims to do the same thing (amongst other things) - However, the "±" doesn't appear for me, so that feature seems to be broken (Everything else works well). Possibly that code-method is either fixable, or replaceable with your own eval method? (Utterly beyond my code comfort zone). It might make a lot of people happy, to have that feature back! Quiddity (talk) 01:18, 15 September 2013 (UTC)

Hello! I actually just wrote that, after you suggested it. I could probably improve it, but the user won't notice a difference. It should work on any wiki using enhanced RecentChanges. Currently it's just a one-line mess of JavaScript. eval is not always "evil", but it's not good to use it on untrusted input, and it can be slow (but it shouldn't be in this case). Basically, eval is a feature of a programming language that evaluates code in that language. In this case, the JS code in located in a link address (javascript:... "URL"), and I ran it by removing the "javascript:" (11 characters - that's where the 11 comes from) and evaluating the rest.[1] There are better ways, probably, but it was only a quick fix.

I was not aware of the other script. Are you sure it doesn't work? I can try to fix it, but I can't guarantee that I will succeed. I've also promised to help angwiki and gotwiki with technical matters... for a year. PiRSquared17 (talk) 01:25, 15 September 2013 (UTC)

@PiRSquared17: Your JS code doesn't work at En.Wiki - there's no "toggleVisibilityE" in the html source, which I assume is the problem?

The w:user:js/watchlist definitely doesn't work (to toggle the collapsed sections) at En.wiki - I tried purging cache. (However, I much prefer the way that your code doesn't require any interaction from me, and just auto-opens everything on load. So just a fix your code, on En.wiki, is my preference.) Thanks again, and thanks for the explanation of eval; eventually I'll fill a bucket with all the drops of programming knowledge I'm slowly collecting. :) Quiddity (talk) 01:37, 15 September 2013 (UTC)

Try

$(window).load(function() { $('.mw-enhancedchanges-arrow').click(); });

I assume you know a bit about HTML and/or CSS selectors. On Meta, the arrows aren't in any specific class, but can only be identified by the fact that they are links beginning with "javascript:toggleVisibilityE". On enwiki, the arrows are in the class "mw-enhancedchanges-arrow", which makes it much easier to fake-click them via jQuery. ;) I don't know why there is a difference, but I assume it has to do with CleanChanges vs enhanced RC (I honestly didn't realize there was a difference until just now.) Note: this code is untested. PiRSquared17 (talk) 01:47, 15 September 2013 (UTC)

@PiRSquared17: Tested and works, at En.wiki. Fantastico!

I do know HTML and CSS, circa 2005 (i kept uptodate from 1998 till original CSS Zen Garden era). I can copy and occasionally hack apart javascript and other languages, but I don't readily take to it. Similarly, I've used Ubuntu for (8?) years now, but I still have to look up the man pages every time I do anything in the console. I've read numerous books and used a handful of tutorials (tryruby being the best), but it refuses to sink in past the surface, and every language variant just muddles the bits that do stick in my memory (I've tried to put DOS commands in the Bash terminal soooo many times). So yes, I can basically understand what your code is doing, but I definitely couldn't have written it! Much thanks again.

If you haven't already, I'd recommend adding your code somewhere at that User scripts page. Quiddity (talk) 04:09, 15 September 2013 (UTC)

I will do this later today or tomorrow and I'll see what I can do with the ± on that other script. PiRSquared17 (talk) 04:27, 15 September 2013 (UTC)

For Meta/CleanChanges:

1. To expand the user talk/contributions, and expand each entry, use the code currently on my common.js here. I made it look a little nicer.

   Note that the $(...) now has a comma with two separate selectors. You may remove either, if you want to disable either the auto-expand edits or the auto-expand user links.

   I made a fancier version with a button to expand/collapse. Try that.

For EnWiki/enhanced RC: [2]

I will work on the other script that you said is broken. PiRSquared17 (talk) 17:55, 15 September 2013 (UTC)

@PiRSquared17: Fancier version almost works - the userlinks don't auto-expand. (But the manual toggle does work). That's "good enough" for me, so it's your call whether or not to spend time fixing it. Quiddity (talk) 18:06, 15 September 2013 (UTC)

Fixed. The non-fancy version also does this now. PiRSquared17 (talk) 18:08, 15 September 2013 (UTC)

@PiRSquared17: Much <3 !! Quiddity (talk) 18:14, 15 September 2013 (UTC)

Upcoming IdeaLab Events: IEG Proposal Clinics

Idea Lab

Idea Lab

Hello, Quiddity! We've added Events to IdeaLab, and you're invited :)

Upcoming events focus on turning ideas into Individual Engagement Grant proposals before the March 31 deadline. Need help or have questions about IEG? Join us at a Hangout:

• Thursday, 13 March 2014, 1600 UTC
• Wednesday, 19 March 2014, 1700 UTC
• Saturday, 29 March 2014, 1700 UTC

Hope to see you there!

This message was delivered automatically to IEG and IdeaLab participants. To unsubscribe from any future IEG reminders, remove your name from this list

Barnstar and a request for feedback

	Individual Engagement Grant Barnstar
	Thank you for commenting on Individual Engagement Grant proposals during this recent round! We really appreciate that you took the time to share your thoughts. To help us improve the IEG program for future participants, would you mind taking this quick 3-question survey? Thanks again for your help, --Siko and Haitham, Wikimedia Foundation Grantmaking

Re: GLAMs value analytics/metrics

Did you check outreachwiki:GLAM/Case_studies? Nemo 08:56, 23 January 2016 (UTC)

@Nemo bis: I did, and I even got as far as outreach:GLAM/Indicators_of_Success#Indicators_related_to_visitors, but I couldn't find the specific example that I fuzzily-remember. :-(

I'm trying to find details, in order to help explain the value of analytics to Goldzahn over at Talk:2016_Strategy/Knowledge#Bluerasberry (and how analytics help organizations to rationalize putting dedicated/ongoing resources into the work/donations over many years, instead of just a one-time experiment). I was hoping to include a great example or two, if you can think of any specifically. If not, I'll just explain the abstract benefits, in a few days. Cheers! Quiddity (talk) 22:41, 26 January 2016 (UTC)

mw:Mobile Gateway/Mobile homepage formatting

Hi, do you know if this is still the best/only help page on how to configure/style a Wikimedia project main page for MobileFrontend? Perhaps it should be moved to Help or Manual namespace, the basepage makes little sense nowadays. --Nemo 20:15, 23 May 2016 (UTC)

@Melamrawy (WMF): might be able to answer that. I'm not familiar with MF. Quiddity (WMF) (talk) 02:42, 24 May 2016 (UTC)

Translation administrator

Hi. I assume that Echo has already notified you. In any case, I've closed your request as successful and granted the translation adminship toolkit on this account. Enjoy :-) —MarcoAurelio (talk) 11:02, 16 July 2017 (UTC)

Bug in our user group page?

Hi Quiddity! I come over to you because I have seen you fixed a syntax problem in the Basque Wikimedians User Group. The issue lies with a link in this section: Activities 2017. That link should direct to this page, still it brings you to 2016. I wonder if you could help with this. --Iñaki LL (talk) 22:26, 25 February 2018 (UTC)

@Iñaki LL: fixed. :) (All tvars on a page should be unique). Cheers, Quiddity (talk) 22:33, 25 February 2018 (UTC)

Wow Quiddity, that is actually fast... and great:) Thank you! --Iñaki LL (talk) 22:36, 25 February 2018 (UTC)

Timeless Newsletter • Issue 2

Newsletter • August 2018

The second issue of the Timeless newsletter is out.

The news: Themes are coming to Timeless! Your infobox and navbox templates in particular are probably going to look absolutely horrible in the new built-in night mode.

For more information, background, plans and progress updates, please see the full issue on Meta, complete with a ridiculous list of phabricator task links, gratuitous mention of other skins, and me complaining about the current state of MediaWiki skinning in general.

-— Isarra ༆ 01:48, 30 August 2018 (UTC)

Thanks for your benevolent spontaneity ...

Thank you. I didn't know the utility of <pre></pre>.
At least one utility in Windows— the centralised Help files in .chm format— works far better. Wikipedia/Wikimedia -'s Help pages appear scattered. Or perhaps, there is an utility in Wikipedia to peruse the help pages centrally, of which I am oblivious.
But everything in Wikipedia is very verbose. I liked your The_source_of_many_disagreements.png file. Far better spoken visually/symbolically than that would have been possible in words. Generally applicable in most cases to reduce verbosity.
I have already sent you Thanks messages. But on hindsight they were not good enough gesture.
Thanks once again.
Bkpsusmitaa (talk) 08:14, 13 December 2018 (UTC)

@Bkpsusmitaa: Thank you very much! I sometimes enjoy wikifying things I find in RecentChanges. I agree, our documentation has many problems - that is what 17 years of organic growth from thousands of volunteers and some paid staff can end up with! Eventually it will improve. I also appreciate brevity and obviously infographics. Best wishes, Quiddity (talk) 08:29, 13 December 2018 (UTC)

Timeless Newsletter • Issue 3

Newsletter • December 2018

Welcome to the third issue of the Timeless newsletter, complete with a somewhat dubious explanation of where I've been all this time.

Somewhat dubious explanation of where I've been all this time:

I suffered a rather bad concussion in October, which knocked me pretty much completely out of commission through November, and I'm still recovering even now. One person = bus factor of one, even though it wasn't actually a bus but a very short flight of stairs.

Updates:

• Random bugs have been fixed. More bugs have been found. For a full list of horrors, see the workboard.
• Implementing themes (T131991: the dark/night mode and winter variants of the skin) has proven far more complicated than initially thought, lacking either the extension, or preferably, some core support for this functionality. Thus:
  • I have submitted a Request for Comment proposing to merge Extension:Theme into core - this will enable skins to specify style variants as distinct options for users to select in their preferences by letting the skin specify the styles separately for each, a much neater way of implementing this than some of the existing hacks.
  • Jack Phoenix has already submitted a patch to do this. We simply need the buy-in and consensus to merge it, and to resolve whatever issues may arise from this wider review.

Comments on the RfC (MediaWiki wiki RfC page, task) or bugs, or further reports, are always appreciated.

Until next time, hopefully with no further injuries,

-— Isarra ༆ 22:35, 20 December 2018 (UTC)

Thanks!

Thanks, Quiddity, for reading and correcting this page. It's very appreciated, and I changed the related Commons file accordingly. -- Have a good new year! Johanna Strodt (WMDE) (talk) 09:34, 7 January 2019 (UTC)

Wiki Project Medicine Foundation Membership

Membership renewal

Dear Wiki Project Med Supporter, you are receiving this message as you have shown interest in supporting Wiki Project Med in the past. As our organization grows and evolves, we want to be able to verify peoples ongoing interest in being involved. To that end, the board has decided to require renew of membership every two years. So -- whether you are a current member or not, please fill out our updated membership form, to ensure your membership till the end of 2020. Please note -- We ask that you fill out the form by Feb 3rd, as we are close to elections and only members can nominate themselves for the board and vote!

Best, Shani & Doc James. 01:57, 28 January 2019 (UTC)

thanks

Background helps. Personal opinion is that is not needed, though a decision doesn't come from personal opinion.

Timeless Newsletter • Issue 4

Newsletter • April 2019

Welcome to the fourth issue of the Timeless newsletter, with a cat! Or maybe not.

Un chat qui miaule???

It's true! The angry cat, a fundamental part of Timeless, has resulted in confusion and bug reports all across the projects and phabricator. And now it shall be immortalised forever in the new, shiny Timeless logo.

Updates:

After putting off the project for three months because I got hit in the head with a flight of stairs, and then putting off the project for another two months while working out what the status of the grant was, I have now put off the project even more in order to focus on my other project for a bit. So progress lately has been a bit whims-based as a result:

• The project now has a logo. For some reason.
• The angry cat in the background is now customisable! Behold: not a cat. What would you like to replace it with on your project?
• I broke, unbroke, and then sort of sideways broke all the form styles. Help.

Radar:

• The French Wiktionary voted to set Timeless as their default skin, with results possibly as you might expect: I ran away and hid, and the WMF said no. A bit of discussion later and we largely agreed that all else aside, this is a bit of a branding issue, but we love the enthusiasm! Also the bug reports that inevitably come out of such a discussion. I'm still working on properly going through those.
• Theme support is still stuck in limbo, but now we have another skinning RfC. tl;dr, we wanna replace the entire skinning system, and Skizzerz'll write a prototype later.

I will be fully resuming work on Timeless next week, or maybe the week after, depending on what madness (or illness) comes out of the Hackathon in Prague. Please come talk to me there to discuss strategy!

-— Isarra ༆ 16:51, 14 May 2019 (UTC)

Timeless Newsletter • Issue 5

Newsletter • August 2019

Welcome to the fifth and final issue of the Timeless newsletter!

Progress was made. True story.

I am happy to announce that after about a year, this delightful project in which absolutely nothing has gone according to plan is coming to a close. Or at least, the grant-funded portion is. Which means we will now be resuming our regular schedule of random whims-based development, you probably won't notice any difference whatsoever unless you use MonoBook, and there's a report.

What's new from the past two months:

A lot less than we'd hoped, frankly. We:

• Fixed various bugs, some of which even weren't for stuff I'd just broken two patches previously.
• Resolved sundry compatibility issues for other extensions, templates onwiki, whatever, largely by removing dumb crap from the css.
• Implemented some shiny new features you'll probably hate or just never use or actually see, like click-toggled dropdowns, icons everywhere, and options to select a default layout or set an image for the site header wordmark.
• Brought the total number of open tasks on the Timeless workboard down to 70.

We also wound up with:

• Patches resulting in RelatedArticles working in MonoBook, and FlaggedRevisions showing up in Minerva, unless someone actually managed to turn that off as well. (Blame T181242.) It's possible we went a little overboard with the whole 'let's close all the tasks!' sprint.
• An unfortunate repeated discovery that themes (the Night/Winter variants I keep insisting will happen at some point) are still pretty far off on the horizon. Um.
• Possibly a quite a few more bugs coming your way. This month, and especially the past week, have been a bit of a mess, development-wise. While hopefully none of the worse issues make it to production, please keep the reports coming for whatever you do find and we'll get it fixed as soon as we can. Y'all've been amazing about this, and it's really appreciated.

And I guess that's that. I'm really bad at reporting, and this is a report. For the purposes of the grant, this was a requirement, but do you want me to keep trying to send these out?

-— Isarra ༆ 18:08, 31 August 2019 (UTC)

Watchlist Expiry project page

Hello,

During the Community Whishlist survey 2019, you have voted for the Watchlist item Expiration wish.

Community Tech has created the Watchlist Expiry project page to work on this feature, and is looking for your feedback about the open questions they have.

Regards, IFried_(WMF), 15:51, 25 September 2019 (UTC)

Thanks for your help

Hi there, translator! Here's a little token of appreciation for a recent effort you contributed to. Surprised? Well, the best is yet to come.

• We'd love to send you this badge as an actual sticker. If you want, you can use this Google Form to communicate your address so we can ship it to you. Note that we will close the form on October 13, 2019, and all data will be removed shortly afterwards. Details about this external site are provided at the top of the form.
• We also have this badge waiting for you on Wikimedia Space. You can use the form linked above to let us know what your username is on this brand new hub, so that you can get the award there as well. If you don't have an account yet, just go ahead and enjoy joining via Wikimedia login in just a few clicks. (And in case you hadn't heard yet, you can join the community of translators there as well).

Again, thanks for everything you are doing to make this movement a better (and multilingual!) place: please do not hesitate to reach out if you have questions, and I hope to hear from you soon. Elitre (WMF) (talk) 10:33, 28 September 2019 (UTC)

Mix'n'match and soweego: call for support

Dear @Quiddity:

       TL;DR:

• soweego catalogs are in Mix'n'match.
• Why don't you show your support with a star?
• https://github.com/Wikidata/soweego

First, thank you for being a Mix'n'match [3] user.

Does the name soweego ring you a bell?
It's a machine learning system that links Wikidata to large catalogs [4].
It's a close friend of Mix'n'match, which mainly caters for small catalogs.

The latest catalogs uploaded by soweego need some love: why don't you check them out?
If you are a music enthusiast, Discogs and MusicBrainz are what you need: musicians [5], [6], bands [7], [8], and records [9], [10].
Are you passionate about cinema? IMDb is there with actors [11], directors [12], musicians [13], producers [14], writers [15], and movies [16].

I would be really grateful if you could support soweego with a GitHub star:
https://github.com/Wikidata/soweego

Best,

--Hjfocs (talk) 13:16, 24 October 2019 (UTC)

AI legislation

Dear Quiddity,

I contact you since you are marked among the "People who are interested" in Advanced technology page. As you might already know, the EU is working about a regulation of the AI environment, in order to promote its potential and at the same time to protect the citizens from unwanted uses. It is going to be an important moment for achieving the most empowering, safe and clear definition of the rights and duties related to the AI, affecting also Wikimedia's opportunities, not only inside EU. I kindly invite you to participate to the discussion, firstly by commenting the page that is dedicated to it, in order to draft Wikimedia's answers to this legislative initiative of the EU.

The linked page contains the questions from the public consultation by the European Commission on its Artificial Intelligence White Paper.

The EU's survey will remain open until 14 June 2020, but we will take input into account until 31 May 2020.

Thanks, --sNappy(talk) 21:27, 17 May 2020 (UTC)

User:CreativeC/Proposal

Here is the text of that page before it was pruned, then deleted.

Text
{{Languages|User:Archi38/Proposal}} {{New sister project proposal |status = discussion |project_name = Wikigames |topic = Gaming wiki |project_description = A detailed wiki on video games, consoles, publishers, reviewers. The wiki would also be a how-to guide. |multilingual_wiki = In all languages. At first only in a few languages. |multilingual = Like Wikipedia, each language who wants a wiki must goes through the incubator. |technical_reqs = See ''[[User:Archi38/Proposal#Licenses|License]]'' |tagline = The gaming wiki |url = [http://wikigames.org wikigames.org] (avaible) |logo = [[File:GamesWiki.svg|200px]] |more_settings = |development_wiki = [http://le-goutergfvc.alwaysdata.net/index.php?title=Accueil Test wiki] |participants = {{u|Archi38}} }} <div style="background:#FFF; padding:4em"> <h2 style ="font-weight:bold; text-align:center;"> Goals </h2> Wikigames is a gaming wiki, its objectives would be : * Being a complete guide for Video-games : each item, character, world or game engine will have its own page, no matter its notoriety. * Be able to do a precise report of reviews and players, in order to let us have an neutral opinion. Reviews will be elaborated : for example, we will compare two similar games. And sources used will be up to date. In the same time, we will tell what which was the current update when sources have been written. Youtubers will be valid sources. * Be a how-to guide : System requirements and potential game bugs (and maybe games soluce?) will be written. <h2 style ="font-weight:bold; text-align:center;"> Various specifications </h2> === Article templates === It would be article templates like on Wikivoyage ==== Editor ==== ''Editor'' is a video games editor created in ''Date'' based in ''City'' * Story * Locations and subsidiaries * Games ** Main franchises * Critics * See also ==== Universe ==== Universe of ''game'' is a ''Fantastic/Fictional/Uchronic…'' universe. * Story ** Groups ** Characters ** Critics ** See also ==== Character ==== ''Character'' is a character of ''Game''. * Creation and evolution * Story * Apparitions * Annexes ==== Game ==== ''Game'' is a game developped by ''Developer'' and published by ''Editor'' in ''Date''. * Universe *:''See the complete article + summary'' ** Story ** Characters * Gameplay * Development * Critics * Installation ** Required configuration * See also ==== Environment ==== ''Map'' is a map in ''Game''. * Development * Description * Caracteristics * Critics ==== Reviewer ==== ''Reviewer'' is a ''Kind of media'' wich publish critics on ''Platform'' games. * Story * Critics *:''Critics of community and other reviewers'' * See also ==== Developer ==== ''Developer'' is a video game developer created in ''Date'' based in ''City''. * Story * Locations and subsidiaries * Games ** Main franchises * Critics * See also ==== Console ==== ''Console'' is a console made by ''Company''. * Story * Development * Technical caracteristics * Exclusives * Critics * See also === Collaboration of the month=== Collaboration of the month would be an article promoted for a month on the main page. The wikigamers would focus on the article, which would be mostly dedicated to consoles, developers or publishers. === Flow & Content Translation === Flow and Content translation would be installed as Beta Feature and the Village pump would have Flow on it. === License === In a contribution, users should be able to choose between all licenses that MediaWiki offers and be able to specify where do texts come. (Explanations in the argument 2) === Pages === We would have a different page policy as Wikipedia. As Wikivoyage, we would say that a draft is better than nothing. === Categories === In the header, you can search for games by genre, release date, series, country, theme developer, publisher or distributor. So we will have to classify games conscientiously. === Portals and projects === Projects and portals would work like on Wikipedia. The portal could look like [[w:en:Wikipedia:WikiProject Square Enix|this]]. Authorized portals would be about games, franchises, publishers, developers and consoles. === Geography === Wikigames also touch games by geography, indicating in wich city / country is located an editor / a critic ... And where was conceived a game / a console ... === Appearance === Wikigames wants to be more modern, as shown in the home page of the test wiki, to attract a wider community. Most of the icons would be imported from [https://thenounproject.com The Noun Project] and the main colors of the wiki would be the colors of the Wikimedia {{colorbox|#006699|blue||white}}, {{colorbox|#339966|green||white}} {{colorbox|#990000|red||white}} and {{colorbox|#4d4d4d|gray||white}} <h2 style ="font-weight:bold; text-align:center;"> Arguments </h2> * Video-games have lack of good community in most languages, and main communities are managed by big companies that only wants to earn money (like Curse), or enthusiast amateurs who can't handle them properly and ends by giving up. * Most of video-games wikis uses MediaWiki and suggested CreativeCommons licences. Consequently, this is content that can be used freely. * Wikigames will certainly have a huge community, thanks to every others wikis and communities mentioned before, they will gather around this serious and democratic wiki, moreover there will be video-games project members (projects that, in most Wikipedia languages, are among the most organized and active projects). * Video-games are a way to learn, create and share. It's a collaborative activity where people of any age, any social class and location can meet. It's an art that deserves its own wiki. * There is more than enough content to fill an entire wiki. * No more eligibility issues with pages on Wikipedia : Criterias will be more rigorous. * Community will be younger. This will attract young people on the Wikimedia. * We can compare it with Wikivoyage: Highlight content that could be divided onto both Wikipedia and Wikibooks by organizing it in a different way. </div> == Discussion == It might be interesting in seeing how this proposal relates to the existing collaboratively produced games reference sites. Perhaps a table -- listing features, inclusion criteria, subpage examples, etc, -- for sites such as Mobygames, KLOV, etc. (e.g. Mobygames includes links for everyone listed in the credits who worked on a game, such as [http://www.mobygames.com/game/ps2/katamari-damacy/credits Katamari Damacy].) What would Wikigames solve, that these sites don't already cover? Or how would it do it better? [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 23:34, 23 April 2016 (UTC) : The idea is to have better wikis, without wikia restrictions and pubs, with an effective moderation system, to bring good information to all languages and to put in a single wiki all information wich are currently dispersed over multiple sites (and most of the time only avaible in english). It also would be an up to date site: most of websites still say that Team fortress 2 have too few maps whereas is was true 8 years ago, but Wikigames would tell that it changed. [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) The proposed logo is associated with a few specific types of games. Would Wikigames cover: Video games, PC games, arcade games, mobile games, board games, card games, ball games, pen&paper games, pinball machines, etc? [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 23:34, 23 April 2016 (UTC) : It will cover all video games, including all consoles, PC, linux, mobile, VR games [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) Re: "The wiki will also be a practical guide" - this opens it up a lot further, to comparison with sites like GameFAQs, 1up, gaming.wikia.com, strategywiki.org, etc. for the longtail of games, and to the entire set of game-specific wikis such as those on Wikia. I don't think this is practical, for either readers or writers, for a number of reasons: * There are already such large quantities of good user-generated or user-compiled content at those sites, that we would have a hard time offering a competitive offering. *: Yeah, it will be really hard [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) * Those other sites seem to (? IANAL) skirt around fair-use issues quite frequently, whereas we would almost certainly have to hold to a stricter standard. *: Of course. But there's also lot of little games under free licences that you can put screens. [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) * Some of those other sites have well-established communities, and if we started a successful competitor (mind-share-wise) that could potentially harm them by fragmenting the limited userbase. *: We have already competed many sites (and paper encyclopedias) with our previous projects. [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) * Those sites are already a cluster at the top of search-engine results, e.g. wowwiki.wikia.com, wow.gamepedia.com, ca.ign.com/wikis/world-of-warcraft, wow.allakhazam.com/wiki/, wow.neoseeker.com, etc, which can be a frustration for readers seeking the best information in a single spot. Hope that helps. [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 23:34, 23 April 2016 (UTC) : Sorry it was a translation error, I just wanted to say guide. [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) This should probably be merged with the older proposal, [[WikiGames]]. [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 23:34, 23 April 2016 (UTC) : A steward told me I could make a new page named something like [[Wikigames (2)]] [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) ::Ah, yes, that's a better solution. [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 22:37, 7 May 2016 (UTC) {{Ping|Quiddity}} Please could you help by telling me all unclear things in my proposal ? Thank you [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 08:38, 24 April 2016 (UTC) :{{Ping|Quiddity}} {{Ping|Quiddity (WMF)}} I'm desperate, there is no effective procedure, no people voting for new projects, the incubator is only for existing projects, so there is no way to make a demo ... I don't know what to do . On top of that I asked to mark [[Wikigames (2)|the proposal page]] for translation and have no response... [[User:Archi38|Archi38]] ([[User talk:Archi38|talk]]) 16:20, 2 May 2016 (UTC) ::{{ping|Archi38}} Essentially, I believe (I might be wrong on any of these details) that starting a new project requires multiple people having a strong interest, and fundamentally relies upon one or more of those people being adept at community-organizing. Hence, the proposal ideas only get off-the-ground once there is a proven set of individuals who are dedicated to doing the vast amounts of work necessary to start an entirely new project (templates/helppages/guidelines/etc etc etc). It takes a lot of engineering effort to setup the back-end, plus ongoing maintenance forever thereafter, and it is very complicated to shut down a failed wiki group, so it purposefully isn't easy. Just a couple of enthusiastic individuals are not enough. I.e. The chicken-egg question is answered: first ''must'' come the group of interested people, and ''then'' comes the wiki setup. So, first you've got to find the people, and get them discussing and refining this proposal. That might be a case of trying to start discussions with editors involved with Wikipedia gaming WikiProjects, or might involve discussing the idea with external game-documentation communities. ::Re: translation - there are a limited number of multilingual editors, and they all have their personal priorities (i.e. some work on meta, some on mediawiki, and the majority on articles/content in the various sister projects). More importantly, many translators will not work on a meta/mediawiki page that is undergoing large changes, because then their efforts would rapidly become outdated. TLDR: Don't expect (or even ask for) any translation until the ideas within the primary document are fairly solid. ::Hope that helps. [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 22:35, 7 May 2016 (UTC) ::Oh, and feel free to copy my concerns across to [[Wikigames (2)]], and refactor as needed to make our discussion clearer for newcomers. I'm afraid I won't be likely to have time to look at this again in the forseeable future. [[User:Quiddity|Quiddity]] ([[User talk:Quiddity|talk]]) 22:37, 7 May 2016 (UTC)

History data
(diff) 2017-07-29T17:08:32 . . علاء (A/S) (talk | contribs | block) m 12,724 bytes (علاء moved page User:CreativeC38/Proposal to User:CreativeC/Proposal: Automatically moved page while renaming the user "CreativeC38" to "CreativeC") (diff) 2016-05-31T12:05:01 . . K6ka (talk | contribs | block) m 12,724 bytes (K6ka moved page User:Archi38/Proposal to User:CreativeC38/Proposal: Automatically moved page while renaming the user "Archi38" to "CreativeC38") (diff) 2016-05-07T22:37:37 . . Quiddity (talk | contribs | block) 12,724 bytes (→‎Discussion: addendums) (diff) 2016-05-07T22:35:50 . . Quiddity (talk | contribs | block) 12,297 bytes (→‎Discussion: reply) (diff) 2016-05-02T16:20:37 . . CreativeC (talk | contribs | block) 10,523 bytes (→‎Discussion) (diff) 2016-04-28T15:40:55 . . CreativeC (talk | contribs | block) 10,103 bytes (→‎Arguments ) (diff) 2016-04-28T15:10:50 . . CreativeC (talk | contribs | block) 10,051 bytes (→‎Appearance) (diff) 2016-04-28T15:07:44 . . CreativeC (talk | contribs | block) 10,021 bytes (→‎Portals and projects ) (diff) 2016-04-28T15:03:11 . . CreativeC (talk | contribs | block) 10,009 bytes (→‎Article templates ) (diff) 2016-04-28T14:57:58 . . CreativeC (talk | contribs | block) 9,992 bytes (diff) 2016-04-27T20:08:58 . . CreativeC (talk | contribs | block) 9,993 bytes (diff) 2016-04-27T05:27:08 . . CreativeC (talk | contribs | block) 10,030 bytes (diff) 2016-04-25T20:57:07 . . CreativeC (talk | contribs | block) 10,005 bytes (→‎Article templates ) (diff) 2016-04-24T08:43:03 . . CreativeC (talk | contribs | block) 8,997 bytes (diff) 2016-04-24T08:39:31 . . CreativeC (talk | contribs | block) 8,981 bytes (→‎Discussion) (diff) 2016-04-24T08:02:06 . . CreativeC (talk | contribs | block) 7,323 bytes (→‎Flow ) (diff) 2016-04-23T23:35:33 . . Quiddity (talk | contribs | block) 7,277 bytes (→‎Discussion: comments) (diff) 2016-04-23T22:53:36 . . Quiddity (talk | contribs | block) 4,952 bytes (change headers, to provide [edit section] links) (diff) 2016-04-23T19:11:27 . . CreativeC (talk | contribs | block) 5,054 bytes (diff) 2016-04-23T18:25:36 . . CreativeC (talk | contribs | block) 4,622 bytes (diff) 2016-04-23T16:48:40 . . CreativeC (talk | contribs | block) 4,066 bytes (diff) 2016-04-23T16:31:43 . . CreativeC (talk | contribs | block) 4,065 bytes (diff) 2016-04-21T13:46:06 . . CreativeC (talk | contribs | block) 3,389 bytes (→‎Article templates ) (diff) 2016-04-20T19:21:45 . . CreativeC (talk | contribs | block) 3,225 bytes (diff) 2016-04-20T19:11:09 . . CreativeC (talk | contribs | block) 3,177 bytes (diff) 2016-04-20T18:48:07 . . CreativeC (talk | contribs | block) 2,973 bytes (→‎Arguments ) (diff) 2016-04-20T18:41:44 . . CreativeC (talk | contribs | block) 2,957 bytes (diff) 2016-04-20T18:39:58 . . CreativeC (talk | contribs | block) 2,923 bytes (→‎Portals and projects ) (diff) 2016-04-20T18:38:12 . . CreativeC (talk | contribs | block) 2,718 bytes (→‎Appearance) (diff) 2016-04-20T18:35:27 . . CreativeC (talk | contribs | block) 2,346 bytes (diff) 2016-04-20T18:26:36 . . CreativeC (talk | contribs | block) 2,188 bytes (diff) 2016-04-20T18:24:28 . . CreativeC (talk | contribs | block) 2,190 bytes (→‎Various specifications ) (diff) 2016-04-20T18:13:54 . . CreativeC (talk | contribs | block) 1,403 bytes (→‎Goals) (diff) 2016-04-10T06:02:24 . . CreativeC (talk | contribs | block) m 1,218 bytes (Discussion) (diff) 2016-04-09T20:07:39 . . CreativeC (talk | contribs | block) 1,200 bytes (Titles) (diff) 2016-04-09T14:53:40 . . CreativeC (talk | contribs | block) 769 bytes (diff) 2016-04-09T14:51:40 . . CreativeC (talk | contribs | block) 2,392 bytes (diff) 2016-04-09T14:29:11 . . CreativeC (talk | contribs | block) 2,370 bytes (diff) 2016-04-09T14:27:35 . . CreativeC (talk | contribs | block) 2,371 bytes (diff) 2016-04-09T14:19:27 . . CreativeC (talk | contribs | block) m 2,356 bytes (Archi38 moved page User:Archi38/Brouillon to User:Archi38/Proposal: More clean) (diff) 2016-04-03T14:29:22 . . CreativeC (talk | contribs | block) 2,356 bytes (diff) 2016-03-20T18:30:36 . . CreativeC (talk | contribs | block) 2,351 bytes (diff) 2016-03-17T06:20:26 . . CreativeC (talk | contribs | block) 2,351 bytes (diff) 2016-03-17T06:12:18 . . CreativeC (talk | contribs | block) 2,298 bytes (→‎Description (in french for now)) (diff) 2016-03-17T06:11:15 . . CreativeC (talk | contribs | block) 2,277 bytes (→‎Patrons d'articles) (diff) 2016-03-17T06:09:11 . . CreativeC (talk | contribs | block) 2,198 bytes (→‎Patrons d'articles) (diff) 2016-03-17T06:07:59 . . CreativeC (talk | contribs | block) 2,180 bytes (→‎Collaboration de la semaine =) (diff) 2016-03-16T22:46:40 . . CreativeC (talk | contribs | block) 2,180 bytes (diff) 2016-03-16T22:45:27 . . CreativeC (talk | contribs | block) 2,167 bytes (→‎Patrons d'articles) (diff) 2016-03-16T22:34:29 . . CreativeC (talk | contribs | block) 1,597 bytes (→‎Description (in french for now)) (diff) 2016-03-16T22:29:59 . . CreativeC (talk | contribs | block) 1,453 bytes (diff) 2016-03-16T18:37:05 . . CreativeC (talk | contribs | block) 663 bytes (diff) 2016-03-16T17:12:41 . . CreativeC (talk | contribs | block) 649 bytes (diff) 2016-03-16T17:08:26 . . CreativeC (talk | contribs | block) 769 bytes (Created page with "{{New sister project proposal |status = discussion |project_name = Wikigames |topic = Gaming wiki |project_description = A detailed wiki on video games, consoles, publishers,...")

— xaosflux ^Talk 21:58, 10 August 2020 (UTC)

Community Wishlist Survey 2021: Invitation

The 2021 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 November, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 December and 21 December.

The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!

SGrabarczuk (WMF)

18:26, 20 November 2020 (UTC)

Community Wishlist Survey 2021

We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.

In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.

We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.

We are waiting for your votes. Thank you!

SGrabarczuk (WMF)

16:09, 11 December 2020 (UTC)

FLOSS-Exchange

Hi! I saw you contributed to FLOSS-Exchange article and (?) coordination, so I wanted to let you know I of potential channels for discussion and exchange are https://CHAT.WMcloud.org/wikimedia/channels/wm-floss-adoption and Telegram a group with the same name. --Zblace (talk) 08:17, 19 February 2022 (UTC)

I need the help of a translationadmin in moving a page

Dear Quiddity,

How is your day going? I don't mean to take so much of your time. I raised a little issue on Babylon's Talk and would be so lucky to have you help out. Thank you Danidamiobi (talk) 22:12, 22 June 2022 (UTC)

Why make OWID integration hard?

You are actively making it difficult to include an extraordinary source of synthesized knowledge. The new 'OWID Gadget' page says nothing about the value of the knowledge being excluded, focusing only on marginal risk. It also says nothing about the many efforts to render this knowledge entirely inside our cluster, and how that has become an irrationally difficult thing to do. A better page would be about OWID itself, including the many efforts to include its data, starting from the reasonable assumption that it is important to do so and many people in many languages are working on making that happen. –SJ talk  04:11, 28 April 2024 (UTC)

Hi SJ. I'll pass your comment along to the folks working on this. I was just helping with the page-creation. (n.b. answering here with my work-hat.) Best wishes, Quiddity (WMF) (talk) 20:29, 29 April 2024 (UTC)

AI call 16 May

Hi, you're getting this message as you've signed up as interested in the topic at the Artificial intelligence page.

You might already be aware of this, but in case you had missed other announcements I wanted to send out a reminder about the Wikimedia AI call which is happening tomorrow, 16 May, at 14:00 UTC. There will be presentations from various parts of the movement, with space for questions and discussion. The call will be recorded, if one prefers to watch if afterwards.

See Wikimedia Foundation Annual Plan/2024-2025/Collaboration/AI call for agenda and sign-up. Johan (WMF) (talk) 14:20, 15 May 2024 (UTC)

Reminder to vote now to ratify the Wikimedia Movement Charter

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Dear Wikimedian,

You are receiving this message because you previously voted in the 2021 Movement Charter Drafting Committee (MCDC) election.

This is a reminder that if you have not voted yet on the ratification of the final Wikimedia Movement Charter draft, please do so by July 9, 2024 at 23:59 UTC.

You can read the final text of the Wikimedia Movement Charter in your language. Following that, check on whether you are eligible to vote. If you are eligible, cast your vote on SecurePoll.

On behalf of the Charter Electoral Commission,

RamzyM (WMF) 15:24, 5 July 2024 (UTC)