Skip to content

Make the federation member infrastructure provider more prominent #3545

Description

@choldgraf

I suggest that we make it easier for mybinder.org federation members to be recognized for their service contributions to mybinder.org - either by putting their logos somewhere, or displaying a more prominent recognition on the "launch page" when being launched on their respective BinderHub.

Current challenge

Currently, the mybinder.org federation gives acknowledgements of its launches in a text banner at the top of the page:

Image

This is not super prominent, and feels easy to skip, which reduces the incentives for others to participate as federation members if they'd like acknowledgement and credit for the support they're giving the project. It is also the same space we use for user-facing announcements, which mixes different types of content in one location.

Benefit from this

Running a federation member can take significant time and resources, so the more we can recognize this work, the more likely people will be to step up. I'd hope that this would incentivize other organizations to pitch in to cover mybinder.org through being a federation member.

Implementation discussion

Questions to ask:

  • Is one logo per member enough, or would we want to have separate thanks for infra costs vs. operations labor?
  • Would this require changing the BinderHub of each federation member config, or could we do this in one place?
  • Would this require front-end work in BinderHub to expose this functionality?

We discussed this a little bit here:

#jupyterhub > Binder UI Design and visibility of Federation members @ 💬

And it might be related to this issue:


COI disclosure: I work with one of the organizations that is currently running a mybinder.org federation member so I'd benefit from this!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions