Move calendar samples into a new folder since this repo is now for all G Suite samples, not just Calendar API Sync.

Author: grant

.gitignore

@@ -0,0 +1,24 @@
+# Compiled class file
+*.class
+
+# Log file
+*.log
+
+# BlueJ files
+*.ctxt
+
+# Mobile Tools for Java (J2ME)
+.mtj.tmp/
+
+# Package Files #
+*.jar
+*.war
+*.ear
+*.zip
+*.tar.gz
+*.rar
+
+# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
+hs_err_pid*
+
+.DS_Store

CONTRIB.md

@@ -0,0 +1,31 @@
+# Contributing: submitting patches and tutorials
+
+## Submitting a pull request
+
+### Contributor License Agreements
+
+We'd love to accept your code patches! However, before we can take them, we
+have to jump a couple of legal hurdles.
+
+Please fill out either the individual or corporate Contributor License
+Agreement.
+
+* If you are an individual writing original source code and you're sure you
+own the intellectual property, then sign an [individual CLA](https://developers.google.com/open-source/cla/individual).
+* If you work for a company that wants to allow you to contribute your work,
+then sign a [corporate CLA](https://developers.google.com/open-source/cla/corporate).
+
+Follow either of the two links above to access the appropriate CLA and
+instructions for how to sign and return it.
+
+1. Sign the contributors license agreement above.
+1. Decide which code you want to submit. A submission should be a set of changes
+   that addresses one issue in the [issue tracker](https://github.com/Google/WebFundamentals/issues).
+   Please don't mix more than one logical change per submission, because it makes
+   the history hard to follow. If you want to make a change
+   (e.g. add a sample or feature) that doesn't have a corresponding issue in the
+   issue tracker, please create one.
+1. **Submitting**: When you are ready to submit, send us a Pull Request. Be
+   sure to include the issue number you've fixed and the name you used to sign
+   the CLA.
+

CONTRIBUTING.md

@@ -1,3 +1,4 @@
+
                                  Apache License
                            Version 2.0, January 2004
                         http://www.apache.org/licenses/
@@ -186,7 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2014 Google Inc.
+   Copyright [yyyy] [name of copyright owner]
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

LICENSE

@@ -1,75 +1,9 @@
-Calendar API Sync Samples
-=========================
+# Java Samples
 
-A set of samples that demonstrate how to utilize sync tokens and etags in the calendar API to sync
-resources more efficiently.
+A collection of samples that demonstrate how to call G Suite APIs in Java.
 
-Introduction
-------------
+## Products
 
-To make it easier for your applications to stay in sync with your users' Google Calendar data the
-API has added support for sync tokens. These tokens store information about the data you've already
-retrieved, so that the next time you make a request you'll only be given the resources that have
-been added, updated, or deleted since your last sync. These samples demonstrate how to sync 
-efficiently, utilizing sync tokens as well as resource versioning (etags).
+### Calendar
 
-Prerequisites
---------------
-
-Read the following guides:
-
-- [Syncing Guide](https://developers.google.com/google-apps/calendar/v3/sync)
-- [Resource Versioning Guide](https://developers.google.com/google-apps/calendar/v3/version-resources)
-
-Setup your Java environment:
-
-- Install [JDK 1.6 or higher](http://www.oracle.com/technetwork/java/javase/downloads)
-- Install [Apache Maven](http://maven.apache.org)
-
-Getting Started
----------------
-
-1. Edit `client_secrets.json` and set the client ID and secret. You can create an ID/secret pair
-   using the [Google Developers Console](https://console.developers.google.com).
-2. Run `mvn compile` to build the project.
-3. Run one of the three samples:
-   * Sync Token Sample:
-     `mvn exec:java -Dexec.mainClass="com.google.api.services.samples.calendar.sync.SyncTokenSample"`
-   * Conditional Modification Sample:
-     `mvn exec:java -Dexec.mainClass="com.google.api.services.samples.calendar.sync.ConditionalModificationSample"`
-   * Conditional Retrieval Sample:
-     `mvn exec:java -Dexec.mainClass="com.google.api.services.samples.calendar.sync.ConditionalRetrievalSample"`
-
-Support
--------
-
-- Stack Overflow Tag: [google-calendar](http://stackoverflow.com/questions/tagged/google-calendar)
-- Issue Tracker: [apps-api-issues](https://code.google.com/a/google.com/p/apps-api-issues/issues/list)
-
-If you've found an error in this sample, please file an issue:
-https://github.com/googlesamples/calendar-sync/issues
-
-Patches are encouraged, and may be submitted by forking this project and
-submitting a pull request through GitHub.
-
-License
--------
-
-Copyright 2014 Google, Inc.
-
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
-
-  http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
+- [Sync Tokens and Etags](calendar/sync)

README.md

@@ -0,0 +1,37 @@
+# Calendar API Sync Samples
+
+A set of samples that demonstrate how to utilize sync tokens and etags in the calendar API to sync
+resources more efficiently.
+
+## Introduction
+
+To make it easier for your applications to stay in sync with your users' Google Calendar data the
+API has added support for sync tokens. These tokens store information about the data you've already
+retrieved, so that the next time you make a request you'll only be given the resources that have
+been added, updated, or deleted since your last sync. These samples demonstrate how to sync
+efficiently, utilizing sync tokens as well as resource versioning (etags).
+
+## Prerequisites
+
+Read the following guides:
+
+- [Syncing Guide](https://developers.google.com/google-apps/calendar/v3/sync)
+- [Resource Versioning Guide](https://developers.google.com/google-apps/calendar/v3/version-resources)
+
+Setup your Java environment:
+
+- Install [JDK 1.6 or higher](http://www.oracle.com/technetwork/java/javase/downloads)
+- Install [Apache Maven](http://maven.apache.org)
+
+## Getting Started
+
+1. Edit `client_secrets.json` and set the client ID and secret. You can create an ID/secret pair
+   using the [Google Developers Console](https://console.developers.google.com).
+1. Run `mvn compile` to build the project.
+1. Run one of the three samples:
+   * Sync Token Sample:
+     `mvn exec:java -Dexec.mainClass="com.google.api.services.samples.calendar.sync.SyncTokenSample"`
+   * Conditional Modification Sample:
+     `mvn exec:java -Dexec.mainClass="com.google.api.services.samples.calendar.sync.ConditionalModificationSample"`
+   * Conditional Retrieval Sample:
+     `mvn exec:java -Dexec.mainClass="com.google.api.services.samples.calendar.sync.ConditionalRetrievalSample"`