Explore Projects

Okular, the cross-platform universal document viewer developed by KDE supports PDFs with forms. These forms often use Javascript to make forms more convenient for its users. However, as of today, the support for Javascript within Okular is lacking. A lot of pre-defined javascript form functions are either partially implemented or not implemented. This often breaks form functionality for the users. Also at present, many essential objects and functionalities outlined in the PDF Javascript API Reference specification are either only partially implemented or completely absent. This leads to a lot of bug reports regarding broken form support for Okular. This project aims to resolve this, by improving the Javascript support for PDF forms. For this, the pre-defined Acrobat methods shall be implemented and newer JS objects shall either be added or improved upon during the course of this project. Deliverables : 1. Pre-Defined Acrobat method implementations. i. AFNumber_Keystroke ii. AFSpecial_Keystroke iii. AFMerge_Change iv. AFTime_Keystroke v. AFDate_Format vi. AFDate_Keystroke vii. AFPercent_Format viii. AFPercent_Keystroke 2. Expand the implementation for the event object. 3. Expand the implementation for the field object. 4. Implement the global javascript object. 5. Implement the submit and reset actions.

<p>Enabling kdevelop to use lldb as a debugging backend, which would be especially useful on Max OS X and Windows, where gdb support is rather scarce, and it can also help people that want to switch to lldb on linux by adding decent IDE support.</p>

<p>Comment alter allows changing values of a fields on a node through comments. The module allows selecting any field of the content type to be altered from comments unlike any other contributed modules present in Drupal. It can be used to create a full featured bug tracker, customer support, etc. The modules strives to integrate different modules like core's Node module to store the changes as new revisions and Diff module for displaying the changes made in a particular comment. At present the module is available for Drupal 7 only and thus we have this project to port the module for Drupal 8.</p>

This project enhances SymPy’s Beam, Column, and Structure2D modules in the continuum_mechanics package by addressing key limitations in the current implementations. The work focuses on improving method robustness to handle a wide range of edge cases, adding missing features, and ensuring comprehensive testing across various scenarios. Key improvements include: Beam module: Enhanced input validation, improved error reporting for better user experience, and modifications to existing methods to support more complex and symbolic cases. Column module: Introduction of features such as max_axial_force() and max_extension() methods to support horizontal (axial) force analysis, manual support applicataion using apply_load() and bounadary conditions. Structure2D module: Integration of the Column module into Structure2D, enabling full horizontal and vertical structural analysis, making it more flexible and complete.Adding plots like plot_axial_force(), plot_deflection(), plot_extension().adding plots on the structure for better analysis like plot_shear_force_on_structure(), plot_axial_force_on_structure() and plot_bending_on_structure(). and also a plot to show the deformation of the structure under load applications. These enhancements aim to ensure reliability, clarity, and ease of use for students, engineers, and researchers working with symbolic structural mechanics problems in SymPy.

The app is currently limited to displaying a single list of basic numeracy topics. Together, these topics comprise what we call a 'classroom'. With this proposal, my aim is to introduce support for more than just mathematics topics by revising the core home screen & navigation flows to support topics grouped by their classroom. Future classrooms will include science, financial literacy, and more.

<p>Terasology is designed to be a modular voxel engine but as said: “with great power comes great responsibility”. Keeping track of all the modules can be tough. The idea of the proposal is to provide an automation system that aggregates all the modules and display their information on a generated website. Provide a way for the user to download, list dependencies. With a stretch-goal of improving the UX of the website along with speed and accessibility.</p>

<p>The Authentication server of the litmus portal (which resides in the <code>litmus-portal</code> folder of the main litmus repository) is written in golang, uses certain outdated dependencies (such as mgo), and currently does not support third-party OAuth authentication modules such as:</p> <ul> <li>Google Authentication</li> <li>GitHub Authentication</li> <li>Local Authentication</li> </ul> <p>The current implementation of the authentication server also consumes more resources than the litmus portal’s GraphQL server.</p> <p>This proposal shall focus on re-writing the Authentication Module of the litmus-portal so that it achieves the following:</p> <ul> <li>The Authentication Module is Independent (Can be moved to a separate repository)</li> <li>The Module is light-weight and makes use of actively maintained dependencies (if any)</li> <li>The Authentication Server is robust and flexible to any future addition of features</li> <li>The Authentication Server supports OAuth authentication such as Google Auth and GitHub Auth</li> </ul>

GitLab uses Gitaly to read and write git data to the repositories. Gitaly provides RPC access to the git repositories. The RPCs that provide the author and the committer information make use of the git-cat-file command, which doesn’t support mailmap. So, this project aims to add mailmap support in git-cat-file command, make Gitaly to use it and thus enable GitLab to honor the .mailmap file across its various features.

This proposal aims to improve observability for Kerberos- and certificate-based authentication workflows in Metasploit. At present, operators often need to interrupt module execution, export authentication artifacts such as .ccache, .kirbi, .pem, or .pfx, and analyze them with external tools in order to understand failures, inspect identities, or validate exploitation steps. This project introduces two opt-in tracing facilities, KerberosTicketTrace and CertificateTrace, together with a reusable X.509 inspection backend to surface protocol and artifact metadata during module execution without changing default Metasploit behavior.

