UX/UI and overall architecture are two very different things, why are they being lumped together?
Topic on Talk:WMF product development process/Archive 3
@Legoktm are you referring to WMF_product_development_process#Design and its related column? I think the term "Design" is used correctly there, with the meaning it has in the context of engineering processes (see i.e. w:Design). I agree it is inconsistent with the use of the term in mediawiki.org (see Design) as in strictly Visual/UX, but I think it is better to fix the latter, not the former. Having Architecture, Performance, and Operations as part of the Design stage makes sense to me.
@Brion VIBBER @Ori Livneh @Mark Bergsma (WMF) what do you think?
Yes. I think Brion pretty much summed up exactly what I wanted to say :)
The current list of tasks under 'Design' seems mostly focused on UX, with "Architecture and operations" sorta thrown in randomly. :)
What is it that arch & ops would be expected to provide in terms of feedback? If what you're asking for is, say, feasibility assessment, it probably belongs back a step or two in Plan. If you're looking for advice on what technical directions to work in ("should this be an extension or in core?" "should this use a mysql table or a separate storage service?" "should this have a a web API?" "how much JS should we use?") then I think you need it in the build stage along with Performance.
@WMoran (WMF), what do you think?
@Brion VIBBER good points. Planning and build are more logical for the respective examples. @Ori Livneh (WMF) and @Mark Bergsma (WMF)?
@WMoran (WMF), I think it is safe to just proceed with the changes and move forward.