Explore Projects

<p>This project aims to implement a library that integrates with the existing coala code and allows writing native bears for coala that can leverage the power of ANTLR and enable them to advanced linting routines based on the parse-tree of a language with a given grammar.</p>

<h4>GitMate for all!</h4> <p>This time with user configurable plugins!</p> <h3>About the product</h3> <p><strong>GitHub</strong>, <strong>GitLab</strong> and <strong>BitBucket</strong> support webhooks for common events like opening/closing/commenting on Merge Requests, creating Issues, etc. These webhooks could be configured for automated response using their own API's for comments, tests/integrations, etc. <strong>GitMate</strong> merely acts as a tunnel for these events and responds accordingly. The interface for these API's is held by its wrapper library, IGitt.</p> <h3>Aim of the project</h3> <p>This project is aimed at extending the support for <strong>GitMate</strong> to <strong>GitLab</strong> and <strong>BitBucket</strong> repositories. This adds up to unified and automated code analysis and maintenance on the big three code hosting platforms.</p> <h3>Implementation</h3> <p>This project consists of implementing <strong>GitLab</strong> and <strong>BitBucket</strong> interfaces in <strong>IGitt</strong>, following the already implemented <strong>GitHub</strong>'s convention, while simultaneously creating webhook responders and tasks for the same on <strong>gitmate-2</strong>.</p> <p>Extending plugins is quite easy on <strong>gitmate-2</strong> following <code>gitmate_testplugin</code> as an example, thanks to its plugin-based architecture.</p>

The project aims to eliminate GBridge and merge its functionality into greybus (linux driver) and cc1352 driver. The subtasks I have identified are the following: 1. Allow Greybus Linux driver to directly communicate with cc1352 2. Move SVC and APBridge roles into cc1352 3. Eliminate the need for GBridge

