The Breakdown

Becoming a Part of the Flock

We love our people and we love empowering them to contribute what they know to push the project forward. We've attempted to make a simple flow for users who want to get more involved, to automate as much of the mundane process as possible.

Every project within the Legesher portfolio follows a similar guideline and flow. Here's the inside scoop to understand how everything works together. 👍

Releases

Releases are the larger moments that the public are aware of. When a new version of a software is released, it is included in a "Release". Some may be a patch because a certain bug was found to full on version upgrades.

Assignees

On each issue an individual or team of people will be assigned when it is added to a Milestone/Sprint. If you are assigned to the issue it is your responsibility to complete the assignment. As always, we are more than willing to help and involve the community as best as you can - even documenting your thought process along the way. If you would like to be assigned to the issue and help solve the issue, please comment on the issue and take the initiative. We love that!! ❤️

We have contributor guidelines that are to ensure you're not wasting your time with mundane tasks and additionally so we maintain consistency across the project.

Issues

We rely heavily on our repository issues to inform us of minor bugs, feedback from users, and to host our roadmap. Many of the repositories relate to one another, as do the issues. Keep an eye on our public roadmap to better understand where Legesher is headed.

Issue Labels

For issues in any repository, they follow the same conventions in terms of the labels that are available. They follow the same style guide for consistency sake across projects.

We group labels by color, according to broad categories. In most cases, each issue will assign a label from each category.

Labels are consistent across repositories, except for a few repository specific concepts. This is for the purpose of making the process of creating new issues and contributing to any repository in the Legesher portfolio easy and consistent.

Opportunity Labels

Opportunities describe the type of contribution that the issue is requesting. This follows the all-contributors description of recognizing all types of contributions.

