README.md in solidus_mailchimp_sync-1.0.0.beta01 vs README.md in solidus_mailchimp_sync-1.0.0.beta02

@@ -65,19 +65,30 @@
 could take a while:
 
     RAILS_ENV=production rake solidus_mailchimp_sync:bulk_sync
 
 Known issues/To do
--------
+------------------
 
 * If a user changes their email addresses, their old orders may be no longer associated with
   them in mailchimp, they will wind up with two mailchimp customer records. (Mailchimp
   docs suggest you can change an existing Customer's id itself, but it didn't seem to work.
   can't change an existing Customer's email address)
 * Debounce: This may send a LOT of updates to mailchimp, when you're editing something.
   In checkout process there are sometimes multiple syncs for order, not sure why.
   Have an idea for an implementation debounce feature that could debounce/coalesce mailchimp
   syncs in the general case.
+
+Maintenance Expectations
+------------------------
+
+We've develoepd this for our own clients needs. We are sharing it with the intention
+of sharing/collaborating with other developers, so they don't have to re-invent
+the wheel.
+
+We think this is solid and reliable code, but our future ability to attend to
+any maintenance or development will depend on our time and clients needs. We
+will do our best to respond to PR'.
 
 Testing
 -------
 
 First bundle your dependencies, then run `rake`. `rake` will default to building the dummy app if it does not exist, then it will run specs, and [Rubocop](https://github.com/bbatsov/rubocop) static code analysis. The dummy app can be regenerated by using `rake test_app`.