Skip to content

Webpage Integration: User Profile - Contribution Bio #2452

Description

@henryajisegiri

Goal

Display a read-only contribution summary on the public profile, listing the libraries a user has contributed to and their contribution types. This is a happy-path implementation using already-bound user records in the database.
Figma: https://www.figma.com/design/5j0fQssrV9ipoU16P7hfKy/Website-Deliverables?node-id=6635-23412&t=gg2LYOefZJQdTDDx-4

Image

Scope

Full-stack: data fetching and read-only rendering on the public profile page.


Behaviour

  • Query existing user-related records to determine which libraries the user has contributed to
  • Display contribution types: author, maintainer, contributor
  • Logic mirrors the existing library detail page query in reverse: instead of "get contributors for a library," query "get libraries for a contributor"
  • Results should be cached (~24h)

Acceptance Criteria

Data fetching and rendering

  • Contribution data is fetched from the backend and rendered on the public profile page.

Data source

  • Contribution data is pulled automatically from the database and/or repository records.
  • The user cannot write or edit this section.

Contribution types

The following contribution types are supported:

  • Author
  • Maintainer
  • Contributor
  • Reviews (not in scope for this ticket)
  • Version Author
    Each type displays its label as a heading, followed by a comma-separated list of library names where the user holds that role.

Conditional rendering

  • If a user has no contributions under a specific type, that type is not displayed.
  • If a user has no contributions of any type, only the contribution section is hidden. The user-authored bio is still displayed.

FE/BE Actions

Description URL
Fetch user contribution records by type

Out of Scope

  • Reviewer / reviews contribution type — the underlying data does not currently exist in the models. This should be filed as a separate ticket once the data layer is available. (Note: this area overlaps with Teo's achievements work.)
  • Duplicate user record edge cases (same person with different email variants or name variants causing split contribution counts), these are out of scope here and wil be filed separately. The broader fix is the v3 profile flow where users can add their own commit emails.
  • Re-parsing commit emails to recompute contributions, use existing bound records only

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions