-
Notifications
You must be signed in to change notification settings - Fork 59
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
Request for opening a new chapter for Mumbai, IN #582
Comments
Hi @Omkaragrawal, that's awesome. Do you have other co-organisers? We usually recommend at least 2 or 3 people to co-organise a given chapter. Since the Mumbai chapter and team already exists, please try to get in touch with them as well. If that doesn't work out, we can go ahead and make you the new organisers along with your new co-organisers |
Hey @riyadhalnur I've tried contacting them, but couldn't find any place to contact them, and I may have a co-organiser with me. It's been many years since last activity on those chapters. So if someone volunteers here then I would be glad to have them. OR/AND I'll contact some of my friends for co-organizing. |
Thank |
1 similar comment
Thank |
Since there's no update since the last year, I believe the NodeSchool community itself is inactive, it's sad that it has been inactive for this long. |
No description provided. |
Hey,
I am Omkar Agrawal . I want to open a new chapter for Mumbai. I can see that nodeschool/Mumbai and nodeschool/mumbaiteam aren't active for like 6 years or more. Hence I propose to open a new Chapter for Mumbai. I am a freelancer based in Mumbai. I have been using node for well over a year and would like to share and gain knowledge, experience with people. As for sessions, I have some sessions and speakers in mind, I don't have any specific target audience as whatever meets I had, I keep sessions for the beginners, intermediate and advance developers (typically in 1 - 2 - 1 or 1 - 1 - 1 session counts). I have previous experience of organizing 2 offline meets and 1 online meetup.
The text was updated successfully, but these errors were encountered: