Talk:Wikimedia Foundation website
Active discussions
How can we help you?
About this page
- This page is for discussing wikimediafoundation.org, the official Wikimedia Foundation website. If you have questions or problems related to Wikimedia fundraising or your donation please email donate
wikimedia.org.
- The comments you enter here are publicly viewable, editable, and deletable. If you would prefer to give private feedback about the Foundation website, the Wikimedia Foundation Communications department can be emailed at communicationswikimedia.org.
- Inquiries about a particular Wikimedia project, like a comment about English Wikipedia, are expected to go directly to that wiki. Such comments may simply be removed from this page.
- The comments you enter here are publicly viewable, editable, and deletable. If you would prefer to give private feedback about the Foundation website, the Wikimedia Foundation Communications department can be emailed at communications
- You will not receive a reply by email for any feedback given on this page. Instead, feedback will be dealt with by Wikimedia Foundation staff and contractors or knowledgeable volunteers. Please note some responses below are from volunteer Wikimedians and have no official approval from the Foundation.
- All languages are welcome here, however English inquiries are expected to be replied to more quickly.
Traffic statisticsEdit
Alexa statistics have many flaws, but they are one indicator. I see the global Alexa rank for wikimediafoundation.org now floats around 100k, while it used to be a top 10k domain in USA not so many years ago.
A decline does not surprise me given the website has grown more and more distant from the core of the Wikimedia movement's communication to the world, but I admit I did not expect the traffic to drop by order(s) of magnitude. (Some significant traffic has been moved elsewhere, for instance the most important pages for the Wikimedia wikis' registered and unregistered users are now on foundation.wikimedia.org; but some other sources of traffic like blog.wikimedia.org have been folded in the main domain.) I hope Alexa is wrong but I've not seen any data to support such hopes.
What can we do to stop the decline of the website, and possibly even return it to is former (moderate) glory? After such a long neglect, we should all feel a sense of urgency in improving the situation. Presumably it doesn't help to have accessibility issues, broken HTML, scarce i18n support, less languages, slower pages, poor recognisability, broken incoming links and so on, but I wonder if it takes more than fixing technical regressions. Nemo 13:39, 10 July 2019 (UTC)
- @Nemo bis: When combined with data on the Wikimedia Foundation Governance Wiki there does not appear to be a decline. Additionally, traffic to the site has steadily increased since the 30 July 2019 soft launch (which is when the decrease in traffic from pages on that wiki went into effect). Additionally, the site is performing significantly better than the previous site on many regards such as recruitment, partnership awareness, and donations. We will continue to work to improve the site, as we have with this latest design, as we do with all of our active sites. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:50, 12 July 2019 (UTC)
Typo in font stackEdit
Great job on the new website, it is certainly quite an improvement. I was experimenting with bringing a more OOUI-based look to it and found a typo in font stack: Seogoe UI instead of Segoe UI. Currently most Windows users have wrong fonts because of it. (Reporting this here because it is a pretty small thing to write a Phabricator task about.) stjn[ru] 16:44, 11 July 2019 (UTC)
- @Stjn: Great catch and thank you for the feedback and pointing out this bug. I have gone ahead and submitted a patch to resolve this which should deploy live soon. Thank you! --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:50, 12 July 2019 (UTC)
Staff historyEdit
You know, one of the things that I really just miss now, is history.. It's all slick, but it has simply become impossible to have any sort of idea for instance about which employee joined and/or left when, department changes etc.. I fear with the staff and contractors page fully in the new website, that information on meta will be even less up to date going forward (HR definetly doesn't seem to be keeping it up to date).. This hurts the transparency of the organization that we are supposed to be... —TheDJ (talk • contribs) 20:05, 11 July 2019 (UTC)
- @TheDJ: I agree that we need a better solution for listing the staff which engage with the community. However, we have seen that just because we can use a channel for something, does not necessarily mean we should. Utilizing the organization website for dozens of things was simply not allowing us to do any of them very well. Hopefully we can work to improve department and team document on Meta-Wiki. The audiences asking for this are community leaders and affiliate staff, so housing this information on channels meant for those groups I think makes more sense and hopefully where we can move toward. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:57, 12 July 2019 (UTC)
- "so housing this information on channels meant for those groups"; I respect that, but it was nice if it was actually happening.. I get it, it's hard enough to keep track of the payroll details, revoking people's shell and building access etc... but this is the part that the community is looking at. The public stuff, the transparency, it is important, maybe because of our history more important than anything else in long term stability and sustainability. I get that the general HR employee doesn't understand that, but it's the responsibility of the organization to educate it's employees. —TheDJ (talk • contribs) 09:46, 12 July 2019 (UTC)
- I should note that the HR folks involved very much agree and have indeed been trained on our value of transparency (training on our values is required for all new hires). This is a matter of resources and not desire. I empathize completely with wanting this to be resolved yesterday, and that on the surface solutions may seem simple. However, any task (even simple ones) come at the cost of another task. And as we grow from 150 to 250 to soon 350 - this is not as simple a task as it once was (years ago updates were done monthly - today they are done almost daily) and we long ago passed the size of most organization's online staff listings. But that does not mean we have given up! My personal hope is that you will start to see some progress on this during this fiscal year. That said, I should note that many teams have already begun work on improving their on-wiki documentation and indeed some have been great at it long before there were even discussions around focusing the organization website. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 20:39, 12 July 2019 (UTC)
- @GVarnum-WMF: Okay, we need a way to have a transparent and manageable system for keeping track of staff. We already list various staff groups on all sorts of pages here on Meta which need to be kept up-to-date. It seems like the clear solution is to have a central staff page here on Meta which is structured in a way that allows the various other pages to pull the same lists from that page. I've started work on a template and module for this, which can make it possible for navboxes (both the general departments one and those for individual departments), department/team galleries, and simple lists to all update from the central staff listing. If we get all the styling nice, perhaps we could redirect the WMF site's staff page to here and push all staff updating work onto the one page.
- You mention that the HR folks agree on the value of transparency. I don't suppose there's any chance we could get some data from them? I imagine that they have plenty of records. It would be quite useful if we could get, for example, a historical list/timeline of WMF staff, and maybe also a list of all WMF job descriptions. It doesn't need to be nicely formatted or anything, the data alone would be quite useful. --Yair rand (talk) 04:22, 30 July 2019 (UTC)
- @Yair rand: Thank you for the great work on that template. Regarding HR, I would not conflate the issue of information on existing roles with information on data about hundreds of individuals from the past fifteen years maintained across several different systems over the years. :) It is not an area I can speak to, but I can already imagine a number of complexities that request would bring and they are indeed two very different topics. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 16:56, 1 August 2019 (UTC)
- @GVarnum-WMF: Is the data really spread across several different systems? I was under the impression that Talent & Culture had unified all its HR data into the (unfortunately closed-source) Namely setup years ago. In any case, do you happen to know who would be the best person to contact in order to request the data on those areas? --Yair rand (talk) 16:53, 5 August 2019 (UTC)
- @Yair rand: Again, not the best person to speak to HR questions, but my understanding is that system unification was for existing employees. However, my main point is that data on existing employees and data on past employees are two very different topics and my past comments on documentation on current employees should not be conflated as comment about information on past employees. Since it is a request to the organization, I would suggest using the Answers system. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 19:58, 5 August 2019 (UTC)
- @GVarnum-WMF: Is the data really spread across several different systems? I was under the impression that Talent & Culture had unified all its HR data into the (unfortunately closed-source) Namely setup years ago. In any case, do you happen to know who would be the best person to contact in order to request the data on those areas? --Yair rand (talk) 16:53, 5 August 2019 (UTC)
- @Yair rand: Thank you for the great work on that template. Regarding HR, I would not conflate the issue of information on existing roles with information on data about hundreds of individuals from the past fifteen years maintained across several different systems over the years. :) It is not an area I can speak to, but I can already imagine a number of complexities that request would bring and they are indeed two very different topics. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 16:56, 1 August 2019 (UTC)
- I should note that the HR folks involved very much agree and have indeed been trained on our value of transparency (training on our values is required for all new hires). This is a matter of resources and not desire. I empathize completely with wanting this to be resolved yesterday, and that on the surface solutions may seem simple. However, any task (even simple ones) come at the cost of another task. And as we grow from 150 to 250 to soon 350 - this is not as simple a task as it once was (years ago updates were done monthly - today they are done almost daily) and we long ago passed the size of most organization's online staff listings. But that does not mean we have given up! My personal hope is that you will start to see some progress on this during this fiscal year. That said, I should note that many teams have already begun work on improving their on-wiki documentation and indeed some have been great at it long before there were even discussions around focusing the organization website. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 20:39, 12 July 2019 (UTC)
- "so housing this information on channels meant for those groups"; I respect that, but it was nice if it was actually happening.. I get it, it's hard enough to keep track of the payroll details, revoking people's shell and building access etc... but this is the part that the community is looking at. The public stuff, the transparency, it is important, maybe because of our history more important than anything else in long term stability and sustainability. I get that the general HR employee doesn't understand that, but it's the responsibility of the organization to educate it's employees. —TheDJ (talk • contribs) 09:46, 12 July 2019 (UTC)
- +1 to that, TheDJ! I also miss the possibility to follow each change long after it happened. But we're kinda nerdy you and I, resources are limited, and needs are not. I understand the change, but yeah, also would like Comms and HR to know there are sad unicorns on Earth who used to like that particular solution. Last but not least, why are we that transparent, anyway? Tar Lócesilion (queta) 14:06, 18 July 2019 (UTC)
- I am periodically (about every 6 months) feeding whole WMF website to archive.org since end of last year. Last crawl has happened this month, but the history between the archival is lost. — regards, Revi 07:26, 22 July 2019 (UTC)
AttributionEdit
The website says that it's licensed under CC-BY-SA 3.0, but the pages don't have histories, or any other way to tell who the authors of a page are, afaict. How is one supposed to comply with the license's attribution requirements? --Yair rand (talk) 19:53, 14 August 2019 (UTC)
- @Yair rand: The author is Wikimedia Foundation, which is also how the previous version of the site was generally cited on places like English Wikipedia and how Wikimedia Foundation Governance Wiki is generally cited. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 18:11, 26 August 2019 (UTC)
Translation in other languagesEdit
Hi, how to translate in other languages? I and other volunteers can help translate in Italian. Is there a TranslateWiki page?--Ferdi2005[Mail] 22:17, 13 November 2019 (UTC)
and also please translate in Indonesian because that's my official language --PutriAmalia1991 (talk) 14:19, 19 January 2020 (UTC)
- @Ferdi2005 and PutriAmalia1991: We are very interested in expanding to additional languages! However, we need to have a system in place for long-term support of the language to avoid having outdated content in the future. This has been a problem for us before, and we committed on this project to developing methods to prevent that from occurring again. There are legal complexities which limits us in terms of methods, but we are working with people across the movement on this effort. You can visit the Organization communications translators group page on Meta-Wiki for more information on the project and how to apply to join when additional languages are added. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:56, 30 January 2020 (UTC)
Broken linksEdit
https://wikimediafoundation.org/about/jobs/ links to URIs like https://grnh.se/d5acb5a81 and https://grnh.se/343b413f1 which are 500 Internal Server Error. —Justin (koavf)❤T☮C☺M☯ 23:24, 2 February 2020 (UTC)
- @Koavf: I am sorry you are having problems with these links. They are working okay for me, can you verify that you are still having problems accessing them? Thank you! --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 22:36, 4 February 2020 (UTC)
- @GVarnum-WMF: "500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong." —Justin (koavf)❤T☮C☺M☯ 22:44, 4 February 2020 (UTC)
- Why is this a URI redirect rather than a direct link? —Justin (koavf)❤T☮C☺M☯ 22:45, 4 February 2020 (UTC)
- @Koavf: Those are the links which the platform provides us. I am not sure if that is because the final links could change. However, I know that people outside the organization (colleges, job fairs, etc.) sometimes take and post those links in a way where having a short URL is helpful. I believe it also helps with analytics around the origin of where the job posting info came from, but I could be wrong on that. But in short, I believe it is because the benefits outweigh the potential problems. It is also unlikely to be related to this, as the long URLs would probably not have worked either. My best guess is that they posted it to the website accidentally a tiny bit before the posting went live officially, and you just happened to catch it during that window. It has not happened before to my knowledge, but seems logical to me knowing the systems. I have never personally seen a situation with this platform where the shortlink does not work and the long link does. Can you verify if they are working for you now? If so, I can look into the timeline a bit and see if that is what happened. If they are still not working for you, obviously a different problem. Thank you! --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:18, 5 February 2020 (UTC)
- @GVarnum-WMF: Firefox, https://grnh.se/d5acb5a81: "500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong." Brave, https://grnh.se/d5acb5a81: redirects to https://boards.greenhouse.io/wikimedia/jobs/2034175?gh_src=d5acb5a81 just fine. Firefox, https://boards.greenhouse.io/wikimedia/jobs/2034175?gh_src=d5acb5a81: just fine. This is likely due to the many anti-tracking add-ons I have on Firefox and the fact that Brave is fresh out of the box. —Justin (koavf)❤T☮C☺M☯ 00:24, 5 February 2020 (UTC)
- @Koavf: Interesting! I will let the department who operates the job posting platform and manages that page know about this. This is the first time I have heard anything like this with these links, so need to look into it a bit more. Thank you for letting us know! --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:29, 5 February 2020 (UTC)
- @GVarnum-WMF: And thank you for your cordial response, Gregory. I would very much encourage the WMF to rethink using these sort of redirects, as I find them very suspicious and block them by default. If nothing else, you can use the shortened URIs in the very narrow contexts where they are most useful (e.g. a printed flyer at a job fair) but save the proper locations for the links on the Foundation's site. —Justin (koavf)❤T☮C☺M☯ 03:13, 5 February 2020 (UTC)
- @Koavf: Interesting! I will let the department who operates the job posting platform and manages that page know about this. This is the first time I have heard anything like this with these links, so need to look into it a bit more. Thank you for letting us know! --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:29, 5 February 2020 (UTC)
- @GVarnum-WMF: Firefox, https://grnh.se/d5acb5a81: "500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong." Brave, https://grnh.se/d5acb5a81: redirects to https://boards.greenhouse.io/wikimedia/jobs/2034175?gh_src=d5acb5a81 just fine. Firefox, https://boards.greenhouse.io/wikimedia/jobs/2034175?gh_src=d5acb5a81: just fine. This is likely due to the many anti-tracking add-ons I have on Firefox and the fact that Brave is fresh out of the box. —Justin (koavf)❤T☮C☺M☯ 00:24, 5 February 2020 (UTC)
- @Koavf: Those are the links which the platform provides us. I am not sure if that is because the final links could change. However, I know that people outside the organization (colleges, job fairs, etc.) sometimes take and post those links in a way where having a short URL is helpful. I believe it also helps with analytics around the origin of where the job posting info came from, but I could be wrong on that. But in short, I believe it is because the benefits outweigh the potential problems. It is also unlikely to be related to this, as the long URLs would probably not have worked either. My best guess is that they posted it to the website accidentally a tiny bit before the posting went live officially, and you just happened to catch it during that window. It has not happened before to my knowledge, but seems logical to me knowing the systems. I have never personally seen a situation with this platform where the shortlink does not work and the long link does. Can you verify if they are working for you now? If so, I can look into the timeline a bit and see if that is what happened. If they are still not working for you, obviously a different problem. Thank you! --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:18, 5 February 2020 (UTC)
- Why is this a URI redirect rather than a direct link? —Justin (koavf)❤T☮C☺M☯ 22:45, 4 February 2020 (UTC)
- @GVarnum-WMF: "500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong." —Justin (koavf)❤T☮C☺M☯ 22:44, 4 February 2020 (UTC)