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

Creation of new repository cloudfoundry/pcap-release for App Runtime Platform WG #363

Closed
plowin opened this issue Jul 19, 2022 · 4 comments
Assignees
Labels

Comments

@plowin
Copy link
Contributor

plowin commented Jul 19, 2022

Hi,

raised via an issue on cf-deployment, we raised a proposal of a new CF component that can support debugging network issues for CF applications by enabling app developers to take their own tcpdump. The initial proposal was introduced on July 6th in the "App Runtime Platform WG", see agenda and recording.

The code of the demo is currently included in https://github.com/domdom82/pcap-server-release.

If our App Runtime Platform WG lead @ameowlia can approve this request, we kindly ask you to create the following repository and merge our PR to toc/working-groups/app-runtime-platform.md created shortly.

We suggest this repository name and will include the sources in there. We will take care of setting up CI/CD and maintaining this repo in the future:
https://github.com/cloudfoundry/pcap-release

plowin added a commit to plowin/community that referenced this issue Jul 19, 2022
This repo does not yet exist. This PR can be merged after its approval and creation via cloudfoundry#363
@stephanme
Copy link
Contributor

https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0007-repository-ownership.md mentions that TOC needs to approve the creation and WG lead (@ameowlia) + TOC needs to approve adding the new repo to a WG (= #364).

I guess that repo is created by @christopherclark after approval.

@ameowlia
Copy link
Member

I approve!

@stephanme
Copy link
Contributor

+1

@AP-Hunt
Copy link
Contributor

AP-Hunt commented Jul 19, 2022

Closing because it's not necessary. Org automation in #364 will take care of it all.

@AP-Hunt AP-Hunt closed this as completed Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

4 participants