New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc inspection tool 001 #87
Conversation
Initial steps for some Apache Wayang related content.
LIBS folder should not be added to the repo.
Hi Justin, Now we have two options: In case (B) no generated content will be published in a software repository, it is just temporary information which allows I understand that following the path towards (A) is still a risk. Hence, the goal is the creation of tool which can be configured to use multiple LLMs, starting from public offerings to personal deployments (such as OpenAI model in Azure self hosted by a user vs. the fully managed OpenAI model which is used right now. |
Is it possible to continue with this kind of activity, as long as we do not use the generated content as "Apache Training content", but rather work on an assistance system which supports content editors (especially for software documentation and for training material) to get better docs faster released? |
OK, thanks Justin. |
Also for a PR like this ... a bit more description would be nice ... I think from having a look at the payload of the PR, I can get a rough idea of what it's about ... but I did notice quite some binary files being checked in and that's one thing we generally don't like to see in apache repos. |
Ok, thanks for the feedback. I will provide description and a clean-up, especially the binaries. |
Hey, after being hit by a first wave of all the LLM Hype, I thought, it would be a nice contribution to the Apache Training project, if we would use this new opportunity. My first experiments with langchain made me confident, that this is the next great thing. There have been several obstacles, e.g., the question: To what extend are we allowed to use LLMs in the ASF context. I have realised that going forward on the tool-level would probably not improve the situation. We can use tools like: https://github.com/peterw/Chat-with-Github-Repo for this purpose. But when I started working on this topic, I did not see this coming. With this in mind, we can close the PR. |
No description provided.