Name: Design Research
Description: Wikimedia foundation Design Research team
Type of project: team
Policy:
Visible To Public : yes (can this be changed later?)
Editable By All Users : team members only
Joinable By All Users : no
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Aklapper | T911 Phabricator project display names use awkward capitalization and hyphenation | |||
| Duplicate | None | T78140 Projects with spaces are being displayed on two lines | |||
| Resolved | Qgil | T75994 Phabricator project names and hashtags inconsistently use spaces, hyphens, and underscores | |||
| Resolved | • Jaredzimmerman-WMF | T75807 Request Team "WMF-Design-Research" |
Event Timeline
Comment Actions
If the research team needs to store sensitive or semi-sensitive data or videos about research participants the group would need to not be public.
Comment Actions
It sounds like you want a way to hide tickets and boards rather than the team itself.
Comment Actions
For what is worth, private projects (as in projects containing only private tasks) are at the very end of the queue, see T823: Implement Phabricator Spaces.
Specific tasks can be made private, but we still don't have a fluent process to handle that out of security, operations, wmf-nda...
If this is clear, WMF-Design-Research corresponds to an actual WMF team, so having a team project for them is a no brainer.
Comment Actions
Yes, we should go ahead and create as a team, and pre-add @aripstra and myself. we can deal with the privacy issues later.
Comment Actions
Alright, since now you are in Project-Admins, and you made this proposal, and it looks ok, you can create the project yourself. :)
Just in case: https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#New_projects
Comment Actions
#WMF_Design_Research is missing the dashes. Please follow the guidelines.
https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Name
Reasoning and ongoing discussion: T911: Phabricator project display names use awkward capitalization and hyphenation
Comment Actions
PS: @Jaredzimmerman-WMF please bring a dash back to #WMF_Design as well. I could not edit these two projects myself due to the restricted policies they have.
Comment Actions
@Qgil I can't find the discussion as to why this naming convention was used post migration, can you link to it? I've changed these for now, but after I have a chance to look at the rationalization I might want to talk more. It feels very techy(in a bad way) and dated. But I'm interested in learning more about the rational.
Comment Actions
@Jaredzimmerman-WMF There's also a conflict between:
#design at https://phabricator.wikimedia.org/tag/design/
#Design at https://phabricator.wikimedia.org/tag/wmf-design/
I recommend deleting the second. (It doesn't work anyway, the hashtags seem to ignore capitalization. But it might confuse someone in the future.)
Comment Actions
If we allowed spaces in project names, referencing a "#project name" in text will not work for these projects (you'd have to know that you have to write "#project_name"), plus entering a URL replacing spaces by %20 HTML entities (instead of underscores) like in http://phabricator.wikimedia.org/tag/Some%20Project/ will not work. (T283#3526)
Comment Actions
@Aklapper that makes sense if phab didn't support aliases but since it does I'm not sure why official names can't have spaces, and aliases can be created with underscores, camelcase, dashes, whatever people want.
Comment Actions
fwiw the right place to discuss the current naming guidelines is T911: Phabricator project display names use awkward capitalization and hyphenation.