Re: [Wikimedia-l] [Wiki Loves Monuments] Wiki Loves Monuments in Italy largely blocked by WMF fundraising

[Platonides]

Really sad indeed. Specially for a country with such a complicated 
situation as Italy.


Given that they are going to take you banner time, maybe they would be 
possible to be convinced to include a small "WLM ad" in the donation page?
I would expect targetting people that visit the page but doesn't donate, 
or listing "other ways to help" after donation (a more standard one 
about editing could be used, too). It won't have the same impact as a 
banner, but it'd be an interesting approach.


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Fw: important

[Platonides]

Kenneth Cook wrote:

I consider this to be spam, do you?

Ken


Yes, of course. It is a misleading text "Important message, visit xyz" 
with a link to a compromised website that redirects to a page 
impersonating a newspaper in order to get you use a trading program. (at 
your own risk, and according to the TOU you can only use it if you have 
enough financial knowledge and experience).


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] License issue on GPL and CC-by-sa mix up

[Platonides]

> On Sat, Feb 23, 2013 at 11:12 AM, Mathieu Stumpf wrote:
> Unfortunately, this dictionary is under GPL which is a well known free
> license (but a strange choice for a non-software project). So I would
> like to know, can I mix up a GPL content with a CC-by-sa page (in cases
> where such a page already exist), and more generaly can I add GPL
> content into the wiktionary.
No.

> If no, could we approach their community and ask them for a relicensing
> under CC-by-sa, so we could add their great work into our wiktionaries.
> I also send this message to email I found to contact them[2].
Sure, that would be great.


On 23/02/13 11:51, Andre Engels wrote:
> No. What you stumbled upon is a well-known (at least to me) problem of
> share-alike licences: The only thing they are two-way compatible with
> is themselves. Even if one would have a different license with exactly
> the same meaning, it would not be possible to move texts from that
> license to CC-BY-SA (or GPL or whatever) or vice versa.

There are a few cases where sharealike licenses include provisions for
compatible licenses. Sadly, the license owners don't seem too interested
in advacing in that front.

See for instance the list at
http://creativecommons.org/compatiblelicenses ...which is empty.


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Wikimedia Foundation's support of OTRS

[Platonides]

On 21/02/13 07:19, [[w:en:User:Madman]] wrote:
> Does anyone know what the status is of the OTRS project on Labs? Given
> a contact, I'd be happy to do what I can to help; I have some limited
> experience configuring/deploying OTRS (up until the end of the 3.0
> branch last year, nothing with 3.1 or 3.2 unfortunately).
>
> I think opportunities for *volunteer* help have to consciously be
> maximized, especially for volunteers who are or are willing to be
> agents and/or identified to the Foundation. It's not going to get done
> otherwise.
>
> -Madman/ea

I don't see much future in that, sadly. Yes, a puppetization from a
volunteer could help the WMF, however they won't give you access to the
current setup that you would be replicating. And that's a point that has
been barring any volunteer help for years on this topic. Only ops can
work on it, but nobody is assigned to otrs, and they have other tasks.
There's a mixture of technical needs, legal issues and
too-risky-to-touch it.
Then Martin Edenhofer appeared offering to help with it, but there was
delay after dealy: a NDA is needed, then separate machines, later he
needs to provide the ssh key...
And no work is done.


On 21/02/13 07:32, James Alexander wrote:
> Yeah, I have to agree sadly that we need more tech support and this has
> been a thing that has been ongoing for a while. I personally think it
> should remain in the foundation for many reasons (the least of which is
> relatively large legal reasons) but we REALLY need to focus on it, or a
> replacement, more.
> 
> OTRS is the public face of not only the projects but the foundation in
> general and answers an absolutely insane amount of  email every year and
> that has been the case for a while. When I first started applying to work
> at the foundation my big interview ended up being about 8 hours (with a
> liquor break in the middle) explaining to Philippe how I thought OTRS
> needed to be replaced. I thought, and continue to think, that the system
> underserves the job and we would be better served with something else that
> could take much better advantage of modern advancements and clarity in
> purpose.
> 
> Sadly at the time they didn't have the money for me to work on OTRS (and so
> I came to do the fundraiser) and since then I have heard rumors of it's
> upgrade or replacement every single year (multiple times) only to be told
> later that the resources aren't available. I've seen us look at the upgrade
> multiple times, I've heard it be called both new "ceiling wax and cake
> frosting" but not necessarily called a good option. It may be, I don't know
> and we (as usual with outside products) overwork it beyond measure. Even
> the professional OTRS folks when we were talking to them about helping
> upgrade basically said "errr, you have HOW much in the database?" and told
> us to just abandon it and start fresh with their new version. That said
> even their internal OTRS version wasn't upgraded yet last year 
> 
> We need to do something though, it is disappointing to me that it hasn't
> been a bigger priority because I think it should have been and I think it
> should be now. I'm not sure if an OTRS upgrade is the best option... but it
> is probably better then what we have. For a long while I thought we should
> wait and not upgrade so that we can just replace it... but clearly it's
> been too long for that now.
> 
> James

