The JavaScripters Community

The purpose of our Community Code of Conduct is to ensure that all participants in the JavaScripters community have the best possible experience. We are all here to help each other learn, grow our skill sets and have a good time!The JavaScripters Community Code of Conduct covers our behaviour as members of the JavaScripters community, in any forum, mailing list, website, social media channels, code repository, private correspondence, or public meetings.

As a worldwide community, diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to, to ensure that the JavaScripters community continues to be an excellent space in which to communicate, collaborate, and contribute.This isn’t an exhaustive list of things that you can’t do. Rather, take it in the spirit in which it’s intended — a guide to make it easier to be excellent to each other. We expect it to be followed in spirit as much as in the letter.

Be patient. This mostly applies to forums, mailing lists, Social channels and code contributions (i.e. asynchronous forms of communication). Communities are often built on volunteer time both from participants and organisers. It is possible that your question or code contribution or suggestion might not receive an immediate response. Be patient and consider the norms of the community. One reminder ping is welcome, many reminder pings in rapid succession are not a good display of patience. Similarly, posting the same question in multiple threads is frowned upon and should not be done.

Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the JavaScripters community to be respectful when communicating with other community members, as well as with people outside the JavaScripters community.

Be nice. Everyone in the JavaScripters community should feel welcome, regardless of their background. Please be courteous, respectful and polite to fellow community members. No offensive comments related to gender, gender identity or expression, sexual orientation, disability, physical appearance, body size, race, religion; no sexual images in public spaces, real or implied violence, intimidation, oppression, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, or unwelcome sexual attention will be tolerated.

Communicate effectively. We don’t all speak the same language at the same skill level. Clear communication can help to avoid misunderstandings, as can remembering that our interpretations of words can be different depending on our backgrounds. Having context is important. It’s better to ask for clarification than to make assumptions. Disagreements, social and technical, are normal, but we expect participants in the project to resolve disagreements constructively — so please avoid flamewars, trolling, personal attacks, and repetitive arguments. Resources for how to most effectively engage with JavaScripters’s various forums for project participation and communication — including forums, IRC, and more — are shown here.

Ask for help when unsure. Nobody is expected to be perfect in this community. Asking questions early avoids many problems later, so questions are encouraged, though they may be directed to the appropriate forum. Those who are asked should be responsive and helpful.In addition to this Code of Conduct, all JavaScripters events are governed by the following policy. All attendees, speakers, Organizers, mentors, sponsors and volunteers, including the event organizing team, are required to follow the following Organisers are expected to enforce this policy throughout the event. We expect cooperation from all participants to help ensure a safe environment for everyone.

Policy 

Harassment includes offensive verbal comments related to gender, age, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.

Participants asked to stop any harassing behavior are expected to comply immediately. Sponsors are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Meetup organizing staff and other volunteer organizers should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.If a participant engages in harassing behavior, the JavaScritpers community authority may take any action they deem appropriate, including warning the offender or expulsion from the event.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please follow the directions in the “If You Need Help” section, directly below this policy.Organizers will be happy to help participants contact security or local law enforcement, provide escorts to an alternate location, or otherwise assist those experiencing harassment to feel safe for the duration of the meetup. We value your attendance.

We expect participants to follow these rules at our all of our event venues and event-related social events.If You Need Help

Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by contacting contact@javascripters.community

As a JavaScripters community, we take our community’s health seriously and want to ensure everyone has a good experience, so please contact us at contact@javascripters.community

if there is an issue so we can help address it.

JavaScripters Community – India’s Leading JavaScript Hub

This agreement is between the JavaScripters Community and the Speaker, outlining expectations, responsibilities, and mutual understanding for participating in our community events, including meetups, workshops, and conferences.

1. Speaker Responsibilities:

• Deliver a talk/workshop/session that aligns with the agreed-upon topic and timeframe.
• Ensure content is educational, respectful, and relevant to the JavaScript or broader tech ecosystem.
• Submit a final version of slides/presentation at least 3 days prior to the event for review.
• Maintain professionalism and uphold community standards during and after the session.

2. JavaScripters Community Responsibilities:

• Provide a platform and audience for knowledge sharing.
• Promote the speaker’s profile, topic, and session via official communication channels.
• Provide technical and logistical support during the session (AV setup, hosting, timekeeping, etc.).
• Offer a certificate of appreciation (digital or printed) post-session.
• Provide access to event photos/videos (if applicable) for personal branding.

3. Content Ownership:

• The speaker retains full ownership of their content.
• JavaScripters Community may request permission to record and share the session on social platforms, YouTube, or our website with due credit to the speaker.
• Reuse of content by the community will always involve written consent from the speaker.

4. Branding & Promotion:

• Speaker agrees to be featured in event promotions (name, designation, company, photo, topic).
• Speaker is encouraged (but not obligated) to promote the event within their personal or professional networks.

5. Code of Conduct:

• Speaker will adhere to the JavaScripters Community’s Code of Conduct.
• Harassment, discrimination, or disrespect of any kind will not be tolerated.
  
  
  

🎤 Speaker Guidelines

For a smooth and impactful session, please keep the following guidelines in mind:

Content & Presentation:

• Avoid using content that is promotional or sales-driven.
• Prefer storytelling, real-world examples, live demos, and case studies.
• Keep your talk interactive when possible — engage the audience via Q&A or polls.
• Time your talk well — respect the allocated duration (usually 20–30 minutes for talks, 45–60 minutes for workshops).

Submission & Communication:

• Share your session title, abstract, bio, and photo at least 2 weeks in advance.
• Coordinate with the community team for dry runs or technical setup checks.
• Be available on time on the event day (minimum 30 mins before the session begins).

Respect & Inclusion:

• Respect all participants and fellow speakers.
• Avoid inappropriate language, political or religious bias, or sensitive content.
• Ensure accessibility where possible (e.g., readable slides, avoid jargon-heavy language).

For Any Assistance you can reach out to contact@javascripters-community.com