max-mapper / max-mapper/hexbin

Question: Which of these stickers would be appropriate to put in hexb.in?

Open
#211 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
530
Forks
214
PR merge metrics
No merged PRs in 30d

Description

hi! my friend @torcado194 and i discovered hexbin a couple of weeks ago and we were quickly impressed by the idea of having a standard size for hexagonal stickers. but as we did research for what stickers were available for purchase online, a lot of the services and brands we wanted didn't exist, so we made our own from scratch. all of them were constructed in a vector program by us.

because of some past concern in #155 regarding copyright, creating an issue beforehand seemed like a wise idea. all of these stickers will be put on the Creative Common license like many of the existing hexbin stickers. none of these stickers are being sold anywhere by us. we only plan to upload them to hexbin, wherever possible.

here's the full list of what we'd like to submit:

list of stickers 1

(note: the red lines in these images represent cut lines)

names for each row of stickers, left to right
row 1: Rubik's Cube, Unity, LSDJ, Brackets, Imgur, cPanel
row 2: Glitch, Paint Tool SAI, Toyhou.se, ShareX, Google
row 3: Less, Discord, Google Play Music, Twitch, itch.io, Git
row 4: Hyper, Trello, Ghost Bird (this is a project that @torcado194 is directly in charge of), Aseprite

list of stickers 2

names for each row of stickers, left to right
row 1: Chrome v8, Teenage Engineering
row 2: socket.io, Stepmania, Stencyl

i preferred to create an issue and ask about the entire collection of hexagonal sticker designs we made so that the hexb.in maintainers here on GitHub could quickly comment and help us figure out which ones seem safe to add to the hexbin project and which ones might infringe on the IP of existing projects or companies. please let us know which of these stickers we should upload and we'll pack them into a single neat pull request!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the copyright discussion in issue #155 and the existing hexbin sticker collection, then inspect the two linked sticker-list images and the referenced project pages. Done means maintainers have identified which designs are appropriate for inclusion and the approved designs are submitted in one pull request.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, unity
Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.