Contributor Documentation

[jasonnicholson]

Is there any contributor tips or documentation? A quick search tells me no so I am looking for someone to respond with tips. Here what I want to do:

• I am finding bugs and missing features. I'd like to fix them.
• Eventually, I will want to add features.

[joeced]

@jasonnicholson This sounds really great.

There is no contributor documentation, it is pretty much learning by doing. Several contributors have succeeded, so definitely think you can too.

I'll most likely have some time in a week or two to put some more words on it.

[apozharski]

I can help write some words to working with the tree-sitter parse-tree handling part at about the same time @joeced.

[jasonnicholson]

Hi, is there any update here?

[Remi-Gau]

generally related to this: adding issue forms to help triage issues

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

[jasonnicholson]

So long term, I would like to be a contributor and ultimately a maintainer of this project. So anything you can do help pull me in would be helpful. I cannot guarantee anything as I am a father and work full time. I do have approval to contribute to this project from my work email. I don't have time allocated as part of my duties at work. My contributions will be sporadic over the next decade or so.

I do have background in MATLAB, Python, many other languages, GitHub Actions, Linux and Windows. I can help maintain the CI system. I also understand algorithms and data structures. I can also help train others in these areas.