Re: [Outreachy] Move existing tests to a unit testing framework
- From
Luma <ach.lumap@gmail.com>
- Date
- Oct 9, 2023, 09:15 UTC
- Message-ID
- <CAFR+8Dz717pcc2Lm_J29xxiBt-kUrMP4JAUbm=3XaJuJPYseHg@mail.gmail.com>
- In-Reply-To
- <CAFR+8DyN8vbuvdgZPkSVqS2=sqconwhx3QfcpJ0+Wi_oCA=s0w@mail.gmail.com>
Dear Git Community and Mentors,
I hope this email finds you well. My name is Achu Luma, and I am excited to submit my application for the Outreachy program with the Git project. I have been a passionate open-source enthusiast and a dedicated Git user for two years, and I am thrilled at the opportunity to contribute to the Git community.
Introduction: ---------------- I study Computer Science from the University of Bamenda. Over the past 4 years, I have gained experience in software development and have participated in various class projects.
Why I am a Good Fit: ---------------------- 1. Proficient with Git: I have a good understanding of Git's version control system and have successfully used it in both personal and educational projects.
2. Strong Programming Skills: My programming skills in python, C etc and experience with git, shell etc make me well-prepared to contribute to Git's codebase.
3. Open Source Involvement: I have actively contributed to git open-source project, including https://public-inbox.org/git/20231003174853.1732-1-ach.lumap@gmail.com/T/#t , where I have submitted a patch that has been well-received.
Project Idea - Moving Existing Tests to a Unit Testing Framework: ------------------------------------------------------------------ I am excited about "Moving Existing Tests to a Unit Testing Framework". The objective of this project is to enhance the efficiency and maintainability of Git's testing infrastructure by porting existing unit tests to a unit testing framework.
**Project Plan**: - Evaluate the existing tests in the `t/helper/` directory to identify those suitable for migration to the unit testing framework. - Develop a migration strategy and create detailed plans for adapting these tests. - Port the identified tests to the unit testing framework while ensuring they maintain their functionality. - Verify the correctness and reliability of the migrated tests through thorough testing and validation. - Collaborate with the Git community to gather feedback and make necessary adjustments.
**Timeline**: - Community Bonding (Oct 2 - Nov 20): Familiarize myself with the Git project and establish communication channels. - Coding Phase (Dec 4 - Jan 15): Implement the migration of tests and seek feedback from mentors and the community. - Testing and Validation (Jan 15 - Feb 15): Rigorously test the migrated tests and make improvements based on feedback. - Documentation and Finalization (Feb 15 - March 1): Document the migration process and finalize the project.
**Contribution to Git Community**: I have actively participated in Git's mailing-list discussions and submitted a patch( https://public-inbox.org/git/20231003174853.1732-1-ach.lumap@gmail.com/T/#t) for review. I have received positive feedback on my contributions, and it has been queued to be merged into official Git branches maintained by Junio. Additionally, I have been involved in discussions related to the git project.(https://public-inbox.org/git/CAFR+8DyN8vbuvdgZPkSVqS2=sqconwhx3QfcpJ0+Wi_oCA=s0w@mail.gmail.com/T/#t)
**Proposal Drafts**: I have shared drafts of this proposal on the Git mailing list git@vger.kernel.org and will incorporate valuable feedback provided by the community.
**Next Steps**: I am eager to discuss my proposal further and collaborate with the Git community to ensure the success of this project. I will continue to engage with the community, seek guidance, and refine my proposal as per your suggestions.
Thank you for considering my application. I look forward to the opportunity to contribute to the Git project and help make it even more robust and reliable.
Best Regards,
On Wed, Oct 4, 2023 at 12:36 AM Luma <ach.lumap@gmail.com> wrote:
Show 53 quoted lines
> > oh yes, "Move existing tests to a unit testing framework" was the > only listed project for this current Outreachy cohort. So, I used it > to express my intent. > I appreciate the clarification on authorship identity for patches. I > will update subsequent patches with a legal full name to conform to > the community rules. > > Regards. > > On Tue, Oct 3, 2023 at 7:51 PM Junio C Hamano <gitster@pobox.com> wrote: > > > > Luma <ach.lumap@gmail.com> writes: > > > > > Hi; > > > My name is Luma, and I wanted to take a moment to introduce myself > > > and share some > > > insights on an essential aspect of avoiding pipes in git related > > > commands in test scripts. > > > > > > I am an outreachy applicant for the December 2023 cohort and look > > > forward to learning from you. > > > > I notice that the title of the message and the immediate topic you > > discuss in the body of the message do not match. I presume that the > > topic on the title is what you prefer to work on if the unit testing > > framework is ready by the time Outreachy program starts, and the > > mention about "do not clobber exit code of Git with pipes in the > > tests" is your "dip the tip of a toe in water" microproject? > > > > Welcome to the Git development community. > > > > Do you have a single word name? If so please disregard the below, > > but in case "Luma" is just a nickname (e.g. like I am introducing > > myself to my Git friends "Hi, I am Gitster!") you use online, please > > read on. > > > > For signing off your patches, we'd prefer to see your real name > > used, as Signed-off-by: is meant to have legal significance. And > > because we also expect the authorship identity to match the > > name/e-mail of the sign-off, it would mean your patch submissions > > are expected to look like: > > > > From: Luma <ach.lumap@gmail.com> > > Subject: ... title of the patch goes here ... > > > > ... body of the proposed commit log message goes here... > > > > Signed-off-by: Luma <ach.lumap@gmail.com> > > > > but "Luma" replaced with your full real name. > > > > Thanks.