[OpenAFS-devel] [GSoC] Introduction and first patch - Maria-Alexandra Minca

Michael Meffie mmeffie@sinenomine.net
Mon, 23 Mar 2026 18:09:28 -0400


On Sun, 15 Mar 2026 03:46:12 +0200
Alexandra Minca <alexandraminca30@gmail.com> wrote:

> Hello,
> 
> My name is Maria-Alexandra Mincă and I am a second-year student at the
> Faculty of
> Automatic Control and Computer Science, Department of Systems Engineering,
> the
> Polytechnic University of Bucharest, România. I am very interested in
> contributing to OpenAFS as part of this year's Google Summer of Code.

Hello and Welcome!

> To get started, I have already submitted a small patch on Gerrit which
> fixes several pointer type warnings related to afs_int32/afs_uint32
> mismatches that I noticed during my first build of the project. You can
> find the patch here: https://gerrit.openafs.org/#/c/16723/

Thank you for pointing this issue out. Yes, this area of code could use
some attention.  As mentioned in Gerrit for that change, in general, we 
try not to force fit using typecasts, as that can mask the underlying issues.
The underlying issue here is the backup system is still using 32-bit times,
and is mixing signed and unsigned 32 bit values. Converting all those
to 64-bit time is a much bigger change!  For 16723, perhaps we can just
fix the signed-ness warnings for now.

> I am currently doing some research and trying to decide between three
> project ideas that have really caught my interest. I would like to ask what
> is the preferred way of communication, via this mailing list or on the IRC
> chat?

For myself, email is probably more preferred.

> Also, are there any other tasks you would recommend for a newcomer that
> could help me gain a better understanding of the project?

Generally, it is good if you are able to build the project, and if you can
install the client and servers on a virtual machine.  That is normally the
route newcomers take to gain a better understanding.  The learning curve
can be steep since there are a number of components to get setup, including
Kerberos, but we can be here to help, and help improve the documentation.

Best regards,
Mike 


-- 
Michael Meffie <mmeffie@sinenomine.net>