Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements to the review club format #31

Open
jbesraa opened this issue Mar 18, 2024 · 2 comments
Open

Improvements to the review club format #31

jbesraa opened this issue Mar 18, 2024 · 2 comments

Comments

@jbesraa
Copy link
Contributor

jbesraa commented Mar 18, 2024

We have been running the review club for a bit and we would like to increase the engagement and hear from everyone what could be improved in order to make the sessions more accessible and attractive.

Currently the session is running on every second Friday and the sessions are usually published here https://ldk.reviews/ beforehand. The sessions run in a chat format in the LDK discord channel.

The main goal of the sessions is to allow new contributors to raise questions and get a the chance to discuss the merits of a PR with with other developers and get more confidence to contribute to the code base in the future.

A few suggestions were discussed while at Advancing Bitcoin:

  1. Have voice sessions instead of chat(Can be potentially transcribed on the go by the platform we would use)
  2. Change the current time as its more tricky for EU/Asia based participants to join on Friday evening
  3. Allow participants to decide whats the session about

I would love to hear what you guys think and how we can improve these sessions.

cc @jkczyz

@TheBlueMatt
Copy link

I'd really like to hear from folks who would like to join the review club but don't/can't. There's only really a handful of folks trying to get involved in LDK dev very seriously. Most of them seem to be doing it more through writing code, but either they can't find the time to join the review club (possibly timezone-related) or don't want to. We should try to reach out to those folks.

@jbesraa
Copy link
Contributor Author

jbesraa commented Mar 21, 2024

Another idea I had is taking an issue and do collab dev in a couple of sessions and then review it in following sessions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants