On Wed, Mar 13, 2019 at 5:25 AM Tim Starling wrote:
>
> Following approval by TechCom and WMF Interim CTO Erika Bjune, I've
> moved the new Gerrit privilege policy page out of my userspace to
>
> https://www.mediawiki.org/wiki/Gerrit/Privilege_policy
>
> This is a merge of two pages: [[Gerrit/+2]]
Following approval by TechCom and WMF Interim CTO Erika Bjune, I've
moved the new Gerrit privilege policy page out of my userspace to
https://www.mediawiki.org/wiki/Gerrit/Privilege_policy
This is a merge of two pages: [[Gerrit/+2]] and [[Gerrit/Project
ownership]], with some additional changes.
What frustrates me the most are
- bugs found by the editor community, that has obvious simple fixes,
which isn't acted upon for several years
- new features that isn't fully tested, and you have to answer in the
community about stuff you rather want to throw out
- new features and changes that are
On Tue, Mar 12, 2019 at 10:29 PM Bartosz Dziewoński wrote:
>
> I get an impression from this thread that the problem is not really the
> size of the backlog, but rather certain individual tasks that sit in
> said backlog rather than being worked on, and which according to John
> are actually major
Hi!
> 1. My impression is that there's agreement that there is a huge backlog.
Obviously, there is a backlog. As for it being "huge", it's subjective,
for someone who has experience with long-running projects, having
thousands of issues in the bug tracker is nothing out of the ordinary.
Does it
Andre, good points, thanks. I think that this ties in with my comments
regarding having a common situational awareness. I don't think that I have
good situational awareness regarding the state of the backlog, the
composition of the backlog, etc. I'm confident that there is a backlog and
that there
I get an impression from this thread that the problem is not really the
size of the backlog, but rather certain individual tasks that sit in
said backlog rather than being worked on, and which according to John
are actually major issues.
It's hard to disagree or agree with this without knowing
On Tue, 2019-03-12 at 20:34 +, Pine W wrote:
>
> 1. My impression is that there's agreement that there is a huge backlog.
Phabricator is public. Anyone can propose and report anything. Hence
the number of ideas, bugs, feature requests is usually higher than the
number of available developers
>
> I think that there's consensus that the backlog is a problem.
>
For whom is the backlog a problem?
On Tue, Mar 12, 2019 at 4:36 PM Pine W wrote:
> I'm going to make a few points that I think will respond to some comments
> that I've read, and I will try to organize some of my previous point
I'm going to make a few points that I think will respond to some comments
that I've read, and I will try to organize some of my previous points so
that they're easier to follow.
1. My impression is that there's agreement that there is a huge backlog.
2. I think that there's consensus that the bac
Small update on this.
Over the past 3 months, I have slowly familiarised myself with the
tiles.wmflabs.org and I have now migrated rendering and serving of these
tiles to a new server. I still need to do some work on the following things:
1: tile expiration
2: puppet deployment
3: log collection/
Hi all,
in my part of the Design team at Wikimedia Foundation, I'd like to
share an upcoming change in typography, that might be of interest for
you:
Improving reading experience on mobile [0] –
As many of our projects are putting textual content first, we are
consistently aiming at best possible
On Sat, 9 Mar 2019 at 11:50, bawolff wrote:
> In regards to wgUseRCPatrol - I suspect (but don't know) that originally
> that was disabled on enwiki as a performance thing. If it was a performance
> concern, that's probably irrelevant at this point.
>
Sadly, no. It was enabled as a new feature t
On Mon, Mar 11, 2019 at 9:48 AM Piotr Miazga wrote:
> I noticed that ManualLogEntry items could have tags only when those
> entries are published to `rc` or `rcandudp`.
Hmm. Yes, it looks like the tags aren't being added in the `udp` case.
Looks like it was broken in
https://gerrit.wikimedia.or
Regardless of definition-related issues, I concur editors' most
shared/fundamental needs deserve being addressed spending some money.
Vito
Il giorno mar 12 mar 2019 alle ore 11:50 John Erling Blad
ha scritto:
> Without the editors there would be no content, and thus no readers,
> and without re
Without the editors there would be no content, and thus no readers,
and without readers there would be no use for the software provided.
So is the actual users subsidizing the software? Definitely yes! The
content is the primary reason why we have readers. The software is
just a tool to provide the
16 matches
Mail list logo