Develop and implement a badge "stewarded by foundation for public code"

[Ainali]

Design a badge that communicates that a codebase is "Stewarded by the Foundation for Public Code".

Reasoning:
We would rather have a badge in a footer instead of logo's in headers amongst other collaborators of a codebase, as it would more accurately reflect the way we steward it. We are more of the infrastructure for the codebase than being a driving partner.

• Design badge
• have a hosting location for image
• Remove logo from Signalen.org
• Remove logo from OpenZaak.org
• Remove logo from Demodam.org
• Add badge in footer to Signalen.org
• Add badge in footer to OpenZaak.org
• Add badge in footer to Demodam.org

[Ainali]

First rough sketches on a badge just to explore some possibilities.

[angelplasma]

Sounds like a solid idea, @Ainali! I've made some initial variations, attached below.

Questions:

1. Would we be comfortable with shorter phrases, or even something very concise like "Public Code"?
2. Should this definitely be a free-floating graphic, or something that attaches to the edge of the window?

Working file here (which should move to a more appropriate place, like @bvhme's more official logo file in Figma): https://www.figma.com/file/Mcz4evZVI4rRwv3quXtKGC/Site-Map-Wireframe-exploration-Foundation-for-Public-Code?node-id=1303%3A1667

[Ainali]

Very nice! And excellent questions! For 1. I think that, even though the badge in general are more beautiful with less text, we want a bit of a blurb here since this might be the only information about us on the pages this is shown (since we imagine this could be used in the footer of a site).

And for 2. I think we at least need a version that can function as a free floating graphic, since we will not be in editorial control of the sites that the badge gets used on.

[felixfaassen]

@angelplasma Nice work! I really like the third badge from the left in the top row (and the variant). I think one of the important aspects of the badge is show people that we steward this codebase and that people who are interested in what that means can look that up, I agree with @Ainali. Also nice idea to make a floating one!

[Ainali]

Related is also the question of where should this badge link to? There are a few alternatives:

1. The specific codebase overview on publiccode.net, example: https://publiccode.net/codebases/signalen.html
2. The page on stewardship on publiccode.net: https://publiccode.net/codebase-stewardship/
3. The page on stewardship on about.publiccode.net: https://about.publiccode.net/activities/codebase-stewardship/

The first one is the most obvious one, since it is actually verifying the claim. However, there are not a prominent link to Stewardship (there is one in the footer), which makes the second one tempting. However, I feel that we should improve the codebase page instead, perhaps by adding a link in the "stage box".

Separately, since we have plausible, we should probably use something like ?utm_medium=badge&utm_source=signalen.org in the link.

[ericherman]

Related is also the question of where should this badge link to? There are a few alternatives:

Should it be "one size fits all" or should it be "case by case" or are there three or four "known use cases"?

Separately, since we have plausible, we should probably use something like ?utm_medium=badge&utm_source=signalen.org in the link.

Does this suggest the need for some level of case-by-case customization, regardless?

[Ainali]

Should it be "one size fits all" or should it be "case by case" or are there three or four "known use cases"?

I'm thinking that the link type should be universal, but if we go with the specific codebase overview it will obviously be unique links for each codebase's badge.

Separately, since we have plausible, we should probably use something like ?utm_medium=badge&utm_source=signalen.org in the link.

Does this suggest the need for some level of case-by-case customization, regardless?

Yes. Perhaps the utm_source is overkill for our codebases, since I guess they'll pass along the referrer anyway, but I see no reason why we should not add it. It'll still be separate pull requests to each codebase to add the badge and the link, so we don't have to find a code snippet that works universally.

[Ainali]

Trying to move this forward. Since @felixfaassen liked the third one from the left (and I do too), @angelplasma can you finalize the design of that one and upload the files to the brand repository?

[angelplasma]

@Ainali Apologies for the delay here! I like the rounded as well... but what do you make of this extended hexagonal variation? :)

Let me know, and I'll finalize the assets.

[Ainali]

Personally, I like the rounded more. It's something with the two hexagons having 90 degrees rotation to each other that creates too many angles in a small space. Any thoughts @felixfaassen?

[ericherman]

I, too, like the rounded one more.

[Ainali]

I also made a PR to the brand repository: publiccodenet/brand#22