# replicatedhq
###### 'collaboration'

## proposed email

From: TIGER
To:
Orlin Vasilev - VMware <[e-mail]>
Daniel Jiang - VMware <[e-mail]>
Yonghui Li - VMware <[e-mail]>
Jiaolin Yang - VMware <[e-mail]>
Wes Hayutin - Red Hat <[e-mail]>
Grant Miller - Replicated <[e-mail]>
Marc Campbell - Replicated <[e-mail]>
Chris Sanders - Replicated <[e-mail]>
Subject: Greetings from The Velero Community!

Dear Replicated,

TL;DR, want to collab on [replicatedhq/local-volume-provider](https://github.com/replicatedhq/local-volume-provider)

There have been [requests in upstream velero project to support non-object store backends such as NFS](https://github.com/vmware-tanzu/velero/issues/1229). The *local-volume-provider* plugin would suit this purpose perfectly.

However, it is not considered supported or tested by the Velero community at this time.

We wanted to reach out possible collaborations between Replicated and Velero community to get *local-volume-provider* plugin officially supported.

The work will include
- Adding *local-volume-provider* to Velero CI systems.
- Updating *local-volume-provider* to work with latest Velero main
- Kopia support [replicatedhq/local-volume-provider#32](https://github.com/replicatedhq/local-volume-provider/issues/32)
- Discussions around where upstream should be for *local-volume-provider*
- Whether [replicatedhq/local-volume-provider](https://github.com/replicatedhq/local-volume-provider) would become a fork and move upstream development to [project-velero](https://github.com/project-velero) or vice versa
- Bringing on Replicated members as a Velero maintainer

Sincerely,

The Velero Community

#### Ways to reach us:
- [GitHub](https://github.com/vmware-tanzu/velero/):
- [Issues](https://github.com/vmware-tanzu/velero/issues)
- [Discussions](https://github.com/vmware-tanzu/velero/discussions)
- [Kubernetes Slack](https://app.slack.com/client/T09NY5SBT/C6VCGP4MT) ([request invite!](https://slack.k8s.io/))
- [Google Group](https://groups.google.com/g/projectvelero)

<!-- structure
* intro
* specifics about the type of collaboration on /local-volume-provider
* invite to the velero community mtg
-->

PS. We got Marc and Chris email from Grant response from [e-mail]

Wes is my manager.
Orlin is Velero community manager.

## original email

What is the best channel for reaching out about collab/testing opportunities between replicatedhq/local-volume-provider: A Velero plugin for backup/restore directly to Kubernetes volumes. (github.com) and vmware-tanzu/velero: Backup and migrate Kubernetes applications and their persistent volumes (github.com) communities?

My team intend on getting local-volume-provider plugin tested against latest upstream velero and to bring in "official velero support" for the plugin.

Hoping to get some names/slack channels/emails for my team to reach out soon.