[OpenAFS-devel] Interest in Contributing to OpenAFS CLI JSON Output – GSoC 2025

[Michael Meffie]

On Sun, 23 Mar 2025 04:18:42 +0530
Mrunal Mehar <mrunalmehar863@gmail.com> wrote:

> Dear OpenAFS Development Team,
> 
> I hope this email finds you well. I am a B.Tech student at SPPU University,
> Pune, India, eager to contribute to OpenAFS through GSoC 2025. I am
> strongly interested in distributed file systems and have worked on projects
> involving command-line tool development, JSON processing, and automation.
> 
> I designed an offline parallel antivirus pipeline leveraging C programming,
> distributed processing, and automated scanning workflows, gaining deep
> expertise in scalable system design, structured data handling, and
> automation. Additionally, I developed a GIS-based web application using
> PostgreSQL and PostGIS, refining my skills in JSON data parsing, efficient
> data processing, and CLI-based tool development. Through these projects, I
> have built a strong foundation in scripting, automation concepts, and
> command-line interface (CLI) design principles, making my skill set highly
> aligned with OpenAFS’s technical requirements and objectives.
> 
> Leveraging my expertise in C, JSON processing, and scripting, I am excited
> to contribute to the "Enhance OpenAFS Command-Line Tools with JSON Output"
> project. By integrating structured JSON output, this enhancement will
> streamline automation, improve interoperability, and simplify integration,
> making OpenAFS more adaptable and efficient for modern workflows.
> 
> I would appreciate your guidance on:

Hello,

Thank you for your interest in OpenAFS.

> 1. Gaining a deeper understanding of OpenAFS’s CLI architecture and best
> practices for integrating JSON output.

The OpenAFS command line tools use a small internal library called libcmd
to process command line argument. You could start by seeing how the
arguments are processed.

> 2. Relevant discussions, design references, or documentation that outline
> existing considerations for this enhancement.
> 
> 3. Identifying suitable entry points in the codebase, including
> beginner-friendly issues to explore.

I recommend starting by reading the "Contributor Guide" (see links
on www.openafs.org).

> I look forward to contributing and learning from the OpenAFS community.
> Thank you for your time.
> 
> Best regards,
> Mrunal Mehar
> mrunalmehar863@gmail.com
> GitHub: github.com/mrunalx863  <http://github.com/mrunalx863>

Thank you,
Mike


-- 
Michael Meffie <mmeffie@sinenomine.net>