Rust Foundation Request

# Rust Foundation Request - Rust Foundation Fellowship Application Form ---- - Please tell the name by which you choose to be known. * - What are your pronouns? - What is your email address? - Please provide a link to your GitHub account. - Please provide links to personal website/public social media handles/LinkedIn (as appropriate) * --- - Where are you based? - What is your primary language of communication? - What languages do you speak? --- Your experiences and proposed work Please provide some background about yourself and your experience with Rust. For example: - How long you have been involved with Rust: - I have been working with Rust for over 4 years, but it was only in the past year that I fully immersed myself in Rust and became exclusively focused on it. My interest in compiler work stems from my master's studies in Type Theory at the University of Pisa. - Details of any teams/working groups you may be a member of (where applicable) - In the last year, I have been involved in the async working group, and I had the opportunity to work with a few people involved in the compiler, such as @eholk, who served as one of my first mentors within the async working group. - Through my contributions, I have been included as a team member in the async-wg. You can find the confirmation in this pull request: [rust-lang/team#991](https://github.com/rust-lang/team/pull/991). - I am also interested in a neglected area of the compiler, which is macros. In fact, I am currently working on an MCP (Minimal Compiler Change Proposal) to initiate a macros-wg within the compiler team. The MCP can be found here: [rust-lang/compiler-team#637](https://github.com/rust-lang/compiler-team/issues/637). - Links to example pull requests you have submitted (where applicable) - https://github.com/rust-lang/rust/pull/103029 - https://github.com/rust-lang/rust/pull/107902 - https://github.com/rust-lang/rust/pull/103902 - https://github.com/rust-lang/rust/pull/100817 - more here https://github.com/rust-lang/rust/pulls?q=is%3Apr+author%3Avincenzopalazzo+is%3Aclosed - Links to examples of code reviews you have carried out (where applicable): - [Code Review: Rust PR #111071](https://github.com/rust-lang/rust/pull/111071) - Additionally, I co-lead the triage meeting with the async working group, where I revive forgotten issues and provide solutions. For instance, you can find an example in [this comment](https://github.com/rust-lang/rust/issues/74497#issuecomment-1534485733). - I am also developing tools to generate useful agendas for other working groups. You can find an example of this work in [my GitHub repository](https://github.com/vincenzopalazzo/penguin). - Any Rust-related materials/public writing you have done (where applicable): - I delivered a talk on async runtime, which you can find [here](https://pisadev-write-async-runtime-rust.vercel.app/). - I have also written a blog post on writing an async runtime, available [here](https://blog.hedwing.dev/async-rust/rio/write_runtime/). - Furthermore, I made an announcement about an experimental runtime on my blog, which can be found [here](https://blog.hedwing.dev/async-rust/rio/). - Details of any Rust-related events you have been involved with (where applicable) - I am working with the async-wg and the people that are interested in macros-wg to make a in person meeting in the next rust conf in US in September. In this way we can have a sync chat for the problem that we had and take some decision on how to move forwards. - Details of how you participate in the Rust community (virtually or in person) --- - If you are interested in applying for a mentored Fellowships, please select the ones you are interested in from the below list. You can choose more than one should you want want to. - Please tell us about how you propose supporting the Rust project during your Fellowship year and what the benefit of your work will be for the Rust project and the wider community of users - I am interested in becoming a fellow of the Rust compiler team. I strongly believe that in open source projects, it is challenging to mentor new people and groom them as future maintainers. This is especially true in the Rust compiler ecosystem, where there is a lack of available experts who can guide and teach newcomers. This gap is particularly evident in the macros subsystem. Currently, there is a shortage of experts with sufficient time to mentor others and contribute to the macros subsystem. This shortage is reflected in the absence of alternative libraries like `quote` or `syn`. It is crucial to mentor individuals in projects like Rust because being a maintainer is a demanding role, and it is essential to have a plan in place to handle potential turnover. In summary, my motivation to be a fellow for the Rust compiler lies in the opportunity to learn from experienced individuals and potentially become a future maintainer of one of the subsystems.