On Thu, Feb 13, 2014 at 1:15 AM, Tomasz W. Kozlowski
wrote:
> Hi!
> In a shameless copy of Sumana's August 2012 idea, I'd like to send public
> thanks to some people who have helped me get some things done in the past
> few weeks/days:
I am new here, and I am already in love with this community.
Le 21/02/2014 01:25, Luis Villa a écrit :
>> Can a trademark owner sue the registrar directly? After all it sold a
>> > product (the domain) using your trademark.
>> >
> Remember that "wiki" is not a WMF trademark :) But presumably if someone
> registered something like pedia.wiki we'd have a varie
Thanks Matt! I've been looking forward to more public communication on this
work!
(Per
https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-02-21the
meeting is in #wikimedia-office and not #wikimedia-meetbot .)
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundatio
Gabriel and I have posted about the current work, prototype
implementations, and proposed solution in a new wiki page:
https://www.mediawiki.org/wiki/Requests_for_comment/HTML_templating_library/KnockoutProposal
We hope everyone has a chance to read it and bring their comments /
questions / conce
On Tue, Feb 18, 2014 at 10:10 AM, Faidon Liambotis wrote:
> Last time we were discussing PHP 5.4 it was quite a while ago but I
> remember hearing that we'd need to do some porting work for our
> extensions. Plus, we we re having a debate we were having about Suhosin
> that I don't think ended up
On Thu, Feb 20, 2014 at 4:25 PM, Luis Villa wrote:
> On Thu, Feb 20, 2014 at 4:23 PM, Antoine Musso wrote:
>
> > Le 20/02/2014 22:51, Brion Vibber a écrit :
> > > TLD proliferation is a scam by money-hungry registrars who want people
> to
> > > register (and thus pay) in multiple TLDs to "protec
Hey,
I would like to present Jamie with the official barn-kitten of useful data
brought to a wikitech thread.
https://pbs.twimg.com/media/Bg9lHl8CMAAhXz-.jpg
Congratulations Jamie!
I'd also like to take this opportunity to start an RFC on redesigning all
of MediaWiki's UI, with me doing the work
Being a firm believer in the LTS model, I support David's take on this issue.
Besides, they tend to be tested and reliable and have a longer support window
by default, so it makes sense to support them in turn.
> From: dger...@gmail.com
> Date: Fri, 21 Feb 2014 01:04:39 +
> To: wikitech-l@li
I had some free time today and made some minor improvements to Bingle to
take care of two longstanding, really annoying issues:
https://github.com/awjrichards/bingle/issues/10
https://github.com/awjrichards/bingle/issues/11
(Same issues also reported via BZ:
https://bugzilla.wikimedia.org/show_bug.
On Thu, Feb 20, 2014 at 2:37 PM, Ryan Lane wrote:
> Note that unless you're willing to keep up to date with WMF's relatively
> fast pace of branching, you're going to miss security updates. No matter
> what, if you use git you're going to get security updates slower, since
> they are released int
On 21 February 2014 01:00, Techman224 wrote:
> Let me put this out there so there isn’t confusion. The regular 6 month
> releases of Ubuntu are the stable releases. A LTS release is released every
> two years on the same cycle as regular Ubuntu releases. A LTS release is
> certainly more stabl
Let me put this out there so there isn’t confusion. The regular 6 month
releases of Ubuntu are the stable releases. A LTS release is released every two
years on the same cycle as regular Ubuntu releases. A LTS release is certainly
more stable than regular releases, but not calling regular releas
On Thu, Feb 20, 2014 at 4:23 PM, Antoine Musso wrote:
> Le 20/02/2014 22:51, Brion Vibber a écrit :
> > TLD proliferation is a scam by money-hungry registrars who want people to
> > register (and thus pay) in multiple TLDs to "protect their brands".
> >
> > I recommend we boycott/ignore these var
Le 20/02/2014 22:51, Brion Vibber a écrit :
> TLD proliferation is a scam by money-hungry registrars who want people to
> register (and thus pay) in multiple TLDs to "protect their brands".
>
> I recommend we boycott/ignore these various things and just avoid them, but
> I know we're going to end
On Thu, Feb 20, 2014 at 3:58 PM, James Forrester
wrote:
> On 20 February 2014 15:34, Ryan Lane wrote:
>
> > On Thu, Feb 20, 2014 at 3:22 PM, Trevor Parscal > >wrote:
> >
> > > Is that the rule then, we have to make MediaWiki work on anything
> Ubuntu
> > > still supports?
> > >
> > > Is there a
On 20 February 2014 15:34, Ryan Lane wrote:
> On Thu, Feb 20, 2014 at 3:22 PM, Trevor Parscal >wrote:
>
> > Is that the rule then, we have to make MediaWiki work on anything Ubuntu
> > still supports?
> >
> > Is there a rule?
> >
>
> We should strongly consider ensuring that the latest stable re
On Thu, Feb 20, 2014 at 3:22 PM, Trevor Parscal wrote:
> Is that the rule then, we have to make MediaWiki work on anything Ubuntu
> still supports?
>
> Is there a rule?
>
>
We should strongly consider ensuring that the latest stable releases of
Ubuntu and probably RHEL (or maybe fedora) can run Me
One asks whether the Foundation would've asked for a .wikimedia tld when
ICANN had that application period open (provided we actually could've
afforded funds to pay the huge fees required).
On Thu, Feb 20, 2014 at 2:05 PM, Marc A. Pelletier wrote:
> On 02/20/2014 04:51 PM, Brion Vibber wrote:
>
Maybe not a firm rule, but something worth being aware of. Lots
of people use LTSes, so it'd be nice to not break them without
some upgrade path :)
-Chad
On Thu, Feb 20, 2014 at 3:22 PM, Trevor Parscal wrote:
> Is that the rule then, we have to make MediaWiki work on anything Ubuntu
> still supp
Is that the rule then, we have to make MediaWiki work on anything Ubuntu
still supports?
Is there a rule?
- Trevor
On Thu, Feb 20, 2014 at 12:25 AM, Markus Krötzsch <
mar...@semantic-mediawiki.org> wrote:
> On 20/02/14 05:17, Jamie Thingelstad wrote:
>
>> Regarding PHP 5.3 support, I put toget
On 2014-02-20 2:50 PM, Bartosz Dziewoński wrote:
> On Thu, 20 Feb 2014 23:21:37 +0100, Greg Grossmeier
> wrote:
>
>>
>>> It's worth noting that WMF branches also include temporary hacks to
>>> keep current JS/CSS and cached HTML output compatible (for at least 30
>>> days), while release branches
I've taken the liberty of enabling[1] lower-resolution .ogv video
transcodes, at 360p and 160p in addition to the 480p we already generated.
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=61690
These will be useful for older or slower or mobile machines which need to
use non-native software
> Note that unless you're willing to keep up to date with WMF's relatively
> fast pace of branching, you're going to miss security updates. No matter
> what, if you use git you're going to get security updates slower, since
> they are released into the tarballs first, then merged into master, then
On Thu, 20 Feb 2014 23:21:37 +0100, Greg Grossmeier wrote:
It's worth noting that WMF branches also include temporary hacks to
keep current JS/CSS and cached HTML output compatible (for at least 30
days), while release branches never contain them (and thus require
HTML caches to be purged dur
On 02/15/2014 09:07 PM, Ryan Kaldari wrote:
> Frankly, I think there has been a large degree of intransigence on both
> sides. The free font advocates have refused to identify the fonts that
I still miss an answer to
http://lists.wikimedia.org/pipermail/design/2013-December/001285.html
I don't w
On Thu, Feb 20, 2014 at 1:20 PM, Sumana Harihareswara wrote:
> Reuben Smith of wikiHow asked:
> "We're having a hard time figuring out whether we should be basing our
> wikiHow code off Mediawiki's external releases (such as the latest 1.22.2),
> or off the branches that WMF uses for their intern
> It's worth noting that WMF branches also include temporary hacks to
> keep current JS/CSS and cached HTML output compatible (for at least 30
> days), while release branches never contain them (and thus require
> HTML caches to be purged during the upgrade process).
Isn't that:
>> Feel free to b
On 02/20/2014 01:55 PM, Rob Lanphier wrote:
> On Wed, Feb 19, 2014 at 4:21 PM, Sumana Harihareswara
> mailto:suma...@wikimedia.org>> wrote:
>
> This week, we're mostly discussing the HTML templating and SOA RFCs -
> https://www.mediawiki.org/wiki/Architecture_Summit_2014/HTML_templating
>
On 02/20/2014 04:51 PM, Brion Vibber wrote:
> TLD proliferation is a scam by money-hungry registrars who want people to
> register (and thus pay) in multiple TLDs to "protect their brands".
Well, the ostensible pretext is that .com. is now ridiculously
overloaded with myovercomplicateddomain.com b
On Thu, Feb 20, 2014 at 9:53 PM, Isarra Yos wrote:
> It would require pretty consistent maintenance of their own, but it could be
> worth it.
IOW, you need to hire a Greg Grossmeier :)
-Jeremy
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Wed, Feb 19, 2014 at 4:21 PM, Sumana Harihareswara wrote:
> This week, we're mostly discussing the HTML templating and SOA RFCs -
> https://www.mediawiki.org/wiki/Architecture_Summit_2014/HTML_templatingand
>
> https://www.mediawiki.org/wiki/Requests_for_comment/Services_and_narrow_interfaces
On 20/02/14 21:32, Bartosz Dziewoński wrote:
It's worth noting that WMF branches also include temporary hacks to
keep current JS/CSS and cached HTML output compatible (for at least 30
days), while release branches never contain them (and thus require
HTML caches to be purged during the upgrade
TLD proliferation is a scam by money-hungry registrars who want people to
register (and thus pay) in multiple TLDs to "protect their brands".
I recommend we boycott/ignore these various things and just avoid them, but
I know we're going to end up registering a bunch for the "brand protection"
(rac
It's worth noting that WMF branches also include temporary hacks to keep
current JS/CSS and cached HTML output compatible (for at least 30 days), while
release branches never contain them (and thus require HTML caches to be purged
during the upgrade process).
This usually only affects changes
I got permission from Reuben Smith of wikihow and WMF release manager Greg
Grossmeier to re-post this exchange.
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Reuben Smith of wikiHow asked:
"We're having a hard time figuring out whether we should be basing our
wikiHow co
We've been in discussions with Top Level Design, both to look into
potentially appropriate uses (e.g. URL shorteners) and to prevent
squatting of WMF trademarks.
James points out that now there's .foundation there's some additional
potential for mischief :P. Damn TLDs sprouting like mushrooms ..
On 02/20/2014 10:56 AM, Derric Atzrott wrote:
> I'm not entirely sure what that means for all of us exactly, but I
> suspect that the WMF is going to want to at least register Wikipedia.wiki and
> Wikimedia.wiki once the gTLD is open for registration.
I'm not even sure media.wiki is a good idea, b
On Feb 20, 2014 1:57 PM, "Derric Atzrott"
wrote:
> ICANN just delegated the gTLD .WIKI yesterday. It's being managed by Top
Level
> Design, LLC. I'm not entirely sure what that means for all of us
exactly, but I
> suspect that the WMF is going to want to at least register Wikipedia.wiki
and
> Wi
http://honeycoding.wordpress.com/2014/02/20/mediawiki-vagrant-is-tough-to-be-tamed-in-your-local-machine/
Charul is an OPW intern with Fedora working on infrastructure visualization
(the Datagrepper/Dataviewer project). Charul: thanks for the post! If you
have any improvements for
https://www.med
ICANN just delegated the gTLD .WIKI yesterday. It's being managed by Top Level
Design, LLC. I'm not entirely sure what that means for all of us exactly, but I
suspect that the WMF is going to want to at least register Wikipedia.wiki and
Wikimedia.wiki once the gTLD is open for registration.
Some
On 20/02/14 05:17, Jamie Thingelstad wrote:
Regarding PHP 5.3 support, I put together a quick report in WikiApiary
showing the versions of PHP in use across wikis.
https://wikiapiary.com/wiki/PHP_Versions
In short, 5.3 is the most common PHP version used by a large, large
majority.
Three thing
41 matches
Mail list logo
