Skip to content

Latest commit

 

History

History
90 lines (60 loc) · 2.28 KB

CONTRIBUTING.md

File metadata and controls

90 lines (60 loc) · 2.28 KB
Raw

📃 Contribute Guideline

👋 Welcome, new Wopers

First off, thank you for considering contributing to Wopslang. Wopslang could be existed because of many devoted Wopers like you.

🛠️ How to contribute

❗ Using Issues

Report performance errors on code (memory leak, infinity loop, etc).
There isn't any issue template, but your issue must have these three parts.

  • How to reproduce
  • Error Message
  • Your code(if necessary)

If you already have a solution for it, please make a PR.

🍴 Using PR

If you already have a solution for it, PR suits you.
Code style should satisfy these checklist.

/*
 * <file path>
 * <file description><Headerfile/Sourcefile>
 *
 * <year>, Wops Team
 * */

// if your code is header
#ifndef WOPS_[filename_CAPITAL]_H
#define WOPS_[filename_CAPITAL]_H

/* your code */

#endif

All commit messages should satisfy these checklist.

  • Description Starts with Lowercase Character
  • No Emoji
  • Use Boilerplate Code :
<file name/path>: <description>

Also, your PR can be rejected by these reasons:

  • Too much change
  • No bug check(or performance check)
  • Doesn't match with our plan

Finally, your PR branch's name should be in one of these forms:

  • patch-[username]-[number]
  • dev-[username]-[number]: only for inside Wopers
  • docs-[username]-[number]

💬 Being the Wopslang Manager

Wopslang managers mediate the overheated community, review the issues and pull requests, and lead the development of Wopslang. Of course, this job requires not only deep knowledge of Wopslang, but also conversation skill. Also, Wopslang managers should be in Wops team; Wopslang managers should be inside Wopers.

We're not recruiting the Wopslang manager for now.

Wopslang manager list

Github Username Slack Username
@RedoC-github @RedoC-github
@rdxxer @codenstory
@pokmui @pokmui

2023, Wops Team