👋 Hi @jaibhedia ,

I am Sanjay, program Manager 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

• #1
• #2
• #3
• #4
• #5

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.

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.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Additional context
Add any other context or screenshots about the feature request here.

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."

Please assign this issue to me.

Is your feature request related to a problem? Please describe.
The navbar is not good in below tablet view section

Describe the solution you'd like
Add Navbar in below tablet view section

Additional context
Add any other context or screenshots about the feature request here.

Add this feature in below tablet view section

I am GSSOC24 Contributor
please assign me, I would like to work on this issue

Describe the Feature you want to end

Currently, the issue template for this repo seems to be basic also it is less visually appealing.👇

Changes I will make

Expected behavior

Screenshots (optional)

Additional context (optional )
Will add issue forms to the respective issues to make it easier for the contributor to raise it.
Here is an example of how a Bug Issue Form will look like 👇

Is your feature request related to a problem? Please describe.

I'm always frustrated when I'm unable to find clear and concise information about the functionalities and features of the ChainzRegistry repository. Users, including myself, often need a comprehensive resource to understand what ChainzRegistry does and how to use it effectively.

Describe the solution you'd like

I would love to create a dedicated website for the ChainzRegistry repository. This website will provide detailed explanations about the functionalities, features, and usage of ChainzRegistry. It will serve as a one-stop resource for both new and experienced users to get the most out of ChainzRegistry.

You can access the website at jaibhedia.github.io/chainzRegistry.

Additional context

The website will include:

• An overview of ChainzRegistry and its purpose.
• Detailed documentation on how to use various features.
• Examples and tutorials for common use cases.
• A FAQ section to address common questions and troubleshooting tips.
• Links to the repository, issue tracker, and other relevant resources.

This will not only help current users but also attract new users by providing a clear and structured presentation of what ChainzRegistry offers.

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 can add the tag GSSoC'24, good first issue etc.
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

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to the problem of lack of communication and acknowledgment when issues are closed in the repository. Contributors may feel neglected or uncertain about the status of their issues if they are closed without any feedback or acknowledgment. This can lead to frustration and a decrease in motivation to contribute further.

Describe the solution you'd like
The solution is to automatically post a comment on the issue whenever it gets closed. This comment should thank the issue creator for their contribution and inform them that their issue has been closed. The message can include the issue number and a friendly greeting to make it more personal. This automation ensures that every closed issue receives a consistent and timely response, improving communication and contributor experience.

Additional context

Please assign me this issue under gssoc 24

What's missing int this repository !!

Including a README file, a Code of Conduct, and a Contributing file in your repository is essential for fostering a collaborative, organized, and respectful project environment. As these files plays an important role in user/contributor convenience and maintains
project respectful .

Hey @jaibhedia , Kindly assign this issue to me under GSSoC'24

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.

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.

I know it's a basic issue, but i want to start from somewhere, i am new to the platform and want to contribute. If needed please assign this issue to me under gssoc.

A Code of Conduct is essential for open-source projects because it sets clear expectations for behavior, ensuring a respectful and inclusive environment. It helps prevent harassment and discrimination, making the community welcoming and safe for everyone. By outlining consequences for unacceptable behavior, it maintains a positive and collaborative atmosphere, which is crucial for the project's success and sustainability.

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

Is your feature request related to a problem? Please describe.
Over time, repositories can accumulate a large number of open issues, including some that may no longer be relevant or actively worked on. Manually closing these old issues can be time-consuming and tedious.

Describe the solution you'd like
I would like a workflow that automatically identifies and closes old issues based on certain criteria, such as no recent activity or being open for a specific duration.

Additional context

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.

Docker is a must for open-source projects nowadays as it has its benefits.

Use Case
Dockerfile has many benefits but consistency and isolation stand out the most.

Docker allows you to package your entire application, including its dependencies, into a single container. That makes sure your application will run across different environments.
another benefit is that it runs in its environment without interfering with other applications or the host system.

I will also be updating the docs for it.

Readme.md file is good currently but it can be more fascinating by adding animated emojis , fixing allignment , adding snapshots of our project, adding headers , contents and dropdowns.

Is your feature request related to a problem? Please describe.
Creating a new logo for your website

Describe the solution you'd like
i want to create a new logo for your website

Additional context
Add any other context or screenshots about the feature request here.

I am writing to express my interest in contributing to your repository by creating a pull request template.
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 me the issue under gssoc24? I am excited about the opportunity to contribute to your project and help improve the workflow for all contributors.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
Over time, open pull requests (PRs) can accumulate in a repository, cluttering the interface and making it difficult to focus on active development tasks. Additionally, outdated or abandoned PRs may no longer serve their intended purpose and should be closed to maintain repository cleanliness.

Describe the solution you'd like
Implement a workflow that automatically closes old PRs based on predefined criteria, such as their last update timestamp. By regularly closing PRs that have not been updated within a certain timeframe, the repository can stay organized, and contributors can focus on active and relevant PRs.

Additional context

Hey @owner,

As I was delving into the project, I stumbled upon a specific issue that caught my attention. Let me walk you through it:

Improvement Opportunity: Error Handling for Flutter SDK Location

Currently, your code checks for the Flutter SDK location in the local.properties file and throws a GradleException if it's not found. While this is a good practice to ensure the necessary configuration is present, it lacks detailed error handling and guidance for users.

Issue Details:

Limited Error Message: The current error message thrown (Flutter SDK not found. Define location with flutter.sdk in the local.properties file.) is informative but doesn't provide users with guidance on how to resolve the issue.

