Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Description:

The project would benefit from a PR title checker that ensures conformity to conventional commit prefixes. Currently, the following prefixes are considered valid:

• build:
• chore:
• docs:
• feat:
• fix:
• perf:
• refactor:
• revert:
• style:
• test:

Problem:

Enforcing consistent and descriptive PR titles following conventional commit prefixes helps maintain clarity and organization in the project's version history.

Describe the solution you'd like

Implement a PR title checker that validates each PR title against the specified conventional commit prefixes. This will ensure that PR titles adhere to the established guidelines.

To-Do:

• Develop the PR title checker script to verify titles against the defined prefixes.
• Integrate the checker into the project's CI/CD pipeline.
• Define error messages or warnings for non-compliant PR titles.

Checklist

• I have read the Contributing Guidelines
• I am willing to work on this issue
• I am a GSSoC'24 contributor

Use Cases and Benefits

No response

Priority/Impact

Medium

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Add the board icons functionality .

Use Cases and Benefits

No response

Priority/Impact

Medium

Is there an existing feature request for this?

• I have searched the existing issues

Summary

Work on add draggable component and right section.

Why should this be worked on?

@mohit-fsdet he want to work on it .

Repository

InfraBoard

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Error : https://cloud.appwrite.io/v1/account/sessions/oauth2/google?success=https%3A%2F%2Fwww.infraboard.xerocodee.com%2F&failure=https%3A%2F%2Fwww.infraboard.xerocodee.com%2Flogin&project=65ca043c0d7319fd7c23

Steps to reproduce

Google OAuth2 is not working.

Environment

Production ( Master Branch )

Version

Local

Repository

InfraBoard

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

when I click on the sign in with google it is not working

Steps to reproduce

clicking on sign in with google will ask for Google account then after choosing and giving permission it will redirect to login page

Environment

Production ( Master Branch )

Version

Local

Repository

InfraBoard

Design Title

InfraBoard Mobile Experience

Design Description

The mobile view of InfraBoard's landing page should prioritize responsiveness and ease of navigation. It should display the most critical information about the platform succinctly, with a clear call to action. The design needs to be clean, with intuitive touch controls, and must ensure that content is legible on smaller screens. Interactivity should be optimized for touch gestures, and the design should reflect the branding and design language consistent with the desktop version, ensuring a seamless user experience across devices.

Figma File Link

https://www.figma.com/file/HALTRuGqqInPg3VQ0kMwH2/InfraBoard?type=design&node-id=0%3A1&mode=design&t=xyJoYYMZLRupZbZy-1

Terms and Conditions

• I have read and agree to the Terms of Service and Privacy Policy.

Design Category

UI/UX

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

I propose implementing a feature that automatically comments on an issue when it is raised. This comment will serve as an acknowledgment to the contributor for bringing the issue to our attention and provide any necessary guidance or next steps.

Use Cases and Benefits

No response

Priority/Impact

Medium

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When I do register self error happens and I see the error message attached below Failed to construct 'URL': Invalid URL What I expect is Signup successfully

Steps to reproduce

1. Go to Signup page
2. Enter your details
3. Click on remember me
4. Click the register button
5. Got an above mentioned error
   

Environment

None

Version

Cloud

Repository

InfraBoard

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

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. 👍

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

facing problem with login and signup

Steps to reproduce

1.Verify the functionality of the login and signup processes.
2.Test the login and signup functionalities.

Environment

None

Version

Local

Repository

InfraBoard

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Security Feature

In your application anyone can enter using temporary or disposable email.
I will add a feature so that no one could create an account using temporary or disposable email.

Use Cases and Benefits

It will allow only genuine users in your database.
It will help to avoid any bot.
Assign me this work under GSSoC24, I will implement it.

Priority/Impact

High

Is there an existing feature request for this?

• I have searched the existing issues

Summary

Improve the left sidebar.

Why should this be worked on?

@pratik-fsdet he is good on frontend side .

Repository

InfraBoard

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Edit the environment variables name

Use Cases and Benefits

No response

Priority/Impact

None

👋 Hi @xerocodee,

I am Prince,web developer 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

• #80
• #81
• #82
• #83
• #84

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

I would like to add a pull request template for this repository. Please assign me this issue under GSSOC'24.

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Setting up a login system using Appwrite as a backend service involves several steps. Appwrite provides a complete backend server with user authentication that you can integrate into your web or mobile applications. Here’s a brief overview of how to set up a login system with Appwrite:

1. Set Up Appwrite Server: Install Appwrite on your server or use a hosted instance. Follow the Appwrite installation guide to get it up and running.

2. Create a Project: Once Appwrite is installed, go to the Appwrite console, create a new project, and note down your project ID.

3. Add a Web Platform: In your project's settings, add a new Web platform and specify your website's domain to enable CORS.