Color: Blue (#66CCFF)

Opportunity	Description
💬 Question	Answering Questions in Issues, Stack Overflow, Gitter, Slack, etc.
🐛 Bug	Links to issues reported by the user on this project
📝 Blog	Links to the blog post
💼 Business	People who execute on the business end
💻 Code	Links to commits by the user on this project
🖋 Content	e.g. website copy, blog posts are separate
📖 Documentation	Links to commits by the user on this project, Wiki, or other source of documentation
🎨 Design	Links to the logo/iconography/visual design/etc.
💡 Example	Links to the examples
📋 Event Organizing	Links to event page
💵 Financial	People or orgs who provide financial support, links to relevant page
🔍 Funding Finding	People who help find financial support
🤔 Ideas	People who help with ideas and planning
🚇 Infra	Hosting, Build-Tools, etc. Links to source file (like travis.yml) in repo, if applicable
🚧 Maintenance	People who help in maintaining the repo, links to commits by the user on this project
💌 Marketing	People who help in marketing the repo/project
📦 Platform	Porting to support a new platform
🔌 Plugin	Links to the repo home
📆 Project Management	Aids in the initiating, planning, controlling, and closing of a project
👀 Review	People who review the repo
🛡️ Security	Identify and/or reduce security threats, GDPR, Privacy, etc
🔧 Tool	Links to the repo home
🌍 Translation	Links to the translated content
⚠️ Test	Links to commits by the user on this project
✅ Tutorial	Links to the tutorial
📢 Talk	Links to the slides/recording/repo/etc
📓 User Testing	Links to user test notes
📹 Video	Links to the video

Status Labels

Color: Yellow (#E9FF70)

• Status: Available: been through sprint cleaning is available for delegation

• Status: Accepted: accepted by development team to be completed in the upcoming sprint

Color: Light Orange (#FFD670)

• Status: In Progress: currently a work in progress

• Status: On Hold: placed on hold

Color: Red (#FF6666)

• Status: Blocked: blocked and needs additional information to resolve

Color: Orange (#FF9770)

• Status: Review Needed: needs further review in order to be marked complete

• Status: Revision Needed: needs further revision before placed in review

Color: Green (#70FF74)

• Status: Completed: has been completed

Color: Grey (#CFD3D7)

• Status: Abandoned: has been abandoned, may revisit at a later time

Type Labels

Color: Coral (#FF70A6)

• Type: Bug: bug related fix/issue

• Type: Epic: larger snapshot of a feature

• Type: Duplicate: already been mentioned elsewhere

Priority Labels

Color: Purple (#D1A4FF)

• Priority: Critical: at the upmost importance and needs to be completed asap

• Priority: High: top priority as the project cannot proceed without

• Priority: Medium: the resolution has a flexible or extended deadline

• Priority: Low: the resolution is non-immediate

Dialect Labels

Color: Dark Pink (#CD5A86)

Dialect List
Abkhazian	Afar	Afrikaans	Akan
Albanian	Amharic	Arabic	Armenian
Assamese	Avar	Aymara	Azerbaijani
Bambara	Bashkir	Basque	Belarusian
Bengali	Bihari	Bislama	Bosnian
Breton	Bulgarian	Catalan	Chamorro
Chechen	Chinese	Chuvash	Cornish
Corsican	Cree	Croatian	Czech
Danish	Divehi	Dzongkha	English
Esperanto	Estonian	Faroese	Fijian
Finnish	French	Galician	Georgian
German	Ganda	Greek	Greenlandic
Guarani	Gujarati	Hausa	Hawaiian
Hebrew	Hindi	Hiri Motu	Hungarian
Icelandic	Igbo	Indonesian	Interlingua
Interlingue	Irish	Italian	Japanese
Javanese	Kannada	Kashmiri	Kazakh
Kikuyu	Kinyarwanda	Kirghiz	Kirundi
Komi	Korean	Kurdish	Kurdish (Kurmanji)
Kurdish (Sorani)	Kyrgyz	Lao	Latin
Latvian	Limburgian	Lithuanian	Luxembourgish
Macedonian	Malagasy	Malay	Malayalam
Maltese	Manx	Maori	Marathi
Marshallese	Moldovan	Mongolian	Nauruan
Navajo	Ndonga	Nepali	North Ndebele
Northern Sami	Norwegian	Norwegian Nynorsk	Occitan
Ojibwa	Oriya	Ossetian / Ossetic	Pali
Pashto	Persian	Polish	Portuguese
Punjabi	Quechua	Raeto Romance	Romanian
Russian	Samoan	Sanskrit	Sardinian
Serbian	Serbo-Croatian	Shona	Sindhi
Sinhalese	Slovak	Slovenian	Somali
Sotho	Spanish	Sundanese	Swahili
Swedish	Tagalog	Tahitian	Tajik
Tamil	Tatar	Telugu	Thai
Tibetan	Tigrinya	Tonga	Tsonga
Tswana	Turkish	Turkmen	Twi
Uyghur	Ukrainian	Urdu	Uzbek
Venda	Vietnamese	Welsh	Wolof
Xhosa	Yiddish	Yoruba	Zhuang

Programming Language Labels

Color: Coral (#F48370)

Programming Language
Atom	Agda	AFL	Bash
C	C#	Fluent	Golang
Haskell	HTML/CSS	Java	JavaScript
Julia	JSDoc	JSON	Node
OCaml	PHP	Python	Razor
RegEx	Ruby	Rust	Scala
Swift	TypeScript	Verilog

Technical Experience

Color: Teal (#2EC4B6)

• Technical Experience: None: Issue that does not require a technical background

• Technical Experience: Beginner: Issue that requires a beginner technical background

• Technical Experience: Intermediate: Issue that requires an intermediate technical background

• Technical Experience: Advanced: Issue that requires an advanced technical background

Universal Labels

Color: Grey (#E9EBF8)

• good first issue: Indicates the issue is great for beginners to open source / legesher, that includes first-time contributors!

Label Templates

In order to update or add the labels to a new project repository, navigate to legesher-docs/guide/legesher/labels and run the command ruby legesher-issue-labels.rb.