Talk:Technical Collaboration Guidance/Principles

Wording and grammar
I like the idea of such a guideline, and thanks for working on it. Two remarks: Bináristalk 06:19, 17 November 2015 (UTC)
 * responsive is widely understood in programming in a different meaning (it's a UI design that adapts to the device)
 * grammaticaly, the first group of keywords consists of adjectives concerning the product, there is a group of adjectives concerning the developer, and finally a group of nouns. Let's be consistent! I like the first approach the best.
 * Thanks for the feedback, I've incorporated both points. Keegan (WMF) (talk) 22:04, 17 November 2015 (UTC)
 * Responsive was changed to Reactive. Perhaps Adaptive would be nicer? --KSmith (WMF) (talk) 22:58, 17 November 2015 (UTC)
 * I Like It™. Changing. Keegan (WMF) (talk) 00:51, 18 November 2015 (UTC)
 * I added a section header, to make it possible in the future to edit just this section. --KSmith (WMF) (talk) 00:04, 20 November 2015 (UTC)
 * The points are still an odd mix of "Developers should xxx" and "The product should xxx". I would suggest splitting these into 2 separate lists. The first 3 points (and maybe the last one) are about the product. That would also clear up some of the ambiguity (like is is the software that should be adaptive, or the developer?). --KSmith (WMF) (talk) 00:04, 20 November 2015 (UTC)

Scale / Privacy / Security
I liked how unicef called out Scale and Privacy / Security directly (for obvious, biased reasons). I think these are things are often brought up in code reviews, so to not have them here (except for a minor mention under "Accessible") seems to miss what I think is a "principle" that the developer community holds itself to. But maybe these are meant to embody things we think are missing from the way we currently do things? CSteipp (WMF) (talk) 18:53, 17 November 2015 (UTC)
 * ✅ Keegan (WMF) (talk) 22:04, 17 November 2015 (UTC)

+1. Also, can we make the wording take into account that the list isn't exhaustive? -- Krenair (talk &bull; contribs) 20:08, 17 November 2015 (UTC)
 * Sure, I'll poke at the wording there. Keegan (WMF) (talk) 22:04, 17 November 2015 (UTC)

Accessible
It's good to see this, but I almost want to list "accessible" as a specific item in its own list. It's important to aim for accessibility to people with visual disabilities, for example. Without calling it out specifically, the other meanings might overshadow that one. --KSmith (WMF) (talk) 22:58, 17 November 2015 (UTC)
 * Good point. The initial idea was to have "accessible" delineate all forms of accessibility, but now that security is split out it might make sense to split this out further. Keegan (WMF) (talk) 00:51, 18 November 2015 (UTC)
 * I've changed the wording to "consistent, usable experience for everyone, regardless of user ability." How's that? Keegan (WMF) (talk) 20:26, 18 November 2015 (UTC)

Free
"Free" is sadly ambiguous to what it actually means when it comes to software. I would suggest linking to The Free Software Definition by GNU/FSF to explain what we actually mean. Legoktm (talk) 02:42, 18 November 2015 (UTC)