<p>This project will convert some pre-trained Keras models into TensorFlow js models and explains how they can be made accessible by packing them in npm packages. Additionally, a model that is mobile-ready will be created and trained for skin cancer prediction. This model will then be made available over an npm package for other developers to use it in their applications. Furthermore, the neural style transfer will be implemented in TensorFlow js to enable a completely client-side based style transfer. This is interesting for privacy aspects because the image will only be processed locally and not uploaded to a server.</p>

The project aims to enhance the metadata support in sunpy-soar, enabling better searching and filtering of solar data in the Solar Orbiter Archive (SOAR). Currently, sunpy-soar offers only basic metadata, such as SOOP name, time, and level. However, there is a wealth of additional data in SOAR that is not yet accessible through sunpy-soar. To address this, we propose adding support for various tables in SOAR, such as v_<ll/sc>data_item, v<ll/sc>repository_file, and v<instrument>_<ll/sc>_fits. These tables contain valuable metadata like filenames, filesize, sensors, and instrument-specific data. By implementing these tables, users will be able to access a broader range of metadata in sunpy-soar. Additionally, we plan to enable querying multiple tables simultaneously to retrieve more comprehensive metadata. This involves updating the sunpy-soar/client module to support constructing queries with metadata from different tables. We will also refine the sunpy-soar/attrs module to handle new metadata attributes efficiently. Overall, the deliverables encompass the entire process of updating and enhancing metadata support in sunpy-soar, from implementation to documentation, ensuring that users can effectively utilize the improved functionality for solar data exploration.

The objective of the project is to add support for STAC(SpatioTemporal Asset Catalog) to istSOS. The STAC specification is an open specification developed to improve the discovery, accessibility, and interoperability of geospatial datasets. STAC provides a common, interoperable metadata framework to expose geospatial assets, like satellite images either of optical or SAR, or other spatiotemporal data. STAC allows ease of access to different format of spatial data through a common way to find more information about the geographic location over a period of time. Expected outcome of the project is adding support for STAC based metadata generation and serving through api server.

<h3>The Problem</h3> <p>All IDE/Quality Systems plugins, build tools need to use Checkstyle module metadata for their functioning. But as of now they have to maintain their own metadata which becomes time consuming and the onboarding process of a new third party application becomes cumbersome.</p> <h3>The Solution</h3> <p>If we could build and maintain universal internal metadata for all modules which IDE/Quality Systems plugins and build tools could use, it would be very useful and maintain uniform configurations across all partner applications. It would solve 3 major problems viz; Ease of Eclipse and Sonar Plugin Development, Third Party Application Integration and Automated Site Generation</p>

<p>PostgreSQL is an object-relational database management system (ORDBMS), unlike MySQL which is a Relational Database Management System(RDBMS). It is easy to setup and install and offers support for both SQL and NoSQL. While there are pros and cons of both of these database management systems, it ultimately boils down to your requirements.</p> <h3>Why use PostgreSQL for OpenMRS?</h3> <p>As stated in the project description there are a large number of implementations who would like using PostgreSQL instead of MySQL. There is also another category who have already invested in PostgreSQL servers, where requiring them to install and learn another type of database server would not only be an unnecessary waste of their time, but also a wastage of computer resource.</p> <h3>Thus, this project aims to add PostgreSQL to the list of databases that OpenMRS supports.</h3>

<p>PyTorch-Ignite is a great library built on top of pytorch. It provides an extremely simple engine and event system to work with, which work really well in a distributed environment. It also has a set of very handy metrics which can be used right out of the box. This is why I would like to become a contributor for the PyTorch-Ignite library. I wish to work on the metrics module because I have worked in Brain-Computer Interface, Computer Vision, Augmented Reality and am familiar with a myriad of different metrics. I am also familiar with using pytorch library and have built, trained and tested many models with it, making me a suitable candidate to work on the metrics module of PyTorch-Ignite. Contributing to PyTorch-Ignite can help me learn more about using pytorch in a distributed environment, writing test cases for your code, get used to the GitHub workflow in general.</p>

Kdenlive is a cross platform, open source, video editing software. Currently, Kdenlive saves its subtitles in the SRT format, which only allows very basic styling features - that means only one style for the complete subtitle file. A more advanced file format like ASS (SubStation Alpha Subtitles) would allow much more powerful styling, for example attributing different styles to different speakers, proper styling (using bold, italic or colors on words or sentences only), etc. Currently, Kdenlive can already read basic ASS files (without styling support). I'll improve Kdenlive's support for ASS files. Expecting results include opening and saving an ASS subtitle and keeping the styling infos, implementing a widget allowing to create styles and attribute a style to a subtitle sentence, and adding some attributes like bold to selected parts of the text.