4. Get SDK: Include the Appwrite SDK in your frontend project. You can install it via NPM:

   npm install appwrite

5. Initialize Appwrite SDK: In your application, initialize the Appwrite SDK with your project ID and the endpoint of your Appwrite server:

   const appwrite = new Appwrite();
   appwrite
     .setEndpoint('YOUR_APPWRITE_ENDPOINT') // Set only once at the start of your app
     .setProject('YOUR_PROJECT_ID'); // Replace with your project ID

6. Create Account and Session: Use the Appwrite SDK to create user accounts and manage sessions. Here's an example of creating a session with an email and password:

   appwrite.account.createSession('[email protected]', 'password')
     .then(response => {
       console.log('Session created', response);
     }, error => {
       console.error('Error creating session', error);
     });

7. Handle Authentication State: Use Appwrite SDK's account methods to check if a user is logged in and handle user state accordingly.

8. Secure Your Endpoints: Use Appwrite's server-side SDKs or HTTP API to check the user's session on your backend and secure your endpoints.

Remember to secure your Appwrite console with proper access control to prevent unauthorized access.

For a more detailed implementation, you would refer to the official Appwrite documentation for specific instructions on configuring authentication and handling user sessions.

Use Cases and Benefits

No response

Priority/Impact

High

This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.

Could you please assign me this issue 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

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Description:

• Create a GitHub Action or configure a bot that automatically assigns a user to an issue when they comment with /assign.
• The assigned user should be unassigned automatically if there's no activity from them on the issue within one week.

Acceptance Criteria:

• A user can type /assign in an issue comment to get assigned to the issue.
• The bot/action checks for user activity on the issue.
• If after one week there's no activity from the assigned user, they are automatically unassigned.
• The implementation should not affect any other repository automation.

Please discuss any potential approaches or concerns before implementing this feature.

Use Cases and Benefits

The benefits of implementing such a feature include increased efficiency in issue management, better engagement from the community, and ensuring that progress on the project is continuous and dynamic.

Priority/Impact

High

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.

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

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Overlapping hover card card to another canva board nav card.

Steps to reproduce

Environment

Production ( Master Branch )

Version

Cloud

Repository

InfraBoard

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

AWS SVG Icons : https://awsicons.dev/ | Convert SVG to Model : https://svg2jsx.com/

This site will help you get the SVG icons and convert them into model code.

Use Cases and Benefits

No response

Priority/Impact

High

I would like an automated feature that posts a predefined comment on an issue as soon as it is created. 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.

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

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Error : https://cloud.appwrite.io/v1/account/sessions/oauth2/github?success=https%3A%2F%2Fwww.infraboard.xerocodee.com%2F&failure=https%3A%2F%2Fwww.infraboard.xerocodee.com%2Flogin&project=65ca043c0d7319fd7c23

Steps to reproduce

GitHub OAuth2 is not working.

Environment

Production ( Master Branch )

Version

Local

Repository

InfraBoard

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

I would like add new icons of IOT , i have worked on iot before so i know which are necessary.

Use Cases and Benefits

It would make website more interactive.

Priority/Impact

None

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Kindly assign this issue to me
what i contribute in above issue :
1.Better UI designing of landing page with navbar and responsiveness to all screen.
2.Dark Light theme changing.
3.contact us section better enhancement
4.Card with hover effect that can make it more tempting and seaking more user visiting count.
5.About section content with carousel regarding upcoming or ongoing updated feature

Kindly assign this issue to unser GSSOC24

Use Cases and Benefits

1. Better UI designing of landing page with navbar and responsiveness to all screen.

Usecase: A user visits the landing page on various devices (desktop, tablet, mobile) and expects a visually appealing and responsive design.
Benefit: Improved user experience, increased engagement, and better conversion rates.

2. Dark Light theme changing.
   Usecase: A user wants to switch between light and dark themes to suit their visual preferences.
   Benefit: Enhanced user experience, improved readability, and increased accessibility.

3. Contact us section better enhancement
   Usecase: A user wants to easily find and contact the organization through a well-designed contact section.
   Benefit: Improved communication, increased lead generation, and better customer support.

4. Card with hover effect that can make it more tempting and seeking more user visiting count.
   Usecase: A user hovers over a card element on the landing page, and it responds with a visually appealing effect, encouraging them to click and explore further.
   Benefit: Increased user engagement, improved click-through rates, and enhanced overall user experience.

5. About section content with carousel regarding upcoming or ongoing updated feature
   Usecase: A user wants to stay informed about the latest features, updates, and news about the organization through a carousel in the about section.
   Benefit: Improved user engagement, increased transparency, and better communication of the organization's value proposition.

Priority/Impact

Medium

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.

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

Create the right side panel to see the code of drop element.

Use Cases and Benefits

No response

Priority/Impact

Medium

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

