-
Notifications
You must be signed in to change notification settings - Fork 178
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 cnbapplifecycle repo #821
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Pavel Busko <[email protected]>
02d7499
to
efe0dea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @modulo11, Thanks for opening this PR.
In order to add a new repo, I think you will also have to open a PR to add it here first. That way the automation will create a blank repo. Then @christopherclark can move it over.(oops this is already done in this PR.)- Are any approvers moving over with this repo? If, so can you add them in the same PR?
- Also, since those approvers probably don't want to maintain other diego components, I think you should create a new area for this.
Should we start with the repo just being in the Diego area with no additional approvers. That way we'll have the repo for opening PRs. I guess we'll anyway need to figure out whom to invite for review for some initial work. We can then later figure out how to treat the new lifecycle with regard to approvers. @cloudfoundry/toc WDYT? |
move cnbapplifecycle to its own area in ARP
Following @beyhan's comment, we would like to request a cloudfoundry/cnbapplifecycle repository for the lifecycle created within this RFC.
Is that the right spot?
CC @loewenstein @stephanme @ameowlia