rasa VS open-sauced

Support Rasa on GitHub ⭐

It itself is not a GPT. It is a a framework of a framework project built on top of Rasa (https://github.com/RasaHQ/rasa) and Langchain which by default uses gpt3.5-turbo (change it in the .env file) or any foundation model you wish.

There was already a GitHub issue https://github.com/RasaHQ/rasa/issues/11084 but it seems like there was no solution provided.

Rasa - also an open source platform. You can use it to build chatbots that are more in line with customer service and sales. Reading that, it’s kind of a big yikes for people under this kind of job knowing you can automate a part of their job via a chatbot. I think they also have a Pro version which is an extension that has additional analytics and probably more security features. I probably will check out the Open source one first and maybe ask about what the Pro version is.

At the moment it can recognise the type of statements in the training data set [1] and transpile them to Python, Java or C++ using the mappings defined here [2].

This is very different from how Codex/Autopilot work as it is trained using an NLU framework [3] which is usually used for training chatbots.

[1]: https://github.com/Flex-lang/transpiler/tree/master/transpil...

[2]: https://github.com/Flex-lang/transpiler/tree/master/transpil...

[3]: https://github.com/RasaHQ/rasa

Check out Rasa

It looks like it is built upon a Chatbot platform called “messengerx.io”, which itself seems to be built upon an open-source/machine-learning framework for voice/text conversations called “Rasa”

Use Python and use the Rasa framework to make a chat bot. https://rasa.com/docs/

This example is sourced from RasaHQ

OpenSauced cultivates a thriving community of developers through its interactive forum. This virtual space provides a platform for developers to exchange ideas, seek guidance, and collaborate on projects, fostering a sense of camaraderie and shared passion for open source. All wrapped up in a nice GitHub stromboli.

In Part 3 of this series, we'll talk about our use of various plugins for Vite on the Open Sauced project. Vite provides extensibility in the form of a Plugin API, based on that of Rollup. For reference on which Rollup plugins Vite is compatible with (and to what degree), see Vite Rollup Plugins

The most straightforward fix for the circular reference was to update react-markdown through one major revision, but this introduced a new snag. In this major revision, react-markdown changed to ESM only, which would be fine for Vite, but not for our testing approach for jest (other than experimentally, so I learned. @0vortex and I got some help from @jasonericdavis on Discord to mock the react-markdown component in Jest (bypassing the need for ESM support) as part of a preparatory PR, and we got back on track.

This is Part 1 of a series about how recently in Open Sauced, we converted the project from using Webpack v4 to using Vite! A lot of what we'll cover in this series deals with PR #1322. @bdougieyo started this as a create-react-app project 5+ years ago and so this conversion certainly turned out to be an undertaking!

In contributing to Open Sauced and other OSS projects as well, I've found time and time again that there are such ample opportunities to learn. However, contributing a feature and sticking with it on a longer term can cause those opportunities to multiply! In Part 3 of this series, I'm going to talk about some of the after-effects of implementing dark mode on Open Sauced in PR #1020.

This is Part 2 of the series on Implementing Dark Mode. This was done in open-sauced/open-sauced#1020, and handily demonstrated to me the wealth of learning opportunities in contributing to Open Source. I for one have learned a ton! On this one, I got the opportunity for learning in several areas. I was still pretty new to React (and I still am), so I had not yet used the Context API. For a lot of the same reasons, I hadn't used the styled-components library before.

This tool is meant to accelerate development on Open Sauced by giving contributors a way to access Docusaurus 2 powered developer documentation available at docs.opensauced.pizza.

Expanding the @open-sauced ecosystem, it became tedious to apply all the necessary tooling available in open-sauced/open-sauced to newly created repositories and synchronising existing ones with minor updates.

I'd like to share the story behind one of my favorite contributions to Open Sauced so far, which is the addition of "Dark Mode", PR #1020. This PR touched 25 files and was pretty substantial in scope, so I'm going to break this up into 3 parts. Part 1 is here is just the background - the what and the why, as @bdougieyo sometimes says. If there's one takeaway though, it's the value of opening a PR early in your process - you can share your progress and your roadblocks, and maintainers can help you get unblocked!