Naming guidelines

Program name

The official name of the platform is GDG.
  • DO

    Refer to the platform as “GDG”.

  • DO

    Describe the platform as “GDG stands for Google Developers Groups and is a platform offered by Google Developers to support community-run developer groups”.

  • DON’T

    Refer to the platform as “Google Developer Groups” or “Google Developers Groups” instead of "GDG".

Chapter names

Each local GDG chapter should be named as “GDG [Location]”.
  • DO

    Name your chapter with a “Location” that is a city or area (e.g. London, Silicon Valley).

  • DO

    Refer to your chapter as “GDG [Location]”.

  • DO

    Refer to your GDG chapter as “a community-run developer group supported by Google Developers”

  • DON’T

    Refer to your chapter as a “Google Developer Group Location” or “Google Developers Group Location”.

  • DON’T

    Name your chapter with a “Location” that is a state, country, region, or continent (e.g. California, France, EMEA, Africa).

Lockup guidelines

The logo represents the platform’s identity, creates recognition, and should be used in a consistent way. The GDG logo consists of:

  • The Google Developers logomark (icon): This is the unifying graphic element across all Google Developers products and programs.
  • The GDG text lockup: The logomark combined with the official platform name (GDG) in Google Sans font.

How to customize the GDG lockup for your chapter

Rules are in place to ensure consistent branding of the GDG platform across the community. If you don’t have or want to use a custom chapter lockup, use the main GDG lockup instead to represent the platform.
  • GDG Dublin lockup
  • DO

    Customize the GDG lockup for your chapter using the official lockup generator tool (made available only to confirmed members of the platform) and following the naming guidelines indicated above.

  • GDG Dublin custom lockup
  • DO

    If you want to further customize your brand, create a visual asset that can be shown in addition to but NOT as part of the lockup. The spacing around the lockup should at a minimum match the height of “GDG”.

  • Google Developers lockup
  • DON’T

    Use the Google Developers name or lockup to represent your chapter. Always use your custom GDG [Location] lockup OR the main GDG lockup instead (but don’t use both at the same time!).

  • GDG localized lockup
  • DON’T

    Localize "GDG" or the Location within the lockup. Always use "GDG" and your location in English and localize comms instead.

  • Lockup with custom logo
  • DON’T

    Alter or distort the official lockup in any way, including altering fonts, colors, shapes, proportions, or rotating/flipping it in any direction.

  • Knockout lockup
  • DON’T

    Use a knockout version unless absolutely necessary for print/swag. If using a flat knockout lockup don’t apply any color besides white.

  • Lockup with busy background
  • DON’T

    Use the lockup on a poorly contrasting or busy background.

  • Lockup with custom backdrop
  • DON’T

    Overlap or crowd the lockup with other custom elements including text or artwork.

Code of conduct

When you join our programs, you’re joining a community. And like any growing community, a few ground rules about expected behavior are good for everyone. These guidelines cover both online (e.g. mailing lists, social channels) and offline (e.g. in-person meetups) behavior.

Violations of this code of conduct can result in members being removed from the program. Use your best judgement, and if you’d like more clarity or have questions feel free to reach out.

These guidelines are modeled after the Ubuntu Code of Conduct, and likewise licensed under Creative Commons Attribution-Share Alike 3.0.

Community guidelines

Be nice. We're all part of the same community, so be friendly, welcoming, and generally a nice person. Be someone that other people want to be around.

Be respectful and constructive. Remember to be respectful and constructive with your communication to fellow members. Don't get into flamewars, make personal attacks, vent, or rant unconstructively. Everyone should take responsibility for the community and take the initiative to diffuse tension and stop a negative thread as early as possible.

Be collaborative. Work together! We can learn a lot from each other. Share knowledge, and help each other out.

Participate. Join in on discussions, show up for in-person meetings regularly, offer feedback, and help implement that feedback.

Step down considerately. If you have some form of responsibility in your community, be aware of your own constraints. If you know that a new job or personal situation will limit your time, find someone who can take over for you and transfer the relevant information (contacts, passwords, etc.) for a smooth transition.

Basic etiquette for online discussions. Don’t send messages to a big list that only need to go to one person. Keep off topic conversations to a minimum. Don’t be spammy by advertising or promoting personal projects which are off topic.

Organizer acknowledgements

  1. The Google Event Community Guidelines and Anti- Harassment Policy must be followed. This Anti-Harassment Policy template is available for organizers to enstate in their community.
  2. It’s NOT ok to use GDG for profit. Organizers should only charge attendees for ticket entry and/or get sponsorships to cover costs of event operations (e.g. food and drinks, venue, setup, speakers) if needed.
  3. It’s ok to partner with other groups and companies to arrange speakers, venues, and sponsorships.
  4. It’s ok to talk about non-Google technologies in your community. We want to promote learning across technologies without bashing any company including Google or others.
  5. The use of the GDG name/logo is granted to organizers so long as they are in good standing with Google Developers and follow the GDG brand guidelines.
  6. GDG chapters must remain active and run at least 1 event every 90 days. Failure to host events and log activity to the GDG program may result in removal from the GDG program.
  7. GDG chapter organizers are expected to be willing and available to communicate with their Google Regional Lead in a timely fashion when requested.