First, read this:
GTUGs are for developers who are interested in Google's developer technology; everything from the Android, App Engine, and Wave platforms, to product APIs like the YouTube API and the Google Calendar API, to initiatives like OpenSocial.
A GTUG can take many forms -- from just a few people getting together to watch our latest video, to large gatherings with demos and lectures, to events like code sprints and hackathons. However, at the core, GTUGs are focused on developers and technical content, and the core audience should be developers.
Make sure you've checked the chapter list and see that no other chapters are in your area. (If there is one, great! Contact the organizer and join in the fun.) If you have any questions or concerns, ask them in the general GTUG forum. Everything check out? Okay, moving on: Naming
- Decide on a short and catchy name. The de-facto standard that
we
ended up using is of the form <general location> GTUG. So if you
are located in Berlin Germany, it could be Berlin GTUG, or something
similar. The location doesn't have to be a city name. It could also be
a region such as SV-GTUG, where "SV" stands for Silicon Valley.
- As a general rule, you should not name your chapter after too large a region, like a state or country. The exception is if you actually plan to rotate your events in different areas of the state/country.
- Check that the name you choose is available as an internet domain. For
example "berlin-gtug.org" would be a logical internet address for a GTUG based in Berlin, Germany. Having your own domain isn't necessary, but it's good to know it's available if you choose to get it in the future.
Submit Application
- Fill out a New Chapter Application (it's pretty short, promise).
- You'll be contacted within a few days to invite you to the manager's forum and get you listed in the directory. In the meantime, check out the wiki for all the shared best practices and tips for running a user group.
Still have questions or feedback?Join the general GTUG forum!
|
|
