Project Description

csbot is a hubot based bot connected to our production RocketChat instance. Most of the functionality in csbot is focused on fun with some scheduling tools available as well. Expanding csbot to have new features will be a fun way to do some creative Javascript coding and see the changes as they land (csbot has a CI/CD pipeline that pushes changes live as they merge!).

csbot is already running in production, so the focus is new features and expansion/improvement on existing features.

Any number of people are welcome to contribute to csbot, either by creating code changes or suggesting features to be implemented. Keep in mind that the framework this is built on, hubot, does not have nlu support, so the options are not as diverse as more modern bot frameworks.

Goal for this Hackweek

Add some cool new csbot functionality. Explore new or unusual ideas for a chatbot. Have a lot of fun.

Resources

csbot is available for anyone with access to the internal gitlab env at bot/csbot csbot has a pre-packaged development environment at bot/csbot-devel on the internal gitlab, this includes a local instance of RocketChat to test out changes

Looking for hackers with the skills:

javascript rocket.chat

This project is part of:

Hack Week 20

Activity

  • almost 4 years ago: ph03nix liked this project.
  • almost 4 years ago: jeremy_moffitt started this project.
  • almost 4 years ago: jeremy_moffitt added keyword "javascript" to this project.
  • almost 4 years ago: jeremy_moffitt added keyword "rocket.chat" to this project.
  • almost 4 years ago: jeremy_moffitt originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    obs-service-vendor_node_modules by cdimonaco

    Description

    When building a javascript package for obs, one option is to use https://github.com/openSUSE/obs-service-node_modules as source service to get the project npm dependencies available for package bulding.

    obs-service-vendornodemodules aims to be a source service that vendors npm dependencies, installing them with npm install (optionally only production ones) and then creating a tar package of the installed dependencies.

    The tar will be used as source in the package building definitions.

    Goals

    • Create an obs service package that vendors the npm dependencies as tar archive.
    • Maybe add some macros to unpack the vendor package in the specfiles

    Resources


    Editor mode at Agama web interface by ancorgs

    Description

    Agama is a new Linux installer that will be very likely used for SLES 16.

    It takes a configuration (in JSON format) as input. And offers several interfaces to build that configuration in an easy and interactive way.

    I was considering the possibility to add to the web interface a "text editor" mode similar to the XML editor available at virt-manager. That could be used to see how the changes in the UI translate into changes on the configuration.

    Goals

    • Refresh my knowledge about UI development for Agama, since there was a major overhaul recently (adopting TanStack Query) and I need to learn the new way to do things.
    • Please hackers who always want to know how things work internally. :-)


    Try to render Agama in a TUI browser by ancorgs

    Description

    Agama is a new Linux installer that will be very likely used for SLES 16. It offers a modern and convenient web interface that can be executed both locally and remotely.

    But of course some users will miss the old TUI (ncurses) interface of the YaST installer.

    So I want to experiment whether would it be possible to render a simplified version of the web interface for TUI browsers. That's only doable and maintainable if we keep the current technology stack we use for rendering the full-blown page, simply replacing complicated UI elements with others that are easy to render. That means the browser would need to support Javascript.

    Chawan seems to be almost there regarding support for Javascript, XHR and related technologies. But according to this conversation, the next missing piece would be to support recursive import of module script tags.

    Unfortunately, Chawan is written in Nim and I'm pretty sure a week is not enough time for me to learn Nim, implement the feature at Chawan and then fix whatever is the next obstacle on the Agama side.

    But if someone could take care of the Nim part, I would do the same with the Agama one. So this is basically a call for help to get this project even started.


    Design the new UI for storage configuration at Agama by ancorgs

    Description

    We are in the process of re-designing the web user interface to configure storage at Agama. We expected to have a clear idea of what we wanted before starting Hack Week. But the idea is still not that clear. So I will use use my Hack Week time to try several prototypes since I really want this to be done.

    Goals

    Have a prototype using Patternfly components and addressing all the use-cases we want to cover. Easy for the easy cases. Capable for the complex ones.


    Agama Expert Partitioner by joseivanlopez

    Description

    Agama is a new Linux installer that will be very likely used for SLES 16.

    It offers an UI for configuring the target system (language, patterns, network, etc). One of the more complex sections is the storage configuration, which is going to be revamped. This project consists on exploring the possibility of having something similar to the YaST Expert Partitioner for Agama.

    Goals

    • Explore different approaches for the storage UI in Agama.