ritukumari98 / imgin Goto Github PK

Hello @RituKumari98
I want to Add
[Home],[Features],[About],[Contact]
(Under GSSoC'24)
I recently made this page

Hey,
I want to make contributions for this website. I need more information about this website to get a basic idea of it, kindly elaborate.

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

RIght now CONTRIBUITING.md file is missing in our repository , @RituKumari98 mam Assign this issue to me , I will add it. Thankyou

currently our Readme.md File looking not so good It can be more fascinating with some 3d images along with contributors , code of conduct section etc. @RituKumari98 assign this issue to me I will create it . Thankyou

👋 Hi @RituKumari98,

I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

• #4
• #7
• #9
• #10
• #13

This feature aims to address the problem of delayed and inconsistent communication following the creation of issues. By automatically commenting on issues as soon as they are created, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

a different color header we can change to.

@RituKumari98
Hello Ritu, I want to contribute on this project under gssoc
kindly elaborate

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

To enhance our communication and acknowledgment process, we're implementing an auto-commenting feature for specific events within our project repository. This feature will automatically generate comments under the following circumstances:
PR Merged: Upon the successful merging of a pull request (PR), an auto-comment will be added to the corresponding issue, indicating that the PR has been merged and expressing gratitude to the contributor for their valuable contribution.

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

Should mention the guidelines of the steps to Contribute i.e. how to make pull request and git command

Didn't find steps to contribute

I want to work on this Readme issue
Please assign me this issue

I am working under GSSOC'24

Plz give tags:-

• GSSOC'24
• Level 1

I am working on it assign it to me so that I can contribute

Hello,
@RituKumari98
I believe I can create the following elements:-
Elements like a search bar, Search Criteria, Search Button, Image Display Area, Loading Indicator, Navigation menu, and Footer.

These elements collectively create a user-friendly and efficient UI for an image scraping tool, providing users with the necessary functionalities to search, browse, and manage scraped images effectively.

Please assign it under GSSOC'24! Looking forward to collaborating on the project!

Regards,
Sanjana

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to your

Please add the project, as everyone is adding their own, which is causing conflicts on the project.

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug

Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to your

Hii @RituKumari98

I would like to add components of Home, Features, About, Contacts to your website.
Could you please assign this task to me under gssoc2024

I have designed a lot of UI for my projects and I can provide you a great UI for the Website if you want

If you assign I will do it. Kindly Just assign me and add the labels of GSSOC and level to it so that I can work upon it.

In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. 👍

The README file on GitHub is crucial for providing a comprehensive guide to users and collaborators interacting with a repository. Serving as an introduction to the project, it outlines its purpose, installation instructions, usage examples, and essential documentation, ensuring clarity on how to interact with the project effectively. Additionally, it establishes guidelines for contribution, fosters community engagement, and ensures legal compliance through licensing information. Moreover, it offers transparency regarding the project's status and future plans, facilitating effective collaboration and adoption within the GitHub community and beyond. Through its documentation, the README empowers users to understand, utilize, and contribute to the project, ultimately driving its success and impact.

Hello @RituKumari98
If adding pricing feature where user become premium member, Also you can earn money
(GSSoC'24)

Implement responsive design techniques, such as fluid layouts and media queries, to ensure optimal display and usability across various devices and screen sizes, enhancing the user experience.

Currently, the repository lacks a Code of Conduct file, which is an essential component for fostering a healthy and inclusive open-source community. A Code of Conduct serves as a guideline for expected behavior, ensuring that contributors and participants feel safe, respected, and valued within our community space.

Kindly assign me this issue, so i can work towards it under GSSOC 24

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

Favicon is missing
@RituKumari98 assign this issue to me I will add it . Thankyou
I am working under gssoc24

Hii @RituKumari98

The logo and the UI of the front Page is not overall interactive
As a User, I wouldn't like the UI of it
If you assign me the task of developing the UI of the imgIN under Gssoc2024

I can provide you with a cool, Interactive and user-friendly UI for the imgIN

kindly Assign me this task under gssoc2024 and add label of gssoc and level

Please assign this project to me

design efficient algorithms for image scraping, considering factors such as data volume, network latency, and resource utilization, to ensure scalability and performance.

In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. 👍

I would like to work on this issue.
Can u assign me

A Responsive website page.

I would like to add a pull request template for this repository. I believe that having a standardized template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review and merge pull requests.

Could you please assign this issue to me under GSSOC'24.

HTML Structure:

1. Navigation Bar (nav):

   • Centered horizontally.
   • Contains navigation links such as Home, About, Services, Contact, etc.

2. Search Bar and Button (div):

   • Centered horizontally.
   • Contains an input field for entering search queries.
   • Positioned adjacent to a search button for submitting the search query.

3. Footer (footer):

   • Positioned at the bottom of the page.
   • Contains copyright information or any other relevant content.

CSS Styling:

1. General Styles:

   • Sets the default font and removes any default margins from the body.

2. Navigation Bar Styles:

   • Centers the navigation links horizontally.
   • Sets the background color, text color, and spacing for the navigation bar.

3. Search Bar and Button Styles:

   • Centers the search container horizontally.
   • Styles the input field with padding, border, and border-radius.
   • Styles the search button with background color, padding, and border-radius.
   • Aligns the search button adjacent to the input field.

4. Footer Styles:

   • Positions the footer at the bottom of the page.
   • Sets the background color, text color, and padding for the footer.

-To create a Landing page with both the options and then lead the users to different pages, i.e login and signin pages. based on their response.

• To create separate and login and user pages for the users to avail this facility.

@RituKumari98 mam , I will add footer section with proper styling and copyright .
please Assign this issue to me . Thankyou

I am working under Gssoc24

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

*Hey s for the project I wanna work on this

Creating a navbar

• with image
• and links

Also making it responsive for various screen

Please assign me this issue I wanna work on it

Under Gssoc'24

This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs. By automatically commenting on PRs as soon as they are raised, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

As instructed I want to create a search box with generate button at the center of the page

Please assign me this task under GSSOC'24

I will add google authentication feature once the login/signup pages are ready
@RituKumari98 assign this issue to me
I am workiing under gssoc24. Thankyou

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

Presently the copyright year is not dynamic in nature , it is created using direct html code will display the year texted in the html code ,

But using javascript we can make it dynamic in nature and it will display current year .

@RituKumari98 mam assign this issue to me I will fix this bug . Thankyou
I am working under gssoc24

CODE_OF_CONDUCT.md file is missing in our repository @RituKumari98 mam Assign this issue to me I will add it.

Hello @RituKumari98
I want to Add
[Home]
[Features]
[About]
[Contact]
(Under GSSoC'24)
Page i've recently contributed in project here ScreeenShot

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Could you please assign this issue to me under GSSOC 24.