Page MenuHomePhabricator

Create short link for outreachdashboard.wmflabs.org
Open, NormalPublic

Description

The URL outreachdashboard.wmflabs.org is so long and consists of such complicated words that students will have problems typing it.

dash.wikimedia.org should redirect to outreachdashboard.wmflabs.org.

Event Timeline

Restricted Application added subscribers: Base, Aklapper. · View Herald TranscriptSep 21 2016, 10:31 PM
Abit added a subscriber: Abit.Nov 8 2016, 5:58 PM

Tighe, Vahid and I have been brainstorming at talking to the WMF comms team about names. We wanted a name that emphasizes that this tool is good for organizing programs while moving away from "Dashboard", since so many things are already called that and there has been some confusion with program leaders creating programs that get deleted from https://dashboard.wikiedu.org/ .

We are close to settling on Program and Events Management System (although Vahid really likes Wiki Program Assistant), the url could be pems,wmflabs.org .

Thanks for reply :).

Not sure that either Program and Events Management System or Wiki Program Assistant are particularly good ideas. Very long and difficult to understand if you do not speak English :). Both need abbreviations to work.

I think this is something we should discuss in the collab - a group of most experienced education leaders. The name will impact the ability to succeed with our projects worldwide.

Pharos added a subscriber: Pharos.EditedNov 8 2016, 6:27 PM

The Wikimedia NYC chapter, thinking about the usefulness of this tool both for classrooms and edit-a-thons, has reserved Wikithon.org, if people would like to use that as a redirect.

I like dash! I like that it's short and unique :-) It doesn't need to have a meaning

  • actually what does Moodle mean anyway? :-)

https://dash.wikimedia.org/ would work for me :)

+1

Easy to type and remember.

Ragesoss updated the task description. (Show Details)Feb 27 2017, 9:52 PM
Ragesoss added a project: Domains.
Restricted Application added a project: Traffic. · View Herald TranscriptFeb 27 2017, 9:53 PM
ema moved this task from Triage to DNS Names on the Traffic board.Feb 28 2017, 11:41 AM
Restricted Application added a project: Operations. · View Herald TranscriptFeb 28 2017, 11:41 AM
Dzahn added a subscriber: Dzahn.EditedFeb 28 2017, 4:28 PM

I think dash.wmflabs.org would be no problem at all, but dash.wikimedia.org might be because it implies a production service and the domains wikimedia.org and wmflabs.org are strictly separated. The theory is that Labs is for testing services and real production services with real end-users are moving to production.

dash.wmflabs.org is a bit awkward.

could the WMF education team register a completely different domain of first order? eg wikidash.org or something of this sort?

Dzahn added a comment.Feb 28 2017, 6:33 PM

What about the option of using dash.wikimedia.org (or outreach.wikimedia.org?) but also actually moving your service into production? I think if it has real users and we want it to be reliable service facing the public it should be anyways. There are other "microservices" like annual.wm.org, transparency.wm.org and also interactive apps like iegreview.wm.org in production like that and it shouldn't be a real problem to do if you tell us about your requirements.

@Dzahn I would love to move it production. I understand that it's a more complicated thing than many of those "microservices", as it's a Ruby on Rails application with a not-insignificant number of dependencies. This is something that @dduvall and @awight previously did some groundwork for, but if you can point me in the right direction for what all it would take to be able to move it to production, I can start working on it and/or trying to find folks to help.

Dzahn added a comment.Feb 28 2017, 7:48 PM

@Ragesoss I am willing to help with the productionizing. One thing to start with would be a list of requirements (software package names) that you had to install on your labs instance to get this going. A second one would be to request a repository on Gerrit (if not already existing) for the content and upload the existing code and get a (security) review for it. Finally we would make a small puppet role/module that installs the packages and git clones your content into the right place from your new repo.

Dzahn triaged this task as Normal priority.Feb 28 2017, 7:50 PM
Dzahn added a comment.Feb 28 2017, 8:52 PM

@Ragesoss @dduvall Oops, is this the same thing that is suggested for deletion here? https://gerrit.wikimedia.org/r/#/c/340164/ is programdashboard and outreachdashboard the same? Let's not delete it yet then?

@Dzahn That was part of the groundwork I mentioned, but it isn't actively being worked on. I think the idea was to delete it now, re-add it if/when it becomes relevant.

@Dzahn: a quick glance, it's also out of date in terms of the requirements; among other changes, the project is on Ruby 2.3 now.

Dzahn added a comment.Feb 28 2017, 9:34 PM

@Ragesoss Ok, just seems like a waste of good work to remove it entirely and start from scratch. Maybe we can start by updating the dependencies list on https://gerrit.wikimedia.org/r/#/c/340164/1/hieradata/role/common/programdashboard.yaml ?

@Dzahn sounds good. I'll start pulling together all the dependency updates I notice. I added the Gerrit one, and I guess the existing set of tasks on the workboard for 'stabilize deployment' is still basically the right set of steps: https://phabricator.wikimedia.org/project/board/1052/

@Ragesoss Nice. Yea, those tasks on that workboard column sound about right to me. I'll comment on T159274 for getting the Gerrit project/repo.

Is it likely to have this implemented by September?

For a wikimedia.org link, very unlikely. Getting all of the requirements in place to move this to WMF production servers is a pretty big project, and one I don't expect to have much time to focus on very soon.

Maybe something like dash.wmflabs.org at least?

awight removed a subscriber: awight.Mar 21 2019, 4:00 PM