unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 56575@debbugs.gnu.org, 56575-done@debbugs.gnu.org
Subject: [bug#56575] [PATCH]: guix-artwork: badges: GNU Guix "Packaged"
Date: Sun, 17 Jul 2022 12:12:54 +0000	[thread overview]
Message-ID: <C6qGJtitHQQrloCTrpiVfT7PN1ovfwia_lDFBfVVRBbqf2Be7AzXuLU8XPt27dO8xrQ93GAh7sEQEm-474jga73-4nkk1R0HjicxGZKj0VI=@protonmail.com> (raw)
In-Reply-To: <87edykc1xz@nckx>


[-- Attachment #1.1: Type: text/plain, Size: 868 bytes --]

Hey,


On Saturday, July 16th, 2022 at 19:05, Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> Luis Felipe via Guix-patches via 写道：
> 

> > Hello, this is a new badge to help increase visibility of Guix
> > through source management services.
> 

> Wonderful, thanks! Pushed as e53033ebdff0308eff0830760a70497527b10443.

Thank you.


> (Why ‘about the same size’? Is there no single standard?)

I don't know if there is. It seems to me that these badges are 20 px height, but I actually didn't measure badges from different services.

Also, the badge in the patch has a very thin border to prevent the dark left side to camouflage in dark backgrounds. The border makes it higher than 20 px.

I designed the badge over a screenshot of GitLab badges, though, and I think it looks ok. But I'll check again and hammer it down if necessary :)

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

      reply	other threads:[~2022-07-17 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 13:25 [bug#56575] [PATCH]: guix-artwork: badges: GNU Guix "Packaged" Luis Felipe via Guix-patches via
2022-07-16 19:05 ` bug#56575: " Tobias Geerinckx-Rice via Guix-patches via
2022-07-17 12:12   ` Luis Felipe via Guix-patches via [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='C6qGJtitHQQrloCTrpiVfT7PN1ovfwia_lDFBfVVRBbqf2Be7AzXuLU8XPt27dO8xrQ93GAh7sEQEm-474jga73-4nkk1R0HjicxGZKj0VI=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=56575-done@debbugs.gnu.org \
    --cc=56575@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).