Given the importance of this issue, I'd love to contribute to its resolution. Could you please assign me this issue? I'm participating in GSSoC and eager to lend a hand.

Looking forward to your thoughts on this!

Best regards,
Ashutosh Singh

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
the navbar is not looks good

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

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.

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.

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

Describe the bug
Legal Record Management form is not looking legal XD,
I can fix that, I am familiar with UI/UX

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://noplaybutton-41656.web.app/'
2. Click on 'https://npb-e-vault.vercel.app/'
3. UI not proper

Expected behavior
A well organized and structured form matching with the website, for better UX

Screenshots

@jaibhedia Please Assign This Issue To Me :)

It would be nice to add a footer with the website logo, different sections and social media links.
@jaibhedia can you please assign this to me?

Describe the bug
There is a UI over flow in entire home page

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Home page'
2. See error

Expected behavior
There should be no Overflow. The Page should be more responsive

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Browser Edge

Gold Price Prediction

Project Overview

This project aims to predict the price of gold using various machine learning models. The project includes data exploration, feature engineering, model training, and evaluation.

Requirements

1. Data Retrieval:

   • Collect historical gold price data from a reliable source.

2. Data Exploration:

   • Perform exploratory data analysis (EDA) to understand the data distribution and patterns.
   • Visualize the data to identify trends and relationships.

3. Feature Engineering:

   • Create new features that could improve the model's performance.
   • Handle missing values and perform data normalization/standardization.

4. Model Training:

   • Train various machine learning models (e.g., Linear Regression, Decision Trees, Random Forest, LSTM).
   • Use train_test_split to create training and testing datasets.
   • Apply techniques like cross-validation to improve model robustness.

5. Model Evaluation:

   • Evaluate model performance using appropriate metrics (e.g., RMSE, MAE, R2 score).
   • Compare the performance of different models.
   • Visualize the model predictions against actual values.

Libraries and Tools

• pandas
• numpy
• matplotlib
• seaborn
• scikit-learn
• tensorflow and keras (for LSTM model)
• Any other relevant libraries for data processing and model training

Approach

1. Data Retrieval:

   • Collect historical gold price data from a reliable source such as Yahoo Finance, Quandl, or other financial data providers.

2. Data Exploration:

   • Load the data into a DataFrame and inspect the first few rows.
   • Check for missing values and handle them appropriately.
   • Perform statistical analysis to summarize the data.
   • Create visualizations (e.g., line plots, histograms, box plots) to understand data trends and distributions.

3. Feature Engineering:

   • Generate additional features like moving averages, rolling statistics, and lag features.
   • Normalize or standardize the data to improve model performance.
   • Encode categorical features if any.

4. Model Training:

   • Split the data into training and testing sets using train_test_split.
   • Train various machine learning models:
     • Linear Regression
     • Decision Trees
     • Random Forest
     • LSTM (using TensorFlow and Keras)
   • Perform cross-validation to ensure model robustness.

5. Model Evaluation:

   • Evaluate each model using metrics like RMSE, MAE, and R2 score.
   • Visualize the predictions of each model against actual gold prices.
   • Select the best-performing model based on evaluation metrics.

Tasks

• Collect historical gold price data.
• Perform exploratory data analysis (EDA).
• Conduct feature engineering.
• Normalize or standardize the data.
• Split the data into training and testing sets.
• Train machine learning models (Linear Regression, Decision Trees, Random Forest, LSTM).
• Perform cross-validation.
• Evaluate model performance using RMSE, MAE, and R2 score.
• Visualize model predictions.
• Compare the performance of different models.

Additional Information

Use the following libraries to assist with model training and evaluation:

import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
import seaborn as sns
from sklearn.model_selection import train_test_split, cross_val_score
from sklearn.metrics import mean_absolute_error, mean_squared_error, r2_score
import tensorflow as tf
from keras.models import Sequential
from keras.layers import Dense, LSTM, Dropout

Expected Outcomes

• A comprehensive analysis of historical gold price data.
• Effective feature engineering to enhance model performance.
• Training and evaluation of multiple machine learning models.
• Selection of the best model for gold price prediction.
• Visualization of model predictions to provide insights.

The project has good potential but the read-me file is not supporting the project well. I would like to improve it.

#6

Is your feature request related to a problem? Please describe.
the title of the main page is not correct and logo is missing
Describe the solution you'd like
adding logo to the main page
Additional context
Add any other context or screenshots about the feature request here.

please assign me @pa

Hello @ChainzRegistry assign me, I can improve your Read.md

Hi @jaibhedia ,
I would like to add thanks to the contributor section and support section to the readme doc. Can you please assign this issue to me?
It makes the document look more beautiful and it shows your love towards the contributors.
screenshot is attached below.

Is your feature request related to a problem? Please describe.

List of Contributors in Readme.md file missing

Is your feature request related to a problem? Please describe.
Currently, the project lacks a copyright message in its source files. This can lead to potential legal and ownership ambiguities.

Describe the solution you'd like
Add the following copyright message at the bottom of each displayed page :
Copyright © 2024 ChainzRegistry Pvt Ltd - All rights reserved

Additional context
Including a copyright message helps establish ownership and clarify licensing terms.

making the navbar sticky helps the user to easily navigate and provide ease to users

in the land contract file there is a error which can lead to gas limit issue , in the MyLands, MyReceivedLandRequest, and MySentLandRequest are storing arrays of values. If these arrays grow too large, it could lead to gas limit issues.we can instead use mapping of structs

please assign under gssoc'24 @jaibhedia