Easy-Guide for contributing to loxilb

[UltraInstinct14]

1. Join as a member and be part of the tribe

It will give access to loxilb slack channel and other helpful resources https://www.loxilb.io/members
Please feel free to discuss any new ideas for implementation with maintainers of loxilb

2. File a bug report

A good bug report should at contain at least the following info

1. Overall description of the issue (can be a subject of the issue for straightforward issues)
2. Build/Release Info ( or just commit-id from where fork was done)
3. Logs or screenshots of the issue
4. Steps to reproduce

Please check a sample issue for reference

3. Check CICD test cases locally

Many of our users have trouble running loxilb initially and have a wide range of doubts. The best thing to do in such cases is to run loxilb's CICD scripts locally in one's own system and try to build-up from there. For example :

cd cicd/tcplb
./config.sh
./validation.sh
./rmconfig.sh

The above will make a docker based test scenario for simple TCP nat LB, perform some test runs and finally cleanup. For curious users, one can check these scripts and even stop after validation script, login to loxilb docker and check various things :

docker exec -it llb1 bash
loxicmd get lb -o wide
loxicmd get ct

4. Contribute to loxilb

loxilb welcomes any code contribution for its improvement with no red-tape in between . Some open issues can be found here. However, users can submit independent patches directly by issuing a pull request of their work. By default, one of the loxilb maintainers will be assigned for code-review and the pull request has to pass mandatory sanity-checks before it can be pushed to main branch.