Hello Labs project maintainers,
Today is your last chance to reboot any instances you may be running
that have Ubuntu Precise and have not been rebooted since my
notification last week!
All instances how have a /usr/local/sbin/reboot-if-idmap script
installed which, if run by root or with sudo,
-- Forwarded message --
From: Keegan Peterzell kpeterz...@wikimedia.org
Date: Wed, Apr 22, 2015 at 1:34 AM
Subject: Re: [Foundation-l] Single login - decision 2004
To: Wikimedia Mailing List wikimedi...@lists.wikimedia.org
On Nov 11, 2004, at 03:27:00 UTC , Erik Moeller
On Wed, Apr 22, 2015 at 10:45 AM Ori Livneh o...@wikimedia.org wrote:
This leads to an interesting marketing possibility, and one that I have
seen in action only a few times: the idea that a subsequent release of a
product might be smaller or have fewer features than the previous version,
and
From http://www.artima.com/weblogs/viewpost.jsp?thread=362327 :
That software systems are getting bigger and more pervasive is testament
that we can at times muster the wherewithal to manage the inherent
complexity of constructing large systems. At other times, however, it
simply supports the
Hi!
This leads to an interesting marketing possibility, and one that I have
seen in action only a few times: the idea that a subsequent release of a
product might be smaller or have fewer features than the previous version,
and that this property should be considered a selling point. Perhaps
On 04/22/2015 01:44 PM, Ori Livneh wrote:
That software systems are getting bigger and more pervasive is testament
that we can at times muster the wherewithal to manage the inherent
complexity of constructing large systems. At other times, however, it
simply supports the view that creating
On 04/22/2015 04:41 AM, Tim Starling wrote:
In the next RFC meeting, we will discuss the following RFC:
* Business Layer Architecture on budget
https://www.mediawiki.org/wiki/Requests_for_comment/Business_Layer_Architecture_on_budget
Minutes:
Merely removing features is not deep enough. This is fundamentally at its
origins an architecture challenge, and a development management challenge.
Removing features is rearguard action, not properly conceived engagement
with the problem.
Complexity can be neutral; code size by itself is not
On 15-04-22 05:06 PM, George Herbert wrote:
He does not seem to understand the harm of
complexity, and does not here appear to understand the role that singular
architects and dev leaders and style guides and code standards can have.
I'm pretty sure I disagree with this. Any system will begin
At those sizes, insisting on APIs between component levels/layers/areas
helps keep sanity and order.
Every system's complexity reflects both actual functional requirements, at
whatever level of simplicity was realistic to impose, and evolution of the
required features as the uses were expanded
took us over a decade but oh well, Well Done Mr Pretzel :D
--
Cometstyles
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Awesome, good job guys!
*Stryn*
2015-04-22 9:37 GMT+03:00 Keegan Peterzell kpeterz...@wikimedia.org:
This is now complete [2]. That wasn't too bad.
2.
https://lists.wikimedia.org/pipermail/wikimedia-l/2015-April/077576.html
--
Keegan Peterzell
Community Liaison, Product
Wikimedia
In the next RFC meeting, we will discuss the following RFC:
* Business Layer Architecture on budget
https://www.mediawiki.org/wiki/Requests_for_comment/Business_Layer_Architecture_on_budget
The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net at the following time:
*
13 matches
Mail list logo