<p>coala is a modular and language-agnostic tool for performing static code analysis. The aim of coala is to make static code analysis easier for the users. However, getting started with coala for a user requires prior knowledge about different bears coala has (users may get confused among lots of available options), how to create a correct coafile, what values to provide for settings, avoid duplicity among the bears, what bear-dependencies to install, etc.</p> <p>coala-quickstart is a tool with an aim to help users to quickly get started with coala by doing all the boilerplate work. It generates a .coafile (coala's configuration file) that is tailored to the project.</p> <p>The ultimate goal of the project is to make coala-quickstart generate a more tailored coala configuration file with less user effort and time.</p> <p>The primary objectives of the project are:</p> <ol> <li>Develop a mechanism to extract information of interest to coala like setting values from some common kinds of project files like <code>Gruntfile.js</code>, <code>Gulpfile.js</code>, etc.</li> <li>Make coala-quickstart include relevant bears to the project in the generated coafile.</li> <li>Improving the user interface, increasing automation and adding some minor features.</li> </ol>

<p>Goal of this project is to use coala's json output format, convert it to various test result formats and then integrate these test format reports to various tools like CricleCI, Appveyor, Jenkins and Phabricator. Result format inconsistencies has been a problem for a long time but the benefit of converting the static analysis results into a test result format can provide tight integration with various systems. This project also aims to provide our upstream linters with some of these test formats using the Result Reporter Tool library and help developers in extending this project to other formats and uses in the future.</p>

<p>The project focuses on improving coala's dependency management for installing bear and their dependencies on multiple platforms. Specifically, the core focus is on trying to automate dependency management using Ansible playbooks and roles. Additionally, improving the existing dependency management API by introducing a <code>PlatformRequirement</code> class for system specific package managers and fixing and improving the exiting cib install bears tool which uses the dependency management API by adding complete test coverage.</p>

<p>This project aims to increase the usability and easiness for all the open-source enthusiasts by enhancing and improving the coala <a href="https://community.coala.io/" target="_blank">Community website</a> as well as coala <a href="https://projects.coala.io/" target="_blank">Projects website</a> for <strong>newcomers</strong>, <strong>developers</strong> as well as <strong>for other communities</strong>. A community website plays an essential role for an open-source community because it spreads the idea of offerings that community provide to other organizations, with information about the active community by exploring their skills as well as their precious contributions to it. So, the major focus of this project proposal is to enhance the architecture of websites. In addition, new API Endpoints will be created in coala <a href="https://gitlab.com/coala/landing" target="_blank">webservices</a>. These new endpoints will manage the user-database as well as coala database in a more structured form.</p>

<p>The <a href="http://www.creative-technologies.de/linux-based-low-latency-multichannel-audio-system-2/" target="_blank">CTAG face2|4 Audio Card</a> is a multichannel I2S soundcard based on the <a href="http://www.analog.com/media/en/technical-documentation/data-sheets/AD1938.pdf" target="_blank">AD1938 audio codec</a> by Analog Devices. Currently the soundcard can only be used with a <a href="http://beagleboard.org/black" target="_blank">BeagleBone Green/Black</a>. Due to CPU intensive calculations in digital audio the <a href="http://beagleboard.org/x15" target="_blank">BeagleBoard-X15</a> seems to be a perfect alternative to realize more complex audio effects and synthesizers and achieve lower latencies. Moreover the BeagleBone-X15 (<a href="http://www.ti.com/lit/ug/spruhz6e/spruhz6e.pdf" target="_blank">TI AM5728 SoC</a>) offers two separate DSPs (<a href="https://www.ti.com/lsds/ti/processors/dsp/c6000_dsp/c66x/overview.page" target="_blank">C66x</a>) which can be used to offload cpu-intensive multimedia tasks in asymmetric multiproccesing (AMP) configurations. The goal of the project is to port the soundcard drivers to the BeagleBoard-X15 and create an user-space library to make use of C66x DSPs via TI OpenCL and TI DSPLIB.</p>

<p>SPI slave driver implementation. The task is to create a driver controlling SPI hardware controller in slave mode, and to ensure optimal performance through the use of DMA and interrupt. Creating an easy to implement realization of SPI slave would definitely help the BeagleBone community members to write applications based on SPI much more easily. The first implementation of my protocol driver is going to example of a bidirectional data exchange. This application will provide the BeagleBone community with valuable experience and will be a good example of SPI slave. Hardware limitations make it impossible to perform any realization of the device using SPI slave. Sending away data to the master during one transaction is not possible. One transaction is enough to receive data by slave device. To receive and send back data, two transactions are needed. The data received from master device in a single transaction is transferred to the user after completing the transaction. The user's reply to received data is sent in the next transaction.</p>

<p>As coala tries to be welcoming organization for newcomers, giving them clear pathways and as much direct assistance as possible. However, it is already known that newcomers face many barriers while attempting to contribute to the open source community for the first time. Some barriers they face include orientation issues that can potentially demotivate newcomers from placing their first contribution. On the other hand, gamification is widely used to engage and motivate people to accomplish task and improve their performance.Therefore, the goal of this project is to use gamification to orient and motivate newcomers to overcome onboarding barriers to contribute and engage with coala and its community.</p>

<p>This proposes a new action system which will allow bears to define their own actions, hence make bears more useful. Implementation of such a system makes providing support for bears which can suggest multiple patches, which is a part of Improve Diff Handling project, easy.</p>

<p>This idea is aimed to improve the experience of Bone101 to make the most use of it to be friendly to novice developers, allowing them to work with BBUI inside tutorials, write python code beside Javascript, and discover new experience of Bone101 in Cloud9 IDE.</p>

<p>Gitmate, a git workflow management bot created by coala, hasn't been actively maintained in the last 3 years. My project aims to update it and bring it back to active use for the coala community. I plan to undertake various improvements to Gitmate as well as IGitt, the underlying library that powers Gitmate's git operations.</p> <p>My primary goal is to set up Gitmate for the coala community. I will also upgrade both Gitmate and IGitt to the latest API versions of Github, Gitlab and Jira and add support for the latest python versions by upgrading the dependencies. Along with this, I will update various aspects of the documentation of both these projects, improve testing, and ensure that the Continuous Integration setup is in perfect condition. The last phase of my project will involve merging three pull request plugins into a combined plugin and improving various pull request events. Throughout the project, I will work on feedback from the coala community and try my utmost best to improve their experience with using Gitmate.</p>

<p>To develop an analyzing routine at least for python and java that will find all documentation strings in a file, parse them into specific groups and check them against a specified documentation style given by the user. The functionality can be extended so that the analyzing routine provides a patch that re-formats the documentation correctly, checks for grammatical errors (eg: checking parameter’s description for imperative present tense) and perform other aesthetical fixes (i.e capitalization, sentence termination with a period).</p>

This project contain two parts which are Bb-Config Improvement and GPIO Benchmarking. For bb-config improvement, I will implement some new features on top of it making more user interactive and functionable. For GPIOs benchmark, We needed data to help ourselves and developers to decide which method accessing GPIOs suit them better. We compare the latency performance of different methods to access GPIOs.

<p>coala has come a long way from its early days in terms of its usability, although all the changes that have been made are improvisations. A proper and planned overhaul of the user interface would help coala become much more user friendly and intuitive. At its core any software is as good as its interface with the user and this project aims to improve that.</p>

<p>coala currently has few generic bears which are not very useful or are not maintained well. The objective of the project is to get most of the generic bears in a working state so that they can be used in production.</p> <p>Apart from the current bear, this project brings many new generic bears which have been requested by the community from a long time but they were not worked upon. Such bears include <code>OutdatedDependencyBear</code>, <code>FileModeBear</code>, <code>FileExistsBear</code>, <code>RequirementsCheckBear</code>, etc. Apart from these, there are several improvements to <code>PEP8Bear</code> and <code>PycodestyleBear</code>. All of the bears are to be well tested and documented. This project also aims to bring a few improvements to coala core and upstream repositories.</p>

<p><strong>corobo Enhancement</strong></p> <p>The goal of this project is to make corobo secure by reducing its surface vulnerability. It also includes implementing a better testing infrastructure to test plugins like LabHub, as well as to make the existing plugins configurable so that they can also be adapted by other communities to cater their needs.</p>

<h3>git-bug</h3> <p>git-bug is a distributed bug tracker imbedded in git.</p> <h3>Current state</h3> <p>Currently the project provides a large set of tools and functionalities (command line, web UI, and terminal UI) to deal with issues locally and supports Github and launchpad issues imports.</p> <h3>GSoC program</h3> <p>During the GSoC program this project aim mainly to:</p> <ul> <li>Complete bidirectional syncing with Github by implementing it exporter. </li> <li>Support bidirectional syncing with Gitlab by implementing it exporter and importer.</li> </ul>

This project is segmented into four primary categories: Adding Missing Capabilities, Fixing Issues and Enhancements and Adding Examples & Improving Documentation Adding Missing Capabilities focuses on integrating new commands and aliases into the Element API to fill current gaps, guided by the W3C WebDriver specifications. This includes not only the introduction of additional commands but also the creation of aliases for existing commands to streamline their usability. Fixing Issues and Enhancements involves addressing existing bugs and making improvements to the Element API, such as making action commands chainable, enhancing Selenium integration, and incorporating touch/pen interactions. This section also proposes the addition of new commands based on the feedback and needs identified through user and community engagement. Adding Examples & Improving Documentation aims to update the existing examples to utilize the New Element API and introduce new examples that demonstrate the API's capabilities through real-life scenarios and automation tasks. Also, improve documentation for usage of the new Element API as well as migrations docs from the old global element API.

@nightwatch/mobile-helper is a tool that allows developers and testers to set up a fully functional Android Emulator environment in just a few minutes, without the need to download the complete Android Studio IDE software. This tool comes in very handy, especially for testers who wish to perform end-to-end tests for their website or native app on Android Emulators, by allowing them to set up everything they need in under 5 minutes, as opposed to having to set up the hefty Android Studio IDE and figuring everything out themselves.This project aims to take this tool one step further, by building on its usability and allowing users to do much more with the tool such that it not only benefits the testers but the developer community as a whole, or anyone who wish to quickly set up Android Emulators on their machines, while only downloading what is necessary, saving both internet bandwidth and storage capacity. To achieve this, this project proposes: a) Adding support for wireless adb connection to avoid the inconvenience of using USB cable. Users will be able to connect and manage multiple devices, both real and emulator. b) Adding support for downloading and managing multiple system images and emulators to facilitate use of a wider range of emulator devices. c) Adding functionality to update the installed SDK tools. d) Document all important SDK commands for easy accessibility of the users. The tool will help users to perform all these tasks with a very interactive and easy to use command line interface.

<p>vulture is a tool which detects and reports dead (unused) code and coala is an automatic linter. The motivation of this proposal is to:</p> <ul> <li><strong>Extend vulture as an API</strong> which respects the Bear's Input Output method</li> <li><strong>Refactor VultureBear</strong> such as to use the new API - this would highly optimize it's performance.</li> <li><strong>Enhance python whitelist</strong> and making it <strong>default</strong> for every run.</li> <li>Implement a method to <strong>acquire the source range of dead code</strong> - currently, only the beginning of the dead code is reported.</li> <li>Revamp vulture's scavenging property by additional <em>detection of the cases which render the <strong>code unreachable</strong> </em>.</li> <li>Implement a <strong>confidence value with results</strong> - this would be necessary when implementing <em>auto</em> removal, as we would need a proportion of surety or certainty with which we report dead code.</li> </ul>

<p>GitMate.io is an automation tool for developers. While it works well, there are a number of plugins which saves a lot of time of our community(for example automatically close PR's from master). Many of them are general plugins, which are required by every org, but we need more plugins which support coala development workflow(Like gitmate coala linter plugin). This project adds more automations and plugins like auto-review, auto-reject PR’s, assign, mark plugins, etc.</p>