move todo list into JIRA
diff --git a/README.md b/README.md
index 0093e1d..b00a080 100644
--- a/README.md
+++ b/README.md
@@ -58,38 +58,11 @@
I hope you agree we can ship this with a few warnings so people can get a
hang of it.
-Here is a rough list of features squared against future milestones:
-Milestone 2: Be creator friendly
- - Make it easy to build a CouchDB plugin by providing one or more easy
- to start templates.
- - Make it easy to publish new plugins and new versions of existing plugins.
- - Make it easy to supply packages for multiple Erlang & CouchDB versions.
+A roadmap, progress and issues can be found here:
-Milestone 3: Public registry
- - Instead of hardcoding a list of plugins into Futon/Fauxton, we load
- a list of applicable plugins from a central (and configurable)
- plugins repository.
- - This allows plugin authors to publish new plugins and new versions
- of existing plugins independently.
+https://issues.apache.org/jira/issues/?jql=component+%3D+Plugins+AND+project+%3D+COUCHDB+AND+resolution+%3D+Unresolved+ORDER+BY+priority+DESC
-Milestone 4: Other Languages
- - Figure out how to handle C-dependencies for Erlang plugins.
- - Figure out how to allow other language plugins
- (c.f. non-JS query servers)
-
-Milestone X: Later
- - Add some account/identity/maybe crypto-web-of-trust system for
- authors to publish “legit” plugins.
- - Sign & verify individual releases.
- - Handle unclean un/installs if CouchDB crashes while installing/
- uninstalling.
- - Add `--aditional_plugin_dir` parameter to `couchdb`.
-
-A few more things that can happen concurrently depending on what
-plugins require:
- - Integrate Erlang/JS tests in the installation
- - Integrate docs
## How it works
diff --git a/src/couch_plugins.erl b/src/couch_plugins.erl
index 2b110bc..a4950be 100644
--- a/src/couch_plugins.erl
+++ b/src/couch_plugins.erl
@@ -298,43 +298,3 @@
% [geocouch-{geocouch_version}-{erlang_version}/config/config.erlt]
% [geocouch-{geocouch_version}-{erlang_version}/share/]
-
-
-% config.erlt:
-% // {{Section, Key}, Value}
-% {{"httpd_db_handlers", "_spatial_cleanup"}, "{couch_spatial_http, handle_cleanup_req}"}
-% {{"httpd_design_handlers", "_spatial"}, "{couch_spatial_http, handle_spatial_req}"}
-% {{"httpd_design_handlers", "_list"}, "{couch_spatial_list, handle_view_list_req}"}
-% {{"httpd_design_handlers", "_info"}, "{couch_spatial_http, handle_info_req}"}
-% {{"httpd_design_handlers", "_compact"}, "{couch_spatial_http, handle_compact_req}"}
-
-% milestones
-% 1. MVP
-% - erlang plugins only
-% - no c deps
-% - install via futon (admin only)
-% - uninstall via futon (admin only)
-% - load plugin.tgz from the web
-% - no security checking
-% - no identity checking
-% - hardcoded list of plugins in futon
-% - must publish on *.apache.org/*
-
-% 2. Creator friendly
-% - couchdb plugin template
-% - easy to publish
-
-% 3. Public registry
-% - plugin authors can publish stuff independently, shows up in futon
-%
-
-% XXX Later
-% - signing of plugin releases
-% - signing verification of plugin releases
-
-
-% Questions:
-% - where should the downloaded .beam files put?
-% - in couch 1.x.x context
-% - in bigcouch context
-% - what is a server-user owned data/ dir we can use for this, that isn’t db_dir or index_dir or log or var/run or /tmp
