Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 2020 roadmap 🛣️ #236

Merged
merged 1 commit into from
Apr 7, 2020
Merged

Conversation

bobcatfish
Copy link
Contributor

Changes

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.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

@tekton-robot tekton-robot requested review from imjasonh and a user March 24, 2020 15:10
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 24, 2020
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.
bobcatfish added a commit to bobcatfish/community that referenced this pull request Mar 24, 2020
I have put together a roadmap for 2020, which attempts to represent the
most requested of the features and issues that we've seen so far. I did
this by:

* [Reviewing the 2019 roadmap](https://docs.google.com/document/d/1zClmMJZU63kEDedjxTI99MCK-mXqm-Ym7PBfjMG5tQE/edit)
* Looking at the oldest and most commented on issues in Tekton Pipelines
  and Tekton Triggers

I also added a section on Tekton's mission: this is the mission that
we've been using at Google when talking about Tekton - so this is a
great chance for anyone who is viewing Tekton differently to mention
their mission and vision so we can tweak it. Having more clarity around
what everyone is hoping accomplish with Tekton will make it easier to
make decisions around features, etc.

Roadmaps for individual projects:
* Pipelines: tektoncd/pipeline#2275
* Triggers: tektoncd/triggers#498
* Catalog: tektoncd/catalog#236
* Dashabord: TBD, initial thoughts in tektoncd#77 (comment)
* CLI: TBD
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 24, 2020
@vdemeester
Copy link
Member

(will need to be "sent" to v1beta1 branch)

@bobcatfish
Copy link
Contributor Author

plz can has lgtm 🙏

@bobcatfish bobcatfish mentioned this pull request Apr 6, 2020
2 tasks
@bobcatfish
Copy link
Contributor Author

Created #259 to add this to v1beta1 also

bobcatfish added a commit to bobcatfish/community that referenced this pull request Apr 6, 2020
I have put together a roadmap for 2020, which attempts to represent the
most requested of the features and issues that we've seen so far. I did
this by:

* [Reviewing the 2019 roadmap](https://docs.google.com/document/d/1zClmMJZU63kEDedjxTI99MCK-mXqm-Ym7PBfjMG5tQE/edit)
* Looking at the oldest and most commented on issues in Tekton Pipelines
  and Tekton Triggers

I also added a section on Tekton's mission: this is the mission that
we've been using at Google when talking about Tekton - so this is a
great chance for anyone who is viewing Tekton differently to mention
their mission and vision so we can tweak it. Having more clarity around
what everyone is hoping accomplish with Tekton will make it easier to
make decisions around features, etc.

Roadmaps for individual projects:
* Pipelines: tektoncd/pipeline#2275
* Triggers: tektoncd/triggers#498
* Catalog: tektoncd/catalog#236
* Dashabord: TBD, initial thoughts in tektoncd#77 (comment)
* CLI: TBD
@vdemeester vdemeester changed the base branch from master to v1beta1 April 7, 2020 05:33
@tekton-robot tekton-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 7, 2020
@vdemeester vdemeester changed the base branch from v1beta1 to master April 7, 2020 05:33
@tekton-robot tekton-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 7, 2020
@vdemeester
Copy link
Member

/lgtm
I'll add it to v1beta1 branch 😉

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2020
@vdemeester
Copy link
Member

/retest

@tekton-robot tekton-robot merged commit 3a5126e into tektoncd:master Apr 7, 2020
tekton-robot pushed a commit to tektoncd/community that referenced this pull request Apr 8, 2020
I have put together a roadmap for 2020, which attempts to represent the
most requested of the features and issues that we've seen so far. I did
this by:

* [Reviewing the 2019 roadmap](https://docs.google.com/document/d/1zClmMJZU63kEDedjxTI99MCK-mXqm-Ym7PBfjMG5tQE/edit)
* Looking at the oldest and most commented on issues in Tekton Pipelines
  and Tekton Triggers

I also added a section on Tekton's mission: this is the mission that
we've been using at Google when talking about Tekton - so this is a
great chance for anyone who is viewing Tekton differently to mention
their mission and vision so we can tweak it. Having more clarity around
what everyone is hoping accomplish with Tekton will make it easier to
make decisions around features, etc.

Roadmaps for individual projects:
* Pipelines: tektoncd/pipeline#2275
* Triggers: tektoncd/triggers#498
* Catalog: tektoncd/catalog#236
* Dashabord: TBD, initial thoughts in #77 (comment)
* CLI: TBD
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants