Figure out whether we want users to have a home wiki? Should courses have a default wiki? Should these fields be optional?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ragesoss | T127803 Release Programs dashboard 1.0 | |||
| Invalid | None | T128250 Release Programs dashboard 1.0 beta | |||
| Resolved | Ragesoss | T128251 Release Programs dashboard 1.0 alpha | |||
| Open | None | T127615 [Epic] Additional multiwiki support for users and courses | |||
| Open | None | T127891 Design changes to Dashboard UI/UX | |||
| Resolved | Ragesoss | T127122 Spike: How should Course and User associate with wiki? | |||
| Resolved | Abit | T127126 Scope out requirements for making courses support multiple wikis and languages |
Event Timeline
Comment Actions
I suggest the answer to both is "yes, and yes". i.e. yes, associate users and (separately) courses with a home wiki, and yes, make it optional.
Comment Actions
That sounds right to me, too. It's a good start, at least!
A minor detail, we might provide a global configuration variable that only Wiki Ed Foundation will use, which causes all of their courses and users to default to enwiki.
Comment Actions
Courses now have a default wiki.
I still don't see a compelling reason to give users a default wiki. We'll implement ULS to let the user choose their interface language. What functionality would be associated with a user's home wiki?
Comment Actions
We've removed any connection to en.wiki, specifically, from the User model. It's still the case that login happens via a specific wiki (currently en.wiki, for outreachdashboard.wmflabs.org), but after that, everything is relative to the specific course and its home wiki. So I think we can close this; adding a user's home wiki can be considered if/when it's needed, but it's outside the scope of this issue.