Explore Projects

<p>The aim of developing the Hawkular android client was to provide users with a seamless experience of monitoring their servers, by allowing general purpose inventory browsing and quick access to favourite metric and alerts. I plan to take this initiative forward and make the android client more detailed, stable and intuitive to use. I plan to do so by:</p> <p>● Adding support for full Alert setup and display.</p> <p>● Adding more details in triggers and improving metric graph visualisations.</p> <p>● Improving and rewriting the previously written tests for models and adapters.</p> <p>● Writing thorough UI tests using the Espresso testing framework.</p>

<p><strong>Create front end components to enable medical image retrieval on the ChRIS platform</strong></p><p>The deadline to create an initial application has passed for the May 2021 Outreachy internship cohort. We are no longer accepting initial applications for internships. We encourage you to sign up for the announcements mailing list to get an email when the next round opens. Why apply to Outreachy? &gt; Start your initial application &gt; May 2021 Outreachy internship cohort &gt; ChRIS Project Community details are hidden until you are approved to participate as a mentor or coordinator.</p><p><br></p><p><strong>Mentorship Cohort:</strong> 2021</p>

The next version of Music Blocks (v4) is currently setup using create-react-app, a widely-used tool but lagging behind in certain key dependency updates. As a result of which certain development features like Hot Module Reloading, are broken. This project aims to take advantage of this lapse and upgrade the core development tooling of the entire project, making it more seamless, with small developer experience upgrades, along with much needed dependency upgrades to make local development fun and fast. Along with these improvements, the project will also tackle the problem of improving production bundle size for faster loading, and creating a Progressive Web App for offline usage.

<p>I've been personally using Riot and Matrix daily for months at this point and have seen many issues thrown around in the development rooms between the core developers. I have made it my task to alleviate some of these, Analytics for one, the devs have been driving blind as far as how people use the app so providing fully anonymous analytics is very important. Discoverability is currently another issue, Riot is a completely frontend application so spidering it is near-impossible, this can be solved through making a read-only server generated view for spiders to work on. Time permitted I will also touch on making a slightly more involved bridging library and look forward until federation stabilises so that I can make an S-S bridge (no HS needed)</p>

<p>A crucial component of the openSNP infrastructure is to make the available data more accessible to the general users and scientists alike. Currently, the portal has independent listing of user <em>Phenotypes</em> and parsed <em>SNP</em>s. Each <em>SNP</em>s entry have an additional information section where data from other credible sources (PLoS, Mendeley, Genome.gov) is made available. There is, however, no direct or inferred relationship available between the <em>SNP</em>s and the corresponding <em>Phenotypes</em> (as reported). <strong>This project proposes to bridge the connectivity between existing <em>Phenotypes</em> and genetic variants with the help of already mined data and implementing additional services as necessary.</strong></p>

The project enhances Plone 6 by integrating Really Simple Syndication (RSS) support through two key components: exposing Plone content as RSS feeds and embedding external RSS feeds within Plone. A new rss_feed content type with a listing block, provided by the backend rss-provider add-on, and the express middleware in volto-rss-provider enable users to share Plone content as RSS feeds. The volto-rss-receiver add-on, which relies on the rss_mixer_data endpoint from the rss-receiver backend, supports efficient retrieval and display of external RSS feeds within Plone. This project simplifies content syndication and broadens the reach of Plone content, enhancing user engagement and accessibility.

At current state of the product, listens on ListenBrainz are collected in the UTC instead of their local timestamp, without taking DST in to consideration. Adding timezone preference for users and adding the time zone field in submitted listens will contribute to the analysis and thus provide better user experience. This project aims to add users’ timezone preference paired with their submitted listens. The main work involves making an appropriate table in Postgres to store timezones, designing a react UI page and implementing the corresponding API endpoints. The stretch goal is to include local timestamp in the API, and extract the timezone information from that timestamp to store in the database. The expected outcome is a finished feature ready to be merged into production code.

