-
Notifications
You must be signed in to change notification settings - Fork 24
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
Next Deep Dive #228
Comments
I wonder if talking about #177 would be good? I think the technical deep dives are great, but seems like there is a fair bit to talk about in regard to corporate sponsorship and supporting the project(s). |
I think this could be a good point, maybe not a public one but it would make sens to have it splitted in two part
Maybe it would make sens to have some people from the foundation (+ LF and OSPO ? ) |
I dont have time for a long thoughtful comment here, however, @wesleytodd and I were chatting earlier today and it sorta dawned on me that perhaps the biggest issue facing Node.js (thinking about "the next 10 years") may be the issue of not having great pathways for new contributors to get involved and grow within the project. I realize that I dont have stats at hand on growth/decline of contributions, but I worry that if a few key people left the project, we would have serious gap in leadership and knowledge. Sidenote: i've been meaning to get this meeting back on my calendar. I have a conflict (doc appt) for the Oct 25 meeting but will try to rejoin the next meeting. |
We ageed today in the team meeting that the next deep dive should be: We need to
Initial suggestion for date was Fed 22nd 10-12 ET but that seems to conflict with some conferences. @sheplu what's the next Thursday after that which might work? |
I think we can try to do it on February 29th. |
@sheplu sounds good to me. |
Created an issue linked to the deep dive #247 |
Closing this in favor of the deep dive agenda linked above. |
Topics ?
The text was updated successfully, but these errors were encountered: