Thank you for taking the time to consider contributing to our project.
The following is a set of guidelines for contributing to the project. These are mostly guidelines, not rules, and can be changed in the future. Please submit your suggestions with a pull-request to this document.
We have adopted a code of conduct from the Contributor Covenant. Contributors to this project are expected to adhere to this code. Please report unwanted behavior to jeff@jeffreyfritz.com
This project is defining the coolest and simplest markup language delimited ONLY by tabs and carriage returns. This started as a goof on YAML because @csharpfritz is not a fan of that markup technology, but grew into something that we believe may have a better purpose and functionality than YAML.
The purpose of this markup language is to delimit and format configuration files as well as formatting data for storage and transmission
This project is designed to be built and run primarily with Visual Studio 2019. The folders are configured so that they will support editing and working in other editors and on non-Windows operating systems. We encourage you to develop with these other environments, because we would like to be able to support developers who use those tools as well. The folders are configured as follows:
/docs -- User Documentation
/src -- TAML Parsers
/dotnet
/Taml
/Taml -- DotNet Parser
/Test.Taml -- Unit tests
/python
/src
/pytaml -- Python Parser
/tests -- Unit tests
All official versions of the project are built and delivered with GitHub Actions and linked in the main README.md and releases tab in GitHub.
Design for this project is ultimately decided by the project lead, Jeff Fritz. The following project tenets are adhered to when making decisions:
We are always looking for help on this project. There are several ways that you can help:
- Visual Studio (Windows)
- Visual Studio Code (Windows, Linux, Mac)
- Visual Studio For Mac
- Any text editor (Windows, Linux, Mac)
- Any Web browser.
- Report a bug with the details of a bug that you have found. Be sure to tag it as a
Bug
so that we can triage and track it
- If you see an issue that you would like to help with, add a comment stating your intest.
- Fork the project to create your own version of the repositorry.
- Clone the repository locally.
- Create a new branch referencing the issue or bug you are addressing.
- Write some code.
Create a new issue if you have suggestions or ideas to improve the project.
We are always looking for help to add content to the /docs
section of the repository with proper links back through to the main /README.md
.
cmjchrisjones Blog: Contributing To Someone else's git repository