Add Tadas Stasiulionis to Contributors list

[tstasiulionis]

Fixes #
Design discussion issue #

Changes

Please provide a brief description of the changes here.

Merge requirement checklist

• CONTRIBUTING guidelines followed (license requirements, nullable enabled, static analysis, etc.)
• Unit tests added/updated
• Appropriate CHANGELOG.md files updated for non-trivial changes
• Changes in public API reviewed (if applicable)

[linux-foundation-easycla]

• ✅login: tstasiulionis / (02f2ff4)

The committers listed above are authorized under a signed CLA.

[alanwest]

@tstasiulionis It is not clear what your goal is with this PR.

[tstasiulionis]

I just followed the "first open source" contribution tutorial by github, and made a quick pull request as noted in the instructions. I thought that this open source project would be cool to work on and learn. Although I have only completed 2-3 weeks of undergraduate term at Kaunas University of Technology on System engineering and c#.

I am a self tought software engineer since 2015, main goal to contribute to this open source project is to have fun and learn. It is my first Open Source project, but I have worked with languages like lua + web dev langs.

[tstasiulionis]

@alanwest

[tstasiulionis]

p.s my undergraduate degree is in Humanitarian Sciences :)))

[martincostello]

While you wanting to get involved in open source is commendable, this isn't the type of change you should make to go about to do that (for any project, not just this one). Maybe you misunderstood the tutorial and meant to just change your fork of the project, not submit the change from your fork to this repository (what would typically be called the upstream of your fork).

Adjusting formatting just for the sake of changing it isn't valuable to this project, and there's no reason to put your name in the contributing guide at all from this project's perspective.

A good way to get started is to either look at topic such as good-first-issue to see if there's a piece of work that contributions are actively sought for, or if you find a genuine mistake in some documentation (like a typo) that you can fix.