Back from break - catching up on everything

[ma2t]

Hey everyone, I was off the grid for two weeks and just catching up now.

Wow, a lot happened! Really cool to see this level of activity on the project.

@rathlinus the energy you put into PR #25 and #26 is impressive.
@chrilep, @wrenix, @madsmh, @rensreinders, @smorks — thanks for all the testing and feedback.

Here's where I'm at:

• Reviewing open PRs (fix: align sticky week headers with calendar grid #33, fix: replace inline calendar delete confirms with centered modal dialog #34) right now
• Going through every open issue
• Looking at fixes from @rathlinus's fork to bring relevant ones upstream

About PR #25: it covers a lot of ground which makes it hard to review as one block.
@rathlinus if you're up for it, let's figure out how to land those improvements as smaller focused PRs.

Contributions are very welcome and I want to make that easier going forward.
More replies on individual issues coming shortly.

[rathlinus]

Do we maybe want to discuss this via Discord or something else?

[chrilep]

Hey all, I strongly recommend to combine skills to prevent inventing the wheel a few times...

I followed @rathlinus because we share the same goal: Have the best possible webclient for stalwart's features.

In the last 12 days it wasn't possible to have any progress in this repo because there was no maintainer. As a result the code went to a fork and later into a fully-blown project and even has a name and a website now. Bulwark was born and is very close to production stage today.

If Discord is not an option for everyone I am happy to host any chat server or bridge possible. Data hosted in germany in my semi-pro home lab.

Let us build something big together!

[rathlinus]

I believe there's no shortage of computing power among the three of us, so that shouldnt be a problem

[ma2t]

Thanks both. I get the appeal of real-time chat, but I'd prefer to keep technical discussions on GitHub where they're searchable and linked to the code. Issues, PRs, and Discussions cover most use cases.

@chrilep the offer to host a chat is generous. If the community wants a chat channel for quick questions and coordination that's fine, but decisions and code reviews should stay here.

As for combining efforts: we shipped v1.1.3, v1.1.4, and v1.2.0 today addressing issues reported by the community. PRs #33, #34, #36, and #37 from @rensreinders are in review. Contributions are flowing and getting merged.

The best way to move forward is focused PRs against this repo. That's how open source scales.

[rathlinus]

i dont think i can split about 70k lines of code spread over more then 120 commits into pull requests

[rathlinus]

i would be happy to add you as a co-owner