Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lemoji contributions guide #104

Open
gustavwilliam opened this issue Nov 21, 2020 · 6 comments
Open

Lemoji contributions guide #104

gustavwilliam opened this issue Nov 21, 2020 · 6 comments
Labels
area: documentation Documenting workflows and conventions type: feature A request for or implementation of a new feature

Comments

@gustavwilliam
Copy link
Member

Lemojis are great and I've heard about many people being interested in contributing. There are however many steps involved and things to know before getting started, which is why I'm proposing a lemoji contributions guide. It will mention at least the following core points:

  • The lemojis are based on Twemojis
  • How relevant Twemojis are found and downloaded
  • We work with vector graphics, which means that the contributors should be based on the source files (svgs)
  • What lemoji template they should use
  • Our workflow and possibly links to the contributions guides
  • Some general advice

If we keep it clear and concise, I think this short guide (located in the emotes/lemojis/ folder) will help keep consistent and high quality contributions. We will still talk to all contributors who are interested in being part of the process and mention the importance of our communication in #dev-branding. This guide will simply aid in making sure the contributions are of the highest possible quality.

@gustavwilliam gustavwilliam added area: documentation Documenting workflows and conventions type: feature A request for or implementation of a new feature labels Nov 21, 2020
@lemonsaurus
Copy link
Member

So basically just a README in the lemoji folder, right?

I'm not mad at that.

@gustavwilliam
Copy link
Member Author

Yes, exactly like that. Would we be able to call it CONTRIBUTING.md and have it displayed automatically when going into the directory, or would we need to call it README.md? I think both would be fine.

@lemonsaurus
Copy link
Member

I think it has to be a readme to be displayed, but not sure.

@Akarys42
Copy link
Contributor

Akarys42 commented Mar 8, 2021

It has to be called README, yes. The extension doesn't matter.

@lemonsaurus
Copy link
Member

I'd still very much like to see this one happen.

@lemonsaurus
Copy link
Member

Whoops, lol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation Documenting workflows and conventions type: feature A request for or implementation of a new feature
Projects
None yet
Development

No branches or pull requests

3 participants