rajat2502 / standnote Goto Github PK

Hello @rajat2502 @vinitshahdeo @friskycodeur @geekquad @PragatiVerma18
We came accross your Standnote Project. I’ve been having some trouble with the setup process, and I was wondering if you might be able to offer some guidance or advice.

Any help would be greatly appreciated.

Thanks and Regards

Is your feature request related to a problem? Please describe.
Since most professional teams communicate over slack, adding a Slack bot would be helpful in case people want to push their minutes of the meeting to a Slack channel.

Describe the solution you'd like
Design and Develop a Slack bot that can be added to Slack and used to configure and push minutes of the meeting from StandNote to a specific Slack Channel.

Describe alternatives you've considered
Similarly, a discord bot can also be designed and developed.

Additional context
Please read the following resources to learn more about developing a Slack bot in Python:

1. How To Build a Slackbot in Python on Ubuntu 20.04 - DigitalOcean
2. Building an app with Bolt for Python - Slack API Tutorial

Your README currently looks great! I would recommend adding:

• How users can setup the project on their local machine for contributions.
• Explaining to users you have a LEARN.md file
• Mention your CONTRIBUTING file
• Mention your code of conduct

This is a really cool project. I am trying to set up the backend but the social application login steps are not clear to me. There are three windows that I can see here. Could you please guide me regarding the steps to set up the social logins. My login system is not working because of this issue. Attaching images of the three windows that I can see in the set up.

Waiting for a response.

I can't register in the app.

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.

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?

Learn repos should have a LEARN.md file to teach another 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.

If you feel your project is too large to teach step-by-step how to build it, consider just teaching a certain tool or implementation that your project utilizes.

Other than GitHub Topics, your description will be the primary way of catching the users eyes. Your repo description should be clear and concise. Currently it is long. Ask yourself:

• In one sentence, how do I convey what my repo does?
• What type of users am I interested in attracting to my repo?
• If I was a user, what words or phrases might spark my interest?

👋 Hi @PragatiVerma18,

I am your GitHub mentor for the GitHub Education, Community Exchange (CX) project. I'll be collaborating with you on preparing your repo for CX.

You mentioned in your submission that you wanted to submit a Learn + Collaborate repo. This means that you would like to teach students, step by step, how to build this project as well as invite other students to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for a Learn + Collaborate CX submission on June 1, 2022.

This issue will serve as a tracking issue to track all issues related to CX. 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.

Your repo is currently in great shape, so I don't believe we will have to do too much to get your repo ready for a CX submission 😄

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

Issues

• #13
• #14
• #15
• #16
• #17

Describe Problem
The summarization algorithm here doesn't summarize well in case there are smaller sentences, or there are broken sentences.

Describe the solution you'd like
We would like to have an optimized summarization algorithm such that it summarizes the text effectively without generating broken text in summary, and also is able to identify action words such as dates, days, etc, such that they're given more importance in the generated summary.

Please submit the PR to ml branch. Once we finalize the improvements in the algorithm, we will go ahead and integrate it into the backend.

Unable to sign-up using google OAuth

Is your feature request related to a problem? Please describe.
StandNote uses the old way of pushing the text to a Notion doc via making a request to the Notion client with the doc link and Notion V2 Token (using notion==0.0.27 Python package).

Describe the solution you'd like
Since Notion has released its new API, we would like to integrate the new API and remove the old way of pushing the summarized text to a Notion doc.

You can read more about Notion API here.

I used Standnote for a meeting but when I finished it, my notes weren't loading when I click on one of them. They were saved in the Dashboard but on clicking on one of them the page just keeps loading without my application showing.

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

In order to submit your project into CX you will need at least one issue, but we recommend more so other students have an idea on where to start.