Add 2020 roadmap 🛣️

In tektoncd/community#77 we started on a roadmap
for 2020 for all of Tekton but folks pointed out it makes more sense to
let each project's own roadmap live in the repo with them.

README.md

@@ -16,6 +16,11 @@ The contents of this repo originated from implementing
 (visible to members of
 [the Tekton mailing list](https:/tektoncd/community/blob/master/contact.md#mailing-list)).
 
+* [Background](#background)
+* [Want to start using Triggers?](#want-to-start-using-tekton-triggers)
+* [Want to contribute?](#want-to-contribute)
+* [Project roadmap](roadmap.md)
+
 ## Background
 
 [Tekton](https:/tektoncd/pipeline) is a **Kubernetes-native**,

roadmap.md

@@ -0,0 +1,23 @@
+# Tekton Triggers Roadmap
+
+In 2019 we created a simple system for creating instances of Tekton resources, triggered
+by json payloads sent to HTTP endpoints (Tekton Triggers).
+
+In 2020 we would like to add missing features and then push for a `beta` release in the
+same year.
+
+We are targetting improving the experience for both end users and operators:
+
+* For end users:
+ * [Pluggable core interceptors](https:/tektoncd/triggers/issues/271)
+ * [Increased expression support in TriggerBindings](https:/tektoncd/triggers/issues/367)
+ * [Using TriggerTemplates outside the context of an event](https:/tektoncd/triggers/issues/200)
+ * [Routing to multiple interceptors](https:/tektoncd/triggers/issues/205)
+ * [Dynamic TriggerTemplate parameters](https:/tektoncd/triggers/issues/87)
+ * Support for poll-based triggering (e.g. when a repo changes state)
+ * Support for additional expression languages
+* For operators:
+ * [Improved support for many EventListeners](https:/tektoncd/triggers/issues/370)
+ * Increased traceability (e.g. why did my interceptor reject the event?)
+ * [Performant Triggers](https:/tektoncd/triggers/issues/406)
+ * A scale-to-zero `EventListener`