Skip to content

Conversation

@lengau
Copy link
Contributor

@lengau lengau commented Sep 12, 2025

We need to talk about your flair.

We were only using the minimum amount of flair.

What do you think of a person who only does the bare minimum?

Rendered: https://github.com/canonical/craft-parts/blob/work/more-flair/README.md

  • Have you followed the guidelines for contributing?
  • Have you signed the CLA?
  • Have you successfully run make lint && make test?
  • Have you added an entry to the changelog (docs/reference/changelog.rst)?

We were only using the minimum amount of flair.

![What do you think of a person who only does the bare minimum?](https://y.yarn.co/5d341f52-5344-4110-9067-6db74c0b06ee_text.gif)

Signed-off-by: Alex Lowe <[email protected]>
Signed-off-by: Alex Lowe <[email protected]>
@lengau lengau marked this pull request as ready for review September 13, 2025 00:39
@lengau lengau requested a review from cmatsuoka as a code owner September 13, 2025 00:39
@lengau lengau requested review from a team, jahn-junior and medubelko and removed request for cmatsuoka September 13, 2025 00:39
Copy link
Contributor

@medubelko medubelko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And in the proper spirit of the 90s, it's like I'm looking at the site footer on Geocities.

I'm going to be the devil's advocate, assuming we want this to become a pattern across our projects. It's not what I had in mind with the README model.

Do we need all of these? There are several that from what I can tell don't provide a variable status. They feel like TF2 hats.

I think there ought to be a rational order to these, at minimum. Something like license > builds > security checks > build checks.

There's no way that download count is an honest metric, right?

@lengau lengau marked this pull request as draft September 13, 2025 01:35
Copy link
Contributor

@upils upils left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @medubelko. It is shiny and fun but it is becoming a bit too much and might be counterproductive by making it hard to find the desired information.

Should we write a small policy with what badges should be / could be / should not be present? (and where they should be?)

renovate bot and others added 8 commits September 17, 2025 12:29
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Make sure to clean the package cache layer when an underlying layer is cleaned.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Some of these are also causing frequent lint CI failures
[![GitHub License][license-badge]][license-link]
[![PyPI - Version](https://img.shields.io/pypi/v/craft-parts)][pypi]
[![PyPI - Downloads](https://img.shields.io/pypi/dm/craft-parts)][pypi]
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/craft-parts)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this isn't as readily available information, I'm not sure about how useful it actually is. Given that we just run make setup and go about our day, the exact Python versions in use aren't that important to surface.

Also, why is this one formatted differently from the rest (doesn't begin with [)?

[![Codecov Status][codecov-badge]][codecov-status]
[![Code Style][ruff-badge]][ruff-site]
[![Canonical Starcraft][starcraft-badge]][canonical-link]
[![GitHub License][license-badge]][license-link]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can understand wanting to add this (being GPL is cool!), but this information can already be found in multiple other places, particularly on the sidebar of the repository.

I'm on the side of "let's delete it", but if others have a strong FOSS spirit and strongly want to keep it, I'm okay with that too.

[![Code Style][ruff-badge]][ruff-site]
[![Canonical Starcraft][starcraft-badge]][canonical-link]
[![GitHub License][license-badge]][license-link]
[![PyPI - Version](https://img.shields.io/pypi/v/craft-parts)][pypi]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is helpful information, it's already on the sidebar.

[![Canonical Starcraft][starcraft-badge]][canonical-link]
[![GitHub License][license-badge]][license-link]
[![PyPI - Version](https://img.shields.io/pypi/v/craft-parts)][pypi]
[![PyPI - Downloads](https://img.shields.io/pypi/dm/craft-parts)][pypi]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

goofy

[![PyPI - Version](https://img.shields.io/pypi/v/craft-parts)][pypi]
[![PyPI - Downloads](https://img.shields.io/pypi/dm/craft-parts)][pypi]
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/craft-parts)
[![QA][qa-badge]][qa-link]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I wish this said "Tests", but that would have to be fixed by renaming the workflow file.

[![PyPI - Downloads](https://img.shields.io/pypi/dm/craft-parts)][pypi]
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/craft-parts)
[![QA][qa-badge]][qa-link]
[![TICS][tics-badge]][tics-link]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only useful to us, and we have our own ways of checking the TICS status. I don't care for this badge.

[![QA][qa-badge]][qa-link]
[![TICS][tics-badge]][tics-link]
[![GitHub commits since latest release][commits-badge]][releases-link]
[![GitHub Release Date][release-date-badge]][releases-link]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already on the sidebar next to the version

[![Documentation Status][rtd-badge]][rtd-latest]
[![Codecov Status][codecov-badge]][codecov-status]
[![Code Style][ruff-badge]][ruff-site]
[![Canonical Starcraft][starcraft-badge]][canonical-link]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually love this. Should we talk to design about somehow getting an even prettier badge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants