Added myself to reviewer's list. (#191)

* Clone linked list with random pointer

* addition in  reviewers list
pull/194/head
Aayush Jain 2021-04-15 00:08:49 +05:30 committed by GitHub
parent d991c37cf1
commit 6cb96b0d44
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 29 additions and 15 deletions

View File

@ -1,4 +1,5 @@
# Data Structures and Algorithm
Data structure and Algorithm (DSA)
## Contribution Guidelines
@ -10,10 +11,12 @@ The problem being contributed must either be a simple **file** (**Eg.** [`kruska
The directory tree has the following convention of `category/language/problem`, where `category` is the topic or category of the problem being contributed (**Eg.** `strings`, `sorting`, `linked-lists` etc.), `language` represents the language code of the problem (**Eg.** `c-or-cpp` for C/C++, `python` for Python, `java` for Java etc.), and `problem` is a conforming name to the problem (**Eg.** `linear-search.cpp`, `palindrome`, `queue-linked-list.cpp` etc.)
A unit `problem` must conform to the following specifications:
- The name should be in lowercase. (**Eg.** `palindrome/`, `binary-search.cpp` etc.).
- Each word must be separated by a **dash** or a **hyphen** (`-`).
**If you have a problem that belongs to a new *topic* or *category* than one which are present:**
**If you have a problem that belongs to a new _topic_ or _category_ than one which are present:**
1. Create a new folder and an index for it inside (a readme, `README.md` file).
2. To each new index file, write the readme with your `problem` in it ([Markdown Documentation](https://guides.github.com/features/mastering-markdown/)).
3. The folder name can also only contain **lowercase characters** and **dashes** or **hyphens** (`-`) (Eg. `strings` `sorting` etc.)
@ -29,6 +32,7 @@ The project and folder-based contributions have a bit more stricter contribution
The folder should conform to the `problem` specification, along with the following specifications
**Folder Structure**
```bash
problem-name\
| - .gitignore
@ -40,7 +44,7 @@ problem-name\
#### `README.md` Specification / Template
```markdown
````markdown
# <Title of the Problem>
< description of the problem >
@ -57,12 +61,14 @@ problem-name\
```bash
make # or 'cargo run', or 'dotnet run' or 'mvn exec:java' etc.
```
## Test Cases & Output < if exists>
< If you can provide test cases, describe it here, else remove this section >
```
````
#### `.gitignore` File
```gitignore
# add all output files and build files to be excluded from git tracking
main # executable file also must have the project name
@ -70,7 +76,9 @@ target/ # the build file, for example for rust
```
#### Build File / Specification File / Configuration File
It can be any of the following ones
- **C/C++**: `Makefile`
- **Python**: `requirements.txt`
- **JavaScript**: `package.json` and `package-lock.json`
@ -88,24 +96,30 @@ Again, the source codes must conform to a valid file structure convention that t
The programming should keep the naming convention rule of each programming language.
### Other topic
- [First-time contribution](CONTRIBUTING.md)
## Contributors
<a href="https://github.com/MakeContributions/DSA/graphs/contributors">
<img src="https://contrib.rocks/image?repo=MakeContributions/DSA" />
</a>
### Reviewers
|Programming Language| Users |
|-------------------|---------------|
| C or C++ |@Arsenic-ATG, @UG-SEP |
| Java |@TawfikYasser, @cyberwizard1001 |
| Programming Language | Users |
| -------------------- | ------------------------------------------------- |
| C or C++ | @Arsenic-ATG, @UG-SEP, @aayushjain7 |
| Java | @TawfikYasser, @cyberwizard1001, @aayushjain7 |
| C# | @ming-tsai |
| Go |@atin |
| Go | @atin |
| Python | @Arsenic-ATG, @atin, @sridhar-5, @cyberwizard1001 |
| JavaScript | @paulsonjpaul |
## Open Graph
<img src="https://opengraph.github.com/3b128f0e88464a82a37f2daefd7d594c6f41a3c22b3bf94c0c030135039b5dd7/MakeContributions/DSA" />
## License
[MIT](./LICENSE)