Closed rmuir closed 9 years ago
I agree. I started this for analysis plugins (see https://github.com/elastic/elasticsearch-analysis-phonetic/commit/96bf53cb25c6accde96adc73e0295170d29d9b43) but I still need to do it for other repos...
Thanks for the heads up. Assigning this to me.
I think we should probably disable github issues on each plugin repo, once the "see core" notice has been added to the README
@clintongormley It makes sense. I'll do that.
I updated and disabled issues for:
I did not disable issues when a lot of issues are still opened. We first need to look at them and move them to elasticsearch repo if it makes sense. Only documentation has been updated:
Stuff like https://github.com/elastic/elasticsearch-cloud-aws is confusing, because it doesnt mention that the plugin moved to main ES repository for the 2.0 release. Users only see "master: build from source" and probably think we have done nothing at all.
I think we should have at the very top of the README files for all the plugins we have moved in, some note that points you to their new location for 2.0+