Thank you very much for the thorough feedback. I changed the proposal with
your suggestions and answered the questions. Looking forward to hear more
suggestions and improvements on this regard.
Dinu
On Wed, Mar 12, 2014 at 4:59 AM, Sumana Harihareswara wrote:
> Thank you for being interested i
Max Semenik wrote:
>I would like to thank everyone who participated in this effort!
>
>This wasn't an easy decision, however the share of WAP has fallen
>tremendously and we can find better use for engineering resources we
>would have needed to maintain WAP support functional.
RIP, WAP.
It seems
After a lot of analysis, discussions and preparations, today we announce
that WAP/WML support has been removed from MobileFrontend. Our sites
were running HTML only for a couple weeks now, so since we received no
complaints, we pulled the trigger. Final deprectation might take a
couple more weeks,
Brandon Harris wrote:
>Personally, I think talk of "power user skin" versus "reader skin" is
>pointless.
Pointless? Would it help if we used the term "user stories"? :-)
https://www.mediawiki.org/wiki/Special:Search/user_stories
> I think we should be focusing on making the software and system b
On 11 March 2014 16:33, James Forrester wrote:
> On 11 March 2014 16:02, Risker wrote:
>
> > Editors, it seems, chose Monobook 2:1 over Vector as of this time last
> > year, when there were many other skins; that is, they make the conscious
> > choice. (I also think there's something really wonk
I am one of these creatures. I didn’t set a preference when I joined
and just rode through the default changes as it went. Later, I ended up
setting a preference to Vector, but that was after I had played around with
other skins, so I needed a way to get back to the one I liked.
James Forrester wrote:
>This is based on a mis-understanding of
>https://meta.wikimedia.org/wiki/Turning_off_outdated_skins/stats.
>Specifically:
>
>>One limitation of the data is that we could only retrieve users who had
>> actively set a preference for their skin; users who had not done this
>>
On 11 March 2014 16:02, Risker wrote:
> Editors, it seems, chose Monobook 2:1 over Vector as of this time last
> year, when there were many other skins; that is, they make the conscious
> choice. (I also think there's something really wonky about the "power user"
> numbers. There's no way there
On 11 March 2014 17:05, MZMcBride wrote:
> James Forrester wrote:
> >This is based on a mis-understanding of
> >https://meta.wikimedia.org/wiki/Turning_off_outdated_skins/stats.
> >Specifically:
> >
> >>One limitation of the data is that we could only retrieve users who had
> >> actively set a pr
Thank you for being interested in Wikimedia, Wikidata, and open source!
I've asked some questions in
https://www.mediawiki.org/wiki/Talk:Project_Eclipse_:_Wikidata_Outreach_Project#Big_questionsand
as comments in the Google Doc
https://docs.google.com/a/wikimedia.org/document/d/1Vkj8d9q8WiVe2GZ2wkc
Risker, I'm not saying there is not value in paying attention to
Monobook. I'm saying quite the opposite.
I'm saying I _currently_ pay less attention to Monobook as I currently
think of it the same way as Cologne Blue and Modern which I couldn't
care less for.
Take away those 2, it becomes much ea
On 11 March 2014 18:48, Jon Robson wrote:
> + 1 to what Trevor just said.
>
> Isarra, developers make a _decision_ to forget some users exist. This
> is why Wikipedia doesn't support IE5. I am suggesting a decision that
> we forget that users of Cologne blue exist. Although it might seem
> ha
On 11/03/14 22:45, Trevor Parscal wrote:
By making all skins extensions it would also force us to make a few new
APIs which are needed to no longer have skin extensions be second-class
citizens.
This should happen.
- Trevor
Quite so. Think hitting on some of this could be a viable gsoc projec
+ 1 to what Trevor just said.
Isarra, developers make a _decision_ to forget some users exist. This
is why Wikipedia doesn't support IE5. I am suggesting a decision that
we forget that users of Cologne blue exist. Although it might seem
harsh to the 98,541 readers but justified. It's just not
By making all skins extensions it would also force us to make a few new
APIs which are needed to no longer have skin extensions be second-class
citizens.
This should happen.
- Trevor
On Tue, Mar 11, 2014 at 2:38 PM, Isarra Yos wrote:
> On 11/03/14 21:21, Jon Robson wrote:
>
>> If people forge
It's great to see these conflicting ideas!
I agree, this is not simple at all - this is why we have no map
namespace, but there is definitely a need. I'm hoping Zurich can
provide a platform where we can get somewhere close in that direction
and generate some momentum.
The fact we have a BetaFeat
Martijn both of those features are in the beta site and hopefully will
surface soon!! You can get a preview of the history page here -
https://en.m.wikipedia.org/wiki/Special:History/San_Francisco?mobileaction=beta
- let us know what's missing so we can get this up!
On Tue, Mar 11, 2014 at 2:49 P
On Tue, Mar 11, 2014 at 8:14 PM, Jon Robson wrote:
> You can now apply the mobile skin to the desktop site [1]. Wa?!
> To cut a long story short, to help MobileFrontend and VisualEditor
> integrate nicely with one another, we needed the mobile skin to be
> registered as a valid skin. We've pr
On 11/03/14 21:21, Jon Robson wrote:
If people forget they exist I would say that equates to no one cares
about them and no one maintains them.
If this is true, we are doing a disservice to our users by providing
these skins to our users.
Developers forget some users exist. They forget use case
Am 10.03.2014 17:01 schrieb "Manuel Schneider" <
manuel.schnei...@wikimedia.ch>:
>
> Am 10.03.2014 16:54, schrieb Chris Steipp:
> >> 1) catch the click on the "Login" link to show a banner first to ask
for
> >> the users consent, on acceptance forward the user to the login page
> >>
> >> 2) modify
If people forget they exist I would say that equates to no one cares
about them and no one maintains them.
If this is true, we are doing a disservice to our users by providing
these skins to our users.
On Tue, Mar 11, 2014 at 1:20 PM, Isarra Yos wrote:
> On 11/03/14 20:16, James Forrester wrote
Yesterday we were so busy with the beginning of GSoC and FOSS OPW
round 8 that I didn't have time to post about the end of OPW round 7:
https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_7
Quite silently, the six teams participating in this round have set a
new benchmark for fut
On 11/03/14 20:16, James Forrester wrote:
On 11 March 2014 13:10, Isarra Yos wrote:
On 11/03/14 17:26, Trevor Parscal wrote:
It might be easier to revamp the skin system if there were fewer skins to
port.
- Trevor
But that completely ignores the primary users of non-Vector skins
Sure,
On 11 March 2014 13:17, Isarra Yos wrote:
> On 11/03/14 19:21, Jon Robson wrote:
>
>> It might be easier to revamp the skin system if there were fewer skins to
>>> port.
>>>
>> Touché.
>>
>> So.. so 2 questions
>> 1) would anyone have any objections to moving it out of core and into
>> its own ex
On 11/03/14 19:21, Jon Robson wrote:
It might be easier to revamp the skin system if there were fewer skins to
port.
Touché.
So.. so 2 questions
1) would anyone have any objections to moving it out of core and into
its own extension?
2) would anyone have any objections for turning it off on Wik
On 11 March 2014 13:10, Isarra Yos wrote:
> On 11/03/14 17:26, Trevor Parscal wrote:
>
>> It might be easier to revamp the skin system if there were fewer skins to
>> port.
>>
>> - Trevor
>>
>
> But that completely ignores the primary users of non-Vector skins
Sure, because they aren't in Medi
On 11/03/14 17:26, Trevor Parscal wrote:
It might be easier to revamp the skin system if there were fewer skins to
port.
- Trevor
But that completely ignores the primary users of non-Vector skins -
third party users who have developed their own skins. Every time the
skinning systems changes,
On Mar 11, 2014 3:36 PM, "Risker" wrote:
> differentiating which
> nearly-identical wikis one is working on, particularly if one or more of
> the wikis involved are non-public ones.
Do you have specific requests for how to differentiate them?
Either for a whole wiki (could be in main common.css)
On Tue, Mar 11, 2014 at 12:54 PM, Sumana Harihareswara
wrote:
> Hi, Maduranga Siriwardena! Thank you for being interested in Wikimedia and
> in open source software.
>
> First, a quick tip: it's better to include a subject line when you email
> people, especially on mailing lists. Please see
> htt
I don't think anyone is suggesting removing or even moving Monobook. I
think we are more talking about assigning effort more proportionally to
preference of users. Cologne Blue is not the clear favorite of any group of
users that we know of.
- Trevor
On Tue, Mar 11, 2014 at 12:36 PM, Risker wro
On 11 March 2014 15:21, Jon Robson wrote:
> > It might be easier to revamp the skin system if there were fewer skins to
> > port.
>
> Touché.
>
> So.. so 2 questions
> 1) would anyone have any objections to moving it out of core and into
> its own extension?
> 2) would anyone have any objections
I support moving it to an extension and enabling it on deployed sites as to
avoid an disruption in service for the users of the skin.
- Trevor
On Tue, Mar 11, 2014 at 12:21 PM, Jon Robson wrote:
> > It might be easier to revamp the skin system if there were fewer skins to
> > port.
>
> Touché.
This is really awesome, nice work Jon, Kaldari, and everyone else
involved!!!
On Tue, Mar 11, 2014 at 12:14 PM, Jon Robson wrote:
> You can now apply the mobile skin to the desktop site [1]. Wa?!
> To cut a long story short, to help MobileFrontend and VisualEditor
> integrate nicely with on
RE: https://bugzilla.wikimedia.org/show_bug.cgi?id=62233
There's a problem is somewhere in the core which causes warnings.
Can anyone confirm who runs a recent core version younger than 2014-02-28 ?
Logfiles in my recently upgraded (git pull) installations are filling up
with warnings
This would be a great place to get to. Even if we did this but every
other commit or every 5 commits this would be a step in the right
direction!
On Tue, Mar 11, 2014 at 2:44 AM, Martijn Hoekstra
wrote:
> On Mar 10, 2014 4:19 PM, "Greg Grossmeier" wrote:
>>
>>
>> > If the test infrastructure c
> It might be easier to revamp the skin system if there were fewer skins to
> port.
Touché.
So.. so 2 questions
1) would anyone have any objections to moving it out of core and into
its own extension?
2) would anyone have any objections for turning it off on Wikimedia wikis
FWIW, having a single
You can now apply the mobile skin to the desktop site [1]. Wa?!
To cut a long story short, to help MobileFrontend and VisualEditor
integrate nicely with one another, we needed the mobile skin to be
registered as a valid skin. We've previously avoided this as we didn't
want to surface this in th
On Tue, Mar 11, 2014 at 12:34 AM, Gergo Tisza wrote:
> On Mon, Mar 10, 2014 at 8:46 AM, Manuel Schneider <
> manuel.schnei...@wikimedia.ch> wrote:
>
> > The issue at hand is: EU privacy policy 95/46/EG[1] allows usage of
> > cookies only if
> > * the user has been informed beforehand in detail
>
Hi, Maduranga Siriwardena! Thank you for being interested in Wikimedia and
in open source software.
First, a quick tip: it's better to include a subject line when you email
people, especially on mailing lists. Please see
http://en.flossmanuals.net/GSoCStudentGuide/ch014_communication-best-practice
Hello, Devender, and thank you for being interested in open source and in
Wikimedia!
Are you proposing to do this for *Wikipedia* specifically, or just as a
MediaWiki extension that any MediaWiki installation might choose to
install? If you want to do this to Wikipedia, then I think you haven't
t
Note that the situation is different for Wikimedia projects than for
Mediawiki. Whether or not WMF LCA thinks it is necessary for the
Wikimedia-hosted services, it may still be a useful feature to build for
users of Mediawiki who believe that the rule should apply to them. So don't
let "WMF doesn't
Am 11.03.2014 12:57, schrieb Federico Leva (Nemo):
This conversation would IMHO be more appropriate on mediawiki-l
because it affects mainly third parties who care about the higher
privacy standards of EU, but thanks for starting it.
I think, a bugzilla should be filed for this cookie issue (b
Hi,
I am Dinu Kumarasiri an undergraduate at Department of Computer Science and
Engineering, University of Moratuwa. I am Interested in Wikidata Outreach
project for the FOSS outreach Program for Women.
Following is the link to the proposal of my outreach campaign.
https://docs.google.com/documen
It might be easier to revamp the skin system if there were fewer skins to
port.
- Trevor
On Mon, Mar 10, 2014 at 6:48 PM, MZMcBride wrote:
> Tomasz Finc wrote:
> > On Mon, Mar 10, 2014 at 2:10 PM, Jon Robson wrote:
> >> Why is Cologne Blue still in core?
> >
> >A good time to revist
> >
> >ht
On 03/11/2014 12:37 PM, Mark Bergsma wrote:
> Chase comes to us from DeviantArt
Welcome, Chase.
... is there anyone /left/ at DeviantArt? :-)
-- Marc
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/list
I'm very pleased to announce that Chase Pettet is joining the Wikimedia
Foundation as Operations Engineer. Chase comes to us from DeviantArt, where he
was responsible for their general server management infrastructure, monitoring
and networking, as well as supporting the development team(s). Wit
Hi, this IRC meeting is starting in 15 minutes.
On Monday, March 10, 2014, Quim Gil wrote:
> On 03/10/2014 02:37 PM, Quim Gil wrote:
> > Hi,
> >
> > Starting today, candidates of Google Summer of Code and FOSS Outreach
> > for Women can submit their proposals officially. See
> >
> > https://www.
This conversation would IMHO be more appropriate on mediawiki-l because
it affects mainly third parties who care about the higher privacy
standards of EU, but thanks for starting it.
On asking WMF legals, no worries, they were already pointed to the
possibility of an issue with 2009/136/EC / "
On 03/10/2014 04:46 PM, Manuel Schneider wrote:
The issue at hand is: EU privacy policy 95/46/EG[1] allows usage of
cookies only if
[...]
The Austrian Communication Law (§ 96 Abs. 3 TKG) defines a penalty of
37.000 EUR.
Are there any known cases, in Austria or elsewhere,
where a violation of th
On Mar 10, 2014 4:19 PM, "Greg Grossmeier" wrote:
>
>
> > If the test infrastructure can't handle running every test on every
commit
> > (why can't they by the way, and could that be remedied?) Would it be
> > possible and desireable to make sure a more elaborate test suite with
all
> > available
I don’t know much about the matter, but I thought this policy was mostly about
limiting tracking cookies.
Let’s first ask legal@ if anything should be done at all, at this point.
On 11 Mar 2014, at 08:34, Gergo Tisza wrote:
> On Mon, Mar 10, 2014 at 8:46 AM, Manuel Schneider <
> manuel.schnei..
On Mon, Mar 10, 2014 at 10:04 PM, Jon Robson wrote:
> My vision of how this might work is we have an automated tool that
> visits a list of given pages on various browsers, take screenshots of
> how they look and then compares the images with the last known state.
> The tool checks how similar th
On Mon, Mar 10, 2014 at 8:46 AM, Manuel Schneider <
manuel.schnei...@wikimedia.ch> wrote:
> The issue at hand is: EU privacy policy 95/46/EG[1] allows usage of
> cookies only if
> * the user has been informed beforehand in detail
> * the user has accepted the cookie
> * this acceptance was given f
Hello, Everyone,
Follows is a link to my project proposal for the Summer 2014 FOSS Outreach
Program for Women. I would like to create a Hacker's Map to make it easier
for new contributors/hackers to get started on Wikidata and then to use the
Map as part of an outreach campaign. Feedback is more t
54 matches
Mail list logo
