Projects in the topic javascript
JavaScript (JS) is a lightweight, interpreted, or just-in-time compiled programming language with first-class functions.

Build an open-source appliance editor for SUSE Studio that interacts only with the API, using modern JS web frameworks. For users, this provides an opportunity to influence, or create unique tailored editing experiences for Studio appliances. For Studio maintainers, this provides a road towards a modern appliance editor, and a chance to remove tens of thousands of lines of brittle legacy code. For hackers, this provides a chance to get your feet wet with modern client-side web technologies, like

Finish extension for server side history for jabberd2 server and create a simple webui to browse it using tntnet. Part of the project is to learn to use tntnet toolkit, other part is to have server side history.

QA uses a dashboard (SUSE internal: http://qa.suse.de/dashboard/ ) to provide an overview of various data to assess the quality of a product. The project is about improving the available data points and the usability for users outside of QA department.

Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components: - RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)

a widget to list events from a JSON backend. the widget may be included by any website to share community events.

<a href="http://trivialine.herokuapp.com/" target="blank"><img src="https://scontent-a.xx.fbcdn.net/hphotos-xap1/v/t1.0-9/103560303124060156120696822168581672115471n.png?oh=d7ff3f6c32934ea362156d071e0b660a&oe=54B1308C" width="460px"/></a>

We have the pleasure to introduce you to the first Online Multiplayer Trivia:

It is well-known that two git commits within a single repo can be independent from each other, by changing separate files to each other, or changing separate parts of the same file(s). Conversely when a commit changes a line, it is "dependent" on not only the commit which last changed that line, but also any commits which were responsible for providing the surrounding lines of context, because without those previous versions of the line and its context, the commit's diff would not cleanly apply. As with most dependency relationships, these form a directed acyclic graph. Sometimes it is useful to understand the nature of parts of this graph; for example when porting a commit "A" between git branches via git cherry-pick, it can be useful to programmatically determine in advance the minimum number of other dependent commits which would also need to be cherry-picked to provide the context for commit "A" to cleanly apply.

One of the winning factors of Docker is the Docker Hub. This the a place where the Docker community shares their images. Thanks to Docker's integrated build system it is possible to create new Docker images by just extending an existing one. That's why the Docker Hub is so useful.

Displays your openQA instance status, the feature/behavior should had at least like the list below,

Option page

We have some internal systems for videoconferencing like Big Blue Button or OpenMeetings. But in my experience none of them can compare to Google Hangouts, which is still the best free (as in free beer) alternative for videoconferencing with integrated screen sharing. While implementing an alternative to Sqwiggle on previous hackweek, I discovered Janus, a lightweight WebRTC gateway that proved to be a quite capable tool to implement video applications.

This project will focus mostly on getting to know the Clojure and ClojureScript ecosystem. As part of this project I want to see how good the integration with the respective hostplatform is and how easy it is to use libraries for e.g. JavaScript in ClojureScript.

CodeMirror is a text editor implemented in JavaScript for the browser, openQA introduced CodeMirror in its source viewer, this project is learn more things from CodeMirror and trying to improving the source viewer in openQA, already had a ticket related, even can polish source viewer more, eg. file folding, etc.

The current Jangouts UI is limiting us when thinking about adding new features. Some examples: * This (using the whole thumbnail to pin a participant) was implemented, but the result is far from optimal (I have not even deployed it in production).

PXEAT (stand for PXE Administration Tool) is a tool to easily deploy and manage PXE service. It's NOT a tool for automatic deployment. It can enable user to add their own PXE items by themselves, but of course, very limited for security reasons. The tool will be developed with the light-weight framework - flask, as well as a sqlite database.