We need to develop a landing page for the InfraBoard project to provide a comprehensive overview and entry point for new visitors. The landing page should be visually appealing and user-friendly, encapsulating the essence of InfraBoard.

Tasks:

• Design the layout.
• Implement the frontend interface.

Resources:

• Designs: https://www.figma.com/file/HALTRuGqqInPg3VQ0kMwH2/InfraBoard?type=design&node-id=0-1&mode=design&t=rk496XO9YTTAjgJD-0

Notes:

• Please ensure the design is responsive and accessible.

File Structure

/src
  /pages
    /landing        # Directory for landing page components
      index.tsx     # Main landing page component
      styles.module.css # CSS modules for styling specific to the landing page
  /components       # Reusable UI components
    /Header
      Header.tsx    # Header component used across multiple pages
    /Footer
      Footer.tsx    # Footer component used across multiple pages
  /public           # Public assets folder
    /images         # Images used on the landing page
      logo.svg      # Logo file
      hero-bg.png   # Background image for the hero section
  /styles           # Global styles
    globals.css     # CSS for global styling

Use Cases and Benefits

No response

Priority/Impact

High

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

I signup from my Github , and after that I am not able to login , whole page got refreshed

Steps to reproduce

Trying by login using any of the ways , either my Google, or try with github

Environment

Stage ( Stage Branch )

Version

Local

Repository

InfraBoard

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

There must be a better loader as its used and presence make the overall experience for user decide as its coming in various ways.

Use Cases and Benefits

Benefits:
Improved user experience and better ui design

Priority/Impact

High

THIS ISSUE IS UNDER GSSOC'24 @pratik-fsdet assign this issue to me

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

It should be center

Steps to reproduce

Ui

Environment

Deploy preview ( Test Branch )

Version

Local

Repository

InfraBoard

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When a user attempts to sign up without entering any data in the input fields, the form does not provide appropriate feedback to indicate that the fields are required. Instead of prompting the user to fill out the required fields, it displays email is not valid which is confusing and does not accurately reflect the issue. This behavior can lead to user frustration and difficulty in understanding the validation requirements.

Steps to reproduce

1. Visit the Login page.
2. Do not enter any data in the input fields.
3. Click the Login button.

I Resolved this issue Locally waiting for ur valuable response

Environment

None

Version

Local

Repository

InfraBoard

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Test the github action score

Steps to reproduce

Test the github action score

Environment

Stage

Version

Local

Repository

InfraBoard

Is there an existing feature request for this?

• I have searched the existing issues

Detailed Description

The landing page should serve as the entry point to InfraBoard, highlighting its core features and benefits. It should be visually appealing and informative, providing a snapshot of what InfraBoard offers. The design should be intuitive, guiding new visitors to explore the tool's capabilities and encouraging them to try or adopt it for their cloud infrastructure management needs.

Use Cases and Benefits

• Clearly communicate the value proposition of InfraBoard to first-time visitors.
• Showcase ease of use and efficiency in cloud infrastructure management.
• Increase user engagement by highlighting key features through interactive elements or demos.
• Serve as a marketing tool to boost sign-ups and conversions.

Priority/Impact

High

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

I'm encountering a build error when running next build. It fails during the static page generation with a "ReferenceError: window is not defined". This seems to happen in components that are server-side rendered and are trying to access the window object.

Steps to Reproduce:

1. Run npm run build
2. Observe the error during the static generation phase.

Expected Behavior:
The build process should complete without any reference errors related to the window object.

Actual Behavior:
The build fails with a "ReferenceError: window is not defined".

Environment:

• Next.js version: [e.g., 10.0.0]
• Node.js version: [e.g., 14.15.1]

Additional Context:
Here's the error log from the terminal:

Steps to reproduce

Possible Solution:
Ensuring that window is not accessed during server-side rendering or using dynamic imports with { ssr: false } for client-side only components.

Environment

Production ( Master Branch )

Version

Local

Repository

InfraBoard

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Hello @aryasoni98
try to sign up with google and github, on click these button are not working
I want to solve this issue. assign me

Steps to reproduce

1.First, check the onclick function.
2.Verify Appwrite authentication with Google or GitHub.
3.Attempt to validate through testing.

Environment

None

Version

Local

Repository

InfraBoard

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 yours.

I would like to add a issues template for documentation issues in this repository. I believe that having a standardised template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review issues.

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

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Steps to reproduce

Linting and checking validity of types . ⨯ ESLint: Failed to load plugin 'next' declared in '.eslintrc': Cannot find module '/InfraBoard/node_modules/eslint-plugin-next/index.js'. Please verify that the package.json has a valid "main" entry Require stack: - /InfraBoard/__placeholder__.js Referenced from: /InfraBoard/.eslintrc

Environment

Production

Version

Local

Repository

InfraBoard