Thanks Nuria. Let me know when you're ready for review.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 18 2017
Apr 1 2017
Hey, sorry I think I missed that date. I'm working on it now, but running a little slow due to the conference. What if we send to them end of next week? I can send to you earlier.
Mar 26 2017
A specific story from 2016 would make a good introductory hook.
Mar 24 2017
Looking forward to it!
Feb 28 2017
What about moving this to 2017? I like t-shirts, but I think it will be more useful to think about this for the upcoming year.
We chatted about the results, but we haven't yet turned it into a list of TODOs.
The results of the meeting are now up at Commons:Wiki Loves Monuments International Team meeting 2017.
Feb 24 2017
I recommend the GPLv3. If you have a preference for Apache 2.0, please shoot me an email.
Feb 22 2017
In T94239#3047494, @greg wrote:In T94239#3047419, @Slaporte wrote:@mmodell: Which of these contributions were made by Wikimedia Foundation staff as part of their work? We can help reach out to people to get their agreement if you need help.
the inverse is: Paladox, Sebastien, Alex Monk. Everyone else is/was staff when contributing to scap.
@mmodell: Which of these contributions were made by Wikimedia Foundation staff as part of their work? We can help reach out to people to get their agreement if you need help.
Jan 24 2017
In T154912#2966341, @Nuria wrote:I think we are getting side tracked here. The user agents on api are of a different nature than browser UAs and there is no point on parsing/agreggating those with ua-parser which is made for UAs that follow the usual "browser protocol". The point of this ticket is not to decide whether UAs "in general" are identifying (they are, and that is well stablished) but rather whether APIs UAs have any expectation of privacy.
It is a fundamentally different question as in the UA policy (https://meta.wikimedia.org/wiki/User-Agent_policy) we explicitly ask users to include an e-mail or similar with their request to api so we can identify them. Then, it really seems that data has no expectation of privacy just like @Tgr pointed out early on.
Jan 16 2017
Thanks!
Jan 9 2017
We clarified the tile usage policy in the Maps Terms of Use:
If the user-agent data is non-public and may be used to identify individual users, then it should be kept private under the Privacy Policy. It may be possible to aggregate some user-agent data to the point that it is no longer identifiable, but it would need to be reviewed before its published.
Jan 5 2017
In T111224#2891395, @Pnorman wrote:Hi folks, I'd like to ask some clarifications about the current wikimedia maps licensing. Is it allowed to access the tile map server from a commercial application? Thanks.
My entirely unofficial interpretation is that there is no restriction against use in a commercial application provided that it complies with the requirements of "Using maps in third-party services". This does not mean it is a good idea to base an application on it, commercial or otherwise.
We reserve the right to discontinue or change our service, block or limit certain users or applications, or take other measures in cases at our sole discretion at any time without notice
If you build a business or software around using the maps server, it could go away if your use causes a problem for WMF needs. You should also not hard-code the TMS URL into your app.
Dec 23 2016
Rescinding an agreement is little more complicated than just removing a signature from the terms. Termination may depend on the text of the agreement itself (eg, even if you want to cancel a confidentiality agreement, you still need to respect the confidentiality around private data you accessed). It may be misleading to people if they can "delete" their signature but the agreement isn't really cancelled.
Dec 7 2016
This looks good to me.
Dec 6 2016
Nov 18 2016
Nov 17 2016
Looks up to me now -- I think @chasemp's restart worked?
Nov 10 2016
Nov 1 2016
Fixed and deployed!
Oct 21 2016
Oct 15 2016
Oct 11 2016
We've deployed a fix this morning.
Change ready -- we'll deploy within the next day.
Oct 9 2016
Oct 5 2016
Confirmed, Montage supports PNG and TIFF.
Here you go, you can get the round config as a juror or admin. I also added a sketch of the process for editing the config for rounds.
Sep 30 2016
Sep 24 2016
In T76158#2663787, @Legoktm wrote:In T76158#2663507, @Slaporte wrote:Stephen, this doesn't really help me because I'm still waiting for a response from you or another legal team member about a different software/copyright related matter since August 8th (and resent on September 6th). If email is the recommended communication medium, how long should I expect to wait to get a response about AGPL software?
Sep 23 2016
We can put together some short guidance so it's not only "behind closed doors", but in the meantime you can get advice if you need it for a specific situation via email. We have the checklist that Luis mentioned above for internal use.
Sep 20 2016
That's right, my wikitech username is Slaporte
Sep 7 2016
I'd be happy to discuss. Want to set up time?
Sep 2 2016
Hi all,
Aug 29 2016
Aug 26 2016
In T141576#2587155, @Tazerdadog wrote:Can we get an update on this? It's been 2 weeks, Is WMF Legal still working on a statement?
Aug 18 2016
Aug 3 2016
Having cross-project stats would be helpful for our work as well, such as evidence for defending Wikimedia trademarks in various countries. Follow up with me via email if you need any more detail.
Aug 1 2016
Jul 30 2016
In T141576#2507883, @Alsee wrote:I don't think anyone believed it was *illegal* to store sever-side drafts. There are strong concerns that it's a very bad idea and extremely undesirable.
I'm working with the team on a more detailed response to these concerns, but I wanted to quickly clarify the legal position. As Luis stated in T39992#947108 , there is no legal prohibition on storing server-side private drafts.
Jul 28 2016
I'll follow up with you by email with some specific questions about your project here. Generally, we can either choose to include the copyright info and other notices in the file headers or in a NOTICE file, but we don't have a strict policy on this for now.
You can add the "Wikimedia Foundation" as the copyright holder if it was only built by Wikimedia staff so far.
Jul 16 2016
Jul 4 2016
GPLv3 is acceptable for a MediaWiki extension.
Jun 14 2016
Jun 8 2016
Excellent, thank you!
WordPress tells me that they have resolved the issue. It looks fixed to me, but this is a bit outside my area of expertise. Do you see anything else we need to do to fully address it? Thanks!
Jun 7 2016
I've reported this to wordpress, and I'll update here as they resolve it.
Jun 1 2016
May 29 2016
May 27 2016
Once MapBox is updated on their side, I can post a short page on MediaWiki.org with simple licensing guidelines for maps.wikimedia.org. Would that be helpful?
Staying with a Creative Commons license will be fine for the webpage itself, with only simple styling markup and minimal javascript. I'll speak with @debt about the best license for any related code or libraries.
In T115906#2242143, @Aklapper wrote:In T115906#2076726, @Dereckson wrote:@Slaporte did you take in account in your assesment the public IP address of the signatory will be transferred from WMF to Wikimedia Sverige?
@Slaporte / @ZhouZ: Could you answer the last question if possible? Thanks in advance!
Hi @Dereckson, the quickest way to get legal feedback is by emailing me (slaporte@wikimedia.org) or Zhou Zhou (zzhou@wikimedia.org) for internal questions. Community requests can go to legal@wikimedia.org, and they will get sent to the appropriate attorney quickly too.
May 24 2016
In T134651#2324058, @Ladsgroup wrote:One thing is that I'm a contractor working for WMDE and we have this "(If you are staff or contractor for Wikimedia Germany, please check with WMF-legal if this step is necessary.)". So is it necessary then?
Wes Moran (@Wwes) can approve.
May 7 2016
I like @JAllemandou's approach. Excluding IPs with a completely unrealistic amount of human traffic is probably simple enough. One way to validate this is to compare the results to human filtered list in the English Wikipedia Top 25 report. It uses the percentage of mobile views to detect and remove artificial traffic:
May 5 2016
It won't work to move from WordPress unless there is a system that will allow us to create/edit pages without editing HTML. I'm not necessarily attached to the other features in WordPress, but a replacement would need to be similarly easy to update and maintain.
Apr 27 2016
Apr 21 2016
In T132104#2215041, @Dzahn wrote:@Slaporte I am able to help with setting up a simple static site on our servers.
Apr 17 2016
Apr 15 2016
Thanks. I poked around, but couldn't find instructions for that anywhere.
Apr 11 2016
I'm very interested in getting it hosted internally, converted to a simple static site, or having it proxied internally. Who's able to help?
Apr 8 2016
I agree with @Quiddity, reusing the existing edit summary box is nice and simple, and users are already doing it for programs like #artandfeminism (for example).
Apr 5 2016
Mar 31 2016
Mar 25 2016
In T118463#2151224, @Amit_gkp wrote:
In T118463#2148805, @Amit_gkp wrote:Hi @Slaporte I would like to work on this project. Can you help me how to get started?
Mar 24 2016
In T130790#2148713, @Dzahn wrote:Hi @Slaporte could you approve this request?
Mar 16 2016
@Paladox, you can report trademark abuse here, and we'll investigate: https://meta.wikimedia.org/wiki/Special:Contact/licenseabuse
Mar 7 2016
From what I can see, the data from Feb. 23-29 looks fixed now. Thank you!
Mar 5 2016
Mar 1 2016
There is no issue under the Privacy Policy with deploying the extension.
Feb 17 2016
In T124716#2036647, @BGerstle-WMF wrote:
Feb 16 2016
@mmodell, yes, please disable her phabricator account.
Feb 13 2016
My vote:
Feb 11 2016
I'd recommend using this text, consistent with the mobile web:
Feb 10 2016
@Marshallsumter, we'll take a look and get back to you shortly.
Feb 8 2016
I've reached out to the style author, and I'll ping them again and let you know what I find. Thanks!