Regarding 'A recent unrelated ticket I made was closed with the "no
resource to waste on that" by a product owner.': I think that civil
messages explaining why a ticket won't be addressed would be helpful, as
would civil messages explaining why tasks are being moved to a "freezer",
instead of move
Hello,
Thank you for this info. I share an interest in the maintainability of code
that may be around for years, long after the people who write it are no
longer involved with Wikimedia.
It sounds like the Code Health Group is effectively an internal special
interest group for Wikimedia people (I
Code Health Newsletter
The Code Health[0] newsletter is a monthly publication provided by the
Code Health Group[1]. The Code Health Group serves as the hub for all
Code Health topics and activities within the movement. If you are
aware or engaged in Code Health activities, we'd love to hear abou
Paladox wrote:
> i am collecting feedback for Gerrit's New UI […]
You might want to check out the CSS tweaks I developed for the old
Gerrit UI. This stylesheet removes a lot of clutter, makes Gerrit
usable on smaller laptop screens, and increases critical click
regions. If the new Gerrit UI looks
For point1, there is now status badges on change screens. On the dashboard
text is highlighted to tell if it's merged/abandoned/wip/private.
For point 2, upstream have implemented that which will be part of 2.16.
For point 3 they changed it on smaller screens so it would take less space (i
think
Hi!
Some tweaks that I found useful to do for myself in new UI (some can be
done custom styles/scripts etc.) and that might be interesting to
implement if possible:
1. Color coding of changes on the dashboard:
- one with +1 gets green
- one with -1/-2 gets red
- one that has merge conflict gets i
Hi, i am collecting feedback for Gerrit's New UI called PolyGerrit. It's
possible to use PolyGerrit on gerrit.wikimedia.org since 2.14. The new UI has
recently been made the default upstream. The Old UI is going away in the next
release after 2.16. Upstream have given PolyGerrit another update t
În mie., 3 oct. 2018 la 19:08, Mathieu Lovato Stumpf Guntz
a scris:
> On the other hand, I discovered in the process that for some other people in
> the community phabricator is perceived as an hostile place, out of what they
> feel as part of "their" community. Actually, to the point that start
I'm not sure it is a so focused issue. A recent unrelated ticket I made was
closed with the "no resource to waste on that" by a product owner.
A first thing is that I want to work on this issue, and would find that useful
to use phabricator to track that task even if no specific resource would
Just one note about "needs-volunteer".
If the staff maintaining an extension don't have time to work on a problem,
they may also not have time to review any changes relating to it.
If you do use this tag, I see this as an indication you are willing to take
time to review any contributions relating
Oct 8 seems to be a particularly bad time to freeze the train given that we
are forking for the MW 1.32 release on Oct 15, and a lot of folks have
last-minute things they want to get into the release (eg deprecations, etc).
--scott
On Thu, Aug 30, 2018 at 10:57 AM Pine W wrote:
> +1 to DJ's qu
Reminder: The switchback is next week.
On Wed, Aug 29, 2018 at 8:28 PM Alexandros Kosiaris
wrote:
>
> Hello everyone,
>
> This is to inform you that there will be a datacenter switchover and
> switchback on the next few weeks. The timeline's are
>
> Services: Tuesday, September 11th 2018 14:30 UTC
Last call! We're starting in just under an hour.
On Tue, Oct 2, 2018 at 11:07 AM, Trey Jones wrote:
> Just a reminder that this is happening tomorrow, about 24 hours from now.
>
> Trey Jones
> Sr. Software Engineer, Search Platform
> Wikimedia Foundation
>
> On Thu, Sep 27, 2018 at 10:42 AM, Tre
Another side effect of closing a ticket with Declined, is that it doesn't
show up in search (because it's closed and closed tickets are omitted by
default). But if the problem or desire for the feature still exists, it is
likely to be reported again by users via a new ticket and other people then
h
My two cents:
I would personally make those type of tickets as "stalled", "stalled"
basically for me means blocked and these type of tasks are blocked on human
resources, some miracles might happen and we might end up having enough
resources to unblock it but until that day it's stalled IMO.
OTOH
15 matches
Mail list logo
