Clear sailing ahead.
Clear sailing ahead.
Clear sailing ahead.
Sep 17 2014, 6:19 PM (365 w, 5 d)
Busy Busy until Sep 27.
I am not a Product Manager.
So far I vaguely interpreted the workboard columns as a linear "moment in time" indicator and naively planning to use the Priority value to express what's more urgent per column. But I do not have strong opinions on this (apart from avoiding to mix
progress and category style column concepts).
For the records, we have a brand new "In Progress" task status since T288956
, so I would try to avoid duplicating via a column.
Assuming that "breaking very soon" means this becomes a higher priority.
: Thanks for reporting this. For future reference, please use the bug report form (linked from the top of the task creation page) to create a bug report, so your bug report includes all needed information.
: There is a server side where things are hosted. There is also a client side where things are shown in your web browser. These are two different things.
All subtasks are resolved, can this be closed?
Thanks for the update!
As I understand the text in the box above this feature does not cause big problems.
No. The task description above says "severely degrades performance" and "cache fragmentation".
Hah! Thanks for the clarification and correction! Reopening.
For example, this makes no sense, but tagging and moving creates notification noise:
: I wrote "All this information is already expressed via task status, or the "Feature" task type, so I don't understand why there are also columns for this." You did not reply to this, I'm afraid it's still unclear why this user project exists, and which actual (!) and real (!) problem it solves.
Does the same problem happen with a way shorter list of pages (for example, 2 pages)?
: Thanks a lot for your interest! If you need specific access permissions to something (what exactly?) for a specific reason (which one?), then please elaborate. I'm going to decline this ticket for the time being, as it's currently unclear why this is needed. Also see https://wikitech.wikimedia.org/wiki/Volunteer_NDA
for more information. Thanks for your understanding!
"I was not personally asked for my opinion" for software changes does not scale with millions of users. :) What you describe is exactly what Tech News has been for for many years now. If you care about changes which have a larger user impact and would like to join conversations earlier, then please follow Tech News. Thanks for your understanding.
having to install just another Google app on my private phone
: Do you work on fixing this task? If not, then why did you set "In Progress" status?
(Would be cool if people could collect a few things (or tasks!) to mention until then. I have an initial but quite incomplete list so far only.)
Reality bites. Going to punt to end of September.
Thanks for the clarification!
Request access to the LDAP-wmf group through Phabricator
Hmm, this makes me wonder if the "Purpose" field in the SRE task template should be rephrased, and/or the underlying reason why this item is in onboarding docs...
Doesn't this have the exact same problem, but just on a different task?
Hi and welcome @ERayfield
! None of Gerrit, Phabricator or IRC usage in itself require being a member of an LDAP group. Thus I'm closing this ticket. If there are more specific or different purposes, then please correct the task description by clicking Edit Task
, plus set the status of this Phab task back to "Open". Thanks a lot!
: Hi, I don't see a bug here, and I don't see what makes you think that this has something to do with the human language the text is written in.
Does this problem still happen if you remove that line separator \u2028
character from your input, plus if you replace all \xa0
with "normal" whitespaces?
: Statuses are global across all and any projects; I am very reluctant to add dropdown clutter for a single codebase (plus its extensions) only :)
librsvg repo haas been disabled
: If noone can reproduce an error at all anymore, is there a reason to keep its ticket open?
, thanks for taking the time to report this!
This idea makes a lot of sense and I've also wondered a bunch of times, between random after 1.xx free-text suffixes in task titles, potential project tags or columns, or a potential dedicated task specifically about cutting a branch for the next version and making lots of other tasks depend on it. :-/
: See the task title - this task is about 1.38. For 1.37, see T279842
Send API request in enwiki: