Welcome to codestream Discussions!

[gbowne1]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[gbowne1]

@MalathiBalaraman31 Thanks for the first contribution to this project.

Feel free to work on any of the issues in this project or any of my others here:

https://github.com/gbowne1

Feel free to post todo, features, bug reports, issues too.

[gbowne1]

First of all I want to welcome

@abhisheksingh1204
@rization42
@shishir-21
@Sriram2272
@SouravVerma-art
@Amanc77
@rupcode1794
@Vandna0609
@amisha6870
@Ved178
@Houria-hs
@Mustansir-06
@djnadackal
@MalathiBalaraman31
@EricKart

To this project

If you wish to be a regular contributor, a collaborator, a regular maintainer, am going to invite you as soon as you reach a minimum of 2 successful merges of your contributions.

This area is for discussion of this project.

I will only merge those with a minimum of 2 approved reviews including reviews.

There will be a Development guide as DEVSETUP.md soon.

This Discussion area is for asking questions about the project, discussing possible and potential new features and anything about the project outside of its bugs and issues so that it keeps issues and bug reports and feature requests clean.

If you would like to propose a new feature please do so here

This project will be self hosted and fully open source as

Also, as you contribute fixes, please:

Include a brief description of your changes

Include logs and or capture of the browser console and other helpful items that will shoe

Before vs After also helps show us control over fixes.

Include a short video, screenshot and or show working changes so we as reviewers, collaborators, contributors, maintainers know exactly what to expect when we look at your changes

Do not trust "Well, it works on my machine"

Avoid "looks good to me"

If you're unable to complete a fix within a reasonable amount of time let us know.

Thanks for being a part of this project

[gbowne1]

There's 8 pending PR's for ready for review which need to be triaged to figure out which to merge in which order. Currently not sure which order to merge these after spproved reviews are completed by these collaborators, contributors and maintainers.

We had a bunch of PRs. I checked out the changes but not sure what will overlap or cause merge conflict's

Is anyone willing to provide screenshots etc for design and development purposes and for layout purposes as well

If you can help with this let me know

@Haseebx162006

[Haseebx162006]

Hi , I hope you’re doing well. I wanted to inform you that I have completed the implementation for **issue #51**, which fixes the login API to properly use HTTP status codes 400 (missing fields) and 401 (invalid credentials), replacing the previous nginx-specific 444. Additionally, I added **login and logout screens** for testing purposes, as the frontend was not previously implemented. These screens allow easy verification of the backend logic without requiring a live MongoDB connection. Since the `MONGODB_URI` is not provided, I created a **`test_auth.js`** script in the project root, which simulates the database and tests the critical login logic directly. To verify the changes: 1. Open a terminal in VS Code. 2. Run: node test_auth.js Screenshot ***@***.***> wrote:

…

There's 8 pending PR's for ready for review which need to be triaged to figure out which to merge in which order. Currently not sure which order to merge these after spproved reviews are completed by these collaborators, contributors and maintainers. We had a bunch of PRs. I checked out the changes but not sure what will overlap or cause merge conflict's Is anyone willing to provide screenshots etc for design and development purposes and for layout purposes as well If you can help with this let me know @Haseebx162006 <https://github.com/Haseebx162006> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQZXC7MACM3AMDZ5ZJ5D6OL4IXLUJAVCNFSM6AAAAACB7MS3TOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNRQGQYDKNQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gbowne1]

@Haseebx162006

PR #50 includes a sample .env file.

I'm reviewing your PR at the moment and I'm only merging PRs after at least one other collaborator, contributor, maintainer can check out and review changes for some measure of security especially since theres no vite tests yet or any workflow/action for code quality, lint, etc.

I'll issue invitations to be collaborators maintainers contributors once theres two successful merges of their code (separate PRs).

Once the initial development cycle is over I'll place it on the host system.

I'll need someone to check out the 8 PRs and help determine what gets merged first. I'll invite anyone working on this project to go ahead and check out the individual PRs and help decide

[shishir-21]

Hi @gbowne1
I can help review the open PRs and provide feedback on code quality and potential risks.
I will start by checking the documentation and service worker related PRs and share my thoughts here.
Let me know if there’s any specific PR you want reviewed first.

[gbowne1]

@shishir-21

There's 8 open PRs including yours.

This post in Discussions is really just a welcome message.

I would prefer comments on individual PRs and or comments be made in a new Discussion in the Ideas or General section of this Discussion.

I would start with the oldest PR first.

Trying to minimize overlap and potential for merge conflict here is what I'm doing.

[Ved178]

Hi @gbowne1
I'd also like to help review the PRs.

[gbowne1]

@Ved178 thanks. I appreciate that. One thing about GitHub I did not realize is that anyone not just maintainers and contributors and collaborators can review PRs. Feel free to review each PR.

[gbowne1]

Still a pile of 7 or 8 PRs open most of them need one or two more reviews or re-reviews. Also a few have a large merge conflict with a bunch of files so needs rebase up to current.

Maintainers can commit a rebase

I'm so anxious and waiting to get in the Live chat and go live functions into the app just waiting on the reviews to do that. I'd really appreciate more reviews so I can merge stuff