sorry for the big honking commit. we're cleaning up our git/scm proce…

…ss now...

.gitignore

@@ -0,0 +1,6 @@
+.DS_Store
+node_modules
+artifacts
+.*.swp
+*~
+.svn

DEPRECATIONS.md

@@ -0,0 +1,79 @@
+
+As Mojito matures, there are a number of changes/cleanups that we want to make
+that break backwards-compatilibity.  However, we don't want to prevent you from
+upgrading in a timely fashion, so that you can use the latest and greatest
+version of mojito.
+
+To enable both our needs and yours, we need a clear, predictable path into the
+future.
+
+
+
+Currently Deprecated
+====================
+
+
+### Deprecated but Available
+
+* (2012-04-23) The `autoload/` directory is going away in favor of
+`yui_modules/`, which better reflects its contents.  Everthing else about it is
+the same, only the name has changed.  You can start using `yui_modules/` today.
+
+* (2012-04-23) The `.guid` member of Mojito metadata (such as binder metadata)
+is going away.  Often there's an associated member which more specifically
+expresses the intent of the unique ID (for example `.viewId` or `.instanceId`).
+
+* (2012-04-23) `ac.dispatch()` will be going away.  (This already emits a
+warning.)  Currently the best alternative is `ac._dispatch()`.
+
+
+### Deprecated with Warnings
+nothing for mojito 0.3
+
+
+### Removed
+nothing for mojito 0.3
+
+
+
+Deprecation Process
+===================
+A feature will move through the following phases, at a well-defined pace.
+
+
+### "Deprecated but Available" Phase
+
+* The documentation is updated to mark the feature as "deprecated".
+* The feature will be in this phase until the end of the quarter year.
+(It's possible that a feature won't spend much time in this phase, if it is
+deprecated near the end of the quarter.)
+
+
+### "Deprecated with Warning" Phase
+
+* The feature is removed from the documentation.
+* Mojito emits a warning (if possible) if the feature is used.
+* The feature will spend a full quarter in this phase.
+
+
+### "Removed" Phase
+
+* The feature (and warning) is removed from Mojito.
+
+
+### Example
+
+* On 2012-04-19 (Q2), Mojito deprecates the "foo" feature by saying so in the
+documentation.  This event is also mentioned in an email and/or blog post for
+the next release.  It's also added to this DEPRECATIONS.md document.
+
+* On the next release after 2012-06-30 (end of Q2), Mojito removes
+documentation for feature "foo" and adds a warning if someone tries to use
+feature "foo".  It is still documented in this DEPRECATIONS.md document.
+
+* On the next releaes after 2012-09-30 (end of Q3), Mojito removes feature
+"foo" (and the associated warnings).  It is mentioned as "removed" in this
+DEPRECATIONS.md document.
+
+
+