jatiinyadav / crew-connect Goto Github PK

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

• Whenever a PR is created there should be a automated message to the user, something like this:

• When a PR is merged there should be a Thankyou message by the bot. For example: - Thankyou @username for your contribution. You can improvise the message.

• This empowers community members to report bugs, suggest improvements, and share ideas directly.
• Benefits include enhanced collaboration, community engagement, diverse input, and increased transparency.
• Implementation involves enabling issue creation permissions for contributors, providing guidelines, and implementing moderation.

Let's work together to foster collaboration and innovation within our project.
Feel free to share your thoughts and suggestions!🚀

Note: Don't message in the issue for assigning this issue, you are open to create new issues in this repo.

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.

Hi Admin,

I'm interested in contributing to your project as part of GSSoC. I've been following your work and believe my skills align well. You can find my portfolio here: (https://sites.google.com/view/uibymehtab) and LinkedIn (https://www.linkedin.com/in/mehtabarkhan/)

Thanks,
Mehtab

1. When a new group is created, copy the group name to the clipboard.
2. Add a popup using the already installed NPM package ng-angular-popup, which state that Group Name is copied something like that. You can improvise the message.

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.

What problem is this feature trying to solve?
This feature aims to automate the process of managing old issues, ensuring that the repository remains organized and focused on relevant tasks. By automatically closing old issues, it reduces manual overhead for repository maintainers and helps keep the issue tracker tidy and up-to-date.

1. Generate unique alphanumeric codes of 5-6 characters for each new chat group.
2. Ensure that the generated codes are unique across all existing groups.
3. Consider scalability and performance implications, especially as the number of groups grows.
4. Integrate the code generation logic into the process of creating new chat groups.
5. There should be a new input when a user is joining a group. A user can join a group by entering group name or unique code.
6. There should be a option for the Admin to copy the group name or unique code.

If you have any doubts, feel free to ask in comments.

1. In the MongoDLL Class Library project I have created a Class as MongoData.cs, in that class I have implemented the Mongo DB change stream, but it is not working correctly. Line 53

2. When a user sends a message from the frontend, for now the message is being directly added into the array of messages, But I want that the message should be added by the data that is passed by the MongoDB change stream.

If you have any doubts, feel free to ask in the comments.

Is your feature request related to a problem? Please describe.
There is no feature of reacting to other messages.

Describe the solution you'd like
I would like to add feature where one can react to other messages through emojis or notes.

Describe alternatives you've considered

Additional context
Please assign me this issue under GSSoC'24

1. Remove inline CSS from all the components and create new class with proper names in styles/common.css
2. Remove the styleURLs property from every component and make sure that all the components are using css from styles/common.css.

Chat should be scrolled at the bottom in following cases.

1. When a user login's in the group
2. After login, if the user scrolls above in the chat and if sends a message.

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.

What problem is this feature trying to solve?
This feature aims to automate the management of open PRs in a repository, ensuring that outdated or abandoned PRs are closed in a timely manner. By doing so, it helps maintain repository hygiene, improves workflow efficiency, and provides a better experience for both maintainers and contributors.

Is your feature request related to a problem? Please describe.
No feature of sending voice notes

Describe the solution you'd like
I would like to add feature where crew mates can send voice notes to each other.

Describe alternatives you've considered

Additional context
Please assign me this issue under GSSoC'24.

The context of images here means, while creating the docs make sure to only add images related to the installation of the project.

• Make the landing page responsive for all the screen sizes.
• Make sure to do the styling changes in styles/common.css

I want to design a logo and brand identity before going into the UI design. As i am being designing the UI for the project.

It will be great to design a logo first and got your view.

1. A user can join multiple groups and the notifications of all the groups should be in real time and user should be notified about the message.
2. If the user clicks on the notification of the new message, user's chat should be of that group.

If you have any doubts, feel free to ask in comments.

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.

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

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.

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

👋 Hi @jatiinyadav ,

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

• #8
• #4
• #5
• #6
• #7

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

1. Add a regex pattern for email validation in both the cases: When creating a group or joining a group.
2. Use the existing Toast Message NPM Package for appropriate errors.