[22:30:56] nimish_g, howief; sorry, but how exactly is there a deadline for bug reports? :-) [22:31:30] we'd like to get as many in as possible by the deadline [22:31:36] the goal is to identify any blockers [22:32:15] also, we hope to motivate people by giving them a date, rather than it being some ambiguous point in the future [22:32:15] we want to switch over on Sept 1, and find out if there's anything stopping us from doing so well before that. but, yeah, please keep sending bugs in after that date =) [22:33:01] yup [22:33:36] also translations for the messages and so forth. [22:35:18] *kibble nods. [22:35:23] We might want to phrase it better. [22:35:52] if someone can come up with better phrasing, that's great [22:36:03] let's just make sure we economize on words [22:36:23] *AlexZ_ volunteers kibble to do that. [22:36:37] jorm, yeah, I know all about translations. :-) [22:42:18] O RLY [22:43:55] what is considered as blocker? [22:44:41] good question :) [22:45:15] an important gadget that doesn't work with Vector [22:45:26] i think we'll have to make these calls case by case [22:47:12] actions menu not accessible with keyboard [22:49:41] what do users do in this case? [22:49:48] do they just go back to monobook? [22:49:57] yes [22:50:19] and is it difficult for them to do so, e.g., is it difficult for them to find the take me back link? [22:50:59] take me back isn't the best wording [22:51:37] wording aside, is it difficult for them to find the feature? [22:52:09] (we should have a conversation about the wording if enough of the community thinks take me back is unclear) [22:53:25] it depends on what you mean by find. the link should definitely have more prominent style than the current one [22:53:49] i'm not so sure about that [22:54:14] this is a feature which shoudl be easy for users to find, but i don't think we should advertise/promote the feature [22:55:17] people see that skin has been changed. they consider those new two links as a part of the change and ignore it since they think it's just some new personal related feature since it's in personal menu [22:55:44] what evidence do we have of that? [22:59:47] well, that's quite unfair question. the answer is probably none but random feedback or observation. however, it's same like if i asked what evidence do we have on "the changes we've done are good improvements" or what evidence do/did we have to make us to do such and such major change in ui [23:00:17] *jorm posits, "monobook was hella ugly". [23:00:49] design != functionality, do not combine them, please [23:01:29] well i actually do think it's a fair question, as are the questions you posed [23:01:55] i'm not attacking [23:02:00] I'm going to disagree with that, actually. Form and function are often intertwined heavily. [23:02:34] neither do i [23:02:45] rather, i think we all know that given our current tracking, we don't have the granularity we'd like to see [23:03:19] unfair maybe wasn't the best english word for that, i may lookup other one. [23:03:30] let's not get hung up on semantics [23:04:05] i'd rather focus on the problem at hand [23:04:22] which is what we do for accessibility [23:04:35] if it's not difficult for these users to revert to monobook [23:05:01] it's a solution of course [23:05:03] and we think users can take this path if they want to [23:05:25] then it's probably not a blocker and something we can solve after release [23:05:26] the question is, if it's the best one [23:05:32] well it's not the best solution [23:05:38] i see what you mean now [23:06:27] who's pushing forward the accesibility work? [23:06:35] then basically nothing is blocker, because usercan whenever switch to monobook (or any other skin) [23:07:17] well if there was an important gadget that a lot of editors rely on that was incompatible with vector [23:07:30] that would be a blocker [23:07:46] but it's hard to really discuss without specifics [23:07:53] correct