Challenger #1-Sankhadip Das

[sankhadip10]

name: Sankhadip Das github_user_name: sankhadip10 discord_id: SAnkhaDip#4293

[sankhadip10]

Fork link:-https://github.com/sankhadip10/scaler-open-source-september-challenge

[sankhadip10]

Third challenge

[sankhadip10]

Fourth day challenge

[sankhadip10]

Fifth Day challenge

[sankhadip10]

Six th day challenge

[sankhadip10]

7th day

[sankhadip10]

8th Day

[sankhadip10]

9th day

[sankhadip10]

10th day

[sankhadip10]

11th day

[sankhadip10]

12th Task

[sankhadip10]

13th day Task

[sankhadip10]

14th day Task

[sankhadip10]

15th day Task

[sankhadip10]

16th day

[sankhadip10]

17th day I didn't got any conflict on PR

[sankhadip10]

18th day

[sankhadip10]

19th day

[sankhadip10]

20th day

[sankhadip10]

21st

[sankhadip10]

22nd

[sankhadip10]

23rd

[sankhadip10]

24th day

Open Source Contribution Best Practices:

1. Issue Creation:

• Clear Title: The title should be concise and clear, providing a general idea of the issue.
• Detailed Description: Elaborate on the problem. Include screenshots, error logs, or any relevant information to help maintainers understand the issue.
• Steps to Reproduce: Always provide steps that lead to the said issue, so that maintainers can replicate and verify the problem.
• Expected vs. Actual Behavior: Describe what you expected to happen and what actually happened.
• Environment Details: Provide information about the operating system, software version, and other relevant details.
• Label Appropriately: If possible, categorize the issue using appropriate labels (e.g., bug, enhancement, etc.)
• Check for Duplicates: Before submitting an issue, ensure that the same issue hasn't been reported already.

2. Git Branch Naming Conventions:

• Consistent Naming: Stick to a naming convention that the project follows or, if there isn't one, adopt a universally accepted one.
• Categorization: Use categories like feature/, bugfix/, hotfix/, or release/ to indicate the purpose of the branch.
• Descriptive: The branch name should be descriptive enough to identify its purpose. E.g., feature/user-authentication.
• Use Hyphens: Use hyphens to separate words instead of spaces or underscores.
• Short and Meaningful: Avoid overly long branch names; keep them succinct but meaningful.

3. Pull Request (PR) Creation:

• Clear Title: Similar to issues, PR titles should be clear and concise. If it's related to an open issue, you can mention the issue number.
• Detailed Description: Describe the changes you've made, the reason behind them, and the impact they'll have.
• Reference Related Issues: If the PR is related to any existing issues, make sure to reference them.
• Small and Focused: PRs should address a single concern. Avoid mixing multiple features or fixes in one PR.
• Include Tests: If possible, include tests that verify your changes.
• Update Documentation: If your changes include new features, updates, or deprecations, update the corresponding documentation.
• Follow Project's Code Style: Ensure that your code adheres to the style guide or linting rules of the project.
• Interactive Review: Be responsive to feedback from maintainers or other contributors. Engage in discussions and be open to making necessary changes.

4. General Practices:

• Stay Updated: Regularly fetch and pull the latest changes from the upstream before starting your work to avoid merge conflicts.
• Commit Messages: Write clear and meaningful commit messages. A general rule is to write commit messages in the present tense.
• Active Participation: Engage in discussions, review other people's PRs, and provide constructive feedback.
• Respect the Code of Conduct: Adhere to the community's code of conduct, if provided. Open source contributions should be respectful and inclusive.

[sankhadip10]

25th day Explored various repositories. Started conversation on this https://github.com/sankhadip10/ward Forked the repository,installed the dependency,understanding the codesbase

[sankhadip10]

26th Still looking for issues The issues that I found in the previous is already solved. Looking for other projects

[sankhadip10]

27th day

[sankhadip10]

28th day Exploring the open source project --continue

[sankhadip10]

29th day Task Readme updated for the Github profile https://github.com/sankhadip10

[sankhadip10]

30th Day As the 30th day of the Open Source September challenge draws to a close, I find myself reflecting on the journey I've undertaken this past month. The initiation into the world of open source, especially through platforms like Git and GitHub, was both enlightening and somewhat overwhelming. The intricate details, commands, and processes of Git seemed daunting initially. However, the challenge ensured a structured and methodical learning path.

Every day brought with it new lessons, insights, and experiences. The plethora of resources shared, from comprehensive links to insightful videos, paved the way for a deeper understanding of open source's essence. These knowlegable insights didn't just introduce me to the technicalities but also instilled in me the ethos of open source—collaboration, sharing, and community-building.

Starting from a place of curiosity and, admittedly, a fair amount of apprehension on September 1st, I now find myself on the 30th, little more confident, knowledgeable, and enthusiastic. I've not only grasped the mechanics behind Git and GitHub but have also embraced the spirit of open-source contribution.

Thank you, Shiva for curating this challenge.