- User Since
- May 6 2015, 12:00 AM (422 w, 2 d)
- LDAP User
- MediaWiki User
- Zhousquared [ Global Accounts ]
Sep 22 2017
I can confirm Stephen is taking over this.
Sep 15 2017
Yes, please revoke the old key - sorry I forgot to tell you earlier.
Sep 14 2017
Thanks also Legal might also want to create a separate Legal space in addition to the one with Analytics folks
Aug 28 2017
Aug 24 2017
Good point. It would be nice to have it jump immediately to a localized version (especially if this link ends up in the article footer) but not necessary. The Disclaimer page has a pretty obvious language selector in the mobile view so the user can easily change it to another language variant.
Having a link to the General Disclaimer somewhere in the app, perhaps in the article footer or in the setting page would be a good idea.
Aug 23 2017
Aug 4 2017
HI all, if there are no further objections, are we all ready to move forward with the new proposed language?
Aug 1 2017
The API specification is available under the Apache 2.0 license.
Hi @mobrovac, without going into the legal weeds, often the license that works best for text content (or software) may not be the most appropriate license for data. For example, data for projects in the Wikimedia movement are usually available under a CC0 license (see the Wikidata license and our open access policy) even if text content for projects like Wikipedia is under a CC BY SA 3.0 license (and images on Wikimedia Commons may also have their own specific license).
Here's the language we can provide at the specific endpoints on the https://wikimedia.org/api/rest_v1/ page. This is an example for the GET /metrics/pageviews endpoint but we should add similar language in the "Implementation Notes" sub-section for all other endpoints in the Pageviews data, Unique devices data, Legacy metrics, and Pagecounts data (legacy) sections on the https://wikimedia.org/api/rest_v1/ page API documentation page.
I will provide some proposed language we can add.
Jul 21 2017
Jul 19 2017
I can confirm zhousquared belongs to me.
Speaking for legal, we clear this change as well.
Jul 13 2017
Jun 5 2017
May 22 2017
May 8 2017
Sorry for the delay - Legal still is reviewing this (the Fedora situation is good news). We hope to have a response by the end of the week.
Apr 11 2017
Hi everyone! Wikimedia Legal has been analyzing this issue and we can provide you with an update once that it is done.
Apr 10 2017
Let's start with the basics and add links to our policies on the API help pages.
Mar 27 2017
Mar 22 2017
Mar 17 2017
Feb 8 2017
Feb 7 2017
After an investigation, I believe legally this is a free file format as required under Commons policy.
Jan 24 2017
Just as an updated reminder to this task.
Dec 12 2016
Thanks for flagging @Volker_E and helping fix this issue!
Dec 9 2016
Dec 6 2016
Hi, we have done some research on this matter and it appears PLY is an open file format. Please contact me about other considerations if you are interested in having commons support this file format.
Hi, we have done some research on this matter and it appears OBJ is an open file format. Please contact me about other considerations if you are interested in having commons support this file format.
Nov 29 2016
Nov 23 2016
Sure - let sync up.
Thanks @eliza. Can you work with @Aklapper to get the necessary permissions when you are ready to roll this out next Jan?
@bbogaert, @eliza, I understand you can help implement task as part of the on-boarding process starting in Jan. 2017. That is receive permissions to add members to WMF-NDA and use this permission to add new employees to the WMF-NDA group on request from their managers in the on-boarding form.
Nov 21 2016
Nov 16 2016
Sorry can either @jeblad or @ArthurPSmith clarify what is the concern here?
Nov 15 2016
Oct 19 2016
My understanding is there is only one notification preference (@JMinor can confirm). Also I think people might be more concerned about notifications being based on a personalized profile rather than the preference itself.
Oct 18 2016
I'd love OIT to create the Phab account of new hires (which very likely requires being logged in on mw.org with the new hire's account) and after that OIT to add the new hire's Phab account to the WMF-NDA Phabricator project (which would require members of OIT to receive permissions to edit members in WMF-NDA Phabricator project and I'm happy to hand out these permissions).
Oct 14 2016
so just to circle back on this task and confirm - if OIT can create phabricator accounts for new hires using their Meta login, would you then be able to confirm NDA access as needed and this issue would be resolved?
Oct 12 2016
I think perhaps something like this would provide even more information to the user (assuming this is not too verbose):
Oct 6 2016
I am not sure what is this recommendation system. I am only tracking the task at this point.
Sep 23 2016
Sep 22 2016
Thanks - it works.
Sep 20 2016
Hi @Dzahn, just to confirm my Wikitech username is actually this: ZZhou (WMF)
Sep 16 2016
Sep 14 2016
@RobLa-WMF this is done - see https://www.mediawiki.org/wiki/Requests_for_comment/Survey_Cookies/Local_Storage_on_Wikimedia#Proposal.
Sep 13 2016
@RobLa-WMF, yes - actually both https://meta.wikimedia.org/wiki/Privacy_policy/FAQ#Can_you_give_me_some_examples_of_types_of_cookies_and_how_you_use_local_storage.3F
and https://wikimediafoundation.org/wiki/Cookie_statement contain the relevant (and same) cookie tables. This is the type of information we want to keep up to date and will be helped by this project.
Sep 12 2016
Thanks @RobLa-WMF for volunteering to shepherd this.
Sep 9 2016
This looks good. Thanks!
Sep 2 2016
Sep 1 2016
Aug 31 2016
Can we actually just place this on-hold for now? Still touching base internally to see if we can get resources - will update.
Aug 29 2016
Aug 25 2016
Hi @Aklapper I have talked to both OIT and HR about this process. Their understanding is the process will like below
I see - I have done more investigation into this process. Will update the other task then and close this one.
Aug 24 2016
So to recap what we want to do:
Aug 22 2016
Aug 18 2016
Aug 17 2016
Aug 16 2016
The GPL requires some sort of copyright notice for the source code. But if we want to, in general it should not be a problem to put the credits in a centralized CREDITS file instead, see T139300 and point to that file from each source file.
Aug 11 2016
What about a task / email by their manager? It should be simple to verify the manager's username/email.
Aug 10 2016
Ok I see - I was mistaken then.
Aug 9 2016
@ZhouZ: What type of account is a "@wikimedia.org account"? Also, Phabricator does not expose the email addresses of user accounts.
Aug 8 2016