[OpenAFS-devel] (no subject)

Michael Meffie mmeffie@sinenomine.net
Sat, 22 Mar 2025 09:28:51 -0400


On Wed, 19 Mar 2025 12:20:31 +0530
Tejas Sonawane <sonawanetejas031@gmail.com> wrote:

> Dear OpenAFS Mentors,
> 
> I hope this message finds you well. My name is Tejas, and I am a MERN stack
> developer with experience in JavaScript, TypeScript, Python, and Java. I
> have a keen interest in system-level development and am enthusiastic about
> contributing to the "Develop a GNOME Shell Extension for OpenAFS" project
> for GSoC 2025.
> 
> To ensure that my proposal aligns with the project's objectives and adheres
> to best practices, I would appreciate your guidance on the following:
> 
>    1.
> 
>    *OpenAFS Client Management:*
>    - Are there specific OpenAFS client operations or configurations that
>       users frequently manage and would benefit from being included in
> the GNOME
>       Shell extension?

The most basic feature is just starting, stopping, and showing the current
running status. Another useful feature is acquiring tokens for authenticated
access, but that means users would need to be confident the extension is
not malicious.

>    2.
> 
>    *Security Considerations:*
>    - Beyond authentication, are there other security aspects or potential
>       vulnerabilities we should be mindful of when developing the extension?

Yes. This would be related to kerberos and GNOME integration I would think.
I dont think GNOME requires extensions to be signed, so that is a challenge.

>    3.
> 
>    *User Experience (UX) Design:*
>    - Are there any particular UX design principles or features that you
>       believe would enhance the usability of the extension for OpenAFS users?

This would be more of a GNOME question I would think.

>    4.
> 
>    *Testing and Compatibility:*
>    - Are there recommended strategies or tools for testing the extension
>       across different Linux distributions and GNOME versions to ensure broad
>       compatibility?

I would assume this would entail virtual machines with different GNOME versions.

>    5.
> 
>    *Community Engagement:*
>    - How can I best engage with the OpenAFS community during the
>       development process to gather feedback and ensure the extension
> meets user
>       needs?

Contributors work directly with the mentors via a combination of email,
chat, and weekly zoom calls.

>    6.
> 
>    *Documentation and Resources:*
>    - Are there specific OpenAFS documentation, APIs, or community resources
>       you recommend I review to gain a deeper understanding of the client
>       operations and integration points relevant to this project?

See the OpenAFS Contributor Guide for an overview. (Link is on www.openafs.org)

> 
> I am committed to developing a tool that enhances the OpenAFS user
> experience within the GNOME environment and aligns with the community's
> needs. Your insights and recommendations will be invaluable in shaping a
> robust project proposal.
> 
> Thank you for your time and support.
> 
> Best regards,
> 
> Tejas

Thank you,
Mike

-- 
Michael Meffie <mmeffie@sinenomine.net>