Nominatim currently classifies places using a single OSM class/type pair, which causes duplicate database entries for multi-tagged objects, fragile handling of administrative boundaries, and insufficient granularity for modern search queries. This project adds native category support to Nominatim's PostgreSQL backend by introducing a categories column across the place, placex, and search_name tables using PostgreSQL's ltree[] type for hierarchical querying. Categories are assigned in the Lua import scripts following Photon's osm.<class>.<type> approach, replacing the place_classtype_* tables currently used for POI filtering. Deliverables include: schema changes with migration support for existing installations, Lua-based category assignment, replacement of classtype table lookups with category-based queries in search_name, and as stretch goals, API include/exclude filtering parameters and a flexible YAML-driven CategoryGenerator for enriched categories like cuisine.italian or access.wheelchair.yes.

The project focuses on writing a Python library for GRASS GIS that utilizes EODAG API. Currently, GRASS uses different APIs for each satellite data provider. As a result, a lot of maintenance has to be done to keep up with the changes happening to all the different APIs. Thus, adding EODAG support to GRASS GIS will provide a lot of flexibility in the future development of GRASS, by decreasing the amount of maintenance needed to keep up with all the different APIs updated, and instead maintain the support for EODAG library. Deliverables for this proposal are supporting Sentinel, Landsat, and MODIS datasets with EODAG, and reimplementation of both i.sentinel.download and i.landsat.download modules with the new GRASS EODAG library.

<p>The javascript code is written in ES5 exposing many of the variables and functions globally and the package manager is not used for the modules. So I will work on implementing package manager for modules like jQuery, jQplot etc which are being used in phpMyAdmin, transforming ES5 code to ES6 which has new features block scoped variable defining, classes and dynamic import-export, babel compiler for compiling ES6 code to ES5 which browsers support. The functions will also be converted into modules which makes it easier to import the required function only. This will help in making the functions unit testable. I will also implement webpack which will bundle the static JavaScript files and also minify them, which can be loaded as scripts.</p>

<p>This project aims to provide an R interface to Ideogram.js, integrate it with bioconductor infrastructures and possibly provide an interactive whole-genome exploring tool combining with other visualization components.</p> <p>Ideogram.js is a JavaScript library for chromosome visualization. It can be used for interactive visualization of chromosomes of different species, showing cytobands, showing annotations along the chromosomes, showing position mapping (e.g. homology) between different chromosomes, etc.</p> <p>There is already a simple R interface to the Ideogram.js library at freestatman/ideogRam as a proof of concept. The main purpose of this project is to improve this interface and integrate it with bioconductor infrastructures (e.g. to support S4 classes like GRanges as annotation data).</p> <p>Moreover, the most important feature that the package may provide for static visualization is the ability to combine with other visualization packages to interactively exploring the whole genome.</p>

Computers with ARM architecture are prevalent but GNU Boot currently doesn't support them. My focus has also shifted from the classic x86_64 laptops compatible with fully free BIOS to newer armv7 and beyond to armv8 computers. The defunct fully free Libreboot has supported a few Chromebooks that didn't require blobs to boot, thanks to efforts of contributors such as PaulK. I checked with him for basic guidance and I'm in need of a mentor from the GNU Boot project under the GNU umbrella (as GSoC 2026 approved organization). Having GNU Boot support ARM computers would play well into the efforts of fully free GNU/Linux-libre distributions such as Trisquel to complete freedom-respecting ARM laptops. My work will involve updating the previous code in Libreboot and (PaulK's fork libettereboot) for the Chromebook C201 and C100 laptops and porting GNU Boot to newer ARM targets found in coreboot. Since I'm a Embedded Systems Master's student, Google Summer of Code seems to be the perfect opportunity to extend the GNU Boot contributor team while providing basic funding for taking GNU Boot to the next architecture.

<p>p5.js, and Processing in general, have been revolutionary tools in the world of creative coding. For visual artists, there are few programmatic tools which come close to the usability of Processing. The birth of p5.js has opened up yet another dimension, and the p5.js-sound library paves the way to even more possibilities. However, while p5.js-sound offers many powerful features through integration with Web Audio, it is not yet an intuitive tool for the general p5.js audience.</p> <p>The goal of this project is to plug this hole, through the introduction of new features, accessible examples and tutorials that empower all users to create musical projects on p5.js-sound, with a particular focus on support for algorithmic composition tasks.</p>

<p>Brief Explanation</p> <p>Qt is an open source cross platform framework facilitating GUI applications development, for mobile, desktop and embedded devices. Although the framework is written in C++, it brings with it a meta-language (or modelling language), QML. To accelerate UI development, QML provides the Qt Quick Controls module with ready made widget types, each supported by a C++ class, like Button or Switch, ready to be styled and modified at our project needs. The module is currently on version 2.4 but there is no support for Calendar in the latest version, to be more specific, the Calendar was lastly provided in version 1.4 of the Qt Quick Controls module that was released with the Qt 5.3 version.</p> <p>Expected Results</p> <p>The Qt Calendar widget is updated, modified accordingly and ported into Qt 5.12 and Qt Quick Controls 2 current version following the QtQC2 module standards and supporting all features like styling. The Calendar, ideally would have a Template type where from properties like background and/or contentItem can be set for style customisation &amp; switching support. Also, it should be possible to be instantiated as a standalone QML type and be styled locally for regular usage.</p>