do i work on a branch and PR or work in

Funny you ask. We have a contributing guide, but its only ok-ish, working on an update right now

But basically, fork the repo, work on your fork, then propose the PR

There's a CLI tool to help boostrap a package, or you can just copy the closest existing package

For example, if I was adding a new LLM, I would copy llama-index-integrations/llms/llama-index-llms-openai-like into a new folder like llama-index-integrations/llms/llama-index-llms-my-llm and work from there

parfait

merci

Hopefully the folder structure makes the organization clear 🙏

i basically assumed what you said but wanted to check

before i messed up

😄

what about nodeparsers @Logan M?

they seem to be in 'core' instead of 'integrations'

Ah that just means theres no node parser integration yet 👀

oh ok

gotcha

(eventually if things are cool enough, or don't require any huge dependencies, they might move to core)

yeah i wanna use unstructured to make a little bit of a more advanced parser

deciding if it's a good idea to work within llama-index repo to make it a tool or just develop using llama-index

shrug

If you think it will be generally useful, highly recommend a PR 💪