The project proposal is to bring password-less authentication to Plone 6 by implementing WebAuthn, a password-less web standard by W3C. The proposal suggests that the implementation should allow the user to decide whether to use WebAuthn as the primary or second-factor authenticator. WebAuthn uses public key cryptography to store user credentials, which makes it more secure than traditional password-based authentication methods. However, the proposal also discusses the challenges of using WebAuthn, such as the Scenario where the authenticator device is not available or lost. The proposed solutions include backup codes, recovery codes, and administrator reset, but all of them require storing some kind of secret on the server, which is a security concern. The proposal suggests alternative solutions like encouraging users to use at least two different Authenticating devices to register.

<p>With the number of sequenced and annotated genomes continuously increasing, there is a need for new algorithms and tools for comparative analyses both at the nucleotide and genic levels. The Genome Context Viewer (GCV) is an OSS tool that enables comparative genomics by using gene families as a unit of search and comparison. It currently uses Chado as a reference implementation for its data services and can be integrated with other GMOD components via a service layer/API. This work will create an extension module that will integrate new and existing pan-genomics algorithms into GCV while leveraging the existing UI for visualization purposes. This will help to serve communities facing the challenges of having multiple reference genomes within a single species, as well as improving GCV’s utility for clade-oriented resources.</p>

Karmada would like to improve the UT coverage of the code to better maintain the quality of the code and reduce the introduction of defects. Increase the UT coverage rate to 50% to 60% (currently, the UT coverage rate is [28.26%](https://app.codecov.io/gh/karmada-io/karmada) ). The entire Karmada repository is a bit large for one project, so we will split it into two projects. The current focus is mainly on `karmada-search`, `karmada-operator`, `karmada-webhook` components. Expected Outcome: - Increase the UT (Unit Test) coverage by more than 25% and add more than 5500 lines of code coverage except for the following directories: pkg/controllers pkg/dependenciesdistributor pkg/descheduler pkg/detector pkg/estimator pkg/scheduler pkg/resourceinterpreter pkg/util

This project aims to extend the existing cBioAbstractor prototype into a schema-driven formatting pipeline that assists curators in transforming heterogeneous supplemental datasets into cBioPortal-compatible formats. Currently, curation is a manual and time-consuming process due to inconsistent file structures, lack of automated schema mapping, and the need to interpret validation errors manually. This results in inefficiencies, variability, and high onboarding effort. My preliminary extension implementation suggests the feasibility of this approach by connecting existing components, introducing fuzzy column normalization, and providing a simple interface for file upload, transformation, and result inspection. Initial qualitative experiments show that the system can reconstruct correct cBioPortal formats from intentionally perturbed datasets, suggesting strong potential for reducing manual work and improving consistency.

<p>WildFly Elytron is a new security framework developed by WildFly to provide a single unified security framework across whole of the application server which replaced the pre existing Java Authentication and Authorization Service (JAAS) which used to be the standard Pluggable Authentication Module (PAM) information security framework. To extend Elytron’s functionality beyond the existing security realms, custom security realms can be implemented using existing Elytron’s APIs and SPIs for their usage in WildFly Elytron subsystem. Now to extend this functionality of custom development to scripting languages other than Java, Java ScriptEngine is used. During the summer as the project of GSoC under JBoss Community, I’ll be working on extending the functionality of WildFly Elytron’s implementation of custom security realms using other scripting languages.</p>

Currently, keeping privacy in mind, Matrix uses seshat to store a searchable database on the user’s device itself. As the number of conversations and messages increase, maintaining an index on the client side becomes tougher. The solution to these problems is a Searchable Symmetric Encryption (SSE) scheme that lets the client safely store an encrypted database on an untrusted server and search through it with full privacy. This project will implement, in particular, the keyword search scheme outlined in a Demertzis et al. paper titled “Fast Searchable Encryption with Tunable Locality”. I will achieve this by creating a Python library that exposes methods to create, update and search on encrypted indices stored in content repositories in a Matrix homeserver. As a part of the project I will be demonstratively integrating the library into an existing Matrix client. Additionally, I will submit results of preliminary performance evaluation.

This project aims to seamlessly integrate all functionalities of the ListenBrainz website's Dashboard into the ListenBrainz iOS app. This integration will enable users not only to view their own dashboard within the app but also to explore the dashboards of other users. This exploration will be implemented using various navigation techniques and state management. Also, this project aims to revamp the feed section of the app and to maintain design consistency with the ListenBrainz website. The dashboard offers a variety of features such as detailed music listening statistics, recent listens, taste, and more, all within a user-friendly and engaging mobile interface. In the implementation, the SwiftUI framework will be utilized to craft an intuitive and visually appealing user interface while Apple's Combine framework will handle asynchronous event management. Additionally, Alamofire library will be employed for networking tasks, ensuring smooth communication between the app and the backend server.

<p>The main goal of this project is to implement a mechanism to be in sync with the latest human data submitted to dbSNP. Once imported, this information can be distributed via EVA implementations of the GA4GH APIs htsget and Beacon specifications, as well as the EVA website.</p> <h6>Acceptance criteria</h6> <p>Given a dbSNP FTP directory with the human variant information, the pipeline should parse JSONs for each chromosome and write the variants from the JSONs to the EVA archive</p> <h6>Needed tasks</h6> <ul> <li>Construct an object model for dbSNP and parse the JSONs to objects in that model</li> <li>Convert the objects in the dbSNP model to the EVA variant object model</li> <li>Construct a variant object by including its component objects from above. Use the Variant writer of variation-commons to write the variants to the EVA archive</li> </ul>

<p>Elytron is an open-source, standalone library made with the purpose to provide a single, unified security solution across the whole Wildfly application server, which earlier was using two separate security solutions, one based on JAAS for application and other based on SASL for management. While developing Elytron the idea was to provide a better and stronger authentication and build something that does more than just unifying the security solution. Intrusion Detection using Elytron is aimed at doing the same i.e. to extend Elytron’s functionality. Intrusion Detection is the art of sensing when a system or network is being used inappropriately or without authorization. Without intrusion detection, an attacker can attempt attacks many times until an attack is finally successful. Intrusion detection allows for these attacks to be identified before a successful attack is likely to occur. The purpose of this project is to implement an Intrusion Detection system that detects suspicious activity or a potential attack and report it to the administrator.</p>

<p>Drools and Java can work together. Java and Minecraft work together. The obvious next step is to get Drools and Minecraft to work together.</p> <p>The plan is as follows:</p> <p>--A Minecraft mod boots up a list of Drools rules. These are either stored in a predetermined directory, or listed in a config file.</p> <p>--Minecraft does it's start-up routines. The user loads a world.</p> <p>--Each tick (world update) (or X ticks, determined by efficiency needs), the mod executes the rules.</p> <p>--The rules call functions in the mod's Drools API. This is where the majority of the work will come in—I'll have to write a largish set of functions for drools to use. The functions will take two shapes: returning boolean values for tests, or acting upon the world.</p> <p>--The mod reacts to the function calls, altering the world...</p> <p>–...which the user then interacts with.</p>

<p>In the last GSoC, kingiw created an initial version of casbin.js. This version has a CASL-like API. He also adds support to go-casbin and node-casbin.</p> <p>However, casbin.js relies on an insufficient way to share permissions between the frontend and backend. The backend needs to send the whole policy definition model to the frontend, which will use node-casbin to check the permission. This method requires a heavy data transfer in between, and has potential security problems.</p> <p>To build a production-ready frontend permission control library, we need to</p> <ul> <li>Design a new data structure to only store one-user permission.</li> <li>Add a full set of API to operate on the data structure.</li> <li>Implement integration with the frontend frameworks like React or Vue.js.</li> <li>Add util function in different implementations of Casbin.</li> </ul>

This project integrates n8n, a no-code workflow automation platform, with OpenVINO Model Server to let users build AI-powered workflows that run on Intel GPUs and NPUs. The core is a custom n8n node package that connects to OVMS - users pick a model, choose a target device, and the node handles inference. The system is deployed through Podman Compose with one command. The primary workflow is a Smart Document Processing Pipeline: it watches a folder for incoming documents, runs text extraction on NPU, classifies and extracts entities using an LLM on GPU, and saves results locally. OpenVINO's AUTO plugin handles device selection automatically based on availability and load. Deliverables: custom n8n node package with GPU/NPU/AUTO device selection, Podman Compose deployment, the document processing pipeline, 2-3 additional workflow templates (RAG chatbot, multimodal content analysis), and documentation with installation guide and tutorials."

<p>ListenBrainz currently only displays the list of listens imported into a user's profile and the basic stats about the artists that a user has listened to. There isn't much a user can do with the recordings/listens imported into their profile. Love, hate and delete are the basic features that can be provided to the users. Love/hate feature will help in perceiving the user's taste in music and hence refine the recommendations that are generated for them. Keeping in mind the decision to migrate to Timescale DB and upon a discussion on IRC <a href=""https://chatlogs.metabrainz.org/brainzbot/metabrainz/2020-03-16/?msg=4550029&amp;page=1"" target="_blank">here</a> it was decided to club the delete a listen feature into the love/hate a recording project. My proposal for this project aims to</p> <ul> <li>Add the 'love/hate a recording' feature</li> <li>Add the 'delete a listen' feature</li> <li>Adding the UI components for the above features and revamping the 'My Listens' page.</li> </ul>

<p>MusicBrainz has client libraries for various programming languages such as C++, Python, Java, Go and more. However, we're still missing out on a proper client library for the Rust programming language. There previously have been attempts on creating such a client library, such as the <a href="https://github.com/leoschwarz/musicbrainz_rust" target="_blank"><code>musicbrainz_rust</code></a> (not being maintained at the moment) and the <a href="https://github.com/oknozor/musicbrainz_rs" target="_blank"><code>musicbrainz_rs</code></a> projects, but none of these attempts entirely wrap around the MusicBrainz Web-API.</p> <p>As a part of GSoC'21, I propose to implement further functionality in <code>musicbrainz_rs</code>, a Rust client library which has proper automated tests and has been carefully documented along with examples. However, it still misses out on covering some important functionality from the Web-API, namely the Search feature and the CoverArt endpoint. There are also further possible improvements that could be made, such as gracefully handling rate-limiting from the MusicBrainz servers by performing auto-retries on failed queries in the library.</p>

The Plones’ Volto user management system is missing several key features, such as the ability to edit existing users and groups in the frontend. This project aims to address these shortcomings by implementing robust and responsive UI techniques to improve the user experience and functionality. To achieve this, the existing user and group management screens will be redesigned using React, and new workflows connecting the frontend and backend will be developed using Python. Edit functionalities will be added across all three screens (User, Group and User Group Membership), ensuring a smooth user experience and minimizing errors. In addition to addressing the missing features, this project also aims to improve the overall appearance and responsiveness of the system. By thoroughly testing all pages and resolving any issues that arise, we can ensure that the final product is both visually appealing and highly functional. Overall, this project represents a significant step forward in Plone's user management capabilities, providing users with a more powerful and streamlined system for managing users and groups.

<p>JSON Schema is a vocabulary to specify the structure of a JSON document. JSON Schema is widely used and well supported and sees a growing use for many GA4GH standard representations and schema collection is growing and currently, there is no mechanism to manage these JSON schemas. As a solution, introducing JSON schema service which has the ability to manage growing JSON schemas and maintains the consistency among GA4GH JSON schemas by introducing a standard template as a meta schema. The proposed system consists of 3 main components such as Schema Service, Schema Repository and Schema UI. Schema service is designed as a REST full web service and mainly it manages GA4GH JSON Sachems. Schema Repository is the persistence layer for Schema Service and JSON schemas can be stored within the schema repository for retrieval. Schema Repository is implemented using a document-oriented database model. Schema UI is a single page web application for the application layer of the system and provide a user interface for JSON Schema management.</p>