987299 - Profile: "Top Contributor on ..."

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: Profiles, enhancement)

Description

[Luke Crouch [:groovecoder]]

What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
MDN profile page; e.g., https://developer.mozilla.org/en-US/profiles/groovecoder

What problems would this solve?
===============================
1. Contributors are not recognized for their contributions
2. MDN docs are not associated with the people who write them
3. There are no clear "Calls to Action" from profile pages

Who would use this?
===================
Visitors & Contributors

What would users see?
=====================
On a user's profile page, a new section:

Title: Top Contributor on ...
Content: The list of wiki articles for which the user is the top contributor, by count of wiki revisions they've made. And a CTA link: "Join <username> by contributing"

What would users do? What would happen as a result?
===================================================
Visitors can click the articles to see them.

Visitors can click the CTA link to https://developer.mozilla.org/en-US/docs/Project:MDN/Contributing

Is there anything else we should know?
======================================
We should track the clicks to the CTA link to learn a baseline of CTA engagement from the profile page.

Comment 1

[Luke Crouch [:groovecoder]]

:lorchard - what do you think on the tech design of this? Especially - should we run the top contributor query at profile page render time? Or should we start a new aggregate table/view of contributions by page?

Comment 2

[Les Orchard [:lorchard]]

If it's a data that only changes when a doc changes, I'd say the rule of thumb is that we should pre-calculate & update an aggregate table at the time of doc change.

Not that we're great at this, yet, but we should try to only do super-trivial queries at view time (eg. select name from table where indexed_column=?) This sounds like it might be a bit more complex than that.

Comment 3

[Les Orchard [:lorchard]]

Better yet, queue up a celery task at the time of doc change, since this doesn't sound like something that's critical for rendering feedback on document editing.

Comment 4

[Luke Crouch [:groovecoder]]

:lorchard - Sounds good to me.

:mars - can you schedule this bug into the backlog and help break it down into dependency bugs as needed?

Comment 5

[Māris Fogels [:mars] (please needinfo)]

Removing needinfo until we figure out what the team plans to do next.

Comment 6

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.