Sat, Jan 20
strategic planning is, IMO, deciding where we want to arrive first and on the route to get there only after that
Wed, Jan 17
Do we have assumptions that we like to test (not as in usability test, but more as find out about the possible context)
Improve Gadget Infrastructure: Gadgets could be
Cleaning up preferences: Yes.
Tue, Jan 16
Some scenarios with realistic show-rates (how often one will, without any muting, encounter a survey) could be helpful in planning this, e.g. one for a person of a group that might be asked relatively often, one for a less frequently asked and another one for readers or so.
Mon, Jan 15
I wonder if "What general purpose they serve" is answerable by a quantitative study.
Fri, Jan 12
Seems like a useful feature to me.
Wed, Jan 10
So I feel like the choice here is really between not supporting free-form answers at all, or support storing them privately for researcher-only access.
Mon, Jan 8
Update: we might also use a mass message with signup OR a "newsletter" (https://www.mediawiki.org/wiki/Extension:Newsletter)
But apart from these details, my big question is – how do we educate our users about these new features?
This "?" would be a keyboard shortcut, not something I type in some box or so?
It does not look nice, indeed. On the other hand, I assume it was never designed systematically (in the sense of "If we put IDs in the header, where else do we use this element?"). So I would frame it as a bit of (non-wicked) design debt. Like with technical debt, we might want to refactor it.
Fri, Jan 5
Yes. For the sake of clarity, let’s assume the schedule @Lea_Lacroix_WMDE suggested initially (if we think we can make it) OR suggest a new date. (Both being fine, I just don't want loose it in unclarity about the "when")
Thu, Jan 4
Wed, Jan 3
For most questions I can think of, the just-record-the-namespace idea is fine. One could also think of an abstraction layer that could potentially extract some other information like article length, number of editors etc. in chunks (like percentiles, S/M/L/XL or so) and put it into a structured format (JSON or so), resulting into data like
Why are free form fields excluded? (a link or so to a discussion on this or so would be nice)
Dec 14 2017
Yes, the latter would be much better. It is not a unbreak-now, but neither the under-the-data-headline nor the huge whitespace are good enough for not changing it to a better version.
I think it does semantically not belong under the "Daten" headline.
I don't know where we currently have/need an error icon. In case it is needed, take this:.
I thought is is done for me and I did not tidy the tasks yet.
Dec 13 2017
I don't get what c) means, but I think that a) and b) make sense. They are not mutually exclusive options but cases to consider, is it?
I suggest to add (Optional) to the field's label/placeholder
I do agree to disallow decimal points (and I don't think, we should add this feature at all).
OK, I see 3 points on order of urgency:
Oky, that is easy to fix, I assume. I edited the background away.
Please advise dear product and UX overlords!
Dec 12 2017
@Pablo-WMDE If you mean the moving of the ticket on the design board: I strongly assume @Charlie_WMDE did this as part of our normal organize-design-tasks-meeting. @kai.nissen are you fine with the icon files, the task is done for design.
rather overflow than overlap.
@Jdforrester-WMF : you mean this, I assume?
If yes, I see no problem in the change itself, but rather in some (If I remember it right) brittle UI around that link.
@thiemowmde: Thanks! I'm fine with that, too. (I'd still prefer the examples a bit, but only a test could show, so we can move on with either)
Dec 11 2017
Was on the fast lane and not estimated. Would have been an S.
I consider this solved from the design side and would unassign our tag if that is fine.
So the error occurs only if there actually is an error (which is found via checksums or the like)?
I suggest that transition from private to company triggers the invalid state for Company Name and that transition from company to private triggers invalid state for Given Name and Sirname.
Do you think that's ok, @Jan_Dittrich
Dec 8 2017
Here the improved mockup:
Dec 7 2017
"Fördermitglied" and "akt. Mitglied" (without line break at space)
- I would never have thought of "Klarna" when thinking of Sofortüberweisung. Do they currently rebrand? I was thinking of this brand, the SOFORT name.
Deep link for testing: http://localhost:31337/?skin=cat17&betrag_auswahl=50&periode=0&zahlweise=UEB
I think the label BIC (Optional), as suggested by @gabriel-wmde is correct. Checkmark if BIC is given. If no BIC given: no checkmark, no error, no "did you forget your BIC" message.
@kai.nissen : In this case the blue would be green and have the corresponding "?" or "✓"- icon.
Is it about this state?
Dec 6 2017
There are several aspects I have considered to make the warning appear as such: Icon, color, display of the text
let use select payment interval before amount?
@Jan_Dittrich So we change the order of items?
Dec 5 2017
Dec 4 2017
Dec 1 2017
I only spend like 10 min, but have a look and ping me if you need more variations:
Nov 30 2017
Nov 28 2017
thanks @Bachounda, I oversaw the 2017.
thanks @Bachounda, I oversaw the 2017.