Thanks for your insight, James. It's very interesting.
As you have dealt with it, can you clarify why is the upgrade such a big
problem? Yes, we have tons of emails. So what? Does the upgrade use
O(2^N) operations??
Even if not-too-efficient, I would expect the upgrade to have finished
in three years :)
I don't even know about a test upgrade being performed ever.

I agree that OTRS is kind-of inefficient. We could easily build a
replacement in 1-2 months *keeping the old data*. If OTRS works quite
well on a single server, just imagine what we could do in a multiple
server setup. I find hard that such version would perform worse. Not to
mention the “handy” improvements we could add based on our usage.
But just a newer OTRS version would be an improvement.



___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Throttling (was: Re: Please can someone put 50p in the meter)

[Platonides]

On 15/10/12 16:15, WereSpielChequers wrote:
> https://www.mediawiki.org/wiki/Manual:Edit_throttling is well worth
> reading, especially the warning that "Many users sharing the same IP
> address could kick in throttling". Which seems a pretty clear indication to
> me that this is working at the IP level and looking at all edits by newbies
> and unregistered editors, rather than treating each member of the workshop
> separately. Once you get to each trainee you find that previewing and
> trying to save again will usually solve the problem, but leave you unable
> to replicate the bug.
> 
> So I think we have found our problem! Now lets see how many months it takes
> to fix it.

That's right. The ip limit applies to both anon and newbie users. The
newbie limit applies by action and user, and the ip limit by action and ip.
So if you have many newbies going out through the same ip, they all
aggregate in the same count.


> Presumably established users of some sort are whitelisted through
> this? (...) But other editors have complained that Cat a Lot doesn't
> work for them and mysteriously hangs or fails,

If you are autoconfirmed, newbie and ip limits don't apply to you.



> One obvious workaround is to use multiple IPs in the same workshop. I think
> the cost of Satellite broadband is only a few hundred quid a year per
> subscription. I've already proposed a subscription for the UK as it would
> enable  people to run editing sessions at big public events such as county
> shows, but it would also help counter this bug.
> 
> WSC

When we whitelist an ip for a workshop, we should also be increasing the
throttling limit for that ip.



___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] photography restrictions at the Olympics

[Platonides]

On 24/07/12 12:15, Richard Symonds wrote:
> WMUK have asked, and we live in London; some of us next door to the
> stadium. The answer is a resounding 'no' from all corners, even when we
> speak to the government. We've got a volunteer with very good access to the
> games, but even behind the scenes it's difficult to get photographs.
> 
> The IOC are not here to give things away for free, it seems: something
> which is painfully apparent to those who've seen the ticket prices!
> 
> Richard Symonds, Wikimedia UK

Did you try to get a compromise offering a delayed publication?
ie. You take photographs but do not make them available under a free
license until after X time (you coould use a more restrictive license
such as CC-BY-NC-SA or not to publish it at all during the "embargo").

As I see it, they want that the media reporting the event is all
acreditated, not republishing third-party images (perhaps to get some
quality level, maybe to make it a selling point for accreditations)

However, all those agencies, TVs and newspapers have no use of those
images after the event.  Much less to scrape others coverage. One month
after the event, it will get buried in the archive.
But our article will be left without a free image for 70 years (plus
author lifetime). It would be suboptimal not being able to publish them
right away, but it is very sad not having a photograph of  gold
medal just because IOC sold draconian tickets.


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] photography restrictions at the Olympics

[Platonides]

On 27/07/12 09:46, Nikola Smolenski wrote:
> An excellent list :) I'd like to add: you sneak in the stadium without
> paying the ticket. IOC can do nothing.
> 
> Seriously, if IOC decides to go after someone, don't they first have to
> prove that he bought the ticket? And how can they prove that?

What if someone else bought the ticket and then gifted it to you?



___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Update on IPv6

[Platonides]

On 13/06/12 00:39, Kim Bruning wrote:
> What with XS4ALL (my ISP) now also offering IPv6 out-of-the-box, there's 
> at least one extra IPv6 anon on en.wp. ;-)
> 
> I noticed that my current IPv6 address appears to be assigned
> dynamically by XS4ALL. I can probably get static if I choose it. But the
> dynamic assignment option does alleviate some people's privacy
> concerns, right?

A 'privacy problem' of IPv6 addresses is that they could be tied to your
network card identification number (the MAC), so even if you changed
networks, and got a different ip, the lower bytes would remain constant
indentifying you. Then privacy extensions were developed to avoid that.
I think you should check how much dynamic it by looking not just but
what ranges change. Maybe it's static but your OS is making it look
dynamic on each reboot. Or viceversa, your OS could be leaking your MAC
even though your ISP gives you a dynamic one.


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] [Announcement] James Forrester joins WMF as Technical Product Analyst

[Platonides]

I don't think "welcome" is the appropiate word to say him :)
SO I sum myself to the other people on this thread saying instead:
Congratulations!


___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l