diff --git a/ROADMAP.md b/ROADMAP.md index e1a7e2ae3..0b5f2910d 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1,7 +1,7 @@ ## Velero Roadmap ### About this document -This document provides a link to the [Velero Project board](https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/board?repos=99143276,112385197,190224441,214524700,214524630,213946861) that serves as the up to date description of items that are in the release pipeline. The board has separate swim lanes based on prioritization. Most items are gathered from the community or include a feedback loop with the community. This should serve as a reference point for Velero users and contributors to understand where the project is heading, and help determine if a contribution could be conflicting with a longer term plan. You will need the ZenHub plugin to view the board. +This document provides a link to the [Velero Project boards](https://github.com/vmware-tanzu/velero/projects) that serves as the up to date description of items that are in the release pipeline. The release boards have separate swim lanes based on prioritization. Most items are gathered from the community or include a feedback loop with the community. This should serve as a reference point for Velero users and contributors to understand where the project is heading, and help determine if a contribution could be conflicting with a longer term plan. ### How to help? Discussion on the roadmap can take place in threads under [Issues](https://github.com/vmware-tanzu/velero/issues) or in [community meetings](https://velero.io/community/). Please open and comment on an issue if you want to provide suggestions, use cases, and feedback to an item in the roadmap. Please review the roadmap to avoid potential duplicated effort. diff --git a/site/content/community/_index.md b/site/content/community/_index.md index 68762dbd9..b07aea2bf 100644 --- a/site/content/community/_index.md +++ b/site/content/community/_index.md @@ -7,11 +7,9 @@ id: community If you’re a newcomer, check out the “[Good first issue](https://github.com/vmware-tanzu/velero/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+first+issue%22)” and “[Help wanted](https://github.com/vmware-tanzu/velero/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3A%22Help+wanted%22+)” labels in the Velero repository. -Read how [we're using ZenHub](https://velero.io/docs/main/zenhub) for project and roadmap planning. - If you are ready to jump in and test, add code, or help with documentation, follow the instructions on our [Start contributing](https://velero.io/docs/main/start-contributing/) documentation for guidance on how to setup Velero for development. -You can follow the work we do, see our milestones, and our backlog on our [ZenHub board](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). +You can follow the work we do, see our milestones, and our backlog on our [GitHub project boards](https://github.com/vmware-tanzu/velero/projects). * Follow us on Twitter at [@projectvelero](https://twitter.com/projectvelero) * Join our Kubernetes Slack channel and talk to over 800 other community members: [#velero](https://kubernetes.slack.com/messages/velero) diff --git a/site/content/docs/main/support-process.md b/site/content/docs/main/support-process.md index fc06e72e9..d07268c52 100644 --- a/site/content/docs/main/support-process.md +++ b/site/content/docs/main/support-process.md @@ -35,10 +35,10 @@ Generally speaking, new GitHub issues will fall into one of several categories. - If you resolve the issue with the user, close it out - If the issue ends up being a feature request or a bug, update the title and follow the appropriate process for it - If the reporter becomes unresponsive after multiple pings, close out the issue due to inactivity and comment that the user can always reach out again as needed - + ## End of Week We ensure all GitHub issues worked on during the week on are labeled with `Investigating` and `Needs Info` (if appropriate), and have updated comments so the next person can pick them up. -[0]: https://app.zenhub.com/workspaces/velero-5c59c15e39d47b774b5864e3/board?repos=99143276,112385197,213946861,190224441,214524700,214524630 +[0]: https://github.com/vmware-tanzu?q=velero&type=&language= [1]: https://groups.google.com/forum/#!forum/projectvelero diff --git a/site/content/docs/main/zenhub.md b/site/content/docs/main/zenhub.md deleted file mode 100644 index 5ae51702d..000000000 --- a/site/content/docs/main/zenhub.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: "ZenHub" -layout: docs ---- - -As an Open Source community, it is necessary for our work, communication, and collaboration to be done in the open. -GitHub provides a central repository for code, pull requests, issues, and documentation. When applicable, we will use Google Docs for design reviews, proposals, and other working documents. - -While GitHub issues, milestones, and labels generally work pretty well, the Velero team has found that product planning requires some additional tooling that GitHub projects do not offer. - -In our effort to minimize tooling while enabling product management insights, we have decided to use [ZenHub Open-Source](https://www.zenhub.com/blog/open-source/) to overlay product and project tracking on top of GitHub. -ZenHub is a GitHub application that provides Kanban visualization, Epic tracking, fine-grained prioritization, and more. It's primary backing storage system is existing GitHub issues along with additional metadata stored in ZenHub's database. - -If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub for your regular workflow (to see open bug reports or feature requests, work on pull requests). However, if you'd like to be able to visualize the high-level project goals and roadmap, you will need to use the free version of ZenHub. - -## Using ZenHub - -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/content/docs/v1.5/zenhub.md b/site/content/docs/v1.5/zenhub.md deleted file mode 100644 index 5ae51702d..000000000 --- a/site/content/docs/v1.5/zenhub.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: "ZenHub" -layout: docs ---- - -As an Open Source community, it is necessary for our work, communication, and collaboration to be done in the open. -GitHub provides a central repository for code, pull requests, issues, and documentation. When applicable, we will use Google Docs for design reviews, proposals, and other working documents. - -While GitHub issues, milestones, and labels generally work pretty well, the Velero team has found that product planning requires some additional tooling that GitHub projects do not offer. - -In our effort to minimize tooling while enabling product management insights, we have decided to use [ZenHub Open-Source](https://www.zenhub.com/blog/open-source/) to overlay product and project tracking on top of GitHub. -ZenHub is a GitHub application that provides Kanban visualization, Epic tracking, fine-grained prioritization, and more. It's primary backing storage system is existing GitHub issues along with additional metadata stored in ZenHub's database. - -If you are a Velero user or Velero Developer, you do not _need_ to use ZenHub for your regular workflow (to see open bug reports or feature requests, work on pull requests). However, if you'd like to be able to visualize the high-level project goals and roadmap, you will need to use the free version of ZenHub. - -## Using ZenHub - -ZenHub can be integrated within the GitHub interface using their [Chrome or FireFox extensions](https://www.zenhub.com/extension). In addition, you can use their dedicated [web application](https://app.zenhub.com/workspace/o/vmware-tanzu/velero/boards?filterLogic=all&repos=99143276). diff --git a/site/data/docs/main-toc.yml b/site/data/docs/main-toc.yml index a6f419d9d..414840374 100644 --- a/site/data/docs/main-toc.yml +++ b/site/data/docs/main-toc.yml @@ -91,9 +91,7 @@ toc: url: /api-types - page: FAQ url: /faq - - page: ZenHub - url: /zenhub - page: Support process url: /support-process - - page: For maintainers + - page: For maintainers url: /maintainers diff --git a/site/data/docs/v1-5-toc.yml b/site/data/docs/v1-5-toc.yml index a6f419d9d..414840374 100644 --- a/site/data/docs/v1-5-toc.yml +++ b/site/data/docs/v1-5-toc.yml @@ -91,9 +91,7 @@ toc: url: /api-types - page: FAQ url: /faq - - page: ZenHub - url: /zenhub - page: Support process url: /support-process - - page: For maintainers + - page: For maintainers url: /maintainers diff --git a/site/layouts/index.redirects b/site/layouts/index.redirects index 402e3bdc8..b336ccfb1 100644 --- a/site/layouts/index.redirects +++ b/site/layouts/index.redirects @@ -5,7 +5,7 @@ /docs/latest/* /docs/{{ $latest }}/:splat /docs/troubleshooting /docs/{{ $latest }}/troubleshooting /docs/supported-providers /docs/{{ $latest }}/supported-providers -/docs/zenhub /docs/{{ $latest }}/zenhub +/docs/zenhub /docs/{{ $latest }}/support-process /docs/install-overview /docs/{{ $latest }}/basic-install /docs/start-contributing /docs/{{ $latest }}/start-contributing /docs/customize-installation /docs/{{ $latest }}/customize-installation